A Complete Guide to PST Files – How To Manage?

Introduction of PST files

PST files are widely used in many organizations and often contain business-critical or sensitive data, but they are frequently completely unmanaged and can present a significant risk to the organization as well as causing ongoing issues for IT support teams.In this article, we take a look at these files and the problems they can cause. We then discuss the options for addressing these problems and concludes with a summary of the benefits an organization can realize by managing PST files.

What Are PST Files?

An unfamiliar term to those outside of IT, they are often known as Outlook Archives or Personal Archives and are typically created by Outlook when the “Auto Archive” function is enabled. PST is actually an acronym for “Personal Storage Table” but that term is not often used.The auto-archive function in Outlook allows users to bypass the mailbox quota limits which IT departments may enforce as a result of size limitations with their central Exchange server. This feature was turned on by default in Outlook 2003 and 2007 and generated PSTs as container files to store email locally for the user.Where Are They Located? PST files can be located almost anywhere. By default, Outlook will create them on a user’s desktop or laptop, however, that does not stop them being located on corporate servers, removable media such as USB and flash drives etc., or even home PCs.

Are They Secure?

This depends on a number of factors, but normally they are not.PST files are highly portable, as they can be disconnected from Outlook and copied or moved to another
Outlook client with ease and they are also widely used as a great way of moving email data between people and/or organizations quickly. They can be password protected, although a simple search on the internet will find any number of programs that can crack these passwords.Are They Reliable? PSTs are notoriously unreliable, as they were never designed to hold the amount of email data they often do today. Users keep pouring more emails into them, blissfully unaware of the risk this poses to their data, and
10 or 15% of an IT department’s daily helpdesk calls can be taken up with looking after these files.Due to their size, they are also susceptible to internal corruption if they are located on a network share or accessed over a network, and Microsoft specifically advises against accessing them this way.

Are They Always Available?

The perception for a lot of users is yes, but this is not always the case, as Outlook must have access to the location where the PST file is stored. This is fine for office-based users who have the same access to either local or network storage, however, if the user has the ability to work from different desktops or locations they may not be able to always access their PSTs. Also, if the user uses Outlook Web Access (OWA) then they cannot gain access to their files.PST files can easily be disconnected by users from their Outlook profile, either inadvertently via a failure such as a power outage or PC crash, or by the user ‘closing’ them. For some users, this is standard practice when
they are managing a number of PST files, and these PSTs can be reopened at any time as long as the user knows their location. But for most users, once the PST is ‘closed’ it is either forgotten about or they cannot find it again, thereby creating an ‘orphaned’ PST. Orphaned PST files can still contain valuable business information that may need to be preserved and made available.

Are They Backed Up?

This depends on their location and how the IT department is managing them. If they are located on desktops and laptops there is a high probability they fall outside the corporate backup strategy, and are therefore not protected. If however they are located on network shares, then the chances are they are being backed up.However, this in itself brings a set of new challenges for the IT department.

Do Companies Still Use Them?

Yes – as many companies will copy a former employee’s mailbox to a PST as a method of retention. These practices can change from time to time or be overlooked, so consistency may be a problem. Companies also frequently use them for passing large amounts of email data around between locations or even between organizations.

Do Employees Still Use Them?

Yes – although, there is a high chance they don’t know it. Many workers favour the “Auto Archive” as a way to organize and keep older emails without understanding the risks, particularly if their mailbox is restricted by quota limits.

Do PSTs Fall Under Compliance and Legal Hold Requirements?

The PST file itself does not, as it is merely a container, but the emails and attachments that are stored in the file do. Since most legal discovery occurs sometime after the alleged incident, not knowing the location or indeed the owner of PSTs can make legal hold and compliance problematic.

Which IT Projects Can PST Files Impact?

 

Office 365 Migration

Where organizations are looking to move the overhead of their office applications to Microsoft’s online platform, PST files should be considered either as part of that migration or certainly straight after.Consolidating all email data into the online Exchange environment will not only enhance the end user experience and productivity but also ensure that any legacy email data is protected.

Desktop Refresh

When considering a refresh to either new hardware or a virtual environment the impact of PST files should not be underestimated. They can be located anywhere in the desktop environment, and end users are likely to lose access to them if they are not identified and handled correctly. Without careful consideration, a large
amount of valuable business data could be at risk of being lost.

eDiscovery and eDisclosure

Situations may arise where an organization needs to identify all historical information (including emails) that is relevant to a particular issue or request. In this situation, the email contained within PST files is difficult to identify and retrieve because the location of the files may not be known or their contents are available only to their end-user.
Corporate Compliance Best practice is often jeopardized by PST files because they typically contain emails which should be managed according to corporate compliance policies, but have fallen outside the scope due to their location. It is important to note that Defensible Compliance dictates that all known sources need to have a consistent policy applied to them.

How Big is the PST Problem?

