Exchange 2007 - End of Life

March 6, 2017 at 9:08 AMSaso Erdeljanov

Just a reminder to everyone still using Exchange 2007 in production environment. We are approaching End of Live for Exchange 2007 on April 11, 2017. Please consider upgrading to newer version very very fast. :)


You can read more at Microsoft Support web site.

Exchange 2007 End of Life Roadmap

Posted in: Exchange | Microsoft | Unified Communications | EoL


Issue after installing MS13-061 security update on Exchange 2013

August 15, 2013 at 10:50 PMSaso Erdeljanov

Microsoft temporary removed MS13-061 security update for Exchange Server 2013 due to bug with content index. After installation you will notice Content Index for mailbox databases failed and service Microsoft Exchange Search Host Controller service is renamed.

For customers that already deployed updated, Microsoft provided KB article with steps to resolve issue.

Update 2874216 breaks the content index in Exchange Server 2013

After you install update 2874216, you experience the following issues in Microsoft Exchange Server 2013:

The content index (CI) for mailbox databases shows "Failed" on the affected server.
The Microsoft Exchange Search Host Controller service is missing.
You see a new service that is named "Host Controller service for Exchange."



Update 2874216 breaks the content index in Exchange Server 2013

Exchange 2013 Security Update MS13-061 Status Update

Updates for Exchange 2007, 2010 and 2013 (+security fixes!)

August 13, 2013 at 8:08 PMSaso Erdeljanov

Microsoft just released a bunch of updates for Microsoft Exchange Server 2007, Exchange Server 2010 and Exchange Server 2013. It’s important to deploy updates since they contain security fixes.

Update Rollup 11 for Exchange Server 2007 SP3
Update Rollup 7 for Exchange Server 2010 SP2
Update Rollup 2 for Exchange Server 2010 SP3
Exchange Server 2013 RTM CU1 MSRC Security bulletin MS13-061
Exchange Server 2013 RTM CU2 MSRC Security bulletin MS13-061


Microsoft Security Bulletin MS13-061 - Critical



Exchange 2007 Rollups

The Exchange 2007 SP3 RU11 update contains two fixes in addition to the changes for MS13-061. For more details, including a list of fixes included in this update, seeKB 2873746 and the MS13-061 security bulletin. We would like to specifically call out the following fixes which are included in this release:

  • 2688667 W3wp.exe consumes excessive CPU resources on Exchange Client Access servers when users open recurring calendar items in mailboxes by using OWA or EWS
  • 2852663 The last public folder database on Exchange 2007 cannot be removed after migrating to Exchange 2013


Exchange 2010 Rollups

The Exchange 2010 SP2 RU7 update contains the changes for MS13-061.  For more details, see the MS13-061 security bulletin.

The Exchange 2010 SP3 RU2 update contains fixes for a number of customer-reported and internally found issues, as well as, the changes for MS13-061. For more details, including a list of fixes included in this update, see KB 2866475 and the MS13-061 security bulletin. We would like to specifically call out the following fixes which are included in this release:

  • 2861118 W3wp.exe process for the MSExchangeSyncAppPool application pool crashes in an Exchange Server 2010 SP2 or SP3 environment
  • 2851419 Slow performance in some databases after Exchange Server 2010 is running continuously for at least 23 days
  • 2859596 Event ID 4999 when you use a disclaimer transport rule in an environment that has Update Rollup 1 for Exchange Server 2010 SP3 installed
  • 2873477 All messages are stamped by MRM if a deletion tag in a retention policy is configured in an Exchange Server 2010 environment
  • 2860037 iOS devices cannot synchronize mailboxes in an Exchange Server 2010 environment
  • 2854564 Messaging Records Management 2.0 policy can't be applied in an Exchange Server 2010 environment


Exchange Server 2013

MS13-061 is the first security update released for Exchange Server 2013 utilizing the new servicing model.  MS13-061 is available as a security update for:

Important: If you have previously deployed CU2, you must ensure you are running build 712.24 in order to apply the security update. For more information about build 712.24, please see Now Available: Updated Release of Exchange 2013 RTM CU2.


External links & downloads:

Update Rollup 11 for Exchange Server 2007 Service Pack 3 (KB2873746)

