Error Message: Cannot Start Desktop “[DesktopName]” When Trying to Launch a Desktop VDA

Open an RDP connection to the Desktop VDA that cannot be launched and check if there is another existing connected/disconnected session in the Task manager. If that is the case then logoff the session and try to launch the published Desktop again.

Note: If the session cannot be logged of from the Task Manager, that probably is because it is an administrator account. Administrator accounts cannot be logged off from the Task Manager. In that case try to contact the person who owns the administrator account and request to logoff. Otherwise, proceed to reboot the host. Then try to launch the published Desktop again.


  • No Related Posts

Understanding Workspace Environment Management (WEM) System Optimization

The WEM System Optimization feature is a group of settings designed to dramatically lower resource usage on a VDA on which the WEM Agent is installed.

These are machine-based settings that will apply to all user sessions.

Managing Servers with different Hardware Configurations

Sets of VMs may have been configured with different hardware configurations. For instance some machine may have 4 CPU cores and 8GB RAM, while others have 2 CPU Cores and 4GB RAM. The determination could be made such that each server set requires a different set of WEM System Optimization settings. Because machines can only be part of one WEM ConfigSet, administrators must consider whether they need to create multiple ConfigSets to accommodate different optimization profiles.

WEM System Optimization Settings

User-added image

Fast Logoff

A purely visual option that will end the HDX connection to a remote session, giving the impression that the session has immediately closed. However, the session itself continues to progress through the session logoff phases on the VDA.

CPU Management

CPU Priority:

You can statically define the priority for a process. Every instance of, for example, Notepad that is launched on the VDA will be launched with a priority of the desired CPU priority. The choices are:

  • Idle
  • Below Normal
  • Normal
  • Above Normal
  • High
  • Realtime *


CPU Affinity:

You can statically define how many CPU cores a process will use. Every instance of Notepad that is launched on the VDA will use the number of cores defined.

Process Clamping:

Process clamping allows you to prevent a process from using more CPU percentage than the specified value. A process in the Process Clamping list can use CPU up to the configured percentage, but will not go higher. The setting limits the CPU percentage no matter which CPU cores the process uses.

Note: The clamping percentage is global, not per core (that is, 10% on a quad-core CPU is 10%, not 10% of one core).

Generally, Process Clamping is not a recommended solution for keeping the CPU usage of a troublesome process artificially low. It’s a brute force approach and computationally expensive. The better solution is to use a combination of CPU spikes protection and to assign static Limit CPU / Core Usage, CPU priorities, CPU affinities values to such processes.

CPU Management Settings:

CPU Spikes Protection:

CPU Spikes Protection is not the same as Process Clamping. Process Clamping will prevent a process from exceeding a set CPU percentage usage value. Spikes Protection manages the process when it exceeds the CPU Usage Limit (%) value.

CPU Spikes Protection is not designed to reduce overall CPU usage. CPU Spikes Protection is designed to reduce the impact on user experience by processes that consume an excessive percentage of CPU Usage.

If a process exceeds the CPU Usage Limit (%) value, for over a set period of time (defined by the Limit Sample Time (s) value), the process will be relegated to Low Priority for a set period of time, defined by the Idle Priority Time (s) value. The CPU usage Limit (%) value is global across all logical processors.

The total number of logical processors is determined by the number of CPUs, the number of cores in the CPU, and whether HyperThreading is enabled. The easiest method of determining the total number of logical cores in a machine is by using Windows Task Manager (2 logical processors shown in the image):

User-added image

To better understand CPU Spikes Protection, let’s follow a practical scenario:

Users commonly work with a web app that uses Internet Explorer. An administrator has noticed that iexplore.exe processes on the VDAs consume a lot of CPU time and overall responsiveness in user sessions is suffering. There are many other user processes running and percentage CPU usage is running in the 90 percent range.

To improve responsiveness, the administrator sets the CPU Usage Limit value to 50% and a Idle Priority Time of 180 seconds. For any given user session, when a single iexplore.exe process instance reaches 50% CPU usage, it’s CPU priority is immediately lowered to Low for 180 seconds. During this time iexplore.exe will consequently get less CPU time due to its low position in the CPU queue and thereby reduce its impact on overall session responsiveness. Other user processes that haven’t also reached 50% have a higher CPU priority and so continue to consume CPU time and although the overall percentage CPU usage continues to show above 90%, the session responsiveness for that user is greatly improved.

