/build/static/layout/Breadcrumb_cap_w.png

How to capture, save, and reinstate a computer's name while deploying an image to it?

Our company programs the computer name into the BIOS of every workstation we put out. I need a reliable way to either pull it from the BIOS->Maintenance->Asset Tag field, or out of the operating system before it lays the image down...then have it rename the computer back to it's previous name post imaging.

0 Comments   [ + ] Show comments

Answers (3)

Answer Summary:
For anyone interested in how to maintain the hostname while deploying a sysprep image to workstations here's what I found... www.kace.com/support/kb/?action=artikel&id=1137 Follow that article. In your sysprep xml file under the shell setup section make sure you have a place holder set in for the computername field. That way the get/set tasks will be able to populate it in the post installation tasks.
Posted by: Trinity 12 years ago
Brown Belt
3
LiteTouch using MDT 2010. You can perform an image deployment called Refresh or Upgrade that allows you to backup the PC, Apply a new image, Restore User Data/Applications with a simple VBS script call.

http://www.windowsnetworking.com/articles_tutorials/Deploying-Windows-7-Part7.html
Posted by: ramseygr 12 years ago
Senior Yellow Belt
3
IF the workstations are Dell Systems, you can use the Client Configuration Toolkit (CCTK) in WinPE - "cctk.exe --asset"
you can capture that output with vbscript (maybe .bat, I haven't done that myself)
http://en.community.dell.com/techcenter/systems-management/w/wiki/1954.dell-client-configuration-toolkit-cctk-samples.aspx

https://support.dell.com/support/edocs/SOFTWARE/smcctk/2.0/CLI/html/cctkugcb.htm

Comments:
  • That's interesting...any idea how to integrate that into the KBOX deployment scheme? - camrevard 12 years ago
  • thank you for the replies... - camrevard 12 years ago
Posted by: Roonerspism 12 years ago
Second Degree Brown Belt
0
Do you have a K1000 asset system also? If you do, an alternative is if you dont want to hard code it into the bios and make future deployments a little more dynamic you can source your machine names from the K1 asset records and use the post install task listed in this article:
http://www.itninja.com/question/name-machines-via-k1-with-k2-post-install-script
David did a fantastic job of turning this into a post install task for the K2's use. Might reduce your overhead?
 
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