Hi, when you publish a new website, the security do not follow. You have the parent web's security.
(I assumed you have iis 5.X)
Copy the roles.ini for your website to the new server (%document and settings%\all users\application data\microsoft\web server extensions\50\W3SVC1\%your site%.ini
This will transfert the roles configuration of your web site then you make a "check server health" and be sure to check "repair" checkboxes.
Your site should be fine after that.
* you must do this only the first time the site is published.
Hope this helps. Please let know if this resolve your issue
The only problem is we are still using FP2000, I know the "check server health" is an applet under the FP2002 FSE.
So ...
some observed issues ...
Publishing from one FP2000 site to another is causing the "read" permissions to change and also an observed issue is the scripting permissions is changed to "none" whereas it was previously 'scripts only
I got to hinking about the permissions issues and WHY they were being transferred when a person published ...
well I know the file structure inherits the permissions for mthe parent ... BUT ... a web site permissions inherit the specific permissions from the orignal website ... so when you right click on the base folder within FP ofthe host site you will see the option to allow "browsing" and "aloow scripts to be run" ... if those are not checked the desitination website will inherit these base web permissions. That was why regardless of how many times I would go into IIS and allow "check" read and "allow scripts only" ... immediately after someone published from that host site (staging) it would convert those permissions to those on the host site.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.