Video Screencast Help

HII Tools 3.2.1 for Deployment Server 6.8, 6.8 SP1, and 6.8 SP2

Created: 07 Feb 2008 • Updated: 07 Jul 2009 | 71 comments
CondorMan's picture
+2 2 Votes
Login to vote

The new HII Job Wizard makes Hardware Independent Imaging a breeze.

Driver Collection job populates your Driver Library for you.

Features:

  • Supports Windows XP x86 SP3
  • Supports Windows 2003 x86 SP2
  • Supports Windwows XP/2003 x64 SP2
  • 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.
  • HII Job Wizard, easily create jobs to manage your Hardware Independent Imaging.
  • Driver Collection job to reliably and efficiently gather drivers from your managed computers.
  • Supports driver injection to a custom location
  • More reliable and flexible

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 works on Deployment Server 6.8, 6.8 SP1, and 6.8 SP2. Vista support requires 6.8 SP2 or later.

Comments 71 CommentsJump to latest comment

CondorMan's picture

It looks like I accidently included two new features that I am developing for a future version. In the Job Wizard when you create a Collect Drivers Job, you are able to enable Automatic scheduling of the job on computers with new devices. Also, in the console under Tools you will see HII Tools>Driver Library Maintenance.

If you try to use these features you will get an error message. You can overcome this error by running the following SQL Query against the Deployment Server Database: "CREATE TABLE hii_settings (CleanupRun smalldatetime, CleanupScheduled smalldatetime, CollectStatus tinyint, AutoCollectMode tinyint, AutoCollectJob int, AutoCollectDay tinyint, AutoCollectHour tinyint, AutoCollectMinute tinyint, AutoCollectPM bit)" (without quotes).

Again, these are untested features that were intended to be held for a future version. But now that they have been leaked, I welcome any input about them :^)

+1
Login to vote
rstaats's picture

Excellent. Hi-5 to CondorMan!

Now I just need WinPE to work for me >.>

0
Login to vote
CondorMan's picture

I found a typo in the query provided earlier, please use this one: "CREATE TABLE hii_settings (CleanupLastRun smalldatetime, CleanupScheduled smalldatetime, CollectStatus tinyint, AutoCollectMode tinyint, AutoCollectJob int, AutoCollectDay tinyint, AutoCollectHour tinyint, AutoCollectMinute tinyint, AutoCollectPM bit)" (without quotes).

+1
Login to vote
erikw's picture

You are doing a great job for me.
i use HII tools a lot, and it is a real time saver when it is installed and works correctly. i just need some time to get this new version.

Regards
Erik
www.dvs4sbc.nl

Regards Erik www.DinamiQs.com Dinamiqs is the home of VirtualStorm (www.virtualstorm.org)

*************************************************************
If your issue has been solved, Please mark it as solved
***********

0
Login to vote
CondorMan's picture

I was just made aware of some missing components in the installer. I have re-created the installer and re-uploaded it.

If you installed version 3.2.1 with the original installer, you will need to re-install using the new installer for the HII Tools to work properly.

+1
Login to vote
bmooney2008's picture

is HII 3.2.1 compatible with all versions of SQL? Will it run on Microsoft SQL Express 2005 or should I be using MSDE 2000 SP4?

0
Login to vote
CondorMan's picture

It is compatible with both. I personally would recomment SQL Express for you since it is less restricted than MSDE.

+1
Login to vote
CondorMan's picture

I have created an article you might be interested in that explains how to install SQL 2005 Express to work with Deployment Server. You can find it at http://juice.altiris.com/article/4661/install-and-...

+1
Login to vote
bmooney2008's picture

I am having an issue with the scripts that run after the image is deployed.

echo Configuring PreSetup.exe to launch before setup.exe
.\RDeploy\DOS\firm copy PROD:\Windows\system32\setup.exe PROD:\Windows\system32\setup.0
.\RDeploy\DOS\firm copy .\HII\PreSetup.exe PROD:\Windows\system32\setup.exe

what is presetup? where is it located?

this is the log that is generated when the script runs. the log file is under:

D:\Program Files\altiris\eXpress\Deployment Server\RDeploy\DOS\firm.log

Error description:
The file could not be opened.

Possible causes:
A file that was expected to exist does not exist.
You do not have permission for this operation on the file or directory.

Possible resolutions:
Make sure the file exists and is accessible.
If the missing file is part of this program, reinstall the program.
Fix the permissions on the file or directory.

==================== Technical details ====================

