I'm trying to figure out the most ideal method to update Active Directory with the serial number attribute automatically ( hopefully not requiring I install RSAT for the AD management tools ) on all my currently running systems ( likely via a on-demand script )?

The idea is that I want all the computers in my system that have a serial number to put that info in active directory. That way the computer name can correlate to the serial number which is more reliable for the script I'm going to create to make it so I no longer need to specify/confirm the computer name ( making this more automated and accurate ) when imaging or doing scripted installs on k2000.
0 Comments   [ + ] Show Comments


Please log in to comment


if you want to name the computer during the k2000 scripted installation process you can apply a postinstallation task to rename the computer using WSNAME in correlation with the serial number.

Had a similar question last week. maybe you can use this information also. Please take a look at.

Answered 04/01/2015 by: aragorn.2003
Red Belt

  • We're currently using that or a similar script. Those scripts are a bit too basic for our needs and wouldn't help us accomplish what we're looking to do presently. Those tools simply look at the hard drive for that information which may no longer be accurate or otherwise present ( due to being wiped or hard drive replaced ).

    We need to update AD with all our currently deployed systems with their serial number that way when we do a AD query for the serial number we will get the corresponding computer name that it's registered with to avoid several potential issues.

    What I'd like to know is what options do I have that doesn't require me to install the RSAT or otherwise AD management tools on each system ( via script ) to update the serial info. I may very well be able to do this on the KACE side when they check in.
Please log in to comment
If you are familiar with Autoit there is an Active Directory plugin for it that will let you connect to AD and query or change just about anything you want with regards to interacting with AD.

You can create a script to do what you need and run it as post install task.

If you couple this with KBE manipulator and add ADSI to your PE you can use these together to query AD as a pre, midlevel, or obviously a post install task to connect to AD and do anything you want.

If you have more specific questions let me know,
Answered 04/02/2015 by: matiasm
Orange Senior Belt

Please log in to comment
Answer this question or Comment on this question for clarity