Deployment Solution

Migration User

Dec 15, 2008 01:53 PM

Supposedly there is an updated version of tap.exe that is dated from from 06. Do you know if this fixes the WinPE 2.1 issue. I have downloaded Embedded tools from the sp2 release and it only gives me an old version of TAP that only works with 1.6.
2.1 loads dramatically faster on my systems.

Migration User

Jul 11, 2008 10:45 AM

HII Tools hasn't been tested for WinPE 2.1 yet. I have been busy with other projects. I have heard that there is an updated version of TAP.EXE that supports WinPE 2.1, but I haven't verified this myself.
By the way, make sure you are using HII Tools 3.2.1, since it is the latest version.

Migration User

Jul 07, 2008 05:26 PM

When I run a distribute hardware image on the "Retrieve OS Version and Hardware Profile" I get a error "Incorrect Function"
script:
--------------------------------------
REM Retrieve OS Version and Hardware Profile
REM Retrieve OS Version
.\RDeploy\Windows\firm copy PROD:\OS_Ver.txt .\Temp\HII\%ID%.osv
REM Retrieve Hardware Profile
.\HII\ta.exe /O .\Temp\HII\%ID%.pmq
----------------------------------------
Script Operating System: Windows
Script Run Location: On the Client Computer
Automation pre-boot environment:Default Automation (Auto-Select) its Win_Pe2.1

Migration User

Jan 11, 2008 09:57 PM

Thanks condorman for the tool set itself and dharric for all your work in helping me better understand the tools. I too was able to get the driver collection working with a bit of tweaking but was having trouble with the deployment and in particular the copying of the HAL to the client.
At HII setup I selected my supported OS's that I would be using and the OS Ver folders were created to contain the HAL / system files for each version. When came time to copy the HAL files for the image that I had created, the %ID%.osv file had the correct information but the HAL files that were copied to the client were wrong and prevented the PC from booting. Does anyone know where these files could be sourced from as the weren't the ones in the
'.\HII\Drivers\HAL\NTX86.5.1.SP2' folder. Any help would be appreciated.

Migration User

Nov 07, 2007 08:23 AM

Was the Copy Driver and Hal script successful for you?
B. Brooks

Migration User

Nov 06, 2007 05:37 PM

I have uploaded the GetHAL.exe, you can get it at http://juice.altiris.com/download/2830/gethal

Migration User

Nov 05, 2007 07:32 PM

The installer checks the size of the HAL files to make sure they are the correct version. It is possible that the Norwegian HAL files are a different size.
I will upload the GetHAL.exe that I created to do the HAL collection and you will be able to run it manually, thus bypassing the file check. I will post a reply to this comment when it is available.

Migration User

Nov 05, 2007 07:24 PM

Actually, in Deployment Server 6.8 and above, the default sysprep.inf file now includes all the tokens required to configure all the computer settings. So, the MakeInf is no longer needed. I recommend that you use the default sysprep.inf.
Make sure that the computer record shows that the computer is a member of the appropriate domain and that credentials are supplied in the Domain Accounts List (Under Tools>Options>Domain Accounts)

Migration User

Nov 01, 2007 10:42 AM

Help!
I'm trying to install HII-tools, and check for Windows x86 SP2 support. Then installer ask for Windows installer files, but will not accept the files from my CD (Windows XP x86 SP2 Volum License Norwegian)Is the language a problem?
Please, can anyone help me?

Migration User

Oct 30, 2007 08:33 AM

HJ,
I do not see this folder. I have a .\temp\hii folder but no .\hii\temp folder. In the .\temp\hii folder, i see a couple of PMQ files, a TON of cfg files, and numerious .bat files. Is this the directory you are referring to?
B. Brooks

Migration User

Oct 22, 2007 04:28 PM

Dharric,
Thanks for the scoop on the "Microsoft Desktop Deployment Resource Kit" it's on the way. In the meantime, in the "Deploy Hardware Independent Image" Job on the "Distribute Disk Image" Task, I have selected:
Prepared using Sysprep = Checked
Advanced settings.... (Used old sysprep.inf from the Makeinf of HII tools for 6.5) and it is not joining the domain with the SQL queries. What are you using? I also need to add machines to multiple domains, what would you suggest?
HJ

