Hii! I need to deploy package.msi without startup to n client because these are all server and they cant restart.
I cant use psexec or sccm tools
I think the only way is: scheduled task in gpo, but doesnt work.
In the task i set: action: Create name: deploy NT AUTHORITY\System user account Run whether user is logged on or not Run with highest privileges triggers tab: Once time - status enabled action tab: Start a program; program/script: powershell.exe add arguments: -NonInteractive -ExecutionPolicy Bypass \netsharedpath\package.msi condition: start only if the following network connection is available: any connection settings: allow task to be run on demand
what's wrong?
i see no error in gpo log / task scheduler log
windows server 2019
I edit my gpo from the gpom and add my scheduled task under computer because I need it to be deployed on all the computers within the OU
I don't see any errors in the logs, and the task is not created and consequently the.msi is not installed
I tried starting msiexec.exe instead of powershell, the result is the same. in the event viewer under group policy I have no errors, the gpo apparently is not taken into consideration also because it does not create any tasks. I don't have a log from which to troubleshoot
Manual Trigger Check: Try manually triggering the scheduled task from the Task Scheduler on a client machine to confirm it can execute as expected. I can't do that because the task I create in the GPO is not created in the task scheduler and therefore I cannot start it on demand the msiexec and/or the script I created work if started manually on the client. What doesn't work is the scheduled task, I don't even understand how to find logs on the scheduled task since if I tell it to create it it doesn't create it or execute it
EDIT:
so: if I create the task manually from the task scheduler on the client, it works perfectly.
If I create the task in the GPO --> computer configuration --> preferences --> control panel settings --> scheduled task
--> new task and then the configuration parameters that I mentioned in the first message, he does not create this task in the client.
After some tests I discovered that the script did not start directly from the share folder due to execution policy problems, so I added 2 fundamental steps: create a folder on the client, copy the script from the share locally, and finally start the script locally.
Now the task is configured perfectly and if I create it manually on the client, with these latest changes, it works.
However, from the GPO it doesn't work, or rather only if I restart the client I see the task created in the task scheduler without it ever having been executed.
I need a solution WITHOUT REBOOTTING THE CLIENTS.