Deployment Solution

He got a error 2 message and the job stopped.

I asked him to export the job and to send it to me, and then I noticed that there was a error in the script.

So in this article I'm going to explain how the script is built.

And for all those who just want to use it? It is attached at the bottom of the article. Download it, unzip it and import it.

The script is just for computers that you wish to deploy Vista to. In the XP version of Microsoft Windows the error will not occur.

So let's get started.

The first thing to do is go down to the bottom of this article and download the attached file.

When you have it on your own computer, then start the deployment server, and import it.

Click to view.

Go to your folder HII tools or test scripts and right click with the mouse. Then select Import.

Click to view.

Select the downloaded file DinamiQs.bin, and select the folder were you want it to be imported. Then click OK.

Click to view.

Now you see a job called deploy DinamiQs HII Vista image. When you select the job you see in the upper right that it contains 7 jobs.

So let's open the job by double clicking on it and see what it actually does.

Step 1: Distribute Disk Image

Click to view.

Select the previously built image in the Name path. Do not use the sysprep. You may use it, but then the machine will be on the domain before we finished all the tasks, and that is not the best idea right now.

In the bottom you can select your default Automation Pre-boot environment. Click Next to continue, and then finish to confirm the changes.

This job will image the computer with the hardware independent image.

Step 2: Run first script Assign drive letters.

Click to view.

It is just a short script that helps us to determine the correct file partitions. The job runs in Windows mode. The text file diskpart contains the following text:

select disk 0
select partition 1
assign
select partition 2
assign


select partition 3
assign
select partition 4
assign
select partition 5
assign
select partition 6
assign
select partition 7
assign
select partition 8
assign
select partition 9
assign
select partition 10
assign
select disk 1
select partition 1
assign
select partition 2
assign
select partition 3
assign
select partition 4
assign
select partition 5
assign
select partition 6
assign
select partition 7
assign
select partition 8
assign
select partition 9
assign
select partition 10
assign
select disk 2
select partition 1
assign
select partition 2
assign
select partition 3
assign
select partition 4
assign
select partition 5
assign
select partition 6
assign
select partition 7
assign
select partition 8
assign
select partition 9
assign
select partition 10
assign
select disk 3
select partition 1
assign
select partition 2
assign
select partition 3
assign
select partition 4
assign
select partition 5
assign
select partition 6
assign
select partition 7
assign
select partition 8
assign
select partition 9
assign
select partition 10
assign
select disk 4
select partition 1
assign
select partition 2
assign
select partition 3
assign
select partition 4
assign
select partition 5
assign
select partition 6
assign
select partition 7
assign
select partition 8
assign
select partition 9
assign
select partition 10
assign

Click Next to go the next screen.

Click to view.

Here we just tell the task that it should run on the client computer. Again we give in the correct Automation pre-boot environment.

Click Next and then finish. Step two is now also completed.

Step 3: Retrieve OS Version and Hardware Profile

Click to view.

Here we run a script to find the correct OS version and the hardware path.

The complete script is as follow:

REM Retrieve OS Version and Hardware Profile


REM Find the OS path and set the %ProductionDrive% and %ProductionRoot% variables
call .\HII\FindOS.bat

REM Retrieve OS Version
XCOPY /E /V /H /R /Y /f %ProductionDrive%\OS_Ver.txt .\Temp\HII\%ID%.osv

REM Retrieve Hardware Profile
.\HII\tap.exe /O .\Temp\HII\%ID%.pmq

exit 0

This step will only succeed when you previously collected the drivers of the PC, Because the osv version should be known.

Click Next and then Finish to confirm changes.

Step 4: Prepare Drivers for destination computer

Click to view.

Now we prepare the drivers. The complete script is:

.\HII\DriverPrep.exe -src:.\HII\Drivers -dst:.\Temp\HII\%ID%D -ver:.\Temp\HII\%ID%.osv -pmq:.\HII\Logs\%ID%D.log

