Expand the Operating Systems tree and choose Task Sequences.

On the Create New Task Sequence screen:

On the Task Sequence Information screen:

On the Upgrade the Windows Operating System screen:

On the Include Updates screen:

On the Install Applications screen:

On the Summary screen:

Once the Task Sequence has been created, double-click it to open the Properties. Select the Advanced tab then configure the boot image as indicated below

In the Properties dialog:

• two 1E WSA Actions steps (one to initialize the task sequence and the other to finalize it)
• two groups (the Main group for the actions in the task sequence which contains multiple sub-groups and the Rollback group)

within the Main group, we are going to customize it by:

• moving groups from the base task sequence in it
• adding new steps to it

The process and procedure is described below.

With the 1E WSA Actions step highlighted, click Add and choose New Group. 

1. 

   With the Main group highlighted, click Add and from the menu, choose 1E Nomad > Set Nomad as Download Program. Right-click the step and from the context menu, choose Move Up so it becomes a child of the Main group and click OK. No additional settings are required for this step. This step sets Nomad as the download program for all Task Sequence content so should be added at the top of the Main group before any content is required.

   
   

2. 

   With the Set Nomad as Download Program step highlighted, click Add and choose New Group. This group contains steps that will validate the WiFi and VPN credentials entered by the user in the Windows Servicing Assistant. If the Task Sequence was not initiated through WSA (i.e. 1EWSA is not true), this group will be skipped. If the Task Sequence was initiated through WSA, this group will validate the credentials by disconnecting WiFi and VPN (if applicable) and attempting to reconnect using the supplied credentials. If the validation fails, the Task Sequence will fail and the user will be notified through the final WSA page that there was a problem with either the WiFi or VPN credentials. This group is included in the Task Sequence to fail before doing anything destructive on the PC if there are any problems with the supplied credentials. On the Properties tab On the Options tab Name the group Test Connection   Click Add Condition > Task Sequence Variable. Enter the following details. Variable 1EWSA Condition equals Value True Click OK. Click Apply. When the task sequence runs, connectivity to the Configuration Manager site must be maintained after any system restart into the full OS. Throughout the task sequence, the 1E WSA Actions step attempts to automatically establish WiFi connections (using WSA gathered credentials) when either of the Refresh Content Locations or Switch Between online and offline content options are selected. For locations using VPN, the Connect to VPN step uses the ConnectVPN.PS1 PowerShell script to establish a VPN connections. Provided the VPN profile name has been defined in the task sequence, VPN connection credentials have been entered during running of the Assistant  and an external network exists, the script will attempt to establish the connection. Currently, WSA has been developed for use with the Microsoft VPN Client. The VPN connection process within WSA can be extended to accommodate other VPN client solutions. Future releases of WSA will also supports solutions implementing two factor authentication, where user input may be required at the time the connection is established. The steps defined within the Test Connections group are designed to exercise those connection credentials supplied by the user when they ran WSA wizard and establish their validity before proceeding any further in the task sequence.  With the Test Connection group highlighted, click Add and from the menu choose General > Run Powershell Script. On the Properties tab On the Options tab Enter the following details: Step parameter Value Name Validate WiFi VPN Credentials Description Test WiFi and VPN connection credentials before allowing the task sequence to continue Package Browse to the WSA Scripts package Script name ValidateWiFiVPNCreds.ps1 Parameters  -VPNProfile <VPNProfile> PowerShell Execution Policy Set the PowerShell execution policy to Bypass. Click Apply. Select Continue on error. There is a known issue where a Run PowerShell Script step can erroneously return 1 to the Task Sequence, causing this step to fail even though the script completes successfully. This step is configured to continue on error, but the next step will report back any actual error to the Task Sequence if the return code from this step is neither 0 or 1. Both the ValidateWiFiVPNCreds.ps1 script and the VPN connection script ConnectVPN.PS1, require a VPN profile name in order to establish the connection. <VPNProfile> must be the same name defined in the rasphone.pbk included in the WSA Scripts Package. If the profile name includes spaces, surround it in single quotes (e.g. '1E (UK)'). If rasphone.pbk includes multiple profiles (e.g. US and UK), the parameter can be configured to use a Collection variable (e.g. -VPNProfile '%VPNProfile%') - if you use this approach, ensure there is a Collection variable named VPNProfile defined for all clients that will run WSA otherwise this step in the Task Sequence will fail. Click Add and from the menu choose General > Run command line. This step is to work around an issue when running PowerShell script steps where a command in the script returns 1 but the script does not error and completes successfully. CM reports this as an error even though the ValidateWiFiVPNCreds.ps1 script finally exits with 0. The step will be skipped if the last action (Validate WiFi VPN Credentials) returns either 0 or 1 and the Task Sequence will continue to execute. Otherwise it will return the actual return code from the Validate WiFi VPN Credentials and the TS will fail. On the Properties tab On the Options tab   Enter the following details, leaving the remaining options unchecked. Step parameter Value Name Filter return codes from Validation script Description Allows TS to continue if the previous step returns 0 or 1, otherwise fails with the return code of the previous step Command line cmd /c exit %_SMSTSLastActionRetCode% Click Apply. Click Add Condition and choose Task Sequence Variable Enter the following details: Variable _SMSTSLastActionRetCode Condition not equals Value 1 Click OK. Click Add Condition and choose Task Sequence Variable. Enter the following details: Variable _SMSTSLastActionRetCode Condition not equals Value 0 Click OK. Click Add and from the menu, choose General > Run PowerShell script. This step establishes a VPN connection if the Task Sequence was initiated by a remote user. On the Properties tab On the Options tab   Enter the following details: Step parameter Value Name 1E WSA Connect VPN Description Connect VPN using WSA Gathered credentials Package Browse to the WSA Scripts package Script name ConnectVPN.ps1 Parameters  -VPNProfile <VPNProfile> PowerShell Execution Policy Set the PowerShell execution policy to Bypass. <VPNProfile> must match the name of the profile defined in rasphone.pbk. Click Apply. Click Add Condition and choose Task Sequence Variable. Enter the following details: Variable 1EWSA_RemoteUser Condition equals Value True Click OK. Click Apply.

   
   

