Details
-
Feature
-
Status: Released (View Workflow)
-
Minor
-
Resolution: Fixed
-
None
Description
Current Situation
The JobScheduler Universal Agent Powershell interface does not set the $PROFILE variable and does not load any profile.
Desired Behaviour
- $PROFILE.AllUsersAllHosts, $PROFILE.AllUsersCurrentHost
- <agent_data>\config\powershell\JobScheduler.PowerShell_profile.ps1
- $PROFILE.CurrentUserAllHosts, $PROFILE.CurrentUserCurrentHost
- Agent/Job runs as system account: the same profile as stated above is processed
- <agent_data>\config\powershell\JobScheduler.PowerShell_profile.ps1
- Agent/Job runs as user account: the profile is looked up in the Users sub-directory for the current user (indicated by <user_name>).
- <agent_data>\config\Users\<user_name>\powershell\JobScheduler.PowerShell_profile.ps1
- Agent/Job runs as system account: the same profile as stated above is processed
Attachments
Issue Links
- relates to
-
SET-117 Ship sample for PowerShell profile with JobScheduler Agent for Windows
- Released
- requires functional consideration of
-
JS-1747 Agent (Running jobs as a different user) - setting the JobScheduler/Agent specific environment variables for the target user
- Released
- mentioned in
-
Page Loading...