In order to simplify Exchange 2013 deployment, I created PowerShell scripts to automatically download and install software prerequisites as well as activate Windows role and features. One script has been created for Windows Server 2008 R2, another one for Windows Server 2012. For each script: Specific for Windows Server 2008 R2, a ZIP file containing […]

In order to help/assist administrators, Microsoft has published CHM file (complied help file) for Exchange 2013 http://www.microsoft.com/en-us/download/details.aspx?id=35395 2 files are available: one for hybrid deployment (don’t forget you need an Office 365 “2013 version” tenant for hybrid deployment) and one for On Premise deployment (don’t forget, if you have Exchange already deployed you need Exchange

With the coming version of Office server products, Microsoft has split Office Web Application, used to render Office document in a web browser, from SharePoint. This means Office Web Apps can now be used by other server products, such as Lync 2013 or Exchange 2013. in this post, we will see how to configure Exchange

With Office 2013, Microsoft has introduced a new way to provide add-on for Office client as well as for Exchange Web Access or SharePoint; this way is called Apps. So, with Exchange 2013, you may want to enable some apps by default to all of your users, instead of teaching them how to enable these.