Current and Future Clients/Partners are Welcome.
With larger environments, it’s important to consider the implications of different architectures and system types when building a ProfileUnity Console cluster. Some of the key things to note are how many geographic locations will be home to machines running the ProfileUnity Client Tools and what type of environment is being delivered. For example, single-user Desktop OSes or multi-user Server OSes with the RDSH Server Role enabled.
ProfileUnity Cluster notes to keep in mind:
- ProfileUnity uses MongoDB for the database back end and RabbitMQ for the license fabric - both are clustered automatically when you build a ProfileUnity Console cluster.
- MongoDB requires a cluster containing an odd-number of nodes under a 100% node-up scenario. This ensures a tiebreaker for cluster operations. Generally, this means 3, 5 or 7 nodes.
- MongoDB, while clustered, always requires at least 2 running nodes, hence the minimum node-count of 3.
- If you have a single site you likely only need a 3-node cluster. This would spread the load out among all nodes and allow for a single node to fail while maintaining normal operations. An example benefit would be a rolling Windows Update/reboot cycle or even a ProfileUnity Console version upgrade without service interruption.
- If you have 3 geographic regions and want to make sure that you have license and FlexDisk redundancy at each location, you might deploy a 7-node cluster. Site 1 would have 3 nodes while sites 2 and 3 would each have 2 nodes. In this configuration, the MongoDB cluster would span all 3 sites while the RabbitMQ license/FlexDisk fabric would be isolated within each site. This would allow for a single node at each site to be rebooted for maintenance, while maintaining normal operations at all sites. It would also allow for 2 of 3 sites to go dark and not interrupt ProfileUnity license or FlexDisk operations at the remaining site.
ProfileUnity Cluster sizing considerations:
- Environments with a majority of Desktop OSes, or Server OSes without the RDSH role acting as single-user desktops, can require a cluster with higher CPU requirements and lower memory requirements. The main reason is that the Liquidware Client License Service in the Client Tools only connects to the fabric to make a license "consume" or "release" request and then immediately disconnects.
- Environments running a majority of Server OSes with the RDSH role enabled will require both CPU and additional memory as the number of client machines increases. In this situation, because the server will be making many license "consume" and "release" requests throughout the day, the Liquidware Client License Service connects to make the first license "consume" request and remains connected until rebooted. These open connections require the ProfileUnity Console cluster to have a higher memory requirement.
For cluster sizing suggestions, please refer to this KB article: https://liquidwarelabs.zendesk.com/hc/en-us/articles/360039686092-ProfileUnity-Cluster-Sizing-Suggestions
Dashboard - SpotCheck - Physical Desktops
This Can be imported into your 6.1.4+ Stratusphere System.
Note: After Import you will need to press F5 to refresh the dashboard list.
Setup /download configuration-Office365-xXX.xml
Once downloaded start FPC Capture
Setup /configure configuration-Office365-x64.xml
Once complete Save FPC Capture, Save Icon
Playback and add script to post activate
Bat script details.
"C:\Program Files (x86)\Microsoft Office\root\Integration\integrator.exe" /R /License PRIDName=O365ProPlusRetail.16 PackageGUID="9AC08E99-230B-47e8-9721-4577B7F124EA" PackageRoot="C:\Program Files (x86)\Microsoft Office\root"
"C:\Program Files\Microsoft Office\root\Integration\integrator.exe" /R /Msi MsiName="SPPRedist.msi,SPPRedist64.msi" PackageGUID="9AC08E99-230B-47e8-9721-4577B7F124EA" PackageRoot="C:\Program Files\Microsoft Office\root"
Makes adjustments for your environment
<!-- Office 365 client configuration file sample. To be used for Office 365 ProPlus apps,
Office 365 Business apps, Project Pro for Office 365 and Visio Pro for Office 365.
For detailed information regarding configuration options visit: http://aka.ms/ODT.
To use the configuration file be sure to remove the comments
The following sample allows you to download and install the 64 bit version of the Office 365 ProPlus apps
and Visio Pro for Office 365 directly from the Office CDN using the Monthly Channel
<Language ID="en-us" />
<ExcludeApp ID="OneDrive" />
<ExcludeApp ID="Lync" />
<ExcludeApp ID="Groove" />
<ExcludeApp ID="Teams" />
<ExcludeApp ID="Lync" />
<ExcludeApp ID="Publisher" />
<Updates Enabled="False" />
<Display Level="Full" AcceptEULA="TRUE" />
<Property Name="AUTOACTIVATE" Value="1" />
<Property Name="FORCEAPPSHUTDOWN" Value="FALSE"/>
<Property Name="SharedComputerLicensing" Value="1"/>
<Property Name="SCLCacheOverride" Value="1" />
<Property Name="SCLCacheOverrideDirectory" Value="%appdata%\Microsoft" />
<Property Name="PinIconsToTaskbar" Value="TRUE"/>
perparim test edit
Working with our clients in Physical, Virtual/VDI and Cloud environments we see many of the same issues. This video shows the top 5 issues that we have found and helped clients resolve.
Connect Power BI Workstation to Statusphere
In this blog we detail the steps to connect Power BI Workstation to Stratusphere.
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!