two extra strength sominex does provigil make you smart provigil patient assistance forum which is stronger ritalin or provigil

Exchange 2013

Remove Dead Exchange Servers from Active Directory

Working with  my Exchange 2012 Hybrid configuration I into the following error:

ERROR : Subtask NeedsConfiguration execution failed: Configure MRS Proxy Settings

Execution of the Get-WebServicesVirtualDirectory cmdlet has thrown an exception. This may indicate invalid parameters in your hybrid configuration settings.

The task wasn’t able to connect to IIS on the server ‘exchange’. Make sure that the server exists and can be reached from this computer: The RPC server is unavailable.

This is because I did not properly remove the retired exchange servers form Active Directory during past migrations to Exchange 2013.

To remove these objects to continue with your Hybrid configuration task do the following:

  1. Launch the run dialog (Windows Key + R)
  2. Type in the command “adsiedit.msc” and press OK
  3. In the drop down menu select “Configuration”
  4. Expand “CN=Configuration [domain]\CN=Services\CN=Microsoft Exchange\CN=[organization]\CN=Administrative Groups\CN=Servers”
  5. Right click on the dead server and “Delete”
  6. Navigate to ”CN=Configuration [domain]\CN=Services\CN=Microsoft Exchange\CN=[organization]\CN=Administrative Groups\CN=Databases”
  7. Right click on each dead database and “Delete”

Step 1-5 will get you past the Hybrid error, but you might as well cleanup while your here.

Cumulative Update 6 for Exchange Server 2013

I’ve been working with the Microsoft team on several issues I have faced with my Exchange Hybrid deployment.

Most recent issue: HCW Serialization Error

Today I am informed that Cumulative Update 6 for Exchange Server 2013 was just released.

Cumulative Update 6 for Microsoft Exchange Server 2013 was released on August 26, 2014. This cumulative update resolves a list of issues.


Download Here


Exchange Server 2013 SP1

If your following my posts you may notices I touched on a bug with Exchange 2013 SP1 before even posting about this update. That’s because I started to write this and didn’t yet finish; better late than never; I guess!

The following enhancements have been made with the release of Service Pack 1 for Exchange 2013

  • Support for running Exchange 2013 SP1 on Server 2012 R2.
  • Support for Windows Server 2012 R2 Domain Controllers and Windows Server 2012 R2 Forest and Domain Functional Level.
  • MAPI over HTTP. More information on MAPI over HTTP here. Note that MAPI over HTTP requires Outlook 2013 SP1; you can download Office 2013 SP1 32-bit version here and the 64-bit version here.
  • DLP policy tips for OWA.
  • Add custom document types to DLP using fingerprinting technologies.
  • Cmdlet logging in Exchange Administrative Console.
  • Support for IP-less DAGs (on Windows Server 2012 R2).
  • S/MIME support.
  • Rich-Text editor for OWA.
  • Edge Transport server role.
  • Support for SSL Offloading.

Since the release of Microsoft Exchange Server 2013 Service Pack 1 (SP1), Microsoft has become aware of an issue that affects some customers who use transport agents that are provided by third-party OEMs. For more information about this issue and a supported fix, see the following Microsoft Knowledge base article:

2938053 Third-party transport agents cannot be loaded correctly in Exchange Server 2013

This service pack resolves the issues that are described in the following Microsoft Knowledge Base (KB) articles:

  • 2860242 HTML format is lost after saving as an MSG file in Exchange 2013
  • 2900076 Mailbox quota warning message uses an incorrect language in Exchange Server 2013
  • 2910199 “Reply all by IM” chat window displays seven recipients in Outlook Web App
  • 2913999 Meeting request body and instructions are lost in delegate’s auto-forwarded meeting request
  • 2918655 Microsoft.Exchange.Servicehost.exe crashes after you enable FIPS
  • 2918951 Users cannot access public folders after you upgrade to Exchange Server 2013 Cumulative Update 3
  • 2925281 Outlook connectivity issue if SSLOffloading is “True” in Exchange 2013
  • 2925544 Empty ExternalURL value for ActiveSync virtual directory after build-to-build upgrade of Exchange Server 2013
  • 2927708 Resource mailboxes that are created by EAC will not be updated by policies in Exchange Server 2013
  • 2928748 Default from delegate’s address in shared mailboxes in Exchange Server 2013
  • 2928803 Long server connection for Outlook after a database failover in Exchange Server 2013
  • 2930346 POP3 access does not work if the name of the resource mailbox differs from the user’s name
  • 2930348 Manual redirection occurs in Outlook Web App if External URLs in each site are the same
  • 2930352 Outlook Web App cross-site silent redirection does not work in Exchange Server 2013

