PENDINGUnable to push powershell script file via sccm

SagiVarma

SagiVarma

Member
9
0
1
Hi All,

I am trying to execute powershell script file as application from SCCM. The file is shown in the software center of the client device and when I install the file it shows error as 0xFFFFD0000(-196608)

Attachments

  • Error.png
    Error.png
    32.2 KB · Views: 4
Garth

Garth

Well-Known Member
Staff member
1,757
149
63
Have you tested your script using the local system account?

Are you using a program or application to deploy this?
OP
SagiVarma

SagiVarma

Member
9
0
1
  • Thread Starter
  • #5
Have you tested your script using the local system account?

Are you using a program or application to deploy this?
Hi Garth,

We created an application.


Yes. I tested my script on a local system and it runs successfully and installs the msi file and exe file and creates bgptray.exe on the startup menu and replaces it with bgp tray agent shortcut.

我还测试了该脚本时SCCM Server path location and executed in powershell with Network path defined and it ran successfully.
OP
SagiVarma

SagiVarma

Member
9
0
1
  • Thread Starter
  • #6
Have you tested your script using the local system account?

Are you using a program or application to deploy this?
Hi Garth,

We create an application in SCCM and trying to deploy to a test device.

Thanks & Regards,
Sagi Varma
Garth

Garth

Well-Known Member
Staff member
1,757
149
63
Hi Garth,

We created an application.


Yes. I tested my script on a local system and it runs successfully and installs the msi file and exe file and creates bgptray.exe on the startup menu and replaces it with bgp tray agent shortcut.

我还测试了该脚本时SCCM Server path location and executed in powershell with Network path defined and it ran successfully.
For 100% clarity, you use the Local System account. e.g. you use psexec to access the account and then run the script.

I'm unclear you last statement saying you deploy it with ConfigMgr and it was successful. If this is the case then what is the problem?
  • Like
Reactions: SagiVarma
OP
SagiVarma

SagiVarma

Member
9
0
1
  • Thread Starter
  • #8
Hi Garth,

I opened the Powershell ISE window on the test device which is a windows 10 workstation and executed the script which worked fine. I created an application in SCCM for the script and when I deployed to the windows 10 workstation. the application is shown in the software center. when I run it from software center then the error comes as shown in my earlier screenshot.

Thanks & Regards,
Sagi Varma
Garth

Garth

Well-Known Member
Staff member
1,757
149
63
Hi Garth,

I opened the Powershell ISE window on the test device which is a windows 10 workstation and executed the script which worked fine. I created an application in SCCM for the script and when I deployed to the windows 10 workstation. the application is shown in the software center. when I run it from software center then the error comes as shown in my earlier screenshot.

Thanks & Regards,
Sagi Varma
So that is NOT testing with the local system account. Please read the blog and use PSexec to access the local system account and test the script again.
OP
SagiVarma

SagiVarma

Member
9
0
1
  • Thread Starter
  • #10
Hi Garth,

The client's workstation does not have PsTools in it. Please note the powershell script is located on the SCCM server E drive which is a shared folder. I downloaded the PsTools and copied to C drive but I am unable to execute the psexec utility.
OP
SagiVarma

SagiVarma

Member
9
0
1
  • Thread Starter
  • #12
HI Garth,
My client provided me Domain account to use on the client workstation. I do not have local system account to execute the script.

Thanks & Regards,
Sagi Varma
Garth

Garth

Well-Known Member
Staff member
1,757
149
63
HI Garth,
My client provided me Domain account to use on the client workstation. I do not have local system account to execute the script.

Thanks & Regards,
Sagi Varma
So, what you are saying is that you can't test the script in the same manor that ConfigMgr will execute it. You need to talk to your client about allowing you to solve this problem.

This goes to the first step of troubleshooting an application install. Does it work outside of ConfigMgr with the local system account. Until it passes this step, there is no point moving forward.
OP
SagiVarma

SagiVarma

Member
9
0
1
  • Thread Starter
  • #14
Hi Garth,

Thanks for your continuous support. I identified one of the powershell script line was not pointing to the required path for creating the bitglass agent tray shortcut location. I set it to the correct path and deployed the application to test device which is successful.

If I face any further issues I will get back to you.

Thanks & Regards,
Sagi Varma
OP
SagiVarma

SagiVarma

Member
9
0
1
  • Thread Starter
  • #15
Hi Garth,

There is one more request regarding this script. The shortcut icon should be copied to the Default profile start Menu on windows 10 and windows 11. By default, windows 10 default profile has start Menu under default profile but windows 11 does not have it.
Please suggest.

Thanks & regards,
Sagi varma
Garth

Garth

Well-Known Member
Staff member
1,757
149
63
Hi Garth,

There is one more request regarding this script. The shortcut icon should be copied to the Default profile start Menu on windows 10 and windows 11. By default, windows 10 default profile has start Menu under default profile but windows 11 does not have it.
Please suggest.

Thanks & regards,
Sagi varma
Look at your environment variable. There will be one for the shared desktop.