Standalone promoted to DC 1

[manerch]

I haven't seen this particular situation described anywhere.

I have a W2K Server that is a standalone server, in fact it's the only server in the small network. I've been considering promoting it to a DC, but I'm not really confident about any consequences of this action. If I do a DCPROMO on it, how hard will it be to configure my 5 XP workstations to be able to connect to it? What changes will I need to make? I have my router being the DHCP server, will this be a problems as far as having to make any IP changes? Finally, if the move goes horribly wrong, how hard will it be to reverse everything and continue the way I was before? I have good backups. TIA

 

[rphips]

its a simple task

Just ad the AD
Add all users
Go to each workstation and add them to the domain

You should ensure that your server is running a static IP address

You do not have to install DHCP on the server but if you want to you will have to disable it on your router.

DNS will be installed with AD

If a problem does occur just demote the server (remove AD dcpromo) and start all over



bob

Jones' Law
The man who can smile when things go wrong has thought of someone he can blame it on.

 

[manerch]

rphips,
Thanks for the speedy reply and good info. Currently, I have the server obtaining an IP automatically from the Linksys router. If I switch it to static, will I have to change the TCP/IP setting for either the clients or the router? I think the clients obtain DHCP and DNS automatically; that's the way it is setup for the server. I think that this may stem from when the system was originally setup. I thought that everything (DHCP, IPs, internet access...) would flow down from the router. I might be wrong though.

 

[rphips]

Go to your futer server and do the following

1. Go to run - type cmd
2. in the command box type ipconfig /all (this will list out all your ip settings Your IP address, subnet, DNS settings, and gateway.

4. Make note of what the settings are.
5. then in network nieghborhood properties but the setting into the proper places
6. reboot and make sure you can connect to the internet and other computers in you workgroup.

7. your ready to go



bob

Jones' Law
The man who can smile when things go wrong has thought of someone he can blame it on.

 

[manerch]

If I understand you correctly, I would enter the info that I got from an ipconfig /all into the TCP/IP tab that currently has me obtaining an IP automatically (I would deselect that option and instead choose 'Use the Following IP'). Is this done with the intention of making the server the DHCP server and relieving the router of these duties or is this just the needed steps to make the server's IP static? I think it's more for the latter reason than the former, but I'm not really sure. Is there any real advantage of having one be the DHCP server over the other? I apologize for all of the questions, and you can feel free to preface any response with, "Geez, you're dumb!" Thanks a lot.

 

[rphips]

Geez
There are no stupid questions only those that are not asked.

It just to make the server static - if you want to DHCP off the server instead of the router you will have to install DHCP and disable DHCP on the router.

The only advantage to having the router do it is it takes the load off the server

The only other thing is how heavey you use the internet -

If the router goes down there is no internet access or local network access if the router is doing DHCP (depending on when they leased thier IP address).

If the server is doing DHCP and goes down there is still internet access depending on when they leased thier IP address).


bob

Jones' Law
The man who can smile when things go wrong has thought of someone he can blame it on.

 

[manerch]

Bob,
You've been a veritable font of wisdom. I can't thank you enough. You've given me enough information to let me feel like I could safely promote this server without having a meltdown. Now I'm wondering, "should I?" What exactly would be the benefits of using AD over just leaving my server as a standalone? I have a small, single site network w/ 1 W2K Server, 5 XP clients, and no exchange server. Money, as always, is an issue. So I'm trying to implement only cost effective methods.

 

[rphips]

That small of a network I would leave it as a Point to Point, No need for a AD server.

Growth of the company or if your company wants thier own email server might push you to creating the AD otherwise you should just stay cost wise and efficiency wise.

Growth When you start getting close to 10 users I would switch to AD (more efficient, and easier to mantain (central point of failure next multi-points of failure))

bob

Jones' Law
The man who can smile when things go wrong has thought of someone he can blame it on.

 

[manerch]

Bob,
Again, I want to thank you for taking the time to answer my questions. You've been great!!!

 

[rphips]

Your welcome anytime.


have a nice day



bob

Jones' Law
The man who can smile when things go wrong has thought of someone he can blame it on.