ADHOC_Update_CXT_Timeout.ps1 — Update ClaimsXten Timeout Interval

A small, purpose-built PowerShell utility to update the ClaimsXten timeout setting to 120 in the product’s XML configuration. This change was used to mitigate NCCI Market errors prior to the R59 (Feb 1) release, which now hard‑codes this behavior.

Script header: Original/Last Updated: 2022‑02‑27.
Note: As of R59, this script is no longer required in normal operations.

---

What it does

• Opens a file picker so you can choose the ClaimsXten XML config.
• Connects (optionally) to a remote machine using PowerShell Remoting.
• Edits the XML to set the ClaimsXten timeout value to 120.
• Saves the file and prints a success or error message.
• Cleans up any PSSession created by the script.

---

Prerequisites

• Windows PowerShell 5.1 (or newer, Desktop edition).
• Permissions to read/write the target XML file.
• If running against a remote server:
  • PowerShell Remoting enabled on the target (Enable-PSRemoting).
  • Network/Firewall allows WinRM.
  • You have credentials/rights on that server.

Because this is an ad‑hoc script, there is no dry‑run mode. Create a backup before you run it (see below).

---

How to run

1. Open Windows PowerShell as an Administrator.
2. Navigate to the folder containing the script:

   cd <path-to-script>

3. Execute:

   .\ADHOC_Update_CXT_Timeout.ps1

4. When prompted with the Open File dialog, browse to the ClaimsXten XML configuration file and select it.
5. Wait for the script to finish. You’ll see a success message if the value was updated, or an error message if something went wrong.

If the script connects to a remote host, it will create a PSSession, perform the edit, and then remove the session before exiting.

---

Safety first (recommended)

• Make a backup of the XML file before running:

  Copy-Item 'C:\Path\to\config.xml' 'C:\Path\to\config.xml.bak'

• Test locally on a copy of the file to confirm the change before running on production.
• Ensure ClaimsXten version actually requires this change (pre‑R59). For R59 and later, the timeout is already coded by the release.

---

Troubleshooting

• Access denied / locked file
  Close any app that might be holding the file open. Run PowerShell as Administrator.
• Couldn’t find the timeout node
  Make sure you selected the correct ClaimsXten configuration file. If your environment uses a different node/attribute name, you may need to adapt the script.
• Remoting errors (WinRM cannot complete the operation, etc.)
  Verify Enable-PSRemoting on the target, network reachability, and that your account has rights.
• Session cleanup
  The script removes its session on exit. If you stopped it mid‑run, clear any lingering sessions:

  Get-PSSession | Remove-PSSession

---

Notes & scope

• This script was designed as a temporary operational fix for environments prior to R59.
• Keep it in your ops toolbox for emergency use, but prefer upgrading to R59+ where possible.

---

Attribution

• Author: TW
• Purpose: Update ClaimsXten timeout to 120 to prevent NCCI Market errors (pre‑R59).