Migration User

Oct 22, 2007 04:07 PM

BarBrooks,
I got the error 1 message as well. I cleaned out the .\HII\temp folder of all osv, pmq, driver folders and re-ran. I think the error means a file cannot be copied because it already exists.
HJ

Migration User

Oct 18, 2007 08:12 PM

dharric,
First off let me tell you thanks for the tips you posted. They helped me get further than I have gotten with this tool before. With that said, i am having a problem when altiris gets to the final script "copy driver, hal, and oem files" it gives me an error code of 1. Any suggestions?
Another question i have for you is that,in the Prepare Drivers job, you added the .\Temp\HII\%ID%DSystem32. What is the "D" for prior to the System32? Does it need to be added in the "Copy Driver, Hal" script?
Thank you in advance for any help you can offer.
B. Brooks

Migration User

Oct 09, 2007 11:22 PM

If you need help capturing drivers you should purchase the Microsoft book, "Microsoft Windows Desktop Deployment Resource Kit". It includes several scripts that help you capture driver files based on their inf. The directory structure is just a bunch of folders with numbers as their names, for each driver set. The script that creates the directory structure is very easy to use, just cd to the directory first.

Migration User

Oct 04, 2007 11:37 AM

I understand the capture drivers job is no longer included, but what is the best way to collect the drivers also what does the directory structure look like in the HII directory?

Migration User

Sep 27, 2007 12:34 PM

After step 2, on 'Create Hardware Independent Image', run the script ‘Manual Driver Sort.bat’, which will sort the \HII\Drivers directory so that the subsequent image deployment jobs can use those directories for driver copy purposes. The driver copy jobs will fail without this sort.

Migration User

Sep 25, 2007 01:43 PM

Ok, here's what worked for me:
Create Hardware Independent Image:
1. Make certain you have installed the xp tools and copied the ta.exe and tap.exe files to the Deployment Server\HII folder.
2. For the 'Create Disk Image' job go to > Sysprep settings > Advanced Settings > 'Enable mass storage device support using following'. Then modify the path to the MSD.inf file, that was created by the 'Prepare Storage Drivers' script. You will have to find the folder that was created by that script and hard code the path to the MSD.inf file (obviously this means you will need to run this task, even though it will error, to have this folder and contents created first)
Deploy Hardware Independent Image:
1. In the 'Distribute Disk Image' job select 'Automatically perform configuration task after completing this task' (this is what actually carries out the rdeployt reimage after copying down the image file). And of course you will have to enter your xp license key also.
4. For script 'Retrieve OS Version and Hardware Profile', in 'Choose the script operating system', choose Windows instead of Dos.
5. For script 'Prepare Drivers for destination computer', add this line to the beginning of the script code--before .\HII\DriverPrep.exe command:
md .\Temp\HII\%ID%Dsystem32
Because if the folder is missing you get a status code 1 error message. By the way that's not a typeo, there's no '\' before system32.
6. Finally for 'Copy Driver, HAL, and OEM files to production', in 'Choose the script operating system', choose Windows instead of Dos.
This may seem like a lot of work, but it would be a lot worse if we had to roll our own solution for standardizing images. So thanks condorman.

Migration User

Sep 25, 2007 09:42 AM

Ok, so I'm getting further with the tool. I'm now able to image a machine by simply hard coding the inf path in the advanced section for sysprep settings of the "Create Disk Image" job. I'm also able to reimage and get the second job to run in the "Deploy Hardware Independent Image" task. I had to check the "Automatically perform configuration task ..." and reset the sub jobs as windows jobs under the "Choose the script operating system" section. However it now stops at the second script job "Prepare Drivers for destination computer". I've not modified the command for this job, but the log in HII\Logs states, "Could not find a part of the path '.\TEMP\HII\5001096Dsystem32\hal.dll'.
Warning 1: Unable to copy HAL files". As you can see it has an invalid path. When I look at the osv file it has NTx86.5.1 SP2, which makes sense because the hal files are on .\HII\Drivers\HAL\NTX86.5.1.SP2 entry (which is where the HII tools installed them to). Anyone?

Migration User

Aug 30, 2007 01:00 PM

