Administrators Guide: Managing Wyse® Thin Clients with ... · PDF fileAdministrators Guide...

Administrators GuideManaging Wyse® Thin Clients with Microsoft® System Center Configuration Manager 2007 and Embedded Device Manager 2011

Issue: 013012 PN: 883955-01 Rev. A

ii

Copyright Notices© 2012, Wyse Technology Inc. All rights reserved.

This manual and the software and firmware described in it are copyrighted. You may not reproduce, transmit, transcribe, store in a retrieval system, or translate into any language or computer language, in any form or by any means, electronic, mechanical, magnetic, optical, chemical, manual or otherwise, any part of this publication without express written permission.

End User License Agreement (“License”)A copy of the Wyse Technology End User License Agreement is included in the software and provided for your reference only. The License at http://www.wyse.com/license as of the purchase date is the controlling licensing agreement. By copying, using, or installing the software or the product, you agree to be bound by those terms.

TrademarksThe Wyse and PocketCloud logos and Wyse and PocketCloud are trademarks of Wyse Technology Inc. Other product names mentioned herein are for identification purposes only and may be trademarks and/or registered trademarks of their respective companies. Specifications subject to change without notice.

Restricted Rights LegendYou acknowledge that the Software is of U.S. origin. You agree to comply with all applicable international and national laws that apply to the Software, including the U.S. Export Administration Regulations, as well as end-user, end-use and country destination restrictions issued by U.S. and other governments. For additional information on exporting the Software, see http://www.microsoft.com/exporting.

Ordering InformationFor availability, pricing, and ordering information in the United States and Canada, call 1-800-GET-WYSE (1-800-438-9973) or visit us at http://www.wyse.com. In all other countries, contact your sales representative.

http://www.wyse.com/license

http://www.microsoft.com/exporting

http://www.wyse.com/

Contents

1 Introduction 1About this Guide 1

Finding the Information You Need in this Guide 1Wyse Technical Support 2

Related Documentation and Services 2Wyse Online Community 2

2 Getting Started: Prerequisites and Supported Management Features 3General Prerequisites 3Wyse Enhanced WES7 Firmware Image Prerequisites for Configuration Manager and Device Manager Support 4Management Features Supported 4

3 How to Distribute Software 5Phase 1: Creating a Software Package that is Ready for Distribution 5Phase 2: Advertising the Software Package Using Device Manager 7

4 Using File-Based Write Filter Aware Task Sequences 9What is a File-Based Write Filter Aware Task Sequence? 9

Adding a Task to Disable the File-Based Write Filter 9Adding a Task to Enable the File-Based Write Filter 9

Working Case Example: How to Deploy a Mozilla Firefox Software Package to Wyse Thin Clients Protected by the File-Based Write Filter 10

5 Imaging Wyse Thin Clients with Configuration Manager 13Phase 1: Capturing an OS Image from a Reference Thin Client 13Phase 2: Importing the Captured OS Image (WIM File) into the Configuration Manager Server 17Phase 3: Deploying the OS Image to the Destination Client Using the Operating Systems Deployment (OSD) Task Sequence 18

6 Windows Security Update Deployment 25Creating Common Search Folders 25Creating a New Search Folder for a Specific Year 26Creating a New Search Folder for New Monthly Releases 26Case Example: Downloading and Installing Security Updates 27

A Localization Requirements: Multilingual User Interface (MUI) 31Contents of the sysprep.xml File 32

B Troubleshooting and Reference Information 35Troubleshooting Tools 35Microsoft Reference Documents 35Configuration Manager-Device Manager Script Details 36

iv Contents

This page intentionally blank.

1 Introduction

Wyse provides a simple solution to support and extend Microsoft® System Center Configuration Manager 2007 (Configuration Manager) and Windows® Embedded Device Manager 2011 (Device Manager) capabilities to manage Wyse thin clients running Wyse® Enhanced Microsoft® Windows Embedded Standard 7.

Configuration Manager is a systems management software product by Microsoft for managing large groups of Windows-based computer systems. Some of the Configuration Manager features are:• Deploying operating systems• Deploying software applications• Deploying software updates• Collecting hardware and software inventory• Metering software usage• Reporting

Device Manager extends the capabilities of Configuration Manager to enable the management of specialized devices such as thin clients.

About this GuideThis guide is intended for administrators of Wyse thin clients running Wyse Enhanced WES7. It provides the necessary information for using the Wyse solution to support and extend Configuration Manager and Device Manager capabilities to manage Wyse thin clients running Wyse Enhanced WES7.

This guide contains information on • Features supported for Wyse Enhanced WES7 builds by Configuration Manager SP2

and Device Manager. • Software distribution of Wyse Enhanced WES7 images using Configuration Manager

SP2 and Device Manager. • OS Capture and deployment of the Wyse Enhanced WES7 image using Configuration

Manager SP2 and Device Manager.

Configuration Manager, Device Manager, and Windows Embedded Standard 7 help can be accessed from the Microsoft Help and Support Web site at: http://support.microsoft.com/default.aspx.

Windows Embedded Device Manager 2011 Administration Guide can be accessed on TechNet at: http://technet.microsoft.com/en-us/library/ff522826.aspx.

Finding the Information You Need in this GuideYou can use either the Search window or Find toolbar to locate a word, series of words, or partial word in an active PDF document. For detailed information on using these features, refer to the Help in your PDF reader.

http://technet.microsoft.com/en-us/library/ff522826.aspx

http://support.microsoft.com/default.aspx

2 Chapter 1

Wyse Technical SupportTo access Wyse technical resources, visit http://www.wyse.com/support. If you still have questions, you can submit your questions using the Wyse Self-Service Center at http://support.wyse.com/selfservice.html or call Customer Support at 1-800-800-WYSE (toll free in U.S. and Canada). Hours of operation are from 6:00 A.M. to 5:00 P.M. Pacific Time, Monday through Friday.

To access international support, visit http://www.wyse.com/global.

Related Documentation and ServicesFact Sheets containing the features of hardware products are available on the Wyse Web site. Go to http://www.wyse.com/products/hardware, click the link for your hardware product, and then click the link for the Fact Sheet.

If you need to upgrade your operating system, contact Wyse Customer Support at: http://www.wyse.com/support.

Wyse Online CommunityWyse maintains an online community where users of our products can seek and exchange information on user forums. Visit the Wyse Online Community forums at: http://community.wyse.com/forum.

http://www.wyse.com/support

http://www.wyse.com/support

http://www.wyse.com/products/hardware

http://support.wyse.com/selfservice.html

http://www.wyse.com/global

http://www.wyse.com/products

http://community.wyse.com/forum/

2 Getting Started: Prerequisites and Supported Management FeaturesBefore using Configuration Manager and Device Manager, be sure to meet all prerequisites and understand the supported management features for Wyse thin clients contained in the following sections:• "General Prerequisites"• "Wyse Enhanced WES7 Firmware Image Prerequisites for Configuration Manager and

Device Manager Support"• "Management Features Supported"

CautionIf you are planning for Multilingual User Interface Deployments for WES7, refer to "Localization Requirements: Multilingual User Interface (MUI)" before you begin.

