After a (successful) migration from Lync 2010 to Lync 2013 I wanted to decommission the old Lync 2010 servers. In my previous blog post I already explained why the CMS didn’t want to move, but the next issue was challenging as well.
Before removing the last Lync front-end server you have to remove all Lync 2010 objects from this front-end server. Well known issue for example is the conference directory that for some reason always stays at the front-end server.
Continue reading Unable to delete Lync 2010 Front End Pool after migrating to Lync 2013
After upgrading from Lync 2010 to Lync 2013 I was not able to move the CMS from the Lync 2010 front-end server to the Lync 2013 front-end server using the Move-CsManagementServer command. It constantly returned this error:
Continue reading Move CMS from Lync 2010 to Lync 2013
Last TechEd in Madrid I got an interesting question about Exchange 2013 supportability in the PowerShell ISE (Integrated Scripting Environment). This gentleman was using the Remote PowerShell functionality in ISE and was wondering if this was a supported solution.
It took some time to get a confirmation, but these are the supported scenarios:
- Exchange Management Shell (which is running Remote PowerShell) – supported
- Regular PowerShell connecting to Exchange via Remote PowerShell – supported
- Powershell ISE connecting to Exchange via Remote PowerShell – supported
Regular PowerShell or PowerShell ISE simply loading Exchange snapins is not supported unless Technet specifically calls out that you must run local PowerShell for a specific cmdlet.
Remote PowerShell can be activated like this:
$Session = New-PSSession –ConfigurationName Microsoft.Exchange –ConnectionUri http://ams-exch01.contoso.com/PowerShell -Authentication Kerberos
This can be done in a normal PowerShell window or in the ISE:
A Microsoft knowledgebase article was released recently regarding an issue with Remote Powershell, ISE and Exchange Server 2010 SP3:
http://support.microsoft.com/kb/2859999 – Some cmdlets fail in PowerShell ISE after an upgrade to Exchange Server 2010 SP3
Now that Microsoft has released Exchange Server 2013 RTM CU2 it’s time to have a closer look at installing this Cumulative Update.
In contrast with the previous Update Rollups as we’ve seen in Exchange 2007 and Exchange 2010, which were only a set of hotfixes bundled together, a Cumulative Update is a full version of the product. So, it is now possible to install an Exchange 2013 server from scratch using the CU2 download.
Another advantage of a CU is that Microsoft can bundle new functionality into the product, even Schema changes are possible (as a matter of fact CU2 does include a number of Schema changes) but also the Configuration container in Active Directory can be changed.
Continue reading Upgrade to Exchange Server 2013 RTM CU2
On July 9th Microsoft has released Cumulative Update 2 for Exchange Server 2013 RTM. Besides a large number of (undisclosed) fixes there are several enhancements in CU2:
- Per-server database support – The maximum number of Mailbox databases has been raised from 50 up to 100. The Exchange Server 2013 Server Role Requirements Calculator also has been updated with this information;
- OWA redirection – CU2 introduces a single sign-on experience when using Forms Based Authentication (FBA) which is great in a coexistence scenario;
- High Availability – Exchange 2013 RTM CU2 introduces a new service, the DAG Management Service. The DAG Management service contains non-critical code that used to reside in the Replication service. This change does not introduce any additional complexities in event reporting, either – events are written into the Application event log with the source of MSExchangeRepl and crimson channel;
- Managed Availability -In addition to improvements in various probes and monitors, there have been changes to the responder throttling framework. Prior to Exchange 2013 RTM CU2, many responders were only throttled per-server (e.g., RestartService). Now, these responders are throttled per group ;
- Cmdlet help -Exchange 2013 RTM CU2 introduces the capability for administrators to get updates to Exchange Management Shell cmdlets without needing to deploy a new service pack or cumulative update. Administrators can launch the Exchange Management Shell and run the Update-ExchangeHelp cmdlet to update their local Shell help ;
- OWA Search improvements;
- Malware Filter Rules -Exchange 2013 RTM CU2 introduces the –MalwareFilterRule cmdlets. You can use the –MalwareFilterRule cmdlets to apply custom malware filter policies to specific users, groups, or domains in your organization. Custom policies always take precedence over the default company-wide policy, but you can change the priority (that is, the running order) of your custom policies;
Setup.exe /PrepareSchema /IAcceptExchangeVersionLicenseTerms
The configuration partition in Active Directory has also been changed to reflect changes (additions) in RBAC. To update the configuration partition you can use the following command:
Setup.exe /PrepareAD /IAcceptExchangeVersionLicenseTerms
Please note that with the new Service Model from Microsoft the Cumulative Updates are now a full product with a normal setup application. CU’s will now be released on a quarterly basis. A very important yet dangerous aspect of a full product is that an upgrade will overwrite custom settings on the ‘old’ Exchange Server 2013 server. A common example of this is OWA customization. Also, there’s no roll back model. If you’re not satisfied with the latest CU there’s no way to uninstall and revert to a previous version.
As with all major changes please perform an upgrade first in a test environment and evaluate CU2 appropriately.
These are the Release Notes, the Exchange Product Group announcement can be found here and the download can be found on the Microsoft download site.