Across the organizations we work with, we see an average of between two and four PST files per active mailbox, ranging in size from a couple of Megabytes up to many Gigabytes.A typical PST file may contain 10,000 individual messages with attachments, which normally represents around 1 GB of data. In storage terms, this doesn’t sound like a lot, but multiply this by the number of mailboxes and triple that figure (with the average number of PSTs per mailbox being three) and the scale of the problem can be seen.Consider too that these emails may contain business-critical data such as supplier contracts, customer orders and research data, so the size of PST files is not always the biggest problem. In practice, most enterprises have thousands of PSTs littered throughout their infrastructure going unseen and unprotected.

How Do We Find Out if We Have a PST Problem?

The IT department will have a good idea if PST files exist with their organization, but the scale of the problem will be less clear.An initial search will certainly give an indication of the problem, and this may be enough, but in our experience, more information is required. For example, you will need to consider the actual data size compared to the
on-disk size. You will also need to identify who owns the data in each PST file, which is especially important for all those lost or orphaned PSTs.Once you have this information, careful consideration will need to be given as to what to do with each PST file.

Can IT Departments Manage PST Files?

Yes, with the right strategy and tools – although this does not mean that they are currently being managed.For a long time, PST files have been the thorn in the side of IT departments. PSTs have served a purpose for many years for both the user and the IT department with either the associated risks to the business being invisible or a blind eye being turned to the risks being taken.IT administrators have several options available to them, including:

  • Migrating the data back into Exchange or Office 365, then deleting them
  • Moving them all to a central network server
  • Ingesting the data into a third party archiving solution, then deleting them
  • Simply living with the existence of PST files

Why Can’t Users Manage Their Own PST Files?

By their very nature, PSTs are created by the end-user, so it is therefore fair to say that by default the user has ended up managing them, but with varying degrees of success. The more alert user will have made ad-hoc copies of their PSTs on network shares or removable disks, which provides them with some level of backup or protection. But apart from the potential security risk, this presents, it can also lead to data duplication.So should users manage their PST files? The simple answer is no, they should not be burdened with ensuring business-critical data is protected. This responsibility falls at the door of IT departments who are better equipped to do so.Indiscriminate deletion of information could mean the organization falls foul of various laws if data pertaining to litigation or investigation is involved, resulting in fines and bad publicity.

What Tools Are Available for Managing PST Files?

A number of archiving solutions include embedded PST management tools, however, these have limited functionality and offer varying degrees of success.
Organizations should consider the value of stand-alone PST Management tools. These range from Microsoft’s free PST Capture tool to enterprise-class solutions such as Barracuda’s own PST Enterprise, which can meet the demands of more complex PST migration projects.

Microsoft’s Tool is Free – Is That Not Enough?

Microsoft has attempted to solve the problem with their PST Capture application, which addresses the challenges of legacy PST files by ingesting the data from these files back into the user’s mailbox. The problem with this is that PST Capture doesn’t scale to the typical size of PST problem that many larger companies face.The Microsoft PST Capture tool is also only a partial solution and requires a great deal of manual intervention.In particular, it doesn’t cover the work involved in finding and organizing PSTs or deleting PSTs after they have been processed, so unless you are a company with less than 100 mailboxes, deployment of a third party solution such as PST Enterprise is advised.

What Features Should a PST Management Tool Provide?

Key features should include:

  1. Discovery of PST files wherever they exist across the organization, whether this is on local or network drives, or even on removable storage.
  2. Determining and assigning an owner for each PST file.
  3. Removing passwords from protected files.
  4. Migrating data selectively, based on the file contents or the age of the data.
  5. Providing a choice of target locations to move data to, such as to the primary or archive mailbox, to a network server, or dedicated servers to a third-party archive solution.
  6. Deleting files once they have been processed.

All these features should include a high degree of automation. In particular, locating PSTs on remote desktops and laptops is a time-consuming task, so the tool should automate this process without involving or impacting end users.

Can’t PST Files Just be Deleted?

Many PST files are simply collections of old and obsolete emails which are candidates for deletion. However, the PST file properties not only restrict access but also fail to provide details on what the file actually contains or how old the emails within it are.An organization must consider whether it is prepared to live with the consequences of deleting these files without understanding the type and value of the information contained within them. In particular, if it has a corporate retention policy then it should ensure that it complies with this at an individual item level for each email within each PST file.

Which of Those Options is Best?

The choice will depend on the three key factors of risk, performance and cost:

pst files

These decisions are individual to each company, and will normally fall within the overall company retention and discovery requirements that facilitate governance and best practice.The key is to have a consistent, automated, scalable practice that solves the problem, backed up by an audit trail of the activity.

Will the PST Problem Ever Go Away?

