Check the bdd.log and search for OSDComputerName, where is the value getting
set?
The rules in ztigather.xml show:
<property id="OSDComputerName" type="string" overwrite="false"
description="The new computer name to assign to the computer (used with
ConfigMgr) " />
With overwrite=false, the ZTIGather.wsf script will not overwrite the value
if already set.
From: [email protected] [mailto:[email protected]]
On Behalf Of Kent, Mark
Sent: Monday, January 27, 2014 8:35 AM
To: [email protected]
Subject: [MDT-OSD] OSDComputername already set
We use the MDT Db to assign the computer name during imaging. With SCCM2007
this was working fine but with 2012 we are getting the following example
(from the BDD.LOG):
"Value for OSDCOMPUTERNAME is already set to MININT-L5M6A8Q so database
value of LSP228 will be ignored."
So it's essentially ignoring the OSDCOMPUTERNAME property for some reason.
Anyone come across this or know why this might be happening and what to do
to correct it? Is there some way to force it? Thanks!
Mark Kent (MCP)
Sr. Desktop Systems Engineer
Computing & Technology Services - SUNY Buffalo State
