Current and Future Clients/Partners are Welcome.
The Stratusphere UX Optimization feature automatically optimizes CPU/Memory and keeps “Bad Actor Applications/Processes” from hurting the performance of the users on priority applications brought to the forground.
Since release of the Process Optimization feature many clients have reported extending life cycles for physical machine by 6-18 months with greater User Experience. This has resulted in a huge capital savings for many clients.
Think about it: Why should windows updates or any process running in the background slow my applications running in the foreground down?
Process Optimization is a very simple, automated and almost zero impact feature that is included with Stratusphere UX. You can turn it on for single machines, groups or globally from the administration pages in Stratusphere UX. There are 4 Profiles that you can select depending on the type of machine(s) that you are targeting. Other options include: (Path\Executable to be exclude), (Processes to be Raised\Lowered), (Processes to be Terminated).
Optimizer can be use in Physical, Virtual and Cloud environments. It is recommended by Liquidware SEs that all attempts be used to “Fix” the issue using the data provided in Stratusphere UX before turning on Optimizer. The reason is that Optimizer does not fix bad actors. It only lowers their impact on the “In Focus” application.
Note: Optimizer was designed with security and reliability in mind from day one. Our “Do No Harm” philosophy is at the heart of the Process Optimization feature. If the machine is not under stress Optimizer does nothing! If optimizer ask a process to lower its CPU priority and it says no, optimizer will not force the change and it will not ask again. For example, you should never change the CPU priority of a security/virus application.
How to Enable Optimizer in Stratusphere UX:
The goal was to increase RAM for specific users within a pool due to work role or requirements. I created a powershell script that uses PowerCLI Set-VM cmdlet to change the VM RAM. By placing a user in a specific AD Group we were able to leverage ProfileUnity Elevated Privileges and Application Launcher settings to initiate the command that was compiled into an EXE. The steps below document the process in more detail.
1) On the Template image, change the hardware settings to Enable 'Memory Hot Plug'
2) Power up the template and Install VMware.PowerCLI component on Template image
Install-Module VMware.PowerCLI -Scope:AllUsers -Force -AllowClobber
3) Shutdown template, snapshot and recompose Non-Persistent pool
4) In vSphere create an account with appropriate permissions to modify a Virtual Machine to be used in Powershell/PowerCLI script.
5) Create a PowerShell script (I used Sapien Tools because I will later compile it into an EXE) (Note: might not be the most efficient or robust code feel free to expand error checking)
#Get Argument from Commandline default to 4GB if nothing passe
$envVM =Get-ChileItem env:computername
#Setup PowerCLI Environment
Set-PowerCLIConfiguration -InvalidCertificateAction Ignore -ParticipateInCeip $false -Confirm $false
#Connect to VirtualCenter
Connect-viserver -server <vcenter name> -Username '<account with perms to modify>' -Password 'password' -ErrorAction Stop
#Check to determine VM Available before attempting to change RAM setting
Get-VM $VM -ErrorAction Stop
$Set the VM's memory in GB, also update Notes field in vSphere to reflect the change was done dynamically
Set-VM -vm $VM -memoryGB $sizeInGB -notes "Dynamic increase to $sizeInGB GB" -Confirm:$false
6) Compile the script into an EXE (sure there are other ways to do it, but don’t want the password to be clear text).
7) In ProfileUnity create a Filter Management to target the Dynamic RAM increase. In my case I created 3 different groups (6GB, 8GB, 12GB)
8) In ProfileUnity Configuration Management click on Privilege Elevation and create a new privilege elevation rule for each Group (or you could nest the groups into another Filter Management group within ProfileUnity if you like that method better).
9) In ProfileUnity go to Application Launchers and create a new application launcher rule. In this example I am sending the argument of 6 to the script which will increase it to 6GB of memory. Likewise I have 8GB and 12GB application launcher rules.
10) Update the Configuration file and deploy to your share.
11) After login you should see it update in vSphere (Memory and Notes).
This would be a welcome addition to the logon process, or better yet, integration with the default Windows logon process typically used by gpsvc to better integrate/modernise the look and feel.
Connect Power BI Workstation to Statusphere
In this blog we detail the steps to connect Power BI Workstation to Stratusphere.
The staff at Liquidware just released this new video of FlexApp in a Microsoft WVD environment. Pretty slick. Apps at Boot time, Login, and Click-to-Layer. A webex plug-in for Outlook is also attached. Here the link. https://www.liquidware.com/videos/flexapp/microsoft-wvd-and-liquidware-flexapp-streamlined-base-image-management-layering
On virtual machines, even though there is no vGPU in the host, VMware tools still have a driver that looks like a GPU to the OS and the applications. Making a few simple tweaks to the registry, group policy, or ProfileUnity to turn off hardware acceleration to core applications on non vGPU virtual machines can result in a CPU reduction on your host operating system.
More information can be found here: https://community.liquidware.com/discussion/39/stratusphere-spotcheck-methodology-cheat-sheet
The attached PDF will guide you through disabling hardware acceleration either through GPO, Registry, or ProU for the following applications:
- Google Chrome
- Mozilla Firefox
- Microsoft Office
- Internet Explorer
The attached TXT file is a registry module import for ProU. Please remove the .txt to make it a .json for import.
When you're looking for the Domain Controller and IP for a specific user login trace, after you have clicked into a specific login time, its easy to navigate to Details|Group Policy Domain which reveals the Login DC name and IP address. This is a short group policy, but I was looking for the Domain Controller name and IP and went this route.
Stratusphere has a lot of data. The SpotCheck documents and methodology are designed to help clients focus on key metrics. SpotCheck is not an exhaustive “Health Check” of the systems but can identify high impact issues that can affect the users. Think of the SpotCheck documents as a cheat sheet of industry standard metrics and their accepted max values.
SpotCheck Docs for Virtual, Physical and Cloud Environments are Attached.
Liquidware Video Presentation:
Docs Last Updated: 08/29/2019
The best FlexApp packages come from a clean FlexApp console. To start, you read the guide found here:
Next, you should install your runtimes, which can be found here:
Finally, you should use the following process to optimize your image, assuming you are using version 1607-1903 of Windows 10:
First, download the attached .TXT file and rename it to an .XML
1. Run the attached template in the same directory as the VMWare Optimizer.
2. Run the VMWare Optimizer, select the FPC_Windows 10_Version 7 template, select Analyze and then Optimize.
3. Disable the user account that you're currently logged into.
4. Enable the SID-500 master Administrator account and set a password.
5. Reboot. There will be an error at login where it tries to login with the cached account that you first used to build the OS. This is normal.
6. Login with the Administrator account.
7. Snapshot and save the image. You can now clone it for use as an FlexApp Packaging Console. Enjoy!