I apologize for my delay in response, I have been very busy. The documentation is very out of date. My goal with the HII Tools has always been to simplify the process of creating a Hardware Independent Image. With this release of HII Tools, I have taken care of some of the steps for you. Here is a summary of the changes made.
Steps you no longer need to worry about:
Step 1 is done by the installer.
Step 3 is done by the installer.
Step 4 is now handled via aclient.
Step 5 is no longer needed.
Steps that are still required:
Step 2 is still required
Step 7 now only requires you to modify the Create Disk Image task to set the OS and Key.
Step 8 now only requires you to modify the Distribute Disk Image task to set the OS and Key.
Step 6 is not currently required because I removed the Capture Drivers job until I could iron out some bugs in the DriverCollect.exe utility. I have re-written DriverCollect.exe to be much more robust and I think it is working pretty well. I hope to release a new version of HII Tools soon that will have this feature again.

Migration User

Jul 11, 2007 03:55 PM

I was getting the same errors as above and they are in fact due to .NET Security but there is away around it without modifying the code. I found the answer here.
The Caspol.exe utility comes with .Net it is located at C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322
C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727
In .Net 1.1 and 2.0 respectively I believe this only needs to be run on .NET 2.0.
From a command line I entered the following command on the client machine:
CasPol.exe -m -ag 1.2 -url file://Server_Name/express/* FullTrust
This was very exciting news to me at the time however I am still unable to get Driverprep to run correctly.
Amongst others it seems that I get this error the most:
Invalid parameter specified
DriverPrep 3.1.0
This utility will read the specified PMQ File and copy files from the source Driver Library to the destination location
DriverPrep.exe -src:source -dst:destination -ver:osverfile { -pmq:pmqfile | -msd:msdfile }
source Root path (Relative or UNC) of the driver to copy
destination Root path (Relative or UNC) to sort the driver into
osverfile .VER file that contains OS Version information
pmqfile .PMQ file to use in order to determine which drivers to copy
msdfile .INF file to use as the base for creating an MSD.INF file
If this helps anyone get to the next step please, please post for the rest of us poor souls.
Ryan

Migration User

Jun 29, 2007 10:51 AM

Unhandled Exception: System.Security.SecurityException: Request for the permissi
on of type 'System.Security.Permissions.SecurityPermission, mscorlib, Version=2.
0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' failed.
at System.Environment.Exit(Int32 exitCode)
at DriverPrep.Program.Main(String[] args)
The action that failed was:
Demand
The type of the first permission that failed was:
System.Security.Permissions.SecurityPermission
The first permission that failed was:

Migration User

Jun 28, 2007 04:39 PM

that you do not have .NET Framework 2.0.50727 or higher installed on the DS server that you are executing this script from...ok, I installed this on the server and now I receive Error Code 1
I'm still not seeing any of the drivers being copied into the .\HII\Temp directory so this script isn't executing at all or something isn't working (but I do see the log file being created)

Migration User

Jun 27, 2007 01:41 PM

DriverPrep.exe fails to run and causes the drivers not to be copied down to the deployed OS. The error that I'm receiving is -2146232576 and on the client computer is shows "This program cannot be run in DOS mode". All settings for the "Prepare Drivers for destination computer according to hardware profile" script remain the default as after installation of the HII tool. They are as follows:
REM Prepare Drivers for destination computer according to hardware profile
.\HII\DriverPrep.exe .\Temp\%ID%.pmq .\HII\WINXP .\Temp\%ID% > .\HII\Logs\DriverPrep-%ID%.log
Choose the script OS = Windows
Script Run Location = Locally on the DS
Run when the agent is connected = checked
Client Run Environment = Automation pre-boot env.
Any help would be greatly appreciated

Migration User

Jun 20, 2007 01:40 PM

Same issue here. I finally got the capture to work but during the image deploy, the Firm of the drivers never takes place. This is a nice concept and would be great if it worked out of the box. Guess this is why Altiris won't support it. It's starting to remind me of working with LiveState (DeadState). "It's supposed to work, just don't know why it isn't."

Migration User

Jun 18, 2007 10:57 AM

I followed the instructions that are posted which let me install the program. I ran the Driver collect which appears to be working. But it isn't installing the drivers after I make the HII image and deploy it? Do I have to manualy put the drivers on the C: drive? Any help with this would be most appreciated!

