Connecting a second SBS 2003 Server to an existing SBS 2003 Server

First, you CANNOT have two SBS servers on the same network.  SBS has a requirement that it MUST hold the 5 Flexible Single Master Object (FSMO) roles - since you can only have one master for each role and SBS MUST be it, how can you have a second SBS server ALSO be the master?  You can't.

By creating a second domain, you are forcing yourself into a lengthy migration.  If it's not too late for you, you would be better off spending the $250 or so on the www.swingmigration.com kit, which contains a great deal of documentation and scripts to allow you to quickly migrate from one server to another.  You can do it without it, but it will almost certainly take much longer and be more difficult for you.  

If you want the old server to be a second DC (or server in general), you will need to purchase a copy of Windows Server 2003 STANDARD edition (not SBS) and install that. SBS domains CAN have additional servers - but only ONE SBS server.

Ok, and thanks for the quick responses.  Now the question is, if I transfer all the files and licenses over to the NEW server, can I just unplug the old server and have the new server take over?  Or how does this work please?

No you most certainly cannot.

The new server will be on a different domain, if you try to make it the same domain, you will be rebuilding it from the floor up, this means that you will have to remove the old server from the network first, then rebuild the domain (users and all) on the new server.  After this, you will then need to readd all of the computers in your domain to the new server.

-saige-

As for the swing migration, yes it works, it from the standpoint of migrations, it is the one that uses the least administrative effort.

-saige-

No.  Windows links everything by Security IDs (SIDs) - these are UNIQUELY generated at installation time (install of the server, workstation, etc).  The old server will have a different SID from the new server and you will have to rejoin all computers to the new domain and recreate all the user accounts.  Then you'll have to reset ALL permissions, everyone will have new profiles (because the old ones will belong to users with different SIDs.  There are ways around everything, but if you want to do this right, you should get the SwingMigration kit OR hire a consultant.  (It's great you want to learn this - and I encourage you to do so - but your company is making a mistake if they rely on their computers for anything and have asked you to do it with no experience in the area).

Leew is correct that you will have redo everything.
There was already a good source of info on this that you can veiw here
http://www.experts-exchange.com/OS/Microsoft_Operating_Systems/Server/SBS_Small_Business_Server/Q_22008948.html

OK, I have already created it on a different domain and a different server name.  And I am installing all the information, Users, computers, etc by hand.  I do understand that I have to reinstall permissions and that each client  computer has to be set up on the new server.

What I am asking is whether I need to take the Old server offline prior to setting up each individual client computer.  The reason I'm asking this is because they've already stated that they don't want to spend the 650 to 1000 to buy Server 2003, so my option is to eliminate the old server completely.  

I would suggest that we use swing migrator but one of the reasons we are having the issues with the old server is that an old tech which had knowledge in this area, decided to leave on bad terms and really screwed up the old one on the way out.  It's still working, but the decision was made that since the hardware was over 7 years old, it was time to replace it.

I do agree that at times like this it is always great to hire a consultant, but the server is part of a church with very limited funds.  I have run a small computer repair business for about 11 years now but have never had to deal with SBS until now.

In short, any help you could give would be very appreciated.

Gregg

If this is a church with a 501(c)(3) status, then they should be purchasing their software from TechSoup - That server licenses should cost them, at most $50.  Further, TechSoup has listings of consultants who sell services at a discount to non-profits.

If you are doing this pro-bono, then YOU may want to buy the swing kit - because the time you spend on this could be spent making more money with your own business.  And if you're not, then that kit should save them money because you'll be able to do it faster.

You do not need to take the old server off line, but you do need to keep the server names different.  (otherwise, you would have to take it off line).

To answer your first question, I do not know their status.  However, I will be asking them on Monday due to your response.  As to your second statement, yes I am doing this pro-bono since they are really great people and I'm just trying to help them out.  I will discuss getting the swing kit with them on monday as well.  

The current problem that I was left with when I left tonight was the fact that I couldn't get the individual PC's to log into the new server, even though the new server is set up with a different server name and domain name.  Any ideas?

And as always, thanks for the help.

Did you join the workstations to the domain?  Is the DNS setup properly on the new server and the workstations?  Which SBS server is handing out DHCP addresses?  (SBS shuts down DHCP if it detects another, so if either SBS server detected the other SBS server, then one may not be handing out the right IPs.  How did you setup the SBS servers?  (SBS is, in my experience, ROCK SOLID - *IF* - it's setup correctly and managed through the wizards.  If you think you know better and manage it like another server, you WILL cause problems (and I don't use absolute words like WILL often).  I know this from experience - I spend 5 years managing Windows servers and I ROYALLY messed up my first SBS install because I thought I knew better.

ok I have been trying to join the workstations to the domain.  That is the problem.  Every time I try, it rejects it.  I'm guessing that the DHCP on the new server is shut down due to the auto shutdown that SBS does.  

I have used nothing but wizards to set up the second server.  I didn't set up the original.

Is there a way to shut down the DHCP on the old SBS server and then activate it on the new server?

Will do, on tuesday when I return to it.

Gregg

If I was to shut of the Old server completely, and then turn on the new server, would that work just as well as turning off the DHCP settings on the old server?  If not, could you please tell me precisely what I'm supposed to do to shut down the DHCP setting on the old server?

GRegg