Using MDTweb front end on MDT2010update1, I've added in about half a dozen new custom properties.
I've added the names of those new properties into the customsettings.ini under the [settings] section so that the line reads Properties=MycustomProperty,BUSINESSCONTACT,TECHNICALCONTACT, etc etc
The intention is that the value entered in for these values from the MDTwebfront end are picked up by a wsf script in the task sequence and writen out to the registry for further use.
the script does the following :-
<script language="VBScript" src="ZTIUtility.vbs"/>
Dim strComputer, strCBKeyPath, strValue, strValueName
strComputer = "."
Set objRegistry = GetObject("winmgmts:\\" & _
strComputer & "\root\default:StdRegProv")
strValueName = "TECHNICALCONTACT"
strValue = oEnvironment.Item("TECHNICALCONTACT")
Now teh script for for any properties taht are built into MDT, however it fails to pick up the value for those properties that I've extended via teh MDTweb front end.
the ztigather.log files do however indicate that a value for these properties has been picked up by MDT.
Anyone have any ideas? I beleive when extending the database, taht added new custom settings via MDT Web front and and adding the lines mentioned above to customsettings.ini is all that has to be done?
Copuld it be that these properties are not acvaully environment variables at this stage but something else?