Powershell Script

Question

Powershell Script

Handian Sudianto 6,071

I have powershell script to get defender status for all servers using below command.

Below command was successfull if I run the script manually but if we run this script using schedule task the script is running but no any result. Anyone know why?

$remoteComputer = 'server01'
$session = New-PSSession -ComputerName $remoteComputer
Invoke-Command -Session $session -ScriptBlock {
$status = Get-MpComputerStatus

1 answer

Your answer

Answer 1

MotoX80 36,181

When you run it manually, it runs as your account which has administrator access to server01. The most likely problem is that the account that you configured to run the task as does not have admin access. Also "System" will not work.

Add a transcript to the script so that you can see what it does.

Start-Transcript C:\YourLogFolder\MyTask.log
$remoteComputer = 'server01'
$session = New-PSSession -ComputerName $remoteComputer
Invoke-Command -Session $session -ScriptBlock {
$status = Get-MpComputerStatus
...
Stop-Transcript

Handian Sudianto 6,071 Reputation points

2025-06-05T00:12:29.1966667+00:00

hi @MotoX80

yes i think the issue related to the credentials. How we can solve this?

New-PSSession : [server01] Connecting to remote server server01 failed with the following error message : WinRM cannot process the request. The following error with errorcode 0x8009030e occurred while using Kerberos authentication: A specified logon session does not exist. It may already have been terminated.
Possible causes are: -The user name or password specified are invalid. -Kerberos is used when no authentication method and no user name are specified. -Kerberos accepts ___domain user names, but not local user names. -The Service Principal Name (SPN) for the remote computer name and port does not exist. -The client and remote computers are in different domains and there is no trust between the two domains. After checking for the above issues, try the following: -Check the Event Viewer for events related to authentication. -Change the authentication method; add the destination computer to the WinRM TrustedHosts configuration setting or use HTTPS transport. Note that computers in the TrustedHosts list might not be authenticated. -For more information about WinRM configuration, run the following command: winrm help config. For more information, see the about_Remote_Troubleshooting Help topic. Other Possible Cause: -The ___domain or computer name was not included with the specified credential, for example: DOMAIN\UserName or COMPUTER\UserName.
MotoX80 36,181 Reputation points

2025-06-05T01:04:01.05+00:00

What account did you configure the task to run with?

We never used personal accounts because we were required to change our passwords every 60 days. So for any automated process we used a dedicated service account whose password never expired and where only a very small number of admins knew what the password was.

MS also introduced Group Managed Service Accounts which I never used, but might fit your requirements.

https://techcommunity.microsoft.com/blog/itopstalkblog/step-by-step-how-to-work-with-group-managed-service-accounts-gmsa/329864

https://learn.microsoft.com/en-us/windows-server/identity/ad-ds/manage/group-managed-service-accounts/group-managed-service-accounts/group-managed-service-accounts-overview
Handian Sudianto 6,071 Reputation points

2025-06-05T02:10:14.97+00:00

hi @MotoX80

In the schdule task the author set using admin ___domain account.
MotoX80 36,181 Reputation points

2025-06-05T02:28:57.1433333+00:00

Can you launch Powershell.exe with that account using runas.exe and then run the script? Check the security event log on server01 for errors.
Handian Sudianto 6,071 Reputation points

2025-06-05T03:22:02.7133333+00:00

if i run manually by opening the poweshell as admin ___domain and run the script, then the script was work fine.
MotoX80 36,181 Reputation points

2025-06-05T12:10:30.8033333+00:00
In the schdule task the author set using admin ___domain account.

The author of the task does not matter.

Set the account using the "Change user or group" button. Make sure that you have these 3 options set. Run the task if the user is logged on or not. Do not select "Do not store password". And also select "Run with highest privileges".

if i run manually by opening the poweshell as admin ___domain

Did you use runas.exe to launch Powershell as the admin account, or did you do a desktop (RDP) logon? The task scheduler does a user impersonation and not a full desktop logon. If you have a user logon script for desktop logon, that will not be executed by the task scheduler.

Are network shares visible to your account and also the admin account? Test that manually and also in the script (scheduled task).

dir \\server01\c$ dir \\server01.YourDomainName.com\c$ net.exe view server01 net.exe view server01.YourDomainName.com
MotoX80 36,181 Reputation points

2025-06-13T16:13:02.9833333+00:00

Did you get it working?

Share via

Powershell Script

1 answer

Your answer