Logfile = created Tue Mar 4 15:52:06 2008
Build = FIRM.EXE 6.8 (8192)
Cmdline = F:\.\RDeploy\DOS\FIRM.EXE copy .\HII\PreSetup.exe PROD:\Windows\system32\setup.exe

Status = 41 (0x29)
Source file = imglib\fs\native\nativefs.cpp
Line number = 806 (0x326)
Stack trace = 0x69bab7 0x69b26f 0x62cabe 0x63435f 0x6111f2 &Known=0x61c1d0
Path = .\HII\PreSetup.exe
Imaging library revision = 8192 (dos-x86-release build, Wed Sep 06 22:38:39 2006)

0
Login to vote
bmooney2008's picture

does anyone know how presetup.exe gets into the HII folder? I have installed HII tools more then once and it doesnt appear. This is affecting my deploying HII by failing on the script portion that uses this file. Any help would be appreciated.

_________________________________________________

interestingly, I installed DS on a fresh test server and installed HII and presetup.exe was put in the HII folder. I copied this from the test server to my production server and now my errors are gone.

Does anyone have any suggestions why though, installing HII on a production 6.8 DS SP2 did not put this file in the HII directory?

0
Login to vote
bmooney2008's picture

I receive this error when deploying the HII during the last portion "run script" does anyone have any suggestions? From what I see below it says

Cmdline = F:\.\RDeploy\DOS\FIRM.EXE -recurse copy F\Temp\HII\5000749D\Drivers\HAL

shouldnt the last part be F:\Temp\HII\etc?

Error description:
The file could not be opened.

Possible causes:
A file that was expected to exist does not exist.
You do not have permission for this operation on the file or directory.

Possible resolutions:
Make sure the file exists and is accessible.
If the missing file is part of this program, reinstall the program.
Fix the permissions on the file or directory.

==================== Technical details ====================

Logfile = created Thu Mar 13 16:27:10 2008
Build = FIRM.EXE 6.8 (8397)
Cmdline = F:\.\RDeploy\DOS\FIRM.EXE -recurse copy F\Temp\HII\5000749D\Drivers\HAL PROD:\Windows\System32

Status = 41 (0x29)
Source file = imglib\fs\native\nativefs.cpp
Line number = 806 (0x326)
Stack trace = 0x69b6f7 0x69aeaf 0x62cbd7 0x634421 0x6111f2 &Known=0x61c1d0
Path = F\Temp\HII\5000749D\Drivers\HAL
Imaging library revision = 8397 (dos-x86-release build, Fri Jul 20 17:34:28 2007)

0
Login to vote
npares's picture

I'm currently having the same issue as bmooney. When I deploy an image it does not have the drivers installed on after finishing and I have the same error listed.

I have "DriverPrep.exe" in the HII folder.

Somehow, no drivers are being placed in the .\Temp\HII\%ID%D folder. All I have listed there is an empty folder named "Drivers".

This would be the reason for the FIRM error. I'm very new at this so I'm trying to look at this logically.

My .PMQ file shows it is populated with hardware that was discovered from TA.exe.

Next DrivePrep.exe is initiated and here is the log which is produced:

"
Creating the destination directory
Establishing database connection using DSN=Altiris eXpress Database
Reading from file: C:\DS_Share\TEMP\HII\5000031.OSV
OS Version: NTx86.5.1
Service Pack: SP2
Reading from file: C:\DS_Share\TEMP\HII\5000031.PMQ
Finished.
"

Are there supposed to be files or devices listed underneath the line indicating that it is reading the PMQ file?

If so, then where have I gone wrong?

0
Login to vote
MichaelH15's picture

Hello CondorMan,

I'm receiving this error in my Collect Drivers job in the C2.log file at the beginning.

Initiating database connection using 'DSN=Altiris eXpress Database'
Updating database with Driver Collect status.
Executing SQL command: IF NOT EXISTS (SELECT 1 FROM hii_settings)
INSERT INTO hii_settings (CollectStatus, AutoCollectMode, AutoCollectJob, AutoCollectDay, AutoCollectHour, AutoCollectMinute, AutoCollectPM) VALUES (0, 0, 0, 1, 1, 0, 0)
Exception while updating database with Driver Collect status: ERROR [42S02] [Microsoft][ODBC SQL Server Driver][SQL Server]Invalid object name 'hii_settings'.

Thank you,
MichaelH15

Update:
I just realized that this is a new feature that was mentioned in the first post. I will ignore this message for now if thats the case.

0
Login to vote
MichaelH15's picture

I don't see a .osv file anywhere. Which job/script creates and reads this file?

Update:
I'm receiving this in the %ID%S log file after running the Collect Drivers job.

