Again our Exchange CXP team released Update Rollup 1 for Exchange Server 2010 SP3 to the Download Center.
A known issue with Exchange 2010 SP3 RU1 Setup
You cannot install or uninstall Update Rollup 1 for Exchange Server 2010 SP3 on the double-byte character set (DBCS) version of Windows Server 2012 if the language preference for non-Unicode programs is set to the default language. To work around this issue, you must first change this setting. To do this, follow these steps:
- In Control Panel, open the Clock, Region and Language item, and then click Region.
- Click the Administrative tab.
- In the Language for non-Unicode programs area, click Change system locale.
- On the Current system locale list, click English (United States), and then click OK.
After you successfully install or uninstall Update Rollup 1, revert this language setting, as appropriate.
Exchange team is planning to resolve it in a future rollup, but did not want to further delay the release of RU1.
The Microsoft Connectivity Analyzer Tool is a downloadable client program that is used to identify connectivity issues that occur between email clients and a server that is running Microsoft Exchange Server. The tool can also be used to identify connectivity issues between email clients and Office 365. The tool can be used both by email users, to identify common problems, and by IT Administrators, to troubleshoot issues that are affecting their Exchange Server deployments.
The Microsoft Connectivity Analyzer Tool simulates several client logon and mail flow scenarios. When a test fails, many of the errors message provide troubleshooting tips to help the user or IT Administrator to resolve the problem.
This tool is a companion tool to the Remote Connectivity Analyzer website. Whereas the Remote Connectivity Analyzer website enables IT Administrators to pinpoint connectivity issues by simulating connectivity from a location outside the customer environment, the Microsoft Connectivity Analyzer Tool lets both email users and IT administrators run the same tests within the user’s environment.
You must be running one of the following operating systems:
- Windows 8
- Windows 7
- Windows Server 2008
- 64-bit edition of Windows Vista
Download the client tool (Microsoft Connectivity Analyzer (Beta) here.
Connectivity check as follows
Select one of the option below to continue to next screen
Enter the credential you want to check for connectivity issues
They have done it again.. now with a lot of option
Microsoft Connectivity Analyzer (beta), a portable version of the Remote Connectivity Analyzer website, and a short 49 second video that introduces the Microsoft Connectivity Analyzer.
Read more…click here
Microsoft Connectivity Analyzer Pre-Requisites
- The tool supports the following operating systems: 64bit Windows 7, Windows 7, Windows Server 2008+
- Microsoft .NET Framework 4.5 is required.
- Browsers requirements:
The installation will work on all modern browsers. However…
Good work folks!!!
New software release for Evoko room manager, that supports Office365 and Google Apps. Read the Blog
The improvements to the Remote Connectivity Analyzer CAPTCHA experience. It was very annoying to have both password fields get blanked out if you got the challenge incorrect. While we can’t remove this “feature” completely, we hope the enhancements will make a big difference.
The latest version (V1.4) of the Remote Connectivity Analyzer has the following improvements:
We are using a new CAPTCHA service provided by an internal team!!! EHLO rocks again!!!
- The challenge is NOT case sensitive, so it doesn’t matter if you type upper or lower case letters. We also note this on the web page.
- The CAPTCHA challenges will not include hard to distinguish letters/numbers. For example 2 and Z or O and 0.
- If you get the challenge wrong, the password entries will not be removed.
- Once you enter a correct response to the challenge, you will be verified for a set amount of time. This means you will not see additional CAPTCHA challenges until the timeout period expires.
- The inbound SMTP test now inserts the IP address of the user performing the test into the test email message. The IP is also inserted into an SMTP Header (X-Originating-IP).
- Fixed an issue in the Sender-ID test where certain DNS responses while evaluating the “exists” mechanism were incorrectly being treated as a TempError
- The outbound SMTP Sender-ID tests now conform to the RFC specified limit of ten DNS-based mechanisms that can be used during the evaluation of the SPF record.
To know more, click here
- Outlook on Cache mode not updating..Disabling Cached mode on client manually fixes the problem.
- OWA is not affected at all. All changes are instantly reflected in OWA.
- Deleteing the .oab files in the user app data folder fixes the problem
This is not a solution to this issue.
Create new OAB and perform the following tasks:
- Create new OAB from EMC.
- Make sure Web based and Public Folder distribution is enabled.
- Restart MS Exchange System Attendant and File Distribution Service.
- Update the OAB from EMC and Set it As Default.
- Associate the new OAB to Mailbox Database.
- Check the location for the .LZX files C:\Program Files\Microsoft\Exchange Server\V14\ExchangeOAB
and C:\program files\Microsoft\Exchange Server\V14\ClientAccess\OAB\
- Make sure you don’t have web.config file @ .LZX file location.
- I hope you are doing full download of the OAB in Outlook.
- When you download the OAB, Make sure you uncheck the box“Download changes since last send/recieve”
- “Global Address Book” is the only option
- Set-EventLogLevel –Identity LABMBX\MSExchangeSA\* -Level High
- Set-EventLogLevel –Identity “LABCASHT\MSExchangeFDS\*” -Level High
- How to troubleshoot the OAB Generation process..click here
- How Exchange 2007 OAB Files are replicated to a Client Access Server for download…Click here
- Managing Offline Address Books…Click here
- Understanding why error code 0X8004010F is thrown when trying to download an OAB..Click here
- Outlook client OAB download process..Click here
- Administering the offline address book in Outlook 2003 and Outlook 2007…Click here
Microsoft Exchange on Twitter has moved to a new hash tag – #MSExchange. If you tweet about Microsoft Exchange or related topic, please use #MSExchange to tag your tweet… to follow use @MSFTExchange for the latest on Microsoft Exchange, including post updates from EHLO.
Thank you team
Moving mailboxes is a key part of managing an email service for the long-haul. There will be updated technologies, new business priorities, mergers, acquisitions, hardware and version upgrades. Moving mailboxes is an important part of managing an email service. Check out the latest Geek Out with Perry blog and video to gain some deep insights on our approach to moving mailboxes with Mailbox Replication Service (MRS) and get Perry’s take on this topic and how it works. This technology is also incredibly important if you want to move mailboxes to the cloud on your terms with a hybrid deployment.