Well, it's done. I migrated my Sametime infrastructure this morning to support LDAP. A lot of people had warned me it wasn't pretty. They were right. I got a nice early start in hopes that I would get done quick. That didn't happen. It took over three hours to get the first server updated. The problem I ran into which I hadn't seen before was that my Domino program folder and data folder are on too different drives. So when you run the stnamechange.cmd file, it's assuming the data folder lives where the program folder is. Since it didn't I opened a Sev1 call. We looked in the trace folder and found the error that led to this link
Sametime Name Conversion fails if data directory is not under program directory
Running the command stnamechange.cmd <prog dir> <data dir> immediately converted it and I was good to go!
Another heads up that someone pointed out the other day was to apply a policy to everyone's Sametime that would force the client to download and overwrite the local buddy list. Well, some people didn't get the policy the other day and they reported duplicates today. I'm sure I'll have to deal with that tomorrow.
I've updated the SnTT-Sametime Woes (Domino Directory to LDAP) - Now Happy! post with the few gotchas that showed up. At least now we are set up right.
Showing posts with label Sametime. Show all posts
Showing posts with label Sametime. Show all posts
Sunday, December 16, 2012
Wednesday, November 28, 2012
SnTT-Sametime Woes (Domino Directory to LDAP) - Now Happy!
In my previous post, I was pretty upset with the instructions I found online about migrating my IBM Sametime Entry 8.5.1 installs to LDAP from the Domino Directory configuration they were set up with. So, I decided to document my steps in case someone else along the way comes across the same issue. YOUR MILEAGE MAY VARY depending on how your environment is set up, so take this with a grain of salt. Again, I'm using Sametime Entry 8.5.1. Let's begin. Also, I've decided to make it a SnTT post!
**BEFORE YOU BEGIN**
You will need to create a directory assistance database for this to work! Again, this is something that will be different for each company. I'm using a Domino server for LDAP. My consultant set that up for me and by the looks of it, he followed the steps that are listed in the book IBM Sametime 8.5.2 Administration Guide, available on Amazon. As those steps are listed in a book written by people I admire greatly, I will not highlight those steps here. But if you get the book, the steps are there. Also need to make sure that you server document is set up with the da.nsf file.
But assuming that you have that complete, here are all the steps!
1. On your workstation, create a text file called domtoldap.csv using a text editor.
2. In the file, type the word LDAP
3. Save and close the file.
4. In the Domino Console, issue the command Tell staddin q
5. You will need to create an LDAP document in the STConfig.nsf database
6. Open STConfig.nsf on Sametime server via your Notes client.
7. Click Create-Other-LDAPServer and then OK
8. In the new document, in Network address of LDAP Connection, type the FQDN of your LDAP server. I'm using my Domino application server for this process.
9. In the field for “Login Name for LDAP Connection”, type in CN=The Name used for authentication to your ldap server.
10. In the field for “Password for LDAP Connection” type in the password for the account used for authentication.
11. Press esc and save and close the document.
12. Make sure all ST processes are not running in the services section of the server before going any further.
13. Locate the following files in \Lotus\Domino folder
STAuthenticationLdap.dll
STGroupsLdap.dll
STResolveLdap.dll
StBrowseLdap.dll
14. Make abackup copy to another folder of those files.
15. Rename each of those files removing the LDAP so they should read
STAuthentication.dll
STGroups.dll
STResolve.dll
StBrowse.dll
16. If you get a file already exists/overwrite message, make a backup of the original file first, then do the rename.
***DO NOT SIMPLY RENAME THE FILES. COPY THEM OUT, RENAME THEM AND COPY THEM BACK. NOT SURE WHAT DID/DIDN'T WORK, BUT I RENAMED THE FILES. WHEN I RESTARTED THE SERVER, SAMETIME WOULDN'T START UNTIL I BUT THE ORIGINAL FILE WITH THE LDAP NAME IN THEM BACK. DON'T KNOW WHY. AGAIN, ANOTHER UNDOCUMENTED FEATURE!***
17. Open the sametime.ini file.
18. Locate the line DirectoryType=NOTES.
19. Change that line to read DirectoryType=LDAP
20. Save and close the sametime.ini
21. From a web browser, open the following site http://(yourservername)/stcenter.nsf
22. Click on the Administer the server link
23. Click on Domino Directory->Name change Tasks
24. Click New
25. In the description field, type ToLDAP
26. Click Browse
27. Locate the domtoldap.csv file and select it.
28. Click OK
29. Go back to your Domino server and open a command prompt
30. Go to your Lotus\Domino install directory.
31. Type in stnamechange.cmd and press enter.
***IF YOU ARE ON A WINDOWS SERVER WHERE THE DATA DIRECTORY IS NOT ON THE SAME PHYSICAL DRIVE AS THE PROGRAM FILES, RUNNING THIS .CMD WILL NOT WORK. YOU NEED TO ISSUE THE COMMAND
stnamechange.cmd <program dir> <data dir>
IF YOU DO NOT, THE UPGRADE .CMD DOES NOT KNOW WHERE TO LOOK FOR THE STNAMECHANGE.NSF AND YOUR UPGRADE WILL FAIL.***
32. Once the command finishes running, type exit to close the command prompt.
33. Type q in the Domino console and quit Domino.
34. once Domino and all related tasks have stopped, reboot the OS. Not doing this had led to errors with STUser.exe not working correctly and causing Sametime not to launch.
35. Once the OS has restarted and if you don't have Domino set to launch automatically, start Domino.
36. Once Sametime starts up, you should see a graphic like this appear on your Notes client. That means you've done it right.
37. Do happy dance.
38. If you don't get that message, start over with great sadness.
So there. A long, drawn out wiki reduced to 38 steps. Again, YOUR MILEAGE MAY VARY and if it doesn't work, I'm not sure what to tell you. But in my environment where I had installed several Sametime Entry 8.5.1 instances and I couldn't get things to convert, these steps fixed it for me!
**Special thanks to Gab Davis for leaving a comment on something that I had tried before, but missed in some testing. Once she reminded me of that, all the pieces fell together. She rocks!**
**BEFORE YOU BEGIN**
You will need to create a directory assistance database for this to work! Again, this is something that will be different for each company. I'm using a Domino server for LDAP. My consultant set that up for me and by the looks of it, he followed the steps that are listed in the book IBM Sametime 8.5.2 Administration Guide, available on Amazon. As those steps are listed in a book written by people I admire greatly, I will not highlight those steps here. But if you get the book, the steps are there. Also need to make sure that you server document is set up with the da.nsf file.
But assuming that you have that complete, here are all the steps!
1. On your workstation, create a text file called domtoldap.csv using a text editor.
2. In the file, type the word LDAP
3. Save and close the file.
4. In the Domino Console, issue the command Tell staddin q
5. You will need to create an LDAP document in the STConfig.nsf database
6. Open STConfig.nsf on Sametime server via your Notes client.
7. Click Create-Other-LDAPServer and then OK
8. In the new document, in Network address of LDAP Connection, type the FQDN of your LDAP server. I'm using my Domino application server for this process.
9. In the field for “Login Name for LDAP Connection”, type in CN=The Name used for authentication to your ldap server.
10. In the field for “Password for LDAP Connection” type in the password for the account used for authentication.
11. Press esc and save and close the document.
12. Make sure all ST processes are not running in the services section of the server before going any further.
13. Locate the following files in \Lotus\Domino folder
STAuthenticationLdap.dll
STGroupsLdap.dll
STResolveLdap.dll
StBrowseLdap.dll
14. Make a
15. Rename each of those files removing the LDAP so they should read
STAuthentication.dll
STGroups.dll
STResolve.dll
StBrowse.dll
16. If you get a file already exists/overwrite message, make a backup of the original file first, then do the rename.
***DO NOT SIMPLY RENAME THE FILES. COPY THEM OUT, RENAME THEM AND COPY THEM BACK. NOT SURE WHAT DID/DIDN'T WORK, BUT I RENAMED THE FILES. WHEN I RESTARTED THE SERVER, SAMETIME WOULDN'T START UNTIL I BUT THE ORIGINAL FILE WITH THE LDAP NAME IN THEM BACK. DON'T KNOW WHY. AGAIN, ANOTHER UNDOCUMENTED FEATURE!***
17. Open the sametime.ini file.
18. Locate the line DirectoryType=NOTES.
19. Change that line to read DirectoryType=LDAP
20. Save and close the sametime.ini
21. From a web browser, open the following site http://(yourservername)/stcenter.nsf
22. Click on the Administer the server link
23. Click on Domino Directory->Name change Tasks
24. Click New
25. In the description field, type ToLDAP
26. Click Browse
27. Locate the domtoldap.csv file and select it.
28. Click OK
29. Go back to your Domino server and open a command prompt
30. Go to your Lotus\Domino install directory.
31. Type in stnamechange.cmd and press enter.
***IF YOU ARE ON A WINDOWS SERVER WHERE THE DATA DIRECTORY IS NOT ON THE SAME PHYSICAL DRIVE AS THE PROGRAM FILES, RUNNING THIS .CMD WILL NOT WORK. YOU NEED TO ISSUE THE COMMAND
stnamechange.cmd <program dir> <data dir>
IF YOU DO NOT, THE UPGRADE .CMD DOES NOT KNOW WHERE TO LOOK FOR THE STNAMECHANGE.NSF AND YOUR UPGRADE WILL FAIL.***
32. Once the command finishes running, type exit to close the command prompt.
33. Type q in the Domino console and quit Domino.
34. once Domino and all related tasks have stopped, reboot the OS. Not doing this had led to errors with STUser.exe not working correctly and causing Sametime not to launch.
35. Once the OS has restarted and if you don't have Domino set to launch automatically, start Domino.
36. Once Sametime starts up, you should see a graphic like this appear on your Notes client. That means you've done it right.
37. Do happy dance.
38. If you don't get that message, start over with great sadness.
So there. A long, drawn out wiki reduced to 38 steps. Again, YOUR MILEAGE MAY VARY and if it doesn't work, I'm not sure what to tell you. But in my environment where I had installed several Sametime Entry 8.5.1 instances and I couldn't get things to convert, these steps fixed it for me!
**Special thanks to Gab Davis for leaving a comment on something that I had tried before, but missed in some testing. Once she reminded me of that, all the pieces fell together. She rocks!**
Sametime Woes (Domino Directory to LDAP)
***QUICK UPDATE***
Issue resolved, but, I still think the wiki should be worded better. Here is the updated blog post on the resolution.
********************
For the past couple of days, I have been having a real problem. And that problem is Sametime. I have been tasked with getting an instance of Sametime Standard up and running in our environment. Most of that work has been done by a consultant who knows what he is doing. While he is working on finishing that up, I have decided to test the steps of getting my current environment of Sametime Entry migrated to talk to the new Sametime Standard servers. You see, long ago when I installed Sametime Entry, I used the Domino Directory as the directory source for Sametime and not LDAP. As I had found out early on in the project, if you have a Sametime configuration set for Domino Directory, it won't talk to an LDAP configuration. So to get the old Sametime Entry to talk to the new Sametime Standard you have to go through a process of copying files, renaming files and overwriting files. For this task, I found this wiki article online
The steps seem VERY straight forward. Let's review. (My comments are italicized)
1. On the Lotus Sametime server, create a working directory to copy files to so that you can rename them.
Okay, no problem, I can do that.
2. Copy the "STAuthenticationLdap.dll" from the directory C:\Program Files\Lotus\Domino\Directory BB\Ldap to the working directory.
Okay, that shouldn't be a problem...wait, that directory \Lotus\Domino\Directory BB\Ldap is empty on all of my installs. The folder is there, but it's empty. The .dll that it calls for is located in the \Lotus\Domino folder, okay, I'll use that one instead. Moving on.
3. In the working directory, rename the "STAuthenticationLdap.dll" file to "STAuthentication.dll."
Easy-peasy. Done. Next!
4. Copy the renamed "STAuthentication.dll" file to the C:\Program Files\Lotus\Domino or $installeddir\Lotus\Domino.
Note Copying the "STAuthentication.dll" file to the C:\Program Files\Lotus\Domino or $installeddir\Lotus\Domino will overwrite an existing file of the same name.
Hmm...didn't ask to be overwritten. The file didn't exist in the first place. Odd. Moving on.
5. Copy the file "STGroupsLdap.dll" from the directory C:\Program Files\Lotus\Domino\Directory BB\Ldap to the working directory.
Again, the LDAP folder is empty, had to find the file in the Lotus\Domino directory.
6. Rename the "STGroupsLdap.dll" file to "STGroups.dll."
No probs
7. Copy the renamed STGroups.dll file to the C:\Sametime directory.
Note Copying the "STGroups.dll" file to the C:\Sametime directory will overwrite an existing file of the same name.
Okay, this one did ask to be overwritten! Next!
8. Copy the file "STResolveLdap.dll" from the directory C:\Program Files\Lotus\Domino\Directory BB\Ldap to the working directory.
Again, not in \LDAP directory, but in the \Domino directory.
9. Rename the "STResolveLdap.dll" file to "STResolve.dll."
Yup, no probs.
10. Copy the renamed "STResolve.dll" file to the C:\Program Files\Lotus\Domino or $installeddir\Lotus\Domino.
Note Copying the "STResolve.dll" file to the C:\Sametime directory will overwrite an existing file of the same name.
Another one that needed overwritten! WooHoo! Next.
11. Copy the "StBrowseLdap.dll" file from the directory C:\Program Files\Lotus\Domino\Directory BB\Ldap to the working directory.
You guessed it, it was in the \Domino directory.
12. Rename the "StBrowseLdap.dll" file to "StBrowse.dll."
Ok.
13. Copy the renamed STBrowse.dll file to the C:\Program Files\Lotus\Domino or $installeddir\Lotus\Domino.
While the steps didn't call for it, this file needed overwritten.
14. Copy the "StDirectoryListLDAP.sym" file from the directory C:\Program Files\Lotus\Domino\Directory BB\Ldap to the working directory.
This file exists NOWHERE. None of my 6 Sametime Entry servers have this file. Even a clean installation of Sametime Entry 8.5.1 does not have this file included in it.
15. Rename the "StDirectoryListLDAP.sym" file to "StDirectoryList.sym."
Can't do it, because I don't have it.
16.Copy the renamed StDirectoryList.sym file to the C:\Program Files\Lotus\Domino or $installeddir\Lotus\Domino.
I'm thinking I'm going to need a milk carton "Have you seen me?" for this file.
17. Copy the "StLdap.dll" file from the directory C:\Program Files\Lotus\Domino\Directory BB\Ldap to C:\Program Files\Lotus\Domino or $installeddir\Lotus\Domino.
File already existed in the \Domino directory. The \LDAP, again, NEVER had any files in it.
18. Copy the "stLdap.ini" file from the directory C:\Program Files\Lotus\Domino\Directory BB\Ldap to C:\Program Files\Lotus\Domino or $installeddir\Lotus\Domino.
Again, same as step 17. That file was already in \Domino.
Okay, so I followed all the steps as listed the best I could, setup up and ran the rename task for the vpuserinfo.nsf file, changed the DIRECTORY= line in the sametime.ini from NOTES to LDAP and started up the STADDIN task. Hoping that things would "just work", they of course didn't. Right away I am noticing that the following services won't start:
STDirectory
ST Reflector
ST Resolve
ST Users
Plus, I am seeing this message flash by on my test server
[0A0C:004A-13DC] 11/28/2012 09:41:56 AM Process E:\Lotus\Domino\StUsers.exe (5400/0x1518) has terminated abnormally
So I ask you, my dear fellow Admins. What the frak am I missing?
Issue resolved, but, I still think the wiki should be worded better. Here is the updated blog post on the resolution.
********************
For the past couple of days, I have been having a real problem. And that problem is Sametime. I have been tasked with getting an instance of Sametime Standard up and running in our environment. Most of that work has been done by a consultant who knows what he is doing. While he is working on finishing that up, I have decided to test the steps of getting my current environment of Sametime Entry migrated to talk to the new Sametime Standard servers. You see, long ago when I installed Sametime Entry, I used the Domino Directory as the directory source for Sametime and not LDAP. As I had found out early on in the project, if you have a Sametime configuration set for Domino Directory, it won't talk to an LDAP configuration. So to get the old Sametime Entry to talk to the new Sametime Standard you have to go through a process of copying files, renaming files and overwriting files. For this task, I found this wiki article online
The steps seem VERY straight forward. Let's review. (My comments are italicized)
1. On the Lotus Sametime server, create a working directory to copy files to so that you can rename them.
Okay, no problem, I can do that.
2. Copy the "STAuthenticationLdap.dll" from the directory C:\Program Files\Lotus\Domino\Directory BB\Ldap to the working directory.
Okay, that shouldn't be a problem...wait, that directory \Lotus\Domino\Directory BB\Ldap is empty on all of my installs. The folder is there, but it's empty. The .dll that it calls for is located in the \Lotus\Domino folder, okay, I'll use that one instead. Moving on.
3. In the working directory, rename the "STAuthenticationLdap.dll" file to "STAuthentication.dll."
Easy-peasy. Done. Next!
4. Copy the renamed "STAuthentication.dll" file to the C:\Program Files\Lotus\Domino or $installeddir\Lotus\Domino.
Note Copying the "STAuthentication.dll" file to the C:\Program Files\Lotus\Domino or $installeddir\Lotus\Domino will overwrite an existing file of the same name.
Hmm...didn't ask to be overwritten. The file didn't exist in the first place. Odd. Moving on.
5. Copy the file "STGroupsLdap.dll" from the directory C:\Program Files\Lotus\Domino\Directory BB\Ldap to the working directory.
Again, the LDAP folder is empty, had to find the file in the Lotus\Domino directory.
6. Rename the "STGroupsLdap.dll" file to "STGroups.dll."
No probs
7. Copy the renamed STGroups.dll file to the C:\Sametime directory.
Note Copying the "STGroups.dll" file to the C:\Sametime directory will overwrite an existing file of the same name.
Okay, this one did ask to be overwritten! Next!
8. Copy the file "STResolveLdap.dll" from the directory C:\Program Files\Lotus\Domino\Directory BB\Ldap to the working directory.
Again, not in \LDAP directory, but in the \Domino directory.
9. Rename the "STResolveLdap.dll" file to "STResolve.dll."
Yup, no probs.
10. Copy the renamed "STResolve.dll" file to the C:\Program Files\Lotus\Domino or $installeddir\Lotus\Domino.
Note Copying the "STResolve.dll" file to the C:\Sametime directory will overwrite an existing file of the same name.
Another one that needed overwritten! WooHoo! Next.
11. Copy the "StBrowseLdap.dll" file from the directory C:\Program Files\Lotus\Domino\Directory BB\Ldap to the working directory.
You guessed it, it was in the \Domino directory.
12. Rename the "StBrowseLdap.dll" file to "StBrowse.dll."
Ok.
13. Copy the renamed STBrowse.dll file to the C:\Program Files\Lotus\Domino or $installeddir\Lotus\Domino.
While the steps didn't call for it, this file needed overwritten.
14. Copy the "StDirectoryListLDAP.sym" file from the directory C:\Program Files\Lotus\Domino\Directory BB\Ldap to the working directory.
This file exists NOWHERE. None of my 6 Sametime Entry servers have this file. Even a clean installation of Sametime Entry 8.5.1 does not have this file included in it.
15. Rename the "StDirectoryListLDAP.sym" file to "StDirectoryList.sym."
Can't do it, because I don't have it.
16.Copy the renamed StDirectoryList.sym file to the C:\Program Files\Lotus\Domino or $installeddir\Lotus\Domino.
I'm thinking I'm going to need a milk carton "Have you seen me?" for this file.
17. Copy the "StLdap.dll" file from the directory C:\Program Files\Lotus\Domino\Directory BB\Ldap to C:\Program Files\Lotus\Domino or $installeddir\Lotus\Domino.
File already existed in the \Domino directory. The \LDAP, again, NEVER had any files in it.
18. Copy the "stLdap.ini" file from the directory C:\Program Files\Lotus\Domino\Directory BB\Ldap to C:\Program Files\Lotus\Domino or $installeddir\Lotus\Domino.
Again, same as step 17. That file was already in \Domino.
Okay, so I followed all the steps as listed the best I could, setup up and ran the rename task for the vpuserinfo.nsf file, changed the DIRECTORY= line in the sametime.ini from NOTES to LDAP and started up the STADDIN task. Hoping that things would "just work", they of course didn't. Right away I am noticing that the following services won't start:
STDirectory
ST Reflector
ST Resolve
ST Users
Plus, I am seeing this message flash by on my test server
[0A0C:004A-13DC] 11/28/2012 09:41:56 AM Process E:\Lotus\Domino\StUsers.exe (5400/0x1518) has terminated abnormally
So I ask you, my dear fellow Admins. What the frak am I missing?
Wednesday, July 1, 2009
SnTT - Enabling ALL the bells and whistles!
As we're getting ready to start the big push of rolling out some form of the R8.* client, one of the features that management requested was to enable video chat via the integrated Sametime client. After speaking with some technical people from IBM about this, they told me that it was no problem to turn on all of the functions that the stand-alone Sametime client has in the integrated Sametime Connect in Notes. I just needed to have at least standard installation of Sametime installed on the server and it should work.
So of course I didn't read any documentation about it, I just set off to install Sametime Standard on a test server I have in our environment and reconfigured mine and anothers Notes client to use that server as our Sametime server. Thinking that was all that I needed to do, I was pretty disappointed when when we came to find that features like "Call" and "Instant Meetings" were unavailable to us.
Knowing that there are no desktop policies that control functions in the integrated Sametime Connect client for Lotus Notes..harrumph.., I set off to look in the Sametime server administration to see if there were any settings there they would turn those functions one. There are! But, there are not easy to find and can be easily overlooked. Here are the steps I followed:
1. Log into the Sametime server with a web browser.
2. Click on "Administer the server"
3. From the left hand menu, select "Policies"
4. Now click on "Sametime Default Policy"
5. When the page refreshes, scroll all the way to the bottom of the page to the "Integrated Sametime Connect" section.
6. In the section "Allow all Sametime Connect features to be used with integrated clients", select the check box next to "Yes" to activate the setting.
7. Click Ok to save the settings
At this point, I restarted the server and when Sametime initialized, we were able to call each other and have a video and voice chat. Neat stuff!
So of course I didn't read any documentation about it, I just set off to install Sametime Standard on a test server I have in our environment and reconfigured mine and anothers Notes client to use that server as our Sametime server. Thinking that was all that I needed to do, I was pretty disappointed when when we came to find that features like "Call" and "Instant Meetings" were unavailable to us.
Knowing that there are no desktop policies that control functions in the integrated Sametime Connect client for Lotus Notes..harrumph.., I set off to look in the Sametime server administration to see if there were any settings there they would turn those functions one. There are! But, there are not easy to find and can be easily overlooked. Here are the steps I followed:
1. Log into the Sametime server with a web browser.
2. Click on "Administer the server"
3. From the left hand menu, select "Policies"
4. Now click on "Sametime Default Policy"
5. When the page refreshes, scroll all the way to the bottom of the page to the "Integrated Sametime Connect" section.
6. In the section "Allow all Sametime Connect features to be used with integrated clients", select the check box next to "Yes" to activate the setting.
7. Click Ok to save the settings
At this point, I restarted the server and when Sametime initialized, we were able to call each other and have a video and voice chat. Neat stuff!
Tuesday, June 23, 2009
A plea for a policy from Lotus
In the past I've posted several "how-to's" on using InstallShieldTuner for Lotus Notes to create custom install packages of the Lotus Notes client for use in either a roll-out or a Smart Upgrade package for an upgrade. With the recent death of the 8.0.x code stream, I decided to bite the bullet and start looking at creating a new package that I could use to test rolling out 8.5 Standard clients. In the past, I had created custom installs for R6, 7 and 8 basic and in those installations, I was able to have some parameters set for the embeded Sametime functionality. My favorite, and the ones that my management liked having set, where that after 5 minutes away from the keyboard, Sametime would set your status as Away and when the mouse is moved, the status retured to Active. The following settings are added to the notes.ini during the install that is created using InstallShieldTuner:
$STActiveToAwayEnabled=1
$STAwayToActiveEnabled=1
$STActiveToAwayTimeout=5
So in looking at creating a new install package for 8.5.0, I couldn't find anything similar to these notes.ini to set that functionality. I can still add those to the install package and they will work as expected if I run the basic install, but in Standard, the settings are ignored. So I opened a PMR asking how to get that setting put in place during install or even with a policy. Well, the email from the helpful Lotus support representative told me that he understands what I'm trying to do, but that functionality is not there.
So Lotus, please hear me, a lowly admin crying out in the night. If it's not too late for 8.5.1, is there some way to either set those Auto-Status change values in the installation or better yet, with a policy?
Stay tuned!
$STActiveToAwayEnabled=1
$STAwayToActiveEnabled=1
$STActiveToAwayTimeout=5
So in looking at creating a new install package for 8.5.0, I couldn't find anything similar to these notes.ini to set that functionality. I can still add those to the install package and they will work as expected if I run the basic install, but in Standard, the settings are ignored. So I opened a PMR asking how to get that setting put in place during install or even with a policy. Well, the email from the helpful Lotus support representative told me that he understands what I'm trying to do, but that functionality is not there.
So Lotus, please hear me, a lowly admin crying out in the night. If it's not too late for 8.5.1, is there some way to either set those Auto-Status change values in the installation or better yet, with a policy?
Stay tuned!
Monday, February 9, 2009
Make Sametime Servers Play Nice With Each Other
I had another one of those "pulling what's left of my hair out of my head" moments today. You see, as my company grows, I've decided that it's time to install a couple more remote Sametime servers instead of having all users come back to the home office to connect. My WAN people would appreciate that I'm sure. So with the new server up and running at the remote location, I thought all I would need to do was dabble in the STConfig.nsf and make sure that the VPS_TRUSTED_IPS= was populated correctly. But after checking, rechecking and checking my configuration settings again, I was still unable to have the Sametime server talk to another one. Then I remembered to look in the sametime.log. All of a sudden it was like watching "Blues Clues" with Molly when she was younger. A clue! A clue!
The log file reported the following error:
I Server 09/Feb/09, 12:55:24 Rejecting server server IP - reported security level=0
After searching Sametime support site for "reported security level=0" I found the answer right away. To resolve the issue, I opened the sametime.ini on the new server and looked for the line:
VP_SECURITY_LEVEL=
By default, the server had set the value to 25 during initial install. After changing the value to match what my other servers are set to, 0 (zero) and restarting Domino, I was able to get the servers talking to one another. That value must be the same in each Sametime server that you are attempting to get to connect.
Now if I just remember to do this again in a couple weeks with the next server, I just might save a few hairs.
The log file reported the following error:
I Server 09/Feb/09, 12:55:24 Rejecting server server IP - reported security level=0
After searching Sametime support site for "reported security level=0" I found the answer right away. To resolve the issue, I opened the sametime.ini on the new server and looked for the line:
VP_SECURITY_LEVEL=
By default, the server had set the value to 25 during initial install. After changing the value to match what my other servers are set to, 0 (zero) and restarting Domino, I was able to get the servers talking to one another. That value must be the same in each Sametime server that you are attempting to get to connect.
Now if I just remember to do this again in a couple weeks with the next server, I just might save a few hairs.
Friday, August 29, 2008
Sametime Entry 8.0.1 Upgrade Error (Funny)
Like the good little Domino Administrator that I am, I wanted to make sure that the upgrade for my Sametime 7.0 Limited to Sametime 8.0.1 Entry would work fine on my test server before I roll it out in production with my 8.0.2 server upgrade. Sounds like a no brain-er, right? Wrong.
During the installation process, I kept getting the following error popup:
Domino has not been configured. Configure Domino before installing the Sametime server
So it was off to the usual search locations to see if anyone else has had this problem in the past. Google, Notes.net, support site had nothing similar to this. Then the thought occurred to me to make sure that I had put the Domino server installation location in the PATH statement on the Windows server. Well, that was there too. Not wanting to think much more about it, (it is Friday after all), I called and opened up a PMR with support.
Once the technician was on the line, I explained the problem to him. After a short pause he said that he had heard of it before. He then asked me to open my notes.ini file on the server. I complied. He then asked me to look at the first line in the file, [NOTES.INI]. Okay, it's there. He then asked me if all of the letters were upper case. They are. He then asked me to leave the first letter uppercase, but make all of the other letters lowercase so it looks like this [Notes.ini]. I saved and closed the file and started the server installation back up. It ran right through with no errors. We both had a good laugh over that one.
During the installation process, I kept getting the following error popup:
Domino has not been configured. Configure Domino before installing the Sametime server
So it was off to the usual search locations to see if anyone else has had this problem in the past. Google, Notes.net, support site had nothing similar to this. Then the thought occurred to me to make sure that I had put the Domino server installation location in the PATH statement on the Windows server. Well, that was there too. Not wanting to think much more about it, (it is Friday after all), I called and opened up a PMR with support.
Once the technician was on the line, I explained the problem to him. After a short pause he said that he had heard of it before. He then asked me to open my notes.ini file on the server. I complied. He then asked me to look at the first line in the file, [NOTES.INI]. Okay, it's there. He then asked me if all of the letters were upper case. They are. He then asked me to leave the first letter uppercase, but make all of the other letters lowercase so it looks like this [Notes.ini]. I saved and closed the file and started the server installation back up. It ran right through with no errors. We both had a good laugh over that one.
Subscribe to:
Posts (Atom)