R
Robert
Hi Guys,
I have problem that has only appeared after installing SP4 on Windows 2000
Server.
There are 3 accounts that can log on directly to the server - Admin,
SophosSweep (Antivirus account - Admin rights) and User 1(member of most
groups APART FROM Admin).
I do all the basic everyday duties on the server (as User 1 - I am not
allowed Admin rights to the server <not officially>) - checking the
anti-virus log, checking the backup (NTBackup) logs and changing the DAT
tapes.
What I was doing before was to login to the server in the morning check the
backup log, print out the summary log and swap the tapes and then log off
the server.
NTbackup is setup to look for the .bks (backup selection) files under my
server user account (User 1). This file is stored in C:\Doc & Setting\User
1\Local Settings\App Data\Windows\Windows NT\Ntbackup\DailyBackup.bks.
However, since installing SP4 everytime that I log off the server, the
C:\...\Windows\Windows NT\Ntbackup\ folder and all files within it are
deleted.
So, when the backup schedule runs at 23.00, if the User 1 is logged out, the
backup log says "..could not find DailyBackup.bks file/folder"
I have worked around this by changing the tapes in the morning and 'Locking'
computer instead of logging out. This is all well and good, but my boss
works later than me and sometimes logs onto the server and logs out (messing
up the backup).
I know there is an underlying issue that is causing this, but I want to move
the .bks file to persistent place on the server .i.e (C:\Backup) that won't
get delete when I log off. But NTBackup seems to be hard-coded to look for
the .bks file in C:\Doc & Setting\User 1\Local Settings\App
Data\Windows\Windows NT\Ntbackup\DailyBackup.bks.
Is there a reg key that I can change to hard-code NTBackup to look in
C:\Backup (for instance)? Or is there another fix that will enable my
UserProfile for User 1 not to be deleted each time I log out?
TIA,
Robert
p.s. Sorry for the rambling account, I always like to give a little
background story for better understanding.
I have problem that has only appeared after installing SP4 on Windows 2000
Server.
There are 3 accounts that can log on directly to the server - Admin,
SophosSweep (Antivirus account - Admin rights) and User 1(member of most
groups APART FROM Admin).
I do all the basic everyday duties on the server (as User 1 - I am not
allowed Admin rights to the server <not officially>) - checking the
anti-virus log, checking the backup (NTBackup) logs and changing the DAT
tapes.
What I was doing before was to login to the server in the morning check the
backup log, print out the summary log and swap the tapes and then log off
the server.
NTbackup is setup to look for the .bks (backup selection) files under my
server user account (User 1). This file is stored in C:\Doc & Setting\User
1\Local Settings\App Data\Windows\Windows NT\Ntbackup\DailyBackup.bks.
However, since installing SP4 everytime that I log off the server, the
C:\...\Windows\Windows NT\Ntbackup\ folder and all files within it are
deleted.
So, when the backup schedule runs at 23.00, if the User 1 is logged out, the
backup log says "..could not find DailyBackup.bks file/folder"
I have worked around this by changing the tapes in the morning and 'Locking'
computer instead of logging out. This is all well and good, but my boss
works later than me and sometimes logs onto the server and logs out (messing
up the backup).
I know there is an underlying issue that is causing this, but I want to move
the .bks file to persistent place on the server .i.e (C:\Backup) that won't
get delete when I log off. But NTBackup seems to be hard-coded to look for
the .bks file in C:\Doc & Setting\User 1\Local Settings\App
Data\Windows\Windows NT\Ntbackup\DailyBackup.bks.
Is there a reg key that I can change to hard-code NTBackup to look in
C:\Backup (for instance)? Or is there another fix that will enable my
UserProfile for User 1 not to be deleted each time I log out?
TIA,
Robert
p.s. Sorry for the rambling account, I always like to give a little
background story for better understanding.