Forum Discussion

Elliot_the_Goose's avatar
Elliot_the_Goose
Copper Contributor
May 28, 2020

I'll give this a try, for more information though..

 

This has only began happenning since upgrading from SCCM 1906 to SCCM 1910, the Operating systems are on v1803 and upgrading to v1909 🙂

 

gwblok 

gwblok's avatar
gwblok
Iron Contributor
May 28, 2020

Elliot_the_Goose 

Ok, our Splash screen (which is completely PowerShell) didn't have any issues between any of the CM Upgrades.
https://garytown.com/windows-splash-screen-for-the-task-sequence-progress

Feel free to take a look.  There have been changes in the TS engine with each build, but I haven't seen any issues with any of the places I've used ServiceUI.exe in my testing.

If you use ServiceUI to launch a Command Prompt, do you get the same issue?  Basically do you get error anytime you use ServiceUI in your TS, or just with your Splash Screen?
Other examples of using ServiceUI: https://garytown.com/launch-application-in-task-sequence-in-os-serviceui

 

  • Elliot_the_Goose's avatar
    Elliot_the_Goose
    Copper Contributor
    May 29, 2020

    gwblok  - Thanks for the response, So after more testing.. I can run ServiceUI.exe manually as Domain admin and it will launch programs succesfully.

     

    However when i use PSEXEC and run ServiceUI as the System Account, it times out (even when using it to launch something as basic as notepad.exe)

     

    So this points to me that System doesn't have the permissions to launch a process as a user (Error 5 above).. However i have no idea what permissions are required for this.

    • Elliot_the_Goose's avatar
      Elliot_the_Goose
      Copper Contributor
      Jun 02, 2020

      After more investigation, and talking with a Microsoft MVP.. the outcome for us has been this.

       

      ServiceUI.exe is an ancient program with no support anymore, and is seen as a security flaw.

      Therefore it could be a case of the SCCM Upgrade has changed the Task Sequence engine, which is recognising ServiceUI.exe as a security risk and blocking it.

       

      We are looking into reverting to Windows Servicing to perform our OS updates instead.

      • Shandiaak's avatar
        Shandiaak
        Copper Contributor
        Aug 12, 2020

        Elliot_the_Goose Hello Elliot, thanks for this. I am not seeing this statement anywhere in the MeM release notes though. Is this somehow intentionally not public information?

         

        I am currently building a task sequence with a pop up solution which needs to be interactive and I am running into this very issue. But interesting part is that the pop up executed via ServiceUI.exe works on 1809 while it stops working after the OS gets upgraded to 1909 via the same Task sequence.

         

        Are there any other possibilities to overcome this issue instead of trashing the whole framework and going to Windows 10 servicing? 

         

        Thanks,

        Petr

Resources