New-RdpSpnAuditPlan

The New-RdpSpnAuditPlan command is used to identify potential issues with Remote Desktop Services (RDS) SPNs in Active Directory. This command helps organizations ensure that their RDS infrastructure is properly configured and compliant with security best practices.

Key stakeholders who use this command include:

• IT administrators responsible for RDS deployments
• Security teams tasked with ensuring compliance with organization-wide security policies

Potential risks associated with misconfigured RDS SPNs include:

• Compromised security posture due to weak or missing credentials
• Inability to troubleshoot issues related to RDS connectivity and performance

Managers typically care about the output of this command when it indicates potential security vulnerabilities or compliance issues that require immediate attention.

To use New-RdpSpnAuditPlan, follow these steps:

1. Ensure you have a valid connection to Active Directory using the Connect-AD cmdlet.
2. Run Get-RdpSpnCandidate to retrieve the expected set of TERMSRV SPNs for your organization.
3. Use New-RdpSpnAuditPlan with the output from step 2 as input, specifying any additional parameters as needed (e.g., -ComputerName, -Credential).

Example code:

$expectedSPNs = Get-RdpSpnCandidate -Verbose
$result = New-RdpSpnAuditPlan -Candidate $expectedSPNs
$result | Export-Csv -Path "C:\AuditResults.csv" -NoTypeInformation

Watchpoints:

• Verify that your AD connection is established and functioning correctly before running the command.
• Use caution when modifying or deleting existing SPNs, as this can impact RDS connectivity.

New-RdpSpnAuditPlan is a PowerShell cmdlet used to compare actual TERMSRV SPNs in Active Directory against expected values. This helps ensure that RDS services are properly configured and secure.

To use this command:

1. Get the list of expected TERMSRV SPNs using Get-RdpSpnCandidate.
2. Compare these expected values against the actual SPNs in AD.
3. Identify any missing or orphaned SPNs, which may indicate security vulnerabilities.

If you’re stuck, try:

• Verifying your AD connection and configuration
• Reviewing the command’s output to understand potential issues

Licence terms are proprietary and are supplied with the purchase, subscription or evaluation agreement. No open-source licence is granted.

The New-RdpSpnAuditPlan command adheres to standard data-handling best practices, including:

• Secure transit: Data is transmitted securely using established AD connections.
• At-rest security: SPN data is stored securely in Active Directory.
• Audit trail: Command output provides a clear audit trail of potential issues.

Compliance requirements for this command include adherence to organization-wide security policies and regulations related to RDS deployments.