Holiday weekends are always great times to do server upgrades and mail migrations.
Funny thing is all types of things can go wrong. Well here are some pieces for you all, just in case.
If you will be updating your classic community server (Domino Sametime) see this blog post from Marc Champoux where he outlines some steps and also hits on Quickr integration and some other issues.
Most of this was found when doing a Domino upgrade from 8.5.2 to 8.5.3. Also a Sametime upgrade from 8.0.1 to 8.5.2IF1 and Traveler from 8.5.2.X to 126.96.36.199.
Always backup everything first.
First thing to remember is to stop Domino from restarting automatically on reboot. Installing 8.5.3 will force you to reboot before you can restart Domino.
Second thing is you may find on reboot your server never comes back. You will be forced to have someone on site help you or go and do it yourself. The server, in this case a Windows 2003 server showed applying computer updates or something like that but it wasn't, just hung. 2 reasons can be guessed. One is remote desktop or your logoff did not go as planned and it hung with your login. The second is that 8.5.3 may ask if you want to upgrade the databases ODS. If so it stops with a yes/no request and if you did not change the automatic start to manual, you would be stuck too. So how do you resolve this? Easy, boot into safe mode of windows using F8. Then when you get to the desktop, run Domino and select yes or no to the question. But more likely you did not set automatic boot to manual. Do it now if you can and then restart the box. All should be good.
Another gotcha is Single Copy Template, an excellent idea, but if implemented without any thought, you may have errors which sayunable to open file or find single copy template. Also if you see ISpy errors about the single copy template, it is because Ispy uses the mail file template. Aha, you get the picture. So how do you fix it? See this Technote, #7002574 which explains it all. You shut down Domino and run the convert task and you must know the file name AND the Template Name. Example: >nconvert ispy50.nsf STDR85Mail mail85.ntf
Wait there is more. Hate the debug by default look of 8.5.3? Remove it using the console command:
set config debug_threadid=0 or to reinstate it set config debug_threadid=1
Traveler showing it can't respond in the allotted time frame with a user in 25,000 microseconds. Use Kevin from Groupwave's Post and add the properties. Thanks Kevin for that one which solved my problem!
Then there is a post I wrote that detailed how to resolve ST meetings, Classic community server version, though it was from 8.0.2 for cases when meetings would refresh every minute or 2 and wipe everything out.
Another Sametime item. If you see this, never mind the technote says its 8.0.2 related, we saw it on an 8.5.2 Sametime server, HTTP JVM: Caught exception from local listener: For input string: ""
Here is the Technote #1313986 about it. Sametime 8.5.2IF1 resolved this by the way in our case.
Also if you need the File list of ST 8.5.2IF1, you can see this Technote #4031295.
An oldie but a goodie, Sametime BuddyList is broken in iNotes and you see errors in the console, try this fix from this blog post of Gunawan. I got through the language issue, pretty sure you can too.
Edited 11/28/11 In case you lost Sametime client connections, the server edits the sametime.ini file and not with your previous information. Follow these references to ensure all clients can reconnect...or not.
Wiki about VPS allowed when you list the clients you want to use.
ST_MINIMAL_CLIENT_VERSION setting: reference from the 8.5.1 docs. Set this to zero and all clients are allowed
After upgrading Sametime Server to 8.5.1 users using Notes 8.x Basic and older Notes clients cannot log in Technote 1443291
This post may get edited more over the weekend.