Difference between revisions of "Active Directory/Documentation/WDS/Management/Server Setup"

From WolfTech
Jump to navigation Jump to search
(→‎Authorizing the WDS server: Remove outdated WolfTech-specific info.)
Line 36: Line 36:
 
==Authorizing the WDS server==
 
==Authorizing the WDS server==
 
* If you are using a custom DHCP template that directs PXE clients to your server, you can skip this step.  See [[../Separating DHCP From WDS]] for more info.
 
* If you are using a custom DHCP template that directs PXE clients to your server, you can skip this step.  See [[../Separating DHCP From WDS]] for more info.
Have a domain admin login to one of the domain controllers (DC Admins: use NOIR), select the DHCP admin tool, then "authorize servers". Add in the IP address of the new server.
+
Have a domain admin login to one of the domain controllers, select the DHCP admin tool, then "authorize servers". Add in the IP address of the new server.
  
 
==Resources==
 
==Resources==
 
*http://technet2.microsoft.com/WindowsVista/en/library/9e197135-6711-4c20-bfad-fc80fc2151301033.mspx?mfr=true
 
*http://technet2.microsoft.com/WindowsVista/en/library/9e197135-6711-4c20-bfad-fc80fc2151301033.mspx?mfr=true
 
*http://technet2.microsoft.com/WindowsVista/en/library/88f80cb7-d44f-47f7-a10d-e23dd53bc3fa1033.mspx?mfr=true
 
*http://technet2.microsoft.com/WindowsVista/en/library/88f80cb7-d44f-47f7-a10d-e23dd53bc3fa1033.mspx?mfr=true

Revision as of 14:45, 17 July 2009

WDS Setup

Running a WDS server requires either Windows 2003 Server or Windows Server 2008. If you need to deploy Windows XP clients via RIS, you need to use Windows 2003 Server as your WDS server OS, because Windows Server 2008 WDS cannot run in legacy or hybrid modes. It is highly recommended that you migrate your RIS images to wim format and start using WDS native mode, however.

Windows Server 2008

Coming soon!

Windows 2003 Server

  1. Install Windows 2003 Server R2 SP2
    • Create separate partition for images. (Required for RIS; not necessary but recommended for WDS)
  2. Install Windows Deployment Services from Add/Remove Programs/Windows Components
  3. Reboot
  4. Setup Legacy RIS
    1. Open Administrative Tools > Windows Deployment Services Legacy
    2. Edit default computer creation location
      1. In ADUC, open the WDS server's properties
      2. In the Remote Install tab, Click Advanced Settings
      3. Choose "The following directory service location," and browse to the desired OU.
  5. Open Administrative Tools > Windows Deployment Services
    1. Expand Servers
    2. Right click on the server and select Configure Server.
      1. Choose a path on the 2nd drive (ie E:\RemoteInstall).
      2. Choose PXE Response policy.
  6. Install the Windows Automated Installation Kit
  7. Add boot images
    1. c:\program files\Windows AIK\Tools\PETools\x86\winpe.wim
    2. c:\program files\Windows AIK\Tools\PETools\amd64\winpe.wim
    3. boot.wim from the Vista disc
  8. Add an install image. For more info, see [[../WDS_Images | WDS Images]]
  9. Set share permissions
    1. RemoteInstall shared with Everyone RWA access
    2. Remove Authenticated Users from RemoteInstall.
    3. Add permissions for Setup for ECE-OU Admins, ECE-Computer Admins, ECE-Allow RIS
    4. Add permissions for Images for ECE-OU Admins, ECE-Computer Admins

Authorizing the WDS server

  • If you are using a custom DHCP template that directs PXE clients to your server, you can skip this step. See [[../Separating DHCP From WDS]] for more info.

Have a domain admin login to one of the domain controllers, select the DHCP admin tool, then "authorize servers". Add in the IP address of the new server.

Resources