Links for Exchange Info and Procedures

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 AntiSpamFilteringEnabled
  http://community.office365.com/en-us/forums/613/p/151551/434560.aspx
   
• Upgrade from Exchange 2007 to Exchange 2013
  http://technet.microsoft.com/en-us/library/jj898581%28v=exchg.150%29.aspx
   
• Exchange 2010 Vs Exchange 2013
  http://www.itbigbang.com/exchange-2010-vs-exchange-2013/
   
• Step by Step Exchnge 2007 to 2013 migration
  http://blogs.technet.com/b/meamcs/archive/2013/07/25/part-1-step-by-step-exchange-2007-to-2013-migration.aspx

Reg Update to add Powershell to Plugable Protocol Handlers.

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 to Eriq VanBibber for the original post.

Exchange SSL Certs and DNS configurtion(s)

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 create an unnamed entry ("@") pointing to your internal CAS server(s). 

This way, it does not interfere with all of your existing DNS records for the "domain.com" zone, such as www, etc. 

So now, with this configuration, all that you need for a 3rd party SSL Cert is the "domain.com" name.  

Additional Reference:

• Internal DNS and Exchange Autodiscoverhttp://acbrownit.wordpress.com/2012/12/20/internal-dns-and-exchange-autodiscover/

Public Folder Migration Exchange 2003 to 2010

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
• ... 

Office 365 - How to connect Powershell to Office 365 Service

How to connect Powershell to the Office365 Server, so that you can administer a Hybrid environment.

Issue the following commands:

• Set-ExecutionPolicy Unrestricted
• $cred = Get-Credential
  (Enter your Tenant Login to Office365)
• $Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://ps.outlook.com/powershell/ -Credential $Cred -Authentication Basic -AllowRedirection
  (Note: You may get a redirection as this command is executed:
  WARNING: Your connection has been redirected to the following URI:
  "https://pod51042psh.outlook.com/powershell-liveid?PSVersion=3.0 ")
• Import-PSSession $Session

Before issuing this command, following are the Modules that were loaded:
PS>Get-Module
ModuleType Name                                ExportedCommands
---------- ----                                ----------------
Manifest   Microsoft.PowerShell.Management     {Add-Computer, Add-Content, Cheomputer, Clear-Content...}
Manifest   MSOnline                            {Add-MsolForeignGroupToRole, Add-MAdd-MsolRoleMember,...

After issuing a successful connection to the Office365 Service, you now have the following:
PS C:\Windows\system32> Get-Module
ModuleType Name                                ExportedCommands
---------- ----                                ----------------
Manifest   Microsoft.PowerShell.Management     {Add-Computer, Add-Content, Checkpoint-Co...}
Manifest   Microsoft.PowerShell.Security       {ConvertFrom-SecureString, ConvertTo-Secu...
Manifest   Microsoft.PowerShell.Utility        {Add-Member, Add-Type, Clear-Variable, Compare-Object...}
Manifest   MSOnline                            {Add-MsolForeignGroupToRole, Add-MsolGroupMember, ...
Script     tmp_fhnxmnma.xiw                    {Add-AvailabilityAddressSpace, Add-Distribution...

This module adds 469 new commands.

http://help.outlook.com/en-us/140/cc952755.aspx

Outlook: When I send an email message it doesn't leave my outbox

Outlook: When I send an email message it doesn't leave my outbox

I ran into this problem today and was baffled until I found this link:

http://office.microsoft.com/en-ca/outlook-help/when-i-send-an-e-mail-message-it-doesn-t-leave-my-outbox-HA001187988.aspx
The above link says that it describes Outlook 2003, but the information applies to my Outlook 2010.

The symptoms are that in Outlook 2010, when I send a message, it goes to the outbox but is not in italics and does not get sent. 
I can forward that same message and the copy goes just fine.  Also, this is a global problem on several Outlook profiles, not just one.

The culprit turns out to be an Outlook Addin from Apple.  I apparently had installed the application called iCloud on my laptop, and ever since then this problem existed.  

I was able to simply disable this Addin and the problem was resolved.

Enabling feature .Net Framework 3.5 and Framework 2.0 on Windows 2012

Enabling feature .Net Framework 3.5 and Framework 2.0 on Windows 2012
Problem: The .Net Framework 3.5 and Framework 2.0 feature is initially not installed on a new windows 2012 server.  It has an installation status of "removed"

[ ] .NET Framework 3.5 Features                         NET-Framework-Features         Available
    [ ] .NET Framework 3.5 (includes .NET 2.0 and 3.0)  NET-Framework-Core               Removed
    [ ] HTTP Activation                                 NET-HTTP-Activation            Available
    [ ] Non-HTTP Activation                             NET-Non-HTTP-Activ             Available
[X] .NET Framework 4.5 Features                         NET-Framework-45-Fea...        Installed
    [X] .NET Framework 4.5                              NET-Framework-45-Core          Installed
    [ ] ASP.NET 4.5                                     NET-Framework-45-ASPNET        Available

I am still trying to figure out WHY this is not "Available", but there appears to be 2 ways to install the NET-Framework-Core
 
Method 1:
 
Open Run with administrator privilege, and type this at the command :
dism.exe /online /enable-feature /all /featurename:NetFX3 /Source:D:\sources\sxs /LimitAccess

 Method 2: using GUI

1. You have to insert Windows Server 2012 DVD or iso to D drive.
2. Open Add Roles and Features Wizard
3. Select .NET Framework 3.5 Features and then click next,
4. Select Specify an alternate source path link in the Confirm installation selections screen.
5. Path: D:\Sources\SxS and then click OK.
6. Finally click Install button.
 
 Method 2: using PowerShell

 PS >Install-WindowsFeature NET-Framework-Features,NET-Framework-Core -source d:\Sources\SxS