moving to new server
Hi,
I have an old windos 200 sbs that nees replaicing. Im going to install a new Win 2003 SBS. My client pc's will not be changing so what i was wondering is, is there an easy way to get the pc's off the old server/domain and onto the new easily. I would like to keep their current profiles and individual settings on there pc's.
Any ideas
Cheers
I have an old windos 200 sbs that nees replaicing. Im going to install a new Win 2003 SBS. My client pc's will not be changing so what i was wondering is, is there an easy way to get the pc's off the old server/domain and onto the new easily. I would like to keep their current profiles and individual settings on there pc's.
Any ideas
Cheers
ASKER
what if im not happy with the current setup?
What parts of it?
As long as there aren't any serious issues with corruption or anomalies in AD, you should then be able to selectively move the bits that you want and elave the bits that you don't. AD is generally migrated "as a whole" otherwise weird things start happening.
If they're a small organisation then you may want to start from scratch and "keep it clean". However, if you want to minimise migration time then you may not want to do this - having said that, I should say that migrating a corrupt AD is probably not the best of ideas :-), having spent 15 man-days trying to migrate an SBS once!!! Fascinating as it would have been to solve the problem (we even had an SBS-MVP working on it - probably the one man most suited to the job) we ended up starting from scratch just for business reasons.
So, if it's a small environment, keep it clean and start from scratch. Migrating an older environment may be quicker now but if it's creaky then it may cost a lot more time later on.
If it's clean & large now, then just migrate. Remember, I'm essentially referring to AD, the rest of the configuration is a lot easier to pick and choose and configure from scratch.
As long as there aren't any serious issues with corruption or anomalies in AD, you should then be able to selectively move the bits that you want and elave the bits that you don't. AD is generally migrated "as a whole" otherwise weird things start happening.
If they're a small organisation then you may want to start from scratch and "keep it clean". However, if you want to minimise migration time then you may not want to do this - having said that, I should say that migrating a corrupt AD is probably not the best of ideas :-), having spent 15 man-days trying to migrate an SBS once!!! Fascinating as it would have been to solve the problem (we even had an SBS-MVP working on it - probably the one man most suited to the job) we ended up starting from scratch just for business reasons.
So, if it's a small environment, keep it clean and start from scratch. Migrating an older environment may be quicker now but if it's creaky then it may cost a lot more time later on.
If it's clean & large now, then just migrate. Remember, I'm essentially referring to AD, the rest of the configuration is a lot easier to pick and choose and configure from scratch.
Didn't know it's not to be used... why is it there?
Its a feature that was built and has yet to be properly implemented...at the moment all it does is cause confusion :)
Gotcha...
I would suggest you look into the www.sbsmigration.com solution. It's about $200 I believe, so it's not free... but in general, it's highly recommended and I can't recall a single instance where someone said it didn't work well if not fantastic.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Have a look at this document with detailed info on the migrate process:
http://go.microsoft.com/fwlink/?LinkId=16414