Backtrack:  
Blog
 
showing posts tagged with 'exchange'
Access Exchange 2013 Management Shell (EMS) without installation
edited by on September 15th 2015, at 15:56
Rather than installing the Exchange 2013 management tools, you could also connect to the Exchange Management Shell (EMS) through Powershell "remoting".

Connect to EMS using the current credentials (i.e. the user running Powershell):

$session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri http://exchange-server-fqdn/PowerShell -Authentication KerberosImport-PSSession $session

Replace exchange-server-fqdn with the FQDN or IP address of the Exchange server you wish to connect to. With this command, you will be using the credentials of the current logged in user, and authenticate through Kerberos. If the user is not a organizational admin, you will be able to l  ...
 
Crude script to defrag Exchange mailbox databases
edited by on September 11th 2015, at 10:39
This is a very crude script to defrag (using eseutil) Exchange mailbox databases.

The script takes the database name as a mandatory parameter. It then dismounts the database, checks whether the database state has been shutdown cleanly, performs the defrag, verifies the state again, and finally, mounts it again.

Note that this is an offline process. The specified mailbox database will be offline, meaning that all mailboxes in the database will not be accessible until the process has been completed.

Use with caution!
This script has not been tested extensively and does not account for everything that can go wrong. I merely provide it as a good starting point to extend the script to somethin  ...
 
Health probes in Exchange fail with error: WrongServer (0x00000478)
edited by on September 3rd 2015, at 14:08
The internal health monitoring system may report Unhealthy, and an error similar to the following is reported by SCOM:

Alert: {2} Resolution state: New
Alert: {2}
Source: EXCH02 - Compliance
Path: EXCH02.contoso.com;EXCH02.contoso.com
Last modified by: System
Last modified time: 9/3/2015 11:43:37 AM Alert description: EMSMDB.DoRpc(Logon) step of ComplianceOutlookLogonToArchiveRpcCtpProbe/EXCHDB03 has failed against EXCH02.contoso.com proxying to Unknown for HealthMailbox8414258ad6574db1ad62eb67e94b9d6d@contoso.com.
Latency: 00:00:00.9250000
ActivityContext:
.
.
.
Details:
Error: Error returned in LogonCallResult. Error code = WrongServer (0x00000478)
Log: RpcProxy connectivity verification  ...
 
Blackberry Enterprise Server (BES) agents crash on Exchange 2013 (native or mixed)
edited by on September 3rd 2015, at 10:48
When running Blackberry Enterprise Server (BES) 5.0.4 in an environment with users whose mailboxes are located on Exchange 2013 servers, you may encounter the following problem: certain, but not all users lose their connectivity on their mobile devices. They can no longer send or receive e-mail, calendar, contacts.

When looking at the event viewer, an application crash is logged:

Event 1000 Application Error
Faulting application name: BlackBerryAgent.exe, version: 5.0.4.17, time stamp: 0x502e604b
Faulting module name: exmapi32.dll, version: 6.5.8320.0, time stamp: 0x517e1c40
Exception code: 0xc0000005
Fault offset: 0x00010188
Faulting process id: 0x1fbc
Faulting application start time: 0x0  ...
 
Restore missing HealthMailbox for an Exchange mailbox database
edited by on September 2nd 2015, at 17:02
Exchange 2013 uses Managed Availability to monitor its own health. One part of this monitoring is achieved through the use of synthetic transactions, mimicking regular user activity, such as accessing mailboxes, send/receive e-mail, etc. For this to work properly, the monitoring system uses so-called Health Mailboxes. These are just regular mailboxes (with a regular AD account), but are created automatically and used for the sole purpose of health monitoring. Depending on the CU-version of Exchange 2013, these are created for every database on every CAS (or just one per CAS and one per database, starting from CU6).

Sometimes, these mailboxes may become corrupt or unusable, in which case the  ...
 
System Center agent not properly discovering services on a server
edited by on September 2nd 2015, at 16:29
If you notice that SCOM is not properly discovering services on a particular server (e.g. it does not detect the presence of Exchange), you can resolve this by clearing the cache of the agent on the server. This will trigger a new full discovery, and the agent should now be able to detect the new services:

Log on the server of which services are not discovered properly.

Stop the agent (System Center Management service): net stop HealthService



Delete the contents of the Health Service State folder, located in the installation folder of the agent.
(default location: %PROGRAMFILES%\System Center Operations Manager\Agent).

Start the agent again (System Center Management service): net start  ...
 
Purge migrated or disabled mailboxes in Exchange
edited by on September 1st 2015, at 16:24
If a mailbox gets migrated or disabled (= disconnected), the mailbox is not removed from the mailbox database right away. Instead, Exchange uses the retention configuration of the mailbox database in which the mailbox was stored. This is useful if a restore of the mailbox is needed (e.g. in case of accidental deletion).

