Whenever I run updates, patches, or detach/reattach databases I have to set EVERY user (except for me of course) as domain admin in Active Directory to have the "Raiser's Edge has detected.." message appear when users log-on to RE and begin updating. Otherwise I have to log on to the machine as myself (as a domain admin), or map to the deploy folder and do a manual update. We set users as local admins by default. Any ideas? Thanks so much! Bryce

It sounds like the users do not have the appropriate rights to the network share where the updates reside.

Would Read, List, and Read & Execute access do the trick?

We had other problems with the last upgrade until we made sure all the users had power user rights. Have you tried that?

Yes, on p. 7 of the RE Installation User Guide, it says, "If you are not at least a Power User, your system administrator must install the prerequisites before you can use The Raiser’s Edge." On p. 35, there are instructions for alternative update method, "Deploy The Raiser’s Edge as an MSI Package" Mark F. DeWitt, Database Manager College of Engineering University of California, Berkeley [Email Removed]

We do not set anyone as Domain Admin (there are only 3 of us and no users), all users are Power Users on their workstations. I have to go around to each workstation, Power Users don't seem to be able to run the upgrades/patches. I'm not understanding why local admins cannot upgrade, unless they do not have rights to the deploy folder on the server?

Besides the deploy folder, the other folder where I have had rights problems is on the local workstation where the software is installed. I believe the install default for this is C:\Program Files\Blackbaud, at least that's how we have it set up. Do Power Users have read-write-execute privileges on that folder on all of your workstations? Mark F. DeWitt, Database Manager College of Engineering University of California, Berkeley [Email Removed]

So let's clarify what locations we are talking about: 1) On the local workstation, the user must have at least Power User rights (ours have LOCAL Admin rights) 2) On the deploy folder, the user must have Power User rights? Thanks for your help so far!

That sounds like it should work, according to the documentation. Mind you, I've never gotten it to work, but I haven't really tried it since they weakened the requirement from local admin to power user. Now, we're moving to using a terminal server, where this shouldn't be an issue. Mark F. DeWitt, Database Manager College of Engineering University of California, Berkeley [Email Removed]

1) Yes, local admin is fine. I have had issues with local Power User access and decided to give local admin rights until I can get Power Users rights to work. 2) Read & Execute, List Folder Contents, & Read are the only permissions you need on the deploy folder on the network share. I created a group in Active Directory for Blackbaud users and assigned the group the above rights to the network share. Paul

Our shop has it set-up that users are local admins and the AD group for RE has modify rights to the deploy folder, but alas no prompt to update, unless I give them domain admin rights.. I wonder if the SQL groups play into this at all considering it occurs when starting RE.. [i]--- Edited at 12/3/2007 12:21:28 PM by Bryce Katzman[/i]

With local admin rights this should work. The only thing I can think of is to verify in the Blackbaud Management Console where the deploy folder is located and the user has the appropriate rights to that folder. Do you have any issues accessing the database? Paul

Our Auto Update works fine. We have each user set up as with Local Admin rights on their workstations.

It sounds like most of the posters here have only a small group of users (less than 50). What is the best way to make sure the update will occur when there are 100+ users and some are scattered all over the world- deploy Raiser's Edge as an MSI Package? Wouldn't the System Administrator have to do this (network engineer)?

A dedicated server running Terminal Services or Citrix would be the way to go, yes? We're about to deploy Terminal Services but we only have ~30 users, so we're going to use the same box as the database server and the terminal server. Mark F. DeWitt, Database Manager College of Engineering University of California, Berkeley [Email Removed]