Invalid parameter specified

DriverPrep 3.2.1
This utility will read the specified PMQ File... etc

I don't see where DriverPrep is being called to run?

Can anyone assist with this?

0
Login to vote
g00ner's picture

Any one used this with DS 6.9 yet?

0
Login to vote
babston's picture

I also have 6.9 and would like to find out if this works with this version. I was talking with Altiris support the other day and he from what he heard it was not working with 6.9. Can anyone confirm this?

0
Login to vote
neonfry's picture

I installed latest HIITools to DS 6.9. Only problem i have occurred that DriverPrep.exe doesn't populate temp\hii\%id%D -folder with hardware drivers. Collecting drivers has worked so far.
But i don't know is this a problem with 6.9 + HIITools or just some weird problem with our server. Anyone got more information?
But this tools looks great, i'm hoping that support to DS 6.9 comes quickly or i some work-around to DriverPrep.exe problem.

0
Login to vote
CondorMan's picture

Check the log file .\HII\Logs\%ID%D.log, does it explain why it failed to populate the folder?

+1
Login to vote
neonfry's picture

I have checked those logs, no errors etc.

- One of the logs

Creating the destination directory
Establishing database connection using DSN=Altiris eXpress Database
Reading from file: D:\eXpress\Deployment Server\TEMP\HII\5001068.OSV
OS Version: NTx86.5.1
Service Pack: SP2
Reading from file: D:\eXpress\Deployment Server\TEMP\HII\5001068.PMQ
Finished.

-

Also i have checked that drivers are imported to database (there is lots of information in hii_* tables).

Any suggestions?

Edit 2008/05/15: Is there possible to run DriverPrep.exe from server command-line, with those real parameters? I have tried that and everytime it just crashes. Even if i just type DriverPrep.exe.

0
Login to vote
MikeCharles's picture

I have the same issue as neonfry, but I can run driverprep from the command line. The logs show that the .osv file was read, as well as the .pmq file. The .pmq file is populated with driver data. I've looked in the database, and the driver data exists. All data exists from the drivercollect as well. But the .\temp\hii\%id%\d\driver folder is empty after running driverprep.

Does anyone have a resolution for this, or is there another log where I may be able to see the problem?

Thanks,
Mike

EDIT: Ok, the problem was with ta.exe. I upgraded to DS9, installed winpe2.1 from Altiris, and found the version of tap.exe for winpe2.1. All is well.

0
Login to vote
mphicks741's picture

Where did you find the tap.exe for winpe 2.1 I am unable to locate it.

0
Login to vote
setral's picture

The only location I know of to get tap.exe at least the latest one. Is from Windows XP Embedded, once you download and install it (even a trial).

It should be located under C:\Program Files\Windows Embedded\utilities\tap.exe

0
Login to vote
mphicks741's picture

I downloaded the version for xp. but tap.exe give me an error that it has to run on windows xp or higher. it works on winpe 1.6 but I am having issues with sata drivers on that version.

0
Login to vote
MikeCharles's picture

It's a real PIA to get. Not only do you have to install the embedded utilities, but you also have to find, download, and install the windows embedded tools update sp2 fp2007. (The .msi for this may be named sp1, but says sp2 when launched.) That will install tap.exe dated 10/26/2006.

Good luck.

0
Login to vote
Palvaran's picture

Do you have to recompile WinPE once you get the updated tap.exe?

Systems Administrator
Rice University

Remember, "The happiness of your life, depends on the quality of your thoughts."

0
Login to vote
Palvaran's picture

Ok, so it appears that tap.exe is a dynamic file that gets pushed from the DS server upon making a connection.

I am loving HII at the moment as our latest test was a moderate success. Everything appears to be a good as it is automagically injecting the drivers it needs, except one... kinda. On Dell GX960's, during the sysprep part, it is asking for 3 different audio parts of the driver. It pops up an error message stating, "Setup cannot copy the file: smwdmif.dll, smax4pnp.exe, and smaxesp.cpl." The thing is if you cancel the pop ups and let Sysprep continue, it will finish the process and has the drivers loaded.

Is there a modification that needs to be made to allow for it to continue the process without popping up errors and pausing

Systems Administrator
Rice University

Remember, "The happiness of your life, depends on the quality of your thoughts."

0
Login to vote
Palvaran's picture

Found out that Manual Driver Sort works to resolve the HII detection issues we were having with Audio drivers. Awesome tool. Thanks C-Man!

Systems Administrator
Rice University

Remember, "The happiness of your life, depends on the quality of your thoughts."

