Brian Reid – Microsoft MVP and Microsoft Certified Master
-
Exchange 2013 Transport Agents
Earlier today I posted http://blog.c7solutions.com/2012/10/creating-simple-exchange-server.html on how to create a transport agent in Exchange, and though the steps cover some of the detail for Exchange Server 2013 they do not cover some of the detail, so I’ve added that to this post below: Use .NET Framework 4.0 for Exchange 2013 though it is possible to…
-
Creating a Simple Exchange Server Transport Agent
This blog post follows a session that I delivered at the MEC 2012 conference in Orlando. If you attended the conference the slides are available on http://mymec.mecisback.com for the rest of 2012. Part of the transport agents session was writing a new transport agent, and the example agent was to do add a form of…
-
Installing and Configuring AD RMS and Exchange Server
Earlier this week at the Microsoft Exchange Conference (MEC 2012) I led a session titled Configuring Rights Management Server for Office 365 and Exchange On-Premises [E14.314]. This blog shows three videos covering installation, configuration and integration of RMS with Exchange 2010 and Office 365. For Exchange 2013, the steps are mostly identical. Installing AD RMS…
-
Create Shadow Redundancy Cross Forest in Exchange 2010
Send connector cross forest shadow redundancy New-SendConnector ToTailspin -AddressSpaces SMTP:tailspin.com -SmartHosts mail.tailspin.com -ProtocolLoggingLevel verbose -DNSRoutingEnabled $False -SmartHostAuthMechanism ExternalAuthoritativeGet-SendConnector ToTailspin | Add-ADPermission -user “MS Exchange\Externally Secured Servers” -ExtendedRights ms-Exch-SMTP-Send-XShadow Receive connector cross forest shadow redundancy New-ReceiveConnector FromFabrikam -RemoteIPRanges 192.168.100.1 -Bindings 0.0.0.0:25 -ProtocolLoggingLevel verbose -Banner “220 Tailspin XShadow SMTP Server” -AuthMechanism ExternalAuthoritative Get-ReceiveConnector FromFabrikam | Add-ADPermission…
-
Creating GeoDNS with Amazon Route 53 DNS
UPDATE: 13 Aug 2014 – Amazon Route 53 now does native GeoDNS within the product – see Amazon Route 53 GeoDNS Routing Policy A new feature to Exchange 2013 is supported use of a single namespace for your global email infrastructure. For example mail.contoso.com rather than different ones for each region such as uk-mail.contoso.com; usa-mail.contoso.com…
-
Access Is Denied Message After Sysprep–How To Fix
If before you use Sysprep to prepare a Windows machine for imaging you set the administrators password “User cannot change password” then sysprep will not clear this setting, but will set the “User must change password at next logon” setting. Normally these two settings are mutually exclusive, but in the scenario for sysprep it seems…
-
Recovering Exchange Items When Entourage Corruption Deleted Them From The Server
I have a client who has an Exchange 2003 server and uses Entourage for the Mac. Last week all his sent items disappeared. It seems the problem is that Entourage’s local database corrupted and sync’ed back to the server that all these items where now deleted! To recover them I used PFDAVAdmin from http://www.microsoft.com/en-us/download/details.aspx?id=22427 and…
-
How To Speed Up Exchange Server Transport Logging
In Exchange 2010 SP1 and later any writing to the transport log files for activity logging (not the transaction logging on the mail.que database) is cached in RAM and written to disk every five minutes. In a lab environment you might be impacted by this as you might have sent an email and want to…
-
Configuring Exchange Server 2013 Unified Messaging With 3CX and Not AsteriskNOW
This article is an addendum to my blog series on configuring Exchange Server 2010 and Exchange Server 2013 with AsteriskNOW. AsteriskNOW is a easy to install version of Asterisk 1.8 in that it includes the underlying OS and the FreePBX software. The problem with Asterisk 1.8 is that it does not work well with the…
-
Building An Exchange Unified Messaging Lab (Part 8)
In the extended series of blog posts we are looking at creating a unified messaging lab for Exchange Server. So far we have looked at installing a software PBX (AsteriskNOW) and configuring Exchange Server (both 2010 and 2013) to accept calls from our PBX. We have also looked and configuring our PBX to send and…
-
Building An Exchange Unified Messaging Lab (Part 7)
In this series of blog posts I am looking at creating a Unified Messaging lab for Exchange Server 2010 (and 2013). Earlier posts have looked at the installation of the PBX (AsteriskNOW) and the configuration of the Exchange Server. This post will look at the configuration of the user’s settings. For each user there are…
-
Building An Exchange Unified Messaging Lab (Part 6)
Earlier parts in this blog have talked about VoIP, configured AsteriskNOW software PBX and configured inbound and outbound calls via the PBX. Now it is time to configure voicemail to be provided by Exchange Server 2013 and for the telephone users to be able to call Exchange an listen to their voicemail. In addition to…
-
Building An Exchange Unified Messaging Lab (Part 5)
Earlier parts in this blog have talked about VoIP, configured AsteriskNOW software PBX and configured inbound and outbound calls via the PBX. Now it is time to configure voicemail to be provided by Exchange Server and for the telephone users to be able to call Exchange an listen to their voicemail. In addition to listening…
-
Building An Exchange Unified Messaging Lab (Part 4)
This blog post series is the steps to build a working unified messaging lab for Exchange Server. I thought I would write it all down as I found a lack of end to end documentation for the process and what I thought would be a days work turned into many as I worked at finding…
-
Building An Exchange Unified Messaging Lab (Part 2)
This series of blog posts started with Part 1 where we discussed the requirements of the lab and what you would need from any PBX that you might have to hand. Part 2 (and the next few parts) will look at installing AsteriskNOW to provide a software PBX to support the Exchange Server unified messaging…
-
Building An Exchange Unified Messaging Lab (Part 3)
This blog is part of a series on creating a unified messaging lab for Microsoft Exchange Server. Configuring Unified Messaging was not as easy as I thought it would be and there was a lack of information that brought all the settings into one place, and a lot of incorrect information! The series started with…
-
Installing Dell Open Manage 7.1 on Hyper-V R2 Servers
This set of instructions goes through the process for installing Dell Open Manager on Windows Server 2008 R2 and Windows Server 2012. Download both the 6.5 and 7.1 versions of Dell Open Manage You need to install 6.5 first, or you will get errors about “omchecks has stopped working” failing during the RunPreReqChecks process and…
-
Merge Exchange 2010 Personal Archive Back to Primary Mailbox
A feature of Exchange 2010 SP1 was to store “older” emails in a different database and to have that database on a cheaper storage subsystem. Given that Exchage primary mailboxes work very well on slower storage anyway you could well be in the position of needing to move archived content, that is content moved to…
-
Building an Exchange Unified Messaging Lab
This is a project I have been meaning to do for some time, and when I got around to doing it found it to be harder than I expected it to be. So this blog series covers the steps needed to build a Unified Messaging lab utilising Exchange Server 2010 and Microsoft Lync Server along…
-
Highly Available Geo Redundancy with Outbound Send Connectors in Exchange 2003 and Later
This is something I’ve been meaning to write down for a while. I wrote an answer for this question to LinkedIn about a week ago and I’ve just emailed a MCM Exchange consultant with this – so here we go… If you configure a Send Connector (Exchange 2007 and 2010) or Exchange 2003 SMTP Connector…
-
Starting Exchange When You Have Active Directory Issues
I had a call the other day from a company who had Exchange issues. One investigation it turned out they had a very suspect Active Directory and no-one would admit to what they had actually done to get it in such a state! One server (DC1) would not talk to the other DC’s (Kerberos issues…