Technical white paper

Managing HP Thin Clients with

SCCM 2012 SP1
Table of contents
Executive summary ...................................................................................................................................................................... 3
Feature overview ........................................................................................................................................................................... 3
Configuration .................................................................................................................................................................................. 3
Server requirements ................................................................................................................................................................ 3
Client requirements .................................................................................................................................................................. 3
Additional reading ..................................................................................................................................................................... 3
Inventory in Configuration Manager .......................................................................................................................................... 3
Hardware inventory in Configuration Manager .................................................................................................................. 4
Software inventory in Configuration Manager.................................................................................................................... 4
Asset Intelligence in Configuration Manager ...................................................................................................................... 4
Upgrading the Configuration Manager client on WES devices ............................................................................................ 4
Distributing applications to WES devices ................................................................................................................................. 4
Imaging with SCCM 2012 SP1..................................................................................................................................................... 4
Capturing an operating system image ................................................................................................................................. 5
Creating a driver package for imaging ............................................................................................................................. 5
Creating a capture media task sequence......................................................................................................................... 5
Capturing a WES7 image from a reference system ...................................................................................................... 5
Deploying an operating system image through OSD........................................................................................................ 6
Importing a captured WES7 reference image into SCCM ............................................................................................. 6
Syncing the Configuration Manager client package to the Destination Point ......................................................... 6
Syncing the User State Migration Tool (USMT) package to Distribution Point (optional)...................................... 6
Creating a task sequence to deploy a WES7 reference image ................................................................................... 6
Deploying a WES7 reference image.................................................................................................................................. 7
Post deployment tasks ........................................................................................................................................................ 8
Imaging with the Microsoft Deployment Toolkit (MDT) 2012 and SCCM 2012 SP1 ....................................................... 8
Installing and integrating the MDT 2012 with the SCCM .................................................................................................. 8
Deploying an operating system through MDT .................................................................................................................... 9
Creating a driver package for imaging ............................................................................................................................. 9
Importing a captured WES7 reference image into SCCM ............................................................................................. 9
Preparing a Configuration Manager client package in SCCM ....................................................................................... 9
Preparing a USMT package in SCCM .................................................................................................................................. 9
Creating an MDT task sequence in SCCM ......................................................................................................................... 9
 Configuring Capture Image in the MDT task sequence ............................................................................................... 10
Deploying the MDT task sequence (including both Capture Image and Deploy Image) ..................................... 10
Appendix A .................................................................................................................................................................................... 11
Preparation for a task sequence with User State Migration .......................................................................................... 11
Appendix B .................................................................................................................................................................................... 11
Enabling the write filter in a Deployment task sequence .............................................................................................. 11

2
Executive summary
This document describes how to use Microsoft System Center 2012 Configuration Manager SP1 (SCCM) to manage HP thin
clients running Windows Embedded Standard 7 (WES7).

Feature overview
Asset Intelligence
SCCM Asset Intelligence gives organizations better control over their infrastructure by providing IT administrators with
continuous insight into what hardware and software assets they have, who is using them, and where they are.
Software Update Management
SCCM Software Update Management simplifies the delivery and management of updates to IT systems across the
enterprise. IT administrators can deliver updates of Microsoft products, third-party applications, custom in-house line-of-
business applications, hardware drivers, and system BIOS to a variety of devices.
Desired Configuration Management
SCCM Desired Configuration Management ensures that IT systems comply with the organizations desired configuration to
improve availability, security, and performance network wide.
Software Distribution
SCCM Software Distribution simplifies the distribution of applications and updates to desktops, servers, laptops, and mobile
devices across enterprise networks.
Operating System Deployment
SCCM Operating System Deployment is a highly flexible, automated solution that allows IT administrators to deploy and
configure servers and desktops from any previous state, including bare-metal deployments.