However, sometimes it may not be necessary to have the mailbox available for undelete. E.g. when you have migrated a large number of mailboxes, you may not wish to keep the old mailbox copies to free up disk space. In that case, you can manually "purge" the mailbox from the mailbox database.

Note that this only works with a disconnected mailbox. These are mailboxe  ...
 
Reclaim disk space on Exchange 2010/2013 mailbox servers
edited by on August 28th 2015, at 10:05
Exchange mailbox database files (EDB-files) grow in size as the data within them grows. But when data is removed, their file sizes will not shrink back. Instead, the file will contain "white space", which will be re-used if additional space is needed again.

Older versions of Exchange (2007 and earlier) did (limited) automatic space reclamation as part of their online database maintenance routines. Starting from Exchange 2010, these maintenance routines have changed and space reclamation no longer occurs. It is up to the Exchange administrator to perform space reclamation if the need arises.

There are two viable methods for reclaiming disk space, each having their pros and cons:

  ...
 
Can I reboot witness server of a two member Exchange DAG?
edited by on August 27th 2015, at 11:51

You can reboot a DAG witness server but only if your DAG cluster is operating with all of its members online.

An FSW (file share witness) will only come into play during a failover scenario. This means that it will become a problem if a DAG member fails at the exact same moment your FSW is rebooting, because the remaining DAG member will then not achieve majority, causing the cluster to fail completely.

Note that if you reboot the FWS often in a short period, the cluster will mark the FWS as unreliable and fail the cluster. In that case, you should manually bring it back online by running the following PS cmdlet on a DAG member:

Get-ClusterResource | Start-ClusterResource
 
Clearing Exchange 2013 performance (diagnostics) logs using Powershell
edited by on August 26th 2015, at 10:38
Exchange 2013 has several performance counters running by default. While this is useful for diagnostic purposes, it also can take up a lot of disk space (can go over 1 GB a day). You can use Powershell to clear out older performance logs.

gci 'S:ExchangeLoggingDiagnosticsDailyPerformanceLogs','S:ExchangeLoggingDiagnosticsPerformanceLogsToBeProcessed' | gci -Include '*.log','*.blg' -Recurse | ? LastWriteTime -lt (Get-Date).AddDays(-7) | Remove-Item

