How to install Lotus SameTime 8.5.1 on Citrix PVS Streamed pooled desktop (VDI)

IBM Lotus Sametime is the enterprise communicator similar to OCS. It has similar feature as Microsoft OCA along with , it has ability to take screenshot and share over chat . Some of the cool feature liked by end users to  have his/her  own emotions on chat.

While installation is easy but it does not launch in PVS streamed VM's . PVS streamed VM  uses roaming profile because of pooled environment . This can only be achieved via storing user's profile data on shared storage.

IBM Sametime does not like it because it has tendency to store it locally . Below screenshot shows that  value called rcp.data store it locally. This setting does not allow the sametime to launch when desktop is access via ICA session.

To make it work , mount the roaming app data GPO by updating registry

And now make change to the file rcplauncher.properties by updating the field called rcp.data as shown below .

With this you would be able to launch IBM same time on streamed pooled VM.

How to Publish Google Chrome 13.0 with XenApp 6

To publish Google Chrome , we need to download standalone msi package from google

12/29/2008-13:42:29 http://dl.google.com/update2/1.2.131.27/GoogleUpdateSetup.exe
12/29/2008-13:42:29 http://dl.google.com/update2/1.2.131.27/clickonce_bootstrap.exe
12/29/2008-13:42:35 http://cache.pack.google.com/chrome/install/154.36/chrome_installer.exe

Or from following url https://www.google.com/chrome/eula.html?standalone=1

Install the standalone package and this will get installed under the user profile whoever is logged in. In this example Administrator is logged in hence the shown path . We need to copy Chrome.exe under 13.0.782.112 folder as shown below. Administrator folder should be given Modify permission for all the users.

Now create googleChorme.cmd file under program folder with shown entry.

Publish this CMD as usual using Citrix Delivery Console.

You can launch and safely ignore the message   and use google chorm

How to install Desktop Director and configure for MultiSite in XenDesktop 5.0

When you have multiple site running XD 5.0 Farm and Help Desk want to use single desktop director to manage both farm . We need to update desktop director with other farm controller name

To install standalone desktop director you can run DDC 5.0 ISO and choose following . Update DDC FQDN in the given format and hit test

This will finish Desktop Director  installation

Once installation done we need to open IIS management . Drill down to DesktopDirector and highlight Application setting.

This will bring all the setting related to Desktop Director . There are two setting which we need to modify in order to manage multiple site.

We need to change from 'false' to 'true'

Update here with all the controller FQDN to manage all the site.

Restart the IIS here and then browse to the page . This webpage will be different and here you wont get dashboard. Only thing can be done here is search users and then address the issue pertaining to the user. So it would be very important to decide if you like to make these changes and use it . This is with Desktop Director 1.0 . There are few changes which has been made to Desktop Director 2.0 which will allow you to manage XD 5.5 and XA 6.5 farm as well . Source is here

How to remove XenDesktop DDC5 gracefully from the XD5 farm

In my previous blog I mention hard way to remove stale DDC from XD database.

Launch the Desktop Studio and highlight controllers as shown below. Select the controller you want to remove and choose "Remove Controller"

This will prompt for action to update Database . Choose "NO " here

This will prompt for generating SQL script which needs to be run on SQL server database

Script looks like this . Copy this script

And then choose DDC database on SQL manager . Right click and select new script . Paste  it from previous step and run "Execute"

Once the script is ran then it will give following message

Once Desktop Studio is update , controller will be removed

Run powershell command Get-BrokerController and confirm that other controller is out completely.

How to remove stale DDC from XenDesktop 5 Farm

Stale DDC inside XenDesk 5 Farm may get created because of various reason and this does not get removed unless database is cleaned.

1. If you run Get-brokercontroller from PS console of Desktop Studio then you see the stale entry. Below two stale entry for SID

S-1-5-21-1757981266-413027322-725345543-64627 and  other one ending with 64712 

2. Same thing will be shown via Desktop Studio

 

3. Following script needs to be run in same order from desktop studio PS console with XD database name

Get-ConfigDBSchema -DatabaseName <XD database name> -ScriptType Evict -SID $sid > EvictDDC.sql  (Here we are creating EvictDDC.sql)
Get-AcctDBSchema -DatabaseName <XD database name> -ScriptType Evict -SID $sid >> EvictDDC.sql(Here we are appending to  EvictDDC.sql)
Get-HypDBSchema -DatabaseName <XD database name> -ScriptType Evict -SID $sid >> EvictDDC.sql
Get-ProvDBSchema -DatabaseName <XD database name> -ScriptType Evict -SID $sid >> EvictDDC.sql
Get-PvsVmDBSchema -DatabaseName <XD database name> -ScriptType Evict -SID $sid >> EvictDDC.sql
Get-BrokerDBSchema -DatabaseName <XD database name> -ScriptType Evict -SID $sid >> EvictDDC.sql

4. This is how Script needs to be run in following order . First SID variable needs to be set and then rest of the commands need to be run. Here we are creating EvictDDC.sql file which is nothing but a stored procedure

5.  This file can be found under following

6. Now when we open this file with notepad  following entry can be found.

 

7.   Open SQL server management studio and select the database and then open new script. Select the content from EvictDDC.sql  and paste as shown. Execute as shown below

8.   Last command Get-BrokerDBSchema -DatabaseName <XD database name> -ScriptType Evict -SID $sid >> EvictDDC.sql  need to run as follows.

9.  Sometime Get-BrokerDBSchema -DatabaseName <XD database name> -ScriptType Evict -SID $sid >> EvictDDC.sql will fail with following message. Create new store procedure using working XD SID and then replace host name and SID with non working SID.

10.  Once all the above store procedure ran it will remove the stale entry from DDC

Even Desktop Studio will update the entry