In which Lync forces me to dig into the Exchange world again…..
I got an excellent question as a followup to my post breaking down the exchucutil.ps1 script in excruciating detail.
The questions by user “soder” basically asked if the –verify switch was still valid in the Exchange 2010/2013 versions of the script. In short – no. In long – mostly no.
Looking at the script, the following is seen on line 10:
param($Forest = $null,[Switch]$Verify)
This means that the script is looking for a command line parameter named -Verify. Running the script with the -Verify parameter runs the script in “verify mode”. (The [Switch] construct basically means that if -verify is present, set the $verify variable to $True, else set it to $false).
However, something strange happens a few lines down – line 21 to be exact:
$Verify = $false;
This sets $Verify to $false NO MATTER WHAT you set on the command line. So effectively, $Verify is disabled.
I don’t have any idea why this is done but there must be a good reason. I don’t want to speculate.
However, if you want to run a verify pass anyway, comment out line 21. Then run exchucutil.ps1 -verify. I ran it in my lab and I got a list dumping out the permissions and not attempting to actually make changes.
Microsoft effectively removed the verify permissions. (Well, it could be an oversight. It probably is….)
In summation, as of at least Exchange 2013 (and maybe 2010) verify does not officially work anymore.