Tip of the week: Sametime and multiple connect.ini's
Category Sametime Technote
I was chatting to Thomas G. yesterday and we were discussing a shared a friend in England that works for IBM. He was explaining how he doesn't get to chat to her on Sametime internally because of the wya there is an IBM and Lotus Sametime Community, and one can't see the other. So there are a few options to solve this problem in the form of different clients, Trillian with the Sametime plugin, but not all the Sametime functionality; Gaim; The memory hungry IBM Community Client etc. etc. Anyway, it came about in this conversation that Thomas didn't know anything about the /Multi option to launch the Sametime connect client multiple times. That is still a pain as you have to change the server you are connecting to everytime you connect. So this combination of discussions got Thomas to thinking, surely there is a way he can just copy the Connect client directory and have different INIs. Well I told him to try this and to let me know how much time he wasted finding out it didn't work, which he kindly did, but then being Thomas he came up with a workaround, and here's what you need to do to have connect clients that can use different connect.ini. So here via Thomas is how you can do it:
Create more duplicate directories to laod more ST Connects with different settings.
I was chatting to Thomas G. yesterday and we were discussing a shared a friend in England that works for IBM. He was explaining how he doesn't get to chat to her on Sametime internally because of the wya there is an IBM and Lotus Sametime Community, and one can't see the other. So there are a few options to solve this problem in the form of different clients, Trillian with the Sametime plugin, but not all the Sametime functionality; Gaim; The memory hungry IBM Community Client etc. etc. Anyway, it came about in this conversation that Thomas didn't know anything about the /Multi option to launch the Sametime connect client multiple times. That is still a pain as you have to change the server you are connecting to everytime you connect. So this combination of discussions got Thomas to thinking, surely there is a way he can just copy the Connect client directory and have different INIs. Well I told him to try this and to let me know how much time he wasted finding out it didn't work, which he kindly did, but then being Thomas he came up with a workaround, and here's what you need to do to have connect clients that can use different connect.ini. So here via Thomas is how you can do it:
- In the program directory for Sametime Connect you will see a connect.exe, using the right mouse button in the folder create a new text file. Change the properties/name of that file to connect.exe.local - This is a funky thing only available to Windows 2000 and later, that makes Windows run a program whilst ignoring any previous instances of it.
- Now copy that entire sametime connect sub directory, with exes etc, to a new one example: Sametime Client2
- Create a shortcut, pointing to the connect.exe in the new folder (be sure to still use the /Multi switch)
Create more duplicate directories to laod more ST Connects with different settings.
| Permalink | 
Comments
Posted by Huptus At 10:02:57 AM On 12/06/2004 | - Website - |
Posted by Adi Guptha At 05:15:47 AM On 12/12/2005 | - Website - |
Posted by adriana At 11:52:46 PM On 02/15/2006 | - Website - |
The problem started after upgrading to Windows XP. I was able to connect to two servers simultaneously when I was using Windows 2000.
Posted by Vinamra Chandra At 05:40:31 PM On 05/03/2006 | - Website - |