Thursday, January 24, 2013 7:48 PM
I'm working on upgrading our Helpdesk team to MDT 2012. So far I love it. I'm just trying to get one feature back that we had in MDT 2010 and was hoping for a little input from you guys on how to do it. In MDT 2010 we separate our applications under OS-Specific folders. So if someone selects a task sequence to deploy an image for Windows 7 with Sp1 x86 we suppress the other Application folders in the MDT Wizard for any other OS but that one. That way they can only install applications that have been approved and tested for Windows 7 with Sp1 x86. In MDT 2010 getting this to work involved using selection profiles and making an edit to "DeployWiz_Initialization.vbs". The process is outlined in this fantastic blog post by Michael Niehaus:
I was hoping the same thing would be possible in MDT 2012, byt maybe this time I wouldn't have to edit any of the base scripts. I've Googled around for a method, but I've come up empty so far. Does anyone know how to achieve this in MDT 2012?
Thursday, January 24, 2013 7:55 PM
Yes this has changed in MDT 2012. Take a look at this:
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. ”
- Marked As Answer by ZeusABJ Friday, January 25, 2013 4:10 PM
Friday, January 25, 2013 2:19 PMwe still use this and it works like before if you follow the instructions from the link Frank posted.
Friday, January 25, 2013 4:10 PM
Thank you for your help. I am really sorry it has taken me so long to respond. I've suddenly started getting "Unexpected Error" every time I try to reply to or post any thread in this forum. It’s very annoying! The only way I was (finally) able to update this post was by copying my response into notepad and resubmitting it over and over again until it worked. Anyway, on to my reply:
Although I was hoping for a solution that did not involve script edits at least the previous solution still works. Also (FYI) I actually found a bug in the code Michael posted there. Michael says to edit that first line like so:
g_oXMLAppList.sSelectionProfile = oEnvironment.Substitute("For %TaskSequenceID%") ' MODIFIED
But (apparenlty) the word "For" in front of "%TaskSequenceID%" is a typo because the only way I was able to get it to work was by removing it like so:
g_oXMLAppList.sSelectionProfile = oEnvironment.Substitute("%TaskSequenceID%") ' MODIFIED
Maybe I did something wrong, but it refused to work for me with that "For" in there.
- Edited by ZeusABJ Friday, January 25, 2013 8:39 PM
Friday, January 25, 2013 4:42 PMif you keep the "for" in there your selection profiles also need the FOR in their name for example "For 6.2-PRO-X64".
- Marked As Answer by ZeusABJ Friday, January 25, 2013 8:30 PM
Friday, January 25, 2013 8:06 PM
if you keep the "for" in there your selection profiles also need the FOR in their name for example "For 6.2-PRO-X64".Oooooooooohhhh okay, I get it! Its for notation!
Friday, January 25, 2013 8:35 PM
Wow Stefan, that was such a great tip I had to mark your replay as an aswer too! I feel like a total idiot for not realizing what that "For" was... well FOR! LOL! I know enough about scripting that it should have registered with me. Sometimes I just get tunnel vision when I mess with someone else's code my brain just stops working. I've actually gone back and reedited the script and (as a slight variation) I'm using "Filter TSID -" as my prefix, like so:
g_oXMLAppList.sSelectionProfile = oEnvironment.Substitute("Filter TSID - %TaskSequenceID%") ' MODIFIED
Now all my Task Sequence-specific Selection profiles are all nice and sorted together in the Workbench view! AWESOME!
- Edited by ZeusABJ Friday, January 25, 2013 8:36 PM
Monday, January 28, 2013 8:14 AMno problem glad i could help :)