In this scenario, the machine has 4 logical processors. If the processes’ CPU usage is spread equally across all logical processors, each will show 12.5% usage for that process instance.

If there are two iexplore.exe process instances in a session, their respective percentage CPU usage values are not added to trigger Spikes Protection. Spikes Protection settings apply on each individual process instance.​

User-centric CPU Optimization (process tracking on the WEM Agent):

As stated previously, all WEM System Optimization settings are machine-based and settings configured for a particular ConfigSet will apply to all users launching sessions from the VDA.

The WEM Agent records the history of every process on the machine that has triggered Spikes Protection. It records the number of times that the process has triggered Spikes Protection, and it records the user for which the trigger occurred.

So if a process triggers the CPU Spikes Protection in User A’s session, the event is recorded for User A only. If User B starts the same process, then WEM Process Optimization behavior is determined only by process triggers in User B’s session. On each VDA the Spike Protection triggers for each user (by user SID) are stored in the local database on the VDA and refreshing the cache does not interfere with this stored history.

Limit CPU / Core Usage:

When a process has exceeded the CPU Usage Limit value (i.e. Spikes Protection for the process has been triggered), in addition to setting the CPU priority to Low, WEM can also limit the amount of CPU cores that the process uses if a CPU / Core Usage Limit value is set. The limit is in effect for the duration of the Idle Priority Time.

Enable Intelligent CPU Optimization:

When Enable Intelligent CPU Optimization is enabled, all processes that the user launches in their session will start at a CPU Priority of High. This makes sense as the user has purposefully launched the process, so we want the process to be reactive.

If a process triggers Spikes Protection, it will be relegated to Low priority for 180 seconds (if default setting is used). But, if it triggers Spikes Protection a certain number of times, the process will run at the next lowest CPU Priority the next time it’s launched.

So it was launching at High priority initially; once the process exceed a certain number of triggers, it will launch at Above Normal priority the next time. If the process continues to trigger Spikes Protection, it will launch at the next lowest priority until eventually it will launch at the lowest CPU priority.

The behavior of Enable Intelligent CPU Optimization is overridden if a static CPU Priority value has been set for a process. If Enable Intelligent CPU Optimization is enabled and a process’s CPU Priority value has been set to Below Normal, then the process will launch at Below Normal CPU priority instead of the default High priority.

If Enable Intelligent CPU Optimization is enabled and a process’s CPU Priority value has been statically set to High, then the process will launch at High. If the process triggers Spikes Protection, it will be relegated to Low priority for 180 seconds (if default setting is used), but then return to High priority afterwards.

Note: The Enable CPU Spikes Protection box must be ticked for Enable Intelligent CPU Optimization to work.

Memory Management

Working Set Optimization:

WEM determines how much RAM a running process is currently using and also determines the least amount of RAM the process requires, without losing stability. The difference between the two values is considered by WEM to be excess RAM. The process’s RAM usage is calculated over time, the duration of which is configured using the Idle Sample Time (min) WEM setting. The default value is 120 minutes.

Let’s look at a typical scenario when WEM Memory Management has been enabled:

A user opens Internet Explorer, navigates to YouTube, and plays some videos. Internet Explorer will use as much RAM as it needs. In the background, and over the sampling period, WEM determines the amount of RAM Internet Explorer has used and also determines the least amount of RAM required, without losing stability.

Then the user is finished with Internet Explorer and minimizes it to the Task Bar. When the process percentage CPU usage drops to the value set by the Idle State Limit (percentage) value (default is 1%), WEM then forces the process to release the excess RAM (as previously calculated). The RAM is released by writing it to the pagefile.

When the user restores Internet Explorer from the Task Bar, it will initially run in its optimized state but can still go on to consume additional RAM as needed.

When considering how this affects multiple processes over multiple user sessions, the result is that all of that RAM freed up is available for other processes and will increase user density by supporting a greater amount of users on the same server.

Idle State Limit (percent):