Exchange Server 2013 SP1 Transport Service Issues

I recently updated Exchange Server 2013 CU3 to Exchange Server 2013 SP1. The update seemed to go smoothly however I discovered that external emails were not flowing. Oddly enough outbound emails worked just fine.


  • No inbound email being processed by Exchange 2013 SP1.
  • You also notice the following loged in the Application Event Logs:
    Source: MSExchangeFrontEndTransport 
    Event ID: 7012
    Description: The service state for frontend transport is inconsistent. Current state – Inactive. Expected state – Active.


Transport agent failure caused email to stop being processed. I later found the following post regarding the issue: [E2013][TA] Exchange 2013 SP1 transport agent “type not found” issue


To resolved this issue (in my case). I needed to restart the Microsoft Exchange Frontend Transport service.  *note* restarting the transport service alone will not solve this.


  • Avoid updating service packs for several months until all the bugs are worked out and known
  • If you are updating, be prepared to face the unknown


Microsoft has just officially confirmed the existence of this issues in Exchange Server 2013 SP1:

I must note that I am not using any third-party agents.

Possible solution to the lsass Issue – event 1000 application error

Back in July of 2013 I faced an issue with my Exchange 2013 Server running on Microsoft Server 2012.

Our server would unexpectedly reboot ( — chuckles  — aren’t all reboots without notice unexpected).

The message I kept running into was regarding a faulting application which caused the reboot was the local security authority subsystem service (LSASS).

What’s known about the lsass.exe is that if it is stopped it will result in causing your system to reboot. LSASS also handles the validation of user logins on a Windows Computer / Server.

As I mentioned in my previous blog post:

There was an event message in the system event log of: 

The process wininit.exe has initiated the restart of computer EXSERVER on behalf of user for the following reason: No title for this reason could be found

Reason Code: 0×50006
Shutdown Type: restart

Comment: The system process ‘C:Windows\system32\lsass.exe‘ terminated unexpectedly with status code 255. The system will now shut down and restart.

 Later I found in the application log event 1000 application error:

Faulting application name: lsass.exe, version: 6.2.9200.16384, time stamp: 0x50108ab2
Faulting module name: schannel.DLL, version: 6.2.9200.16384, time stamp: 0x5010892c
Exception code: 0xc0000409
Fault offset: 0x000000000001a73a
Faulting process id: 0×224
Faulting application start time: 0x01ce7f8a27d7e7ff
Faulting application path: C:Windowssystem32lsass.exe
Faulting module path: C:Windowssystem32schannel.DLL
Report Id: c2142447-f4f2-11e2-9404-000c299625b9
Faulting package full name:
Faulting package-relative application ID:

The Exception code: 0xc0000409 only tells me that the application experienced an event it could not handle and crashed causing windows to reboot.

Months of searching forums and discussing this with systems administrators from all over the word we all determined that there was no clear regarding how to handle this issue.

Today I got an email regarding a solution for this problem:

There seems to be a solution in the form of roll-up update from Microsoft to address this along with other issues which are also listed in the following KB articles:

2732840 Tasklist.exe tool displays no process information on a computer that is running Windows
2785146 Data is corrupted when there is insufficient memory on a Windows-based computer

2789397 Data corruption and network issues when you run a WFP-based application on a computer that is running Windows

2792867 Virtual switch extension cannot send packets over different network adapters in Windows Server 2012

2793908 Memory leak occurs in the Wmimgmt.exe process on a computer that is running Windows Server 2012

2796620 Application that uses the DirectComposition API does not work correctly in Windows RT, Windows 8, or Windows Server 2012

2798040 You cannot stop a process by using the Taskkill.exe utility in Windows

2800086 Windows Store apps can’t connect to the Internet over PPPoE in Windows 8

2800185 Windows Error Reporting reports a crash when you shut down a computer that is running Windows RT, Windows 8, or Windows Server 2012

2809153 Sound is not playing from the paired Bluetooth audio device after you reconnect the device to a Windows 8-based or Windows RT-based computer

This update roll-up also includes the following performance and reliability improvements:

  • Increased power efficiency to extend battery life
  • Performance improvements in Win 8 applications and Start screen
  • Improved audio and video playback in many scenarios
  • Improved application and driver compatibility with Windows 8

Here are two links to articles to  send you on your way.  I will follow up soon on my findings after this has been applied.

I would like to thank all of you who have commented about this issue via Email, Twitter, Google+ and Facebook