Monday, September 2, 2013

Step 1.1: Full OS Validation

This is the first step of the All-in-One task sequence. This step initiates only when it is run in Full OS mode, in other words when initiated by an end user.
Key points are;
-          The task sequence will check the associated conditions and executed only if it is launched in Full         OS Mode
-          Will NOT execute if launched in WinPE or OEMMedia

In Full OS Validation step:
-          We will copy few files to local drive of the machine
-          Task Sequence will launch few scripts based on the conditions. These scripts will create a flag  
       files on the target machine.
-          Based on the flag file existence, we will create a Task Sequence custom variables
-          If a condition is true for supported model, HTA will prompt with a warning msg and with a password prompt. After validating the password the TS continues or user can cancel.
Following Group conditions should be met before executing Full OS Validation;
                 Task Sequence variable true  _SMSTSLaunchMode equals SMS
               Task Sequence variable true  _SMSTSMediaType  notequals OEMMedia
Create Package called FullOSValidationHTA using Migration.hta file (sample code provided below), ServiceUIx32.exe and ServiceUIx64.exe
Copy HTA step copies the FullOSValidationHTA package source files to C:\Migration folder.

Create a package called FullOSDMigration using Unsupported.hta and Supported.cmd (Both sample sourced provided below). We will be adding more files to this package later.
Copy OSD++ step copies the FulISDMigration package contents to existing C:\Migration folder.

Model validation step will be executed if the conditions are met.
For example if the condition is TRUE for SELECT * FROM Win32_ComputerSystem WHERE Model LIKE '%VMware Virtual Platform%' then this step will execute and launch Supported.cmd file from C:\Migration, which was copied in previous step. That cmd file will write Supported.txt file to C:\Migration.
Sample Supported.cmd file:
**********************************************************
@echo off
REM Supported.cmd
echo Supported model detected>>C:\Migration\Supported.txt
**********************************************************
Based on the existence of the Supported.txt file, we will create custom Task Sequence variables.
Supported Model TS Variable step will be executed based on the TRUE condition of existence of Supported.txt in C:\Migration and created a custom Task Sequence variable win7supported value TRUE
 
 
Unsupported Model TS Variable step will be executed based on the None TRUE condition of existence of Supported.txt in C:\Migration and created a custom Task Sequence variable Win7Supported value FALSE