You are currently offline, waiting for your internet to reconnect

HOW TO: Change the IP Address of an Automated Deployment Services (ADS) Controller

Support for Windows Server 2003 ended on July 14, 2015

Microsoft ended support for Windows Server 2003 on July 14, 2015. This change has affected your software updates and security options. Learn what this means for you and how to stay protected.

Important This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:
256986 Description of the Microsoft Windows Registry

IN THIS TASK

SUMMARY
This step-by-step article describes how to change the IP address of an Automated Deployment Services (ADS) Controller. The procedure applies to configurations where the ADS services are collocated (running on one server) and to configurations where ADS services are dispersed across many systems, except where noted.

back to the top

Change the IP Address of the ADS Controller

  1. Change the IP address of the ADS Controller (the Windows Server 2003-based computer that runs the ADS Controller service) by using any supported method. For example, you can change the IP address in the properties of your network adapter, or you can use the Netsh.exe tool from the command line.

    For additional information about how to use the Netsh.exe tool, click the following article number to view the article in the Microsoft Knowledge Base:
    242468 How to Use the Netsh.exe Tool and Command-Line Switches
  2. Verify that the IP address change was successful. Make sure that you can connect to remote servers. Also, verify that the computer name and the IP address are correctly registered in DNS and in Windows Internet Naming Service (WINS). You can use the Nslookup utility to verify DNS entries.

    For additional information about how to use the Nslookup utility, click the following article number to view the article in the Microsoft Knowledge Base:
    200525 Using Nslookup.exe
back to the top

Update the Registry with the New IP Address of the ADS Controller

WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.
  1. Start Registry Editor.
  2. Locate and then click the following registry key:
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Adsctlr\BMDP\Parameters
  3. In the right pane, right-click BindExcept, and then click Modify.
  4. In the Value data box, change the existing IP address to the new IP address of the ADS Controller, and then click OK.
  5. If the ADS services are not collocated, skip this step and go to step 6. The other services will discover the new IP address when the ADS Controller service is restarted.

    If the ADS services are collocated, repeat steps 2 through 4 for each of the following registry keys:
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ADSBUILDER\Parameters

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\adsimgsvc\Parameters

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ADSPXE\Parameters
  6. Quit Registry Editor.
back to the top

Use the ADS Management Console to Change the IP Address in the Properties of Each ADS Service

  1. Start the ADS console. To do this, click Start, point to All Programs, point to Microsoft ADS, and then click ADS Management.
  2. Expand Automated Deployment Services (server name), and then click Services.
  3. Right-click Controller Service, and then click Properties.
  4. In the IP_address box, type the new IP address for the ADS Controller, and then click OK.
  5. If the ADS services are not collocated, skip this step.

    If the ADS services are collocated, repeat steps 3 and 4 for Network Boot Services and Image Distribution Service.
back to the top

Restart the ADS Services

  1. Click Start, point to Administrative Tools, and then click Services.
  2. If the ADS services are not collocated, and if only the IP address of the ADS Controller was changed, restart only the ADS Controller service.

    If the ADS services are collocated, restart the following ADS services:
    • ADS Controller
    • ADS Deployment Agent Builder
    • ADS Image Distribution Service
    • ADS PXE Service
    • ADS Administration Agent
After you restart the services, view the ADS console to make sure that all the services show their state as Connected. You may have to update the console view first. To do this, click Refresh on the Action menu. Also, check both the system event log and the application event log to make sure that the ADS services have started correctly.

back to the top

Update the Registry for Devices that Run the ADS Administration Agent

For any device that runs the ADS Administration Agent, you must update the
ControllerIPAddress
registry value with the new IP address of the ADS Controller so that the device can locate the ADS Controller. To update the device's registry key with the new IP address of the ADS Controller, follow these steps.

WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.
  1. On the computer that runs the Administration Agent, start Registry Editor.
  2. Locate and then click the following registry key:
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\BMSS
  3. In the right pane, right-click BindExcept, and then click Modify.
  4. In the Value data box, change the existing IP address to the new IP address of the ADS Controller, and then click OK.
  5. Restart the computer.
back to the top

Test and Troubleshoot

After you make these changes, boot a device into the Deployment Agent, and then send a test job to the client that runs the Administration Agent. This will make sure that the ADS server functions correctly.

If devices show up in the ADS console with the status of Busy or Disconnected, determine whether there are any active jobs that are running against those devices. You can look for active jobs in the ADS console under Running jobs, or you can type adsjob /l at a command prompt and then press ENTER. If you find that active jobs are running, try to stop them. Update the ADS console view. If the device's state does not change, verify that the registry values that you configured with the new IP address of the ADS Controller are correct.

back to the top
Properties

Article ID: 825039 - Last Review: 09/22/2003 16:18:29 - Revision: 2.2

Microsoft Windows Server 2003 Enterprise Edition, Microsoft Windows Server 2003 Datacenter Edition

  • kbhowtomaster KB825039
Feedback
soft.com/c.gif?DI=4050&did=1&t=">/html>