3. 

   Click Add and from the menu, choose General > Set Task Sequence Variable. On the Properties tab On the Options tab Enter the following details: Step Parameter aaaa Value Name Set SMSTSPostAction Task Sequence Variable SMSTSPostAction Value shutdown.exe /r /t 30Select Click Apply. No action required

   
   

4. 

   Click Add and from the menu, choose General > Set Task Sequence Variable. This step sets the OSDBitLockerStatus variable to Protected if the C: drive is protected when the Task Sequence starts. It is used later in the Task Sequence to enable BitLocker if it was enabled and the drive was protected before the upgrade when the Task Sequence started. On the Properties tab On the Options tab Enter the following details: Step parameter Value Name Set OSDBitLockerStatus Task Sequence Variable OSDBitLockerStatus Value Protected Click Apply. Click Add Condition and choose WMI Query. Enter the following details: WMI Namespace: root\cimv2\Security\MicrosoftVolumeEncryption SELECT * FROM win32_encryptablevolume WHERE driveletter = 'c:' AND protectionstatus = '1' Click OK. Click Apply.

   
   

5. 

   Select the Prepare for Upgrade group and move it up so it becomes a child of the Main group.

   
   

6. 

   Select the Upgrade the Operating System group and move it up so it becomes a child of the Main group.  With the Upgrade the Operating System group selected, click Add and from the menu, choose General > Run a command line This is an optional step to work around an issue identified on some Dell PCs where restarting the PC when connected to VPN on a wireless connection would cause the PC to blue-screen. It installs a service that disconnects the VPN connection when a shutdown is requested by the OS, which has been observed to prevent the blue-screen. On the Properties tab On the Options tab Enter the following details: Step parameter Value Name Install RasdialDisconnect service Command line InstallRasdialDisconnectService.bat Check the Package option and browse to the WSA Scripts package. Click Apply. Click Add Condition and choose Task Sequence Variable. Enter the following details: Variable 1EWSA_RemoteUser Condition equals Value True Click OK. Click Apply. Select the Restart Computer step, click Add and from the menu, choose 1E OSD > 1E WSA Actions. On the Properties tab On the Options tab Enter the following details: Step parameter Value Name 1E WSA Action Refresh Content Location Checked Switch Between online and offline content Checked Click Apply. Click Add Condition and choose Task Sequence Variable. Enter the following details: Variable 1EWSA Condition equals Value True Click OK. Click Apply. Click Add and from the menu, choose General > Run PowerShell script and configure it as follows: On the Properties tab On the Options tab Step parameter Value Name Connect to VPN Package Browse to the WSA Scripts package Script name ConnectVPN.PS1 Parameters -VPNProfile <VPNProfile> PowerShell Execution Policy Set the PowerShell execution policy to Bypass <VPNProfile> must match the name of the profile defined in rasphone.pbk. Click Add Condition and choose Task Sequence Variable. Enter the following details: Variable 1EWSA_RemoteUser Condition equals Value True Click OK. Click Apply.

   
   