Configuration
Server requirements
Windows Server 2008 R2 SP1with Active Directory (AD), Dynamic Host Configuration Protocol (DHCP), Domain Name
System (DNS), Windows Deployment Services (WDS), Windows Server Update Services (WSUS), and Windows Assessment
and Deployment Kit (Windows ADK)
Microsoft SCCM 2012 SP1
Microsoft Development Toolkit 2012 (MDT can be used instead of OSD to deploy an image)
Microsoft SQL Server 2008 R2 SP1

Client requirements
HP t5740e, t5570e, t510, t610 with WES7E image version 6.1.7601.286 (or later)
HP t610 with WES7P image version 6.1.7601.2013.03.14 (or later)
HP mt40 with WES7 image version 6.1.7601.060.WES7eSP1
SCCM 2012 SP1 client preinstalled

Additional reading
For more information about Microsoft System Center 2012 Configuration Manager SP1, go to
http://technet.microsoft.com/en-us/library/gg682077.aspx.

Inventory in Configuration Manager

The SCCM Configuration Manager has many methods to inventory hardware and software. Use the hardware inventory to
find detailed information about the hardware of the client computers and mobile devices that are enrolled by the
Configuration Manager. Use the software inventory to find information about the software and files present on the client
computers. Asset Intelligence extends these inventory capabilities to help manage licenses for software in the enterprise.

3
 Hardware inventory in Configuration Manager
For more information about hardware inventory, go to http://technet.microsoft.com/en-us/library/gg682093.aspx.

Software inventory in Configuration Manager

For more information about software inventory, go to http://technet.microsoft.com/en-us/library/gg682126.aspx.

Asset Intelligence in Configuration Manager

For more information about asset intelligence, go to http://technet.microsoft.com/en-us/library/gg699382.aspx.

Upgrading the Configuration Manager client on WES devices

The following methods can be used to install the Configuration Manager client.
Client push installation
Software update point installation
Group Policy installation
Logon script installation
Manual installation
Upgrade installation by using application management
Automatic client upgrade
Client imaging
Make sure that the latest SCCM client (5.00.7804.1000) is installed before continuing. For more information, go to
http://technet.microsoft.com/en-us/library/gg682132.aspx#BKMK_DeployClientComputers.

Distributing applications to WES devices

SCCM Configuration Manager provides a set of tools and resources that can help you to create, manage, deploy, and monitor
applications in the enterprise.
For more information on how to create an application, go to http://technet.microsoft.com/en-us/library/gg682159.aspx.
For more information on how to deploy an application, go to http://technet.microsoft.com/en-us/library/gg682082.aspx.
For more information on how to create packages and programs, go to http://technet.microsoft.com/en-
us/library/gg682112.aspx.
For more information on how to deploy packages and programs, go to http://technet.microsoft.com/en-
us/library/gg682178.aspx.
When you deploy applications to a WES device with the write filter enabled, you can specify whether to disable the write
filter on the device during the deployment. Restart the device after the deployment. If the write filter is not disabled, the
software deploys to a temporary overlay and is not installed when the device restarts unless another deployment forces the
changes to persist.
The checkbox Commit changes at deadline or during a maintenance window (requires restarts) controls the write filter
behavior.

Imaging with SCCM 2012 SP1

Complete the deployment process first. Then, use one of the following methods to deploy the operating system to a
computer with the Configuration Manager client. For instructions, go to http://technet.microsoft.com/en-
us/library/gg682108.aspx#BKMK_Workflow.
PXE initiated deployments
Multicast deployments
Bootable Media Deployments
Stand-alone Media Deployments
Pre-staged Media deployments
For more information, go to http://technet.microsoft.com/en-us/library/gg682108.aspx#BKMK_OSDMethods.

