Discussion Locked

Copying local groups and perms.

0 helpful
5 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Having diligently applied the MS AGLP method of assigning permissions to my NT4/IIS4 member server I now find myself in a bit of a pickle.

I'm moving the NT4/IIS4 member server to a new W2K/IIS5 member server in the same domain (i.e. hardware andoperating system upgrade). I can xcopy to copy the data and preserve the NTFS permissions and I can use utilities like Hyena (http://www.systemtools.com/) and/or addusers.exe (res. kit) to copy the local groups to the new box.

The problem is that the permissions on the files/folders do not resolve to the copied local groups on the new machine - SIDs don't match I guess.

Is there a way to move local groups and files/folders from one member server to another such that all the NTFS permissions that have been granted to the local groups on the old server still apply to the folders/files on the new server?

If I do have to reapply the permissions to every freakin' folder I sure won't be using local groups!

Thanks for your help (andthe opportunity to rant!).

5 replies

by 4u21der

Symantec ships a utility with Ghost. It is called 'Ghostwalker'. It allows you to re-image a NT machine, then re-create the SID's for that Machine.

I know that this utility gives you the capability to generate a
statistically unique SID for eachcopy of NT, but I don't think it
allows you to define your own SID.

I am not sure if this utility will work on Win2K. MSFT has not been to clear on the cloning issue!

Hope this info was helpfull.

Good Luck!

by jpoandl

I'm not sure about this. But I think you problem stems from the fact that the local groups accounts look different. For example: OLD SERVER -->\\webiis4\group1 vs. NEW SERVER --> \\webiis5\group1

because the server names are different, the local account look different. This is probably whats causing your problem.

I think what you need to do is recreate the same local group accounts on the new server. Then use SCOPY to copy the data from the old server to the new Windows 2000 server(security copy--if performing the data move from the NT 4.0 box. However, I believe Window 2000 XCOPY has the ability to move NTFS permission...this is something WINNT 4.0 xcopy did not have.) Anyway move the data with NTFS security information.Then take the first server off-line. Delete the server's machine account in the domain. Synchronise the domain. Then re-name the new Windows 2000 server as the same name as the old server.

After this is complete, the security rights should be good.

I've never actually done this, so I would suggest testing the theory first. (There may be a better way.)

by dshaykewich

That's a good thought - one that I had too - but I tried it and had no luck.

I think ultimately it comes down to the SIDs, which I think is what is actually attached to the resources (not the group names) when they're scopy'ed to the new server.

To date I've found no tool to copy the local group accounts' SIDs and names to the new computer.

The reason I've been really frustrated by this is because this must happen all the time - moving a member server on which AGLP permissions have been applied to a new physical machine.

This discussion is closed to new replies.