Pat Spencer

Exchange 2013 Info  Exchange 2013 Build Numbers and Release Dates http://technet.microsoft.com/en-us/library/hh135098%28v=exchg.150%29.aspx   Display Current Build (including CU) Display HKLM\SOFTWARE\Microsoft\CurrentVersion\Uninstall\Microsoft Exchange V15\DisplayName Example "Microsoft Exchange Server 2013 Cumulative Update 2" Client connectivity in an exchange 2013 coexistence environment http://blogs.technet.com/b/exchange/archive/2014/03/12/client-connectivity-in-an-exchange-2013-coexistence-environment.aspx Some CAS Transistion exxamples http://msexchangeguru.com/2012/10/23/e2k7-to-e2010-cas-transition/ Exchange 2013 Procedures: Exchange 2010 and below Build Numbers http://social.technet.microsoft.com/wiki/contents/articles/240.exchange-server-and-update-rollups-build-numbers.aspx Installing Cumulative Updates for Exchange Server 2013 http://exchangeserverpro.com/exchange-2013-installing-cumulative-updates/   Hybrid configuration wizard fails on parameter AntiSpamFilte

With the following registry additions, you can create a new URL protocol handler for PowerShell: This allows me to do the following: Start -> Run: ps:3+5 Start -> Run: ps:get-process Start -> Run: ps: A new powershell window opens, parses and executes the command and leave the window open. Import the following to set it up: Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Classes\PS] @=" URL:Powershell Protocol" "URL Protocol"="" [HKEY_LOCAL_MACHINE\SOFTWARE\Classes\PS\DefaultIcon] @="\"C:\\WINDOWS\\system32\\WindowsPowerShell\\v1.0\\powershell.exe\",1" [HKEY_LOCAL_MACHINE\SOFTWARE\Classes\PS\shell] [HKEY_LOCAL_MACHINE\SOFTWARE\Classes\PS\shell\open] [HKEY_LOCAL_MACHINE\SOFTWARE\Classes\PS\shell\open\command] @="\"C:\\WINDOWS\\system32\\WindowsPowerShell\\v1.0\\powershell.exe\" -NoLogo -NoExit -command $ExecutionContext.InvokeCommand.InvokeScript('%1'.Substring(3))" Special thanks

This article discusses how to deal with the fact that you can no longer get a 3rd party SSL Certificate for an internal domain. The issue is that 3rd party Certs will not allow non-verifiable Certs after Oct 2016.  Essentially, that means that you should now configure your Exchange environment (2007/2010/2013) to not depend on Certs for internal names. The solution is too simple.  Just configure your DNS server to implement a "Split-DNS-Horizon". Note that this also works perfectly for auto-configuring your Outlook clients, regardless of whether they are connected internally or externally. For this example, lets assume that your internal domain is domain.local, and that your email domain is domain.com The easiest and simplest trick is to configure an entry in your internal DNS servers, to point autodiscover.domain.com to the internal IP address of your CAS server. The best way to do this is to create a new DNS Zone with the name "autodiscover.domain.com", and then c

Public Folder Migration Exchange 2003 to 2010 Replicate Public Folders to 2010 Server. http://www.petenetlive.com/KB/Article/0000426.htm FAQ on Migrating Public Folders to 2010 http://itmel.wordpress.com/2012/12/01/microsoft-exchange-2013-and-public-folders/   Also, Form 2007/2010 to 2013, here are the Microsoft tools: Migrate Public Folders to Exchange 2013 From Previous Versions http://technet.microsoft.com/en-us/library/jj150486(v=exchg.150).aspx ...