Difference between revisions of "Exchange Installation"

From GWAVA Technologies Training
Jump to: navigation, search
 
(26 intermediate revisions by one user not shown)
Line 1: Line 1:
 
Exchange is the email server from Microsoft.  
 
Exchange is the email server from Microsoft.  
  
==Archive Strategies==
+
==Overview==
Unlike GroupWise it does not have message level retention abilities. So to make sure our customers are able to make proper archives there are some additional steps that need to be taken. For example, a message can come to a user, the user can read it, move it to the trash, and delete the trash.  
+
In simple terms Microsoft Exchange [http://en.wikipedia.org/wiki/Microsoft_Exchange_Server] is a email and message platform for organizations. Exchange manages the mailbox database(s) and connects to Active Directory [http://en.wikipedia.org/wiki/Active_Directory] for authentication and rights management.
  
Has it been removed from disk yet? No, it has not. It is moved to the Recoverable Items area of the database, where it resides for 14 days by default before being deleted. A user can undelete the message from Recoverable Items. However, they can also purge their Recoverable Items, which would remove them from the disk. A hold will prevent this until the hold expires.
+
Exchange can be hosted on-premise or in the cloud using Office365 [http://en.wikipedia.org/wiki/Office_365] which Retain can also connect to.
 
+
Microsoft recommends setting up a Journaling Mailbox if all messages are to be saved. There is a very large downside with this technique. If the Journaling Mailbox becomes too large, ~100GB though it may be smaller, Exchange becomes unable to serve the messages so Retain can archive and delete them. This may work in small systems or in limited circumstances, but for the most part it is not the recommended technique for Retain.
+
 
+
Exchange also has In-Place and Litigation Holds. These holds keep items from being removed from the Recoverable Items folder.
+
 
+
*Exchange Archiving with In-Place Hold http://support.gwava.com/kb/?View=entry&EntryID=2406
+
*Exchange Journaling Mailbox Recommendations http://support.gwava.com/kb/?View=entry&EntryID=2300
+
  
 
==Required Exchange Server Roles==
 
==Required Exchange Server Roles==
Exchange is one point in a cluster of servers for a functioning Microsoft network. https://www.microsoft.com/en-us/download/details.aspx?id=39102
+
Exchange is one point in a cluster of servers for a functioning Microsoft network. [https://www.microsoft.com/en-us/download/details.aspx?id=39102]
  
 
There are only a few functions that are critical for our purposes:
 
There are only a few functions that are critical for our purposes:
Line 22: Line 15:
 
*Exchange Mailbox Server
 
*Exchange Mailbox Server
  
In the lab these functions might all be on one server, in a large organization they would be spread across multiple servers.
+
In the lab these functions might all be on one server, in a large organization they would be spread across multiple servers. MS has guidance on sizing Exchange servers [http://blogs.technet.com/b/exchange/archive/2013/05/06/ask-the-perf-guy-sizing-exchange-2013-deployments.aspx] And how to use their Preferred Architecture. [http://blogs.technet.com/b/exchange/archive/2014/04/21/the-preferred-architecture.aspx]
  
 
===DNS===
 
===DNS===
 
The DNS server resolves the domain name and IP addresses within the network and all these functions need to point to the same one to work correctly.  
 
The DNS server resolves the domain name and IP addresses within the network and all these functions need to point to the same one to work correctly.  
  
If there are multiple DNS then they need to be configured with the correct information. http://support.gwava.com/kb/?View=entry&EntryID=2233
+
If there are multiple DNS then they need to be configured with the correct information. [http://support.gwava.com/kb/?View=entry&EntryID=2233]
  
 
One of the more common failure modes is that not all the servers are pointed to the same DNS.
 
One of the more common failure modes is that not all the servers are pointed to the same DNS.
Line 37: Line 30:
  
 
One of the more common failures is that the Retain user's account has expired.
 
One of the more common failures is that the Retain user's account has expired.
How to check the status of the Exchange Impersonation User http://support.gwava.com/kb/?View=entry&EntryID=2362
+
How to check the status of the Exchange Impersonation User [http://support.gwava.com/kb/?View=entry&EntryID=2362]
  
 
===CAS===
 
===CAS===
The Client Access Servers http://technet.microsoft.com/en-us/library/dd298114%28v=exchg.150%29.aspx  
+
The Client Access Servers [http://technet.microsoft.com/en-us/library/dd298114%28v=exchg.150%29.aspx]
  
 
They are the front door of the network. They authenticate and route users to the correct database. When the Retain user logs into it is into the CAS, using Basic Authentication which needs to be enabled in IIS on the CAS server(s).
 
They are the front door of the network. They authenticate and route users to the correct database. When the Retain user logs into it is into the CAS, using Basic Authentication which needs to be enabled in IIS on the CAS server(s).
Line 50: Line 43:
  
 
The main issue is setting policies for best performance:
 
The main issue is setting policies for best performance:
*Retain and Exchange Server 2010 Throttling Policies http://support.gwava.com/kb/?View=entry&EntryID=2021
+
*Retain and Exchange Server 2010 Throttling Policies [http://support.gwava.com/kb/?View=entry&EntryID=2021]
*Large Attachments and/or Messages Cannot Be Archived http://support.gwava.com/kb/?View=entry&EntryID=2089
+
*Large Attachments and/or Messages Cannot Be Archived [http://support.gwava.com/kb/?View=entry&EntryID=2089]
  
 
==Exchange for the Lab Environment==
 
==Exchange for the Lab Environment==
Line 58: Line 51:
  
 
[[Exchange 2013|Installing Exchange 2013 for Retain]]
 
[[Exchange 2013|Installing Exchange 2013 for Retain]]
 +
 +
[[Creating CAS|Installing Standalone CAS for Exchange 2013]]
  
 
==Retain install==
 
==Retain install==
  
[[Preparing Exchange for Retain]] Getting prerequisites in place.
+
[[Retain Exchange Install]] Full install from scratch.
  
[[Retain Exchange Install]] Full install from scratch good for FastTrack.
+
[[Retain Exchange]] Module setup information
  
 
==Retain Outlook Plugins==
 
==Retain Outlook Plugins==
 +
 +
Prerequisites:
 +
*The workstation will need to be connected to the domain. [http://windows.microsoft.com/en-us/windows-8/connect-microsoft-domain-account]
 +
*Outlook will need to be installed and connected to Exchange.
 +
 +
Troubleshooting:
 +
*Enabling Outlook logging [https://support.office.com/en-ie/article/What-is-the-Enable-logging-troubleshooting-option-0fdc446d-d1d4-42c7-bd73-74ffd4034af5]
 +
*Starting Outlook in Safe Mode [https://support.office.com/en-za/article/I-can-t-start-Microsoft-Outlook-2010-or-2013-or-receive-the-error-%E2%80%9CCannot-start-Microsoft-Office-Outlook-Cannot-open-the-Outlook-Window%E2%80%9D-d1f69da6-b333-4650-97bf-4d77bd7abb85]
  
 
[[Retain Outlook Web Access 2013 Plugin]] these instructions actually work.
 
[[Retain Outlook Web Access 2013 Plugin]] these instructions actually work.
Line 73: Line 76:
 
==Troubleshooting==
 
==Troubleshooting==
  
Some basic KBs:
+
[[Troubleshooting Exchange]]
*How to Create a SOAP Trace for Exchange Jobs http://support.gwava.com/kb/?View=entry&EntryID=2321
+
*Location of Exchange Logs http://support.gwava.com/kb/?View=entry&EntryID=2257
+
 
+
[[Exchange Troubleshooting]] internal and migration stuff
+
 
+
[[Troubleshooting Exchange]] mostly with LDAP stuff
+
 
+
[[LDAP]] Basics
+

Latest revision as of 15:33, 12 June 2018

Exchange is the email server from Microsoft.

Contents

[edit] Overview

In simple terms Microsoft Exchange [1] is a email and message platform for organizations. Exchange manages the mailbox database(s) and connects to Active Directory [2] for authentication and rights management.

Exchange can be hosted on-premise or in the cloud using Office365 [3] which Retain can also connect to.

[edit] Required Exchange Server Roles

Exchange is one point in a cluster of servers for a functioning Microsoft network. [4]

There are only a few functions that are critical for our purposes:

  • DNS (Domain Name Server)
  • AD DS (Active Directory Directory Services)
  • CAS (Client Access Server)
  • Exchange Mailbox Server

In the lab these functions might all be on one server, in a large organization they would be spread across multiple servers. MS has guidance on sizing Exchange servers [5] And how to use their Preferred Architecture. [6]

[edit] DNS

The DNS server resolves the domain name and IP addresses within the network and all these functions need to point to the same one to work correctly.

If there are multiple DNS then they need to be configured with the correct information. [7]

One of the more common failure modes is that not all the servers are pointed to the same DNS.

[edit] AD DS

Active Directory Directory Services is how organizations organize domains, sites, computers, users and more. This is where the user Retain uses for access is created and resides. AD is where rights are assigned and maintained.

Retain logs into AD using SCP, EWS, autodiscover or LDAP.

One of the more common failures is that the Retain user's account has expired. How to check the status of the Exchange Impersonation User [8]

[edit] CAS

The Client Access Servers [9]

They are the front door of the network. They authenticate and route users to the correct database. When the Retain user logs into it is into the CAS, using Basic Authentication which needs to be enabled in IIS on the CAS server(s).

One of the most common failure modes is that Basic Authentication is not set up on the CAS for both EWS and autodiscover.

[edit] Exchange Mailbox Server

This is the server where the mailbox database we are accessing resides. As long as the Global Catalog User aka Retain Impersonation User has Application Impersonation rights to the directory it should be able to get to the data.

The main issue is setting policies for best performance:

  • Retain and Exchange Server 2010 Throttling Policies [10]
  • Large Attachments and/or Messages Cannot Be Archived [11]

[edit] Exchange for the Lab Environment

Installing Windows Server 2012 R2

Installing Exchange 2013 for Retain

Installing Standalone CAS for Exchange 2013

[edit] Retain install

Retain Exchange Install Full install from scratch.

Retain Exchange Module setup information

[edit] Retain Outlook Plugins

Prerequisites:

  • The workstation will need to be connected to the domain. [12]
  • Outlook will need to be installed and connected to Exchange.

Troubleshooting:

  • Enabling Outlook logging [13]
  • Starting Outlook in Safe Mode [14]

Retain Outlook Web Access 2013 Plugin these instructions actually work.

Retain Outlook 2013 Plugin Retain 3.4 and Outlook 2013 client.

[edit] Troubleshooting

Troubleshooting Exchange

Personal tools
Namespaces

Variants
Actions
Home
Exchange
GroupWise
JAVA
Linux
MTK
Retain
GW Monitoring and Reporting (Redline)
GW Disaster Recovery (Reload)
GW Forensics (Reveal)
GWAVA
Secure Messaging Gateway
GW Mailbox Management (Vertigo)
Windows
Other
User Experience
Toolbox
Languages
Toolbox