Log in


Tags » ‘Upgrade’

Datacenter Activation Coordinator Changes in Exchange 2010 SP1!

Categories: Exchange Server Microsoft Related
June 8th, 2010 by Scott

For the past few days I have been down in New Orleans taking in all the valuable information at TechEd and meeting some great people. 

So far it has been a great experience.  Last night I happened to go to the Exchange Round table that was hosted by Jeff Guillet from EXPTA.Com (Great guy btw).  While at the meeting some of the Microsoft Exchange Team happened to come to participate in the discussion.  I had the privilege of speaking with some members on the Exchange team (Smart Guys, if I get nothing more out of TechEd it was worth just the time to hang out with some of the guys on the Exchange Team) and they shared some information with me about Exchange 2010 Service Pack 1, which was totally legal since it was released to the public yesterday.

As you recall I wrote an article back on November 18th called “Managing Split Brain in Exchange 2010 DAG with Datacenter Activation Coordination Mode” and as mentioned in that article there was a restriction on how to use DAC in an environment.  If you look back at the article you will note that you can only use DAC if the following is true:

 1. You need to have at least three database copies to use DAC.  This means that you would require three separate servers. 

2.  That you could not leverage DAC  if the DAG members existed in the same Active Directory Site.

Well, after my conversation last night it was mentioned to me that the requirements above are no longer requirements in Exchange 2010 SP1!  What this means is that with Exchange 2010 Service Pack 1 you can now leverage DAC with only two database copies (2 servers in a DAG)!  He also mentioned to me that on top of that neat feature above that you can also leverage DAC within a single Active Directory Site!  Whoa, Even better!  This now will give organizations the ability to deploy a HA environment with 2 database copies AND leverage DAC thus preventing a split brain scenario which was a risk with the RTM version of Exchange with two database copies.  Now that is awesome! 

What I was not able to find out was the release date of Exchange 2010 SP 1.  I am well aware that the beta is out (Exchange Server 2010 SP1 Beta Now Available for Download) but it is not quite ready for production. 

Hope this helps!

Tags:
2 Comments »

Update Rollup 2 for Exchange Server 2010

Categories: Exchange Server Microsoft Related
March 5th, 2010 by Scott

The Microsoft Exchange Team has announced the release of Update Rollup 2 for Exchange Server 2010.  For the announcement go here: http://msexchangeteam.com/archive/2010/03/05/454155.aspx

Some key fixes are: 

  • KB 977633 This fixes IMAP4 clients ability to log on to their mailboxes if the mailboxes are located on Exchange 2003 backend servers and if the clients are connecting via Exchange 2010 CAS servers.
  • KB 979480 IMAPid was not working correctly after moving a lot of users from one Exchange 2010 server to another*. IMAP4 users complained about the inbox not being updated any more. Old messages were still visible, but messages which were received after the mailbox move were not visible. The problem affected different IMAP Clients. The problem did not affect MAPI clients and OWA. Now it is fixed up. *(Specifically this occurred in the situation with same DAG, now local storage instead of iSCSI storage, all servers are Exchange 2010 with Update Rollup 1 installed on Windows Server 2008 R2).
  • KB 979431 When user migrated from Exchange Server 2003 to Exchange Server 2010, and that user connected via POP3, the POP3 service crashed. This was fixed up so it will not crash.
  • KB 979563 Push Notifications didn’t work because Exchange Server 2010 was not sending SOAPAction header in the notify callback. This caused Exchange to receive a HTTP 500 response from the notification client and the webservice failed. Push notifications should now properly send that SOAP header.
  • KB 980261 We fixed passive page patching when diagnostic tracing code was needed for forensic analysis that was generating a -1022 error case.
  • KB 980262 Source side log copier errors are more gracefully handled when the log has a bad block and the read fails.
  • KB 979566 Activesync proxy was failing for linked mailboxes in a CAS to CAS proxy scenario where the users token is serialized and sent in the request. When attempting to create the client security context from the SID, a AuthZException was thrown because we did not have access to the token information of the linked account, so now for this it no longer throws exceptions.

    • For more information on the Hotfix you can go to the page at http://support.microsoft.com/?kbid=979611.

    Enjoy!

    Tags:
    No Comments »

    Exchange 2007 SP2 Failed because of ‘beremote’

    Categories: Microsoft Related
    November 6th, 2009 by Scott

    I was upgrading Exchange 2007 with Exchange 2007 SP2 on a client exchange server this evening and came across the error “Setup cannot continue with the upgrade because the ‘beremote’ () process (ID: 1876) has open files.  Close the process and restart Setup.

    The problem was a result of having Veritas Backup installed on the Exchange 2007 server.  The service “Backup Exec Remote Agent for Windows Servers” was locking the process and preventing the Exchange 2007 SP2 setup from running.  I had to go into Services and stop the “Backup Exec Remote Agent for Windows Servers” service.  Once I stopped this service I was able to proceed with the installation of Exchange 2007 SP2.

    Tags:
    2 Comments »