Migration User

May 30, 2007 03:42 PM

I have also been struggling with getting this to work but I think I have finally succeeded. Here are the steps I took to do so.
1. Uninstall 6.8 HII Tools
2. Install 6.5 HII tools you need to use the wise editor to remove the Welcome dialog to get past the error message stating you are installing the tools to the wrong version
3. Install 6.8 HII tools (3.1.0)
4. Install the DS Remote Agent to the client you are going to capture the drivers from
5. Install .Net 2.0 (I also installed 1.1 but it did not work until I installed .Net 2.0)
6. Use the script from scorliss
REM Run DriverCollect.exe to collect all drivers to

 \\server\eXpress\Sysprep\Drivers
%temp%\DriverCollect.exe -Src:"C:" -Dst:\\%DSSERVER%\eXpress\Temp\DriverCollect\%ID%\ -UpdateFiles
if errorlevel 1 Goto ErrorRunningDC
if errorlevel 0 Goto DCSuccess
if errorlevel -1073741515 Goto ErrorNoDotNet

Migration User

May 30, 2007 12:29 PM

This does not work!! The download is incomplete, and the documentation does not apply. I have written to "hiitools@gmail.com", and have gotten no response. This has so much potential, and I bet if you have DS 6.5 the old version of this software would work great, but oh well for the rest of us. If anyone knows how & where to get this software, and get it working please let me know, Thanks!!

Steen Bogø

May 25, 2007 08:04 AM

Hi
I have the same problem. When i try to use the sysprep file from step 5 i get an error not files to copy.
Any solution??

Migration User

May 22, 2007 12:28 PM

Ok, so I got the new version of HII Tools installed with the help of this forum. Thanks! Now I am following the help file and am having a problem on step 7 of getting started. It says I should configure the "create image" job by modifying it. Step 3 says to click the sysprep settings. I assume this is meant to be advanced settings since thats all i have. Then step 4 says to enable "Use the following as an answer file for Sysprep" and point it to your inf. Problem is that I don't have that choice. When I click on Advanced Settings, all I get is Sysprep mass storage options and command line switches. Where am I supposed to go to point the job to my inf???

Migration User

May 10, 2007 03:01 PM

Thanks for the idea.

Migration User

May 10, 2007 02:43 PM

If you download the HII for 6.5, you can open the MSI with WISE and convert it to a WSI project. This will extract all of the files including the exported jobs for Capturing Drivers.
I would like to note though, looking at the jobs that do get created it would appear that the creator has updated the capture image job to include all of those steps. I have not tested this as of yet. If this is the case, then it would appear the CHM file needs to be updated.
Hope this helps
Cheers!

Migration User

May 10, 2007 02:25 PM

Could you, or anyone, send the Capture Drivers job? It didn't get installed for us.

Migration User

May 10, 2007 11:57 AM

Are there any issues when using this with XP x64? Don't we need different files in step 3?

Migration User

May 09, 2007 02:19 AM

Hi,
I believe that the /noMS switch triggers that drivercollect should not collect builtin Microsoft drivers...
\Thomas

Migration User

May 08, 2007 12:05 PM

Here is the script I am using:

REM Run DriverCollect.exe to collect all drivers to \\server\eXpress\Sysprep\Drivers
%temp%\DriverCollect.exe -Src:"C:" -Dst:\\%DSSERVER%\eXpress\Temp\DriverCollect\%ID%\  -UpdateFiles
if errorlevel 1 Goto ErrorRunningDC
if errorlevel 0 Goto DCSuccess
if errorlevel -1073741515 Goto ErrorNoDotNet

I am however having trouble with the "Distribute Hardware Independent Image" job. I can not get the tap.exe task or the driverprep.exe task to work properly.

Migration User

May 08, 2007 09:59 AM

When I attempt to run the capture driver job, Error 254 is returned. Placed a pause in the script to see where it fails at and it appears that it fails at the lines listed below. Can anyone tell me what the /NoMS stands for? What could be causing the failure? Anyone else having this problem?

