Exchange Server Pro » Hyper-V

TechEd Video: Exchange 2010 Virtualization

Paul Cunningham — Mon, 03 Oct 2011 10:20:43 +0000

Here are videos for two sessions from TechEd 2011 that go hand in hand. Both are about Exchange 2010 virtualization, and worth watching if you’re still considering whether to virtualize some or all of your Exchange Server 2010 deployment.

Get more Exchange Server tips at ExchangeServerPro.com

NLB Cluster Fails with Status Code 0x8004100a on Hyper-V Guest

Paul Cunningham — Sat, 04 Sep 2010 14:42:18 +0000

When configuring a new Windows Network Load Balancing cluster using Hyper-V guest machines you may encounter the following error.

Update failed with status code 0x8004100a

To resolve this error enable MAC spoofing on the properties of the virtual network adapter for the Hyper-V guest machine.

Get more Exchange Server tips at ExchangeServerPro.com

Exchange 2010 Management Console Initialization Failed

Paul Cunningham — Mon, 14 Dec 2009 12:00:42 +0000

I encountered this problem shortly after installing a second Exchange Server 2010 server into my organization. Initially I thought that this second server had caused the problem but on further investigation I found out the real culprit.

The initialization error I was receiving when opening the Exchange Management Console was:

Initialization Failed: Connecting to remote server failed with the following error message: Access is denied.

The Event Log of the server had this error:

Log Name:      Application
Source:        MSExchangeSA
Date:          13/12/2009 8:22:28 PM
Event ID:      9385
Task Category: General
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      ex1.exchangeserverpro.local
Description:
Microsoft Exchange System Attendant failed to read the membership of the universal security group ‘/dc=local/dc=exchangeserverpro/ou=Microsoft Exchange Security Groups/cn=Exchange Servers’; the error code was ’8007203a’. The problem might be that the Microsoft Exchange System Attendant does not have permission to read the membership of the group.

If this computer is not a member of the group ‘/dc=local/dc=exchangeserverpro/ou=Microsoft Exchange Security Groups/cn=Exchange Servers’, you should manually stop all Microsoft Exchange services, run the task ‘add-ExchangeServerGroupMember,’ and then restart all Microsoft Exchange services.

I double checked the “Exchange Servers” group in Active Directory and confirmed that the two servers were already in there.

I then found this error in the Event Log of the server:

Log Name:      Application
Source:        MSExchangeIS
Date:          13/12/2009 9:14:29 PM
Event ID:      5003
Task Category: General
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      ex1.exchangeserverpro.local
Description:
Unable to initialize the Information Store service because the clocks on the client and server are skewed.   This may be caused by a time change either in the client or the server, and may require a reboot of that computer.   Verify that your domain is properly configured and is currently online.

As we know a time sync problem will cause Kerberos authentication issues. I checked and sure enough the clocks on the Exchange servers were out by more than 5 minutes from the domain controllers.

The reason for this was that my Exchange servers were hosted on a Hyper-V server that is not synced to the same time source as the domain controllers which are hosted on a separate VMware ESX server. Normally the Exchange servers would still sync their time with the PDC-E for their domain but the Hyper-V integration settings were overriding this.

Clearing the Time Synchronisation option and then running net time /set on the two Exchange servers brought their clocks back into sync with their domain controllers.

Restarting the servers then allowed all of the Exchange services to come online properly again, and the intialization error no longer occurred when launching the Exchange Management Console.

Get more Exchange Server tips at ExchangeServerPro.com

Steve Riley on hypervisor attacks

Paul Cunningham — Fri, 05 Sep 2008 07:42:15 +0000

You have to ask: is there malware on my system? You can be 100 per cent certain there is no malware that you can detect, but less than 100 per cent certain that there is no malware at all. Now, ladies and gentlemen, isn’t this true of every computer we already have? There is no difference just because it’s virtualisation.

Read the entire article at ZDNet.

Get more Exchange Server tips at ExchangeServerPro.com

Exchange Server 2007 is now supported for hardware virtualisation

Paul Cunningham — Fri, 22 Aug 2008 10:00:19 +0000

We’ve been virtualising Exchange Server 2007 since it was first released but this week Microsoft has announced their official support policies for virtualised Exchange environments. It is a bit heavy on the Hyper-V but also references the list of support partners for non-Microsoft hardware virtualisation. When I checked this earlier in the week VMWare was a notable absence but today Dugie confirmed for me that they’ve been added to the list, which now stands as follows:

Cisco Systems, Inc.
Citrix Systems, Inc.
Novell, Inc.
Sun Microsystems
Unisys Corp.
Virtual Iron Software
VMware, Inc.

If you’re planning an Exchange Server 2007 deployment using a virtualisation platform be sure to read Microsoft’s recommendations for sizing virtual machines.

Get more Exchange Server tips at ExchangeServerPro.com

Flashy graph proves Microsoft virtualisation more cost effective than VMWare

Paul Cunningham — Mon, 25 Feb 2008 00:02:47 +0000

You can’t argue with this Dan.

Source

Get more Exchange Server tips at ExchangeServerPro.com

Exchange Server Pro » Hyper-V

TechEd Video: Exchange 2010 Virtualization

Related posts:

NLB Cluster Fails with Status Code 0x8004100a on Hyper-V Guest

Related posts:

Exchange 2010 Management Console Initialization Failed

Related posts:

Steve Riley on hypervisor attacks

Related posts:

Exchange Server 2007 is now supported for hardware virtualisation

Related posts:

Flashy graph proves Microsoft virtualisation more cost effective than VMWare

Related posts: