So i'm going to move our SBS2003 off the domain and replace it with a WIndows2003 server. I already have a few regular Windows2003 servers running in the domain. An additional DNS server an additional domain controller. I just want to kill the SBS2003 server and be done with it.
I don't care about exchange i'll be setting that up from scratch on it's own server. I know all i have to do is seize the FSMO roles and remove the SBS2003 from the domain. All i want is active directory to stay in once piece so i can continue with my domain.local.
So it was suggested that I add the new server through the whole SBS2003 wizard process. I have a total of 15 or 20 (need to check) licenses for windows 2003 and only 5 valid licenses for SBS2003. How is this going to effect things? Can i just add the new server to the domain without going through the http://sbsserver/computerconnect
process? Seize the roles and be done with it?
Exhange running on my SBS2003 server is doing a few things. It's doing some shared contacts (no big deal getting them backed up) and handling our voicemail to outlook. Which I can turn off for a week and people get their voicemails on the phone (old school).
Actual emails are handled by an outside source. So the question here is.. Should I remove everyone's exchange mailbox from the sbs2003 before I do the seizing of the FSMO roles? Obviously i need to go to each outlook client and delete the Exchange account.
Things like DHCP are running on another server. Nobody is jazzed about the shared portal thing of SBS2003. I have ISA 2004 running on it's own (soon to be isa 2006).
So really the SBS2003 server is a COW sitting smack dab in the middle of my network and it needs to go away.
Thanks for any help/suggestions