The local system account has full control over all
local resources
(registry,
drives, etc.) so
you shouldn't have any problems provided that you
aren't accessing any
non-local resources
(remote drives or shares) from your schedule (the
local system account =
has
no
domain authority
so accessing remote resources will always fail).

Note that by default the client service is installed
to logon as the lo=
cal
system account.

Hope this helps ......


Pete Tanenhaus, ADSM NT Development
---------------------- Forwarded by Pete Tanenhaus/San
Jose/IBM on 10/1=
Jose/IBM on 10/1=
2/98
02:05 PM ---------------------------


ADSM-L AT VM.MARIST DOT EDU on 10/12/98 12:38:24 PM
Please respond to ADSM-L AT VM.MARIST DOT EDU
To: ADSM-L AT VM.MARIST DOT EDU
cc:
Subject: NTFS permissions


Hello ADSM/NT folks,

Our illustrious Data Protection department has
implemented a new
requirement.  For our NT servers, user Home
directories will not be
accessible by any other user except the user himself.
In other words, =
the
NT "SYSTEM" user and the ADMINISTRATOR will not have
permission to acce=
ss
these files.  I have setup the ADSM Client Scheduler
to run under the
"SYSTEM" account.  I have written procedures for our
operators to log i=
n as
the ADMINISTRATOR when using the Backup/Archive
client.

I was sure that this would cause problems with ADSM.
It seems though t=
hat
the scheduled backup completed OK.  I also ran a test
where I was able =
to
restore a file to a user's home directory where the
ADMINISTRATOR has n=
o
permissions.

How is this possible?  What are the ADSM requirements?

Thanks in advance for your help.

Greg Heis
FedEx



___________________________________________________________
Do You Yahoo!?
Achetez, vendez! @ votre prix! Sur http://encheres.yahoo.fr