Migrating Windows 2000 Clients

I recently moved two of my shops from NT 4.0 to Windows 2000. It was time. NT 4.0 isn't supported anymore (sobs over the loss of a good friend) and they needed new servers.

Let me tell you, if I knew then what I know now, I wouldn't have done it.

What a royal pain in the @)#*Q#2! What were these guys thinking??

Why all the expletives? When they developed Win2000 Professional (a very big improvement over NT Workstation), they created all these multiple security logings and profiles. Every user on the W2K box had a different profile.

Not so bad. But what they also did was create a brand new profile should you change the domain. This means all the programs that were customized or loaded into your particular profile just went bye-bye when you moved from the NT 4.0 domain to the new W2K Server.We're talking everything, from desktop icons, and menu choices to "My Documents."

Now for one or two computers, it's time consuming but doable, but for large installs, Oh My! What a nightmare! Now someone out there will tell me everything (profile) should sit on the server.

Actually, one of my guys likes setting up his servers this way. Great idea, but it really is slow. It bogs down the network. It increases your chances of being totally down, should your server be down.

Why or why doesn't Microsoft do marketing testing with real people??