Click Next to continue. Then again click Next and then Finish.

Step 5: Install Drivers and Windows Packages

Click to view.

This is the difficult step. The complete text of the script is as follow:

REM Install Drivers and Windows Packages
SET DriverSource=.\Temp\HII\%ID%D
SET PackageSource=

REM Assign drive letters to new partitions
diskpart /s .\HII\diskpart.txt

REM Find the OS path and set the %ProductionDrive% and %ProductionRoot% variables
call .\HII\FindOS.bat

REM Prepare an unattend.xml file for pkgmgr driver installation
echo ^<?xml version="1.0" encoding="utf-8"?^> >%temp%\unattend.xml
echo ^<unattend xmlns="urn:schemas-microsoft-com:unattend"^> >>%temp%\unattend.xml
echo   ^<settings pass="offlineServicing"^> >>%temp%\unattend.xml
echo     ^<component name="Microsoft-Windows-PnpCustomizationsNonWinPE" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"^> >>%temp%\unattend.xml
echo       ^<DriverPaths^> >>%temp%\unattend.xml
echo         ^<PathAndCredentials wcm:action="add" wcm:keyValue="0"^> >>%temp%\unattend.xml
echo           ^<Path^>%DriverSource%^</Path^> >>%temp%\unattend.xml
echo         ^</PathAndCredentials^> >>%temp%\unattend.xml
echo       ^</DriverPaths^> >>%temp%\unattend.xml
echo     ^</component^> >>%temp%\unattend.xml
echo   ^</settings^> >>%temp%\unattend.xml
echo   ^<cpi:offlineImage cpi:source="wim:c:/vistadist/install_x86.wim#Windows Vista BUSINESS" xmlns:cpi="urn:schemas-microsoft-com:cpi" /^> >>%temp%\unattend.xml
echo ^</unattend^> >>%temp%\unattend.xml

REM Install drivers using pkgmgr.exe and unattend.xml
ECHO Installing Drivers from "%DriverSource%"...
MKDIR %temp%\tempdrv
.\WAIK\Tools\%PROCTYPE%\Servicing\pkgmgr.exe /o:"%ProductionDrive%;%ProductionRoot%" /n:"%temp%\unattend.xml" /s:%temp%\tempdrv /l:".\HII\Logs\%ID%_pkgmgr_drivers.log" /quiet
RMDIR /S /Q %temp%\tempdrv

REM Install Windows packages using pkgmgr.exe
ECHO Installing Windows Packages from "%PackageSource%"...
FOR %%i IN ("%PackageSource%\*.cab") DO (
  ECHO Installing %%i
  MKDIR %temp%\%%~ni
  .\WAIK\Tools\%PROCTYPE%\Servicing\pkgmgr.exe /o:"%ProductionDrive%;%ProductionRoot%" /ip /m:"%%i" /s:%temp%\%%~ni /l:".\HII\Logs\%ID%_pkgmgr_update_%%~ni.log" /quiet
  RMDIR /S /Q %temp%\%%~ni
)

exit 0

Click Next, Next and then Finish.

Step 6: Modify the Configuration.

This task will enable you to get the correct client name and to give in the correct settings that you want for your environment.

Make sure you change the domain name. The script will try to connect you to my domain, and that will not happen. Sorry.

Step 7: Auto Authorize

Click to view.

The last task is the Auto Authorize. It's a Cscript that starts a local VBS file. Actually this script will help you to get rid of the activation inside Microsoft Vista. After running this script you do not need to activate Vista. The script only runs when you have a valid Vista key inserted.

When the job is finished, the a final task should be to reboot the client. You also can now import user settings that you have extracted from the old user computer if you like, or deploy various other software to the client.

Now you have all the correct tasks inside your job to be successful in deploying Vista hardware independent images.

Deployment Console, Part 8: Building a Clean, Lean Windows XP Machine with DS

Deployment Console, Part 10: Creating Windows WIM and Catalog Files