0
Login to vote
CondorMan's picture

Before the image is created an OS_Ver.txt file is created on the Production Drive.

After the image is deployed, the OS_Ver.txt file is copied from the Production Drive to the eXpress share under .\Temp\HII\%ID%.osv

So, your .osv file should be in the Temp\HII folder. If it doesn't exist there, it might not have existed in the root of your image.

+1
Login to vote
Vinh Huynh's picture

I believe there is a bug in DS 6.9. Try putting a letter in between the \ and %. DS6.9 doesn't seem to like the \% being next to each other.

Change the path to something like this.:

\Temp\HII\t%ID%.osv

Vinh Huynh

Vinh Huynh

0
Login to vote
bmooney2008's picture

when running the collect drivers job I receive an error "file does not exist:

C:\WINDOWS\system32\drivers\ICH7USB.CAT" I have copied the portion of the log file below indicating what is occurring. Any one have any suggestions?

Beginning Driver Collect. Source: registry, Destination: \\PHXWPA01\eXpress\Temp\HII\5000111C
Searching Registry for INF files
Searching for drivers of Class "{25DBCE51-6C8F-4A72-8A6D-B54C2B4FC835}"
Searching for drivers of Class "{36FC9E60-C465-11CF-8056-444553540000}"
Discovering INF file for device 0000
Determining destination directory
Destination directory is: \\%servername%\eXpress\Temp\HII\5000111C\-681227880\
Creating directory: \\%servername%\eXpress\Temp\HII\5000111C\-681227880\
Beginning to copy files for ich7usb.inf
Determining destination path for "ich7usb.inf"
Copying "ich7usb.inf" to "\\PHXWPA01\eXpress\Temp\HII\5000111C\-681227880\ich7usb.inf"
Getting source path for ICH7USB.CAT
Getting destination path for ICH7USB.CAT
Copying "C:\WINDOWS\system32\drivers\ICH7USB.CAT" to "\\%servername%\eXpress\Temp\HII\5000111C\-681227880\ICH7USB.CAT"
Error, file does not exist: C:\WINDOWS\system32\drivers\ICH7USB.CAT
Searching for and copying driver files from C:\WINDOWS\Driver Cache to \\%servername%\eXpress\Temp\HII\5000111C\-681227880\
Searching for driver files: C:\WINDOWS\Driver Cache

0
Login to vote
bmooney2008's picture

When deploying a HII to a computer, the status of the job runs as saying completed with no errors.

However when the computer boots into production, before the sysprep portion, the computer locks up compeletely with a black dos screen showing all the scripts that are running.

This is the last phase from the copy drivers and HAL script that is running. From the syntax it is locking up here.

echo REM Start the installation with the originally given parameters >> %TEMP%\presetup.cmd
echo START /WAIT setup.exe %%* >> %TEMP%\presetup.cmd

the echo start /wait setup.exe %%* >> %TEMP% \presetup.cmd is displaying in the command line window as on the actual computer as:

"C:\windows\system32> START /WAIT setup.exe -newsetup -mini"

after this line the computer locks up and i have to press the power button to restart it. after i restart it, sysprep runs and the system boots into Windows XP. The system isnt given all of the drivers though when it boots.

I need some help with this. If I deploy the HII image to the same model it was created with, the command line window appears and shows the scripts runs and it reboots automatically into sysprep. I assume this is how it should work normally.

0
Login to vote
AFUSILIER's picture

Justing wondering what was the fix for the below problem. I'm having the same problem and would like to know the fix.

[quote=bmooney2008]When deploying a HII to a

computer, the status of the job runs as saying completed with no errors.

However when the computer boots into production, before the sysprep portion, the computer locks up compeletely with a black dos screen showing all the scripts that are running.

This is the last phase from the copy drivers and HAL script that is running. From the syntax it is locking up here.

echo REM Start the installation with the originally given parameters >> %TEMP%\presetup.cmd
echo START /WAIT setup.exe %%* >> %TEMP%\presetup.cmd

the echo start /wait setup.exe %%* >> %TEMP% \presetup.cmd is displaying in the command line window as on the actual computer as:

"C:\windows\system32> START /WAIT setup.exe -newsetup -mini"

after this line the computer locks up and i have to press the power button to restart it. after i restart it, sysprep runs and the system boots into Windows XP. The system isnt given all of the drivers though when it boots.

I need some help with this. If I deploy the HII image to the same model it was created with, the command line window appears and shows the scripts runs and it reboots automatically into sysprep. I assume this is how it should work normally.

[/quote]

0
Login to vote
maweko's picture