Update Rollup 7 for Exchange Server 2010 Service Pack 2 (KB2874216)

Update Rollup 2 For Exchange 2010 SP3 (KB2866475)

Security Update For Exchange Server 2013 CU1 (KB2874216)

Security Update For Exchange Server 2013 CU2 (KB2874216)

Released: Update Rollups for Exchange 2007 & Exchange 2010 and Security Updates for Exchange 2013

Updated Release of Exchange 2013 RTM CU2

July 31, 2013 at 2:41 PMSaso Erdeljanov

Due to issue with the loss of public folder permissions Microsoft updated Exchange Server 2013 CU2 update (build number 15.0.712.24).

If you have already deployed original CU2 (build number 15.0.712.22), you should upgrade to 15.0.712.24 (potential security updates released for CU2 will be dependent on this build).

You can upgrade to CU2 (.24) via GUI interface or execute setup.exe /m:upgrade /IAcceptExchangeServerLicenseTerms from command line.

Download: Cumulative Update 2 for Exchange Server 2013 (KB2859928) – Build Number 15.0.712.24

Edge Planning Tool for Office Communications Server 2007

August 25, 2008 at 2:57 PM2102

Another great tool from OCS team!

The Edge Planning Tool for Microsoft Office Communications Server 2007 provides settings for configuring your perimeter network based on information that you provide to the tool.

The Edge Planning Tool asks questions about your proposed or current edge server deployment. The tool uses your answers and Microsoft Office Communications Server 2007 best practices to generate the following reports:

  • Settings that you can use to configure your certificates, DNS services, and firewalls.
  • Custom documentation for configuring your edge servers, reverse proxy, and next hop server.
  • A comparison of your answers to Microsoft Office Communications Server 2007 best practices.




Source: Edge Planning Tool for Office Communications Server 2007

Designing you DMZ network for OCS 2007

June 29, 2008 at 2:43 PM2102

What is the right/recommended design of our DMZ (perimeter) network for OCS 2007 Edge implementation? This is usually quite common question whenever I have conversation with someone that is in the phase of designing/implementing their OCS 2007 infrastructure.

Microsoft just released new whitepaper. Happy reading! ;-)

Designing Your Perimeter Network for Office Communications Server 2007 White Paper

Brief Description
This paper answers questions about Microsoft® Office Communications Server 2007 with specific regard to its integration into the perimeter network (also known as DMZ, demilitarized zone, or screened subnet).

The first section, “Commonly Asked Questions,” answers key design questions from customers about the initial stages of product deployment.

The second section, “Architecture and Networking Best Practices,” explores ways to prepare for the edge servers in the perimeter network, taking into consideration issues of physical deployment, ways to ensure a publicly routable IP address, firewall configuration, and load-balancing concerns.

Microsoft Response Point

April 11, 2008 at 10:24 AM2102

Microsoft Response Point is IP PBX and VoIP PBX solution  for Small Business Phone Systems with up to 50 users.

Response Point was launched in March 2007, with phones being made available towards the end of 2007.

What is Response Point?
Easy to use and manage, Microsoft Response Point is innovative new phone system software that offers small business customers a radically simplified phone experience. You can access the phone and its features using just your voice. The intuitive Response Point administrator software allows you to complete phone moves, additions, or changes with a few mouse clicks. And there is no special phone training or networking expertise required. For a small business owner, Response Point offers a complete phone system—at an affordable price—that grows with your business.

What makes Response Point different from PBX systems?
Response Point is an advanced phone system that radically simplifies the total phone experience for small businesses. Response Point supports both Voice-over Internet Protocol (VoIP) and analog telephone lines, comes with built-in voicemail, and includes a breakthrough voice-activated user interface designed to give small businesses all the phone capabilities they need—in a single, easy-to-install box. Response Point also enables a small business to manage its phone system in-house, helping to eliminate the need for specialized IT support to implement such things as staffing-related moves, additions, or changes.

What size of small business benefits most from Response Point?
Response Point can benefit small businesses with as few as one employee to as many as 50 employees, and it can grow with your business. Response Point is optimized for small businesses and organizations that need powerful telephony features, but aren't large enough to justify a dedicated IT staff. Businesses with more than 50 employees and a full-time IT staff are likely to consider additional features.

