visionapp Server Management 2008 R2

visionapp Server Management 2008 R2
WDS Installation Guide
Product Documentation
software.visionapp.com
software.visionapp.com
Contents
1
About this Documentation ................................................................................... 1
1.1
Required Knowledge...............................................................................1
1.2
Formats and Symbols .............................................................................1
2
Introduction......................................................................................................... 2
3
Requirements ...................................................................................................... 2
4
Configuration ....................................................................................................... 3
5
6
4.1
Windows 2003 or Windows 2008 Server ...................................................3
4.2
Windows Automated Installation Kit (WAIK) ..............................................4
4.3
Setting up the WDS server ......................................................................4
4.4
Setting up a WDS site in vADM ................................................................5
4.5
visionapp-specific configuration for WinPE Boot Images ..............................6
Image capturing and image deployment.............................................................. 8
5.1
Image capturing ....................................................................................8
5.2
Image deployment .................................................................................9
5.2.1
Creating the Image Sysprep set...............................................................9
5.2.2
Deploying an image ............................................................................. 11
Disclaimer .......................................................................................................... 12
software.visionapp.com
I
1
About this Documentation
1.1
Required Knowledge
In order to successfully work with this manual, a profound knowledge of working with
Microsoft Windows Terminal Services and Citrix XenApp Server farms is required. In addition,
a basic knowledge of Microsoft Windows Server operating systems and software distribution
solutions for operating systems and applications is helpful.
Furthermore, the manual is aimed at people involved in installation, administration and
troubleshooting of servers. visionapp AG assumes that you are qualified in server
maintenance and have been trained to work with the installed software products. This
documentation presupposes a certain knowledge of technical matters and technical terms.
Understanding and using the information provided in this documentation will be easier with a
good knowledge of the documentations listed below:
> vADM online help
In case a problem cannot be solved with the information provided, please visit our website for
additional troubleshooting information.
1.2
Formats and Symbols
The following formats are used for the various instructions:
Bold
Menu names and entries, window names, input and list fields, messages
and important statements are shown in bold.
Monospace
Program code, paths and file names are shown in monospace font.
Links
Underlined red text refers to a hyperlink.
The following symbols are used:
The first-aid box indicates solutions for particular issues, provides hints on
special features, or reveals unusual solutions.
The question/answer symbol indicates a note. It points out special points that
need to be observed for proper functioning of the product.
The warning symbol indicates particularly important sections in the
document. It also reveals practical tips that might help you avoid data loss,
product damage, or other inconveniencies.
software.visionapp.com
1
2
Introduction
Windows Deployment Services from Microsoft offers the possibility of a push installation of
operating systems, i,e, without activating or controlling the client. This allows the installation
or re-installation of an operating system on servers from a central location.
To achieve a problem-free installation some special points need to be taken into account,
which are described in this document. The described tasks include the initial setup of a
Microsoft Windows Deployment Services (WDS) server, preparing a visionapp-compliant
WinPE boot image, and the steps required to capture and deploy an image.
This documentation is intended as a guideline for capturing images from a Windows 2008 or a
Windows 2003 operating system and how to deploy these images using the vADM Console.
Special attention is paid for the visionapp-specific configuration settings.
3
Requirements
One of the base requirements for successful working with this document is a good knowledge
of how to install, configure and operate Microsoft Windows Terminal services and Citrix
Presentation Server farms. Basic familiarity with Microsoft Windows server operating systems
and the deployment of operating systems and applications is recommended.
This documentation addresses people that are responsible for installing, administering and
troubleshooting Windows-based servers. visionapp assumes that readers are suitably
qualified and trained for these tasks and have basic knowledge about the relevant technical
issues and terminology.
To get the most out of this document, you should read the following documents before using
this document:
>
>
>
>
>
Microsoft Windows Deployment Services online help
Unattended Windows Setup Reference
Windows Automated Installation Kit (Windows AIK) User’s Guide
Windows Preinstallation Environment (Windows PE) User’s Guide
vADM Console online help
software.visionapp.com
2
If you are unable to resolve particular problems that occur during the installation or operation
of WDS, you can find further help and information on our Website. Our website also provides
information about:
>
>
>
>
current and upcoming products
product upgrades and updates
visionapp partners near you
numerous white papers and presentations
4
Configuration
The steps to setup a WDS environment described here apply to a Windows
2003 x86 system or a Windows 2008 x86 system.
The steps required to install a Windows 2003 or 2008 x64 system may differ in
certain points.
Please note, that the WDS server must be a member of an Active Directory
domain and that correctly configured DHCP and DNS services must be available
on the network.
4.1
Windows 2003 or Windows 2008 Server
> Install a Windows 2003 or Windows 2008 Server, including the latest service packs and
updates.
> Make sure that this server is the only one in its subnet that offers PXE services.
> Adding Windows Deployment Services under Windows 2003 Server: Add the Windows
Deployment Services using Add/Remove Windows Components (Start  Settings 
Control Panel  Add or Remove Programs  Add/Remove Windows Components). Please
have your Windows 2003 installation CD ready.
> Adding Windows Deployment Services under Windows 2008 Server: Add the Windows
Deployment Services with Start  Administrative Tools  Server Manager  Add Roles.
software.visionapp.com
3
4.2
Windows Automated Installation Kit (WAIK)
> Download the latest WAIK from the Microsoft website.
> Install WAIK following the setup instructions, observing the following points:
> .NET Framework 2.0 must be installed (this may have been installed with step 4.1).
> MSXML 6.0 must be installed (this may have been installed with step 4.1).
> If Windows 2003 Service Pack 2 can not be installed, the WDS Update Package for
Windows 2003 Service Pack 1 must be installed.
4.3
Setting up the WDS server
> Launch the WDS Server Console with Start  Programs  Administrative Tools 
Windows Deployment Services.
> If the local computer has not yet been added, right-click the node Server and add a new
WDS server.
> In the dialog that opens select the local computer.
> Right-click on the new server’s node and select Configure Server from the context menu:
> Click Next on the Welcome Page.
> Accept the default settings for the Remote Installation share. If the selected drive
contains the system partition, ignore any warnings that may pop up.
Note that the visionapp WDS components communicate with the Reminst
default share on the WDS server.
Do not change this share name; otherwise the communication between vADM
and WDS server and between WinPE client and WDS server will no longer work.
> If the WDS and DHCP services are running on the same machine, check both boxes in
the dialog DHCP Option 60.
> In the PXE service settings select Respond to all (known and unknown) client
computers and make sure the notify option for administrators is unchecked.
> Click Finish, uncheck the Add images... box and click Finish again.
> Copy the WinPE Boot Image from <WAIK Program Folder>\Tools\PE Tools\x86\winpe.wim
to a folder of your choice and rename it to vPE.wim.
The visionapp WinPE Agent (vPEA.exe) is executable only in the 32-bit WinPE
Boot Image.
The 32-bit WinPE Boot Image can also be used to do deploy 64-bit (x64) target
machines.
software.visionapp.com
4
> In the WDS console, right-click the Boot Images node and select Add Boot Images:
> In the next dialog select the folder containing the image you have just copied and
renamed.
> In the next dialog define the Boot Image as vPE and set its description to visionapp
WinPE Boot Image. Alternatively you can choose any other name and description. But
for simplicity we will refer to the image as vPE Image below.
> Click Next and then Finish.
> Having created the server and added the Boot Image, right-click the WDS server in the
WDS Console and select Properties from the context menu.
> Select the Boot tab and, under Default Boot Program, select:
> for x86 systems the file pxeboot.n12 in folder
C:\RemoteInstall\Boot\x86\pxeboot.n12).
> for x64 systems the file pxeboot.n12 in folder
C:\RemoteInstall\Boot\x64\pxeboot.n12).
> If the WDS and DHCP services are running on the same machine, select the DHCP tab
and check both boxes.
> Close the Properties dialog.
Note that Windows server systems with an enabled firewall must be configured
to allow incoming requests.
For further information about allowing access to shared folders, write access to
files and SQL, registry and WMI queries to a WDS server with firewall, see the
appropriate Microsoft documentation.
In addition, in their default setting, the visionapp WinPE Agent Loader
(vPEALoader.exe) and the vORS service (which runs on the WDS server) need
ports 10000, 10001 and 10002 for communications. Communication through
these ports must also be enabled in the firewall.
If necessary, the ports of the visionapp components can be configured or
changed for the vORS service by editing the file vPEALoader.ini (the
initialization file for vPEALoader.exe, located in the vPEA folder on the WinPE
Boot Image) and through the Registry.
4.4
Setting up a WDS site in vADM
> Launch the vADM Console and select the topic Software Library:
> Right-click the node Windows Deployment Services and select New > WDS Site from
the context menu..
> Enter the following information in the dialogs:
> A server name (WDS Server Address) under which the server can be addressed in
the network.
> A user account with administrative rights for access to the WDS server.
> Confirm the dialog. In the next dialog enter a unique name for the WDS site and complete
the creation of the site.
software.visionapp.com
5
> After creating the WDS site, switch back to the WDS server console.
If you have not entered an administrative user account for using the built-in
logon when you set up the WDS site, specify an administrator and the
corresponding password for the target machine in vADM in the WDS Site
properties. The target machines need this user account to establish a
connection to the WDS server.
4.5
visionapp-specific configuration for WinPE Boot Images
> In the root folder of a partition on the WDS server create a folder mountedimage (e.g.
c:\mountedimage)
> Launch the command shell for the WAIK tools (Start  Programs  Microsoft Windows
AIK  Windows PE Tools Command Prompt).
> Enter the following command in the command shell to mount the Boot Image, created in
step 3.3:
> imagex /mountrw c:\RemoteInstall\Boot\x86\Images\vPE.wim 1 c:\mountedimage
> Copy the folder vPEA from the Site directory that you created through the vADM Console
into the directory mountedimage:
> C:\RemoteInstall\visionapp\WDSSites\IhreSite\Files\vPEAFiles\vPEA to
C:\mountedimage\vPEA
> Copy the corresponding System32 files from your created site to the folder system32 of
the Boot Image:
> C:\RemoteInstall\visionapp\WDSSite\IhreSite\Files\vPEAFiles\System32\winpeshl.ini
to C:\mountedimage\Windows\System32\winpeshl.ini
> C:\RemoteInstall\visionapp\WDSSite\IhreSite\Files\vPEAFiles\System32\winpe.bmp to
C:\mountedimage\Windows\System32\winpe.bmp
> Copy the WAIK imaging tool Imagex.exe to the system32 folder of the Boot Image:
> C:\Program Files\Windows AIK\Tools\x86\Imagex.exe to
C:\mountedimage\Windows\System32\Imagex.exe
> Copy the WAIK multicast tool wdsmcast.exe to the folder system32 of the Boot Image
> C:\Program Files\Windows AIK\Tools\x86\wdsmcast.exe to
C:\mountedimage\Windows\System32\wdsmcast.exe
> Install all drivers required by the hardware of your machines by entering the following
command:
> peimg /inf=<path to the .in file> c:\mountedimage. Repeat this step for all drivers
required.
Make sure that all network interface card and hard disk controller drivers are
installed.
software.visionapp.com
6
> You can find additional language packages for the WinPE Boot Image on the WAIK
installation volume in folder <WAIK source path>\WINPE_LANGPACKS\X86\. Open the
corresponding directory for your preferred language and enter
> peimg /import <cab file path> c:\mountedimage\Windows to import all cab
files that can be imported from the corresponding language pack directory. Repeat the
command for each cab file.
> After that, type peimg
/list c:\mountedimage to display all available packages for the
WinPE Boot Image:
> Install all packages that are displayed with a “-” (hyphen) using the following
command:
> peimg /install=<Paketname> C:\mountedimage\windows. You can use wildcards,
e.g. *hta* for a WinPE HTA package.
> Run this command for each required package and language.
Make sure that you install the packages for MDAC, HTA, WMI, XML and
scripting, since the visionapp WinPE agent uses these components in various
places.
> Choose the desired language for the WinPE Boot Image using the following command:
> peimg /lang=<language abbreviation> c:\mountedimage\Windows (e.g.:
peimg /lang=de-DE)
> Complete the WinPE Boot Image editing with the following command:
> peimg /prep c:\mountedimage
> Unmount the boot image by typing the following command in the console:
> imagex /unmount /commit c:\mountedimage (the switch /commit saves the
settings).
The WinPE Boot Image is now configured for use with vADM.
software.visionapp.com
7
5
Image capturing and image deployment
After configuring the WDS server and the WinPE boot image you can start capturing and
deploying Windows 2008 or Windows 2003 WIM images.
For the following steps you need experience in using the vADM Console. Refer
to the vADM 2008 documentation for details.
If you have installed the vADM 2008 R2 Console and the WDS server on the
same Windows 2008 machine, observe that, with the Windows User Access
Control feature enabled, a WDS Site can be created only if the vADM Console
has been started with administrator rights.
If this is not the case, the Windows safety settings will prevent the creation of
a WDS site. For further information see the relevant Microsoft documentation.
5.1
Image capturing
> Set up a Windows 2008 or Windows 2003 server and configure it as desired.
> In the vADM Console, create this server under the topic Infrastructure Management under
a farm that has WDS selected as OS deployment method.
> Make sure that a MAC address is provided on the General tab of this server.
> Make sure that the created server can be accessed in the network under the specified
name. If necessary configure the target system’s Windows firewall accordingly.
> Alternatively you can enter a different address in the field Use alternative target
address if the target machine is not accessible under the NetBIOS name defined in the
vADM infrastructure management.
> Make sure that PXE boot is activated in the target server’s BIOS and that the boot order is
set to PXE boot first.
software.visionapp.com
8
> If you want to capture a Windows 2003 system, make sure that the local administrator
password on the target machine is blank. For details, see
http://support.microsoft.com/kb/200607/en-us
Because of the higher security standards in Windows 2003, the blank
administrator password requires a further setting. If the image is being created
using the vADM Console, the files required to create the image – sysprep.exe,
setupcl.exe and syprep.inf – are copied to the template server at runtime.
If the administrator password is blank, copying will fail because the local
default Windows 2003 group policy settings prevents access to shares without
password.
The local group policy must therefore be changed on the template server. On
the template server select Start  Run to launch gpedit.msc and under
Computer configuration\Windows Settings\Security settings\Local
Policies\Security Options set the value Limit local account use of blank
password to console only to Disabled. This value is overwritten by the domain
group policy when an image is written to the computer later and joins a
domain.
> If you want to capture a Vista system, make sure that the Remote Registry Service has
been started on the target machine. During the capture the vADM Console queries various
data from the target machine’s Registry.
> Select the server you have created and select the WDS tab. Then navigate to the Capture
Image tab:
> Under Site name select the WDS site that you have created in step 4.4.
> Under Image name and Description enter a name and a description for the image to
be captured.
> Click Capture Image to start image capture.
> Wait until the capture process is completed. You can refresh the status by clicking the
Refresh button on the WDS tab.
5.2
5.2.1
Image deployment
Creating the Image Sysprep set
> Switch to Software Library and select the WDS Site, created in step 4.4:
> Right-click on the Image Store node and select New  Image.
> In the dialog, select the newly captured image:
> Make sure to set the appropriate operating system version.
> Click OK to add the image.
software.visionapp.com
9
> Navigate to the node Sysprep Store:
> With a right-click create a new Sysprep configuration:
> Choose a unique name.
> Select the operating system version (Windows 2008 x86 or Windows 2008 x64 or
Windows 2003 x86 or Windows 2003 x64).
> Confirm your input with OK.
> Enter suitable values for each Sysprep configuration setting or leave them blank to
have them as variables.
> Note that it is not possible to add or remove Sysprep parameters in vADM 2008 when
using Windows 2008 x86 or x64 configurations.
> Note that the Sysprep configuration in vADM 2008 requires the integration into an
existing Windows domain with one network interface card when using Windows 2008
x86 or x64 configurations.
Note that the following parameters must be entered if a Windows 2003 x86,
Windows 2003 x64-, Windows XP x86 or Windows XP x64 Sysprep
configuration is used:
[GuiUnattended] – Autologon = Yes
[GuiRunOnce] – RunOnceEntry1 = "C:\vPEA\vPEA.exe OS"
These values are important because they allow operating system
installation to be continued and completed after the Sysprep Mini
Setup phase.
> Save your configuration and exit the node.
Currently DHCP is not supported by the Windows 2008 Sysprep parameters. A
static IP address and a subnet mask must therefore be configured in the
General tab.
> Right-click the node Image Sysprep Sets under the WDS Site that you created in step 4.4.
> With a right-click create a new image Sysprep script configuration:
> Choose a unique name.
> Select the newly created Sysprep configuration.
> Select the image created in step 5.1.
> Select a vPEA script (if you have not yet created a custom script, use the default
script). For further information see the vADM 2008 R2 documentation).
software.visionapp.com
10
> Enter the values that have not been configured in the Sysprep configuration:
> Note that you do not need to provide values for ComputerName, Identifier
(Windows 2008), NetCardAddress (Windows 2003) and IPaddress. These
parameters will be completed individually for each server.
> Save the image Sysprep set and exit the node.
For Windows 2003 and Windows XP target systems deployed with the WDS
module, the Sysprep parameter AutoLogon in section GuiUnattended must be
set to Yes.
5.2.2
Deploying an image
> Switch to Infrastructure and select the server created in 5.1.
> Select the WDS tab and select the Installation tab:
> Select the image Sysprep set created in 5.2.1.
> Click the Start button to start image deployment.
> Wait until the deployment is completed. You can check the progress by clicking the
Refresh button on the WDS tab.
software.visionapp.com
11
6
Disclaimer
Disclosure and Warranty
The information, concepts, and ideas contained in this document are the property of visionapp
AG. No part of this document may be disclosed or reproduced in any form without written
permission of visionapp AG. Any violation thereof will be pursued.
All brand names and product names used in this document are trademarks of their respective
holders and are recognized as such.
Any product descriptions or representations in this document are for identification purposes
only and are not to be construed as a warranty of specific properties or guarantee or warranty
of any other type. visionapp shall assume no liability, either explicit or implied, for the
documentation.
All rights reserved ©visionapp AG, October 2008
About visionapp
visionapp specializes in the design, implementation and operation of server-based
infrastructure and portal solutions based on Microsoft and Citrix technologies. The company
provides unique products and services for optimization and cost-effective administration of
Windows Terminal Server infrastructures. visionapp Application Delivery Management Suite
including visionapp Server Management and visionapp Workspace Management as well as
consulting and ASP services form the core business.
The visionapp products and solutions will be provided through a worldwide certified partner
network. Only in Germany visionapp delivers products and solutions directly to large
enterprises. The SME market is also being supplied through certified partners.
Technical Support
visionapp Application Delivery Management Suite (vADM) is developed by visionapp AG.
Technical support is provided through the visionapp website and by e-mail.
The visionapp website software.visionapp.com offers varied information and downloads:
> Information on new products
> Product updates and fixes
> Whitepapers and presentations
The latest product versions and the supporting documentation is available under
software.visionapp.com/download-center.
For technical support via email, please contact:
support@visionapp.com
software.visionapp.com
12
Please include the following information in your request so that we can provide quick and
efficient support:
>
>
>
>
>
>
>
>
Your visionapp Application Delivery Management Suite version.
Your visionapp Server Management and visionapp Workspace Management edition.
Version, name and language of the client operating system of your vADM Console.
Version, name and language of the database server of your vADM Console.
Version, service pack and language of the Microsoft SQL server of your vADM database.
A detailed description of the issue, including messages.
Logs from the Event Logs of the servers affected.
Any relevant screenshots that may be useful for further assistance.
Using visionapp Server Management:
> Detailed information on the target platforms of the servers to be managed and installed.
> A ZIP file with a complete copy of the visionapp folder on the target platform. This folder
is located under %ProgramFiles%. If this directory is too large to be sent, we need the
following files or folders as minimum information:
>
>
>
>
>
>
%ProgramFiles%\visionapp\visionapp.ini
%ProgramFiles%\visionapp\visionapp.xml
%ProgramFiles%\visionapp\ICS\ICS.ini
%ProgramFiles%\visionapp\ICS\Install.log
%ProgramFiles%\visionapp\ICS\Log
%ProgramFiles%\visionapp\Log\visionapp.log
> If the visionapp directory does not exist yet, also send the vTT.log file located in the root
directory (c:\).
Using visionapp Workspace Management:
>
>
>
>
>
>
Name, version and language of the webs servers used.
Name, version and language of the database of your vAC database used.
Version, service pack and language of the Microsoft SQL server of your vAC database.
Name, version and language of the application servers used.
Name and version of the Internet browser.
The export files of visionapp.config, web.config and configuration data (everything from
vADM Console under Export basic settings).
Further Information
visionapp AG
Head Office Frankfurt am Main
Helfmann-Park 2
65760 Eschborn
Germany
web: software.visionapp.com
software.visionapp.com
13