Friday, May 22, 2015

Export All SMTP Addresses & Exchange 2010

If you would like to export all SMTP proxy addresses into CSV file to be used for your discovery or preparation for office 365 migration , here is simple PS script to complete the task.

Here is an example of user with three SMTP proxy address, we will capture all SMTP addresses for all users and provide output to CSV file.


Get-Recipient -Identity Aki.Armstrong | Select Name -ExpandProperty EmailAddresses



Now we want to capture all the SMTP proxy Addresses

Get-Recipient -Identity Aki.Armstrong | Select Name -ExpandProperty EmailAddresses | select Name,SmtpAddress


Now we need to add ( make sure you have the Temp directory under C drive or change the output as you wish to make it fit into your particular scenario.

Export-Csv C:\temp\All_SMTP_Proxy_Addresses_List.csv

Last thing is to make sure we add  -ResultSize Unlimited  ( this will be required if the query runs against more than 1000K recipients)

Get-Recipient -ResultSize Unlimited  -Identity Aki.Armstrong | Select Name -ExpandProperty EmailAddresses | select Name,SmtpAddress | export-csvC:\temp\All_SMTP_Proxy_Addresses_List.csv

the CSV file will look similar to this one


If you like to collect more data, you can also use  Get-member to see all available properties and adjust your output per your needs from available property list



Get-Recipient -Identity Aki.Armstrong | Select-Object Name,EmailAddresses,ServerName



Oz Casey, Dedeal  ( MVP North America)
MCSE 2003, M+, S+, MCDST
Security+, Project +, Server + (Blog) (Blog)


Tuesday, May 12, 2015

Exchange 2013 unattended Installation step by step documentation

We will use unattended installation to install Exchange 2013 server into existing Exchange 2010 SMTP organization. These simple steps can easily reduce the time it takes to install Exchange 2013 servers into your environment.


Exchange 2013 will be installed into existing Exchange 2010 SMTP organization environment.

Exchange 2013 Calculator and proper sizing for the environment:

Sizing for Exchange 2013 has been completed per Microsoft best practices. This is where you do not want to make any mistakes and hopefully invested a good month of time to complete the correct build per the given environment.

Active Directory Schema has been updated, Upper schema range has been updated:

Environments  require change control process , and process oriented ( regulated) it is best to perform schema changes ahead of time, rather performing with first Exchange 2013 server installation. My simple reasoning is, schema changes are critical, and one way street. Changes to schema and .DIT database should be treated as a major task. Performing schema changes ahead of time and let it baked also provides proof of concept to your client.

Perform following task from Windows 2012 R2 Server (All Exchange 2013 Servers)

  • Log into Windows 2012 R2 Server via RDP
  • Use your administrator account and privileges
  • Open Windows PowerShell. ( With administrator privileges)
  • Run the following command to install the required Windows components

You can copy and paste this into PowerShell:

Install-WindowsFeature AS-HTTP-Activation, Desktop-Experience, NET-Framework-45-Features, RPC-over-HTTP-proxy, RSAT-Clustering, RSAT-Clustering-CmdInterface, RSAT-Clustering-Mgmt, RSAT-Clustering-PowerShell, Web-Mgmt-Console, WAS-Process-Model, Web-Asp-Net45, Web-Basic-Auth, Web-Client-Auth, Web-Digest-Auth, Web-Dir-Browsing, Web-Dyn-Compression, Web-Http-Errors, Web-Http-Logging, Web-Http-Redirect, Web-Http-Tracing, Web-ISAPI-Ext, Web-ISAPI-Filter, Web-Lgcy-Mgmt-Console, Web-Metabase, Web-Mgmt-Console, Web-Mgmt-Service, Web-Net-Ext45, Web-Request-Monitor, Web-Server, Web-Stat-Compression, Web-Static-Content, Web-Windows-Auth, Web-WMI, Windows-Identity-Foundation

After you've installed the operating system roles and features, install the following software in the order shown:

Make sure the server has been added to domain , it has static IP address and it has been configured to be in compliance with your environment.( All security patches and other required software has installed and configured)

Make sure you have obtained all required approvals and satisfied your change management process and scheduled this installation in the LAB (production like environment) first and after successful implementation you may deploy same solution in the production environment.

Test before you do it in the production, catch any issues may raise up and document the fixes as you plan production installation.

LAB preparation: ( Please make sure this fits into your needs)

Widows Server Enterprise Edition R2 is installed the drive and LUN assignment are present as follows:

  • C: 120 GIG (OS Drive & Exchange binaries)
  • E: 20 TB (LUN)
  • D: CD-ROM

Copy and save below simple code into notepad and re-name the file as “Install.ps1” note: change any of the parameters as you wish.


# Install Exchange 2013 Server Unattended Install File

# Prepared by Oz Casey, Dedeal


# Roles /m:install /r:C,M

# Logfolderpath E:\Logs\DB1

# Dbfilepath E:\DatabaseFiles\DB1.edb

# Accept LA IAcceptExchangeServerLicenseTerm


D:\setup /m:install /r:C,M /TargetDir:"C:\Program Files\Microsoft\Exchange\V15"'/Dbfilepath:E:\DatabaseFiles\DB1.edb /Logfolderpath:E:\Logs\DB1’ /IAcceptExchangeServerLicenseTerms




Open PS command prompt and execute the PS script to kick off the installation.





Simple and easy now you can deploy more servers quickly and easy by following these steps listed in this article.


Oz Casey, Dedeal  ( MVP North America)
MCSE 2003, M+, S+, MCDST
Security+, Project +, Server + (Blog) (Blog)


Monday, May 11, 2015

Exchange 2016 Supported Scenarios

Exchange 2016 and its futures announced at ignite 2015. Many exciting futures are on the way. Here is summary of topology requirements and few of the highlights, what has changed with Exchange Server 2016.

  • Single Role = Mailbox Server Role ( Prior to Exchange 2016, multi-role deployments were MS best practices, With E16 , there is no choice but single role (-:
  • Edge Role will be released with RTM release.
  • CAS Server role has been transitioned into Client Access proxy , service components. At this point all server roles collapse into single Mailbox Server role.
  • DAG no longer requires administrative access point. Only two operation systems are required Windows 2012 and Windows 10 Server.
  • Mailbox Connectivity the protocol instance is always local to the active database copy. Once the request reaches to correct mail Server all required connectivity stays on that server
  • Rendering data will occur on the Server which hosts the active mailbox, OWA clients etc.
  • Creating
  • Clients wont connect directly to MBX role, all connectivity will go trough Client Access Service located on the MBX Server. Entire CAS server role has been moved into  CAS Service
  • Maximum 16 Mailbox Servers Per DAG
  • 100 database copies/Server
  • Due to recent architectural changes done, Database failovers are 33% faster compared to Exchange 2013. How passive database copies are accessed is changed in Exchange 2016.




Oz Casey, Dedeal  ( MVP North America)
MCSE 2003, M+, S+, MCDST
Security+, Project +, Server + (Blog) (Blog)


Sunday, May 3, 2015

Exchange 2016 and Future

Ignite is going alive real soon less than 17hr as I write this blog. Those of you who are attending will be getting tons of rich content and meet with Exchange 2016 at ignite.

What we should expect from the new release of Exchange 2016. As you might have already noticed from  the IT evolving business, the push for cloud world is increasing each year and one way or other many businesses are moving into cloud space. At the least hybrid configuration is fairly common among agencies.

Few highlights provided by MS Exchange team,

To highlight a few examples:

  • A new approach to document collaboration that makes it easy to send links and collaborate without versioning issues of attachments
  • Faster and more intelligent search, to help users quickly find what they need in their mailboxes and calendars
  • Significant improvements to eDiscovery search performance and reliability
  • Better extensibility, including new REST-based APIs for Mail, Calendar, and Contacts that simplify web and mobile development

If we consider how much Microsoft has invested to Cloud and its surrounding technologies and infrastructure , it is very easy to predict or make educated guess that only online version of most major applications will continue to grow and get better, while on premises versions might not offer all of the futures.

The changes are inevitable , adapting these changes for IT Pros will occur one way or other. On premises version of  major applications might be lacking from future development unless the businesses start investing their own infrastructure to support these application and their managed environment.Of course all these are assumptions with what I have been seeing over few years.

I will come back and update this article especially with improvement related to Exchange 2016 on premises and some of the Office 365 highlights. Office 365 has evolved over the years and now it is providing supper reasonable solid messaging platform to many businesses. Extending Office 365 to Government and its related agencies seems to be also expending, although Government agencies are very slow to adapt these IT changes.


Advantage of office 365 are pretty obvious. The new future releases with office 365 very easy to adopt in general, less to manage, less to worry.

Looking forward for ignite news for Exchange 2016 both on premises and Office 365 platforms.

Oz Casey, Dedeal  ( MVP North America)
MCSE 2003, M+, S+, MCDST
Security+, Project +, Server + (Blog) (Blog)