/build/static/layout/Breadcrumb_cap_w.png

Is my KUID Post-install Task even necessary?

After looking back through my task list for my images, I started to question whether or not the Apply KUID to K1000 Agent post-install task even made sense to have. The first pre-install task I have in place wipes the hard drive and formats/partitions it to prep for the Windows 10 install. If that's the case, then the KUID post install task wouldn't be able to see what KUID the computer had before it was reimaged, correct?

I just want to make sure I'm understanding the process. It seems like if it were to work, there would need to be a pre-install task script to look on the computer for the kuid.txt file, copy it off to one of the KACE network shares, and then copy it back and apply it as a post install task.

Any advice or clarification would be much appreciated.


0 Comments   [ + ] Show comments

Answers (2)

Posted by: Nico_K 1 year ago
Red Belt
0

this is correct. You would need a pre install task to collect the info. Yes.
This Post install task is an example from another time. 

If you install an agent it contacts the appliance. If the appliance recognizes the machine (since an agent was installed before) it gets the same KUID as before and updates the record.
A few (I seen it last in a 6.x) versions back it just created a new KUID and you had two entries.

Posted by: JordanNolan 1 year ago
10th Degree Black Belt
0

I have noticed that even after I wipe a computer and reinstall, the K1000 recognizes the machine as the same device and I do not have any pre or post tasks related to the KUID.  The KUID must be formed in a similar way where MS can tell your hardware is the same device when you re-install Windows.

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