Hi, I have SQL server Agent job using "Runs as" Proxy, with Proxy setup with domain account "domain\ABC".
The job runs cmdexec to run ps1 and connect to Sharepoint.
Case 1.When this job runs, it runs under C:\Users\Default (Default profile) and not under C:\Users\ABC, and it fails with "unable to connect to remote server"
Case 2. When smbdy RDPs as ABC or run as ABC on that server (ABC profile invoked) then this job runs successfully , it runs under C:\Users\SQLAgent (SQLAgent profile)
For testing purposes we gave ABC admin permissions on both windows and SQL Server. Without admin permissions Case 2 fails as well with "unable to connect to remote server".
Could this Default profile cause the job failure/with "unable to connect to remote server"?
Is it normal for Proxy to run under Default profile, or should it be Proxy-specific account (ABC)?
Should Powershell be configured somehow for that Default profile (how?)?
What policies, extra permissions or config are needed to get this right? SQL agent has all standard permissions and functional for other types of jobs.