UDI - Is it possible to have a user choose to Deploy Win7 or 2008 through the UDI Wizard's Image Selection?

[Nordland]

Is it possible to have a user choose between Win7 and 2008 R2 through the UDI Wizard's Image Selection?

 

Or do I need different task sequences for each OS?

 

Also, in the UDI Wizard during deployment it wants to install Windows do D:\Windows instead of C:. Is there a way for me to force it to C?

 

By the way, this is not an image directly from the Windows 7 DVD. It installs fine as a non UDI task sequence.... The only difference I can see is that UDF TS has a partition for Bitlocker.

 

Thanks

[Iroqouiz]

Wondering this myself. Doesn't seem to matter what image I choose, it still picks the image specified when I created the UDI task sequence. It's quite annoying. Anybody know how to fix this?

[jlwalsted]

Same problem here. I gave the images different Index IDs but still no luck.

[conorofarrell]

Are both of these Operatting systems part of the same image? This is how it should work by design. From what I recall, you cannot have multiple WIMs in a task sequence. I've not tried this since the early days for ConfigMgr 2007 through standard OSD. I've not done it through MDT or UDI before, so it may not be the case.

 

If you are trying with multiple WIMS, then your TS variable name might be incorrect. I added this vbscript to my task sequence to write all the variables to a text file. It might be worthwhile looking at to find the correct variable to use. Just run it in a standard TS so it can pull the relevant info first:

'==========================================================================
' test to Log TS variables
'==========================================================================

Dim sNewComputerName, oTaskSequence, sTSMachineName, bPromptName
Dim objFSO, strLogFile, oTSEnv
Set oTaskSequence = CreateObject ("Microsoft.SMS.TSEnvironment")
strComputer = "."
Const ForAppending = 8
Set objFSO = CreateObject("Scripting.FileSystemObject")
strLogFile = "C:\TS_Variables.log"

Set oTSEnv = CreateObject("Microsoft.SMS.TSEnvironment")
For Each oVar In oTSEnv.GetVariables
set objFile = objFSO.OpenTextFile(strLogFile, ForAppending, True)
objFile.WriteLine oVar & "=" & oTSEnv(oVar)
objFile.Close
Next

 

Make sure to run it as the last item in the TS so you capture all variables.

 

I hope it helps

Con

Edited September 6, 2012 by conorofarrell

[Iroqouiz]

Did a workaround by creating one UDIWizard.xml file for every image I want to deploy, and locked the image in the designer. Then created one TS each for those xml files.

[Atomic12]

How????????? Don't just write answer in one sentence, PLEASE! Make tutorial with pictures to help rest of community.