So I have been using the UI++ as a prestart command in our Boot image for quite some time now and never had any issues. However, recently when selecting and populating the 'SMSTSPreferredAdvertID' variable it is still going to the standard task sequence selection screens. I don't know why this is happening all of a sudden.... Does anyone have any ideas?
-We're booting from PXE. -Confirmed that the 'SMSTSPreferredAdvertID' variable does populate with the correct deployment id value.
NOTE: It may have started around the time we upgraded to 2006 and updated to the latest ADK. I'm not sure exactly....
I currently work within a 2006 environment, but I approach this a little differently, but it works amazingly.
I use the OSDInjection.xml to have MECM automatically inject the UI++ files into the boot image when you regenerate them. Search for a guide, but I do not mind helping a bit.
Secondly, UI++ runs even before a prestart command as part of the WindowsPE startup from the unattend.xml and saves the variables to a file using UI++ built in functionality. These values include the SMSTSPrefferedAdvertID.
Lastly, the prestart command executes UI++ a second time, but without an interface, it only loads the variables that were saved from the first execution.
The task sequence runs without any problems and as of this morning.
I know it sounds complex, but in the end, it saves time as an alternative.
I wish I could help more directly with why your current process suddenly stopped working, although, it could be rebuilding/reloading your boot images from the ADK, and updating your distribution points. After that, regenerate your task sequence media, if applicable.