Hi Wanda:
You should be able to use the System Account to backup encrypted files. I
just did a test here:
Create encrypted file with usera
Try to READ with userb (access denied)
Backup and restore with userb (userb has rights to the file) works fine
File is still encrypted after restore (userb cannot read, usera can)
Backed up another encrypted file via the scheduler
Restored file
File is still encrypted
I am running W2K SP1, TSM 4.12.12.
Basically an encrypted file prevents another user from reading the file but
that user can still backup, copy, delete the file etc, as long as they have
rights.
Tim Rushforth
City of Winnipeg
-----Original Message-----
From: Prather, Wanda [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, May 15, 2001 12:39 PM
To: [EMAIL PROTECTED]
Subject: Win2k Scheduler & SYSTEM Account?
We normally install the TSM Scheduler on all our machines using the default
SYSTEM account.
For a Win2K Pro machine, is there any disadvantage/fallout to using the
person's regular network logon account, instead of the SYSTEM account?
(assuming it is a member of the local ADMINISTRATORs group).
It looks like this is what we will HAVE to do to back up files encrypted
with the Windows 2000 File Encryption.
If you use a network logon account to run the scheduler, what happens if the
password expires? It is toast?
