Log in


Tags » ‘rollup for Exchange 2010’

Exchange 2010 RU 4 released (KB982639)!

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

Back on April 22nd you may recall an article I wrote dealing with a Bug identified with Exchange 2010 where there is a “.” in the NETBIOS name (KB981033).  Well last night the MS Exchange Team released Exchange 2010 RU 4.  As part of this rollup there is  a fix for the “.” in the NETBIOS name issue.  I noticed that it wasn’t listed in the KB Article but I did email my contact at Microsoft and he did confirm that this RU does address the “.” in the NETBIOS name.  

For all of you out there having this problem I strongly encourage you to go and get  Exchange 2010 RU 4 (KB982639) and apply it, after all, it’s what you have been waiting for!

NOTE:  For those of you who recieved the Interim Update from MS (KB981033) you will need to remove this update prior to installing Exchange 2010 RU4. 

Have a great day!

Tags:
No Comments »

Bug identified when Deploying Exchange 2010 in a domain with a ‘.’ in the NETBIOS name! (KB981033)

Categories: Exchange Server Microsoft Related
April 22nd, 2010 by Scott

I was starting to deploy Exchange 2010 for a client today that contained a ‘.’ in their NETBIOS name when I came across a bug.   The majority of organizations will deploy an Active Directory environment using a single name for their NETBIOS domain name.  For example, ’scottfeltmann.com’ would have a NETBIOS name of ’scottfeltmann’ or ‘contoso.com’ would be ‘contoso’.  

I started out by running the Exchange 2010 Pre-Deployment Analyzer Tool.  No issues discovered.  I then deployed the Client Access Server role. No errors were reported during the installation of the CAS.  Upon the completion of the installation of the role I opened up the Exchange Management Console (EMC) clicked on the ‘Microsoft Exchange On-Premises’ option and got the following error:

Initialization failed

 “The following error occurred when getting user information from ‘domain.com\username’: 

The operation couldn’t be performed because the object ‘domain.com\username’ couldn’t be found on domaincontroller.domain.com.  It was running the command ‘Get-LogonUser’.

How odd, this isn’t normal.  I haven’t seen this in any other environment, but then again, I haven’t come across a netbios name with a ‘.’ in it.  At first I checked AD for any issues, thinking maybe there was a replication problem.  I did find one small problems, resolved it, tried again, same result. 

I then turned to my friend google. 

Doing some research I came across this article with the same problem: http://www.eggheadcafe.com/software/aspnet/35384695/exchange-2010-period-in-n.aspx  a ‘.’ in the domain NETBIOS name.  Doing further digging I came across this article on StuartP’s blog which describes the issue: http://blogs.technet.com/stuartp/archive/2010/03/31/exchange-2010-and-netbios-domains-with-dotted-notations.aspx

Yup, looks like an identified bug in Exchange 2010 and it will not be fixed until Rollup 4.  I did install Rollup 3 (which was released April 9th) to see if that would help the situation but it didn’t.  I guess at this point it is a matter of waiting for Rollup 4 to be released…..Bugger!

—**UPDATE**—

Working with MS support I was informed that there is an unpublished KB article pertaining to this issue.  If you do have this problem you will need to contact MS Support and refer to KB 981033.  It is my understanding that there is a fix for Exchange 2010 RU 1 and Exchange 2010 RU 3,  I received the update for RU 3 and will be applying it to the server later today.  The size of the update was approx. 35megs. 

I need to point out that when installing this update you will need to remove it prior to deploying RU 4, which will have the fix in the RU 4 release.

Thanks MS Support for getting this guy out here!

Tags:
7 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 »