Video Screencast Help

HII Tools 3.2.0 for Deployment Server 6.8 SP2

Created: 13 Nov 2007 • Updated: 07 Jul 2009 | 20 comments
CondorMan's picture
+1 1 Vote
Login to vote

HII Tools now supports Windows Vista!
The new HII Job Wizard makes Hardware Independent Imaging a breeze.
Driver Collection job populates your Driver Library for you.

Improvements to previous versions:

  1. Supports Windows 2003 x86 SP2
  2. Supports Windwows XP/2003 x64 SP2
  3. Supports Windows Vista
    • Install boot critical drivers to Vista while still in WinPE. You no longer need to re-create your image to support new Mass Storage drivers.
    • Install Hotfixes to the newly imaged computer while still in WinPE.
  4. HII Job Wizard, easily create jobs to manage your Hardware Independent Imaging.
  5. Driver Collection job is back and better than ever.
    • More reliable
    • Better performance

To enable Vista support, you will need to update your WinPE follow the instructions in Install Drivers and Packages to Vista in WinPE

After you run the installer, see the HII Tools Quick Start for configuration instructions.

This version has been tested on Deployment Server 6.8 SP2. Vista support requires 6.8 SP2 or later. XP/2003 support may work on earlier versions of 6.8, but it is untested.

License: AJSL
By clicking the download link below, you agree to the terms and conditions in the Altiris Juice Software License
Support: User-contributed tools on the Juice are not supported by Altiris Technical Support. If you have questions about a tool, please communicate directly with the author by visiting their profile page and clicking the 'contact' tab.

Comments 20 CommentsJump to latest comment

riva11's picture

Nice work CondorMan, just one question about requisitions, can be used also for Deployment Server 6.2 ? Thanks.

+2
Login to vote
CondorMan's picture

In order to deploy Windows Vista with HII Tools, you will need Deployment Server 6.8 SP2.

To deploy all other Operating Systems with HII Tools, you will need at least Deployment Server 6.8.

HII Tools will not install on any version of Deployment Server older than 6.8.

+1
Login to vote
EricVincent's picture

Hi Condorman,

Thank you for your nice work on this subject.
Just performed some tests of this new version ...
I just have a problem in the HII deployment task : driverprep 3.2.0 seems to fail when it tries to read the PMQ file. The log file shows the following :

Creating the destination directory
Establishing database connection using DSN=Altiris eXpress Database
Reading from file: C:\Program Files\Altiris\eXpress\Deployment Server\TEMP\HII\5000004.OSV
Reading from file: C:\Program Files\Altiris\eXpress\Deployment Server\TEMP\HII\5000004.PMQ
Finished.

And no driver is copied in the temporary folder, which only contains an empty HAL subfolder.

Of course after that, no driver is copied onto the destination computer. Any idea ?

Thanks by advance for any help.

0
Login to vote
CondorMan's picture

Please zip up the contents of your HII and Temp\HII folders and e-mail them to hiitools@gmail.com I will be able to run it in debug mode to find out what it is doing.

+1
Login to vote
Andrew Souter's picture

Who developed the HII add on?

is this something Altiris have done or is it 3rd party.

0
Login to vote
srpomeroy's picture

[quote=Andrew Souter]Who developed the HII add on?

is this something Altiris have done or is it 3rd party.[/quote]

CondorMan created it.

It is not supported by Altiris:

Support: User-contributed tools on the Juice are not supported by Altiris Technical Support. If you have questions about a tool, please communicate directly with the author by visiting their profile page and clicking the 'contact' tab.

0
Login to vote
rmarkeson's picture

Any ideas for this problem?

0
Login to vote
Magnum45's picture

I have this same exact problem. I will zip up the files and send them too you.

0
Login to vote
srpomeroy's picture

Where/How does the deployment server get the sysprep.inf answer file? I see that it is created right after downloading the disk image. But it is not listed as a script that is run.

I am trying to add some specialty drivers for my HP laptops. I can get the drivers copied over to the laptop successfully.

Here is the line I added to the Copy Drivers and HAL script:

REM Copy Drivers and HAL

REM Delete AClient.cfg if it exists
.\rdeploy\dos\firm delete PROD:\aclient.cfg

echo Copying Driver files...
.\RDeploy\DOS\firm -recurse copy .\Temp\HII\%ID%D PROD:\Drivers

echo Copying HAL files...
.\RDeploy\DOS\firm -recurse copy .\Temp\HII\%ID%D\HAL PROD:\Windows\System32

echo Copying OEM files...
.\RDeploy\DOS\firm -recurse copy .\HII\$OEM$ PROD:\Sysprep\i386\$OEM$

echo Copying HP extra drivers
.\RDeploy\DOS\firm -recurse copy .\HII\WinXP\Drivers\HP PROD:\Drivers

