Are you backing up anything other than the system state? There was an issue that began with 2003 SP1 - the workaround is to back up any regular file from the boot drive as well as the system state.
Carl From: Joseph L. Casale [mailto:[EMAIL PROTECTED] Sent: Thursday, June 26, 2008 2:18 PM To: NT System Admin Issues Subject: RE: Scheduled Sys state backup on small DC That's what I am doing J It's the User associated with the batch job that causes the UserEnv errors. I know it *can* be done with the local admin account but sometimes you get these issues. Just hoping there was a more correct way I was unaware of to avoid this. jlc From: Reimer, Mark [mailto:[EMAIL PROTECTED] Sent: Thursday, June 26, 2008 11:53 AM To: NT System Admin Issues Subject: RE: Scheduled Sys state backup on small DC I use NTBackup in a batch file (with the command line version of ntbackup) to back up system state to a disk file. It just runs with local system account. I just use the at command to schedule it. Seems to work just fine on a number of servers. Mark _____ From: Joseph L. Casale [mailto:[EMAIL PROTECTED] Sent: Thursday, June 26, 2008 11:42 AM To: NT System Admin Issues Subject: Scheduled Sys state backup on small DC I have one site with a small DC that does an NTBackup script to dump the systate to a disc file that gets backed up later. It uses the Dom Admin account to run and this throws up Userenv errors when its done. What's the best Account to run such a script under? Is it even possible to use Local System for example? Thanks! jlc ~ Upgrade to Next Generation Antispam/Antivirus with Ninja! ~ ~ <http://www.sunbelt-software.com/SunbeltMessagingNinja.cfm> ~