What features does Response Point offer that go beyond a standard phone system?
Response Point transforms phone system management and user experience from end to end.

  • Response Point brings top-quality speech-recognition to the phone experience, allowing users to embrace phone features that were previously cumbersome or complicated to use. Just say, "Transfer my call to Joe," instead of memorizing the right call-transfer keystrokes and Joe's extension number. Call anyone in the company, or any of your Microsoft Office Outlook contacts, just by saying a name.
  • Response Point offers a helpful, Automated Receptionist that is fully customizable (you can record your own voice and company message), and includes the ability to add FAQs about your business (e.g., your hours, location, etc.). Callers need only speak their desired party's name and they will be transferred to that extension.
  • Administrators can easily complete moves, additions, and changes with a few simple mouse clicks. The whole system can be managed by an average PC user, rather than a phone networking specialist.

How does Response Point benefit mobile information workers?
Response Point benefits mobile workers in several ways. First, it allows users to easily forward their office extensions to external lines, so callers don't have to guess whether they are in the office or not. Second, Response Point lets users retrieve and archive voicemail messages in e-mail. Windows Mobile users have found this particularly useful, since they can get instant notification of new voicemails and easily retrieve any message—new or archived—from nearly any location. Third, Response Point gives users access to all their Office Outlook contacts from almost any phone, via voice commands. And these calls can be connected over a Voice-over Internet Protocol (VoIP) line. To enable VoIP service, customers should obtain an integrated access device from their service provider and plug it into the Response Point base unit.

How much will Response Point systems cost?
Customers can purchase a starter pack, featuring one base unit, a four-port ATA, and four to five phones for around $2,500 at manufacturer's suggested retail price (MSRP). Additional phones will cost $139—$159 MSRP each. A typical complete 20-phone system will cost less than $5,500 MSRP.

Microsoft Response Point vs. Office Communications Server 2007 (OCS 2007)

Both systems are VoIP related and both come from Microsoft and this is almost the only thing they have in common and are built on two very different platforms. Microsoft Response Point runs on Windows XP Embedded using solid state memory (no hard disk). Microsoft Response Point is designed for SMB looking for simple solution with great productivity enhancement (speech recognition, voice to mail,...).

Office Communications Server 2007 requires  a lot prerequisites such as Active Directory, IP PBX, Exchange Server 2007 and requires multiple servers. Prerequisites and knowledge are not the only factors. License costs are also high for this kind of environment and usually not acceptable for company with 50 employees.



Posted in: VoIP | Microsoft | Unified Communications


SLOWUG - Exchange Server 2007 Security

March 6, 2008 at 1:57 PM2102

Yesterday, I was presenting at SloWUG event about Exchange Server 2007 Security.

Presentation with all recorded demos is now available for download.

SloWUG - Exchange Server 2007 Security Presentation

Voice Ignite II - Paris

March 6, 2008 at 1:49 PM2102

OCS2007Last week I was attending Voice Ignite II in Paris. The training has been extended from 2 days (Ignite I) to 5 days consisting of presentations, labs and make it real. Overall experience was great!


Cheers to everyone I met there (Rok, Jose, Vincent, Thomas Lee,...)!

Here are some pictures from Paris:






Posted in: Microsoft | Unified Communications


Exchange 2007 SP1 Install Error on Windows Server 2008 RC1

January 20, 2008 at 12:20 PM2102

This is one "simple" error I come across when installing on Windows Server 2008 RC1.

Process MSEXCHANGEADTOPOLOGYSERVICE.EXE (PID=1976). Topology discovery failed, error 0x80040a02 (DSC_E_NO_SUITABLE_CDC). Look up the Lightweight Directory Access Protocol (LDAP) error code specified in the event description. To do this, use Microsoft Knowledge Base article 218185, "Microsoft LDAP Error Codes." Use the information in that article to learn more about the cause and resolution to this error. Use the Ping or PathPing command-line tools to test network connectivity to local domain controllers.


In my case solution was really simple. Between the tests I disabled IPv6 support on network card. I enable it back, re-run setup and everything was fine...