STEP 4. Install ADS
With DHCP installed and operational, you can install ADS 1.1. You can download ADS from the Microsoft Web page at http://www.microsoft.com/windowsserver2003/technologies/management/ads/default.mspx. In this page, you'll see a link to download the technical documentation. The ADS download includes this documentation, so you don't need to download it separately. Here are the instructions to install ADS on the MobileP2V server:
- Run the self-extracting executable and put its contents into the C:\Temp directory on the MobileP2V server.
- Double-click ADSSetup.exe to start the installation.
- On the Welcome to Microsoft Windows Server 2003 Automated Deployment Services page, click Install Microsoft SQL Server Desktop Engine (MSDE).
- After MSDE installs, click Install Automated Deployment Services - Setup to launch the Automated Deployment Services Setup Wizard.
- On the welcome page, click Next.
- On the License Agreement page, review the license agreement. If you agree to the terms of the license, accept them and click Next.
- On the Setup Type page, select Full Installation, then click Next. You'll see a warning regarding installing PXE. Because the mobile ADS server will be isolated, this isn't a problem, so click OK.
- On the Configure the ADS Controller page, leave the default settings and click Next.
- On the Network Boot Service Settings page, select the Prompt for the path when required option. At the bottom of the page, select the Configure these services now option, which automatically configures the DHCP service to interoperate with the ADS PXE service. Click Next.
- On the Windows PE Repository page, select the Do Not Create a Windows PE repository option. Click Next
- On the Image Location page, type D:\IMAGES in the Path to folder text box. Click Next.
- If the ADS setup program detects more than one network adapter on your server, it displays the Network Settings for ADS Services page. In the Bind to this IP address text box, specify 10.10.10.1 as the IP address that ADS should bind to for services, then click Next.
- Click Install.
- During installation, the setup program creates a certificate that's used to authenticate destination devices. After the installation completes, create a directory called D:\ADSCERT, share it as ADSCERT, and copy the C:\Program Files\Microsoft ADS\Certificate\Adsroot.cer file in that directory.
- In the C:\Program Files\Microsoft ADS\Samples\Sequences directory, doubleclick create-templates.bat to install the ready-to-run job templates.
- Check the Event Viewer to make sure that no errors occurred during the installation process.
You can use the MMC ADS snap-in to make sure that all the ADS services (i.e., Controller Service, Image Distribution Service, and Network Boot Services) are in the connected state. To launch the ADS snap-in, select Run on the Start menu, type ads.msc, and click OK. Click the Services folder. As Figure 2 shows, the right pane then displays the status of the three ADS services. The State column should read Connected for each service.
STEP 5. Test ADS
To ensure that ADS is operating correctly, you need to use the test server, which we'll name TESTSERVER, to perform some basic functions. However, you first need to install the ADS Administration Agent on your test server and add TESTSERVER as a device on the ADS Controller.
To install the Administration Agent, connect your test server to the network switch on your mobile ADS solution. Copy the ADS files from MobileP2V to TESTSERVER. After the ADS files are in place, double-click ADSSetup.exe and select the option to install the ADS Administration Agent. The Administration Agent Setup Wizard appears and walks you through the installation process. On the Configure Certificates page, select the Now option and type \\mobilep2v\adscert\adsroot.cer as the path to the certificate. On the Configure the Agent Logon Settings page, select None for the agent's logon settings.
To add TESTSERVER as a device on the ADS Controller, you can use the ADS snapin. In the console tree, right-click Devices, then select Add Device. Type TESTSERVER for the device name and click OK. In the right pane, right-click the device, select Take control, then click OK.
After you've made TESTSERVER a controlled device, you need to set the default template on TESTSERVER so that it always boots into the Deployment Agent. To do this, right-click the TESTSERVER device, then click Properties. In the TESTSERVER Properties dialog box, select boot-to-da in the Default Job Template drop-down list box.
Now that the necessary preparations are complete, you can run one of the sample scripts in the C:\Program Files\Microsoft ADS\Samples\Agentscripts folder to make sure ADS is operating correctly. In the ADS snap-in, rightclick the TESTSERVER device, then click Run job to start the Run Job Wizard. Click Next. On the Job Type page, click Create a onetime job, then click Next. On the Description page, enter test job as the job's description and click Next. On the Command Type page, click Script or executable program, then click Next. On the Script or Executable Program page, enter C:\Program Files\Microsoft ADS\Samples\ Agentscripts\Cpuspeed.vbs in the Path to file text box. Make sure that the Send to the device check box is selected, then click Next. Click Finish to complete the wizard and run the job. Make note of the Job ID that appears after the wizard runs.
To view the results of the job you just ran, click History in the left pane of the ADS snap-in. In the right pane, double-click the Job ID of the job you just ran. If you see TESTSERVER's CPU speed in the job history results, you've successfully configured ADS. However, you're not quite done yet. You still need to make sure Network Boot Services is working properly.
To test Network Boot Services, boot TESTSERVER using the built-in PXE boot client or the RIS boot floppy disk. After TESTSERVER boots, the test server should get an address from the DHCP server, contact Network Boot Services to download the ADS Deployment Agent image, download the image into memory, start the agent, and show that the Deployment Agent is in a connected state, as Figure 3 shows. At this point, you've verified that the ADS task sequences are working, DHCP and Network Boot Services are working, and that you can use jobs to remotely control the test server.
Register