7. 

   Select the Post-Processing group and move it up so it becomes a child of the Main group Select the Install Updates step and configure as follows In the Properties tab In the Options tab No changes required Uncheck the option Retry this step if computer unexpectedly restarts Click Apply. A software update may require one or more restarts of the host to complete its installation. For a WSA deployment, it is important to note that in order for the Install Updates step to complete successfully, only a single restart of the host is permissible at completion of the step. If multiple restarts are anticipated, then multiple Install Update steps must be configured with subsequent 1E WSA Actions and Connect to VPN steps (as detailed in the following two steps). This allows a site connection to be established, before the next update is installed. In this task sequence it is anticipated that no update will require more than one restart of the host. Select Install Updates and click Add and from the menu, choose 1E OSD > 1E WSA Actions. In the Properties tab In the Options tab Enter the following details: Step parameter Value Name 1E WSA Action Refresh Content Location Checked Switch Between online and offline content Checked Click Apply. Click Add Condition and choose Task Sequence Variable. Enter the following details: Variable 1EWSA Condition equals Value True Click OK. Click Apply. Click Add and from the menu, choose General > Run PowerShell script. On the Properties tab On the Options tab Browse to the VPN connection script package and enter these details: Step parameter Value Name Connect to VPN Package Browse to the WSA Scripts package Script name ConnectVPN.PS1 Parameters -VPNProfile <VPNProfile> PowerShell Execution Policy Set the PowerShell execution policy to Bypass. <VPNProfile> must match the name of the profile defined in rasphone.pbk Click Apply. Click Add Condition and choose Task Sequence Variable. Enter the following details: Variable 1EWSA_RemoteUser Condition equals Value True Click OK. Click Apply.

   
   

