Jump to content


Popular Content

Showing content with the highest reputation on 08/13/2023 in all areas

  1. Ok I figured out the issue with the blank message and title. I needed to use the x64 serviceUI.exe. I verified this by copying both architectures of ServiceUI and put them in the same folder as the script, but named each so I know which is which (ServiceUIx86 and ServiceUIx64). In the TS, I duplicated the group that holds all the steps, but set the command line so it uses the respective serviceUI, but also named the step with x86 and x64 so I can see which one failed etc. The one with the x86 presented the blank title and message, while the one with x64 showed perfectly. Now I just need to figure the method for it to auto close since I really need this for acquired deployments. Nonetheless, thanks again for the idea and tutorial for implementing this.
    1 point
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.