Publishing, Site Settings and Permissions

[KenM]

We are moving our Intranet, finally, from NT to Windows 2003 Server, 2002
Server Extensions. Due to our company rules, the Migration Tool was not an
option.
We have published all the webs (~130) to the new development server, set the
subwebs to Unique permissions and assigned approriate rights for different
Authors in each sub site.
I would like that when we publish the sites to the new production server,
the site settings and unique permission settings go with the site, but after
publishing a few sites, they are all set to have the same permissions as the
parent. Is there no way to send the sites settings with the webs when
publishing, to save the hours need to open each site and make the settings?
Thanks in advance.
ken

 

[MD Websunlimited]

Hi Ken M.

No.

 

[Mark Fitzpatrick]

Ken,
User's and groups are specific to the server they are sitting on.
Basically a user account on server a is not the same as a user account on
server b, they are both seperate entities with their own unique ID
structures. The FP client has always been kept at arms length from the NT
SAM, giving it just enough abilities to alter the ACLs on the files to what
they need to be and to add permissions for existing NT SAM accounts, but MS
has always tried to limit it's ability to create accounts. Part of this is
to give admins more control since an administrator of a web could end up
creating accounts like crazy and clogging up the NT SAM and ruining the
authentication time of the server since NT SAM polling can be a taxing
operation.

Without using the migration tool there isn't much you can do as
permissions are really the one thing FP doesn't ever publish and can't
transfer.

Hope this helps,
Mark Fitzpatrick
Microsoft MVP - FrontPage