Excellent! We just ran into an issue with an off-site copy activating unexpectedly, and I was toying with the idea of writing a wrapper myself - now I won't have to!
Thanks, Tim!
John
10 Apr 2013 9:55 PM
#
Great Article for us Exchange On-Premises customers.
Thanks ;-) will use the .ps1 very soon
Patel
11 Apr 2013 2:12 AM
#
Very good Article for us Exchange On-Premises customers.
I am seeing good Exchange On-Premises Articles these days in Exchange Team Blog ;-)
11 Apr 2013 3:43 PM
#
Wonderful! I'm going to be deploying a lagged DB server and one DB at our DR site in the next few months, so this will become part of my normal DB server maintenance.
Frank T
11 Apr 2013 4:17 PM
#
Nice, but could really be built into the product
ie another possible value like DatabaseCopyAutoActivationPolicy: AlwaysBlocked, that the scripts will not change. And something similar at the database level (would be trickier because that one is true/false)
JLong
20 Apr 2013 4:35 PM
#
Just thought i'd point out the syntax above is wrong.
The correct syntax (as noted in the .ps1 notes) is:
maintenanceWrapper.ps1 –server <SERVERNAME> –action START
maintenanceWrapper.ps1 –server <SERVERNAME> –action STOP
Thanks for the script -- works great!