It’s a Microsoft’s best practice to run every Exchange server role on 2 servers at least. So when you deploy a new HubTransport, or HubTransport+Mailbox server – you face a task to duplicate SMTP receive connectors for printers, devices and other services like MSSQL, monitoring and reporting, etc. Medium to large organizations can use several such connectors with dozens of IP addresses and ranges, so copying it manually from server to server is an ungrateful burden.
Here is a nice and sharp method to clone such connectors with all its configuration en masse. God bless Powershell 🙂 UPDATE: A full PS1 script is available for download in the TechNet Scripts Gallery.
As always – one can use these binaries to update their virtual lab installation, a production server, or install a new one. One of the most important points if this CU – is building compatibility to Exchange 2016 future releases.
Most draw-attention fixes and updates:
KB3093866 The number of search results can’t be more than 250 when you search email messages in Exchange Server 2013
KB3078438 Performance issues occur in an Exchange Server 2013 environment that’s running BlackBerry Enterprise Server 5
KB3078404 Can’t access a shared mailbox after you migrate from Exchange Server 2010 to Exchange Server 2013
KB3074823 No Send As audit events are logged when you use Send As permission in Exchange Server 2013
KB3071776 “A problem occurred” error when you access shared folders in Exchang Server 2013 mailbox by using Outlook Web App
Microsoft announced the first public beta of the Office 365 Support and Recovery Assistant is now available.
The Office 365 Support and Recovery Assistant helps users troubleshoot and fix their account or profile related Outlook issues. The assistant performs a series of diagnostics tests to identify the root cause of issues, such as verifying users’ credentials, licenses, updates to Outlook clients, and whether Outlook servers are reachable. Depending on the test results, it can offer to automatically fix problems for users or provide instruction on recommended solutions. All the diagnostics results are saved in a log file for users to share with their Outlook admin or support engineers for further investigation. Each time you run Office 365 Support and Recovery Assistant, it automatically gets updated to its latest version, so it can troubleshoot any new Outlook problems. Continue reading Microsoft Office 365 Support and Recovery Assistant→
Quite often this problem occurs to messaging administrators when deploying Exchange 2013 Edge Transport server role.
After creating a new EdgeSubscription you call for results with Start-EdgeSynchronization and get the following response:
[PS] C:\Start-EdgeSynchronization -Server mbx.domain.local -TargetServer edge.domain.com -ForceFullSync
RunspaceId : 578a8a8c-002b-4bf4-86ff-f78c285d2944
Result : CouldNotConnect
Type : Configuration
Name : Edge
FailureDetails : The LDAP server is unavailable.
StartUTC : 4/23/2014 10:42:24 AM
EndUTC : 4/23/2014 10:42:24 AM
Added : 0
Deleted : 0
Updated : 0
Scanned : 0
TargetScanned : 0
Continue reading Fixing Exchange 2013 EdgeTransport “CouldNotConnect” error→