4
Capturing an operating system image
Creating a driver package for imaging
1. Launch the Configuration Manger Console from Start > All Programs > Microsoft System Center 2012 >
Configuration Manager.
2. Navigate to Software Library. Select Overview from the left panel, then select Operating Systems. Right-click on
Drivers and select Import Driver to open the Import New Driver Wizard.
3. Specify the source folder of the driver and click Next.
4. Select the driver to import and click Next.
5. On the Add Driver to Packages screen, click New Package. Enter the package name and specify the network UNC
pathuse an empty folderin the Create Driver Package dialog. Click OK to close the Create Driver Package dialog
and then click Next.
6. Leave all the defaults on the Add Driver to Boot Images screen and click Next.
7. Click Next on the Summary screen.
8. Click Close when the wizard completes.
9. Navigate to System Center Configuration Manager > Software Library > Overview > Operating System > Driver
Packages. Right-click the driver package just added and select Distribute Content to open the Distribute Content
Wizard.
10. Click Next on the General screen.
11. Click Add and select Distribution Points to open the Add Distribution Points dialog.
12. Check available distribution points and click OK to close the Add Distribution Points dialog.
13. Click Next until the wizard finishes, and then click Close.
14. Refresh the Driver Packages and make sure that the content status is Success before proceeding.
15. Navigate to System Center Configuration Manager > Software Library > Overview > Operating Systems > Boot
Images. Right-click the appropriate boot image and choose Properties. Select the Drivers tab in the Properties dialog
and add the target driver. Click Apply and Yes to open the Update Distribution Points Wizard.
16. Click Next and Close the finish the wizard.
17. Click OK to close the Properties tab.
18. Refresh Boot Images and make sure that the content status is Success before proceeding.

Creating a capture media task sequence

1. Navigate to System Center Configuration Manager > Software Library > Overview > Operating Systems. Right-
click Task Sequences in the left panel and choose Create Task Sequence Media to open the Create Task Sequence
Media Wizard.
2. Select Capture Media and click Next.
3. Select the desired media type and specify the Drive (USB FLASH DRIVE type) or the path/name of the Media file
(CD/DVD SET type), and then click Next.
4. Select the appropriate boot image and Distribution Point, and then click Next. The boot image must include the NIC
driver of the target thin client.
5. On the Summary screen, click Next. The wizard creates the capture media or ISO.
6. Click Close when the wizard has completed.
7. Burn the ISO on media.

Capturing a WES7 image from a reference system

Local access to a client is required for the following procedure to capture a WES7 image.
1. Un-join the reference system from the domain if necessary.
2. Keep the Administrators password as the default value (known as Administrator).
3. Disable the Enhanced Write Filter (EWF) and restart.
4. Log on as Administrator and stop the Embedded Device Manager (EDM) write filter services using the Windows
services.msc.
5. For the task sequence to include User State Migration, make sure that the RAM disk on the source/destination image is
configured to have at least 250 MB of space to support USMT operations. For more information on the preparation to
use State Migration, see Appendix A.
6. Insert the media containing the ISO.

5
 7. If AutoRun does not launch, manually browse to <Task Sequence Capture Media>:\SMS\bin and launch
tsmbautorun.exe.
8. Follow the wizard. You can specify a network location for the WIM file, provided your WINPE boot image has network
connection capability (that is, an NIC driver installed).
9. Once complete, the wizard closes automatically. The system restarts to load WINPE and initiate capture within 25
minutes. If necessary, remove the capture media so the unit does not boot from it.

Deploying an operating system image through OSD

Importing a captured WES7 reference image into SCCM
1. Create a shared folder on the SCCM server: C:\OSDeploy\OSImages\WES7. Be sure to give all users access to
C:\OSDeploy.
2. Copy the captured reference WES7 WIM file to C:\OSDeploy\OSImages\WES7.
3. Navigate to System Center Configuration Manager > Software Library > Overview > Operating Systems. Right-
click Operating System Images and select Add Operating System Image.
4. The Add Operating System Image Wizard launches. Enter the network path (UNC): \\<Server
name>\OSDeploy\OSimages\WES7\<captured wim>.wim and click Next.
5. Click Next on the General page.
6. Click Next on the Summary page.
7. Click Close when the wizard completes.
8. Navigate to System Center Configuration Manager > Software Library > Overview > Operating Systems, and
select the newly added Operating System image.
9. Right-click on Distribute Content and click Next.
10. Add Distribution Point to Content Destination, select the available Destination Point, and then click Next.
11. Click Next on the Summary screen.
12. Click Close when the wizard completes.
13. Refresh the Operating System images and make sure that the content status is Success before proceeding.

