Showing posts with label DHCP. Show all posts
Showing posts with label DHCP. Show all posts

Monday, June 9, 2008

How to replace single domain controller in domain with a single domain controller?

How to replace single domain controller in domain with a single domain controller?

 

A

 
The following article describe a guidelines to replace exiting Windows 2003
Domain Controller with a new server.
 
The article assume the following pre-requirement settings.
 
1. There no Exchange/SQL server etc. on the current Domain Controller.
 
2. There only one domain, and there only one domain controller function as:
 
      DHCP/WINS/DNS/File Server/Print Server.
 
3. The source server using regular (No SBS) Windows 2003 Standard or higher.
 
 
The following steps need to be taken to replace the exiting Domain Controller.
 
 
1. Install the Windows 2003 Standard or higher on a new server.
 
     Tip: You will need to setup the current Domain Controller as DNS server.
 
2. Promote the new server to become Domain Controller (in the same domain).
 
Step-by-Step Guide to Setting Up Additional Domain Controllers
 
http://www.microsoft.com/technet/prodtechnol/windowsserver2003/technologies/directory/activedirectory/stepbystep/addomcon.mspx
 
3. Promote the new Domain Controller to be "Global Catalog" and reboot the server.
 
Enable or disable a global catalog
 
http://www.microsoft.com/technet/prodtechnol/windowsserver2003/library/ServerHelp/7b1c3e1c-ef32-4b8e-b4c4-e73910575f61.mspx
 
4. Install DNS server on the new Domain Controller.
 
How To Integrate Windows Server 2003 DNS with an Existing DNS Infrastructure in Windows Server 2003
 
http://support.microsoft.com/kb/323417

How To Install and Configure DNS Server in Windows Server 2003

http://support.microsoft.com/default.aspx?scid=kb;en-us;814591
 
5. Set the local IP of the new Domain Controller as DNS server.
 
6. Option - Install WINS service on the new Domain Controller and change
 
       the Domain Controller IP settings to point on the local IP as WINS server IP.
 
Tip: You can migrate the current WINS database to the new server.
 
How to migrate a WINS Database from Windows 2000-based WINS server to a Windows 2003-based WINS server
 
http://support.microsoft.com/default.aspx?scid=kb;en-us;875419
 
7. Move FSMO rules to the new Domain Controller.
 
How to view and transfer FSMO roles in the graphical user interface
 
http://support.microsoft.com/default.aspx?scid=kb;en-us;255690
 
8. Demote the original Domain Controller from using as "Global Catalog" and reboot the server.
 
Enable or disable a global catalog
 
http://www.microsoft.com/technet/prodtechnol/windowsserver2003/library/ServerHelp/7b1c3e1c-ef32-4b8e-b4c4-e73910575f61.mspx
 
9. Demote the original Domain Controller from using as "Domain Controller".
 
10. Migrate printer settings from the old server to the new one by using "Windows Print Migrator 3.1" tool.
 
Microsoft Windows Server 2003 Print Migrator 3.1
 
http://www.microsoft.com/WindowsServer2003/techinfo/overview/printmigrator3.1.mspx
 
11. Migrate File Server settings from the old server to the new one by using "Microsoft File Server Migration Toolkit".
 
Microsoft File Server Migration Toolkit
 
http://www.microsoft.com/windowsserver2003/upgrading/nt4/tooldocs/msfsc.mspx
 
12. Install DHCP server on the Domain Controller and migrate the DHCP settings from the old server.
 
How to move a DHCP database from a computer that is running Windows NT Server 4.0, Windows 2000, or Windows Server 2003 to a computer that is running Windows Server 2003
 
http://support.microsoft.com/default.aspx?scid=kb;en-us;325473
 
 
Tip: Don’t forget to set the new Domain Controller as DNS & WINS (Optionally) for the DHCP scope/s.
 
13. Edit users profiles and/or user logon scripts to point to the new Domain Controller as File Server and
       Printer server.
 
