If you use WSO you’ll know it’s a strange creature depending on how you have your environment configured.
Administrator won’t maximise!
Occasionally WSO Admin might refuse to maximise on a desktop and sit in the task bar waiting to be killed off. This is often caused by the users profile data in SQL becoming smelly. To cleanse this, run the following script in SQL Management Studio against your WSO FCSCommon database:
Wipe my profile in Wall Street Office
A more comprehensive script for cleansing a user profile involves running the following. Note – log the user out of WSO before running this.
The following post runs through how to install and package Bloomberg Professional for a VDI environment. The below example uses Liquidware’s FlexApp to do this, but the ideas below are applicable to AppVolumes with VMware DEM to manage the post-deployment script.
Version: This is intended for users of Bloomberg Anywhere and covers how to package and deploy Bloomberg Professional (Full Terminal).
Bloomberg Professional contains Office Tools (MS Office Add-In) and a full standalone desktop client.
2. Run the installer on your provisioning VM selecting Private IP Network as the environment type.
3. Launch the software and click past the connection wizard until you reach the login screen – you don’t want your users to see/do this!
4. Bloomberg has minimum requirements of Read/Write to the following HKLM registry key and subkeys. If you have UAC enabled, you need to set permissions against these keys to allow users R/W access to:
These permissions can’t be captured using AppVolumes or FlexApp because they’re machine-level settings, so we need to use a post-deployment script to add the permissions to the registry after the app has mounted to the desktop at logon time.
There’s a few methods for doing this and at the time we
Configure a post-deployment script using subinacl
The following script should be saved as a .bat file.
1. Ensure subinacl and the .bat script sit in the same folder, ideally your netlogon share. If storing elsewhere, ensure the logged on user has rights to read/execute from that location.
2. Typically Bloomberg allows you to perform an APOD creation – this installs a generic license key which then lets a Bloomberg Anywhere user log in. If you need to configure this follow these steps: once you’ve installed the app on your capture VM, type CONN in the Bloomberg window to see the connection wizard. Under the Connections tab, click Submit. This will create a generic key code and allow the user to login using their Anywhere login creds