We are deploying Windows 2000 servers at our HQ and field (60 sites) offices. Our local admins have only permissions to their OUs, no server permissions. The problem is that ArcServe 9 requires the backup account to be a member of "domain administrators" and "administrators", which is not acceptable to our supervisors, since they do not wish field admins to manage the hardware or modify any settings. Is there any resolution to this? Microsoft says no, Computer Associates says no, but I can't believe we are the organization with this administration policy. Thanks!

First and foremost, if that's the way your company wants to run, then let them. The first time something fails, and no adequate backup is available, and time/money is lost hand over fist...you can point and snicker, and remind them that they thought that having a chosen set of Backup Operators was unacceptable. Chances are, it's not a mistake they'll make twice. Lastly, encourage them to investigate creating one Backup Operator at each site that handles that job primarily. There are such accounts available both at the Local and Domain level. Some mods can be made for security reasons to ensure that a backup can be done, and little else aside from what everyone else has access to. Just takes a little time to research. Personally, I shake my head when I hear tales of companies that are this blunted when it comes to backups.

Are you setting up backup exec or some other software like that to run automatic backups and just having them change the tapes? Set up backup exec with the correct username and PW in services and it will run. Get a auto loader. If they dont want to pay for a auto loader and the proper software then refer to reply 1.

The service can run just fine without the local admins knowing the password. Configure the service to start with the account with the proper permissions. Don't tell the local admins what that password is. I don't see the problem.