none
Customizing MDT: reading variables from the form and using later in deployment

    Question

  • I have inherited an MDT deployment implementation, and decided to build a new server and then get fancy with the Deployment wizard and add my own pane for getting information.

    I've been using the MDT Wizard Studio, quite an amazing tool, and I've made my own form that looks something like this:

    What I want to do is take the values that the analyst sets in the drop-downs and supply them as parameters in a later task that runs a powershell script:

    Here is what is supposed to happen when the values change in either of the dropdowns:

    And finally here is my HTML for the page:

    <H1>OS Customization</H1>
    
    <td width=50>
    	<img src="sla.png">
    </td>
    
    <td>
    	<p>Service Level: </br>
    		<select id=ServiceLevelList language=VBScript onchange="SetServiceLevel" class=wideedit>
    			<option value="2">Gold</option>
    			<option value="3">Silver</option>
    			<option value="4">Bronze</option>
    		</select>
    		<input type=hidden Name=ServiceLevelList />
    
    	</p>
    </td>
    
    <td width=50>
    	<img src="patch.png">
    </td>
    	<p>Patching Group: </br>
    		<select id=WSUSGroupList language=VBScript onchange="SetWSUSGroup" class=wideedit>
    			<option value="PCM_BigFix_Sunday_A_2200">PCM_BigFix_Sunday_A_2200</option>
    			<option value="PCM_BigFix_Daily_A_1700">PCM_BigFix_Daily_A_1700</option>
    			<option value="PCM_BigFix_Manual">PCM_BigFix_Manual</option>
    			<option value="PCM_BigFix_Saturday_A_0000">PCM_BigFix_Saturday_A_0000</option>
    			<option value="PCM_BigFix_Saturday_A_0200">PCM_BigFix_Saturday_A_0200</option>
    			<option value="PCM_BigFix_Saturday_A_0800">PCM_BigFix_Saturday_A_0800</option>
    			<option value="PCM_BigFix_Saturday_A_2000">PCM_BigFix_Saturday_A_2000</option>
    			<option value="PCM_BigFix_Sunday_A_1000">PCM_BigFix_Sunday_A_1000</option>
    			<option value="PCM_BigFix_Sunday_A_1100">PCM_BigFix_Sunday_A_1100</option>
    			<option value="PCM_BigFix_Sunday_A_1200">PCM_BigFix_Sunday_A_1200</option>
    			<option value="PCM_BigFix_Sunday_A_1300">PCM_BigFix_Sunday_A_1300</option>
    			<option value="PCM_BigFix_Sunday_A_1500">PCM_BigFix_Sunday_A_1500</option>
    			<option value="PCM_BigFix_Sunday_A_1600">PCM_BigFix_Sunday_A_1600</option>
    			<option value="PCM_BigFix_Sunday_A_1800">PCM_BigFix_Sunday_A_1800</option>
    			<option value="PCM_BigFix_Sunday_A_1900">PCM_BigFix_Sunday_A_1900</option>
    			<option value="PCM_BigFix_Sunday_A_2000">PCM_BigFix_Sunday_A_2000</option>
    			<option value="PCM_BigFix_Sunday_A_2100">PCM_BigFix_Sunday_A_2100</option>
    			<option value="PCM_BigFix_Sunday_A_2300">PCM_BigFix_Sunday_A_2300</option>
    			<option value="PCM_BigFix_Tuesday_A_0700">PCM_BigFix_Tuesday_A_0700</option>
    			<option value="PCM_BigFix_Tuesday_A_1700">PCM_BigFix_Tuesday_A_1700</option>
    			<option value="PCM_BigFix_Tuesday_A_1800">PCM_BigFix_Tuesday_A_1800</option>
    			<option value="PCM_BigFix_Tuesday_A_2300">PCM_BigFix_Tuesday_A_2300</option>
    			<option value="PCM_BigFix_Wednesday_A_0500">PCM_BigFix_Wednesday_A_0500</option>
    		</select>
    		<input type=hidden Name=WSUSGroupListName />
    	</p>
    </td>

    My issue is that the registry settings are the default values from CS.ini. I am weak with HTML so I'm guessing it's something in there with the names or how I'm assigning them in the vbscript that fires.

    Can anyone with experience help point me in the right direction?

    Friday, July 13, 2018 9:09 PM