Archive for 2013

Out of Office not working when accessing Outlook using Outlook Anywhere

In the mix environment of Exchange Server 2007 and 2010, after doing cut over of Client Access Server and Hub Transport Server to Exchange Server 2010, everything was working fine, Mailflow, Outlook, OWA, FreeBusy, OOF, OAB, IMAP, POP (Internally) and Outlook, OWA, FreeBusy, OAB, IMAP, POP (Externally) except Out of Office.

I could access the FreeBusy and OAB information using Outlook Anywhere of the users on Exchange 2007 as well as 2010, but I couldn't access the OOF for any of the users when accessing it via Outlook Anywhere.
Now, to access the FreeBusy and OOF exchange uses EWS (Exchange Web Services), which was working fine, but when it comes to accessing or setting up OOF, it use to fail with the standard error. "Your Out of Office settings cannot be displayed, because the server is currently unavailable. Try again later"

We are using TMG Server 2010 to publish the exchange services like, OWA, Active Sync, Outlook Anywhere, POP and IMAP. TMG is running Active/Passive Cluster (I wouldn't do it like this). Cause you are not utilizing both the TMG server when running Active/Passive.

After spending sometime on TMG Server I found something which was kind of hard to believe. This is how you are going to fix this issue.
Open TMG Console, go to Firewall Policy, look for Outlook Anywhere Rule.

Double click on Outlook Anywhere Policy and click on Paths TAB.

Make sure that you have Internal Path for EWS is set as /ews/*
Initially this path was missing from OA Rule, after making this entry, apply the changes. Now you can set your Out of Office and it will work like a charm from Outlook Anywhere.

This is my last article and also on the last day of year 2013. I hope everyone had great 2013 year. Wishing you all Happy and Prosperous New Year 2014.


Exchange Server 2013 Service Pack 1 Coming in Early 2014

There's some good news for all of (Exchange Server Guys) us. Microsoft will be releasing SP1 for Exchange Server 2013 in 2014. I am assuming it should be in first Q of 2014.

Some of the highlight of SP1.

Windows Server 2012 R2 Support First answering one the most common questions since the release of Windows Server 2012 R2. Exchange 2013 SP1 will add Windows Server 2012 R2 as a supported operating system for Exchange Server 2013 with SP1. Let your planning begin.
S/MIME support for OWA Support for S/MIME in OWA will be brought back in SP1. With SP1 customers will have S/MIME support across Outlook, Exchange ActiveSync clients, and OWA.
Edge Transport Server Role The Edge Transport server role for Exchange Server 2013 will be available with SP1.
Fixes and Improvements Of course, SP1 will include fixes and improvements in areas you've helped us identity. SP1 is the first service pack issued in the new Exchange Server cumulative update release model - thus SP1 is essentially CU4. The installation of SP1 will follow the same process as the prior Exchange 2013 CU releases. SP1 will include all fixes included in previously released cumulative updates for Exchange 2013.


Now DirSync can be installed on Domain Controller!

Yesterday (November 4th, 2013)  Microsoft released new version of DirSync which can be now installed on domain controller. Previously DirSync couldn't be installed on Domain Controller.

Download new DirSync from here..

Reference article


Microsoft Lync Room System Administrative Web Portal

A Lync Server web component that allows IT administrators to monitor and manage their organization's Lync Room System devices.
Download from here

Supported Operating System:
Windows Server 2008 R2
Windows Server 2012

In order to use Microsoft Lync Room System Administrative Portal, you must also have the following installed:
Lync Server 2013 Cumulative Update 2


Active directory response: 00002098: SecErr: DSID-03150A48, problem 4003 (INSUFF_ACCESS_RIGHTS), data 0

Root Domain: domain.local
Domain Controllers: 3
Child Domain: abc.domian.local
Domain Controllers: 3
2 Exchange 2003 running in child domain
6 Exchange 2010 running in child domain

When trying to register/activate the license key for exchange server 2010, I was getting this error.

Now, I was able to register/activate other server without any issue in the same domain, but this one was failing. I tried Exchange Management Shell and it failed too.
This error message clearly talks about the permission issue, hence I checked the Inheritance blocked on the user account and found that it was unchecked.

Checked the check box.

Tried registering/activating the server but failed again with the same error message. I found the event ID 2080 and it has some issue with SACL rights on few domain controllers on the site.

Ran /PrepareAD to fix the SACL right's and checked the event, no changes in the event result. Waited for the replication to complete. After 20 minutes, tried to register/activate the server, not it's failing on different domain controller not the domain controller for which it was failing.

Now, I had one server activated successfully without any issue. So I went on to the server and activated all the 3 servers without any issues.
But, it's a workaround and not a resolution, cause I will get the same error when I start the migration process when moving the mailboxes from 2003 to 2010.
To check if the issue still exist, I created a Test Mailbox on 2003 and tried to move it on to 2010 server, and as expected, it failed with the same error message.

I checked the Exchange Trusted Sub System Group and Exchange Server Group and found that only one exchange server is a member of these groups not all of them.

Added all the remaining servers in both the groups.

Restarted the domain controller on which the move was failing. Moved the mailbox and it moved successfully.
As per my experience, the straight forward resolution is, Inheritance blocked should be checked. But in this case, check box was getting unchecked by itself. And I also ran the /PrepareDomain switch too, But it didn't helped.

It was the issue with AD replication and the permission issue on the user account.
Note: Still monitoring the issue, will move few mailboxes again and check the issue. Will update the post.


Error: Cannot open Service Control Manager on computer "". This operation might require other privileges.

While publishing the Topology. I got the error "Error: Cannot open Service Control Manager on computer "". This operation might require other privileges."

I checked the connectivity, server could ping each other with IP and NetBIOS name. Checked the firewall setting on both SQL and FE server.
Disabled the Firewall  on SQL server and tried Publishing the Topology and it completed successfully.


Error Parsing Kickstart Config: The provider network interface eth0 does not exist.

I was installing AsteriskNOW-3.0.0 in the LAB (Hyper-V) and got the error "Error Parsing Kickstart Config: The provider network interface eth0 does not exist."

I checked the setting in Hyper-V and the server had the Network Adapter, I restarted the process and it failed again. I checked the settings again and found that Network Adapter is selected by default.

I turned off the server and removed the Network Adapter and added the new hardware and selected Legacy Network Adapter.

After adding the Legacy Network Adapter error disappeared and installation completed successfully.
I believe the only reason it need Legacy Network Adapter and not the Network Adapter, because AsteriskNOW-3.0.0 is Linux based application.


The description for Event ID 3 from source Lync cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupt.

Environment Topology:
1 DC/GC and DNS running on Windows Server 2008 R2 with SP1
1 Lync Server 2013 installed on Windows Server 2012
1 Exchange Server 2010 SP3 with RU2
1 Client Windows 8 x64.
1 Office 2013 Lync Client and Office 2013 Basic Lync Client.
1 Certificate Authority and ADFS 2.0 Server
1 Forefront TMG Server 2010 SP2

I am not able to login to Lync 2013 client after the fresh installation of Lync Server 2013 with CU2. I am getting the error standard error message "The user name, password, or domain appears to be incorrect."

Tried with different accounts as well, but still getting the same error message. I found an update for Lync 2013 client and installed it.

After the update, tried Login, still the same error message. Now I enable the logging on the client so that it will generate the event in case of failure. I found the Event ID 3, 1 and 12.

Now as per the event, there's something wrong with the installation or the files of Lync Client 2013 which got installed. I installed the full version of Office 2013 Lync Client, now I tried with Lync Basic client and it failed with the same error message.

I decided to check the issue with Lync 2010 Client and installed the client after uninstalling the Lync 2013 client from the workstation.
Now I tried to login to the Test account and it worked, no more error with Lync 2010 client.

Resolution/Workaround: Install Lync 2010 client.
I am not sure, why is it failing to login with Lync 2013 client, I am still looking into the issue and will update the post once I find the solution.


Setup Wizard for Update Rollup 6 for Exchange Server 2010 Service Pack 2 (KB2746164) ended prematurely

While doing regular check on the exchange server environment I found the error Mailbox Role "is not configured" on server "". Please run the setup again. I had the same issue error for Client Access Server role too. Environment was running DAG with 2 member server.

I checked the store.exe version on both the servers and found that it was a mismatch.

Now to fix the issue, I ran the setup again on exch01 server and it completed successfully.
Note: exch01 server had Rollup Update 4 installed before running the SP2 setup on the server.
On other server, I had upgraded Rollup Update 6, hence I had to install the same on this server too. Started installing Rollup Update 6 for SP2 on exchange01 and it failed with the error "Setup Wizard for Update Rollup 6 for Exchange Server 2010 Service Pack 2 (KB2746164) ended prematurely".

To fix this issue, what I had to do was, to run the this file as "Run as Administrator". Hence, opened Command Prompt with "Run as Administrator" and copied the path and pasted in it and pressed the Enter Key. Setup took time but it failed again with Rolling Back message and finally the above error message.

Disabled the UAC on the server and restarted the server, ran the setup again and it failed with the same error.
Checked the ExecutionPolicy on PowerShell and it was restricted. Set the ExecutionPolicy as Unrestricted and ran the setup again, but it failed again.
Added the Administrator account in security on PowerShell key in registry "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\PowerShell. Restarted the server and ran the setup still No Go. Checked the setup but didn't find anything, nothing in Event viewer.
I had seen this issue before but those resolutions weren't working here.

Uninstalled the entire exchange server and reinstalled it, tried to install Update Rollup 6, still it failed.

Unbelievable resolution in my case was "Disable the Windows Firewall on the server" run the setup and it completed successfully.

Weird as I didn't had to do it before to install the Update Rollup and on other Active Server, it got installed successfully without making any changes.


Cumulative Update 2 for Exchange Server 2013 (KB2859928)

Cumulative Update 2 for Exchange Server 2013 resolves issues that were found in Exchange Server 2013 CU1 since the software was released. This update rollup is highly recommended for all Exchange Server 2013 customers.

Download CU2 from here


Test Lab Guide: Configure an Integrated Exchange, Lync, and SharePoint Test Lab

The paper describes how to configure a test lab consisting of servers running Exchange Server 2013, Lync Server 2013, and SharePoint Server 2013 by using five server computers and two client computers. After verifying that all three types of servers are working, you then configure server-to-server trust relationships between them. The resulting test lab can be used as a basis for scenarios and solutions that use a combination of Exchange Server 2013, Lync Server 2013, and SharePoint Server 2013, and Microsoft Office 2013.

Hardware and software requirements

The following are required components of the test lab:

The product disc or files for Windows Server 2012. For an evaluation copy, see Download Windows Server 2012 in the TechNet Evaluation Center.
The product disc or files for Windows 8. For an evaluation copy, see Download Windows 8 Enterprise Evaluation.
The product disc or files for Microsoft SQL Server 2012. For an evaluation copy, see SQL Server 2012 Evaluation.
The product disc or files for Exchange Server 2013. For an evaluation copy, see Download Microsoft Exchange Server 2013.
The product disc or files for Lync Server 2013. For an evaluation copy, see Download Microsoft Lync Server 2013 Evaluation.
The product disc or files for SharePoint Server 2013. For an evaluation copy, see Download Microsoft SharePoint Server 2013.
Five computers that meet the minimum hardware requirements for Windows Server 2012.
Two computers that meet the minimum hardware requirements for Windows 8.

Download Test Lab Guide


Five Exchange 2013 migration gotchas to watch for

Exchange Server 2013 is a bigger, more complex platform that leaves behind some of the legacy Exchange features in favor of new ones along with better overall reliability. Before upgrading to the latest version, it's important that you're aware of a few factors that will help ensure a successful migration.
Exchange 2013 migration gotcha #1: Clients
Just as Exchange 2010 removed support for Outlook 2000, Exchange 2013 removes support for Outlook 2003. When it comes to Exchange 2013, you must use Outlook 2007, Outlook 2010 or Outlook 2013. Outlook 2007 must run Service Pack 3 along with the November 2012update or later, while Outlook 2010 must run Service Pack 1 along with the November 2012update or later.
When patching clients, consider Windows Server Update Services. You can also use the Microsoft Assessment and Planning toolkit, as well as the Get-LogonStatistics cmdlet in Exchange 2007 and the Exchange Server User Monitor (ExMon) in Exchange 2010.
And it's not just Outlook you need to worry about. With Exchange 2007, users could experience Outlook Web Access in all its glory with a version of Internet Explorer as low as IE6. In Exchange 2010, the minimum version required to experience the Premium Outlook Web App is IE7. Therefore, it shouldn't surprise anyone that IE8 is necessary for Exchange 2013. At the time of writing, however, IE8 suffers from performance issues when runningOutlook Web App 2013, so consider IE9 the baseline. It will give users the best OWA 2013 experience on Vista and above.
For Windows XP and other operating systems, third-party browsers like Firefox (v17+), Chrome (v24+) and Safari (v6+ on Mac) also provide great support for Exchange 2013. Check out the table of supported clients on Microsoft's TechNet site for the most up-to-date information.
Exchange 2013 migration gotcha #2: Outlook Web App redirection
This one affects companies migrating from Exchange 2007 that use forms-based authentication (FBA) within Exchange. Previously, when a company migrated from Exchange 2003 or Exchange 2007 to Exchange 2010, legacy coexistence with FBA worked very well. When a user logged into OWA, he was redirected to the legacy server, and the username and password were passed along with the redirection request.
In a coexistence scenario with Exchange 2007 and Exchange 2013 (using FBA) the username and password are not passed when an Exchange 2007 user logs in. The user is redirected to an Exchange 2007 server and is forced to log on a second time. If you're expecting a lengthy coexistence period, look into how you'll work around this issue.
If you already use Forefront TMG 2010 to perform pre-authentication and forms-based authentication, you're free to continue using it. Alternately, various third-party load balancers provide built-in pre-authentication support.
All this said, if you've already implemented Windows Integrated Authentication for Outlook Web App logins, you won't be affected.
Exchange 2013 migration gotcha #3: Outlook Anywhere
All communication for Outlook clients with Exchange 2013 use HTTPS rather than the combination of RPC/MAPI and HTTPS used in previous versions. Specifically, this means that Outlook Anywhere  is used for internal clients as well as external clients. Mailboxes that still reside on Exchange 2007 and/or Exchange 2010 during the coexistence period will continue to connect internally via traditional RPC/MAPI.
If your organization uses Outlook Anywhere externally, ensure that Outlook Anywhere is also enabled on Exchange 2007 and/or Exchange 2010. This is because Exchange 2013 will proxy Outlook Anywhere requests to the version of Outlook Anywhere that corresponds to the version of Exchange Server the mailbox is on.
It's not quite as simple as just enabling Outlook Anywhere or leaving it enabled. You must make sure that NTLM authentication at the IIS level is enabled for both Exchange 2007 and Exchange 2010.
One more thing when it comes to Outlook Anywhere: If the Exchange 2007 servers that run Outlook Anywhere are also running the client access server and mailbox server roles -- and not a Global Catalog server -- you must disable IPv6, as detailed in knowledge base article 2794253
Exchange 2013 migration gotcha #4: Sizing and performance
Performance and sizing can certainly prove a contentious aspect of any Exchange 2013 migration. Deployment guidance was released in May 2013, meaning early deployments that didn't benefit from Microsoft's assistance needn't re-evaluate their specifications. Others have been incorrectly looking at existing Exchange 2010 sizing guidance to provide a high-level view of what hardware they need, with some making the mistake of doubling RAM and CPU.
If you've done this, don't panic, but realize you may need to buy additional hardware. Exchange 2013 sizing is fundamentally different and it's not as easy as giving it a bit more power. Instead, you need to re-think the best way to deploy Exchange 2013.
JBOD (just a bunch of disks) is a great option for many customers, thanks to the auto-reseed features, which allow for massive disk savings. The Exchange Product Group also advocates the use of "building blocks," which are servers that only have local storage. For example, you may have 12 internal four TB disks as your Exchange Server base. Consider using these, rather than expensive add-on arrays. You might end up with a smaller user count per-server, but you'll use fewer disks and benefit from improved reliability.
As with any Exchange Server 2013 implementation, a critical step is using JetStress to ensure that the storage subsystem is capable of handling the expected load. JetStress has been updated for Exchange 2013 and is available to download -- but watch out. If you're new to JetStress or looking to follow Microsoft best practices, be warned that the updated version of the JetStress Field Guide has not yet been released.
Additionally, LoadGen, the complementary tool that helps test a real-world simulation of activity has not been released either. Therefore, if these tools are essential to your deployment, you may have to hold tight -- at least for the time being.
Exchange 2013 migration gotcha #5: Ambiguous namespaces and Exchange 2010 migrations
What exactly are namespaces? Well, in the context of Exchange Server, they are the names used to connect to Exchange both internally and externally using HTTPS, as well as connect to Outlook clients internally using RPC/MAPI.
During the coexistence period of any Exchange 2010 to Exchange 2013 migration, you'll need to update the DNS entries for your InternalURLs and ExternalURLs to point at your Exchange 2013 infrastructure. Clients with Exchange 2010 mailboxes will have HTTPS services proxied to the Exchange 2010 servers behind the scenes.
An Exchange implementation that follows Microsoft's recommendations will use a single set of names for both internal and external HTTPS URLs (for example, and a separate name for the RPC client access array (for example, outlook.contoso.local). When the HTTPS name is moved to Exchange 2013, the RPC client access array name remains on Exchange 2010.
There's a gotcha here for organizations that have implemented namespaces incorrectly. Some Exchange 2010 implementations use an external HTTPS namespace (again, call it but internally, use the same name for both the internal URLs and RPC client access array (for example, using for RPC/MAPI and services like OWA).
When you move the internal name to Exchange 2013, you'll break existing Outlook client connectivity. The trick here is to update your internal HTTPS URLs to use the external HTTPs URLs. You may want to consider potentially implementing split DNS or pinpoint DNS in the process.
A small number of organizations have implemented a single name, both for internal and external HTTPS URLs and the RPC client access array. If this describes your setup, you likely need to change your RPC client access array name to something unique. Unfortunately, this does not automatically propagate to clients and you may need to either force Outlook clients to update, or do as Microsoft suggests and move internal Outlook clients on Exchange 2010 to Outlook Anywhere.
Final thoughts
Some of these gotchas might sound like serious problems, but don't let them deter you. Armed with the right information, you can easily complete a successful Exchange 2013 deployment.
Steve Goodman


Top Three KEMP LoadMaster options & things to be aware of when using them

The following is a list of top three KEMP LoadMaster options and things to be aware of when configuring these options on the LoadMaster appliance (virtual or hardware) in a network infrastructure. In particular, the options that will be discussed in detail are: Transparency, High Availability, and Bonding. The goal of this document is to educate an end user with the best approach for when configuring these options as to avoid any possible first time setup/deployment issues with the LoadMaster.
  1. Transparency
  2. High Availability
  3. Bonding/VLAN’s


Exchange and Lync Server Videos from TechEd, North America 2013, New Orleans

Here are some of the technical videos on exchange and lync servers which took place @ TechEd, North America 2013, New Orleans.

Monitoring Microsoft Lync Server 2013: Getting the Most out of Monitoring Service Data
Designing for High Availability and Disaster Recovery in Microsoft Lync Server 2013
Microsoft Exchange Server 2013 Managed Availability
Microsoft Exchange Server 2013 Client Access Server Role
Migration and Coexistence with Microsoft Lync Server 2013
Microsoft Exchange Server 2013 High Availability and Site Resilience
Microsoft Exchange Server 2013 On-Premises Upgrade and Coexistence
Enterprise Network Requirements for Microsoft Lync Server 2013
Microsoft Exchange Server 2013 Sizing
Planning and Deploying Your Enterprise Voice
Planning and Deploying Your Enterprise Voice
Deep Dive into New Unified Communications Web API of Lync 2013
Data Loss Prevention in Microsoft Exchange and Microsoft Outlook 2013
Team Collaboration with Site Mailboxes
Microsoft Exchange Archiving Policy: Move, Delete, or Hold
Planning and Deployment for Edge Server with Microsoft Lync Server 2013
The Deep Dark Secrets of Unified Messaging
Microsoft Lync Server 2013 Dial Plan and Voice Routing Deep Dive
All about Archiving with Microsoft Lync Server 2013
The New Outlook Web App: Designed for Touch and Offline Too!
Scripting and Automation for Microsoft Lync
Introducing Lync Room System


Update Rollup 1 for Exchange Server 2010 SP3

Microsoft has released Update Rollup 1 for Exchange Server 2010 SP3. You can download it from here
Below are the some of the fixes included in Update Rollup.

  1. Mailbox storage limit error when a delegate uses the manager's mailbox to send an email message in an Exchange Server 2010 environment
  2. You cannot open a mailbox that is located in a different site by using Outlook Anywhere in an Exchange Server 2010 environment
  3. Mailbox synchronization fails on an Exchange ActiveSync device in an Exchange Server 2010 environment
  4. Rapid growth in transaction logs, CPU use, and memory consumption in Exchange Server 2010 when a user syncs a mailbox by using an iOS 6.1 or 6.1.1-based device
  5. Unable to soft delete some messages after installing Exchange 2010 SP2 RU6 or SP3
Fifth issue was holding back lots of organization for SP3 upgrade.

Lync Conference 2013

Check these video if you have missed the conference. You can find from level 100 to level 400 topics covered.

Lync Conference 2013 Videos


Error while enabling Windows feature: NetFx3, Error Code: -2146498298

I was doing SQL server 2012 installation for my lync server 2013 lab and I ran into this error "Error while enabling Windows feature: NetFx3, Error Code: -2146498298, Please try enabling Windows feature: NetFx3 from Windows management tool and then run setup again."

Installation Error

Started the server manager and tried to install the .Net Framework 3.5 with SP1 and it failed with error “Do you need to specify an alternate source path? One or more installation selections are missing source file on the destination

Now the only choice I had was to install .Net Framework 3.5 was using Deployment Image Servicing and Management (DISM). For more information on DISM, refer to this article. I tried to install it using DISM by running the command dism /Online /Enable-Feature /FeatureName:NetFx3 /Source:D:\sources\sxs but it failed with below error.

As it say “Error itself has solution in it” indeed it had the solution. I just had to modify the command and run it with /all switch like this, dism /Online /Enable-Feature /FeatureName:NetFx3 /All /Source:D:\sources\sxs and it will complete successfully, as you can see.
Note: Make sure you have Windows Server 2012 media in the drive before you run this command.

After this SQL Server 2012 installation completed like a charm :)

Continued my Lync Server 2013 installation and completed with Archiving and Monitoring server roles.


Command execution failed: Error Constructing or Publishing Certificate

I came across with this error "Command execution failed: Error Constructing or Publishing Certificate" when requesting certificate from internal CA server for Lync server 2013 running on windows server 2012.

After digging into the issue and the error I found that I will have to restart the Active Directory Certificate Services on CA server. Looked into application log and found the event id 53.

I checked and found that Active Directory Certificate Services service on CA server service is already running.

Now I just had to restart Active Directory Certificate Services service. After restarting the service, request the certificates again from Lync server and it will complete successfully.


Microsoft Exchange 2013 Public Folders Directory Sync Support Scripts

Microsoft has recently released "Microsoft Exchange 2013 Public Folders Directory Sync Support Scripts". Scripts to enable creation of public folder related objects in the O365 Active Directory and synchronization of public folder related Active Directory objects between on-premise and O365 directories.

Download from here...

Use this scripts if you need to do one of the following - - Initial creation of mail enabled public folder objects in the destination Active Directory for public folder migration from Exchange 2007 or 2010 to Exchange 2013 - Synchronization of mail enabled public folder objects from cloud to on-premise Active Directory - Synchronization of mail enabled public folder objects from on-premise to cloud Active Directory - Synchronization of public folder mailbox objects from cloud to on-premise Active Directory.


Exchange 2010 datacenter switchover tool (process) now available

Exchange 2010 includes a feature called Datacenter Activation Coordination (DAC) mode that is designed to prevent split brain at the database level during switchback procedures that are being performed after a datacenter switchover has occurred. One of the side benefits of enabling DAC mode is that it enables you to use the built-in recovery cmdlets to perform the datacenter switchover and switchback.

You can download it from here
Note: It's not exactly a tool but a power point guide to help you perform the switchover correctly with all the cmdlets.


Lync Server 2013 Stress and Performance Tool

The Lync Server 2013 Stress and Performance Tools (LSS) can be used to prepare, define and validate performance targets of user scenarios of an on-premise Lync Server 2013 deployment. LSS includes multiple modules and can simulate simultaneous users on one or more Lync Servers. In the 2013 version, video support was added and provisioning and configuration tools are improved.

Download it from here

The Lync Server 2013 Stress and Performance Tool (LSS) is capable of simulating user load of the following types:
  • Instant messaging (IM) and presence
  • Audio/Video/Multi-View conferencing
  • Application sharing
  • Voice over IP (VoIP), including public switched telephone network (PSTN) simulation
  • Web Access Client conferencing
  • Conferencing Attendant
  • Response Groups
  • Distribution list expansion
  • Address book download and address book query
  • E911 calls and Location Profile
The tool does not simulate the following clients:
  • Microsoft Office Live Meeting 2007
  • Microsoft Office Communications Server 2007 R2, Group Chat Console


Exchange Reports for Exchange 2010, 2013 and Office 365

Introducing Exchange Reports
You can download it from here
This application requires .Net 4.0, Powershell 2.0 and Remote Powershell access to Exchange Server. It is tested on Windows 7, Windows 8 and Windows 2008 R2.

Yet, it's still in beta. I tested in my LAB and it's pretty good. List of reports you can get from this tool:
Group Report
Single Group Information
Mailbox Report
Single Mailbox information
Message Tracking
Admin Audit Log (coming soon)
Mailbox Audit Log (Coming soon)
Environment Report (Coming soon)

Here is how Mailbox report looks like.

Update: 06|03|2013
Email notification feature will also be included in coming update.


Installing Exchange Server 2010 SP3 on Windows Server 2012

Not much has changed when you install exchange server 2010 SP3 on windows server 2012. You need to make sure that .Net Framework 4.5 update is installed and windows is up to date.
And if you don't installed the updates, prerequisites will failed with error, few components can't be installed or missing.

Prerequisites for windows server 2012 hasn't changed much.
Note: You don’t need to run “Import-Module ServerManager” as windows server 2012 loads the modules automatically. If you don't have internet connection to you lab machine, then run the prerequisites script with -Source D:\sources\sxs at the end of the script and make sure you have windows server 2012 media in the DVD drive.

Add-WindowsFeature NET-Framework-Core,RSAT-ADDS,Web-Server,Web-Basic-Auth,Web-Windows-Auth,Web-Metabase,Web-Net-Ext,Web-Lgcy-Mgmt-Console,WAS-Process-Model,Web-Mgmt-Tools,Web-ISAPI-Ext,Web-Digest-Auth,Web-Dyn-Compression,NET-HTTP-Activation,Web-Asp-Net,Web-Client-Auth,Web-Dir-Browsing,Web-Http-Errors,Web-Http-Logging,Web-Http-Redirect,Web-Http-Tracing,Web-ISAPI-Filter,Web-Request-Monitor,Web-Static-Content,Web-WMI,RPC-Over-HTTP-Proxy -Restart

Once it's installed. You are all set to install exchange server 2010 SP3

I must say exchange 2010 SP3 is faster, smarter and better on windows server 2012 :)


Microsoft Exchange Server 2010 SP3 and RU 10 for Exchange Server 2007 SP3 for full coexistence with Exchange Server 2013

Microsoft has released Service Pack 3 for Exchange Server 2010 and Update RollUp 10 for Exchange Server 2007 SP3 today.

These updates will make your existing Exchange 2010 and 2007 environment to coexist with Exchange Server 2013.
Exchange Server 2010:
Microsoft Exchange Server 2010 Service Pack 3

Issues that the service pack resolves

Exchange Server 2007:
Update Rollup 10 for Exchange Server 2007 Service Pack 3

Issue that the update rollup resolves

Note: Microsoft also released Update Rollup 6 for Exchange Server 2010 SP2.
Update Rollup 6 for Exchange Server 2010 Service Pack 2

Issue that the update rollup resolves

I would strongly suggest not to install SP3 for Exchange 2010 right now, instead play around with RU6 in the LAB first and then install it in the production. Do the same for SP3 as well.
Install the SP3 after enough testing in the LAB.

We all have been waiting for these release since few months and finally Microsoft has delivered it. Now, this is were the FUN begins.

Update: 15-02-2013
We still can't coexist exchange server 2010 SP3 with Exchange Server 2013 entirely. Cumulative update (CU) is required for Exchange 2013 for coexistence between Exchange 2010 SP3 and Exchange 2013. The change to the cumulative update model, from the past rollup update model, was just announced last Friday.

We should expect the CU for Exchange Server 2013 in the month of April or late March. Let's keep the finger cross.

Gulab Prasad

Install and Configure GFI MailArchiver for Exchange Server 2010- Part 2

In first article we learned how to install GFI MailArchiver for Exchange Server 2010. Now we will configure the MailArchiver (default configuration).

Click on Configure button after installing the MailArchiver.

Next, enter the product key which you received, either for evaluation or full license and click Next.

Next step is configure the archive store settings.

Note: At this step we have several options to choose the storage, I am going to choose the last one, GFI MailArchiver Database. Because at this time I don't have SQL Server installed in the environment. I will configure the MailArchiver with Microsoft SQL Server in different articles.

Enter Admin Login name and Password and click Next. Click next and next on coming 2 steps.

Now it's time to configure Archiving method, there are 2 type of methods available. 1: Manual Archiving and 2: Auto-Archiving (Journalling). Journalling has 2 sub options, A: All email and B: Role Based Archiving.

I am going to demonstrate second option, Auto Archiving in this article and Manual Archiving in coming articles.

First option will be selected by default "Let GFI MailArchiver create new journalling user for you to associate the mailboxes to.

Enter the admin credential and click on next, next and finish.

We have configured GFI MailArchiver successfully with default settings. Next article we will see how MailArchiver works and restore the email from the MailArchiver.

Gulab Prasad