I often get a client’s request to change properties, for example, the version history parameter in all document libraries on all existing farm sites.
So far, the best solution I could think of is a Powershell script, test the script before I run it, and then pray that I don't forget something critical. Is there a better and safer way?
My personal “setup workflow” is as follows:
, " script prod-", "" , SharePoint. SharePoint Feature Solution .
, PowerShell / .
EDIT: , , . , , . , DR, SSP , config db, - .config IIS.
, - , PowerShell . , , ( , - , ).
, PowerShell script, , -WhatIf -Confirm , ( , ..).
-WhatIf : , , , . , .
-Confirm: , : " , xyz".
-WhatIf, , Start-Transcript , , , , , , , .
First take a backup of the content, then run the script.
Backup through stsadm or database.
Not working for any central admin changes.
Source: https://habr.com/ru/post/1702558/More articles:Ruby way to create n-ary wood - ruby | fooobar.comDevelopment in a hostile environment - development-environmentPHP Accelerated Download Method? - phpHow do you map a component that is also a primary key in NHibernate hbm xml (or in a map of the fluent-nhibernate class)? - c #Internal version control for iphone applications - iphoneIn Inheritance: can I override base class data elements? - c ++Resources for learning VBA if you are already familiar with java and ruby - vbaResources for exploring SAS if you are already familiar with R - rHow to find the length of the mantissa on a particular machine? - rounding-errorhow to show a "working" indicator when inserting a large number of dom elements - javascriptAll Articles