|
Post by JoshuaB on Feb 25, 2020 22:25:02 GMT
Hello, I have been using UI++ in our task sequence for a new windows 10 image for a while now. It runs as a pre-start command in the boot image and ask for the PC-Name and the image type. We have different images based on departments and I know it’s not the best way to handle this but it’s what I have until AD can be rebuilt. I am now working on Windows 7 to Windows 10 refresh and I’m running the UI++ in windows 7 to ask for details before running USMT and rebooting to WinPE for the Windows 10 install. When running UI++ it seems to work and after checking the logs it’s correctly setting the variables but after the reboot to WinPE the variables seem to be gone. I’m not sure what I’m doing wrong and I was hoping someone may have some advice?
|
|
|
Post by Jason on Mar 23, 2020 0:01:15 GMT
Unfortunately, UI++ can do much about this as it's up to the task sequence engine to persist the variables. I'm not sure why it wouldn't for this scenario (as to my knowledge it absolutely should) but as a workaround, you could use Variable Saving and Loading to/from a file: uiplusplus.configmgrftw.com/docs/actionconfig/variablesaveload.html.
|
|