Re: DFS/AD Migration
- From: "Jeremy" <jeremy@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Sun, 22 Apr 2007 08:10:25 +1000
A bit of preaching first.
Its best practice for the permissions to be assign to local groups on the file server box (unless of course it is a DC) and then put domain groups in these. That way in the future if you move the box to a different domain or do another migration your only task is populating group and not propagating permisssions.
Off my soap box and to answer your question.
I've never used the security translation wizard before. I would just dump the current ACLs to a CSV file, do some manipulation in excel to make a transation matrix and then run a script that removes one ACL and replaces it with another. If u.sing the transaltion wizard sounds easier than this, then I'd use that.
Cheers,
Jeremy.
"jmp13" <jmp13@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:D38F672B-FC23-4457-9215-7CCA2C935DF7@xxxxxxxxxxxxxxxx
Currently running an NT to AD migration along with a server consolidation
implementing DFS. When the DFS teams move the folders/files to DFS the
accounts have the NT\username for permissions instead of AD\username. The
users have already been migrated but the servers have not. Do we need to
migrate the server then run the security translation wizard then proceed to
move to DFS? Is there a better way to handle the situation otherwise we have
to come up with a way to change the security to be AD\username instead of
NT\username?
.
- Prev by Date: Re: Change local administrator password ? through GPO or push script ?
- Next by Date: Re: ADMT and SID's
- Previous by thread: Re: adprep advice
- Next by thread: Re: replace whole Active directory domain controller whith new machine
- Index(es):
Relevant Pages
|
Loading