8. 

   With the Connect to VPN step highlighted, click Add and from the menu, choose Add > New Group > 1E BIOS to UEFI. On the Properties tab On the Options tab Click Add Condition and choose Task Sequence Variable. Enter the following details: Variable _SMSTSBootUEFI Condition equals Value False Click OK. For the newly created condition, click Add Condition > If Statement > Any Condition > WQL Query and create a query condition for each of the following> WMI Namespace: root\cimv2 SELECT * FROM Win32_ComputerSystem WHERE Manufacturer LIKE "%Dell%" SELECT * FROM Win32_ComputerSystem WHERE Manufacturer LIKE "%HP%" SELECT * FROM Win32_ComputerSystem WHERE Manufacturer LIKE "%Lenovo%" Select * FROM Win32_ComputerSystem WHERE Manufacturer LIKE "%Hewlett-Packard%" The 1E BIOS to UEFI group is responsible for converting the host system disk from legacy BIOS to UEFI and configuring those firmware settings required to implement the associated security features and settings. UEFI is a firmware standard required to support modern security features such as Secure Boot, Device Guard and Credential Guard. In configuring this task sequence, the BIOS to UEFI conversion is performed using the native Windows utility MBR2GPT.exe located in C:\Windows\System32 on Windows 10 1703 editions and later. In the task sequence, conversion is conditioned to take place only if the host is running legacy BIOS. The 1E BIOS to UEFI application is a packaged and ready set of task sequence steps that automate the necessary firmware reconfigurations on Dell, Lenovo and HP systems in order to allow Secure Boot, Device Guard, Credential Guard and other settings to be turned on once the disk has been converted. Full details on how to use 1E BIOS to UEFI and the supported hardware models, can be found here 1E BIOS to UEFI. Click Add and from the menu, choose General > Run Command Line. This step disables BitLocker if it was enabled when the Task Sequence started (i.e. if OSDBitLockerStatus=Protected). The command line disables it indefinitely (so for any subsequent reboots), until it is enabled later in the Task Sequence. On the Properties tab On the Options tab Enter the following details: Step parameter Value Name Disable Bitlocker Command line manage-bde -protectors -disable C: -RC 0 Click Apply. Click Add Condition and choose Task Sequence Variable. Enter the following details: Variable OSDBitLockerStatus Condition equals Value Protected Click OK. Click Apply. Click Add and from the menu, choose General > Run PowerShell script. This step is a workaround for an issue where Configuration Manager may stage the Windows PE boot image on a connected USB disk if it is larger than the local disk and then not be able to boot from it. The step creates a temporary file on the USB drive that fills it so CM cannot stage the boot image on the disk. The temporary file is later removed with the Teardown.ps1 script. On the Properties tab On the Options tab Browse to the script package and enter these details: Step parameter Value Name Setup WinPE Boot Description Prevents TS staging the boot image onto a large USB disk by temporarily filling it. Package Browse to the Setup WinPE Boot package Script name SetupWinPEBoot.ps1 Parameters   PowerShell Execution Policy Set the PowerShell execution policy to Bypass. Click Apply. No action required Click Add and from the menu, choose General > Restart Computer. On the Properties tab On the Options tab Enter the following details: Step parameter Value Name Restart in WinPE The boot image assigned to this task sequence Selected Notifiy the user before restarting Checked   Beginning the UEFI and MBR2GPT conversion. The computer must restart to continue Click Apply. No action required Click Add and from the menu, choose 1E OSD > 1E WSA Actions. The WSA Actions step must be executed after each reboot where drive letters may change or when switching between the full OS and Windows PE On the Properties tab On the Options tab Enter the following details: Step parameter Value Name 1E WSA Action Refresh Content Location Checked Switch Between online and offline content Checked Click Apply. Click Add Condition and choose Task Sequence Variable. Enter the following details: Variable 1EWSA Condition equals Value True Click OK. Click Apply. Click Add and from the menu, choose 1E Nomad  > Install and Configure Nomad in WinPE. This step installs the Nomad agent in Windows PE. Refer to Install and configure Nomad in WinPE for further details on using this step. On the Properties tab On the Options tab Enter the License Key and ActiveEfficiency URL fields. Configure the remaining fields according to your environment. No action required Click Add and from the menu, choose 1E Nomad > Save Nomad Cache. This step saves the Nomad cache to the temporary Task Sequence storage. Refer to Save Nomad cache for further details on using this step On the Properties tab On the Options tab Enter the following details: Step parameter Value Operation Move Wipe CCM Cache Checked Click Apply. No action required Click Add and from the menu, choose General > Run PowerShell script. If the Setup WinPE Boot step created a temporary file to fill an attached USB disk (to prevent CM from staging the boot image on the USB disk), this step deletes that file. On the Properties tab On the Options tab Browse to the script package and enter these details: Step parameter Value Name Delete temporary USB disk fill Description Deletes temporary file created to fill large USB disk Script name Teardown.ps1 Parameters   PowerShell Execution Policy Set the PowerShell execution policy to Bypass. Click Apply. No action required Click Add and from the menu, choose General > Run Command Line. This step converts the disk from MBR to GPT to support UEFI, using the Microsoft MBR2GPT tool On the Properties tab On the Options tab Enter the following details: Step parameter Value Name MBR2GPT in WinPE Command line MBR2GPT.EXE /disk:0 /convert /AllowFullOS /logs:%_SMSTSLogPath% Click Apply. Select the Continue on Error option. Click Add Condition and choose Task Sequence Variable. Enter the following details: Variable _SMSTSBootUEFI Condition equals Value False Click OK. Click Add Condition > WQL Query and create this query condition WMI Namespace: root\cimv2 SELECT * FROM win32_diskpartition WHERE deviceid LIKE '%partition #0%' AND type LIKE '%Installable%' Click OK. Click Apply.

   
   