The value set here is the percentage of CPU usage under which a process is considered to be idle. The default is 1% CPU usage. Remember that when a process is considered to be idle, WEM forces it to shed its excess RAM. So be careful not to set this value too high; otherwise a process being actively used may be mistaken as an idle process, resulting in its memory being released. It is not advised to set this value higher than 5%.

I/O Management

These settings allow you to optimize the I/O priority of specific processes, so that processes which are contending for disk and network I/O access do not cause performance bottlenecks. For example, you can use I/O Management settings to throttle back a disk-bandwidth-hungry application.

The process priority you set here establishes the “base priority” for all of the threads in the process. The actual, or “current,” priority of a thread may be higher (but is never lower than the base). In general, Windows give access to threads of higher priority before threads of lower priority.

I/O Priority Settings:

Enable Process I/O Priority

When selected, this option enables manual setting of process I/O priority. Process I/O priorities you set take effect when the agent receives the new settings and the process is next restarted.

Add Process I/O Priority

Process Name: The process executable name without the extension. For example, for Windows Explorer (explorer.exe) type “explorer”.

I/O Priority: The “base” priority of all threads in the process. The higher the I/O priority of a process, the sooner its threads get I/O access. Choose from High, Normal, Low, Very Low.

Enable Intelligent I/O Optimization:

This adopts exactly the same principles as Enable Intelligent CPU Optimization, but for I/O instead of CPU.

Note: The Enable CPU Spikes Protection box must be ticked for Enable Intelligent I/O Optimization to work.

Exclude specified processes:

By default, WEM CPU Management excludes all of the most common Citrix and Windows core service processes. This is because they make the environment run and they need to make their own decisions about how much CPU time & priority they need. WEM administrators can however, add processes they want to exclude from Spikes Protection to the list. Typically, antivirus processes would be excluded. In this case, in order to stop antivirus scanning taking over disk I/O in the session, administrators would also set a static I/O Priority of Low for antivirus processes.


  1. When configuring, the entered process name is a match to the process name’s entry in Windows Task Manager.
  2. Process names are not case-sensitive.
  3. You don’t enter “.exe” after the process name. So for instance, enter “notepad” rather than “notepad.exe”.


How to Use RightSignature on Android

Click the hamburger icon in the upper left hand corner to be taken to the menu.

User-added image


The Documents tab displays all documents the user is a party to. Click on a specific document to display more details.

User-added image


All Templates in the account will be listed under this tab, with the most recently created one at the top.

User-added image

If there are Merge Fields, you will be prompted to enter merge data into the document before sending.


This tab lists your name and email address, the account you are logged into, and gives the option to Sign Out. The web app will need to be accessed in order to change any account information.

User-added image

Contact Support will send an email request to using the phone’s default email.


SEP 14.2.1031.0100 Blocks .NET ClickOnce

I need a solution

We recently upgraded our SEPM and rolled out SEP 14.2.1031.0100.  Since the update, users attempting to run an MS .Net ClickOnce App (DeltekVision.exe) are met with a blank Microsoft Edge window and the ClickOnce (dfsvc.exe in C:WindowsMicrosoft.NETFramework64v4.0.30319) process running hung in task manager with very high CPU consumption.  The workaround is to set Internet Explorer as the true default, although we would prefer to have Edge as the system default.  Any thoughts on how to exempt the ClickOnce process?  We already tried a central exemption of the executables listed above.  Clearly there is a difference in the release (new feature?) as this only affects clients with 14.2.1031.0100.  Thoughts, greatly appreciated.  Thanks.



Ghost Console Won’t Run Remote Batch File

I need a solution

We have been doing a two-Task process to deploy a piece of software to computers using Ghost Console

Task 1) Deploy an installer and batch file to a specified directory on the target machine(s).

Task 2) Run the batch file in the deployment directory on the target machine, which successfully installs the program.

I tried this with a new piece of software, and while Task 1 copies the installer and batch file into the directory successfully, Task 2 does nothing other than claim to have completed successfully. When I run the deployed batch file on the target machine it works properly, just not through the Ghost Console Task. I tried this on multiple machines with the same results.

