Deyda Consulting Blog
Update of the article to the Workspace Environment Management Version 1906.
In the fourth (and last) part of the series about the WEM Administration Console, I give you an insight into the menu items Administration & Monitoring.
These settings control administrative functions such as delegation, user statistics, and change logging.
The new Current Release of WEM is out now. It does not include many new features, but a lot of bug fixes.
A Profile Management health status column is provided on the Administration > Agents > Statistics tab. As of this release, Workspace Environment Management supports performing automated status checks on your agent hosts to determine whether Profile Management is configured optimally. You can view the status in the column.
Continue reading “Workspace Environment Management Version 1811 is out now”Update of the article to the Workspace Environment Management Version 1906.
In the third part of the series about the WEM Administration Console, I give you an insight into the menu items Active Directory Objects, Transformer Settings and Advanced Settings.
You use this Menu Item to specify the users, computers, groups and organizational units managed by Workspace Environment Management.
In earlier releases, you used Studio to create a restart schedule for machines in a Delivery Group. To create multiple schedules, you used PowerShell cmdlets. Now, the updated Studio interface enables you to create and manage one or more restart schedules.
A schedule can affect either:
Update of the article to the Workspace Environment Management Version 1906.
Now I continue with the second part of the series about the WEM Administration Console. I give an insight into the menu items System Optimization, Policies & Profiles and Security.
These settings are designed to lower resource usage on the agent host machine. They help to ensure that freed-up resources are available for other applications, increasing user density by supporting more users on the same server hardware. The System Optimization settings are machine-based.
When your virtual machines have different hardware configurations, consider creating multiple configuration sets for them, and configuring the system optimization settings differently for each configuration set. Machines can only belong to one configuration set.
