http://technet.microsoft.com/en-us/library/hh831764.aspx
http://technet.microsoft.com/en-us/library/jj648426.aspx
Image file contains OS system files, updates & drivers, installed apps, configuration changes
Prerequisites: Installed: ADDS, DHCP, DNS, NTFS volume, Local Admin
1.1.1 Install the Windows Deployment Services (WDS) role
Windows Deployment Services (WDS) Roles:
Deployment Server (WDS-Deployment) - Image repository(on NTFS), PXE Server, TFTP(uses
UDP) to transport files
Transport Server (WDS-Transport) - subset role that's required by Deployment Server. However, this
can be installed by itself for advanced custom setups.
WDS Tools (WDS-AdminPack)
Install from Server Manager: select server, select WDS, Include Tools, Select Role Services: Deployment Services and Transport Server should be checked
Powershell:
install-windowsfeature -name wds -includemanagementtools
Initial Configuration:
Server Manager -> Tools -> Windows Deployment Services (wdsmgmt.msc)
Expand or double click Servers. The current server will shows as status "Not Configured"
Right-click "Configure server"
Prerequisites are shown. Click Next.
Select "Integrated with Active Directory"
Remote
Install Folder will store the boot images, install images, PXE boot
files, and WDS Tools.You will be warned if you place this folder on the
system volume.
If you are running DHCP on the same server as WDS you will see the Proxy DHCP settings. "Do not listen on DHCP ports" should be checked. This stops WDS from listening on port 67. The next option "Configure DHCP options for proxy" will set option 60 on a MS DHCP server. Non-MS servers should be configured manually.
Set your PXE settings: Do not respond to any
clients, Respond to only known clients, Respond to all clients
(suboption: Require admin approval for unknown computers under Pending
Devices)
You can now check "Add images to server now" if you would like to add images now. Finish.
WDSutil:
Wdsutil /initialize-server /reminst "c:\wdsfolder"
use /server switch for remote WDS server.
use /authorize to authorize in dhcp if needed
(you can also authorize at a later time with wdsutil /set-server /authorize:yes)
After-install configuration:
Configuring the WDS properties:
right click the server and select properties
General
PXE response - covered above in the initialization
ADDS: naming format for unknown clients. Set location to create new computer accounts
Boot: setup pxe options for known and unknown clients and locations for boot images
Clients: Configure unattended install answer file for various client architectures. Configure after-install domain joining. Enable client logging.
DHCP: covered above in the initialization
Multicast: configurations for mass image installing
Advanced: DC and GC prefererence, DHCP authorization
Network: WDS port specification. Network Profile option no longer valid in 2012.
TFTP: TFTP options.
Extra Note: You can unintialize a server using wdsutil and the /unintialize-server switch
Extra Note: New cmdlets for configuring WDS introduced in "Windows Powershell 4.0,
Windows Server 2012 R2 Preview". I started these notes pre-R2 so I only be using WDSUtil for command line configuration examples.
1.1.2 configure and manage boot, install, and discover images
Images use Windows Imaging Format (WIM)
Right click Boot Images and Add Image File. You're looking for boot.wim on the OS install CD.
To add an install image, you right click install image and "Add Install Image". There is a default install image on every OS install CD called install.wim which will do a standard install. Otherwise you can add a custom image here as well.
Image Groups: An image group is made up of images that shares security options and file resources.
Resource WIM file(res.rwm) will contain the file resources for all of the images in a group.
Right clicking a boot image gives you the option to create a capture image or discover image off of that boot image.
Capture image: This image is used to grab an image off the client pc and capture it as a new install image. Images must be sysprep'd before capture. use /generalize and /oobe switches
Discover image: used to boot on a computer that does not support pxe. You can put it on a bootable medium(ie. CDROM) and boot off that. To convert the discover WIM to ISO, use the Windows Assessment and Deployment Kit's oscdimg.exe utility.
Image priority: lowest value is shown first in menu on the client.
Image permissions: can be set in the properties of each image or image group to control who has access to install the image
Unattended Install:
Unattended installs use answer files in XML format that can be created using Windows System Image Manager, part of the WADK. To deploy a server with unattended install you must have an answer file for the boot image and the install image. For the boot image, go to server properties/client tab and check "Enable unattended installation". Then browse to your answer file for the appropriate architecture. Next, go to your images and right click properties and check the "Allow image to install in unattended mode and browse to your answer file for this image under Select file.
WDSUtil:
wdsutil /add-image /imagefile:"c:\wds\boot\boot.wim" /imagetype:boot
wdsutil /add-image /imagefile:"c:\wds\install\install.wim" /imagetype:install
other parameters:
/Imagegroup
/SingleImage: single image from WIM
/Name: Sets image display name
/Description: Sets description
/unattendfile: path for answer file
1.1.3 update images with patches, hotfixes, and drivers
The main thing to know is how to use the DISM tool. As of windows 2008 R2, you can use the WDS console to add drivers to boot images(useful for adding new network driver due to new hardware), and also they added a feature called dynamic driver provisioning(see 1.1.5). Let's start with DISM.
First thing about DISM is to mount the image:
First you want to get the index of the image you want to work with:
dism /get-wiminfo /wimfile:E:\WDSimages\install\windows7install.wim
If you would like to see specific info about this image, just add /index:
dism /get-wiminfo /wimfile:E:\WDSimages\install\windows7install.wim /index:1
Now we need to mount it:
dism /mount-wim /wimfile:E:\WDSimages\install\windows7install.wim /index:1 /mountdir:E:\WDSimages\currentimage
This will expand the image into E:\wdsimages\currentimage.
To add packages, patches, hotfixes, etc that are in .cab or .msu format, use:
dism /image:E:\WDSimages\currentimage /add-package /packagepath:E:\WDSupdates\packages\newpackage.cab
Instead of /add-package use /remove-package to remove from the image
To add drivers to a mounted WIM:
dism /image:e:\wdsimages\currentimage /add-driver /driver:e:\wdsupdates\drivers\newdriver.inf
you can add a lot of drivers at once with the /recurse switch.
dism /image:e:\wdsimages\currentimage /add-driver /driver:e:\wdsupdates\drivers /recurse
use /remove-driver to remove drivers
Now you must unmount the image and either commit or discard changes:
dism /unmount-image /mountdir:e:\wdsimages\currentimage /commit
dism /unmount-image /mountdir:e:\wdsimages\currentimage /discard
About the Dynamic Driver Provisioning in WDS console(2008 R2+):
See the R2 objective 1.1.5.
Extra Note: you can also install drivers using an unattended install answer file.
1.1.4 install features for offline images
You can also install features into WIM images using the DISM utility.
Mount your dism image as explained in 1.1.3
List the features available on this image:
dism /image:e:\wdsimages\currentimage /get-features
Enable a feature:
dism /image:e:\wdsimages\currentimage /enable-feature /featurename:SMTP-SERVER
Disable a feature:
dism /image:e:\wdsimages\currentimage /disable-feature /featurename:SMTP-SERVER
Now you must unmount and /commit your mounted image as shown in 1.1.3
1.1.5 (R2) Configure driver groups and packages
Drivers are installed as the image is installed, not injected directly
into the image. Keep in mind that you can also configure dynamic driver
provisioning with wdsutil.
http://technet.microsoft.com/en-us/library/dd348456.aspx
Add driver packages by right clicking Drivers under the WDS server, and selecting "Add driver packages". You can select a package from an inf file, or select all packages in a folder. Click next to select drivers you want to add. Next you an select an existing group to add to, create a new driver group to add the package to, or leave it unassigned. If you added it to a group, you can edit the filters for the group.
Right click the "Drivers" sub-menu and select "Add Driver Group". You can configure a filter that takes into account the hardware of the client. Some example filter types: Manufacturer, Model, Bios Vendor, Bios Version, Chassis Type, UUID, and Device Group. Next, you can configure a filter by install image using the filter types: OS Version, OS Edition, OS Language, or Image ID.
(Example, OS Version requires Majorversion.Minorversion.Buildnumber.ServicePackNumber. Image ID requires GUID of image)
Finally, you can configure whether driver packages will only be installed if they match client hardware, or if all driver packages in the group will be installed.
Other options when right clicking Drivers: Enable/Disable Driver Packages, Delete Driver Packages. Let's you search for drivers to disable/enable or delete.
Other options when right clicking a driver group:
Disable, Duplicate - Clone the group to a new one, Modify Filters, Add driver packages to
the group, Delete, Rename
Properties - let's you enabled/disable group, set whether drivers only get installed if hardware
exists on client, and edit filters on the Filters tab.
Clicking on All Packages will show you all driver packages. Right click on a driver package allows:
Add or Remove package to group, Disable, Delete, Rename
Properties - Rename, enable/disable, view package info like location and architecture;
Drivers tab lists drivers in package; Files tab lists all files in package;
Group Membership tab to update groups for package.
No comments:
Post a Comment