The Exchange Team has released update rollup 2 for Exchange 2010 SP3.
This update rollup does not apply to Exchange Server 2010 RTM, SP1 or SP2. You should have atleast Exchange 2010 SP3 running.
The following update rollups have also been released today.
- Update Rollup 11 for Exchange Server 2007 SP3
- Update Rollup 7 for Exchange Server 2010 SP2
- Exchange Server 2013 RTM CU1 MSRC Security bulletin MS13-061
- Exchange Server 2013 RTM CU2 MSRC Security bulletin MS13-061
Check the source for more info.
Microsoft has given all TechNet Subscribers a one year full trial of Office 365.
With an Office 365 for TechNet Subscribers trial, you can:
- Use your Office 365 subscription for evaluation and deployment planning of Office 365 Enterprise E3 in your organization.
- Take advantage of the five user licenses provided as part of this benefit to evaluate the multiple users and devices experience available from Office 365 Enterprise E3.
Login to TechNet subscription homepage and activate Office 365. You can use your own domain or a .onmicrosoft.com domain during the trial.
I came across this strange error while installing Exchange 2010 SP2 on a brand new server running Windows 2008 R2 SP1.
[ERROR] The following error was generated when “$error.Clear(); & $RoleBinPath\ServiceControl.ps1 EnableServices $RoleRoleName.Replace(‘Role’,”)
” was run: “Provisioning layer initialization failed: ‘Failed to reconnect to Active Directory server DC.Domain.Local. Make sure the server is available, and that you have used the correct credentials.’”.
[ERROR] Provisioning layer initialization failed: ‘Failed to reconnect to Active Directory server DC.Domain.Local. Make sure the server is available, and that you have used the correct credentials.’
[ERROR] Failed to reconnect to Active Directory server DC.Domain.Local. Make sure the server is available, and that you have used the correct credentials.
[ERROR] Active Directory server DC.Domain.Local is not available. Please retry at a later time.
[ERROR-REFERENCE] Id=AllRolesCommonFirst___56139ce4432346ecb7936afae4c3a9cc Component=EXCHANGE14:\Current\Release\Shared\Datacenter\Setup
Setup is stopping now because of one or more critical errors.
Finished executing component tasks.
Ending processing Install-BridgeheadRole
[WARNING] Setup has made changes to operating system settings that require a reboot to take effect. Please reboot this server prior to placing it into production.
End of Setup
It was complaining about the DC being not reachable/ online and that the credentials was wrong. I checked both – DC was up and running without any issues and the credentials was correct.
After having a chat with Microsoft support, I came to know that it is a known issue – at least among the Microsoft PSS guys. The problem was that the server had SCOM agent installed and the server was put in maintenance mode during the Exchange installation.
After taking the server off from the maintenance mode in SCOM, the setup ran without any issues! I had installed Exchange on a number of other servers with maintenance mode on in the same environment. So, the question remains – what exactly is maintenance mode for?
Version 2 of rollups have become so common these days
The Exchange Team has released version 2 of the Update Rollup 5 for Exchange 2010 SP2 deployments. The version 1 was released a few weeks back, but was withdrawn due to a DAG related bug.
As usual, any interim updates from Microsoft PSS should be uninstalled and Forefront should be disabled before running the rollup setup.
The required services are automatically restarted when you run the setup.
Remote access is lost after upgrading Windows 2008 R2 RTM server to SP1! How to fix it?
I know that SP1 for 2008 R2 has been out for a while and any new server builds should have it by default. But not all companies have their builds upgraded to SP1. I came across this issue while patching a 2008 R2 RTM server before installing Exchange 2010.
The issue was that the base RTM build had Security Hotfix 2667402. From the KB article, following paragraph got my attention.
After you install security update 2667402 on a computer that is running Windows 7 or Windows Server 2008 R2, and then you install Service Pack 1 (SP1) for Windows 7 or for Windows Server 2008 R2, the binary version of Rdpcorekmts.dll is 6.1.7600.16952 and not 6.1.7601.17767. In this scenario, you may be unable to create a remote desktop session to control the Windows 7-based or Windows Server 2008 R2-based computer.
This issue occurs because the SP1 binary version of Rdpcorekmts.dll was not originally deployed when security update 2667402 was originally installed.
On June 12, 2012, security update 2667402 was rereleased to address this issue. Customers who are running Windows 7 or Windows Server 2008 R2 should install the reoffered update. This includes those who already successfully installed the update that was originally offered on March 13, 2012.
The fix was to remove the hotfix 2667402 via ILO.
After the server was restarted, I could establish an RDP session. Microsoft recommends to reinstall the same hotfix which was re-released in June 2012.
We might need this info at times, especially when installing Exchange in a large organization with a number of AD sites.
We can easily find this info from the command line. Run the following from your workstation.
Nltest /server:remoteservername /dsgetsite
If you are running the command locally on the server, nltest /dsgetsite will do.
Any customer thinking of migrating to Office 365 should use the O365 Deployment Readiness Tool as a prerequisite.
It is a “must” to run this tool to gather information about your platform if you are thinking of moving to Office 365. It checks whether your platform is ready to make a move to the cloud and if not, it will point out the steps to be taken to make your platform Office 365 ready.
The tool does the following assessments:
- Email domain discovery and number of users leveraging each domain
- User Identity and Account Provisioning
- Statistical information
- Active Directory schema and forest/domain functional data
- Trusts extract (checks for multi-forest constraints)
- Directory Synchronization
- Pre-requisite checks
- Attribute assessment
- Single sign on
- Attribute assessment
- Exchange Online
- Statistical information
- Public folder, public delegates, and proxyaddresses extract
- 3rd party and unified messaging proxyaddresses information
- Lync Online
- Statistical information
- SIP domains summary
- SharePoint Online
- User object count assessment
- Client and End User Experience
- Summary of domain joined machines for rich experience/SSO readiness
- Port analysis on certain Office 365 endpoints
- DNS records assessment
You need to run the tool from a domain joined machine.
Download the tool here
I got a question by email about the possibility of upgrading the Office 365 Small Business plan to an Enterprise one. Is it possible?
The short answer is NO, atleast at the time of writing. There is no button to click to “upgrade” the current plan. If you do want to move to an Enterprise plan, you will need to subscribe to a new Enterprise plan and migrate your users to the new “platform”.
Although Small Business plan has a cap of 50 users, Microsoft recommends the P plan for companies with a user base of 1-25, with the remaining for future growth.
Hope this clears the confusion.