The latest versions of Exchange have better capacity management, and the need for PSTs has been negated with the addition of in-place archiving. There is also the option of adopting third-party archiving solutions, which allow organizations to better streamline and manage their email environments.It is still important to consider historical PSTs and the data that resides within them. Ultimately, removing PST files will have a positive effect on all downstream processes, as well as eliminating much of the legal risk
and uncertainty in unmanaged containers of email data sitting on your corporate servers and on the end user machines.The emergence of big data, and the realization by enterprises that to retain a competitive edge they need to be able to analyze and realize value from all their data, makes PST management a business driver and not just an IT requirement

Conclusion – The Benefits of Managing PST Files

  1. Reduce Risk
  2. Eliminate risks associated with unmanaged email data.
  3. Protect against end user and intellectual property data loss.
  4. Implement robust data retention and defensible deletion policies.
  5. Ensure compliance with Freedom of Information, Data Protection and other regulations.
  6. Improve Performance
  7. Reduce backup and restore times for business-critical file servers.
  8. Quicker retrieval of centrally stored information.
  9. Remove obstacles for projects such as hardware upgrades, BYOD, VDI or Office 365 migration.
  10. Reduce Costs
  11. Reduce IT support overheads.
  12. Streamline processes for eDiscovery and other disclosure requests.

How to Secure Microsoft Exchange Server In Post-TMG World

Introduction – How to Secure Microsoft Exchange Server In Post-TMG World

For many organizations, Microsoft’s Threat Management Gateway was a critical reverse-proxy security solution for Microsoft Exchange and SharePoint publishing. TMG provided a number of security benefits for Microsoft applications including:

  • Application security
  • Network security
  • Authentication proxy
  • Secure remote access

The Microsoft announcement of TMG’s end-of-sale in 2012 and the end-of-support in 2015 left organizations without a long-term solution for securing their existing Exchange and SharePoint deployments.

Barracuda Solutions are Ideal for Microsoft TMG Customers

Barracuda Networks has a long history of security expertise and experience working with Exchange and SharePoint deployments, making us the ideal partner for customers needing to migrate from TMG. Our application security, anti-malware, and anti-spam capabilities have secured more than tens of thousands of deployments worldwide. In addition, our solutions are certified by Microsoft as recommending hardware load balancing and application delivery solutions.

Secure Application Delivery for Microsoft Exchange

Publishing Exchange Server takes many forms, ranging from Exchange Server Support ,protecting the server infrastructure and safeguarding e-mail traffic, to providing secure access via rich and thin clients. Barracuda supports a number of technological capabilities that support secure access and high performance. In addition, they are designed for easy installation and administration. Barracuda’s Application Delivery Controller deployed as a reverse proxy provides a critical security layer for Exchange Publishing. It segments external access from internal resources, providing a security buffer that protects Exchange servers from application and network threats. Barracuda ADCs are certified by Microsoft as a preferred hardware load balancers for scaling and accelerating exchange deployments.

Exchange Server support with Barracuda

Secure Application Delivery of Exchange ServersThe Barracuda Load Balancer ADC provides a complete solution for Exchange. It has sophisticated load balancing, session management, and server health checks to provide robust scalability and high availability for Exchange. As a reverse proxy, it also provides a layer of security. All requests are terminated and inspected before being sent to the backend servers.
Secure Outlook Web Access (OWA)Barracuda’s ADC has pre-built templates designed specifically for OWA. This allows organizations to provide strong plug-and-play security against SQL Injections (SQLi), Cross Site Scripting (XSS), OWASP Top 10 attacks, DDoS, and other attacks against the Exchange infrastructure.
Secure ActiveSyncBarracuda’s ADC provides secure ActiveSync access. It can provide secure session management and access control based on device and browser type. Additional capabilities like DDoS and brute-force protection ensure availability even in face of rate-based attacks.
Pre-AuthenticationBarracuda can also provide the ability to authenticate users and devices using a number of authentication methods like Active Directory, LDAP, and RADIUS. This allows administrators to offload the authentication process from their Exchange infrastructures and provide Single Sign-On (SSO) across their Microsoft applications.
SSL OffloadingBarracuda ADCs use high-performance hardware for SSL offloading.

About Medha Hosting.

Medha Hosting is the leading global Cloud, Managed hosting and managed IT services provider with award-winning platforms in USA, Europe and Asia. Medha Hosting has delivered enterprise-level hosting services to businesses of all sizes around the world since 2014 and still serve a growing base of customers. They rely heavily on our 100 percent uptime guarantee, unbeatable level of client service through our triumph Support Heroes, and with half-dozen data centres across five regions in Europe, US, and Asia. We have a tendency to integrate the industry’s best technology to supply you better of breed cloud hosting solutions, all backed by our triumph Support Heroes

We aim to be the choice managed IT services and hosting provider. We will attract the best employees, develop and deploy the best technology, and deliver the best products and services.

We are managing and ensuring smooth business continuity and data security of Windows Servers, Exchange Server, Share point servers, SQL server and other Microsoft Server Technologies. And also we work with various Linux server and applications.