Hi,
I am new to the DS stuff and please allow me to remark following problem using the HII Tool 3.2.1

I recently got the problem that installation of HII complained wrong XP SP2 installation files ( XP SP2 VL german). By using the GetHAL tool and ignoring the message I could go ahead installing it.

Afterwards I tried to initiate a collect driver job. This task is failing with an error that is coming from .NET I guess. Strange is that .Net Framework 1.1 andn 2.0 is installed on the DS server.

Following the error log:

See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
Altiris.DSSDK.Security.RbsSecurityException: Unable to complete Create Jobs operation on computer group All Computers. Permission is not granted.
   at Altiris.DSSDK.Security.DeploymentServerPermission.Demand(DeploymentServerIdentity identity, PermissionType type, Int32 objectId)
   at Altiris.DSSDK.Job.Add(String name, String description, Int32 folderId)
   at HIIJobWiz.Form1.btnNext_Click(Object sender, EventArgs e)
   at System.Windows.Forms.Control.OnClick(EventArgs e)
   at System.Windows.Forms.Button.OnClick(EventArgs e)
   at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
   at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.ButtonBase.WndProc(Message& m)
   at System.Windows.Forms.Button.WndProc(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.1433 (REDBITS.050727-1400)
    CodeBase: file:///C:/WINDOWS/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
HIIJobWiz
    Assembly Version: 3.2.1.0
    Win32 Version: 3.2.1.0
    CodeBase: file:///D:/Altiris/eXpress/Deployment%20Server/HIIJobWiz.exe
----------------------------------------
System.Windows.Forms
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.1433 (REDBITS.050727-1400)
    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.1433 (REDBITS.050727-1400)
    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Drawing
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.1433 (REDBITS.050727-1400)
    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
AxDsDm
    Assembly Version: 1.0.2722.33197
    Win32 Version: 1.0.2722.33197
    CodeBase: file:///D:/Altiris/eXpress/Deployment%20Server/AxDsDm.DLL
----------------------------------------
System.Data
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.1433 (REDBITS.050727-1400)
    CodeBase: file:///C:/WINDOWS/assembly/GAC_32/System.Data/2.0.0.0__b77a5c561934e089/System.Data.dll
----------------------------------------
System.Configuration
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.1433 (REDBITS.050727-1400)
    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
System.Xml
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.1433 (REDBITS.050727-1400)
    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
System.Transactions
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.1433 (REDBITS.050727-1400)
    CodeBase: file:///C:/WINDOWS/assembly/GAC_32/System.Transactions/2.0.0.0__b77a5c561934e089/System.Transactions.dll
----------------------------------------
System.EnterpriseServices
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.1433 (REDBITS.050727-1400)
    CodeBase: file:///C:/WINDOWS/assembly/GAC_32/System.EnterpriseServices/2.0.0.0__b03f5f7f11d50a3a/System.EnterpriseServices.dll
----------------------------------------
System.DirectoryServices
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.1433 (REDBITS.050727-1400)
    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.DirectoryServices/2.0.0.0__b03f5f7f11d50a3a/System.DirectoryServices.dll
----------------------------------------
Accessibility
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.1433 (REDBITS.050727-1400)
    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/Accessibility/2.0.0.0__b03f5f7f11d50a3a/Accessibility.dll
----------------------------------------

************** JIT Debugging **************

To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

Hints to solve this issue are highly appreciated

Thanks
maweko

0
Login to vote
CondorMan's picture

The Collect Drivers job requires .Net 2.0 to be installd on both the Deployment Server and the client. Do you have .Net 2.0 installed on your client?

+1
Login to vote
bmooney2008's picture

Where are you Condorman we need your help!

0
Login to vote
CondorMan's picture

I apologize for my delay in response. Sometimes I am too busy with other things, but I try to help as often as I can. I have been working on answering questions today; I hope I have been able to help you.

+1
Login to vote
lscott's picture

Did anyone else get the 'Error 1 during script execution' when running the 'Create Hardware Independent Image' job?

0
Login to vote
levwinski's picture

Hello,

HII 3.2.1 installed fine on my 2003 SP2 x32 virtual system with DS 6.9, but while trying to install to my production system (Win 2003 SP2 x64, SQL 2005 SP2 x64) I get:

ERROR [IM002] [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified

Any advice would be greatly appreciated.

Thanks!

0
Login to vote
CondorMan's picture

The installer tries to use the ODBC System DSN "Altiris eXpress Database". Make sure it is there and configured correctly.

+1
Login to vote
SK's picture

We do not support our core servers (DS, NS & RS) on 64bit platforms.

We can makes us of a 64bit SQL backend, and we can managed 64bit systems, however, we do not recommend installing the core products on these systems.

NS 7.0 will be our first 64bit product.

Connect Etiquette: "Mark as Solution" those posts which resolve your problem, and give a thumbs up to useful comments, articles and downloads.

0
Login to vote
levwinski's picture

Bearing in mind the advice above, I have reinstalled on Windows x32 2003 sp2. The installation went fine and the DSN was created. Thank you.

I would like to create an image. Here is where I am so far:

1. Installed HII 3.2.1, chose to support Win XP SP2 and provided slipsteamed CD.

2. Copied ta.exe and tap.exe as instructed (Will worry too much about driver collection with 6.9 until the issues discussed on this thread are resolved).

3. Installed .net 2.0 on DS and test client.

When I start the wizard, I choose the location for the image, but then it has empty drop-downs for OS and Serial. I could not enter anything there so tried to click Finish without them, but I get an unhandled exception error. Index out of range.. Parameter name: index

How do I proceed?

Thank you.

RESOLUTION FOUND IN AN EARLIER RELEASE THREAD:

OS & Serials populated in DS Console > Tools > Options > Global

0
Login to vote
CondorMan's picture

In the next release I plan to allow you to add your OS and Serials from within the HII Job Wizard. Sorry for the inconvenience.

+1
Login to vote
levwinski's picture

Youre the last person that has to apologise for inconvenience, your application is a real time saver.

How would really be great is 6.9 compatibility, so the driver collection works.

0
Login to vote
Conrad65's picture

Hey All,
I am attempting to create a job to Collect Drivers through the HII Job Wizard for the first time and I am recieving an error when I try to finish creating the Job. Just curious if anyone's encountered this and/or has a suggestion on a solution.

I am running version 6.9 of the Deployment Console. We just recently had this installed for us so I am fairly new to Altiris. Let me know if there is any more information I should include.

**Error
Unable to complete Create Jobs operation on the computer group ALL Computers. Permission is not granted.

See the end of this message for details on invoking 
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
Altiris.DSSDK.Security.RbsSecurityException: Unable to complete Create Jobs operation on computer group All Computers. Permission is not granted.
   at Altiris.DSSDK.Security.DeploymentServerPermission.Demand(DeploymentServerIdentity identity, PermissionType type, Int32 objectId)
   at Altiris.DSSDK.Job.Add(String name, String description, Int32 folderId)
   at HIIJobWiz.Form1.btnNext_Click(Object sender, EventArgs e)
   at System.Windows.Forms.Control.OnClick(EventArgs e)
   at System.Windows.Forms.Button.OnClick(EventArgs e)
   at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
   at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.ButtonBase.WndProc(Message& m)
   at System.Windows.Forms.Button.WndProc(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.42 (RTM.050727-4200)
    CodeBase: file:///C:/WINDOWS/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
HIIJobWiz
    Assembly Version: 3.2.1.0
    Win32 Version: 3.2.1.0
    CodeBase: file:///C:/Program%20Files/Altiris/eXpress/Deployment%20Server/HIIJobWiz.exe
----------------------------------------
System.Windows.Forms
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.42 (RTM.050727-4200)
    CodeBase: file:///C:/windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.42 (RTM.050727-4200)
    CodeBase: file:///C:/windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Drawing
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.42 (RTM.050727-4200)
    CodeBase: file:///C:/windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
AxDsDm
    Assembly Version: 1.0.2965.20033
    Win32 Version: 1.0.2965.20033
    CodeBase: file:///C:/Program%20Files/Altiris/eXpress/Deployment%20Server/AxDsDm.DLL
----------------------------------------
System.Data
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.42 (RTM.050727-4200)
    CodeBase: file:///C:/windows/assembly/GAC_32/System.Data/2.0.0.0__b77a5c561934e089/System.Data.dll
----------------------------------------
System.Configuration
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.42 (RTM.050727-4200)
    CodeBase: file:///C:/windows/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
System.Xml
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.42 (RTM.050727-4200)
    CodeBase: file:///C:/windows/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
System.Transactions
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.42 (RTM.050727-4200)
    CodeBase: file:///C:/windows/assembly/GAC_32/System.Transactions/2.0.0.0__b77a5c561934e089/System.Transactions.dll
----------------------------------------
System.EnterpriseServices
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.42 (RTM.050727-4200)
    CodeBase: file:///C:/windows/assembly/GAC_32/System.EnterpriseServices/2.0.0.0__b03f5f7f11d50a3a/System.EnterpriseServices.dll
----------------------------------------
System.DirectoryServices
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.42 (RTM.050727-4200)
    CodeBase: file:///C:/windows/assembly/GAC_MSIL/System.DirectoryServices/2.0.0.0__b03f5f7f11d50a3a/System.DirectoryServices.dll
----------------------------------------
Accessibility
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.42 (RTM.050727-4200)
    CodeBase: file:///C:/windows/assembly/GAC_MSIL/Accessibility/2.0.0.0__b03f5f7f11d50a3a/Accessibility.dll
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
    <system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception will be sent to the JIT debugger registered on the computer rather than be handled by this dialog box.
0
Login to vote
CondorMan's picture

In your Deployment Server Console, go to Tools>Security disable Console Security. You should then be able to use the HII Job Wizard. You will only need to run through the wizard once for each job you want to create, and then you can re-enable Console Security.

+1
Login to vote
espo9's picture

I do not have Security enabled and am running into the same issue with the create image job and the deploy job. Not all (if any) of the tasks are being created in the jobs. As soon as the OS is selected it crashes with the .Net error. I have tried on DS 6.8 and 6.9 (6.9 preferred). I have been uninstalling and reinstalling DS, OS, and HII Tools all week on multiple boxes :) - what are the exact requirements for HII Tools 3.2.1 to run properly? Are there examples of the fully created jobs anywhere?

0
Login to vote
CondorMan's picture

In the DS Console, go to Tools > Options > Global > Sysprep Settings and then populate the Keys for the OS that you want to deploy.

+1
Login to vote
bhawver's picture

Does this utility support Deployment Server 6.9? I'm unable to install as it complains that 6.8 needs to be installed.

Brian Hawver
Systems Engineer
Yaskawa America, Inc.

Connect Etiquette: "Mark as Solution" those posts which resolve your problem, and give a thumbs up to useful comments, articles and downloads.

0
Login to vote
CondorMan's picture

It is not written to support 6.9, but some people have been able to get it to work with 6.9. The biggest problem is that the old version of TAP.EXE does not work with WinPE 2.1, and you will need to get the latest version of TAP.EXE.

If anyone gets it to work with 6.9, I am interested to hear what you had to do so that I can make the next version 6.9 compatible. I don't imaging that it will take much tweaking to get it to work.

+1
Login to vote
mphicks741's picture

I was able to get this working on DS 6.9. First I had install it on DS 6.8 sp2. then upgrade to DS 6.9. After the right tap.exe it works fine. The only issue I have come across is that the "Driver Library Maintenance" tool has a "Driver Collection Status" of a full blue bar. I cannot manually install a driver or export the drivers.

any thoughts

0
Login to vote
mphicks741's picture

Disregaurd, I was blind the first time I read through this.

When installing these tools the hii_settings batabase does not get created. is there a know issue, or can I just get the SQL code to create it.

0
Login to vote
CondorMan's picture

CREATE TABLE hii_settings (CleanupLastRun smalldatetime, CleanupScheduled smalldatetime, CollectStatus tinyint, AutoCollectMode tinyint, AutoCollectJob int, AutoCollectDay tinyint, AutoCollectHour tinyint, AutoCollectMinute tinyint, AutoCollectPM bit)

+1
Login to vote
Cristiano's picture

You're the last person that has to apologise for sohbet inconvenience, your application is a real time saver.

How would really be great is 6.9 compatibility, so the driver collection works.

0
Login to vote
DerikDavis's picture

We are looking at using HII but need to distribute the imaging process to multiple locations. We wanted to use the DS Image Distribution Framework to leverage our package servers. Is HII compatible with DS Image Distribution Framework? If it is, what changes or configurations are needed on HII. Thanks.

0
Login to vote
aabrown1971's picture

I have installed the 3.2.1 tools.

When I try to run the Job Wizard installer the Driver collect works fine.

The Create hardware image job crases.

It is giving me an error of "Index out of range" after I point it to our image. I don't fill anything else out. I am running 6.8 SP2

0
Login to vote
ITCNB's picture

We are having problems running this tool on 6.9 is there a different solution for this product.

0
Login to vote
Pikoshi's picture

So far I believe that the furthest that HII Tools supports is DS 6.8 SP2. I have tried running this on 6.9 but have as of yet been unable to get it to run correctly. Others have reported success after changing a few things but I do not remember what they have had to change.

If your question was answered, mark the anwser as the solution
Give thumbs up if you found a post helpful

0
Login to vote
syarlett's picture

I got exact same error here and i'm on DS 6.9

0
Login to vote
CondorMan's picture

In the DS Console, go to Tools > Options > Global > Sysprep Settings and then populate the Keys for the OS that you want to deploy.

0
Login to vote
Kevin.Urbanek's picture

Instead of upgrading an old DS server, we installed a new DS with version 6.9. I installed the HII 3.2.1 Tools, I ran the SQL code to create the view for future features. I got the newer TAP files from MS embedded (thanks for the tip).
We can now run all 3 tasks (driver collect, create HII image and Distribute HII image). The only piece I cannot verify is if the HAL install is working. I never see any HAL files get copied during the HII image distribution part, but I believe all our desktops use the same HAL, so no HAL may be copied because no change is needed.
One issue we have seen is that when we distribute our HII image, on the first reboot, sometimes the PC errors on boot with a HAL error. We then re-push the image and all is well. It is strange, unless we are having some glitch as the image is sent down.

0
Login to vote
robyngood's picture

Hi Kevin,

Having alot of differen HAL types I've used a utility called Devcon that you could probably script for the HAL. It may prevent you from having to image the machines over.

0
Login to vote
holazon's picture

I downloaded the version for xp. but tap.exe give me an error that it has to run on windows xp or higher. it works on winpe 1.6 but I am having issues with sata drivers on that version...

0
Login to vote
s0n's picture

I am having an issue with tap not getting all the hardware ids from the computer, this stops it from installing all the hardware. If I run tap after windows installs is grabs all of the hardware but not from within PE. I am running PE 1.6, could it need a newer 2.1 PE enviornment?

FYI tape.exe is 2.0.1500.0 modify date of 5/22/2008

0
Login to vote
noodleNT's picture

Would love to give this a shot once 6.9 is support.

Right now I can't stand having to re-sysprep every time I need to add a new Mass Storage Driver. In the mean time, does anyone one know of a way to manually add a new MSD without haveing to re-sysprep a machine.

-1
Login to vote
Pascal KOTTE's picture

Hi, Yes for sure - Just install SP1 for DS 6.9, and add your mass storage driver in the new DeployAnywhere ghost extension integrated now (Tool menu in Ds conole if I remember well).
You also can add NIC drivers (can be usefull also for a new hardware ;-)
When deploy an image: just check the box "use deployanyhwere option" on the job configuration.
That's it.

But: To preboot WinPE in PXE, you will have to add this driver also in the WinPE, as it is not automatically done :-(

What HIIS seems providing in addition: it is the all Drivers life cycle management automation. See demo video.

~Pascal @ Kotte.net~ Do you speak French? Et utilisez Altiris: venez nous rejoindre sur le GUASF

+1
Login to vote
dcuoq's picture

Is it possible to update the link for the guide ?
It doesn't work ?

Where we can download the new version of tap.exe and the other exe file ?

Cordialement | Best Regards
DAVID CUOQ
Coordinateur Technique Micro-Informatique
a-SIS

0
Login to vote
Pascal KOTTE's picture

www-secure.symantec.com/connect/articles/hii-tools-quick-start
www-secure.symantec.com/connect/articles/install-drivers-and-packages-vista-winpe

Don't ask me why Symantec can not script auto-correction those links... :-(

~Pascal @ Kotte.net~ Do you speak French? Et utilisez Altiris: venez nous rejoindre sur le GUASF

+1
Login to vote
pekay's picture

Hello,

I get following error when trying to run HIIJobWiz.

Unable to connect to database.
ERROR [28000][Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user ". The user is not associated with a trusted SQL Server connection.

The DB is on a remote SQL 2005 server. When I ran setup it asks me for user credential as the user I am running the setup under does not have the appropriate rights.
I decided to use a SQL native accout. After I put in the correct credential setup finishes successfull.

However even giving that SQL account SA rights does not fix the error message when trying to run HII.

I checked with the SQL DBA and he confirms that HII tries to connect to the DB with an empty user which explains while the error message comes up with an empty user as well.

Any advice on what coud be wrong would be really appreciated.

thanks
Peter

0
Login to vote
maduran@srpnet.com's picture

Has there been a HII Tools official release for DS 6.9?

**SUCCESS STOPS WHEN YOU DO**

0
Login to vote
ryanmf's picture

Same question - does HII tools support DS 6.9 SP 2?  Can I install this version on DS 6.9 SP 2?  I am having difficulty determining how best to create a hardware independent image.... (first time).  

Thanks! 

0
Login to vote
garfaldo's picture

Does anyone know if this is compatible with Windows 7?  Having some issues with the correct drivers being selected for injection.

0
Login to vote