1. A Support Environment For Machine
2. A Support Environment For Machine Learning

HTTP/HTTPS Proxy Support. Known limitations, use cases, and workarounds. Following is a summary of current limitations on the Docker for Mac networking stack, along with some ideas for workarounds. There is no docker0 bridge on macOS. Because of the way networking is implemented in Docker for Mac, you cannot see a docker0 interface. Jan 18, 2018 - The Classic environment involves Mac OS 9 running as an application within some versions of Mac OS X, allowing you to use your older applications. However, applications running in the Classic environment cannot take advantage of the new features in Mac OS X, such as protected memory.

Hi All, We're a Windows shop (mix of 50 laptops and desktops; mostly Dell). We have a couple of new employees that say they need a Mac. I'm wondering if anyone has estimates on how much extra time and costs are associated with supporting a mixed environment. I'm a one person show here (actually a 1/2 person show because I work 1/2 time), so, I'm concerned that if I need to support a mixed environment other things are going to suffer. Things that I'm concerned about:.

need to purchase/maintain/support 2 of everything (OSes, office apps, VPN, etc.). our CRM only has a windows client (sure we can run parallels but that complicates support and increases costs even more).

added costs of more expensive hardware (probably not a huge deal). all the 'group management' features of Windows (group policy, scripts, etc.) don't work on macs so they need to be managed more individually (help me here if I'm wrong).

no central print drivers. what else? Anyone have direct experience in this or perhaps know of independent studies that look at this type of thing? Thanks in advance for any advice and/or opinions. You will be able to find studies and reports that prove just about anything that you want to prove.

The real question here is what is the business case for such a move? Your support time would be mitigated by your education. Once you learned what you need you wouldn't notice much difference in support but why should the company educate you (and future employees) when the new hardware has no benefits to the business model (unless I am missing something)? There was a time (only 12-15 years ago in my work) that Apple was the defacto hardware for graphics stuff. I built a guy a smoking desktop with sata raid in 2001 and that was the last time I agreed that Apple had anything on a PC.

The hardware options available today and software compatibility make it all but senseless to introduce new hardware to your already functional environment. Talk to you bosses and let then know what you think. I would personally tell them that rather than retrain IT, the users might want to consider using the systems that 90% of the world use for their needs. If these users are spending all day in Adobe you might have to say 70% but if they are spending any time in CAD apps you might be able to say 99%.

Any way you look at it, the PC is the current standard for office applications. Anyone saying anything else is lying to you or clueless. As for your title. The cost of adding support for macs might be your sanity if you are already over-worked. We have a few Macs and the cost of maintaining them isn't any more than for a PC. The OS is significantly cheaper, but depending on any special software they might need, software costs could be more or less. Most software that runs on both Windows and OSX doesn't cost any more for one than the other.

The hardware is usually much more expensive, but it also tends to last longer and have less problems in my experience. You can connect the Macs to your domain and access domain shares and printers too. Really the only significant headache is learning how to support OSX if you haven't done it before. I found that MAC users asked fewer questions. When I worked for the community college we had a couple of labs with MACs and about 15 teachers with them.

They did not tend to break down as much and just seemed to run fine. I bought a MAC Bible and was able to answer the questions. You should not need a second VPN. Office for the MAC installs easily and operates pretty much like Office for Windows. The hardware is more expensive. Wether it's worth the extra costs is debatable.

Depends on the users needs. If they need a MAC to run some specialized software then that's what you got to have.

Not sure how to manage them in an AD environment, sorry:( Print drivers can be centralized if you learn how to do it with CUPS. Anyone know of another way to let MACs print to a windows print server?

Mac OS X: How to manually add a Windows shared printer You could also just print from the MAC directly to the printer's IP address. Hmm, consider how bitchy the MAC users are going to be if you force a Windows PC on them. EDIT: you can translate that last comment to; You will get more tickets from MAC users using a Windows PC than MAC users using a MAC. Speaking as someone who has been supporting a mixed environment for years, I can tell you that this really depends on the actual Mac users themselves. In general, experienced Mac users require a lot less support than Windows users, and will be able to manage their systems themselves. Most issues will be things like connectivity to SMB shares on non-Windows OSes. Apple seems to be genetically incapable of NOT stuffing up SMB every time they release a new OS.

'need to purchase/maintain/support 2 of everything' Not a big deal unless you have a LOT of macs. The machine comes with the OS preinstalled, and OS upgrades are ridiculously cheap.

Office 2010-2011 compatibility is fine. Not sure what your VPN concerns are, OS X has its own vpn client, and Cisco has a couple of client options as well, so this shouldn't be a big deal. Do a google search, you'll find many Universities have documentation on Macs and enterprise VPNs. Flir thermacam b2 driver for mac. 'our CRM only has a windows client ' Would the Mac user actually NEED to use the CRM? If they're a creative type, they probably don't. If they do, this is probably the closest thing to a deal-breaker. Virtualization could solve this, so could having them RDP into a terminal server if that's an option.

The Microsoft RDP client for Mac is excellent. 'added costs of more expensive hardware (probably not a huge deal)' If they want a Mac Pro, yeah, they're ridiculously expensive, but Mac Minis are cheap, and will work for almost anything but high-end graphics. 'all the 'group management' features of Windows (group policy, scripts, etc.) don't work on macs' Again, not a big deal unless you have a lot of Mac users.

Scripts don't work,of course, but not a big deal, because the things those scripts do would not make sense on a Mac anyway. You can get software that provides some group policy support, but why bother? Most GP settings also wouldn't make sense on a Mac, so you're not really losing much. There are lots of resources online for people who need to support mixed environments.

'no central print drivers' Not really a problem. Most printers can be used with the built-in drivers. You could set up CUPS, but again, unless you have a lot of Macs, not worth the trouble.

Just let them print direct. ' what else?' One thing is file and folder naming conventions. Mac OS allows use of characters in filenames that are illegal under Windows. Question marks, backslashes, stuff like that. This can cause issues for Windows-based backup software, or Windows users who work on the same files. An experienced Mac user familiar with Windows networks will know about this and won't cause problems, but someone who's never used a Mac in a corporate environment may need to be smacked around a bit.

Another thing is the whole iTunes/App store credit card nonsense which I personally hate, and with OS X 10.8 is pretty much rammed down your throat. There are ways to avoid this if it's a big deal. Also, when evaluating this, remember that there are additional costs associated with saying NO. The Mac user will be less efficient on a Windows machine. Their productivity WILL suffer.

This is a real cost to be considered. Political cost of fighting this - is this a hill worth dying for? Realistically, how likely is it that after fighting the battle, you end up having to implement the Macs anyway? If so, best cut your losses and get it over with early. My advice is to find out exactly what the user will be doing and why they need a Mac, then either fight it or give up depending on factor 2 above. Thanks for ALL the replies! Here are some 'answers' / comments to some of the posts.

my mac expertise is limited and i don't have a mac for testing or learn, so. the mac users are just 'normal' users (no special needs, design, etc.). They are just 'mac people' and they feel that they are more productive with a mac. as for my 'worry' re: VPNs.

It is just another VPN client to learn & support. thanks for the heads up on centrally managed print server (i.e. CUPS). It is yet another piece if IT infrastructure that needs to be setup / maintained / supported (and as some mentioned above, for a few macs probably not worth it). my whole '2 of everything' comment perhaps has more to do with supporting & maintaining (as opposed to purchasing). I think my main hesitation (besides costs cuz we're a non profit) is the extra demand on my already limited time to support a mixed environment. Thanks again! I'm not sure of your environment however you need to consider the back office as well.

Our environment makes big use of Microsoft Dynamics CRM, Microsoft Share Point server and Microsoft Exchange Server. We have many, many web applications that use.net framework and Silverlight. To fully use these systems you really need to use Internet Explorer. Safari and Chrome will work for 50% - 90% of the time but it depends on what you are doing.

Our largest 'Mac users' group are sales and executive. Sales needs to use almost all of the features of Dynamics CRM, which requires IE 9 to have all of the features of CRM.

This caused us to have to install vmware Fusion & Windows. You can see the price per Mac just shot way up! We have also had some odd Outlook 2011 issues on the Macs that are just not present on the PC. Things like calendar issues and connection issues. Since Outlook for Mac connects and communicates with Exchange via the EWS virtual directory and NOT RPC like Outlook for PC it's been hard to troubleshoot these calendar and connection issues. They are very random btw.

And we also have may legacy, custom webpages that require IE to run correctly. We are trying to upgrade these but it takes time and resources to re-write the code so that its 100% compatible with Safari, Chrome, Firefox & IE. So basically our entire back office is designed around Microsoft Technologies and Internet Explorer and until we upgrade or migrate to a solution that is more 'open' our Mac's require much more support from us. We spend a lot of time trying to turn a Mac into a PC to the point of, why bother?

I love a Mac as much as anyone else but if 90% or our internal systems require a PC to use and be productive why would I try to use a Mac? Yes, the cost of supporting our Mac's is more than our PC's. Boils down to what is the best tool for the job at hand. Biggest item?.You. will need a Mac machine for testing, troubleshooting, etc. Rather mandatory, and a deal-breaker if not available. Worse case, can install VMware Fusion on the incoming OS X machines ($45) drop Windows & what ever the usual setup is.

Pickle wrote: We've had difficulties using a Windows print server so we gave up and turned our Mac-mini into a Mac print server.kinda. Bill@iscvt wrote.thanks for the heads up on centrally managed print server (i.e. CUPS). It is yet another piece if IT infrastructure that needs to be setup / maintained / supported (and as some mentioned above, for a few macs probably not worth it). OS X Server is $49, and can run on almost anything relatively current. Typical MacMini is a good choice (it can have 2 x 2.5' HDDs and 16GB RAM). OS X Server can be handy for some management, but is not meant to be substitute for AD. Bill2718 wrote.

One thing is file and folder naming conventions. Mac OS allows use of characters in filenames that are illegal under Windows. Question marks, backslashes, stuff like that.

This can cause issues for Windows-based backup software, or Windows users who work on the same files. An experienced Mac user familiar with Windows networks will know about this and won't cause problems, but someone who's never used a Mac in a corporate environment may need to be smacked around a bit. Can be a pain point. Notably when a folder is so named, and its contents become inaccessible to Windows. Can't you install Windows on a MAC? I mean, without the MacOS?

That would be great. They are all happy getting a 'MAC' and when they boot for the first time. Love to see their faces:) But at least they would have the looks of a MAC (which IMHO is one of the main reasons lots of people buy a MAC, iPhone, iWhatever. The looks of it. And of course, looking cool with it) Don't shoot me if I'm wrong about installing Windows on a MAC. I would never spoil the MAC with a windows.

