As Fabian already mentioned: instead of thanking me please learn to quote
properly. I certainly will be reluctant to help otherwise.
Implementation is the sincerest kind of flattery ;-)
The Reason is, that the local Groups on the Windows NT 4.0 Server
contains global groups of the domain. If you create a local group
on the new server with not the same SIDs the global groups should not
automatically assign to the local groups.
This is what i want to reach.
Either you have problems explaining what you want to do, or you don't
understand how local and global groups work. How on earth should the
global groups become members of the newly created local group without
somebody assigning them? And as that somebody would be you, what do you
need the SID for? There is no automatic assigning of group members!
In fact with many Perl Moduls you can do all that you want to
create/change groups, accounts, ...etc. so i thougt that i also
can read the SIDs of my old local groups to create these groups on the
new Server and allocate the original SIDs. So that the global
Groups assign automatical to these local groups.
Whats wrong with these Thoughts ?
It doesn't work like this?
But joking aside: You would be far better of with an upgrade after backup.
Or at least with a backup of your local users and groups and restore on
the new server (There are lots of tools for this purpose, e.g. the NTSEC
suite or even tools from the NT ResourceKit).
I would suggest reading a bit more on the subject, leaving Perl aside.
Thomas
--
$/=$,,$_=<DATA>,s,(.*),$1,see;__END__
s,^(.*\043),,mg,@_=map{[split'']}split;{#>J~.>_an~>>e~......>r~
$_=$_[$%][$"];y,<~>^,-++-,?{$/=--$|?'"':#..u.t.^.o.P.r.>ha~.e..
'%',s,(.),\$$/$1=1,,$;=$_}:/\w/?{y,_, ,,#..>s^~ht<._..._..c....
print}:y,.,,||last,,,,,,$_=$;;eval,redo}#.....>.e.r^.>l^..>k^.-