We partnered with many industries leaders such as Microsoft, Barracuda AWS, IBM, HP, and many others.

To learn more about how Medha Hosting can protect and accelerate check our Microsoft Exchange Server Support.

About Barracuda Networks, Inc.

Protecting users, applications, and data for more than 150,000 organizations worldwide, Barracuda Networks has developed a global reputation as the go-to leader for powerful, easy-to-use affordable IT solutions. The company’s proven customer-centric business model focuses on delivering high value, subscription-based IT solutions for security and data protection. For additional information, please visit www.barracuda.com.

Installing Active Directory step by step on windows server 2012

Installing active directory step by step on windows server 2012

I am installing Active Directory on windows server 2012

First thing I need to do is set network interfaces configured.

The server will be act as DNS server field you can use local host address 127.0.0.0

It is recommended meaning full name “MDH2”

Now ready to start on the Active Directory install.

I can start DNS role install

To do this we need to start “Server Manager” it can open using shortcut on task bar > > Server Manager >> Then click on “Add roles and Features” .

C:\Users\R G\AppData\Local\Microsoft\Windows\INetCache\Content.Word\Untitle1d.png

Then “ADD Roles and Features Wizard” come, Click on next to continue

Next window default “Role-based or feature-based installation” click on next.

In below image window, we can select which server to install role. in our case it will be local. The default selection and click on next.

In the below image window give option to select the roles. select the “DNS Server” and click on checkbox.

In the blow image window. Click on next to continue

In the blow image windows Showing introduction of DNS role, Click on next to continue.

In the below image window it will Showing details about the selected features and click on “Install” then begin installation

Then it will begin the installation and we need to wait till it completes click on close

Now you can access DNS server using server manager >> tools >> DNS

C:\Users\R G\AppData\Local\Microsoft\Windows\INetCache\Content.Word\Untitled3.png

Now all thins ready for Active Directory installation .Click on server manager >> Add roles and Features.

C:\Users\R G\AppData\Local\Microsoft\Windows\INetCache\Content.Word\Untitle1d.png

In the below image just click on next

In the below image Default selection and click on next.

In the below image, I can select which server to install role. in our case it will be local. so, keep the default selection and click on next.

In the below image windows Showing options to select the “server Roles”.Select “Active Directory Domain Services”.

Then it will prompt window to indicate the additional feature installations related to selected role. click on “Add Features” to continue

Then in next window click on next to continue.

Next window click on next

In the below image window click on “install” to start thein stallatuion.

In the below image window it will begins the service install and we have to wait till it finish.Once it finish click on “close” to exit from the wizard. then next step is to reboot the server to complete the installation.

After that completes we need to start on the DC setup. to start that open the “Server Manager” and click Task flag. Then it Showing option as below picture. click on “promote this server to a Domain Controller” option .

C:\Users\R G\AppData\Local\Microsoft\Windows\INetCache\Content.Word\Untitled4.png

Then it starts the DCPROMO wizard. on the first window since its going to be new forest i have selected option “Add a new forest” and i typed the domain name “medhahosting.com.com” which i will be using on the forest. once fill the info click on “next” to continue.

In next window we can select the forest and domain functional levels. i will keep it default. then in domain controller capabilities its by default selected DNS server and Global Catalog as its first DC in the forest. then we need to defined password to use in DC recovery. click on next to continue.

In next window it will give following error but it can be ignore. click on next to continue.

In next window it ask for the netbios name. we can keep it default and click on next to continue.

In next window it give option to change file paths for AD database, log files and SYSVOL files. we can change the paths or keep them defaults. once changes are done click on next to continue.

In next window it gives description about the installation. click on next to continue.

In next window it will run system check and verify system is compatible with the selected installation. once test completes successfully click on install button to begin the installation. if its passes any critical errors those needs to be address before the installation begin.

then it will start the install and we need to wait till it finishes.

Once its complete the install it will automatically reboot the server.

Once server is rebooted log in to server using domain admin credentials.

user : medhahosting\Administrator

password : XXXXXXXXX

Once login, load the “Server manager” and click on “AD DS” option in right hand list. then select and right click as showed in screenshot to start with AD configuration.

Now we successfully completed with the DC setup on server 2012 R2. if you have any issue about the steps feel free to contact me on reddybr@medhahosting.com

Installing active directory step by step on windows server 2012

I am installing Active Directory on windows server 2012

First thing I need to do is set network interfaces configured.

The server will be act as DNS server field you can use local host address 127.0.0.0

It is recommended meaning full name “MDH2”

Now ready to start on the Active Directory install.

I can start DNS role install

To do this we need to start “Server Manager” it can open using shortcut on task bar > > Server Manager >> Then click on “Add roles and Features” .

C:\Users\R G\AppData\Local\Microsoft\Windows\INetCache\Content.Word\Untitle1d.png

Then “ADD Roles and Features Wizard” come, Click on next to continue

