Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations wOOdy-Soft on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

SBS 2003 Installation question

Status
Not open for further replies.

tahoe2

IS-IT--Management
Dec 30, 2002
495
US
Hi. We're migrating from NT to SBS2003.
Right now, our setup is as follows:
DSL into Modem;
Modem into Linux 2.2 Firewall (gateway);
Firewall into network;
PDC runs Proxy, WINS, DHCP.

Here's what I want to do:
DSL into new SBS 2003 DC with ISA server as firewall.
DC will run DHCP.

Here's what I know I need to do for installation:
Disable DHCP on the old PDC;
Disconnect the DSL modem from the internet;
Connect the new server to the network and start installation.

During installation, do I use the IP of the firewall for the new DC, since I'll be removing it from the domain and I need a gateway?

Thanks!

Corie
 
Don't forget that an SBS server must be the primary and only DC on the network. If you are attempting to add it to a network with other NT/2k/2k3 DCs it will not work.
 
Yup, I got that part, the old server will be retired. I just need to know what IP to give it because I'll be removing both the firewall and the old PDC.
Also, should I demote the old BDC before I migrate?

Thanks!
 
The IP you choose won't matter at this point. You will need to configure the Internet NIC with your static IP provided by your ISP. On the LAN side you could go with either 10.0.0.2 or 192.168.0.2 or ANY IP of your choosing. Your DHCP scope will be determined by what you choose. If you have any networked printers that are configred with static IP addresses then you may want to stick with the same subnet so you don't have to change the printers configuration. You would simply want to add those IP addresses and MAC Addresses as reservatiosn in DHCP or exclude those IPs.

Regarding your BDC, are you planning to retire it as well? You will nto be able to join it to the domain without a rebuild since NT4 can't be made just a member server without a rebuild. You can not move a BDC or PDC into an SBS network as a DC.

You CAN have a Windows 2000 or Windows 2003 server as a second DC in an SBS domain but it really won't do you much good for disaster recovery. The SBS box has to hold the FSMO roles. A second DC for an SBS network works well if you have a small remote location and wnat your users to get authenticated locally.

I hope you find this post helpful.

Regards,

Mark
 
Excellent, Thanks!
We will not be retiring the BDC as it runs our payroll software, but you say I cannot add it to the domain, even as a member server? I could upgrade it to W2K server...

Wow, these upgrades never stick to the plan, do they?

I was just planning on going with the one DC.
While we do have a remote office, it is small (5 users) and I don't want to have to maintain anything from a distance. I mean, I can't even get those girls to stop plugging their curling irons into the router power strip!

And since there's only 5, static assignment isn't a big deal.

Thanks again!

Corie
 
For your BDC, yes, you could technically upgrade it to Win2K or Win2K3 but it will be a real pain. You can't just upgrade a BDC, it would need to be promoted to a PDC. You would then have to do the upgrade and go through an entire AD setup. At which point you could then run DCPROMO to remove AD and make it a standalone server. You could then join that server to the new SBS domain.

Easier and faster to just format and install a fresh OS. Then restore data from tape.

I hope you find this post helpful.

Regards,

Mark
 
I read that member servers running NT 4.0 could be migrated over, so could I demote the BDC to member server?
I have and old file server that also runs NT and I planned on retiring that as well. I could promote that to BDC for this last week...

Thanks!
 
The problem si that NT4 requires a reload to remove BDC status. You can't just demote it like you can with Win2K.

NT4 can be a member server without problem. It is the domain controllers you will have trouble with.

I hope you find this post helpful.

Regards,

Mark
 
nuts. I hadn't planned on that, and the BDC runs our payroll software...

Thanks for letting me know now, instead of having to learn it the hard way next week!

Thanks for the help,
Corie
 
I found this on Microsoft's website. Will this also apply to SBS2003, or am I still dreaming?
*********
To add a Windows NT 4.0-based BDC to a domain with a Windows 2000 client as the PDC, use the Srvmgr tool that is included with Windows 2000. You should run this version of the tool only on the Windows 2000 client to pre-create the computer account for the BDC. After you create the account, the BDC installation should finish successfully.

*************

Also, what about the utility UPROMOTE? Did you ever use that?

Thanks!
Corie
 
You are not reading all of it. That is for adding a NEW NT4 BDC to the Domain.

I hope you find this post helpful.

Regards,

Mark
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top