14. Uninstall unnecessary services from the old Domain Controller.
 
15. Install third party tools on the new Domain Controller (Backup Software, Antivirus etc.)
 
16. Re-register users computers in the new DHCP by using ipconfig /release and ipconfig /renew.
 
 

 

80/20 rule fault tolerance dhcp

http://www.networkworld.com/community/node/28080

Monday, May 12, 2008

DHCP

 

 

How To Install and Configure a DHCP Server in a Workgroup in Windows Server 2003

View products that this article applies to.

Article ID

:

323416

Last Review

:

December 3, 2007

Revision

:

7.5

This article was previously published under Q323416

On This Page

http://support.microsoft.com/library/images/support/kbgraphics/public/en-us/downarrow.gifSUMMARY

http://support.microsoft.com/library/images/support/kbgraphics/public/en-us/downarrow.gifHow to Install the DHCP Service

http://support.microsoft.com/library/images/support/kbgraphics/public/en-us/downarrow.gifHow to Install the DHCP Service on an Existing Server

http://support.microsoft.com/library/images/support/kbgraphics/public/en-us/downarrow.gifHow to Configure the DHCP Service

http://support.microsoft.com/library/images/support/kbgraphics/public/en-us/downarrow.gifHow to Create a New Scope

http://support.microsoft.com/library/images/support/kbgraphics/public/en-us/downarrow.gifTroubleshooting

http://support.microsoft.com/library/images/support/kbgraphics/public/en-us/downarrow.gifClients Cannot Obtain an IP Address

http://support.microsoft.com/library/images/support/kbgraphics/public/en-us/downarrow.gifThe DHCP Server Is Unavailable

http://support.microsoft.com/library/images/support/kbgraphics/public/en-us/downarrow.gifREFERENCES

SUMMARY

This step-by-step article describes how to configure a new Windows Server 2003-based Dynamic Host Configuration Protocol (DHCP) server on a stand-alone server to provide centralized management of IP addresses and other TCP/IP configuration settings for the client computers on a network.

http://support.microsoft.com/library/images/support/kbgraphics/public/en-us/uparrow.gifBack to the top

How to Install the DHCP Service

Before you can configure the DHCP service, you must install it on the server. DHCP is not installed by default during a typical installation of Windows Standard Server 2003 or Windows Enterprise Server 2003. You can install DHCP either during the initial installation of Windows Server 2003 or after the initial installation is completed.


How to Install the DHCP Service on an Existing Server

1.

Click Start, point to Control Panel, and then click Add or Remove Programs.

2.

In the Add or Remove Programs dialog box, click Add/Remove Windows Components.

3.

In the Windows Components Wizard, click Networking Services in the Components list, and then click Details.

4.

In the Networking Services dialog box, click to select the Dynamic Host Configuration Protocol (DHCP) check box, and then click OK.

5.

In the Windows Components Wizard, click Next to start Setup. Insert the Windows Server 2003 CD-ROM into the computer's CD-ROM or DVD-ROM drive if you are prompted to do so. Setup copies the DHCP server and tool files to your computer.

6.

When Setup is completed, click Finish.

http://support.microsoft.com/library/images/support/kbgraphics/public/en-us/uparrow.gifBack to the top

How to Configure the DHCP Service

After you have installed the DHCP service and started it, you must create a scope, which is a range of valid IP addresses that are available for lease to the DHCP client computers on the network. Microsoft recommends that each DHCP server in your environment have at least one scope that does not overlap with any other DHCP server scope in your environment. In Windows Server 2003, DHCP servers in an Active Directory-based domain must be authorized to prevent rogue DHCP servers from coming online. Any Windows Server 2003 DHCP Server that determines itself to be unauthorized will not manage clients.


How to Create a New Scope

1.

Click Start, point to Programs, point to Administrative Tools, and then click DHCP.

2.

In the console tree, right-click the DHCP server on which you want to create the new DHCP scope, and then click New Scope.

3.

