We are currently using sysprepped WIM images for Windows 7 SP1 image deployment. We're running into an issue on our 64 bit images. When it comes time to Set KUID, the following errors appear...

1) Error - File Not Found

2) AutoIT Error - Line 21 (File C:\Kace\Applications\42\set_kuid.exe) Error: Subscript used with non array variable.

This issue does not happen on our 32 bit images. I have GetKUID (64 bit version) set as Preinstall, CopyKUID (64 bit) as midlevel, and SetKUID (not OS Arch specific) set as 3rd level task. I tried the /silent parameter per Corey's update notes, but that did not work. Despite these errors, the KUID copy appears to work, however these 2 errors interrupt our unattended image process

Has anyone else run into this issue? Is there a fix? Obviously I would like to keep using the KUID tasks if possible.

Thanks in advance.

Answer Summary:
0 Comments   [ + ] Show Comments


Please log in to comment

Community Chosen Answer


Since you are using 3.4 and deploying .wim's using the native imaging toolkit, make sure that the copy kuid midlevel task comes after deploying the .wim

Lead L3 Enterprise Solutions Engineer, K2000
If my response was helpful, please rate it!

Answered 04/16/2013 by: cserrins
Red Belt

Please log in to comment



Are you using 3.5?  If so, you do not need to use the old Get/Set KUID programs.  This functionality has now been built into the K2000.  The KUID is copied up to the K2000 before deployments and temporarily stored.  There is a new Postinstall Task called "Apply KUID to KBOX1000 Agent" that can now be used to complete the process. Give that a try and good luck!

Answered 04/09/2013 by: andrew_lubchansky
Black Belt

  • FYI this behavior is for Windows only. You would still need the Macintosh tasks.
  • Good to know, thanks for the information. We're still on 3.4 but will be upgrading soon.
Please log in to comment
Answer this question or Comment on this question for clarity
Five Easy Steps to Smarter Systems Imaging
With traditional methods for systems imaging, each image captures a particular hardware and software configuration at a specific moment in time—static, unchanging, unmanageable.