1,745 questions
I run local on-prem Exch stuff under a service account that has the needed perms, not the system account. That always works for me.
Scheduled Task Cannot connect to Exchange PowerShell with System account
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(108.80000000000001, 33%, 20%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EM1%3C/text%3E%3C/svg%3E)
MichaelFuller-1588
66
Reputation points
I created a task to run a health report. The task runs under my credential but will not connect to Exchange PowerShell when I run it under the System account. I used transcription and saw that the script was running but failing to connect to any Exchange server to utilize the Exchange commands. I am not sure what could be causing the issue. I do not think it is a permissions issue because it is the Exchange server system account. PS remoting is enabled and there are no issues with PS remoting other than this account. I am running the task with the highest privileges. The script is Test-ExchangeServerHealth.ps1 from GitHub.
Windows development Internet Information Services
Exchange Exchange Server Management
7,920 questions
Windows for business Windows Server User experience Other
20,212 questions
3 answers
Sort by: Most helpful
-
Andy David - MVP 157.4K Reputation points MVP Volunteer Moderator2022-05-24T18:31:38.977+00:00 -
MichaelFuller-1588 66 Reputation points
2022-05-24T18:49:20.017+00:00 Unfortunately, saving credentials on a scheduled task is blocked in this environment due to it being a STIG violation. So, that is not an option.
Sign in to comment -
-
Andy David - MVP 157.4K Reputation points MVP Volunteer Moderator
2022-05-24T19:17:42.81+00:00 How about using a managed account instead?
-
MichaelFuller-1588 66 Reputation points
2022-05-25T13:24:16.82+00:00 Group Managed Service Accounts (gMSA) are not supported in on-premises Exchange Server environments and thus cannot be used to perform Exchange things.
-
Andy David - MVP 157.4K Reputation points MVP Volunteer Moderator
2022-05-25T13:48:13.79+00:00 Would that apply to the account running the scheduled task though?
I assume your actual connection to the Exchange Server in the powershell script itself is using a service account yes?
Sign in to comment -
-
MotoX80 36,291 Reputation points2022-05-25T20:38:30.05+00:00 In an AD environment a task running as SYSTEM will be seen as the YourDomainName\YourServerName$ account to another computer. That is the computer account within AD.
Can you grant that account access within Exchange? (I am not an Exchange guy.)
-
MichaelFuller-1588 66 Reputation points
2022-05-26T11:56:29.997+00:00 The system account has the permissions of the server. The server has full control of the Exchange environment. You are correct in thinking about permissions because you must have Exchange permissions to connect to Exchange PowerShell. I added the server to Organization Management just to test my sanity. That didn't resolve the issue. I believe the issue is that the System account is not able to provide the necessary credentials to connect. I was hoping someone could prove or disprove that. My work around is to use the system account to schedule the task and use a service account with encrypted credentials within the script to connect to Exchange.
Sign in to comment -