I recently upgraded our Sametime environment to version 8.5.1 from version 7.5.1. Since we also wanted to transfer to new server hardware I figured it would be easiest to do a new installation and just migrate the vpuserinfo.nsf and stconf.nsf. Since no configuration settings are being migrated this was a good opportunity to startÂ afresh.
This here is a quick note (from own experience) that the design of the vpuserinfo.nsf is important for the successful run of Sametime.
Since the vpuserinfo.nsf got copied to the new server after the set-up it didn’t receive any design updates. This causes the Sametime community server to not accept any new client connections. Obviously since neither the user’s contact list nor privacy settings can be found. Thanks to IBM support for hinting into that direction. I spend about two hours on the phone with the support checking all sorts of logs and config settings. Until we were left with none but one possibility: ‘a corrupt vpuserinfo’.
When compact, fixup and updall didn’t yield any success I got suspicious and took a closer look at the design of the database.Â While I refreshed the design of the databases from the stuserinfo.nsf template I did not realise that LocalDomainAdmins do not have access to the template itself. This effectively removes all design elements from the vpuserinfo.nsf, resulting in the issue as described above: no users are able to connect to the Sametime Community server. Once I refreshed the design of the database on the server console instead of the admin client my users where happily connecting to their new Sametime server.