Syncing the Configuration Manager client package to the Destination Point

1. Navigate to System Center Configuration Manager > Software Library > Overview > Application Management >
Package.
2. Right-click the Configuration Manager client package and select Distribute Content.
3. The Distribute Content Wizard starts. Click Next.
4. Add the Distribution Point to Content Destination, select the available Destination Point, and then click Next.
5. Click Next on the Summary page.
6. Click Close when the wizard completes.
7. Refresh the Package screen and make sure that the content status is Success before proceeding.

Syncing the User State Migration Tool (USMT) package to Distribution Point (optional)
1. Navigate to System Center Configuration Manager > Software Library > Overview > Application Management >
Packages.
2. Right-click the USMT package created by installing the Windows Assessment and Deployment Kit (ADK) and select
Distribute Content.
3. The Distribute Content Wizard starts. Click Next.
4. Add the Distribution Point to Content Destination, select the available Destination Point, and then click Next.
5. Click Next on the Summary page.
6. Click Close when the wizard completes.
7. Refresh the Package screen and make sure that the content status is Success before proceeding.

Creating a task sequence to deploy a WES7 reference image

1. Navigate to System Center Configuration Manager > Software Library > Overview > Operating Systems. Right-
click Task Sequence and select Create Task Sequence.
2. The New Task Sequence Wizard starts. Select Install an existing image package and click Next.
3. Enter the Task Sequence Name, select the appropriate boot image and click Next.
4. On the Install the Windows Operating System screen, browse to the previously created WES7 image package.

6
5. Before installing the operating system, select Partition and format the target computer. Deselect Configure task
sequence for use with BitLocker, unless your target device has a well-configured TPM module. Do not specify the
Product Key.
6. Select Enable the account and specify the local administrator password, and enter the password. Click Next.
7. Use the Configure the Network screen to set the preferred configuration, and click Next.
8. On the Install the Configuration Manager Client screen, click Browse and select Configuration Manager Client
Package. Click Next.
9. On the Configure State Migration screen, check the preferred settings and click Next. For the task sequence to
include User State Migration, make sure that the RAM disk on the source/destination image is configured to have at
least 250 MB of space to support USMT operations. For more information on the preparation to use State Migration,
see Appendix A.

Note:
Steps 18 and 19 are required if you select any settings on the Configure State Migration screen.

10. On the Include Software Updates screen, select Do not install any software updates and click Next.
11. Leave Install Applications empty and click Next.
12. Click Next on the Summary page.
13. Click Close when the wizard completes.
14. Browse to the newly created deployment task sequence. Right-click it and select Edit to open the Task Sequence
Editor.
15. Select Partition Disk 0. Double-click on (Primary) Volume to edit its properties.
16. The Partition Properties window opens. Under Use a percentage of remaining free space, enter 95.

Note:
The deployment will fail if this value is left at 100, because Windows will not be able to create the write filter partition.

17. Select Quick format under formatting options. Click OK to close the window.
18. Reopen the Task Sequence Editor. Click Request User State Storage in the group Restore User Files and Settings,
the check the option If computer account fails to connect to state store, use the Network Access account.
19. Click Restore User Files and Settings in the group Restore User Files and Settings, then check option Restore local
computer user profiles and input passwords. Click Apply and then OK to close the Task Sequence Editor.