Next window default “Role-based or feature-based installation” click on next.

In below image window, we can select which server to install role. in our case it will be local. The default selection and click on next.

In the below image window give option to select the roles. select the “DNS Server” and click on checkbox.

In the blow image window. Click on next to continue

In the blow image windows Showing introduction of DNS role, Click on next to continue.

In the below image window it will Showing details about the selected features and click on “Install” then begin installation

Then it will begin the installation and we need to wait till it completes click on close

Now you can access DNS server using server manager >> tools >> DNS

C:\Users\R G\AppData\Local\Microsoft\Windows\INetCache\Content.Word\Untitled3.png

Now all thins ready for Active Directory installation .Click on server manager >> Add roles and Features.

C:\Users\R G\AppData\Local\Microsoft\Windows\INetCache\Content.Word\Untitle1d.png

In the below image just click on next

In the below image Default selection and click on next.

In the below image, I can select which server to install role. in our case it will be local. so, keep the default selection and click on next.

In the below image windows Showing options to select the “server Roles”.Select “Active Directory Domain Services”.

Then it will prompt window to indicate the additional feature installations related to selected role. click on “Add Features” to continue

Then in next window click on next to continue.

Next window click on next

In the below image window click on “install” to start thein stallatuion.

In the below image window it will begins the service install and we have to wait till it finish.Once it finish click on “close” to exit from the wizard. then next step is to reboot the server to complete the installation.

After that completes we need to start on the DC setup. to start that open the “Server Manager” and click Task flag. Then it Showing option as below picture. click on “promote this server to a Domain Controller” option .

C:\Users\R G\AppData\Local\Microsoft\Windows\INetCache\Content.Word\Untitled4.png

Then it starts the DCPROMO wizard. on the first window since its going to be new forest i have selected option “Add a new forest” and i typed the domain name “medhahosting.com.com” which i will be using on the forest. once fill the info click on “next” to continue.

In next window we can select the forest and domain functional levels. i will keep it default. then in domain controller capabilities its by default selected DNS server and Global Catalog as its first DC in the forest. then we need to defined password to use in DC recovery. click on next to continue.

In next window it will give following error but it can be ignore. click on next to continue.

In next window it ask for the netbios name. we can keep it default and click on next to continue.

In next window it give option to change file paths for AD database, log files and SYSVOL files. we can change the paths or keep them defaults. once changes are done click on next to continue.

In next window it gives description about the installation. click on next to continue.

In next window it will run system check and verify system is compatible with the selected installation. once test completes successfully click on install button to begin the installation. if its passes any critical errors those needs to be address before the installation begin.

then it will start the install and we need to wait till it finishes.

Once its complete the install it will automatically reboot the server.

Once server is rebooted log in to server using domain admin credentials.

user : medhahosting\Administrator

password : XXXXXXXXX

Once login, load the “Server manager” and click on “AD DS” option in right hand list. then select and right click as showed in screenshot to start with AD configuration.

Now we successfully completed with the DC setup on server 2012 R2. if you have any issue about the steps feel free to contact me on reddybr@medhahosting.com

Microsoft Exchange Server 2007 end of support

Exchange Server 2007  !! After many years of success, Exchange Server 2007 is reaching end of support on April 11, 2017, per Microsoft Lifecycle Policy. As a reminder, after this date, there will be no new security updates, non-security updates, free or paid assisted support options or online technical content updates. In addition to Exchange Server, the following Office products will also reach end of support within the next 12 months.

  • Microsoft Exchange Server 2007 SP3, Effective Date: 4/11/2017
  • Microsoft SharePoint Server 2007 SP3, Effective Date 10/10/2017
  • Microsoft Office Servers 2007 SP3, Effective Date 10/10/2017
  • Microsoft Office Suite 2007 SP3, Effective Date 10/10/2017
  • Microsoft Office Project 2007 SP3, Effective Date 10/10/2017
  • Microsoft Office Project Portfolio Server 2007 SP1, Effective Date 10/10/2017
  • Microsoft Office Visio 2007 SP3, Effective Date 10/10/2017

After the end of support date is reached, there will be no new security updates, non-security updates, free or paid assisted support options or online technical content updates. Furthermore, as adoption of Office 365 accelerates and on premise deployments decrease, custom support options for all Office products will no longer be available after end of support dates noted above.

