Ortho Chart Remote App Credential Issue

Introduction: The RDS_Creds_Reset script has been deployed via Group Policy and a shortcut has been placed on everyone's desktop. This guide explains how to use the script when encountering the credential issue when opening OrthoChart.

 

Step-by-Step Instructions:

  1. Locate the RDS_Creds_Reset Script:

    • On your desktop, you should find a shortcut named "RDS_Creds_Reset." 
  2. Double-Click the Script:

    • When you encounter the credential issue when trying to open OrthoChart, simply double-click the "RDS_Creds_Reset" script. This will initiate the script's execution.
      • YOU MAY ENCOUNTER THIS ERROR, just hit ok and let the script run.
  3. Let the Script Run:

    • Allow the script to run its course. It will perform multiple tasks we have found that help resolve the credential issue, which include rebooting the computer to resolve the issue.
  4. Wait for the Reboot:

    • After the script has run, your computer will automatically reboot. This is a normal part of the process.
  5. Wait 10 Minutes:

    • After the computer has rebooted, wait for a minimum of 10 minutes. 
  6. Check OrthoChart:

    • Attempt to open OrthoChart after the 10-minute wait period. If it opens successfully, the issue is likely resolved, and you can continue your work as usual.
  7. If OrthoChart Doesn't Open:

    • In the event that OrthoChart still does not open or the issue persists, double-click the "RDS_Creds_Reset" script shortcut again.
  8. Repeat the Process:

    • Allow the script to run once more, followed by the automatic computer reboot. After this, wait for another 10 minutes.
  9. Retry OrthoChart:

    • Try to open OrthoChart again. It should function as expected after the second run of the script and reboot.

Conclusion: The RDS_Creds_Reset script, deployed via Group Policy, is a reliable solution for resolving issues related to OrthoChart. By following these steps, you can ensure a high success rate in resolving such problems without extensive downtime.

0 Comments

Article is closed for comments.
Powered by Zendesk