Note:
Two more settings need to be changed for thin clients that do not have enough disk space to store both the
downloaded WIM and the extracted contents locally.
Select Apply Operating System in the Task Sequence Editor and open the Options tab. Check Access content
directly from the distribution point.
Right-click the reference image package in Operating System Images and open the Properties dialog. Configure the
Package share settings on the Data Access tab.

Deploying a WES7 reference image

1. Right-click on the new task sequence and select Deploy.
2. Choose the collection to deploy to. Click Next.
3. Choose Required in the Purpose field and make this task sequence available to Configuration Manager Clients,
media and PXE. Click Next.
4. Specify the preferred schedule for the deployment and click Next. For a PXE-initiated deployment, a mandatory
assignment schedule must be created.
5. Leave the default values on the User Experience screen and click Next.
6. Leave the default values on the Alert screen and click Next.

7
 7. On the Distribution Points screen, set the deployment option to Download content locally when needed by
running task sequence and check the option When no local distribution point is available, use a remote
distribution point. Click Next.
8. Click Next on the Summary page.
9. Click Close.

Note:
The write filter status is disabled by default after the task sequence finishes successfully.

Post deployment tasks

The deployed image might require more customization. For example, the write filter status, domain membership, and Auto
Logon are not set up.
These customizations are best handled by running command lines or scripts at first boot. For more information on enabling
the EWF and an example script, see Appendix B.

Note:
After the WES7P image is deployed, the system does not start automatically until the settings, such as time zone and
region, have been configured from the client side.

Imaging with the Microsoft Deployment Toolkit (MDT) 2012 and SCCM
2012 SP1
Installing and integrating the MDT 2012 with the SCCM
1. To download the MDT 2012 x64, go to http://www.microsoft.com/en-us/download/details.aspx?id=25175.
2. Install the package and be sure to keep the default settings.
3. After the installation completes, navigate to Start > All programs > Microsoft Deployment Toolkit. Click Configure
ConfigMgr Integration.
4. Select Install the MDT extensions for Configuration Manager and check both Install the MDT console extensions
for ConfigMgr 2012 and Add the MDT task sequence actions to a ConfigMgr server. Fill in the site server name and
site code. Click Next.

Note:
Make sure that the SCCM console is closed when configuring the Configure ConfigMgr Integration. The Configure
ConfigMgr Integration loads the SCCM information automatically if the SCCM Console has been launched before, so
that you do not have to fill in the site server name and site code manually.

5. Click Finish.
6. Launch the SCCM Console. Navigate to Software Library > Operating Systems, and right-click Task Sequences. Verify
that Create MDT Task Sequence is available.

8
Deploying an operating system through MDT
Creating a driver package for imaging
See Creating a driver package for imaging for details.

Importing a captured WES7 reference image into SCCM

See Importing a captured WES7 reference image into SCCM for details.

Preparing a Configuration Manager client package in SCCM

See Syncing the Configuration Manager client package to the Destination Point for details.

Preparing a USMT package in SCCM

See Syncing the User State Migration Tool (USMT) package to Distribution Point (optional) for details.

Creating an MDT task sequence in SCCM

1. Open the SCCM Console and nagivate to Software Library > Overview > Operating Systems > Task Sequences.
Right-click Task Sequences and select Create MDT Task Sequence.
2. Select Client Task Sequence on the Choose Template screen. Click Next.
3. Specify the task sequence name and comments on the General screen. Click Next.
4. Set the preferred configuration on the Details screen. Click Next.
5. Select This task sequence may be used to capture an image on the Capture Settings screen, and specify the
Capture destination and Capture account. Click Next.
6. Specify the appropriate boot image on the Boot Image screen. Click Next.
7. Choose Create a new Microsoft Deployment Toolkit Files package on the MDT Package screen, and specify a UNC
path that includes the target files. Click Next.
8. Specify the MDT files package properties on the MDT Details screen. Click Next.
9. Select Specify an existing OS image on the OS Image screen and Browse to the target image screen. Click Next.
10. Choose the preferred option on the Deployment Method screen: User-Driven Installation or Zero Touch
Installation. Click Next.

