tag:blogger.com,1999:blog-26049584.post5868484409863585680..comments2008-12-13T01:02:23.342-05:00Charles Robinsonhttp://www.blogger.com/profile/04606895130887441753noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-26049584.post-69213940075864572842006-09-25T10:48:00.000-04:002006-09-25T10:48:00.000-04:00Domino has its own roaming implementation, which will keep one copy of the ID file encrypted on the server and move it around as needed. The biggest issue with this is the desktop does not roam, which means the Workspace isn't usable. Lotus' workaround is to have users bookmark databases and pin the bookmark folder open instead of using the workspace. I plan to test that, too, to get user feedback.Charles Robinsonhttp://www.blogger.com/profile/04606895130887441753noreply@blogger.comtag:blogger.com,1999:blog-26049584.post-90006989862366466232006-09-25T03:38:00.000-04:002006-09-25T03:38:00.000-04:00I'm having some problems getting notes and citrix to play well together, so I' glad to see that there are other ways to do it than the IBM cookbook.<br /><br />This seems to be a smart way to do it if you have one terminal server. But what if you have several? And the users log into them in a random fashion. Could you end up with a copy of the id file on each server? And then how do you cope with password changes?<br /><br />You could perhaps have some sort of roaming/copying of these files to a private folder, but you could stil have problems if the server chrashes, the coying breaks or other unseen events.Odd Åge Skogheimnoreply@blogger.com