Just be aware that if you do this you'll have to manually clean up the AD metadata for references to the 'missing' SBS server. MS has a KB for what your want to do - sort of: http://support.microsoft.com/kb/555073
Before 'ripping out' the SBS server go through the same procedure you would for transferring the FSMO roles in a non-SBS environment and then demote the SBS server off the domain after you've checked that all the relevant AD replication has completed. Make sure the new 2003 DC is the FSMO role holder now and then make sure the AD metadata has no leftover references to the SBS server. I would also recommend the following article: http://www.msexchange.org/tutorials/Migrating-Small-Business-Server-2003-Exc hange-Standard-Part1.html As usual - make sure you have backups and a route to back out if the things go belly up on you. HTH Regards, Amer Karim -----Original Message----- From: Phil Brutsche [mailto:[EMAIL PROTECTED] Sent: May 8, 2008 12:41 PM To: NT System Admin Issues Subject: Re: Removing SBS2003. It goes something like that... except that the SBS2003 server won't let any other machine hold the FSMO roles. You need to "violently" rip SBS2003 out and tell the 2003 DC to seize the roles. The procedure would go something like this: 1) Bring up 2003 machine 2) Add 2003 machine to SBS2003 domain as an additional domain controller 3) Let the DCs sync 4) Pull the plug on the SBS2003 server 5) Tell the 2003 DC to seize the roles Joe Fox wrote: > I guess the subject says it all. I have a SBS2003 server on my network, > and want to replace it with a 2003 Server. Is it as simple as bringing > the new 2003 box online, promoting it to domain controller, and then > transferring the FSMO roles to it from SBS? -- Phil Brutsche [EMAIL PROTECTED] ~ Upgrade to Next Generation Antispam/Antivirus with Ninja! ~ ~ <http://www.sunbelt-software.com/SunbeltMessagingNinja.cfm> ~ ~ Upgrade to Next Generation Antispam/Antivirus with Ninja! ~ ~ <http://www.sunbelt-software.com/SunbeltMessagingNinja.cfm> ~
