Hi, Brandon - I've seen this happen with Windows "Mandatory" user accounts (these are the accounts Jason refered to that wipe out any changes to the user's 'Documents and Settings' folder upon logout).
Here's Microsoft's page on assigning mandatory profiles. http://support.microsoft.com/kb/q307800/ I believe to change a profile away from 'mandatory', you can just change their "Ntuser.man" file to be named "Ntuser.dat". (If the profile is manadtory, then 'Ntuser.man' is found under C:\Documents and Settings\<Windows Login Name>\). Hope that helps! -Murph Some say the world will end in fire and ice. Others say it will be segfaults. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jason Etheridge Sent: Thursday, June 12, 2008 10:54 PM To: Brandon W. Uhlman Cc: [email protected] Subject: [OPEN-ILS-DEV] Re: [Support] Installing staff clients onnon-privileged Windows accounts > We've run into a problem on some of our Windows XP staff clients where users > without Administrator rights don't seem to retain workstation registrations. > I'm pretty sure this is because the file ws_info is not being written. Are > there any magic suggestions that people have other than using Evergreen on > user accounts with Administrator rights? Or, are Administrator rights in > fact, required? For installation, Administrator rights are not necessarily required, depending on where you try to install the client (if you install to your Desktop, for example, you should not need Admin rights). For regular use, Administrator rights should not be required as long as the prefs.js file in the installation directory has a line reading pref("open-ils.write_in_user_chrome_directory", true); In Windows XP, this would make files like ws_info get written in a directory resembling this: C:\Documents and Settings\phasefx\Application Data\OpenILS\open_ils_staff_client\Profiles\dqh08qrd.default\chrome\ Now, I have seen Windows systems "protected" in such a way where files in C:\Documents and Settings\ gets purged after the Windows user logs off. I'm not sure how this is done, or whether that's what is affecting you. One thing you could do is run the staff client with the debug window open. This explains how: http://open-ils.org/dokuwiki/doku.php?id=scratchpad:debug_console That'll actually show you the path used for ws_info, and you can then more easily watch the behavior from Windows and see if the file gets created in the first place or deleted after the fact. Let us know if this helps! -- Jason Etheridge | VP, Community Support and Advocacy | Equinox Software, Inc. / The Evergreen Experts | phone: 1-877-OPEN-ILS (673-6457) | email: [EMAIL PROTECTED] | web: http://www.esilibrary.com