9. 

   Click Add and from the menu, choose New Group. On the Properties tab On the Options tab Name the group Firmware Settings Click Add Condition and choose Task Sequence Variable. Enter the following details: Variable _SMSTSLastActionSucceeded Condition equals Value True Click OK. Click Apply. The following steps included in this group are provided as an example of the 1E BIOS to UEFI feature, which can: Unlock the BIOS using a whitelist of password values defined in the step – this step can be added multiple times with appropriate conditions to enable different passwords to be used on different device classes Set the boot order – to ensure that the host will boot from the System partition following conversion to UEFI, if may be necessary to explicitly set the boot order in the firmware Enable Secure Boot Set the BIOS password – if BIOS passwords are used and need to be standardized Each of the steps require the 1E OEM Toolkit Package. Refer to Launching the Create 1E OEM Toolkit Package wizard for details on how to create the 1E OEM Toolkit Package. Click Add and from the menu, choose 1E OSD > 1E BIOS to UEFI Password Setup. This step defines the BIOS admin password(s) that will be attempted when the subsequent 1E BIOS to UEFI steps attempt to make changes to the firmware settings. Refer to Automating password authentication for changing BIOS settings for further details on using this step. On the Properties tab On the Options tab Name the step 1E BIOS to UEFI Define Password Add your current BIOS password(s) in the Password List. Browse for the OEM Toolkit Package Click Apply. No action required Click Add and from the menu, choose 1E OSD > 1E BIOS to UEFI Boot Order. This step defines the UEFI boot order, which should typically be set to Windows Boot Manager. Refer to Changing the BIOS boot order for further details on using this step On the Properties tab On the Options tab Ensure Windows Boot Manager is selected in the UEFI Boot Order drop-down Browse for the OEM Toolkit Package. Click Apply. No action required Click Add and from the menu, choose 1E OSD > 1E BIOS to UEFI OEM. This step configures the firmware settings to enable UEFI, Secure Boot and other options. Refer to Working with BIOS to UEFI for further details on using this step. In order to ensure builds are successful when you enable Secure Boot, we recommended: Client firmware is updated to the latest version You test Secure Boot on those hardware models targeted by the task sequence before deploying into a production environment. On the Properties tab On the Options tab Select the UEFI Configuration option and select UEFI Native with Secure Boot. Browse for the OEM Toolkit Package. Click Apply. No action required Click Add and from the menu, choose 1E OSD > 1E BIOS to UEFI Password Setup . This optional step sets the BIOS password to a predefined password and can be used to standardize on a single BIOS password. Refer to Automating password authentication for changing BIOS settings for further details on using this step. On the Properties tab On the Options tab Add any current BIOS passwords and the password you want to set to the Password List. Select Set New Password and select the password from the drop list provided. Browse for the OEM Toolkit Package. Click Apply. No action required

   
   