echo Adding driver installation commands to cmdlines.txt file...
REM SetupCopyOEMInf.exe will add a reference to each driver into the Windows\inf directory
echo "SetupCopyOEMInf.exe PROD:\Drivers">>%ProductionDrive%\Sysprep\i386\$OEM$\cmdlines.txt
REM WatchDriverSigningPolicy.exe will disable Driver Signing
echo "start WatchDriverSigningPolicy.exe">>%ProductionDrive%\Sysprep\i386\$OEM$\cmdlines.txt
REM remove all devices
echo "devcon remove *">>%ProductionDrive%\Sysprep\i386\$OEM$\cmdlines.txt
REM rescan all devices
echo "devcon rescan">>%ProductionDrive%\Sysprep\i386\$OEM$\cmdlines.txt

So in theory the SetupCopyOEMInf.exe should pickup all these new driver additions and add them... Right?

0
Login to vote
rmarkeson's picture

I too have the issue with the pmq file and the driver files not being prepared.

Has there been a resolution to this? Is it a security issue on the server?

Thanks in advance.

0
Login to vote
farbeyond's picture

Hi Guys,

Does anyone have any problems with the "Collect Drivers" job, I've ran, it runs OK but it's status is stuck at "Complete cataloging new drivers"

Cheers

0
Login to vote
carlsson's picture

Hi I have a drivercollect problem. It doesn't do anything ? I've checked the script and it does everything before the drivercollect.exe and everything after it but no drivers ?
Are the commands after the exe correct ?

I also have an issue that when I install Hii tools it affects my winpe boot, it stumbles at DHCP just before the aclient install, if i then uninstall HII tools it starts working again ???

Update... seems it was "permissions" stopping the creation of folders when the collect job runs on the client and needs to create a folder on the ds server....

C

Hojiblanca

0
Login to vote
bmooney2008's picture

When running the collecting driveres job, it runs succesfully in the console, but the drivers are not coping to the Altiris server correctly.
There are 2 locations that are in my Altiris installation directory:

%altiris share%\eXpress\HII\Drivers
%altiris share%\eXpress\Temp\HII

I am seeking clarification on the difference between these 2 locations. Are both of these locations needed or just one? I seems like the scrupts provided by the HII tool use both of them. It appears that the files are being copied to the \eXpress\HII\Drivers location, folders are created under %altiris share%\eXpress\Temp\HII however no files are being copied into them. For example I just ran this job and it created \eXpress\Temp\HII\5000679C and 1 subfolder with a .inf file.

I am able to image and reimage all day but when I reimage it seems like the scripts provided by the HII tool are not copying the drivers to the imaged PC. I am very confused here and any help would be appreciated.

0
Login to vote
bmooney2008's picture

I have a question for you. I have set up a test environment with DS 6.8 SP2 and attempting to get HII 3.2.1 to work. In the test environment when I run step 2 of the HII job wizard process I get errors. When I execute this on our production using HII 3.2.0 (isnt working entirely) DS which was set up on ver 6.8 build 206, the OS and product key information gets auto populated in the boxes via a drop down menu and allows me to continue. I have installed the new version in a test environment. When I run this step, there is no information in the drop down menu. Because this information cant be NULL the step will error out Any advice would be appreciated. Lastly do you have an email address I can send you these errors to? I have screen shots.

0
Login to vote
carlsson's picture

HI I had the same issue and the fix is to uninstall and then reinstall HII Tools and when you do a reinstall it will prompt you for operating system which you will need the disk for and the product key. You can skip past this but obviously if you do you get this error.
All the jobs you have created previously will still be there so during the install if you rerun the create jobs part you'll get duplicate jobs
Also you need .NET 2.0 installed

HTH C

Hojiblanca

0
Login to vote
mben's picture

While running the Distribute independent hardware job, the 3rd scrip after the distribute image task, I receive an Error #2 message that’s states “ Preparing drivers for destination PC.” There is a Temp\HII directory created on my DS server but for some reason the script is failing. I’m not a script master so I having some issues understanding this script. I would like some insight on what this script is trying to do.

REM Prepare Drivers for destination computer

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

0
Login to vote
CondorMan's picture

In your eXpress share under HII\Logs, you will have a log file that ends in D.log. Please e-mail that log file to me at hiitools@gmail.com and I will be able to see what it is failing on.

+1
Login to vote
Big_Jim's picture

The new Version works great Condor, but I am having an issue with the SQL piece to it. I am trying to automated it and I read your article on the "HII Tools Driver Library Maintenance", and made it all the way to the Automated section. The problem is..Where do I find the Event ID, and where do I copy that "trigger" you put out there?

Thanks,
Jim

0
Login to vote
CondorMan's picture

To get the Event ID, run this query (replacing JobName with the actual name of your job): SELECT event_id FROM event WHERE name = 'JobName'

There are 4 examples of different triggers that you can use. Copy the SQL Query that matches the trigger that you want to create and follow the instructions to customize it.

0
Login to vote
bmooney2008's picture

When I run this step it takes a long time to finish. What is the average time for this process to complete? I just ran this job and it sat there for nearly 2 hours.

After the 2 scripts and copy file to run the job seems to get stuck on create disk image. It just sits there with status "sending signal to restart"
I let is sit there for nearly 2 hours and I had to manually restart for the image process to kick off.

0
Login to vote