install sbs 2003 in existing 2003 domain

[MCSLOY]

Hi

I have a customer who wishes to use sbs 2003 on her network.The network currently consists of 2 2003 standard servers,both of which are dc`s.I have the following plan:

1)install sbs on a new server and recreate users/computer accounts.
2)demote both 2003 standard dc`s to workgroup
3)migrate profiles from domain to local using profwiz.
4)use connect to server wizard
5)when everything is running smoothly on sbs dc,join the 2 2003 standard server`s to the sbs domain and promote them to dc.

If anyone has experienced this scenario before or has any ideas/comments/pointers, please let me know!

 

[ShackDaddy]

There's a better way.

You can stop the SBS install after the OS is installed and before the SBS bits are deployed. Join the existing domain then, make the SBS box a DC and bring the FSMO roles over to it. Then continue with the SBS setup. Later on you can demote one or both of the other servers, but everyone will stay in the same domain and there will be no need to migrate users or resources to a new AD.

Look for Microsoft's instructions for doing a "swing" migration for details on when to stop the SBS setup and how to migrate those roles, or you can spend $200 for the "Swing Kit" set of docs that sbsmigration.com provides.

Dave Shackelford
Shackelford Consulting

 

[MCSLOY]

Hi Dave

Many thanks for your swift reply. I have already tried your suggestion on a previous job and i found that user/computer accounts were not moved to the correct ou on the sbs server and i have been informed that for all the functions of sbs to work properly,each machine must be unjoined/rejoined to the sbs domain and user accounts must be moved as well.

cheers

Martin

 

[ShackDaddy]

Ah... Well, you could manually create the required OU's, but I understand if you want to get maximum benefit from a fresh SBS build. Probably a wise idea.

I would recommend doing steps 3 and 4 before step 2.

I think I would recommend removing each workstation from the existing domain to a workgroup and then rejoining your new SBS domain. Leave the old domain online until the last minute so that you don't have any problem conducting operations there, since removing that AD will wipe out all ability to authenticate against those resources except against the local account. Too many variables there. Then when all the users are on the new server, go ahead and demote them, reboot them, point their DNS at the new server and join the SBS domain...

Dave Shackelford
Shackelford Consulting

 

[MCSLOY]

Many thanks for all of your tips Dave.Just 1 more thing that has got me thinking....

On 1 of the servers, there is a couple of accountancy programmes and i was wondering, if i demote this server to workgroup and afterwards join it to the new domain, should i expect any problems in regard to accessing these programmes? I know that i might have to alter something on the client side programme, but other than that,anything else?

Cheers

Martin

 

[ShackDaddy]

It depends on whether the programs use a domain user account or accounts to handle permissions, or whether the program has its own internal user accounts. If the former is true and you blow away the AD, you could have problems.

I'd make a good backup of the program data and then be willing to reinstall after the domain migration if you had to.

Dave Shackelford
Shackelford Consulting

 

[MCSLOY]

Cheers Dave. I had a feeling that might be the case.will soon find out!