30 avril 2012

Exchange 2010 Mailbox : Can't install mailbox role due to "ANR isn't supported Error"...

Mailbox Role Failed Error: The following error was generated when "$error.Clear(); $name = [Microsoft.Exchange.Management.RecipientTasks.EnableMailbox]::DiscoveryMailboxUniqueName; $dispname = [Microsoft.Exchange.Management.RecipientTasks.EnableMailbox]::DiscoveryMailboxDisplayName; $mbxs = @( get-mailbox -Filter {name -eq $name} -IgnoreDefaultScope -resultSize 1 ); if ( $mbxs.length -eq 0) { $dbs = @(get-MailboxDatabase -Server:$RoleFqdnOrName -DomainController $RoleDomainController); if($dbs.Length -ne 0) { $mbxUser =... [Lire la suite]
Posté par jcdemarque à 16:06 - - Permalien [#]
Tags : , , , , , , ,

03 mars 2012

Retour sur l'incroyable panne d'Azure, le cloud de Microsoft : vers de lourdes conséquences ?

Ce 29 février, Azure, le cloud de Microsoft, a été victime d'une panne mondiale qui a duré plusieurs heures. Retour sur cette affaire ahurissante, qui pourrait avoir un impact majeur sur le déploiement en entreprise du cloud computing, voire de Windows 8... L'affaire a fait grand bruit mercredi : ce 29 février 2012, Windows Azure a connu une panne de grande ampleur qui a privé les utilisateurs répartis sur toute la planète d’une partie de leur service cloud. Selon les explications fournies sur le Windows Azure Blog par Bill Laing,... [Lire la suite]
Posté par jcdemarque à 22:01 - - Permalien [#]
Tags : , , , , ,
21 septembre 2011

vSphere 5.0 + View 5.0 vMotion Fail

There is a bug in the way the object buffer cache size is calculated for vMotion. This bug only appears with Hardware version 8 virtual desktops with large screen resolutions, however only if 3D is disabled. When 3D is enabled ESxi5 takes the necessary screen objects into account in the calculations and allocate sufficient buffer for vMotion to succeed. But with 3D disabled it doesn’t calculate the values correctly for the buffers. This is will impact any VM with large screen size. If you have a peek at my previous post you will be... [Lire la suite]
Posté par jcdemarque à 18:13 - - Permalien [#]
Tags : , , , , , , , , ,
23 décembre 2010

Resolving WinRM errors and Exchange 2010 Management tools startup failures

EDIT 12/10/2010: Added a permissions section. As was discussed in the previous (related) blog post "Troubleshooting Exchange 2010 Management Tools startup issues", in Exchange 2010 the Management tools are dependent on IIS. As was discussed in that blog, we have seen situations where the management tool connection to the target Exchange server can fail, and the error that is returned can be difficult to troubleshoot. This generally (but not always) happens when Exchange 2010 is installed on an IIS server that is already... [Lire la suite]
Posté par jcdemarque à 14:52 - - Permalien [#]
Tags : , , , , ,
26 octobre 2010

Did you know? All hosts failed…

Today I received a very valid question around a full cluster failure. What happens when all the hosts in a cluster go down and at some point return? Will the VMs be restarted and what do I need to have in place to ensure they will? It seems to be an urban myth that you need to use “auto-start” for a full cluster failure. But as you might have noticed that won’t work when HA is enabled. So what will? VMware HA Is it really that simple? Yes it is! When a full cluster fails and nodes start powering up HA will restart the VMs. As... [Lire la suite]
Posté par jcdemarque à 07:38 - - Permalien [#]
Tags : , , , , , , , ,
12 octobre 2010

vCenter Service fails after upgrade to 4.1

Run the scripts attached to the article linked below before upgrading to vCenter Server 4.1. If you have already upgraded, this article provides detailed workaround steps if you are experiencing the issue. 1026688 SymptomsVirtualCenter Service fails after upgrading to vCenter Server 4.1. You see this error in the vpxd logs:Panic: Win32 exception: Access Violation (0xc0000005)   Read (0) at address 0000000000000098   rip: 000000014071edcc rsp: 000000000419c700 rbp: 000000000419e160   rax:... [Lire la suite]
Posté par jcdemarque à 15:25 - - Permalien [#]
Tags : , , , , , , ,
27 novembre 2009

Upgrading ESX 4.0 to 4.0 Update 1 on HP Proliant systems can fail or time out and leave the host in an unusable state

!!! Dont update to ESX 4U1 if you are running HP !!! Upgrading ESX 4.0 to 4.0 Update 1 on HP Proliant systems can fail or time out and leave the host in an unusable state if the host has HP Insight Management Agents running SymptomsOn HP Proliant systems, when attempting to upgrade ESX 4.0 to ESX 4.0 Update 1 (U1), you may experience these symptoms: Upgrade operation may fail or hang and can result in an incomplete installation Upon reboot, the host that was being upgraded may be left in an inconsistent state and may... [Lire la suite]
Posté par jcdemarque à 15:38 - - Permalien [#]
Tags : , , , , , , , ,
25 mars 2009

VMware HA failure got you down?

Comment résoudre les problématiques de HA Agent sur un cluster VMWare.... Consider yourself lucky if you’ve never gotten the VMware HA message: An error occurred during configuration of the HA Agent on the host. But if you have, you may know that the ways to fix the error are extremely limited. Here is a method that worked for me. Current methods The current methods of troubleshooting this issue involve checking that the DNS is working properly, that the FT_HOSTS file in /etc/opt/vmware/aam is properly written for the hosts... [Lire la suite]
Posté par jcdemarque à 19:06 - - Permalien [#]
Tags : , , , , ,