So you're saying when a new hire comes in with the preference of a Mac, your first move is to put them on a long ago EOL operating system which had no security to begin with, to which they are completely unfamiliar with, and wait to see what happens after 30 days? And you have a person who spends 10 hours a week fixing alleged problems with a single Mac (you said user, not users) being on the network? I thought you were kidding in your first email but here is the second. You're doing something wrong guy.
Putting them on an XP machine would kill you? Or possibly just spending a couple days learning something new is out of the question? And don't tell me you don't have the time if you're honest about rebuilding computers with Win9x on them. If you have time to do that you have time to learn something new. -- Mike Gill From: Jon Harris [mailto:[EMAIL PROTECTED] Sent: Friday, May 23, 2008 9:39 AM To: NT System Admin Issues Subject: Re: Mac on 2003 Domain I don't want my Mac user RDPing into anything. He is a big enough issue I don't need servers crashing because of his need to use a Mac. We have one person on staff that spends about 25% of his time just fixing the files that "work just great on the Mac" but will not work right on a Windows system. My boss is fully aware of this and just smiles when the Mac user makes wild claims and moans about no one supporting Macs. Like I said put them on a Windows 98 system and make them prove they can run it before spending the money on a Mac. Ours could not run the Windows 98 system for more than 30 days before we had to rebuild it. ~ Upgrade to Next Generation Antispam/Antivirus with Ninja! ~ ~ <http://www.sunbelt-software.com/SunbeltMessagingNinja.cfm> ~