REM Run DriverCollect.exe to collect all drivers to \\server\eXpress\Sysprep\Drivers
%temp%\DriverCollect.exe \\%DSSERVER%\eXpress\Temp\DriverCollect\%ID%\ /NoMS > \\%DSSERVER%\eXpress\HII\Logs\DriverCollect-%ID%.log
if errorlevel 1 Goto ErrorRunningDC
if errorlevel 0 Goto DCSuccess
if errorlevel -1073741515 Goto ErrorNoDotNet

B. Brooks

Migration User

May 04, 2007 03:57 PM

This method worked perfectly! thank you so much!
B. Brooks

Migration User

Apr 27, 2007 12:19 PM

With the MSI editor I went to dialogs and removed the Welcome dialog. After that it installed just fine.

Migration User

Apr 26, 2007 07:56 PM

Can you tell me how to edit the MSI? What settings need to be changed? What did you use to edit the MSI?
B. Brooks

Migration User

Apr 26, 2007 02:49 PM

That is exactly what i did. It works fine in my environment.
regards
Erik

Migration User

Apr 26, 2007 12:25 PM

One way that worked for me was installing the 6.5 HII tools then installing the 6.8 HII tools on top of that. You will have to edit the 6.5 version with the Wise MSI Editor in order to bypass the version check but so far I haven't had a problem and it has the rest of the files that are needed. Also this is my first time using HII tools so this may not be the best way to proceed.

Migration User

Apr 10, 2007 08:50 AM

I have the same problem, it seems i have only a partial install. So if anyone finds out what the problem is, please update.
Thanks

Migration User

Apr 04, 2007 12:32 PM

The HII tools that we installed (3.1) appears to be a partial installation. How can this be? Can anyone point us to the documentation that will show us the information included in the run scripts AND can you assist with our "partial install" problem?
1. why is the "Make Sysprep INF file" not appearing in the start menu? How can it be added? Why wasn’t it automatically installed?
2. Why is the "Capture Drivers" job and the "Sort Drivers" job not appearing in the Sample Jobs folder?
3. What is the relationship between drivercollect.ext and driverprep.exe?
4. What does the "Capture Drivers" job/run script entail? What does the "Sort Drivers" job/run script entail?
5. Why isn't the Hardware Independent Imaging folder appearing under the Samples job folder?

Migration User

Apr 04, 2007 12:22 PM

I, too, have had this problem and have posted to this forum as well as emailed the developer. The sysprep utility is not the only thing "missing" when compared to the instructions. The Capture Driver jobs that are supposedly created when installing HII is not created. This does not create a major problem for me, if only I could see some sample scripts for this job.
I am attempting to "sell" my coworkers on the ease of use with this tool, however, until I can get some feedback, my project is put on hold.

Migration User

Mar 28, 2007 02:02 PM

After installing the HII Tools, it created a Jobs Folder under Samples, and included the following jobs: Create Hardware Independent Images and Deploy Hardware Independent Images.
It did not create the sample job called Capture Drivers for Hardware as described in the Documentations (in other words I have 2 sample jobs instead of 3).
Is there any way to get this sample job so that I can collect drivers from different machines?
Another quick question, will this process work when running the Linux automation environment?

Migration User

Mar 23, 2007 01:31 AM

I agree, I'm committed to making the HII but it seems that tools necessary aren't a part of the package. Please check and assist.
Thanks

Migration User

Mar 22, 2007 03:01 PM

Hi CondorMan,
I haven't had the opportunity to try out HII Tools in my previous projects, but am looking forward to finally being able to give it a go.
I downloaded and installed version 3.1.0 for DS 6.8, and am working my way through the Getting Started steps in the CHM file.
Steps 1-4 went fine, but I'm stuck on Step 5 - Create Sysprep.INF. It refers to something in the Start menu called "Make Sysprep.INF File", which I can't seem to find. I also looked in the HII folder in the express share, but I don't see it there either. Where is it located?
Also, I have used setupmgr.exe in the Sysprep tools to create sysprep.inf files in the past. How does the "Make Sysprep.INF File" tool differ from it?
Thanks,
Jason

Migration User

Mar 20, 2007 04:13 AM

Hi Condorman,
is there any changelog or alike for this update?
\Fraefel

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.

HII Tools 3.1.0 for Deployment Server 6.8

Tags and Keywords

Comments

Related Entries and Links