General PrerequisitesGeneral prerequisites include:• Wyse Enhanced WES7 firmware image prerequisites (see "Wyse Enhanced WES7

Firmware Image Prerequisites for Configuration Manager and Device Manager Support")

• Configuration Manager Advanced Client• Additional storage space may be required to cache software updates • Configuration Manager SP2 infrastructure supporting Operating Systems Deployment

(OSD) through the PXE service• Configuration Manager R2 SP2• Device Manager• Configuration Manager Advanced Client hotfix KB2516850 (Ramdisk hotfix)• Device Manager Client Agent• Device Manager Client Agent hotfix KB2619310

For some platforms, there is a BIOS dependency for image capture and deployment. Below are validated Wyse platforms and their BIOS:• R class: 1.0J-0T51• C class: 1.0B-0407• Z class: 1.0L• X90c7: 1.0G (Image push through PXE is not supported)• X90m7: 1.0M

4 Chapter 2

Wyse Enhanced WES7 Firmware Image Prerequisites for Configuration Manager and Device Manager Support

Prerequisites include:

1. Configuration Manager Advanced Client must be installed on the client device

2. RamDisk hotfix (KB2516850) for Configuration Manager Advanced Client must be installed on the client device

3. Device Manager Client Agent must be installed on the client device

4. Device Manager hotfix (KB2619310) must be installed on the client device

5. Configuration Manager Scripts for preparing the image for capture and deployment must be available on the client device

6. Device Manager Server Agent must be installed on Configuration Manager server

7. Client device must be joined to a domain

8. Client device must be discovered and available in the Configuration Manager server console

IMPORTANT: Prerequisites 1, 2, 3, 4, and 5 are part of the Wyse Enhanced WES7 WFR3 builds. For older builds, you must download and install the Configuration Manager Advanced Client, Device Manager Client Agent, hotfix KB2516850, and hotfix KB2619310 on thin clients, and then copy the latest Configuration Manager scripts (which are available in latest sysprep4man.zip) to the thin clients.

For hotfix KB2516850, see http://support.microsoft.com/kb/2516850.

For hotfix KB2619310, see http://support.microsoft.com/kb/2619310.

Management Features Supported Management features supported by Configuration Manager and Device Manager on Wyse thin clients running Wyse Enhanced WES7 include:• Configuration Manager + Device Manager supports:

· Asset Discovery· Asset Inventory· Image Pull· Image Push· Software package advertisement· Task Sequence advertisement

• Device Manager supports:· Device Configuration· Write-Filter Management

http://support.microsoft.com/kb/2516850


3 How to Distribute Software

This section explains how third party software can be distributed to Wyse thin clients running Wyse Enhanced WES7.

Software distribution includes the following phases (in order):

1. "Phase 1: Creating a Software Package that is Ready for Distribution"

2. "Phase 2: Advertising the Software Package Using Device Manager"

TipWhile you can use a Configuration Manager task sequence to Advertise the software package (see "Using File-Based Write Filter Aware Task Sequences"), using Device Manager (as described in "Phase 2: Advertising the Software Package Using Device Manager") will automatically handle the File-Based Write Filter disabling and enabling that is required when deploying software packages.

Phase 1: Creating a Software Package that is Ready for Distribution

Step 1: Create a Software Package

1. In the Configuration Manager console, open the New Package Wizard (select Site Database > Computer Management > Software Distribution > Packages, right-click Packages, and then select New > Package).

2. On the General page, name the package, for example: Firefox App, enter any other information you need, and then click Next.

3. On the Data Source page, select the This package contains source files option, click Set, select the path for the Source Directory where the firefox application installer is present (for example, C:\sccm_packages\apps\firefox), select the Always obtain source files from the source directory option, and then click Next. IMPORTANT: The path/folder selected should contain the artifacts that will be required by the package.

4. On the Data Access page, click Next.

5. On the Distribution Settings page, set Sending Priority to High, and then click Next.

6. On the Reporting page, click Next.

7. On the Security page, click Next.

8. On the Summary page, click Next.

9. After the wizard is completed, click Close. The package should appear under the Packages node of the Site database tree in the Configuration Manager console.

6 Chapter 3

Step 2: Create a Program for the Package

1. Under the Packages node, select the Firefox App package to expand it.

2. Open the New Program Wizard (right-click Programs, and then select New > Program).

3. On the General page, enter any program details you need, enter the program name, for example: Firefox, click Browse, set files of type to All Files (*.*), select the application installer file (in our example case: firefox.exe), click Open, type the silent installer option -ms (in our example case: “firefox.exe” -ms) for installing firefox silently. NOTE: The silent installation option varies for different applications.

4. On the Requirements page, select This program can run only on specified client platforms, select only the All x86 Windows 7 option, and then click Next.

5. On the Environment page, set Program can run to the Whether or not a user is logged on option, select the Run with Administrative Rights option, and then click Next.

6. On the Advanced page, click Next.

7. On the Windows Installer page, click Next.

8. On the MOM Maintenance page, click Next.


10.After the wizard is completed, click Close. The program should appear under the Program node of the respective package.

Step 3: Add a Distribution Point to the Software Package


2. Open the New Distribution Points Wizard (right-click Distribution Points, and then select New > Distribution Points), and then click Next.

3. On the Copy Package page, select the servers that you want to designate as the distribution points (other than PXE point), and then click Next.

4. After the wizard is completed, click Close. The distribution points should appear under the Distribution Point node of the respective package.


6. Right-click Distribution Points, select Update Distribution Points, and then click Yes. The package should be copied to all Distribution Points, except the PXE point.

How to Distribute Software 7

Phase 2: Advertising the Software Package Using Device Manager1. In the Configuration Manager console, open the New Advertisement Wizard (select

Site Database > Computer Management > Embedded Device Management > Write Filter Servicing > Advertisements with Write Filter Handling, right-click Advertisements with Write Filter Handling, and then select New).

2. On the Getting Started page, select the I understand that the devices option and the Package supports unattended installation option, and then click Next.

3. On the General page, enter the name for the advertisement, for example: Deploying Firefox App, and do the following:• For package selection, click Browse, select the Firefox package you created, and

then click OK.• For collection selection, click Browse, select the collection (for example, Wyse

Z-Class devices), and then click OK.

4. Click Next.

5. On the Schedule page, click on the yellow star next to Mandatory assignments to open the Assignment Schedule window, select the Assign immediately after this event option, select As soon as possible in the drop down list, click OK, and then do the following:• In the Priority drop down list, select High. • (Optional) Set the Advertisement start time and expires settings you want.

6. Click Next.

7. On the Distribution Points page, click Next.

8. On the Interaction page, click Next.


10.On the Summary page, click Next.

11.Click Close. The advertisement with the name you assigned should appear on the Advertisements with Write Filter Handling page.

IMPORTANT: Time for the Advertisement to appear at the client side depends on the machine and user policy refresh interval time, server and network parameters such as server capacity to handle the clients and network traffic.

If you do not receive an Advertisement, then you must initiate on the thin client:

1 - Go to Control Panel > Configuration Manager > Actions tab, select Machine Policy Retrieval & Evaluation, and then click Initiate Action.

2 - Go to Control Panel > Configuration Manager > Actions tab, select User Policy Retrieval & Evaluation Cycle, and then click Initiate Action.

8 Chapter 3


4 Using File-Based Write Filter Aware Task SequencesThis section explains how to create and use task sequences that are File-Based Write Filter aware to easily install software (and perform other tasks) on your Wyse thin clients that are protected by the File-Based Write Filter.

It includes:• "What is a File-Based Write Filter Aware Task Sequence?"• "Working Case Example: How to Deploy a Mozilla Firefox Software Package to Wyse

Thin Clients Protected by the File-Based Write Filter"

What is a File-Based Write Filter Aware Task Sequence?A File-Based Write Filter aware task sequence is a task sequence that includes disable and enable tasks for use with Wyse thin clients that are protected by the File-Based Write Filter. Specifically, to use a task sequence on Wyse thin clients that are protected by the File-Based Write Filter, you must add a disable task to the beginning of the task sequence and then add an enable task to the end of the task sequence.

For example, a File-Based Write Filter aware task sequence could be as follows:

1. Disable the thin client File-Based Write Filter.

2. Install software onto the thin client.

3. Enable the thin client File-Based Write Filter.

After you create your File-Based Write Filter aware task sequence, you can then Advertise it using Configuration Manager.

Adding a Task to Disable the File-Based Write FilterTo add a Disable File-Based Write Filter task to a task sequence:

1. Select the task sequence to be edited.

2. Right-click the task sequence and select Edit to open the Task Sequence Editor.

3. Click Add > Write Filter > Disable Write Filter. The Disable File-Based Write Filter task is added in the task editor.

Adding a Task to Enable the File-Based Write FilterTo add an Enable File-Based Write Filter task to a task sequence:

1. Select the task sequence to be edited.

2. Right-click the task sequence and select Edit to open the Task Sequence Editor.

3. Click Add > Write Filter > Enable Write Filter. The Enable File-Based Write Filter task is added in the task editor.

10 Chapter 4

Working Case Example: How to Deploy a Mozilla Firefox Software Package to Wyse Thin Clients Protected by the File-Based Write Filter

In this working example, you will create and Advertise a File-Based Write Filter aware task sequence for use on Wyse thin clients that are protected by the File-Based Write Filter.

TipUse the guidelines in this example to create and use task sequences that are File-Based Write Filter aware with your Wyse thin clients that are protected by the File-Based Write Filter.

Step 1: Create a Task Sequence

1. In the Configuration Manager console, open the New Task Sequence Wizard (select Site Database > Computer Management > Operating System Deployment > Task Sequences, right-click Task Sequences, and then select New > Task Sequence).

2. On the Create New Task Sequence page, select the Create a New Custom Task Sequence option, and then click Next.

3. On the Task Sequence Information page, name the task sequence, for example: Firefox Deployment as TS, and then click Next.


5. After the wizard is completed, click Close. The new task sequence with the name you assigned should appear on the Task Sequences page.

Step 2: Add a Disable File-Based Write Filter Task to the Task Sequence

1. Right-click the new task sequence (in our example case: Firefox Deployment as TS) and select Edit to open the Task Sequence Editor window.

2. Click Add > Write Filter > Disable Write Filter. The Disable File-Based Write Filter task is added in the task editor.

Step 3: Add an Install Software Task to the Task Sequence

1. In the Task Sequence Editor window, click Add > General > Install Software. The Install Software task is added in the task editor.

2. Change the name to the name you want, click Browse, select a software package you created and want to use (see "Phase 1: Creating a Software Package that is Ready for Distribution"), and then click OK.

TipYou can add as many performance tasks (such as software installation) as you want by repeating "Step 3: Add an Install Software Task to the Task Sequence." After you have completed adding the tasks you want, continue with "Step 4: Add an Enable File-Based Write Filter Task to the Task Sequence."

Step 4: Add an Enable File-Based Write Filter Task to the Task Sequence

1. In the Task Sequence Editor window, click Add > Write Filter > Enable Write Filter. The Enable File-Based Write Filter task is added in the task editor.

2. In the Task Sequence Editor window, click Apply, and then click OK.

Using File-Based Write Filter Aware Task Sequences 11

Step 5: Advertise the Task Sequence1. Right-click the new task sequence (in our example case: Firefox Deployment as TS)

and select Advertise to open the New Advertisement Wizard.

2. On the General page, enter the name for the advertisement, for example: Deploying Firefox App as TS, and then click OK.

3. Click Next.


5. Click Next.

6. On the Distribution Points page, select the Access Content Directly from a Distribution Point option, and then click Next.

7. On the Interaction page, select the Show Task Sequence Progress option, and then click Next.



10.After the wizard is completed, click Close. The advertisement with the name you assigned (in our example case: Deploying Firefox App as TS) should appear under Software Distribution > Advertisement.





12 Chapter 4


5 Imaging Wyse Thin Clients with Configuration ManagerThis section explains how to capture, import, and deploy an OS image to Wyse thin clients (running Wyse Enhanced WES7) in a Configuration Manager environment.

Imaging includes the following phases (in order):

1. "Phase 1: Capturing an OS Image from a Reference Thin Client"

2. "Phase 2: Importing the Captured OS Image (WIM File) into the Configuration Manager Server"

3. "Phase 3: Deploying the OS Image to the Destination Client Using the Operating Systems Deployment (OSD) Task Sequence"

CautionThe steps included in this section are for administrators who are familiar with OS imaging and Configuration Manager usage. If you are planning for Multilingual User Interface Deployments for WES7, refer to "Localization Requirements: Multilingual User Interface (MUI)" before you begin.

Phase 1: Capturing an OS Image from a Reference Thin Client

Step 1: Format a USB Pen Drive

1. Attach your USB pen drive to your thin client running Wyse Enhanced WES7.

2. Open a command prompt and type diskpart.

3. Use the diskpart tool to determine the disk number of the USB pen drive by typing list disk at the diskpart prompt.

4. Use the diskpart tool to partition and format the USB pen drive. At the diskpart command prompt, type the following, replacing <disk_number> with the disk number of the USB pen drive Select disk <disk_number> Clean Create part pri Select part 1 active format fs=ntfs quick assign exit

14 Chapter 5

Step 2: Add a Network Driver to the Boot Image (x86) File on the Configuration Manager Server

TipBefore capturing the OS image from the reference thin client, a network adapter driver for your specific hardware must be added to the boot image (x86) file on the Configuration Manager server.

1. In the Configuration Manager console, select Site Database > Computer Management > Operating System Deployment > Drivers, right-click Import, and then select the Import all drivers in the following network path (UNC) option.

2. Click Browse, locate and select the network driver you obtained from Wyse or your hardware vendor, and then click Next.

3. On the Driver Details page, select the inf file corresponding to the appropriate platform network adapter, and then click Next.

4. On the Add Driver to Packages page, select New Package to open the New Driver Package window, enter the name for the driver package, and then do the following:• For driver package source, click Browse, select a network share folder, and then

click OK (IMPORTANT: The folder to select is not the driver’s source, but the separate shared folder where ConfigMgr will maintain drivers added to this package).

5. Select the Driver package just created (IMPORTANT: Ensure that all other driver packages in the list are not selected) and click Next.

6. On the Add Driver to Boot Images page, select Boot Image (x86) for the boot image, and then click Next.


8. After the wizard completes the process, click Close.

9. In the Configuration Manager console, select Site Database > Computer Management > Operating System Deployment > Boot Images > Boot Image (x86), right-click Properties, select the Windows PE tab, and then ensure the network driver you imported is listed. IMPORTANT: If any error occurs during the import of a driver into an Operating System Deployment, you must install Microsoft hotfix KB978754 (see Microsoft Support at http://support.microsoft.com/kb/978754).

Step 3: Use Configuration Manager to Create a Capture Media USB Pen Drive or CD/DVD that will Capture the Operating System Image

1. In the Configuration Manager console, open the Task Sequence Media Wizard (select Site Database > Computer Management > Operating System Deployment > Task Sequence, right-click Task Sequence, and then select Create Task Sequence Media).

2. On the Select Media Type page, select Capture Media, and then click Next.

3. On the Media Type page, select CD/DVD set, click Browse, enter the location and name for the ISO, and then click Next.

4. On the Boot Image page, click Browse, select Boot Image (x86), click OK, and then click Next.



Imaging Wyse Thin Clients with Configuration Manager 15

6. After the wizard completes the process, click Close. The ISO file is created in the location you entered for the ISO in step 3.

7. Copy the ISO contents to the USB pen drive you prepared in "Step 1: Format a USB Pen Drive." If a USB drive is not available, the ISO can be burned to a CD/DVD.

Step 4: Prepare the Reference Thin Client for Image Capture

TipTo prepare a reference Wyse Enhanced WES7 image, it is recommended to start with a newly imaged thin client, make any customizations to the build you want, and then make the build ready for Configuration Manager image capture.

1. Be sure the thin client you want to use as a reference thin client is running the image you want.

2. Boot the thin client. For security the thin client will automatically log on using the User account.

3. Log off and log on as an Administrator. Use the Log off button (Start > Log off) to log off the current desktop while holding down the SHIFT key until the Log On window displays. Log on as an administrator (default Username is administrator and default case-sensitive Password is Wyse#123).

4. Disable the File-Based Write Filter by double-clicking the FBWF Disable (red) icon on the desktop (this will disable the File-Based Write Filter and reboot the system).

5. If automatic logon to a user desktop is enabled, you must log off the user desktop and log on as an administrator (as you did in step 3). IMPORTANT: At this time, also be sure the boot order in the BIOS is HDD followed by PXE LAN.

6. Un-join the client from domain and reboot the client. Log on as a local administrator.

7. Make any customizations you want (drivers, etc.).

8. Download the CCMDelCert.exe tool and copy it to the reference thin client C:\windows\setup. This file is required to delete any certificates if they are present from the Configuration Manager reference build. NOTE: The Ccmdelcert.exe tool is part of the SMS 2003 Toolkit 2. Download SMS 2003 Toolkit 2 from Microsoft Web site at http://www.microsoft.com/download/en/details.aspx?id=18153.

9. Run C:\windows\setup\WES7_SCCM_Capture.bat. The WES7_SCCM_Capture.bat will run and reboot the client automatically. Some general activities it will do includes:• Stopping the netxclean (clientcleanup) service and making the startup type manual• Stopping the HAgent service and making the startup type manual• Disabling flash.sys.• Removing Wyse RAM disk Z: • Making the OS partition active• Setting to Administrator Autologon • Putting the C:\windows\setup\WES7_SCCM_AdminRunonce.bat in the

Administrator run once registry key

IMPORTANT: The WES7_SCCM_Capture.bat file is part of the Wyse WES7 WFR3 build. In cases of older builds, the file will not exist and you must download Configuration Manager supported WES7_Sysprep4man scripts from Wyse Web site and copy them to C:\windows\setup.

http://www.microsoft.com/download/en/details.aspx?id=18153

16 Chapter 5

After reboot the thin client will automatically log on as the local administrator and the WES7_SCCM_AdminRunonce.bat script will run and close. Some general activities it will do includes:• Stopping the SMS agent host and EDM write filter service agent service.• Deleting Configuration Manager related certificates and the Configuration Manager

configuration file. • Starting the IIS admin service.• Starting the SMS agent host service.• Putting the C:\windows\setup\AdminSCCM.bat in the Administrator run once

registry key - NOTE that the AdminSCCM.bat will run on the destination thin client once image deployment is complete. This batch file will revert back all the settings made in this step 9.

10.Open the services.msc and ensure that the SMS Agent Host service is started. If it is not started, start the service.

11.Go to the C:\windows\setup folder and ensure that CCMdelcert.exe is deleted. If not, delete it manually as it must not be used as part of Wyse builds due to redistribution license restrictions.

12.Now the image is Configuration Manager clone ready. CAUTION: Do not restart the thin client at this time. Otherwise, all Configuration Manager related customizations will be reverted back.

Step 5: Use Configuration Manager to Capture the Image from the Reference Thin Client

1. Attach the prepared USB pen drive or CD/DVD (with the captured media that you prepared in "Step 3: Use Configuration Manager to Create a Capture Media USB Pen Drive or CD/DVD that will Capture the Operating System Image") to the reference thin client.

2. Go to the USB pen drive or CD/DVD drive, for example drive D:, and launch the TSMBAutoRun.exe file (for example, D:\SMS\Bin\i386\TSMBAutoRun.exe).

3. On the Welcome to the Image Capture Wizard page, click Next.

4. On the Image Destination page, enter either the remote network shared location (recommended) or the local USB drive path along with the .wim file name extension, and then click Next.

5. On the Image Information page, click Next.

6. On the Summary page, click Finish. It will take five to ten minutes for the image capture wizard to start the capture process. During the capture process, the machine will be syspreped and restarted in WINPE. In the WINPE session, the machine will be captured, and after successful capture, the .wim file is generated and stored. NOTE: Once the image is captured, the reference thin client will not be in the same state as it was before the capture because of sysprep. To bring the reference thin client back to its original state, join the reference thin client to the domain and deploy the OS as mentioned in "Phase 3: Deploying the OS Image to the Destination Client Using the Operating Systems Deployment (OSD) Task Sequence."


Phase 2: Importing the Captured OS Image (WIM File) into the Configuration Manager Server

1. In the Configuration Manager console, open the Add Operating System Image Wizard (select Site Database > Computer Management > Operating System Deployment > Operating System Images, right-click Operating System Images, and then select Add Operating System Image).

2. On the Data Source page, type the network path (UNC format) of the captured wim file, and then click Next. IMPORTANT: If the captured wim file is located on a USB pen drive or CD/DVD drive, then first copy the file to a shared location accessible by the Configuration Manager server.

3. On the General page, specify the Name as Reference WES7, specify the Version as 1.0, and then click Next.


5. After the wizard is completed, click Close. The new image you imported should appear under the Operating System Images node in the Configuration Manager console.

6. Open the New Distribution Points Wizard for the newly imported image (select the newly imported image, right-click Distribution Points, and then select New > Distribution Points), and then click Next.

7. On the Copy Package page, select the Non-PXE point server you want to designate as the distribution point, and then click Next.

8. After the wizard is completed, click Close. The Non-PXE point server you selected should appear under the Distribution Points node of the added image in the Configuration Manager console. The package should be copied to all Distribution Points, except the PXE point.

18 Chapter 5

Phase 3: Deploying the OS Image to the Destination Client Using the Operating Systems Deployment (OSD) Task Sequence

TipThis section assumes that the destination thin client is already associated with (discovered by) the Configuration Manager server. For fully automated pushes of WES7 images, only the Non-PXE method of image pushing is supported. If the task sequence is advertised for a PXE method, then the OS will not boot to PXE (this is because the BIOS boot order in WES7 is HDD followed by PXE”). IMPORTANT: Be sure the boot order in the BIOS is HDD followed by PXE LAN.

Step 1: Add a Distribution Point to the Boot Image (x86) Package

1. In the Configuration Manager console, open the New Distribution Points Wizard (select Site Database > Computer Management > Operating System Deployment > Boot Images > Boot Image (x86) > Distribution Points, right-click Distribution Points, and then select New Distribution Points), and then click Next.

2. On the Copy Package page, select both the PXE point and Non-PXE point servers you want to designate as the distribution points, and then click Next.

3. After the wizard is completed, click Close. The two distribution points should appear under the Distribution Point node of the Boot Image (x86) package.

Step 2: Create a Configuration Manager Client Agent Software Package

1. In the Configuration Manager console, open the Create Package from Definition Wizard (select Site Database > Computer Management > Software Distribution > Packages, right-click Packages, and then select New > Package from Definition), and then click Next.

2. On the Package Definition page, do the following:• For publisher, select Microsoft.• For package distribution, select Configuration Manager Client Upgrade.

3. Click Next.

4. On the Source Files page, select the Always obtain files from source directory option, and then click Next.

5. On the Source Directory page, do the following:• For source directory location, select the local drive on the site server.• Provide the path where the configuration manager source files are located for the

source directory (for example, C:\ Program Files\Microsoft Configuration Manager\Client).

6. Click Next.


8. After the wizard is completed, click Close. The Configuration Manager Client Upgrade package should appear under the Packages node in the Configuration Manager console.

9. Open the New Distribution Points Wizard for the Configuration Manager Client Upgrade package (select the Configuration Manager Client Upgrade image, right-click Distribution Points, and then select New > Distribution Points), and then click Next.


10.On the Copy Package page, select the Non-PXE point server you want to designate as the distribution point, and then click Next.

11.After the wizard is completed, click Close. The Non-PXE point server you selected should appear under the Distribution Points node of the added image in the Configuration Manager console. The package should be copied to all Distribution Points, except the PXE point.

Step 3: Create a Software Package for Administrator AutoLogon

TipThis package creation is required to automatically logon as a local administrator after image deployment, to create a local administrator profile, and to proceed with further Wyse scripts to run and make the thin client ready for use.

1. Copy C:\windows\setup\sysprep.xml file (which is present on the Wyse thin client) to \\SCCM-server\share-folder (which is on the Configuration Manager server) and rename it to unattend.xml. This unattend.xml file must be accessible by the Configuration Manager server and all WES7 systems.


3. On the General page, name the package AutoAdminLogonXml, enter any other information you need, and then click Next.

4. On the Data Source page, select the This package contains source files option, click Set, select the path where unattend.xml is present for the Source Directory, select the Always obtain source files from the source directory option, and then click Next.






10.After the wizard is completed, click Close. The AutoAdminLogonXml package should appear under the Packages node of the Site database tree in the Configuration Manager console.

Step 4: Add Distribution Points to the AutoAdminLogonXml Software Package

1. Under the Packages node, select the AutoAdminLogonXml package to expand it.



4. After the wizard is completed, click Close. The distribution point should appear under the Distribution Point node of the respective package.

5. Under the Packages node, select the AutoAdminLogonXml package to expand it.


20 Chapter 5

Step 5: Create a Software Package that Prepares the Thin Client for Image Push

1. A batch file containing the steps to prepare the client for image push must be created. Name the batch file Configure_WES7Client.bat. The contents of the batch file includes:

SC Stop HAgent WSleep 5 SC Config HAgent start= demand Call “C:\windows\setup\W7-OSActive.exe” WSleep 5

You can now create a software package named Prep WES7 Client for the Configure_WES7Client.bat file as follows.


3. On the General page, name the package Prep WES7 Client, enter any other information you need, and then click Next.

4. On the Data Source page, select the This package contains source files option, click Set, select the path where Prep WES7 Client is present for the Source Directory, select the Always obtain source files from the source directory option, and then click Next.






10.After the wizard is completed, click Close. The Prep WES7 Client package should appear under the Packages node of the Site database tree in the Configuration Manager console.

Step 6: Create a Program for the Prep WES7 Client Package

1. Under the Packages node, select the Prep WES7 Client package to expand it.


3. On the General page, enter any program details you need, enter the program name, for example: WES7 Client, click Browse, set files of type to All Files (*.*), select the application installer file (in our example case: Configure_WES7Client.bat), click Open, type the silent installer option -ms (in our example case: “Configure_WES7Client.bat” -ms) for installing silently. NOTE: The silent installation option varies for different applications.








10.After the wizard is completed, click Close. The program should appear under the Program node of the Prep WES7 Client package.

Step 7: Add Distribution Points to the Prep WES7 Client Software Package




4. After the wizard is completed, click Close. The distribution points should appear under the Distribution Point node of the Prep WES7 Client package.



Step 8: Create a Push WES7 Image Task Sequence for Image Push

1. In the Configuration Manager console, open the New Task Sequence Wizard (select Site Database > Computer Management > Operating System Deployment > Task Sequences, right-click Task Sequences, and then select New > Task Sequence).

2. On the Create New Task Sequence page, select the Install an Existing Image Package option, and then click Next.

3. On the Task Sequence Information page, name the task sequence, for example: Push WES7 Image, and then click Next.

4. On the Boot Image page, click Browse, select Boot Image (x86), click OK, and then click Next.

5. On the Install Windows page, do the following:• Select the Reference WES7 image (WIM file) package you imported in "Phase 2:

Importing the Captured OS Image (WIM File) into the Configuration Manager Server."

• Select the Always Use the Same Administrator Password option, enter Wyse#123 for the password (case sensitive).

6. Click Next.

7. On the Configure Network page, select the Join a Workgroup option, type WORKGROUP for the Name, (Optional: If the thin client needs to be joined to the domain, then you can also select Join a Domain, browse for the domain, and then enter the account that has permission to join a thin client to a domain), and then click Next.

8. On the Install ConfigMgr page, do the following:• Select the Configuration Manager Client Upgrade package you created in "Step

2: Create a Configuration Manager Client Agent Software Package."• Type SMSMP=<Configuration Manager servername> in the Installation

Properties box (where <Configuration Manager servername> is the server name you want).

9. Click Next.

22 Chapter 5

10.On the State Migration page, clear (uncheck) all options, and then click Next.

11.On the Include Updates page, click Next.

12.On the Install Software page, click Next.


14.After the wizard is completed, click Close. The new task sequence with the name you assigned (for example: Push WES7 Image) should appear on the Task Sequences page.

15.Right-click the new task sequence (in our example case: Push WES7 Image) and select Edit to open the Task Sequence Editor window for Push WES7 Image.

16.Click Add > New Group. A New Group task is added. Move the New Group task to be the first in the list of tasks. Rename the New Group to Configure Client.

17.Add a Disable File-Based Write Filter task by clicking Add > Write Filter > Disable Write Filter. The Disable File-Based Write Filter task is added to the Configure Client group in the task editor.

18.Add a prepare client task by clicking Add > General > Install Software. The Install Software task is added to the Configure Client group in the task editor. Change the Install Software name to Prepare Client, click Browse, select the software package created for preparing the client for image push in "Step 5: Create a Software Package that Prepares the Thin Client for Image Push" (Prep WES7 Client), click OK, and then click Apply.

19.Select Install Operating System - Partition Disk. On the Options tab select Disable this Step, and then click Apply.

20.Select Install Operating System - Apply Operating System. On the Properties tab, do the following: • For the Apply operating system from a captured image option, ensure the value

for the image selected is 2-2.• Select the Use unattended or sysprep answer file for a custom installation

option, click Browse and select the AutoAdminLogonXml software package you created in "Step 3: Create a Software Package for Administrator AutoLogon."

• Enter unattend.xml for the Filename.• In the Select the location where you want to apply this operating system section,

select Specific disk and partition for Destination. Enter 0 for Disk and 2 for Partition.

• Click Apply.

TipThis step is required to maintain the original Wyse build structure and prevents the whole Disk from being formatted (therefore preserving WYSE partitions).

21.Select Install Operating System - Apply Data Image 1. On the Options tab select Disable this Step, and then click Apply.

22.Select Install Operating System - Setup Windows and ConfigMgr. On the Options tab select Disable this Step, and then click Apply.

23.Select OK to close the Task Sequence Editor window for the task sequence (in our example, the Push WES7 Image task sequence).


Step 9: Advertise the Push WES7 Image Task Sequence for Image Push

1. In the Configuration Manager console, expand Task Sequences (select Site Database > Computer Management > Operating System Deployment, and expand Task Sequences).

2. Right-click the new task sequence (in our example case: Push WES7 Image) and select Advertise to open the Advertisement Wizard.

3. On the General page, enter a name for the advertisement, for example: Deploying Reference WES7, and do the following:• For collection selection, click Browse, select the collection select the collection (for

example, Wyse Z-Class devices), and then click OK.

4. Click Next.


6. Click Next.

7. On the Distribution Points page, select the Access Content Directly from a Distribution Point When Needed by Running the Task Sequence option, select any other options you want, and then click Next.




11.On the Confirmation page, click Close to close the wizard. If the destination thin client already has a Configuration Manager agent installed, an advertisement will appear. Click Run Advertisement. The task sequence will run and the thin client will reboot. IMPORTANT: Be sure the boot order in the BIOS is HDD followed by PXE LAN. During the image deploy process, the machine will restart in WINPE and deploy the WES7 reference image. After successful deployment, the thin client will automatically log on using the local administrator account and the Wyse scripts will run automatically to enable the File-Based Write Filter and reboot the thin client. Now the destination client is ready for use.

24 Chapter 5


6 Windows Security Update DeploymentThis section provides the procedures you can use to configure Microsoft® Windows Server Update Services (WSUS) according to your needs (when deploying WSUS in your Wyse thin client environment running Wyse Enhanced WES7). After your configurations are complete, be sure Software Update Point Role is installed on your Configuration Manager server.

TipIf you need additional assistance beyond the scope of the information contained in this section, see your Configuration Manager installation and setup documentation.

This section includes general procedures and information on the following:• "Creating Common Search Folders"• "Creating a New Search Folder for a Specific Year"• "Creating a New Search Folder for New Monthly Releases"• "Case Example: Downloading and Installing Security Updates"

Creating Common Search FoldersAfter installation, the first thing you must do is create search folders. You can create search folders at your central site to make it easier for administrator site usage. If you need to create a report by year, you can simply use one of the searches you have already created and modify it as you require. You can also create a search folder that will only show the current month's patches. In addition, all of the search folders that you create can include only the patches that have not been superseded or expired.

NOTE: If you are completing these procedures on a new site, you can create a new folder to categorize your searches.

TipThere are many searches you can create. You can modify the search criteria until you configure what you want. For example, you can search by hot fix, Article ID, or even driver.

26 Chapter 6

Creating a New Search Folder for a Specific Year1. Right-click the folder that you created under Search Folders and select New Search

Folder.

2. Select object properties to search, select the following:• Bulletin ID• Expired• Superseded• Product

3. Edit the property's search criteria:• Bulletin ID - Set to MS1{year}

For example: MS12• Expired - Set to No.• Superseded - Set to No.• Product - Set to Windows Embedded Standard 7.

4. Specify search option, select/check Search all folders under this feature.

5. Enter a name for the search folder. For example: 2012 Updates.

6. Click OK.

Creating a New Search Folder for New Monthly Releases1. Right-click the folder that you created under Search Folders and select New Search

Folder.

2. Specify search option, select/check Search all folders under this feature. Select object properties to search and select the following:• Bulletin ID• Date Released• Date Revised• Expired• Superseded• Product

3. Edit the property's search criteria:• Bulletin ID - Set to MS.• Date Released - Set to Last 1 Month.• Expired - Set to No.• Superseded - Set to No.• Product - Set to Windows Embedded Standard 7.

4. Specify search option, select/check Search all folders under this feature.

5. Enter a name for the search folder, For example: Windows Embedded Standard 7 Monthly Updates.

6. Click OK.

Windows Security Update Deployment 27

Case Example: Downloading and Installing Security UpdatesWhile many different scenarios can exist when deploying software updates, you can use this case example as a starting point to understand how you can deploy security updates to your thin clients. Once you are familiar with the process and requirements, you can modify this case example as needed for your requirements.

In this case example, we will:• Use a Software Updates Deployment Package named All Windows Embedded

Standard 7 Updates to store the updates we want (these are the updates that are made available to Windows WES7 machines in the environment).

• Create a new Deployment Management Task to deploy the new updates.• Clean up any previous Deployment Management Tasks by removing/deleting any

expired updates referenced in the software package (All Windows Embedded Standard 7 Updates).

Step 1: Run Synchronization

1. Expand your Software Updates node in your Configuration Manager.

2. Right-click Update Repository, select Run Synchronization, and then click Yes.

3. You can verify that the synchronization process has completed in the Site Status > Component Status > SMS_WSUS_SYNC_MANAGER log. Look for Message ID 6702 stating: SMS WSUS Synchronization Done.

Step 2: Select the New Updates Using the Search Folder

1. Select a search folder that contains the patches you want to apply. For example, if you select a folder named Windows Embedded Standard 7 Patches, you will see the list of patches available in that folder (on the right).

2. Right-click the search folder (in our example, the folder named Windows Embedded Standard 7 Patches), and then select Download Software Updates to open the Deployment Package dialog box.

3. Click Create a New Deployment Package, enter the name All Approved Microsoft Patches, (Optional) enter a description if desired, enter the package source (for example: \\Servername\Share) making sure that the share security is set to full control for everyone so that Configuration Manager can publish the patches to the server (otherwise the download will fail), select the Enable Binary Differential Replication option (this option will allow you to update this package next month with the newest patches and will help save bandwidth when updating the Distribution Points), and then click Next.

4. Click Browse, browse to and select your Distribution Point, and then click Next to open the Distribution Settings dialog box.

5. Set the priority and click Next.

6. Select Download Software Updates from the Internet and click Next.

7. Select the languages that you want to be downloaded, and then click Next to open the Summary page.

8. Click Next to start the process (you will see a progress page until all patches are downloaded).

9. When the process is complete and a Confirmation page appears, click Finished.

10., After the success message, you can browse to the package source folder (in our example, \\Servername\Share) and verify the selected updates have been downloaded.

28 Chapter 6

Step 3: Creating a Software Package for the Downloaded Updates


2. On the General page, name the package, for example: Downloaded Updates, enter any other information you need, and then click Next.

3. On the Data Source page, select the This package contains source files option, click Set, select the path for the Source Directory where the application installer is present (for example, C:\\Servername\Share), select the Always obtain source files from the source directory option, check the Enable binary differential replication check box, and then click Next. IMPORTANT: The path/folder selected should contain the artifacts that will be required by the package.






9. After the wizard is completed, click Close. The package should appear under the Packages node of the Site database tree in the Configuration Manager console.

Step 4: Create a Program for the Package

1. Under the Packages node, select the Downloaded Updates package to expand it.


3. On the General page, enter any program details you need, enter the program name (for example: Updates), click Browse, set files of type to All Files (*.*), select the application installer file (in our example case: updates.cab), click Open, type the silent installer option “Dism.exe /online /add-package /packagepath:\\Servername\share\updates.cab /Quiet /NoRestart” for installing silently. NOTE: The silent installation option varies for different applications.







10.After the wizard is completed, click Close. The program should appear under the Program node of the respective package.

Windows Security Update Deployment 29

Step 5: Add a Distribution Point to the Software Package




4. After the wizard is completed, click Close. The distribution points should appear under the Distribution Point node of the respective package.



Step 6: Use Device Manager to Advertise the Software Package

TipIn this step you will use Device Manager (instead of a Configuration Manager task sequence) to Advertise the software package. This will automatically perform the File-Based Write Filter disabling and enabling that is required when deploying software packages.

1. In the Configuration Manager console, open the New Advertisement Wizard (select Site Database > Computer Management > Embedded Device Management > Write Filter Servicing > Advertisements with Write Filter Handling, right-click Advertisements with Write Filter Handling, and then select New).

2. On the Getting Started page, select the I understand that the devices option and the Package supports unattended installation option, and then click Next.

3. On the General page, enter the name for the advertisement, for example: Deploying Downloaded Updates, and do the following:• For package selection, click Browse, select the Downloaded Updates package you

created, and then click OK.• For collection selection, click Browse, select the collection (for example, Wyse

Z-Class devices), and then click OK.

4. Click Next.


6. Click Next.

7. On the Distribution Points page, click Next.




30 Chapter 6

11.Click Close. The advertisement with the name you assigned should appear on the Advertisements with Write Filter Handling page.





A Localization Requirements: Multilingual User Interface (MUI)When planning for Multilingual User Interface Deployments for WES7, be aware that Wyse Enhanced WES7 WFR3 builds support English only. After pushing MUI WDM add-ons to Standard English builds, the built-in Administrator account name and other language specific information (such as input locale, system locale, time zone, and so on) will be changed based on the respective languages. Configuration Manager-related Control Panel applets will not be changed and will remain in English. Therefore, the following files must be edited on the noted machines (reference thin client and Configuration Manager server) before image capture and deployment.• C:\windows\setup\Powershell_Wordpad.vbs - This file must be edited with the

appropriate local administrator account name on the reference thin client before image capture. For example: For the French language, replace Administrator with Administrateur.

• C:\windows\setup\ fbwf_shortcut.vbs - This file must be edited with the appropriate local administrator account name on the reference thin client before image capture. For example: For the French language, replace Administrator with Administrateur.

• C:\windows\setup\ sysprep.xml - This file must be copied to the Configuration Manager server before image capture, it must be renamed to unattend.xml, and it must be edited for language specific changes to create software packages for Administrator Autologon as described in "Step 3: Create a Software Package for Administrator AutoLogon." For example: For the French language, replace Administrator with Administrateur.

TipYou can use the contents of "Contents of the sysprep.xml File" for convenience.

32 Appendix A

Contents of the sysprep.xml File

CautionDuring MUI image deployment on MUI converted WES7 builds, be sure that server time zone and time match with the time zone and time of the thin client device.

Contents include the following:

<?xml version="1.0" encoding="utf-8"?>

<unattend xmlns="urn:schemas-microsoft-com:unattend" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:ew="urn:schemas-microsoft-com:embedded.unattend.internal.v1">

<servicing>

<package action="configure">

<assemblyIdentity name="Microsoft-Windows-EmbeddedEdition" version="6.1.7601.17514" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" />

<ew:packageInfo releaseType="Product" customInfoVersion="1.0" />

</package>

</servicing>

<settings pass="generalize">

<component name="Microsoft-Windows-PnpSysprep" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">

<PersistAllDeviceInstalls>true</PersistAllDeviceInstalls>

<DoNotCleanUpNonPresentDevices>true</DoNotCleanUpNonPresentDevices>

</component>

<component name="Microsoft-Windows-Security-SPP" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">

<SkipRearm>1</SkipRearm>

</component>

</settings>

<settings pass="specialize">

<component name="Microsoft-Windows-Deployment" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">

<RunSynchronous>

<RunSynchronousCommand wcm:action="add">

<Order>1</Order>

<Path>net user administrator/active:yes</Path>

</RunSynchronousCommand>

Localization Requirements: Multilingual User Interface (MUI) 33

</RunSynchronous>

</component>

<component name="Microsoft-Windows-Shell-Setup" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">

<ComputerName>*</ComputerName>

<ShowWindowsLive>false</ShowWindowsLive>

<RegisteredOrganization>Microsoft</RegisteredOrganization>

<DisableAutoDaylightTimeSet>false</DisableAutoDaylightTimeSet>

<TimeZone>GMT Standard Time/<TimeZone>

</component>

</settings>

<settings pass="oobeSystem">

<component name="Microsoft-Windows-Embedded-Core-Settings" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">

<HideEvaluationWarning>1</HideEvaluationWarning>

</component>

<component name="Microsoft-Windows-International-Core" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">

<InputLocale>en-us/<InputLocale>

<SystemLocale>en-us/<SystemLocale>

<UILanguage>en-us/<UILanguage>

<UserLocale>en-us/<UserLocale>

</component>

<component name="Microsoft-Windows-Shell-Setup" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">

<AutoLogon>

<Password>

<Value>VwB5AHMAZQAjADEAMgAzAFAAYQBzAHMAdwBvAHIAZAA=</Value>

<PlainText>false</PlainText>

</Password>

<Enabled>true</Enabled>

<Username>Administrator</Username>

34 Appendix A

<LogonCount>5</LogonCount>

</AutoLogon>

<OOBE>

<NetworkLocation>Work</NetworkLocation>

<HideWirelessSetupInOOBE>true</HideWirelessSetupInOOBE>

<ProtectYourPC>1</ProtectYourPC>

<HideEULAPage>true</HideEULAPage>

</OOBE>

<UserAccounts>

<AdministratorPassword>

<Value>VwB5AHMAZQAjADEAMgAzAEEAZABtAGkAbgBpAHMAdAByAGEAdABvAHIAUABhAHMAcwB3AG8AcgBkAA==</Value>


</AdministratorPassword>

<LocalAccounts>

<LocalAccount wcm:action="add">

<Password>

<Value>VwB5AHMAZQAjADEAMgAzAFAAYQBzAHMAdwBvAHIAZAA=</Value>


</Password>

<Name>User</Name>

<DisplayName>User</DisplayName>

<Description>Default User</Description>

<Group>Administrators/<Group>

</LocalAccount>

</LocalAccounts>

</UserAccounts>

<RegisteredOrganization>Wyse Technology</RegisteredOrganization>

<RegisteredOwner>Admin</RegisteredOwner>

</component>

</settings>

<ew:answerFileInfo distributionSharePath="C:\Program Files\Windows Embedded Standard 7\DSSP1" footprint="576716800" ecoreFootprint="576716800" />

</unattend>

B Troubleshooting and Reference InformationThis appendix includes:• "Troubleshooting Tools"• "Microsoft Reference Documents"• "Configuration Manager-Device Manager Script Details"

Troubleshooting Tools• Systems Management Server 2003 Toolkit 2 (SMS 2003 Toolkit 2) - Contains

various tools to help with deployment and general troubleshooting.• SMS Trace Tool - Part of the SMS 2003 Toolkit 2 to view log files and trace errors.

Microsoft Reference Documents• Configuration Manager 2007 Features - See

http://technet.microsoft.com/en-us/library/bb680550.aspx.• Operating System Deployment in Configuration Manager - See

http://technet.microsoft.com/en-us/library/bb632767.aspx.• Tasks for Managing Configuration Manager Clients on Windows Embedded

Devices - See http://technet.microsoft.com/en-us/library/bb932159.aspx.• Software Distribution in Configuration Manager - See

http://technet.microsoft.com/en-us/library/bb632640.aspx.• Windows Embedded Device Manager 2011 - See

http://www.microsoft.com/windowsembedded/en-us/evaluate/windows-embedded-device-manager.aspx.

http://technet.microsoft.com/en-us/library/bb680550.aspx




http://www.microsoft.com/windowsembedded/en-us/evaluate/windows-embedded-device-manager.aspx

http://www.microsoft.com/windowsembedded/en-us/evaluate/windows-embedded-device-manager.aspx

36 Appendix B

Configuration Manager-Device Manager Script DetailsUse the script details in the following table when customizing the scripts for your various needs (for example, localization requirements).IMPORTANT: All of the files listed in the table are part of the WES7 WFR3 image and are located in the C:\windows\setup folder. For legacy WES7 builds, use the sysprep4man.zip that contains these files. For more details on how to use sysprep4man, refer to the Readme.txt of the sysprep4man.zip.

The descriptions in the table address the following issues:• Usage: When is it involved - boot, image capture, deployment, post-deployment,

configuration, etc.• What it Does: Stop, start, disable, remove, etc.• How to Use: How to use it with Configuration Manager-Device Manager task

sequences, etc.• Customization Options: If applicable.• Limitations: If any or if applicable.

Item Description

Image: C:\windows\setup\WES7_SCCM_Capture.bat

1. Usage: During image capture.2. What it Does:

a. Stops netxclean (clientcleanup) service and sets startup type to manual.

b. Stops Hagent service and sets startup type to manual.

c. Disables flash.sys.d. Removes Wyse RAM disk Z:.e. Sets OS partition to active.f. Sets logon to Administrator Autologon.g. Places the

"C:\windows\setup\WES7_SCCM_AdminRunonce.bat" in the Administrator run once registry key.

NOTE: All the above requirements are required for Wyse WES7 builds only.3. How to Use: See "Step 4: Prepare the Reference Thin

Client for Image Capture."4. Customization Options: None.5. Limitations: Must be executed manually.

Image: C:\windows\setup\WES7_SCCM_AdminRunonce.bat

1. Usage: During image capture.2. What it Does:

a. Stops SMS agent host and EDM write filter service.b. Deletes Configuration Manager related certificates

and Configuration Manager configuration file.c. Starts IIS admin service.d. Starts SMS agent host service.e. Places the "C:\windows\setup\ AdminSCCM.bat" in

the Administrator run once registry key.NOTE: All the above requirements except point e) are required for any WES7 builds. Point e) is also required (in addition to the other points) for Wyse WES7 builds only.3. How to Use: No Configuration required as it is

automatically triggered by Administrator Run once registry.

4. Customization Options: None5. Limitations: None.

Troubleshooting and Reference Information 37

Image: C:\windows\setup\ AdminSCCM.bat

1. Usage: During image deployment.2. What it Does:

a. Sets startup type of netxclean (clientcleanup) service to automatic.

b. Sets startup type of Hagent service to automatic.c. Enables flash.sys.d. Enables Wyse RAM disk Z:.e. Applies Administrator profile specific settings and

registries which were deleted during sysprep.f. Applies some of the machine specific registries

which were deleted during Configuration Manager image capture.

g. Sets User Autologon and removes it from administrator group.

h. Repairs SMS task sequences which were corrupted during Configuration Manager image deployment.

i. Enables File-Based Write Filter.NOTE: Requirements f, g, h, i are required for any WES7 build and remaining points a through e are also required (in addition to the other points) for Wyse WES7 builds.3. How to Use: No configuration required as it is

automatically triggered by Administrator Runonce registry

4. Customization options: None5. Limitations: None.

Image: C:\windows\setup\sysprep.xml

1. Usage: During Image Deployment2. What it Does:

a. Enables the built-in Local administrator account which was disabled by sysprep during image capture.

b. Sets built-in Local Administrator account to Autologon so that it re-creates the administrator profile which was deleted by sysprep during image capture.

NOTE: Requirements a and b are required for any WES7 build where the local administrator account is required.3. How to Use: See "Step 3: Create a Software Package

for Administrator AutoLogon" and "Step 8: Create a Push WES7 Image Task Sequence for Image Push."

4. Customization options: This file must be renamed to unattend.xml before following "Step 3: Create a Software Package for Administrator AutoLogon."

5. Limitations: Must be renamed manually to unattend.xml.

Item Description

Administrators Guide Managing Wyse® Thin Clients with Microsoft® System Center Configuration Manager 2007 and Embedded Device Manager 2011 Issue: 013012

Written and published by: Wyse Technology Inc., January 2012

Created using FrameMaker® and Acrobat®

Date post:	06-Mar-2018
Category:	Documents
Upload:	dangdieu
View:	222 times
Download:	1 times