I can't find the "rhyme or reason" as to why sometimes the logs are under the "Administrator" profile and sometimes under "Default User" instead. They are consistently in the same folder every night for weeks, but then after a system reboot (like after updates, etc.) then it will sometimes change to the other profile (or not) and then consistently log to that one for weeks, etc.

Who is Participating?

I wonder is it putting them in the Administrator's profile when the server is left logged in but locked, but then when it's sitting at the logon prompt (following a restart or logout) where effectively nobody is logged on it's using the Default User profile? You may be able to run the ntbackup from the [runas /user:domain\Administrator] (you'll have to pipe the password to runas) command which should stabilise which profile ntbackup decides to use.

I looked for a way of changing the path in the past and just looked again, I can't find a way of doing it unfortunately. There's a batch file from Microsoft that just copies them to a new location and changes the name to the date. I suppose you could do something similar; have a batch file that moves the logs out of both those potential directories into one folder, c:\backuplogs\ say.

0

mcjAuthor Commented: 2007-05-30

Thanks Zenith63. It looks like the original problem that the log location is essentially "random" depending on whether the "current user" is Administrator (as in when you've been logged in and then lock the workstation) or Default User (as when the system has been rebooted, but no one has logged on at all) just isn't solvable directly. It seems that ntbackup won't let you specify, and the AT "RunAs" fetaure gets you nowhere either.

However, your answer is right on in that the best workaround is just to run a subequent script to copy from both locations to one, overwriting with newer. Works fine even though you'd think Microsoft would fix this in ntbackup directly.