|
Posted by Roger Abell [MVP] on November 22, 2006, 11:45 pm
Please log in for more thread options Blast from the past ! You're welcome.
--
ra
> Thank-you both for your timely reply! Apologies for not thanking you
> sooner, we went with the
> "backup-to-a-place-with-full-perms-and-index-from-there" route.
>
> Thanks again!
>
>
> Roger Abell [MVP] wrote:
>> You would likely be wary about doing massive changes
>> to the existing permissions of stored content. There is no
>> magic account, as the NTFS permissions are always obeyed,
>> except when access is done via the backup/restore APIs.
>> If the current permissions do not reliably provide a grant of
>> permissions to such as Administrators, then there is no group
>> you could use to allow an account to "become magic".
>> If your content is not too huge, you could try use of NTbackup
>> to copy content to an area where, when restored, it is restored
>> without restoring permissions. You would have the same
>> structures, but differently rooted, and if these new restore
>> roots granted to the magic group, then this could be indexed
>> by an account in the group.
>> Otherwise, you would need alter permissions on the originals.
>>
>> > Hi all,
>> >
>> > We are starting a document retention project. As part of this project,
>> > we need to index all data on all file servers. The indexing program
>> > runs under a domain account.
>> >
>> > How do I create the account in such a way that it has full access to
>> > every file and folder in the domain? (I've explained the security
>> > implications to mgmt)
>> >
>> > I tried it as both a "domain administrator" and "backup operator" but
>> > neither account was able to access everything. Is there another way to
>> > go about it?
>> >
>> > Thanks in advance for any tips.
>> >
>> > Cheers!
>> >
>
|