Current and Future Clients/Partners are Welcome.
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.
Need the ability to give users direct links to dashboards in Stratusphere. Some links need no login and others need to request a login.
The Stratusphere UX Process 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 Process Optimization 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