10. 

    Highlight the 1E BIOS to UEFI Password Setup step, click Add and from the menu, choose New Group. This group contains steps that will restart the computer into the new OS, reconnect the WiFi and VPN if applicable, restore the Nomad cache and enable BitLocker On the Properties tab On the Options tab Name the group Restart and Initialize. Use the down arrow to move the group so that it becomes a child of 1E BIOS to UEFI – at the same level as the Firmware Settings group. No action required With the Restart and Initialize group highlighted, click Add and from the menu, choose General > Restart Computer. Ensure the step is set to restart into The currently installed default operating system. Click Add and from the menu, choose 1E OSD > 1E WSA Actions. The WSA Actions step must be executed after each reboot where drive letters may change or when switching between the full OS and Windows PE On the Properties tab On the Options tab Enter the following details: Step parameter Value Name 1E WSA Action Refresh Content Location Checked Switch Between online and offline content Checked Click Apply. Click Add Condition and choose Task Sequence Variable. Enter the following details: Variable 1EWSA Condition equals Value True Click OK. Click Apply. Click Add and from the menu, choose 1E Nomad > Restore Nomad Cache. This step restores the Nomad cache from the temporary Task Sequence store. Refer to Restore Nomad cache for further details on using this step. On the Properties tab On the Options tab Enter the following details: Step parameter Value Operation Link Activate All Content Checked Click Apply. No action required Click Add and from the menu, choose Run PowerShell script. On the Properties tab On the Options tab Browse to the VPN connection script package and enter the step details: Step parameter Value Name Connect to VPN Script name ConnectVPN.PS1 Parameters -VPNProfile <VPNProfile> PowerShell Execution Policy Set the PowerShell execution policy to Bypass. <VPNProfile> must match the name of the profile defined in rasphone.pbk. Click Apply. Click Add Condition and choose Task Sequence Variable. Enter the following details: Variable 1EWSA_RemoteUser Condition equals Value True Click OK. Click Apply. Click Add from the menu, choose Disks > Enable BitLocker. This step enables BitLocker if the disk was BitLocker protected when the Task Sequence started On the Properties tab On the Options tab Configure the step according to the requirements of your organization. Click Add Condition and choose Task Sequence Variable. Enter the following details: Variable OSDBitLockerStatus Condition equals Value Protected Click OK. Click Apply.

    
    

11. 

    With the Enable BitLocker step highlighted, click Add and from the menu, choose New Group. Use the down arrow to move the group so that it becomes a child of the Post-Processing group – at the same level as the 1E BIOS to UEFI group. This group contains steps that automate the upgrade or replacement of applications during the In-place Upgrade using 1E Application Migration. It will be executed unless the Task Sequence was initiated by a WSA deployment that has Application Migration disabled. On the Properties tab On the Options tab Name the group Install Migrated Applications. Click Add Condition and choose Task Sequence Variable. Enter the following details: Variable 1EWSA_AppMigrationEnabled Condition not equals Value False Click OK. Click Apply. With the Install Migrated Applications group highlighted, click Add and from the menu, choose 1EOSD > AppMigration. This step gets a list of Applications and Packages that need to be installed according to the migration rules defined in Application Migration. The list of Applications and Packages are returned as a series of Task Sequence variables that are then used in the dynamic Install Application and Install Package steps. Refer to Using Application Migration in a task sequence for further details on using this step. On the Properties tab On the Options tab Enter the following details. Step parameter Value Web Service http://[SLA platform URL]/Platform/api/applicationmigration/getApplicationsToBeInstalled Domain\User Name The credentials of a user defined in the SLA platform Domain The FQDN of the domain that the current machine is in Source Computer Name Variable _SMSTSMachineName (In an In-Place Upgrade, the source computer name is the current computer name, defined by this built-in variable) Application Variable Choose a base variable that will be used to define dynamic Applications i..e APPMIG Package Variable Choose a base variable that will be used to define dynamic Packages i.e. PKGMIG Click Apply. No action required Although an in-place upgrade is not destructive and applications are preserved on the disk, Application Migration can be added to the In-Place Upgrade Task Sequence to upgrade or replace applications that are currently installed as part of the upgrade process based on the application migration rules. The following caveats apply when using Application Migration in an in-place upgrade scenario: If a Retain Migration rule applies: if the target application is a Configuration Manager Application, the Application installation should not execute as it is already present (based on the Detection Method defined in the Deployment Type). if the target application is a Configuration Manager Program, the Program will execute (even though the application is already installed). It is therefore important that the Program can execute without error and without adversely affecting the installed application. If an Upgrade Migration rule applies: if the target application is a Configuration Manager Application and the target application is not already installed, it will be installed. If the Application installation does not successfully upgrade the original version of the application, the result will be both the original version and the upgraded version being installed. In this scenario, Application Supersedence can be used to ensure the original version is removed when the newer version is installed. if the target application is a Configuration Manager Program, the Program will be executed. If the Program (command line) does not successfully upgrade the original version of the application, the result will be both the original version and the upgraded version being installed. If a Replace Migration rule applies: if the target application is a Configuration Manager Application and the target application is not already installed, it will be installed. The original application that was to be replaced will remain installed. In this scenario, Application Supersendence can be used to ensure the application to be replaced gets removed when the replacement application is installed. if the target application is a Configuration Manager Program, the Program will be executed. The result will be both the original application and the replacement application being installed

    
    

