Admin

The Admin section of the PowerShell Orchestrator Server provides user account management for the administrative web interface. This is where administrators create and manage user accounts, reset passwords, and control access to the PowerShell Orchestrator Server.

Accessing the Admin section:

1. Log in to the PowerShell Orchestrator Server web interface at https://<server-name>:52866
2. Navigate to Admin in the main navigation

User list overview:

The Admin page displays all configured administrator accounts with their username and email address.

Adding a new user:

1. Click Add User
2. Fill in the user details:
   • Username — unique login name
   • Email — the user’s email address
   • Password — initial password must meet complexity requirements
3. Assign the Administrator role
4. Click Save

When a new user is created they are required to change their password on first login.

Password requirements:

Account security settings:

If a user account is locked after failed login attempts wait 15 minutes for the lockout to expire or have another administrator reset the account.

Changing your own password:

1. Click your username in the top-right corner of the interface
2. Select Change Password
3. Enter:
   • Current password
   • New password
   • Confirm new password
4. Click Update Password

Forced password change:

All new user accounts are created with a forced password change flag enabled. On first login the user is automatically redirected to the Change Password page and must set a new password before accessing the dashboard.

Security best practices:

The following security practices are recommended for PowerShell Orchestrator Server administration:

• Change the default administrator password immediately after first login
• Use strong unique passwords for all accounts
• Replace the self-signed certificate with a CA-signed certificate in production
• Restrict server firewall rules to known agent IP addresses where possible
• Enable HMAC payload verification in high-security environments
• Regularly review job execution logs for unexpected activity
• Keep the server and agents updated to the latest versions

Communication security:

All communication between the server and agents uses HTTPS/TLS encryption. Additional security options available in the server configuration include:

[Your administrator should review the appsettings.json configuration to enable HMAC signature verification and certificate pinning if required by your organization’s security policy.]

Script security:

PowerShell scripts are stored centrally on the server and downloaded to agents on demand at job execution time. Additional script security controls include:

[Your administrator should confirm the appropriate PowerShell execution policy and timeout settings for your environment when configuring agent deployments.]