SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

i have a staging environment and a production environment . The production environment setting is Allow Anonymous access to the Entire Website. Two times we have observed that once after a content deployment the The Anonymous setting gets reverted back to nothing, so we need to login to the Prod site and enable anonymous again. which i dont know why its happening?

We know the reason why its happening when we create a new site in staging environment and when we do an incremental deployment this happens.

Can somebody let me know how to solve this

Thanks in Advance


share|improve this question
Are you using custom site definitions for the sites? – Bernd Rickenberg Aug 9 '11 at 23:15
can you explain how the content deployment is done? can you try making your staging environment to allow anonymous and do a content deployment and check whats happening? – Deepu Nair Nov 8 '11 at 3:19

We figured out this problem. This happens when you create a new site in Stage . In our onet.xml when we provision a site a default page is created (default.aspx). and we have made it as draft. So if we do not publish this page manually and do the ContentDeployment . It will lock the sites. Then we need to explicitly enable anonymous access

share|improve this answer

Not sure about your problem specifically. Not sure how you are performing your deployment. I will say that if the SPWebApplicaiton or the SPWebService is unprovisioned and reprovisioned all custom IIS settings are lost.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.