-
-
-
Automatically back up configuration sets using WEM APIs and Windows PowerShell
-
Manage DaaS-provisioned non-domain-joined machines using WEM
-
Protect Citrix Workspace™ environments using process hierarchy control
-
Troubleshoot scripted task execution problems in Monitor
-
Troubleshoot VDA registration and session launch issues using scripted tasks
-
Use Windows events as triggers to detect VDA registration issues
-
This content has been machine translated dynamically.
Dieser Inhalt ist eine maschinelle Übersetzung, die dynamisch erstellt wurde. (Haftungsausschluss)
Cet article a été traduit automatiquement de manière dynamique. (Clause de non responsabilité)
Este artículo lo ha traducido una máquina de forma dinámica. (Aviso legal)
此内容已经过机器动态翻译。 放弃
このコンテンツは動的に機械翻訳されています。免責事項
이 콘텐츠는 동적으로 기계 번역되었습니다. 책임 부인
Este texto foi traduzido automaticamente. (Aviso legal)
Questo contenuto è stato tradotto dinamicamente con traduzione automatica.(Esclusione di responsabilità))
This article has been machine translated.
Dieser Artikel wurde maschinell übersetzt. (Haftungsausschluss)
Ce article a été traduit automatiquement. (Clause de non responsabilité)
Este artículo ha sido traducido automáticamente. (Aviso legal)
この記事は機械翻訳されています.免責事項
이 기사는 기계 번역되었습니다.책임 부인
Este artigo foi traduzido automaticamente.(Aviso legal)
这篇文章已经过机器翻译.放弃
Questo articolo è stato tradotto automaticamente.(Esclusione di responsabilità))
Translation failed!
Troubleshoot scripted task execution problems in Monitor
DaaS Monitor enables you to run scripted tasks from Filters > Machines > Machine actions > Run scripted task. However, you might encounter errors when attempting to run a scripted task, such as:
WEM Agent is not foundWEM Agent is not recently connectedWEM Agent version is not supported
This article describes the common causes of these errors and how to resolve them.
WEM Agent not installed
Cause: The Run scripted task feature requires the WEM Agent to be installed. In Citrix Virtual Apps and Desktops 2507 LTSR and later, the WEM Agent is installed automatically on VDAs. In earlier versions, the agent must be installed manually.
Resolution: Verify that the WEM Agent is installed on the target machine. The default installation path is:
C:\Program Files (x86)\Citrix\Workspace Environment Management Agent
WEM Agent running in Basic Deployment mode
Cause: When the WEM Agent runs in the Basic deployment mode, it operates offline and does not connect to the network.
Scripted tasks require the agent to run in the Cloud service deployment mode and connect to the WEM service using AD-joined (or called Cloud Connector method) or Non-domain-joined method.
Resolution:
- Use the WEM Health Check Tool to verify the agent mode. The tool is located at:
C:\Program Files (x86)\Citrix\Workspace Environment Management Agent\Health Check Tool -
To switch the agent to AD-joined method in the Cloud service deployment mode, complete one of the following actions:
- Use the Health Check Tool to specify the Cloud Connector IP address or FQDN.
- Use Group Policy to distribute Cloud Connector settings across multiple VDAs. For more information, see Configure group policies.
WEM Agent not registered to WEM service
Cause: The WEM Agent must be registered to a configuration set in the WEM service. Scripted tasks cannot run if the registration is incomplete.
Resolution:
Check the agent’s registration status:
- In the WEM web console, go to Monitoring > Agents > Registrations.
- Verify whether the agent appears as Registered or Unregistered.
-
If the agent is unregistered or registration issues persist, review the following configuration set scenarios to further troubleshoot the issue:
Agent not bound to any configuration set
Cause: No configuration set is assigned to the agent.
Resolution: Assign a configuration set using one of the following methods:
- Configuring WEM options when creating or editing a machine catalog in Web Studio
- Creating Directory Objects (OU, group, or individual machine) in the WEM web console.
Agent bound to multiple configuration sets
Cause: Conflicting assignments exist. For example:
- A machine catalog is bound to Configuration Set A, and
- The Domain Computers group is bound to Configuration Set B.
Resolution: In the WEM web console, go to Directory Objects, review the bindings, and remove conflicting configuration set assignments.
WEM Agents not connected to the WEM service
Cause: The agent cannot connect to the WEM service due to network issues or firewall restrictions.
Resolution: Verify the network environment and ensure that all required connections to the WEM service are allowed.
WEM Agent version limitation for scripted tasks
Cause: WEM Agent versions earlier than 2207.1.0.1 do not support running scripted tasks.
Resolutio:n Upgrade the WEM Agent to a supported version.
WEM service upgrade in progress
Cause: The WEM service is temporarily unavailable during a WEM infrastructure service upgrade.
Resolution: Wait until the upgrade completes, and then retry the operation.
WEM database archived
Cause: The WEM database can be archived if no operations occur and no active agents connect for 30 consecutive days.
Resolution: Unarchive the database by manually opening the WEM web console. This action automatically triggers the unarchive process.
Share
Share
This Preview product documentation is Citrix Confidential.
You agree to hold this documentation confidential pursuant to the terms of your Citrix Beta/Tech Preview Agreement.
The development, release and timing of any features or functionality described in the Preview documentation remains at our sole discretion and are subject to change without notice or consultation.
The documentation is for informational purposes only and is not a commitment, promise or legal obligation to deliver any material, code or functionality and should not be relied upon in making Citrix product purchase decisions.
If you do not agree, select I DO NOT AGREE to exit.