I once used a MAC for a project in school. I was glad when it was done (and that there was actually a fellow student with huge command line knowledge on our project). I don't know a lot about MAC's other than their design is awesome and users can't make them crash because users can't really. Change anything. It's all locked down. Which in turn is good if the user doesn't know what he's doing. Back on topic if they don't need them, don't buy the MAC's.

I'm in a roughly 50/50 PC/Mac environment (figures are more like 168/152), and if there's anything I learned from it, is that I.hate. Macs, without prejudice. Here's why:. Maintenance: Not sure if you noticed, but the newer iMacs are all, um, glued. Good luck repairing them. Extremely time-consuming compared to servicing AIO or set top PCs.

Even the slightly older iMacs, where you have to use suction cups to take it apart. I hope the aluminum iMacs fare better, but I have a huge graveyard of the older white plastic/acrylic iMacs. Some died from various forms of unexplained mysteries, but mostly hosed logic boards and video cards. I already have a few 7.1 aluminum iMacs randomly restarting and generally slowing to a crawl, even after OS rebuild and swapping out everything short of the logic board.

Oh, and if your hard disk gets hosed, you must get one from Apple, because they use proprietary SATA pinouts, and the hard disk thermometer is proprietary. Even if you do manage to shove a 3rd party disk in there, the fan will spin out of control, and you will have to install a fan controller software, essentially creating more maintenance. Cost: Macs are expensive slabs of aluminum on a butchered Unix platform with a pretty screen.

You'll also want to buy Apple Remote Desktop to get any levels of manageability out of them. Management: Depending on your use, all users must be admins to get anything done. The lot of Macs here are used by artists, and they have to install fonts often, so everyone is an admin. Not an option. Along with that, they can do whatever they want, potentially making your life a nightmare. There's no GP-like management, either. Console isn't very clever in sorting out error messages like the Event Viewer.

Updates can't be applied like Windows Update, and no local update server for storage and saving bandwidth. Can't add mapped drives (or SMB shares in this case) like AD GP, must be done manually. Password enforcement is also a torturous pain. Printers can be installed via Bonjour, and if the printers are HP, drivers can be automatically downloaded via Apple's repo, which is convenient.

However, that also means the driver have to be downloaded every time, and printers must be added manually, again, not automatically like one can do with AD GP. Stability: Our iMacs here are no slouch - i5's, 16GB RAM, and yet applications, ranging from Mail, to Illustrator, all crash and burn more often than BTCC championships. No amount of fixes stave these problems off very long. Whether it's caused by the (admin) user or otherwise is still debatable. Processes running on Macs also tend to be massive memory hogs compared to the same thing being run on a Windows platform, may be a 3rd party thing, but doesn't change reality.

By comparison, I had two PCs crash and burn, but that was a lemon with a bad motherboard, covered under warranty, and another because of power supply, both easily replaceable, mind you. Compatibility: Our ERP system is also strictly Windows-based. Mac users that require it had to log on to a Windows Terminal Server to get their fix. A lot of these users have no concept of 'logging off,' and even with the idle timeout set, sometimes they leave the ERP licenses locked in, causing licensing issues if you're short of it. If you have Exchange, avoid Macs at all costs. They will be your greatest nightmare by far. Apple's claim to Exchange compatibility is so laughable, it's a bad joke.

