Search the Community
Showing results for tags 'naming conventions'.
Found 3 results
During the naming convention on the answer file I set the read from WMI property first, and wanted it to pull the serial number as the computer name. I set a prefix and let the WMI query as default. Unfortunately it didn't do this when I deployed the image. Is there a different step I am suppose to do to get it to read and set the serial number as the computer name?
Hi Everyone, I have been having issues with getting Sysprep to read in our computer asset tags and setting them as the computer name. As far as I know, all this requires is setting the WMI property to be the highest priority in the answer file like so: <identification skip="0"> <!-- 0 = Assign a new computer name automatically, 1 = Use the following naming method --> <naming_mode /> <naming_methods> <method>WMI</method> <method>CUSTOM</method> <method>EXISTING</method> </naming_methods> <custom_naming_scheme>EE####</custom_naming_scheme> <prefix></prefix> <wmi_query>SELECT SMBIOSAssetTag FROM Win32_SystemEnclosure</wmi_query> </identification> At its current state, Sysprep is randomizing the computer name and giving computers values like "WIN-LVCP52GBPMP" or other related "WIN" names. This leads me to believe that the above portion of XML is somehow completely disregarded. Perhaps something like the script mentioned here may help me but the attachment has been removed. (For reference, we are testing on a Dell Optiplex 790 and 7010. I have made sure to update their BIOS's and platform packs as well). Any insight would be greatly appreciated! Thank you.
Hello, I want SmartDeploy to assign a new computer name at deployment. I have selected the option for this in the answer file wizard>advanced options>identification , yet when the image is deployed the PC retains its original name. I created fresh answer files to no avail. I suspect, maybe wrong, that this is causing issues with the computers SID, ie, its not changing. Its like SmartD is not syspreping properly, or something. I dont know, im lost. Its having a knock on effect i think with the machines getting GPO's. Any thoughts, pointers etc welcome.