12. 

    With the 1E Application Migration step highlighted, click Add and from the menu choose New Group. This group contains a step that waits for 3 minutes for the CM client to fully initialize (in some environments Application installations can fail if attempted too soon after a restart). It then executes the Install Applications step, which dynamically installs the applications returned by the 1E Application Migration step. On the Properties tab On the Options tab Name the group Install Migrated Apps Click Add Condition and choose Task Sequence Variable. Enter the following details: Variable APPMIG01 Condition exists Append 01 to the application variable you used in the step above. Click OK. Click Apply. Click Add and from the menu choose General > Run Comand Line. This step introduces a 3-minute pause to allow the CM client to fully initialize before attempting to install Applications On the Properties tab On the Options tab Enter the following details: Step parameter Value Name Sleep Time for CM Client Initialise Command line cmd /c ping localhost -n 180 > NUL Click Apply. No action required Click Add and from the menu choose, Software > Install Application. On the Properties tab On the Options tab Enter the following details: Step parameter Value Name Install Migrated Applications Install applications according to the dynamic variable list Selected Base variable name Enter the base variable name used in 1E Application Migration step, for example APPMIG If an application installation fails, continue installing other applications in the list Check if required Click Apply. No action required

    
    

13. 

    Highlight the Install Migrated Applications step, click Add and from the menu, choose Software > Install Package. Move the step down so that is appears as a child of Install Migrated Applications – at the same level as the Install Migrated Apps group. On the Properties tab On the Options tab Enter the following details: Step parameter Value Name Install Migrated Packages Install software packages according to the dynamic variable list Selected Base variable name Enter the base variable name used in the 1E Application Migration step, for example PKGMIG If installation of a software package fails, continue installing other packages in the list Check if required Click Apply. Click Add Condition and choose Task Sequence Variable. Enter the following details: Variable PKGMIG01 Condition exists Append 01 to the application variable you used in the step k. Click OK. Click Apply.

    
    

14. 
    

    Select the Install Migrated Packages step, click Add and from the menu choose General > Run Command Line. Move the step down so it becomes a child of the Main group (at the same level as Install Migrated Applications (k) in the screen shot at the top of this page). Configure the step as indicated below This step uninstalls the RasdialDisconnect service that works around the issue on some Dell systems where rebooting while on WiFi with an active VPN connection causes a blue-screen system crash. On the Properties tab On the Options tab Enter the following details: Step parameter Value Name Uninstall RasdialDisconnect service Command line UnInstallRasdialDisconnectService.bat Check the Package option and browse to the WSA Scripts package. Click Apply. Click Add Condition and choose Task Sequence Variable. Enter the following details: Variable 1EWSA_RemoteUser Condition equals Value True Click OK. Click Apply.