Do you have 3 different profiles created for the 3 instances? Also, are they all installed in the same folder?
Hi Gupta nice to see you over here,
I have three different versions of the Bladelogic Console installed on the same computer (my personal computer) under different installation paths... but the bl_sesscc file is always the same (under user's roaming folder) and is used for all them if they are run at the same time (at less two instances, it doesn't matter if they are the same version or not), the problem it's because they use that file same to populate SSO credentials and if they are more than one connected to different environments with different SSO information, the SSO information present at anytime is that belonging to console and environment which was connected in last place)
You can see what i mean in the screenshot embedded.
I almost forgot to mention this was detected some time ago in our XenApp servers where all the different instance of the consoles are installed, but there we solved this problem through the use of isolated environment for any user session created on them.
I use to connect to 3 different environment and use the same version of console (8.2) but I never faced this issue.
Is the version of BSA also different? There should be 3 different profiles by different names on console.
what you might be able to do is:
- write a bat wrapper to start the gui, in the batch file set the environment variable BL_SSO_CRED_CACHE_FILE and the path to some other cache file like %APPDATA%\BladeLogic\bl_sesscc_1
do that for each of the guis but w/ different files. you'd also want a wrapper for blcred and nsh to do the same thing.
Yes, right. The environment variable BL_SSO_CRED_CACHE_FILE may be set to override the default location. Although we never did that as we never faced such issue.
Yes they are, every Bladelogic console is to connect to different Bladelogic's versions.
have you ever found a way around this.
Now that we are using different versions for our DEV and PROD environment, this issue now hits us again.
I tried to add the following to BSAClient.cfg
Which was not really successfull.
The console would still put the cahce file in the default location, but an "NSH Here" would try to read the file specified in the environment variable, which will then fail.