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 a backup 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!**

2 comments:

pdf digital signature said...

Simply want to say your article is as astounding.
The clarity for your submit is just spectacular and that i could suppose you’re a professional

Lars Olufsen said...

This post is pure gold.

Thanks, Andy!