In the New Scope Wizard, click Next, and then type a name and description for the scope. This can be any name that you want, but it should be descriptive enough so that you can identify the purpose of the scope on your network (for example, you can use a name such as "Administration Building Client Addresses"). Click Next.

4.

Type the range of addresses that can be leased as part of this scope (for example, use a range of IP addresses from a starting IP address of 192.168.100.1 to an ending address of 192.168.100.100). Because these addresses are given to clients, they must all be valid addresses for your network and not currently in use. If you want to use a different subnet mask, type the new subnet mask. Click Next.

5.

Type any IP addresses that you want to exclude from the range that you entered. This includes any addresses in the range described in step 4 that may have already been statically assigned to various computers in your organization. Typically, domain controllers, Web servers, DHCP servers, Domain Name System (DNS) servers, and other servers, have statically assigned IP addresses. Click Next.

6.

Type the number of days, hours, and minutes before an IP address lease from this scope expires. This determines how long a client can hold a leased address without renewing it. Click Next, and then click Yes, I want to configure these options now to extend the wizard to include settings for the most common DHCP options. Click Next.

7.

Type the IP address for the default gateway that should be used by clients that obtain an IP address from this scope. Click Add to add the default gateway address in the list, and then click Next.

8.

If you are using DNS servers on your network, type your organization's domain name in the Parent domain box. Type the name of your DNS server, and then click Resolve to make sure that your DHCP server can contact the DNS server and determine its address. Click Add to include that server in the list of DNS servers that are assigned to the DHCP clients. Click Next, and then follow the same steps if you are using a Windows Internet Naming Service (WINS) server, by adding its name and IP address. Click Next.

9.

Click Yes, I want to activate this scope now to activate the scope and allow clients to obtain leases from it, and then click Next.

10.

Click Finish.

11.

In the console tree, click the server name, and then click Authorize on the Action menu.

http://support.microsoft.com/library/images/support/kbgraphics/public/en-us/uparrow.gifBack to the top

Troubleshooting

The following sections explain how to troubleshoot some of the issues that you may experience when you try to install and configure a Windows Server 2003-based DHCP server in a workgroup.

Clients Cannot Obtain an IP Address

If a DHCP client does not have a configured IP address, this typically indicates that the client was not able to contact a DHCP server. This can be caused by a network problem, or because the DHCP server is unavailable. If the DHCP server started and other clients can obtain valid addresses, verify that the client has a valid network connection and that all the related client hardware devices (including cables and network adapters) are working properly.


The DHCP Server Is Unavailable

If a DHCP server does not provide leased addresses to clients, it is frequently because the DHCP service did not start. If this is the case, the server may not be authorized to operate on the network. If you were previously able to start the DHCP service, but it has since stopped, use Event Viewer to check the System log for any entries that may explain why you cannot start the DHCP service.

To restart the DHCP service:

1.

Click Start, and then click Run.

2.

Type cmd, and then press ENTER.

3.

Type net start dhcpserver, and then press ENTER.

-or-

1.

Click Start, point to Control Panel, point to Administrative Tools, and then click Computer Management.

2.

Expand Services and Applications, and then click Services.

3.

Locate and then double-click DHCP Server.

4.

Verify that Startup is set to Automatic and that Service Status is set to Started. If not, click Start.

5.

Click OK, and then close the Computer Management window.

http://support.microsoft.com/library/images/support/kbgraphics/public/en-us/uparrow.gifBack to the top

REFERENCES

For additional information about DHCP in Windows Server 2003, click the following article number to view the article in the Microsoft Knowledge Base:

169289 (http://support.microsoft.com/kb/169289/EN-US/) DHCP (Dynamic Host Configuration Protocol) Basics

167014 (http://support.microsoft.com/kb/167014/EN-US/) DHCP Client May Fail to Obtain a DHCP-Assigned IP Address

133490 (http://support.microsoft.com/kb/133490/EN-US/) Resolving Duplicate IP Address Conflicts on a DHCP Network

263217 (http://support.microsoft.com/kb/263217/EN-US/) Windows DHCP Server Gives Incorrect Settings for the Default Gateway or the DNS Server

http://support.microsoft.com/library/images/support/kbgraphics/public/en-us/uparrow.gifBack to the top


APPLIES TO

•

Microsoft Windows Server 2003, Enterprise Edition (32-bit x86)

•

Microsoft Windows Server 2003, Standard Edition (32-bit x86)

•

Microsoft Windows Small Business Server 2003 Premium Edition

•

Microsoft Windows Small Business Server 2003 Standard Edition

 

DHCP

http://www.windowsnetworking.com/articles_tutorials/DHCP_Server_Windows_2003.html

Bookmark & Share

© Add This

http://s7.addthis.com/services/favorites.png Favorites

http://s7.addthis.com/services/delicious.png Del.icio.us

http://s7.addthis.com/services/digg.png Digg

http://s7.addthis.com/services/goog.png Google

http://s7.addthis.com/services/myspace.png MySpace

http://s7.addthis.com/services/facebook.gif Facebook

http://s7.addthis.com/services/reddit.gif Reddit

http://s7.addthis.com/services/live.gif Live

http://s7.addthis.com/services/furl.gif Furl

http://s7.addthis.com/services/yahoo-myweb.png Yahoo MyWeb

http://s7.addthis.com/services/su.png StumbleUpon

http://s7.addthis.com/services/plus-16x16-light.gif More...


Setting up a DHCP server in Windows 2003

"Dynamic Host Configuration Protocol (DHCP) is an IP standard designed to reduce the complexity of administering IP address configurations." - Microsoft's definition. A DHCP server would be set up with the appropriate settings for a given network. Such settings would include a set of fundamental parameters such as the gateway, DNS, subnet masks, and a range of IP addresses. Using DHCP on a network means administrators don't need to configure these settings individually for each client on the network. The DHCP would automatically distribute them to the clients itself.

The DHCP server assigns a client an IP address taken from a predefined scope for a given amount of time. If an IP address is required for longer than the lease has been set for, the client must request an extension before the lease expires. If the client has not requested an extension on the lease time, the IP address will be considered free and can be assigned to another client. If the user wishes to change IP address then they can do so by typing "ipconfig /release", followed by "ipconfig /renew" in the command prompt. This will remove the current IP address and request a new one. Reservations can be defined on the DHCP server to allow certain clients to have their own IP address (this will be discussed a little later on). Addresses can be reserved for a MAC address or a host name so these clients will have a fixed IP address that is configured automatically. Most Internet Service Providers use DHCP to assign new IP addresses to client computers when a customer connects to the internet - this simplifies things at user level.

http://www.windowsnetworking.com/img/upl/dhcp1074171258500.jpg

The above diagram diplays a simple structure consisting of a DHCP server and a number of client computers on a network.

The DHCP Server itself contains an IP Address Database which holds all the IP addresses available for distribution. If the client (a member of the network with a Windows 2000 Professional/XP operating system, for example) has "obtain an IP address automatically" enabled in TCP/IP settings, then it is able to receive an IP address from the DHCP server.

Setting up a DHCP Server

This will serve as a step-by-step guide on how to setup a DHCP server.

Installing the DHCP server is made quite easy in Windows 2003. By using the "Manage your server" wizard, you are able to enter the details you require and have the wizard set the basics for you. Open to "Manage your server" wizard, select the DHCP server option for the list of server roles and press Next.
You will be asked to enter the name and description of your scope.

Scope: A scope is a collection of IP addresses for computers on a subnet that use DHCP.

http://www.windowsnetworking.com/img/upl/scope11074178111489.jpg

The next window will ask you to define the range of addresses that the scope will distribute across the network and the subnet mask for the IP address. Enter the appropriate details and click next.

http://www.windowsnetworking.com/img/upl/scope21074172130484.jpg

You are shown a window in which you must add any exclusions to the range of IP addresses you specified in the previous window. If for example, the IP address 10.0.0.150 is that of the company router then you won't want the DHCP server to be able to distribute that address as well. In this example I have excluded a range of IP addresses, 10.0.0.100 to 10.0.0.110, and a single address, 10.0.0.150. In this case, eleven IP's will be reserved and not distributed amongst the network clients.

http://www.windowsnetworking.com/img/upl/scope31074172189828.jpg

It is now time to set the lease duration for how long a client can use an IP address assigned to it from this scope. It is recommended to add longer leases for a fixed network (in the office for example) and shorter leases for remote connections or laptop computers. In this example I have set a lease duration of twelve hours since the network clients would be a fixed desktop computer in a local office and the usual working time is eight hours.

http://www.windowsnetworking.com/img/upl/scope41074172263218.jpg

You are given a choice of whether or not you wish to configure the DHCP options for the scope now or later. If you choose Yes then the upcoming screenshots will be of use to you. Choosing No will allow you to configure these options at a later stage.

http://www.windowsnetworking.com/img/upl/scope51074172453640.jpg

The router, or gateway, IP address may be entered in next. The client computers will then know which router to use.

http://www.windowsnetworking.com/img/upl/scope61074172651765.jpg

In the following window, the DNS and domain name settings can be entered. The DNS server IP address will be distributed by the DHCP server and given to the client.

http://www.windowsnetworking.com/img/upl/scope71074172720531.jpg

If you have WINS setup then here is where to enter the IP Address of the WINS server. You can just input the server name into the appropriate box and press "Resolve" to allow it to find the IP address itself.

http://www.windowsnetworking.com/img/upl/scope81074172799421.jpg

The last step is to activate the scope - just press next when you see the window below. The DHCP server will not work unless you do this.

http://www.windowsnetworking.com/img/upl/scope91074172872828.jpg

The DHCP server has now been installed with the basic settings in place. The next stage is to configure it to the needs of your network structure.

Configuring a DHCP server

Hereunder is a simple explanation of how to configure a DHCP server.

The address pool displays a list of IP ranges assigned for distribution and IP address exclusions. You are able to add an exclusion by right clicking the address pool text on the left hand side of the mmc window and selecting "new exclusion range". This will bring up a window (as seen below) which will allow you to enter an address range to be added. Entering only the start IP will add a single IP address.

http://www.windowsnetworking.com/img/upl/dhcp_exclude1074173011359.jpg

DHCP servers permit you to reserve an IP address for a client. This means that the specific network client will have the same IP for as long as you wanted it to. To do this you will have to know the physical address (MAC) of each network card. Enter the reservation name, desired IP address, MAC address and description - choose whether you want to support DHCP or BOOTP and press add. The new reservation will be added to the list. As an example, I have reserved an IP address (10.0.0.115) for a client computer called Andrew.

http://www.windowsnetworking.com/img/upl/dhcp_reserve1074173059296.jpg

If you right click scope options and press "configure options" you will be taken to a window in which you can configure more servers and their parameters. These settings will be distributed by the DHCP server along with the IP address. Server options act as a default for all the scopes in the DHCP server. However, scope options take preference over server options.

In my opinion, the DHCP server in Windows 2003 is excellent! It has been improved from the Windows 2000 version and is classified as essential for large networks. Imagine having to configure each and every client manually - it would take up a lot of time and require far more troubleshooting if a problem was to arise. Before touching any settings related to DHCP, it is best to make a plan of your network and think about the range of IPs to use for the computers.

About Andrew Z. Tabona

Andrew Z. Tabona photoAndrew Z. Tabona (MCSA, Network+, Security+, etc) heads a QA/CRM team at GFI Software, a leading global security and messaging software firm. Prior to this he plied his trade as a Network Administrator and an independent technical trainer. He has written a wealth of articles, manuals, white papers, etc and tries to “bridge the gap” with his easy going style of writing.

Click here for Andrew Z. Tabona's section.