I have an OSD advertisement and when I try to run a command either directly or from a software package that is in the OSD task sequence, it just hangs on the step. This is only an issue within the Windows environment, I don't have this issue in the WinPE environment.
So for example, I have a task sequence step calling Windows Paint, it will bring up the OSD task sequence dialog box saying it is running the step, but it doesn't actually run from a visible standpoint, nor do you see the actual mspaint.exe process. I see this issue whether I call notepad.exe, a custom executable or whatever and whether I do it as a direct command or as an actual SCCM software package.
I have the command calling %windir%\system32\mspaint.exe and this doesn't work even when specifying the working directory. Below is from the SMTS log, so you can see it is calling the command, but it doesn't seem to actually do anything. Any ideas?
Expand a string: smsswd.exe /run: %windir%\system32\mspaint.exeTSManager9/9/2016 10:29:15 AM4280 (0x10B8)
Expand a string: TSManager9/9/2016 10:29:15 AM4280 (0x10B8)
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.
I have an OSD advertisement and when I try to run a command either directly or from a software package that is in the OSD task sequence, it just hangs on the step. This is only an issue within the Windows environment, I don't have this issue in the WinPE environment.
So for example, I have a task sequence step calling Windows Paint, it will bring up the OSD task sequence dialog box saying it is running the step, but it doesn't actually run from a visible standpoint, nor do you see the actual mspaint.exe process. I see this issue whether I call notepad.exe, a custom executable or whatever and whether I do it as a direct command or as an actual SCCM software package.
I have the command calling %windir%\system32\mspaint.exe and this doesn't work even when specifying the working directory. Below is from the SMTS log, so you can see it is calling the command, but it doesn't seem to actually do anything. Any ideas?
Share this post
Link to post
Share on other sites