A Quick blog on how to execute an Exchange PowerShell script (.ps1 extension) from a command prompt.
A .ps1 cannot be executed from a Command prompt. to execute it one needs to use a PowerShell shell. Further if this script calls any exchange cmdlet, it would require to be executed in an Exchange Management Shell.
The following command does all three in one line. i.e. run the script from c:\script\script.ps1 ( which is an exchange script ) from a command prompt.
C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe -psconsolefile "C:\Program Files\Microsoft\Exchange Server\V14\Bin\exshell.psc1" -file "C:\script\script.ps1"
*Features
~95.5% reduction in IOPS
Exchange 2013 is capable of being deployed in a multi-site worldwide architecture with a single namespace. ( using multiple technologies )
Auto re-seed to spare disk. ( but needs operational maturity )
*Good to know
CAS is now a protocol proxy only. (2 layers V/S 5 layers)
No longer supports MAPI Clients ( only outlook anywhere )
No MAPI on CAS only RPC-over-HTTP
ECP is now EAC
Notification to admin when certificate is expiring ( EAC )
Maximum DB per server; Enterprise Edition- 50, Standard Edition - 5
one thread per DB
Hard block on 2003 to 2013 migration. (even cross forest )
New server gets into maintenance mode once it is installed
Quota notification e-mail is generated during users login ( V/S every day at midnight in Exchange 2010 )