Note:
Additional configuration is needed if using the User-Driven Installation (UDI). Complete the following steps after creating the
MDT task sequence:
Open the UDI Wizard Designer by clicking Start > All Programs > Microsoft Deployment Toolkit > UDI Wizard Designer.
Click Open, and locate the the path of the Microsoft Deployment Toolkit Files package created in step 7 in Creating an
MDT task sequence in SCCM. Open the file UDIWizard_Config.XML in the Scripts folder.
Select BitLocker in the Page Library panel on the left. Extend the BitLocker Mode and uncheck Initially check this
checkbox in the wizard.
Switch to New Computer Details in the Computer Page. Extend Network Details under the Network Details panel and
check Domain.
Extend Domains and OUs under the Network Details panel. Click the + button; specify the Domain Name and Friendly
Name, and then click OK. Specify the OU by right-clicking the added domain and choosing Add OU Manually.
Extend the Domain Join Credentials in the Network Details panel, and add the domain account used for joining the
domain.
Switch to the Volume Page and extend the User Data Combo Behavior. Check Format: Clean all data on the target
volume during install.
Save the UDIWizard_Config.xml and update the MDT Toolkits File Package to the distribution point.

11. Specify the prepared ConfigMgr client package on the Client Package screen. Click Next.
12. Specify the prepared USMT package on the USMT Package screen. Click Next. For the task sequence to include User
State Migration, make sure that the RAM disk on the source or destination image is configured to have at least 250 MB
space to support USMT operations. For more information, see Appendix A.
13. Choose Create a new settings package on the Settings Package screen and specify the UNC path (for example,
\\SCCM\MDT\Settings) to save the package. Click Next.

9
 14. Specify the settings package properties on the Settings Details screen. Click Next.
15. Choose No Sysprep package is required on the Sysprep Package screen. Click Next.
16. Click Next on the Summary screen.
17. Click Finish on the Confirmation screen.
18. Navigate to System Center Configuration Manager > Software Library > Overview > Application Management >
Packages. Synchronize the MDT toolkit files and MDT settings to the distribution point.
19. Refresh the Packages and make sure that the content statuses of all the packages are successful before proceeding.

Configuring Capture Image in the MDT task sequence

1. Open the SCCM Console and nagivate to Software Library > Overview > Operating Systems > Task Sequences.
Right-click the MDT task sequence just created and click Edit to open the Task Sequence Editor.
2. Select Add > General > Set Task Sequence Variable. Set the Task Sequence Variable name as Do Capture and put
YES in the value field. Right-click Set Task Sequence Variable and click Move Up to set the task in the front of the
Capture the Reference Machine group. These steps force the execution of the tasks in the Capture the Reference
Machine group, which are skipped by default.
3. Select Add > General > Join Domain or Workgroup. Use Move Up to make this the first task of the Capture the
Reference Machine group.
4. Leave the default settings for the other tasks, and then click Apply and OK to save the MDT task sequence.

Note:
The EDM service must be stopped and disabled on the client side before executing the MDT task sequence.
To stop the EDM service, select Add > General > Run Command Line and specify cmd /c sc stop "EdmWfSrv in the
command line field.
To disable the EDM service, select Add > General > Run Command Line and specify cmd /c sc config "EdmWfSrv" start=
disabled in the command line field.
Make sure that these two tasks are set as the first executed and second executed task in Capture the Reference Machine
group before continuing. The task in step 3 (Join Domain or Workgroup) will be the third executed.

