What is best practice technique to prevent users from writing to MOSS 2007 farm? RRS feed

  • Question

  • Platform: 32 bit MOSS 2007 enterprise, service pack 3

    We are preparing to move to SP 2010. I want to put the farm in a state where users can read their data, but not start workflows, upload or modify docs, delete things, etc. during the process of getting backups of the databases and then getting the 2010 farm up and running.

    I know that sql server has the ability to make the databases read only, central admin has the quiesce farm option, central admin has site collection quotas and locks which can lock the status of the site as read-only, with stsadm -o setsitelock -url {site_collection_url}<site_collection_url>-lock readonly you can lock the site collections.</site_collection_url>

    Are there other methods?

    Is there a preference of one over the others?

    In an ideal world, the SP 2007 will stay in readonly until the box is shut down; however, during the first few days of the conversion, the option of falling back in case of emergency will be considered... 

    Tuesday, November 5, 2013 8:21 PM

All replies

  • Locking it in Site collection Quotas and locks would be the ideal way,

    1. as it provides a GUI to manage the change in central administration console
    2. It avoids a trip to DB server and we are not touching the DB for changes

    Aravind http://aravindrises.blogspot.com

    Tuesday, November 5, 2013 8:30 PM
  • So let me ask this then - there are 1500 or so site collections on this farm - if I want to shut people out of the farm, then I have to go through and lock each of them?
    Wednesday, November 6, 2013 12:07 PM
  • If you've really many site collections then you can make use of powershell script to do the same.

    Aravind http://aravindrises.blogspot.com

    Wednesday, November 6, 2013 4:54 PM