[vc_cta h2=”Get One Month Free Microsoft Exchange Server Tech Support” h4=”No Credit Card Needed To Avail This Offer.Continue Your Subscription If You Like It.Cancel anytime. No Hidden Costs.No Cheap Marketing Tricks” txt_align=”center” color=”white” add_button=”right” btn_title=”Get My Free Trail” btn_color=”warning” btn_link=”url:https%3A%2F%2Fmedhahosting.com%2Fwhmcs%2Fcart.php%2F%3Fa%3Dadd%26pid%3D141%26promocode%3DEXCHANGE17|title:Free%20One%20Month%20Exchange%20Server%20Management||” css=”.vc_custom_1492560980422{background-color: #2867b6 !important;}”][/vc_cta]

 Recommended options to handle the upcoming end of support:

1) Leverage FastTrack to move from prior versions of Exchange Server and Office to Office 365

Migrate to Exchange Online and or Office 365 Pro Plus as part of Office 365. Customers deployed on Office 365 will always be up-to-date without the worry of end of support deadlines. The Microsoft FastTrack is ready to help and will provide onboarding guidance and data migration services to all eligible Office 365 customers. Once a subscription to Office 365 has been purchased, our FastTrack engineers will aid help you upgrade from Exchange Server 2007 to Exchange Online or from Office Professional Plus to Office 365 ProPlus, as to ensure the initial migration and upgrade is completed successfully.

You can review the FastTrack Benefit Overview to learn more about how to work with Microsoft specialists to get your Exchange Server environment ready for use or your Office 365 ProPlus installation completed. The FastTrack Center can provide:

  • data migration, rollout and planning support for Exchange Online
  • assistance in testing, repackaging, and distributing the latest on-premises version (Office 2016) included as part of Office 365 ProPlus.

2) Leverage Deployment Planning Services as part for Software Assurance

Customers that are on Software Assurance can utilize their Deployment Planning benefits to plan for upgrades and migrations to O365. Benefit information, including available engagements can be found on the Software Assurance Planning Services.

[vc_cta h2=”Get One Month Free Microsoft Exchange Server Tech Support” h4=”No Credit Card Needed To Avail This Offer.Continue Your Subscription If You Like It.Cancel anytime. No Hidden Costs.No Cheap Marketing Tricks” txt_align=”center” color=”white” add_button=”right” btn_title=”Get My Free Trail” btn_color=”warning” btn_link=”url:https%3A%2F%2Fmedhahosting.com%2Fwhmcs%2Fcart.php%2F%3Fa%3Dadd%26pid%3D141%26promocode%3DEXCHANGE17|title:Free%20One%20Month%20Exchange%20Server%20Management||” css=”.vc_custom_1492560980422{background-color: #2867b6 !important;}”][/vc_cta]

3) Leverage Microsoft Consulting Services (MCS)

Customers also have options to engage with Microsoft Consulting Services where available, to assist with planning and deployment activities related to upgrades and migrations to Office 365

4) Premier

For Premier customers that need additional upgrade or deployment assistance, please work with your Premier Services account team (TAMS, Service Sellers) for additional options.

Be ready and don´t wait until last minute. For this type of topic also you can find more information here Microsoft Volume Licensing.

If you are looking for  Exchange server Management support 24/ 7 365 days .We are ready to help you.Please find the more information here Exchange Server Support 