I've lost count on how often I had to clear cache and re-index, delete attachment files in local mail directory storage because it's conflicting, random unexplained crashes, unclear local 'On My Mac' storage and actual Exchange stores, local-only rule creation, and generic errors that don't explain why a message is larger than a quota set on the server, or when a mailbox is full, whereas Windows users see those things in plain English. Even Outlook 2011 for Mac doesn't completely work properly, including its own unexplained crashes and usability issues. Yes, it connects via EWS, but the difference is staggering. The new SMBx protocol in OSX is also massively broken.

Since 10.7, users can't search SMB-mapped network directories in Finder, and as of today it is still not fixed, with Apple generally ignoring the issue, as usual. See, in my environment, it's a necessary evil; all these artists go on and on about how they 'need a Mac' to get their work done, and frankly I'm not sure where that mentality came from. No matter how I see it, PC can do the same, only cheaper, but I digress. Making Macs work in any business environment is, in my experience, generally a walk on a thin wire. In short, if you don't have to get Macs, don't. They're good for ignorant, single users that like to look at pretty animations and ignore all the inherent problems. For IT admins though, the inherent problems may be all that you're looking at.

We used to support a couple Mac users in our Windows shop and it was a large drain on resources. Support calls took three times as long because neither me nor my assistant knew much about Macs and had to learn it as we went. They had a lot of 'glitchy' problems that kept coming back when you had thought you fixed them like Entourage losing it's settings or VMware Fusion no longer working. We let one of the Mac users go and decided to tell the other one we wouldn't support it anymore and if he wanted to use his laptop in-house we'd provide any technical details he might need, but he was responsible for figuring out where to put them and getting the thing to work. Three weeks later, we got him a dual-screen Windows 7 desktop.

Nobody 'needs' a Mac. I don't know of a single software package for OSX that doesn't have an equivalent, usually better Windows version.

June 02, 2013 by Empire Hey, In the PDF guide, when they want to configure the Mac for programming, they tell you to go the Terminal, go to the /dev directory, and located a file something along the lines of cu.PL23A, but when I tried that, I don't find any file that resembles that file name. All my components are wired correctly. What can I do to fix this? June 03, 2013 by Ralphxyz What version of OS X are you on? Chances are you have a newer version in which Apple changed the name of the USB ports.

Search the forum for Mac USB. I just and came up with one of my own post. Try /dev/cu.usbserial Of course I got this from another post. Apple once again has f.cked their legacy users so I can not update to the latest version of OS X on my Mac MiNi. Guess that settles ever buying a Apple product again, this is the second time they got me.

I wonder if I can install Linux on my Mac Mini that might be fun. I know I can do it on a virtual machine but I'd like to do as the default OS.

Ralph June 03, 2013 by Empire Ralph, I'm currently running Mac OS X 10.8.3 (Mountain Lion). Could it be that the driver I installed from the Nerdkits download page is outdated?

I'm only getting a cu.Bluetooth file. Could you (and would you mind) giving me some sort of link to possibly a new driver that I can installed? Thanks Ralph. Alexander June 03, 2013 by pcbolt Alexander - I don't own a Mac, but I remember seeing a thread that listed some of the downloads you might need.

I tracked it down. June 04, 2013 by Empire Pcbolt, Thanks for the link, would I have to uninstall the current driver I already installed or.?

June 04, 2013 by Ralphxyz It is always safe to uninstall a non working driver. You probably do not have to as the new driver points to a different USB designation. Ralph June 04, 2013 by Empire Ralph, Hope I'm not asking too many questions, but I downloaded the latest version of CrossPack for AVR at this link and I plugged the USB cable to my computer, made sure that the programming switch was switched on, and I checked to see if I could find any cu.usbserial was found, and I still couldn't find any file of that sort. Would you have any advice as to what to do from here?

A Support Environment For Machine

June 05, 2013 by labudde ralph In the PDF guide, when they want to configure the Mac for programming, they tell you to go the Terminal, go to the /dev directory, and located a file something along the lines of cu.PL23A, but when I tried that, I don't find any file that resembles that file name. In fact i can not see any files using 10.7.5 OSX on terminal Is command does not work for me please help June 05, 2013 by pcbolt Empire - Did you also install the newer? Seems there is also an instruction page with extra directions in the comment section. Like I said before I'm not a Mac guy so Ralph would know more than I. June 06, 2013 by Ralphxyz Well I have once again been screwed over by Apple so I cannot use the newest version of OS X so all I know is what has been posted here. Others have worked it out. Labudde, what are you doing?

A Support Environment For Machine Learning

In fact i can not see any files using 10.7.5 OSX on terminal Is command does not work for me Can you take a screenshot? Ralph Post a Reply Please to post a reply.