Comment Re:Always wondered About That... (Score 1) 805
The only time that the Windows Update process really was crappy was right at the beginning of the XP Pro deployment. You had thousands of newly installed bleeding edge systems all trying to bang on the Windows Update server at the same time. For about 6 weeks it was chaos. One of the first patches down the pipe was a fix to spread out the updating. They also installed more update servers, or at least it seemed like it. Running sniffers during update cycles showed a broader spread of ip addresses that later resolved to WU possibly related servers.
I run a number of systems from NT 4.0 thru XP Pro and Embedded. The only ones that get Updated are the Win2K and XP Pro boxes. Everything else gets done manually. WU has saved me time but I also have to keep backups on those boxes more frequent. WIN2K Server SP3 and SQL2K SP2/3 are not really compatible and they have to be sequenced properly, what a headache. Really think lomg and hard before letting WU run automatically or "under review" on a SQL2K box after installing Win2K SP3. I had a development system for WinXPE die after updating to SP3 on the Win2K Server.
I run a number of systems from NT 4.0 thru XP Pro and Embedded. The only ones that get Updated are the Win2K and XP Pro boxes. Everything else gets done manually. WU has saved me time but I also have to keep backups on those boxes more frequent. WIN2K Server SP3 and SQL2K SP2/3 are not really compatible and they have to be sequenced properly, what a headache. Really think lomg and hard before letting WU run automatically or "under review" on a SQL2K box after installing Win2K SP3. I had a development system for WinXPE die after updating to SP3 on the Win2K Server.
