There is one major reason to shift
commentards aside, I've seen a few genuinely insightful views posted here. I've also seen a few comments that unwittingly gave away just how little they understand of how windows works. Eg. Remote Desktop is to take control. Remote assistance allows interactive guidance.
One theme that I've seen running through the comments is server-side management.
We currently use server2008 and SCCM to manage our multi-site system. It took me a while to get it working, but now I can schedule a complete OS reinstall on the other side of the world.
They buy a new machine, email me the mac address, and plug it in. We already have a deal with our suppliers so they configure the BIOS correctly.
On my scheduled command, the machine powers up, partitions and formats its' drive, installs windows, its' relevent drivers, any updates and a full suite of software, entirely customised for its' role. Then group policy takes care of configuring every last detail of the OS configuration from dynamic proxy, desktop theme, printer assignment, drive mappings office macro security...
The only thing the user has to do is log in, usually with the profile I also scheduled to migrate from their old machine.
This all works because we are using Vista business. What twisted my arm? The kernel of Vista has a true Hardware abstraction layer. Prior to vista we tended to build OS images catered for hardware profiles because although you can deploy drivers for XP, there are some serious limitations, and this generated a substantial amount of work. Even the BIOS is managed through SCCM thanks to intels AMT and Vpro tech.
Thankfully, all our 'problem' software was developed in-house, and it didn't take much cajoling to get our developers to switch to .net, becuase they all love the IDE.
I'm currently fine-tuning win7. The rollout will be a doddle. Yes, there some elements of it that can be a pain to configure, but that's the whole point of group policy. You only need to get the configuration profile right once (and you don't do it through the confusing interface on the desktop itself - if you're doing that you've failed to grasp the whole concept of server-client relationship)
I've worked with many seasoned unix/linux vets, and I've heard all the arguments before. Yes, unix/linux usually has a comparable app or feature to compete with MOST of these management systems, and usually that app will have MOST of the elements, but invariably they've not been as replete or well intergrated as the MS counterparts.
As for cost? We're an academic institute, so we're laughing all the way to the bank (if we weren't it would be a serious consideration though)
I'm not a complete MS lacky - our primary file server cluster is Solaris, - it simply has no downtime, and we only switched our webservers to IIS for integration with our .net apps.
I'm certainly not going to stand at the alter and preach the virtues of exchange either, as my experiences with it have not always been shiny - but we are migrating to it, because our current IMAP server doesn't do deduplication, and for obvious reasons there isn't anything else on the market that ties into active directory as seemlessly.
So, when it comes to the killer app that makes us switch? As per usual it has nothing to do with the plebs sat in front of the desktop, it's about genuine improvement of the overall system, and that is something that vista and win7 do offer.
The only sticking point is application compatibility, and I have deep sympathy for those sysadmins that have no control over those VB6/COBOL/PASCAL peices of legacy crap in their organisation.
wow, this turned into a ramble, but I hopefully someone will find insight in my meandering experiences