Create a remediation rule using custom-signed PowerShell scripts
Prerequisites
You must be signed in to TechDirect as a Connect and manage administrator or Connect and manage technician.
PCs must have an active ProSupport Plus or ProSupport Flex for Client service plan.
The PowerShell script must be signed.
To avoid issues with proxy connections, the PCs must connect to
https://remediation.dell.com.
For the diagnostic and remediation scripts to execute, the script must be self-signed or signed by a certificate authority, and then deployed to all target PCs. For information about how to generate self-signed certificates, see
New-Self Signed Certificate. These certificates must be imported to the target PC in the following locations:
[Certificates - Local Computer\Trusted Root Certification Authorities\Certificates]
[Certificates - Local Computer\Trusted Publishers\Certificates]
The remediation script executes only if the diagnostic script returns a nonzero exit code. Ensure that your diagnostic script is configured to return a nonzero exit code if remediation is required. For more information about exit codes and using them in your diagnostic and remediation scripts, see
Returning an exit value. The following example explains the use of exit codes in PowerShell scripts. This script returns an exit code value of 1 if Chrome is running and an exit code value of 0 if Chrome is not running.
# If chrome is running return 1
if(Get-Process chrome)
{
Write-Host "Chrome is running"
exit 1
}
# If chrome is not running return 0
else
{
Write-Host "Chrome is not running"
exit 0
}
About this task
Remediation rules help identify and remediate issues within your PC fleet proactively. You can remediate the PCs by uploading diagnostic and remediation scripts to detect and resolve any issues that have occurred on the PC.
When the diagnostic script runs, the script must return a zero or nonzero code. A zero exit code depicts that there were no issues detected and a nonzero exit code depicts that there were issues detected on the PC. Any nonzero exit code triggers the remediation script that is uploaded to resolve the issues.
Steps
From the
TechDirect dashboard, go to
Connect and manage > Manage PC fleet > Connect and manage PCs > Manage > Remediation rules.
The
Remediation rules page is displayed.
Click
Create rule.
The
Create rule page is displayed.
From the
Select category list, select
PowerShell.
In the
Set up your rule preferences section, perform the following scripts:
Test and upload a diagnostic script.
The diagnostic script runs as per the customized rule conditions to detect any issues that have occurred on the PC.
Optionally, enter a description for the diagnostic script.
Test and upload a remediation script.
If any issues are detected when the diagnostic script runs, this remediation script runs to resolve the issues.
Optionally, enter a description for the remediation script.
Select the occurrence and frequency at which the rule should run.
NOTE:Rules can be run once or based on the selected frequency—daily or weekly, and in the morning between 6:00 AM and 11:00 AM or evening between 12:00 PM and 8:00 PM.
Click
Next.
In the
Save and apply the rule on the selected sites and groups section, perform the following steps:
Select the site and group to which you want to assign the rule.
NOTE:The
Sites & groups list displays only PCs that have an active ProSupport Plus or ProSupport Flex for Client service plan.
Enter the rule name.
NOTE:Ensure that you enter a unique rule name between 3 and 50 characters that may contain alphabets, numbers, space, and one of these special characters . , # ( ) - _ / &.
Enable
Apply rule to activate the rule.
Click
Create rule.
Results
The remediation rule is saved and is displayed on the
Remediation rules page.
NOTE:By default, the remediation rule is not applied to a new site or groups that are created after the creation of the remediation rule. You must edit the remediation rule to include PCs in the new site or group, to the rule. See
Update a remediation rule.
Data is not available for the Topic
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please select whether the article was helpful or not.
Comments cannot contain these special characters: <>()\