Missing

A client had errors in Outlook after migrating to Exchange 2013, and Outlook did not show the OAB URL in autodiscover information.   Here is what we did :   Get-offlineaddressbook | fl WebDistributionEnabled,VirtualDirectories,Identity If you have WebDistributionEnabled set to False and/or no value defined for VirtualDirectories (as shown below) this is why you have the issue To solve this issue, run the following command Get-ClientAccessServer | Get-OabVirtualDirectory | fl identity to get... [Lire la suite]

Hello everybody! This post was inspired by a gifted user (in this story I will call her Barbara Streisand), who opened a ticket asking about some missing email sent to him by a colleague (Park Jae-Sang) but that she has never seen in his mailbox. And the more PSY is sending her email, the less she can read them!! How crazy!! You know, apart when you find a bug, email flow is the main business of Exchange, so it’s almost impossible that an email is not delivered without any notification to the sender…   --> Please see the... [Lire la suite]

One of the things that has always been missing from VMware’s High Availability solution stack is application awareness. As I explained in one of my earlier posts this is something that VMware is actively working on. Instead of creating a full App clustering level VMware decided to extend “VM Monitoring” and created an API to enable App level resiliency. At VMworld I briefly sat down with Tom Stephens who is part of the Technical Marketing Team as an expert on HA and of course the recently introduced App Monitoring. Tom explained me... [Lire la suite]

It is possible under Hyper-V to get into a state where you have a virtual machine that is still running correctly - but does not show up in the virtual machine list under the Hyper-V management console.  The two most likely causes for this are: The virtual machine management service (VMMS) is not running.  If this is the case you will not see any virtual machines (or interact with the server in general).  You can fix this by just starting the VMMS again (run "net start vmms" from an administrative command... [Lire la suite]