Replace the paths to the daily performance logs and performance logs to be processed. You can also adjust the number of days it needs to keep (in the example, it's 1 week). In the example, we remove the files, but you could just as easily move th  ...
 
Certificate renewal using the same private key (e.g. GoDaddy)
edited by on August 24th 2015, at 16:09
Certain Certificate Authority providers, such as GoDaddy allow you to renew an SSL certificate using the same CSR and private key. This greatly simplifies the procedure to renew a certificate, but this can also complicate things if you don't have your private key readily available.

On a server running ADFS 3.0 for instance, you do not have IIS available to allow an easy SSL certificate renewal (or even a request). Or perhaps, you lost the current private key, or it is located somewhere where it's not easily accessible.

Luckily, there's a fairly easy way to extract the private key from the previous SSL certificate on your Windows server. By using the Windows Certificate store functionality   ...
 
MSExchange ADAccess Event 2937
edited by on August 24th 2015, at 12:45
The following errors may be logged in an environment that has been upgraded to a new version of Exchange (usually 2003 to 2010), or a service pack to Exchange (2010) has been installed.

MSExchange ADAccess Event ID 2937
Log Name: Application
Source: MSExchange ADAccess
Date: 9/26/2010 9:12:29 AM
Event ID: 2937
Task Category: Validation
Level: Warning
Keywords: Classic
User: N/A
Computer: server.contoso.com

The reason for this error is that an AD attribute of an item (e.g. mailbox, connector, routing group, etc) is pointing to the DN of a server which has recently been deleted from AD. As long as the object is still physically present in   ...
 
MSExchangeSA event 9385 "failed to read the membership..."
edited by on August 24th 2015, at 12:06
You may encounter the following errors in the Application event log:

MSExchangeSA Event ID 9385
Microsoft Exchange System Attendant failed to read the membership of the universal security group '/dc=com/dc=domain/ou=Microsoft Exchange Security Groups/cn=Exchange Servers'; the error code was '8007203a'. The problem might be that the Microsoft Exchange System does not have permission to read the membership of the group.

If this computer is not a member of the group '/dc=com/dc=domain/ou=Microsoft Exchange Security Groups/cn=Exchange Servers', you should manually stop all Microsoft Exchange services, run the task 'add-ExchangeServerGroupMember,' and then restart all Microsoft Exchange servic  ...
 
Mail-enable multiple accounts with Powershell
edited by on August 21st 2015, at 11:06

You can mail-enable multiple accounts with a single Powershell command. Look below for some examples:

Mail-enable AD accounts whose first name is John:

Get-ADUser -Filter * | Where {$_.GivenName -like "John"} | ForEach-Object { Enable-Mailbox -Identity $_.DistinguishedName }

Mail-enable all accounts in an OU called Engineering:

Get-ADUser -Filter * -SearchBase "OU=Engineering,DC=contoso,DC=local" | ForEach-Object { Enable-Mailbox -Identity $_.DistinguishedName }
 
Legacy public folder access for Exchange 2013 users
edited by on August 20th 2015, at 16:26
The way public folders work has been changed radically in Exchange 2013. Starting from Exchange 2013, public folders are basically stored in a regular mailbox, and then published as public folders. With Exchange 2010 being the last version to support so-called "legacy" public folders, Exchange 2013 is not able to access these folders. As a consequence, if you're in the middle of a migration from Exchange 2007/20102010 to 2013, or are running a mixed environment, and you still have these legacy public folders on your Exchange 2010, you will notice that users with a mailbox migrated on Exchange 2013 will no longer be able to access these public folders. As Exchange 2013 no longer sup  ...
 
"Item not found" error for Office365 users with on-premise mailbox
edited by on August 18th 2015, at 15:07
If you have an Exchange Hybrid Configuration setup, you may have some users that use services of Office365 but still have their mailbox on-premise. These users probably have an Office365 license assigned to them. Selecting these users from the Users list in the Office365 Admin Portal reveals the following message when viewing the primary e-mail address for such a user:

Error
The items you're trying to open couldn't be found.

Additionally, the same error is displayed when attempting to view or edit Exchange Online properties for such a user.

The error is actually a "bug" in the Office365 Admin Portal, caused because the user has an Exchange Online license assigned. Because of thi  ...
 
Shared mailbox still visible in Outlook after removing permissions
edited by on August 18th 2015, at 14:20
Exchange's AutoMapping feature allows shared mailboxes to be added automatically to a user's Outlook if that user obtains full access permissions to that mailbox. This eliminates the need for the user to add the mailbox manually in Outlook. Subsequently, the same mechanism is also used when access to a shared mailbox is removed for a particular user. The mailbox should then automatically disappear from Outlook. Unfortunately, this does not always work properly.

Because of an intermittent bug, sometimes it can occur that a shared mailbox is not automatically removed from Outlook after access to that mailbox has been revoked. In fact, manually removing the mailbox (through Registry) doesn't h  ...
 
Configure DNS for Office 365 using DirectAdmin
edited by on August 17th 2015, at 13:25
EDIT: highlight required trailing dots + added CNAME for msoid.

If you're using a hosting provider which uses DirectAdmin for its DNS management, it may be a hassle to correctly configure DNS records for Office 365, mainly because of syntax issues. After some trial-and-error and googling, I finally managed to correctly devise the proper syntax to configure Exchange Online and Lync Online.

The set up of the entries below is a left and right field in the DNS management, safe for MX-records, which are set up elsewhere. For most services, don't forget to add the trailing . at the end of each record pointing to a Microsoft Server. Otherwise, resolving will incorrectly add your own do  ...
 
Count the number of mailboxes on an Exchange Mailbox server
edited by on August 17th 2015, at 10:10

Easily count the number of mailboxes located on an Exchange (mailbox) server with Powershell:

[PS] >Get-Mailbox | Group-Object -Property:ServerName | Select-Object Name,Count

Name                   Count
----                   -----
exchange01                43
exchange02               100
exchange03               252
 
Exchange 2013 Maintenance mode
edited by on August 14th 2015, at 14:22
Every once in a while you will have to perform maintenance (e.g. installing updates, troubleshooting, hardware maintenance) on your Exchange 2013 servers. In the past, you had to schedule proper downtime and do manual changes to configurations for this to work properly. Exchange 2013 SP1 introduced "Maintenance mode", allowing your Exchange 2013 servers to be put in maintenance mode. This allows you to perform maintenance on a server without the end users noticing it's gone, or without having to schedule downtime.

Maintenance mode was designed for mailbox servers (i.e. servers that have the mailbox role, either standalone or multi-role). However, it's worth noting that putting a s  ...
 
showing posts tagged with 'exchange'
 
 
« ‹November 2024› »
SunMonTueWedThuFriSat
     12
3456789
10111213141516
17181920212223
24252627282930
 
Links
 
Quote
« You only find out who is swimming naked when the tide goes out. »
Warren Buffett