> then do the company-wide deployment over a weekend after you know everything works. Even if there weren't serious network infrastructure issues involved, I w

> then do the company-wide deployment over a weekend after you know everything works. Even if there weren't serious network infrastructure issues involved, I wouldn't dare do an OS rollout like this. This isn't a new version of some webapp you can just upload to a server and be done with. You're talking about fundamentally altering the operation of thousands of desktops and laptops around the world being put to diverse use by people who are very probably not technically minded. And it would be impractical at best to upgrade all of that over the network on a weekend. Every piece of hardware would have to be turned on and connected to a high-speed link with appropriate netboot infrastructure. That's not going to happen. QA can't catch everything, so rolling it out all at once means the entire company goes apeshit on IT all at once. Watch the senior IT people walk out the door because they don't have to put up with the abuse and can find a new job. Watch the young and inexperienced IT people have nervous breakdowns and take months to address all the problems, possibly costing the company millions in the process...