This is going to be a 2 part post on how to configure and save ShoreTel Communicator settings in XenDesktop and Appsense.
The first part will be concern how to actually save the user settings while the second part will be on how to automate the configuration of the ShoreTel Communicator settings for a new user.
You can skip the first part if you already know how to manage the Shoretel Communicator settings and just want to know how to automate the setup process. Click Here
So lets get to it.
When it comes to managing applications with Appsense, usually it is more efficient to to use User Personalization as it does not require any package updating on the client. However, I found it to be problematic with managing ShoreTel Communicator settings. The best solution I found was to manage the settings under Policy Configuration.
The settings to manage ShoreTel Communicator are fairly simple. The registry key you need maintain is
[“HKEY_CURRENT_USER\Software\Shoreline Teleworks”].
To manage this, open up Environment Manager on your Appsense server and open your configuration.
Create a new Node under “Logon” in Policy Configuration and give it a name. I used “Shoretel In”
Create another node under Logoff and give it a name. I used “Shoretel Out”.
Click on either node so it’s highlighted and right click in the actions window. Choose Action –> Registry –> Registry Hiving
Give it a title such as ShoreTel Hiving. Under location, choose a directory inside of the users profile. This is where the registry settings will be saved and pulled from.
Click Add below Hive Items and enter
HKEY_CURRENT_USER\Software\Shoreline Teleworks
Leave Value Name blank and ensure Replace is chosen under Restore Format and Use registry key as file name is checked. Click Ok
Now, choose “Import the hive from file to the registry” is chosen if are creating this under the logon node you created earlier or choose “Export the hive from the registry to file” if you are under the Logoff node. Click Ok
Copy the Action you just created and paste it in the other node. Now, all you have to do is double click on the Action and change the Import/Export option to the opposite and your login/logoff actions are set up.
*Important Note* This is just a little reminder for something to look out for when creating these actions and the location you are exporting and more importantly, importing from. If you setup and use any environment variables, and use them in the location path for importing the registry hive, there is a little extra step to take to ensure that these settings are applied consistently.
Here’s what happens. When a user logs in, the all the nodes are processed in the order they are listed. This means, if you put the ShoreTel node above all other nodes, and you reference a environment variable that is created in a node after your ShoreTel import, then desktop will have no idea where to import that registry setting from!
The solution I use for this is to put the ShoreTel import node nested under the lowest node in the Logon list. To do this, Highlight the ShoreTel node you created, Hold CTRL and push the down arrow until it is at the bottom of the list. Then, just hit the right arrow while still holding CTRl until the Node is nested. This means that the ShoreTel node will be the last action to process and ensure the settings are imported.
And there you have it for part 1. Once you configure ShoreTel Communicator, it will save the settings at log off.
Click here for Part 2 on how to automate the setup process for ShoreTel Communicator.
Image may be NSFW.
Clik here to view.
Image may be NSFW.Clik here to view.
