on wds, wdsutil, and VHDs February 27, 2010
Posted by examROAR in Uncategorized.Tags: 70-686, deployment, virtualization, Windows Deployment Services
add a comment
WDS on Server 2008 R2 supports deploying VHD images. These images are automated with an answer file (unattend.xml). In order to deploy VHDs, your configuration must also include the following requirements:
- Only W7 Ent.\Ultimate & Server 08 R2 supported
- Single partition \ single OS VHDs only
- WDSUTIL must be used to add \ remove images (wdsutil /add-image /imagefile: c:\images\Windows7.vhd)
configure WDS for multicasting February 26, 2010
Posted by examROAR in Uncategorized.Tags: 70-686, deployment, Windows Deployment Services
add a comment
From technet- here’s how you configure the WDS namespace for multicasting:
Creating a namespace
To transfer data by using multicasting, you must create a namespace to define how the data is transferred. For example, you must manually set the names for the data and data groups and the path to the folder that contains the data.
Prerequisites for creating a namespace
To create a namespace with Transport Server, you need the following:
- A content provider. You can use the Windows Deployment Services content provider (named WDS) that is included when you install Transport Server. Or you can create your own content provider by using the tools in the Windows SDK.
- Data to transmit. You can transmit any data that your content provider knows how to find (for example, operating system images, data files, or an MP3 archive). The Windows Deployment Services content provider knows how to find any file within a directory.
- Familiarity with WDSUTIL. The only way to manage Transport Server is through the WDSUSTIL command-line tool.
- Routers. The routers in your environment must support multicasting.
Steps for creating a namespace with Transport Server
You can create Scheduled-Cast and Auto-Cast namespaces. For more information about each parameter, see the Options section later in this document.
- To create a Scheduled-Cast namespace, run:
WDSUTIL /New-Namespace [/Server:] /Namespace: /FriendlyName: [/Description:] /ContentProvider: /ConfigString: /NamespaceType:ScheduledCast [/Time:] [/Clients:]For example:
WDSUTIL /New-Namespace /Server:MyWDSServer /FriendlyName:"Custom Scheduled Namespace" /Namespace:"Custom Scheduled 1" /ContentProvider:WDS /ConfigString:D:\Images /NamespaceType:ScheduledCast /Time:"2006/11/20:17:00" /Clients:20 - To create an Auto-Cast namespace, run:
WDSUTIL /New-Namespace [/Server:] /FriendlyName: /Namespace: [/Description:] /ContentProvider: /ConfigString: /NamespaceType:AutoCastFor example:
WDSUTIL /New-Namespace /FriendlyName:"Custom AutoCast Namespace" /Namespace:"Custom Auto 1" /ContentProvider:WDS /ConfigString:D:\Images /NamespaceType:AutoCast