Deploying the MDT task sequence (including both Capture Image and Deploy Image)
If you do not need to perform the Capture Image task, delete the Set Task Sequence Variable task before the Capture the
Reference Machine group in the MDT Task Sequence Editor. Then, use the following steps to deploy the image.
1. Open the SCCM Console, navigate to Software Library > Overview > Operating Systems > Task Sequences, right-
click the created MDT task sequence, and select Deploy.
2. Specify the preferred collection on the General page. Click Next.
3. Select the preferred Purpose and select Configuration Manager Clients, media and PXE on the Deployment
Settings page. Click Next.
4. Specify the preferred schedule on the Scheduling page. If you set the Purpose as Required in the previous step, then
select New. Next, select Assign immediately after this event and set the value to As soon as possible. Click Next.
5. Keep the default settings on the User Experience and Alerts pages. Click Next.
6. Check When no local distribution point is available, use a remote distribution point on the Distribution Points
page. Click Next.
7. Click Next on the Summary page.
8. Click Close on the Completion page.

10
Appendix A
Preparation for a task sequence with User State Migration
The source computer needs at least 250 MB of hard disk space to support USMT operations. For more information, go to
http://technet.microsoft.com/en-us/library/dd560770%28v=ws.10%29.aspx#BKMK_SpaceReqs.
For a WES7 image on an HP thin client, USMT will use RAM disk Z: by default. Extend the disk size before capturing and
deploying an image.
To extend a RAM disk:
1. Modify the registry value and commit to write filter if enabled:
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\RamDrive\Parameters\DiskSize
2. Run command line: reg add HKLM\SYSTEM\ControlSet001\services\Ramdrive\Parameters /v
DiskSize /t REG_DWORD /d 0x10400000 /f

Appendix B
Enabling the write filter in a Deployment task sequence
To enable the writer filter as part of the OS Deployment Process, HP recommends running the command lines or scripts at
first boot. The following is a summary of the steps needed to enable the writer filter:
1. Edit the Operating System Task Sequence to autologin the Administrator during deployment
2. Use unattend.xml to create First Launch Commands.
3. Once the OS deployment completes, the task sequence will exit and return full control to the OS. These example First
Launch Commands will execute the following:
A. Automatically logs in the Administrator after deployment.
B. Enables the write filter.
C. BCD FixupThe Enhanced and File-Based Write Filter require the IGNOREALLFAILS policy be in the Boot
Configuration Data. This flag prevents error dialogs regarding unsafe shutdowns during the boot process.
Typically, in WES7, enabling the write filter will automatically set this policy in the BCD and prevent boot up errors.
It might not be set automatically following a deployment tast sequence in SCCM and with then need to be set
manually.
D. Removes Administrator Autologin on next reboot or sets User Autologin.
E. Restarts the system after 90 seconds.
4. After restarting, the unit is now ready for the end user with the write filter enabled.
The following snippet is the First Launch Command to be included in the unattend.xml file under the <settings
pass="oobeSystem"> section:
<FirstLogonCommands>
<SynchronousCommand wcm:action="add">
<Order>1</Order>
<CommandLine>ewfmgr c: /enable </CommandLine>
<Description>Enable EWF WF </Description>
</SynchronousCommand>
<SynchronousCommand wcm:action="add">
<Order>2</Order>
<CommandLine>bcdedit /set {current} bootstatuspolicy
ignoreallfailures
</CommandLine>
<Description>Fix BCD </Description>
</SynchronousCommand>
<SynchronousCommand wcm:action="add">

11
 <Order>3</Order>
<CommandLine>autologcfg /u:User /p:User</CommandLine>
<Description>Enables user Autologin</Description>
<RequiresUserInput>false</RequiresUserInput>
</SynchronousCommand>
<SynchronousCommand wcm:action="add">
<Order>4</Order>
<CommandLine>shutdown -r -t 90</CommandLine>
<Description>Restarts after 90 seconds</Description>
<RequiresUserInput>false</RequiresUserInput>
</SynchronousCommand>
</FirstLogonCommands>

12
Sign up for updates
hp.com/go/getupdated

Copyright 2013 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. The only warranties for
HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as
constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein.

Microsoft and Windows are U.S. registered trademarks of Microsoft Corporation.

First Edition: June 2013

Document Part Number: 738375-001