When I run the batch file on the target machine I can see Windows Command Processor open in Task Manager, which does not happen when I run the Task through Ghost. I do see the Ghost System Tray Provider open while the warning window comes up, but then it closes and nothing else happens.

I took the successful Task 2 for the first piece of software and changed the target information to match the new program, and it still did nothing. Then I changed it back to the original target and it worked properly for that software.

Any ideas?



Xenapp-7.15-On server 2016 VDA we can see lots of disconnected session without a username

Solution 1:

You should be able to use qwinsta/rwinsta for this

qwinsta /server:myxenappserver

Find the session ID you want to kill, then

rwinsta /server:myxenappserver sessionid

Solution 2:

1.)Logon to the VDA, where the ghostuser is showing up and start taskmgr

2.)Go to users > expand user processes and right click “Windows logon application” and select “go to details”.

3.)You will go to the winlogon.exe proces in the detail tab for this user. Rightclick winlogon.exe and select “analyze wait chain”

4.)There you will see a svchost proces with a particular PID. Remember that PID

5.)Unfortunately, you can’t kill the svchost PID with taskmgr.

Use Process explorer (sysinternals) and run it as admin. Search for the corresponding svchost PID and kill the process.

6.)After that is done the ghostuserlogon will be killed without a reboot.


RSAT Server Manager blocked by 14.2

I need a solution

I just upgraded my SEPM installation from 14.0 to 14.2 and am testing it out on my client test group. One issue I am seeing is that the RSAT Server Manager tool will not launch with this version of SEP. The Server Manager process is there in task manager using a lot of cpu cycles and multiple instances can be spawned quickly using up all available cpu resources. The Server Manager GUI or even the splashscreen does not appear.

If I launch an elevated powershell window and run ServerManager from it, Server Manager launches with normal cpu usage.

This is the only way I am able to launch it, right clicking the shortcut and selecting run as admin does not work.

RSAT version is 1709 x64. Windows up to date with June cumulative update.




Privilege Elevation Challenges in Tasks

I need a solution

Is the below expected behavior?

GSS 3.2 RU3 Run Script tasks when run as specific user, that is also a local administrator of the target machine, does not load an elevated process.

It’s easy to duplicate by running a Run Script task, as a specific user, that is local administrator, maximized, and with a ‘Pause’ statement. If you look at that cmd.exe session in task manager, you will see that the elevated column shows ‘No’.

When tested against a DS 6.9 SP6 installation, the process was run in an elevated session.

So, I’m curious. Where is the bug? Within an old DS install or within the new GSS environment?




Cplex error 1001 Out of memory (on big problem)

Dear @DanielJunglas following a previous question of mine and as regards to the subject of CPU use at the Task Manager, the task of my program (blend.vcproject) barely reaches at the 2,5 GHz (97-99%) and at specific points (when the GAP lies at 0,1% and less).
Regarding the RAM memory the task also reaches at high levels (70-80% of 16GB total) but at specific points during the execution and not all the time. After a primary examination, i revealed that when the messages of CPLEX ERROR 1001: OUT OF MEMORY are appeared, the CPU and RAM indicators are not at their highest level.
Furthermore, as far as i know i haven’t configured any “per-process” limits on the memory; If you assess so please advise me the way of erasing that.
I would also like to mention that two different messages are appeared after the root node search initiates (after the 1st attempt to find upper and lower bound). The first is : “Insufficient memory for presolve” and “Compressing rows and columns files”. The abovementioned messages are revealed on different program executions (on the same scenario with a little bit different WorkMem values).
Finally, i would like to ask about the “probing” process. It seems that it is time consuming process.


CA integration RTM:Can you not select multiple case properties when creating a data field.

I have a question on CA integration with ICM

I’ve been using the knowledge center and the info in the following URL
as a guideline:

My question is:
After creating the audit configuration in the ICM Admin tool, you need
to expose the case properties on CA Process Task Manager (PTM).

How do you select multiple case properties when creating a data field
in CA Process Task Manager (PTM)? It seems like you need to create a
data field for each case property, which creates a table for that data
field in the CA DB Store.

Can I not select multiple case properties when creating a data field,
so that all those data field properties are stored together in the same

Kind Regards,