|
Posted by Joe Richards [MVP] on February 7, 2007, 9:41 am
If you were Registered and logged in, you could reply and use other advanced thread options I agree with Roger here, this is something I have done in the past with
LocalSystem. Create and schedule a CMD script which launches NTBackup
from the command line and once completed copies the file to a remote
machine. This should work fine as LocalSystem assuming you are in an
Active Directory domain.
--
Joe Richards Microsoft MVP Windows Server Directory Services
Author of O'Reilly Active Directory Third Edition
www.joeware.net
---O'Reilly Active Directory Third Edition now available---
http://www.joeware.net/win/ad3e.htm
Roger Abell [MVP] wrote:
> Will,
>
> Within a domain, the System account (or the Network Service account),
> when going off-box to other domain machines, is the Machinename$
> domain account of that machine.
> Your scheduled task is perhaps having other issues.
> To test access to the share as System, try doing a simple access either
> in a startup/shutdown script or via a cmd prompt obtained for System.
> I would suggest that you consider doing the scheduled NTbackup job
> so that it writes to local disk, and then copy this out to remote in a
> separate task.
>
> Roger
>> Sorry, posted that too early and left out the part that generated the
>> subject line for the thread.
>>
>> If we must use a domain account of a user and specify a password, in order
>> to use a share, is there a way to encrypt a string on a member server such
>> that it could only be decrypted by a specific target member server?
>> What
>> are the best options for sharing text you want to keep secret between
>> member
>> servers?
>>
>> --
>> Will
>>
>>
>>> I am looking at issues around having each computer do its own backups
>> using
>>> the native Windows backup application to a file server.
>>>
>>> Rather than having a custodial domain account used by the computers, and
>>> with that all of the hassles of dealing with how to secure the password,
>>> I
>>> am wondering if there is a way to do the DACL permissions to the target
>>> share / file system based on just authentication by Windows domain system
>> of
>>> the target computer itself. Could you put the machine object of the
>>> computer doing the backup into the DACL of the target share\folder-path,
>> and
>>> then run the backup process as SYSTEM on the client computer?
>>>
>>> I did try this as an experiment and the scheduled task refused to run.
>>> That could be a problem with the implementation or with the theory, and
>>> that's why I am checking.
>>>
>>> --
>>> Will
>>>
>>>
>>
>
>
|