[vc_cta h2=”Get One Month Free Microsoft Exchange Server Tech Support” h4=”No Credit Card Needed To Avail This Offer.Continue Your Subscription If You Like It.Cancel anytime. No Hidden Costs.No Cheap Marketing Tricks” txt_align=”center” color=”white” add_button=”right” btn_title=”Get My Free Trail” btn_color=”warning” btn_link=”url:https%3A%2F%2Fmedhahosting.com%2Fwhmcs%2Fcart.php%2F%3Fa%3Dadd%26pid%3D141%26promocode%3DEXCHANGE17|title:Free%20One%20Month%20Exchange%20Server%20Management||” css=”.vc_custom_1492560980422{background-color: #2867b6 !important;}”][/vc_cta]

How To Install Exchange Server 2016 Step by Step

[toc] [/toc]

Welcome to this exclusive edition of  Medha Hosting  Exchange Server 2016 step by step guide.You will be learning how to install and setup your exchange server 2016.  This Exchange Server 2016 Step by step guide is 4 parts installation steps.

  1. Exchange Server 2016 requirements.
  2. The software’s to Download.
  3. Preforming Prerequisites setup
  4. Exchange Server 2016 Installation.

This guide is exclusively written keeping in mind for new Exchange server 2016 Administrators who want to set up Exchange server platform. The installation considers a single server deployment of Exchange Server 2016 with the Mailbox role.

For existing Exchange server 2016  server administrators, I have also listed some pro tips that you should start implementing right now to make your Exchange server 2016 more powerful and professional.

If you are still not comfortable or don’t have time to install Exchange Server 2016, Don’t worry we have one month Free Exchange Server Support for you.

You can get one month Free Exchange Server Support from our Exchange server support section, which comes with a free one month Exchange server support and costs nothing for unlimited administration and troubleshooting tasks.

This process will take 5 minutes and  Click on the below image ( link ) and get one month Free Exchange Server Support package now.

Exchange Server 2016 system requirements

Here are the list of checklist to install Exchange server 2016 before you proceed further please go through this checklist

Coexistence of Exchange 2016 with earlier versions of Exchange Server

Exchange versionExchange organization coexistence
Exchange 2007 and earlier versionsNot supported
Exchange 2010Supported with Update Rollup 11 for Exchange 2010 SP3 or later on all Exchange 2010 servers in the organization, including Edge Transport servers.
Exchange 2013Supported with Exchange 2013 Cumulative Update 10 or later on all Exchange 2013 servers in the organization, including Edge Transport servers.
Mixed Exchange 2010 and Exchange 2013 organizationSupported with the following minimum versions of Exchange:

  • Update Rollup 11 Exchange 2010 SP3 or later on all Exchange 2010 servers in the organization, including Edge Transport servers.
  • Exchange 2013 Cumulative Update 10 or later on all Exchange 2013 servers in the organization, including Edge Transport servers.

Supported hybrid deployment scenarios

Exchange 2016 supports hybrid deployments with Office 365 tenants that have been upgraded to the latest version of Office 365.

Network and Active directory servers

ComponentRequirement
Domain controllersAll domain controllers in the forest need to be running one of the following:

  • Windows Server 2016 Standard or Datacenter
  • Windows Server 2012 R2 Standard or Datacenter
  • Windows Server 2012 Standard or Datacenter
  • Windows Server 2008 R2 Standard or Enterprise
  • Windows Server 2008 R2 Datacenter RTM or later
  • Windows Server 2008 Standard, Enterprise, or Datacenter
Active Directory forestThe Active Directory forest functionality level needs to be at Windows Server 2008 or higher.
DNS namespace supportExchange 2016 supports the following domain name system (DNS) namespaces:

  • Contiguous
  • Noncontiguous
  • Single label domains
  • Disjoint

For more information about DNS namespaces supported by Exchange, see Microsoft Knowledge Base article 2269838, Microsoft Exchange compatibility with Single Label Domains, Disjoined Namespaces, and Discontiguous Namespaces.

IPv6 supportIn Exchange 2016, IPv6 is supported only when IPv4 is also installed and enabled. If Exchange 2016 is deployed in this configuration, and the network supports IPv4 and IPv6, all Exchange servers can send data to and receive data from devices, servers, and clients that use IPv6 addresses. For more information, see IPv6 support in Exchange 2013.

Hardware

ComponentRequirementNotes
Processor
  • x64 architecture-based computer with Intel processor that supports Intel 64 architecture (formerly known as Intel EM64T)
  • AMD processor that supports the AMD64 platform
  • Intel Itanium IA64 processors not supported
For more information, see Sizing Exchange 2016 Deployments.

See the “Operating system” section later in this topic for supported operating systems.

MemoryVaries depending on Exchange roles that are installed:

  • Mailbox   8GB minimum
  • Edge Transport   4GB minimum
For more information, see Sizing Exchange 2016 Deployments.
Paging file sizeThe page file size minimum and maximum must be set to physical RAM plus 10MB, to a maximum size of 32,778MB (32GB) if you’re using more than 32GB of RAM.None
Disk space
  • At least 30 GB on the drive on which you install Exchange
  • An additional 500 MB of available disk space for each Unified Messaging (UM) language pack that you plan to install
  • 200 MB of available disk space on the system drive
  • A hard disk that stores the message queue database on with at least 500 MB of free space.
For more information, see Sizing Exchange 2016 Deployments.
DriveDVD-ROM drive, local or network accessibleNone
Screen resolution1024 x 768 pixels or higherNone
File formatDisk partitions formatted as NTFS file systems, which applies to the following partitions:

  • System partition
  • Partitions that store Exchange binary files or files generated by Exchange diagnostic logging

Disk partitions containing the following types of files can be formatted as ReFS:

  • Partitions containing transaction log files
  • Partitions containing database files
  • Partitions containing content indexing files
None

If you have server hardware requirements you can browse our reliable Windows Unmanaged dedicated Servers or Windows Managed Dedicated Servers.

Operating system

Windows Server 2012 and Windows Server 2012 R2 and 2016

ComponentRequirement
Mailbox and Edge Transport server roles
  • Windows Server 2016 Standard or Datacenter*
  • Windows Server 2012 R2 Standard or Datacenter
  • Windows Server 2012 Standard or Datacenter
Management toolsOne of the following:

  • Windows Server 2016 Standard or Datacenter*
  • Windows Server 2012 R2 Standard or Datacenter
  • Windows Server 2012 Standard or Datacenter
  • 64-bit edition of Windows 10
  • 64-bit edition of Windows 8.1

.NET Framework

Exchange version.NET Framework 4.6.2.NET Framework 4.6.1.NET Framework 4.5.2.NET Framework 4.5.1.NET Framework 4.5
Exchange 2016 CU4 or laterX1X4X4
Exchange 2016 CU3X1XX
Exchange 2016 CU2X2,3X
Exchange 2016 RTM or CU1X

Note: Strongly recommended latest .net framework

Supported clients

  • Outlook 2016
  • Outlook 2013
  • Outlook 2010 with KB2965295
  • Outlook for Mac for Office 365
  • Outlook for Mac 2011

Software’s to download

Download Microsoft Exchange Server 2016

Microsoft .NET Framework 4.5.2 (Offline Installer)

Unified Communications Managed API 4.0 Runtime

Performing Prerequisites.

Note: Run all the prerequisites in the sequence

Install exchange Server Pre-requests on the windows server (where you are installing exchange server)

Install Microsoft.NET framework 4.5.2

Install Microsoft.NET framework 4.5.2 on the machine where Exchange 2016 is going to be installed. Download and install .net framework 4.5.2 and click Finish.

Wait till installation succeeded

Install Unified Communications Managed API 4.0 Runtime

Download from the below link given:

https://www.microsoftstore.com/store/msusa/en_US/cat/categoryID.69403900

Install Remote Administration Tools on Windows

Install-WindowsFeature RSAT-ADDS

Prerequisites for Mailbox Server Role

Launch the Windows PowerShell (run as administrator). Run the following command to install the required Windows components. You must restart the server to complete the installation process.

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

Extend the Active Directory schema

Before you install Microsoft Exchange Server 2016, you need to extend the active directory schema and prepare your Active Directory forest and its domains. Mount the Exchange Server 2016 installation Media. Launch Command Prompt (run as administrator) and navigate to the path where setup files are present. Once you successfully enter the below command, the prerequisite analysis and extending AD schema steps should show the status as Completed.

Note:Windows Server Support 

If you are still not comfortable or don’t have time to manage your windows servers, Don’t worry we have one month Free Windows Server Support for you.

You can get one month Free Windows Server Support from our Windows server support section, which comes with a free one month Windows server support and costs nothing for unlimited administration and troubleshooting tasks.

This process will take 5 minutes and  Click on the below image ( link ) and get one month Free Windows Server Support package now.

Once again Download link for MS exchange 2016 is here

Install Exchange Server 2016

Download Microsoft Exchange Server 2016

Prepare schema


Setup.exe /PrepareSchema /IAcceptExchangeServerLicenseTerms

Prepare Active Directory

Next step is to prepare the Active Directory. In the same command prompt that you launched, run the below command by replacing organization name with a name.

Setup.exe /PrepareAD /OrganizationName:”<organization name>” /IAcceptExchangeServerLicenseTerms

Note: In the above command “<organisation should be replace with your actual organisation name

Example : Setup.exe /PrepareAD /OrganizationName:MDHEX2016 /IAcceptExchangeServerLicenseTerms

Install Windows component RSAT-Clustering-CmdInterface

Install-WindowsFeature RSAT-Clustering-CmdInterface

You have now prepared your server to install Exchange Server 2016.

Installing Exchange Server 2016

The Introduction page begins the process of installing Exchange into your organization. Click Next to continue.

On the License Agreement page, review the software license terms. If you agree to the terms, select I accept the terms in the license agreement and then click next.

On the Recommended settings page, select whether you want to use the recommended settings. If you select Use recommended settings, Exchange will automatically send error reports and information about your computer hardware and how you use Exchange to Microsoft. If you select don’t use recommended settings, these settings remain disabled but you can enable them at any time after Setup completes. Click Next.

On the Server Role Selection page, choose whether you want to install the Mailbox role or just the Management Tools on this computer. The management tools are installed automatically if you install the Mailbox server role. Select automatically install Windows Server roles and features that are required to install Exchange Server to have the Setup wizard install required Windows prerequisites. You may need to reboot the computer to complete the installation of some Windows features. If you don’t select this option, you need to install the Windows features manually. Click Next.

In my case, I am choosing Mailbox Role and Management tools as it is single exchange server in my organization

Select the installation path and click next

If you’re installing the Mailbox role, on the Malware Protection Settings page, choose whether you want to enable or disable malware scanning. If you disable malware scanning, it can be enabled in the future. Click Next to continue.

On the Readiness Checks page, if all readiness checks have completed successfully, click Install to install Exchange 2016.

Readiness check shows some errors and advise.It is recommended to download all the patches from the readiness check window. However, I am skipping this and will install later.

Links to download the required softer

https://support.microsoft.com/en-us/kb/2884597

https://support.microsoft.com/en-us/kb/2894875

https://support.microsoft.com/en-us/kb/2822241

Once the setup is complete, click Finish. Restart the computer after Exchange 2016 has completed.

Let’s now open Exchange Admin Center. Open the web browser and type the below https://Exchange Server FQDN/ECP. This link should show up the Exchange Admin Center. Enter the username and password and click sign in.

Select your time zone and save

You are now ready to explore the options available in Exchange admin center.

What Next.

In my coming post, I will be writing about Step by Step Post-Installation Tasks of Exchange Server 2016.

Do you have any queries about Exchange Server 2016 installation step, do let me know via comments.