Out-of-Office Not Working in Outlook 2007 or Outlook 2010

Outlook Out-of-Office Not working

Outlook Out-of-Office Not working

Out-of-Office Not Working in Outlook 2007

The Microsoft Exchange server version does not matter. It can be Exchange 2010 or exchange 2007, Outlook out-of-office functionality doesn’t work. The user profile for Outlook sets up fine without error but when the user tries to setup Out-of-office emails, they cannot. What can make this an even more peculiar case is that some users on the same network connected to the same exchange server and using the same version of Outlook out-of-office works fine. To make it even more interesting, setting up a different user on the same computer, meaning a user who has not signed in on that computer before, works fine too.

In such a case, the interesting fact to find out is if the user had used Microsoft BPOS or Microsoft Hosted Email services. This problem was found for users at an organization who had used Microsoft BPOS service in the past and not have migrated to their own exchange server.
The solution for my company was the following registry settings had to be changed back to their defaults. Microsoft BPOS changed service these values form their defaults.


The above registry settings are telling Outlook to NOT use Autodiscover and to instead use a local XML file to tell it how to connect to the Exchange server.

Change all the 00000001 to 00000000 . All the values should be zeros.

This worked perfectly. We were able to even do a remote regedit to remotely access the registry and to support it, didn’t even have to remote control the user’s computer desktop. Instead of even remote controlling users computers because there are multiple to many computers to do, you can use login scripts to accomplish the task.


Simple Basic Cisco QoS for IP Phone System to IP Phone System Garbled Voice

Sample Cisco QoS for IP Phone System to IP Phone System to Solve Distorted Voice Quality

On a Cisco 1841 router located at a remote office, there was need to clear up garbled voice. The garbled unclear voice occurred on nearly all phone conversations. The station sets at the remote office were digital handset but the phone system was IP based.
The simple solution for this problem was to implement QoS on the router to prioritize the voice packets that were sent in and out of the router.

Cisco Remote Office Router – QoS class-map, policy-map, and access-list on router for Voice Quality

This required a simple access list that contained both phone systems ip addresses and then a class-map and policy-map on the router.
The policy map is applied to an interface.

First in configuration mode of the router create the access list. The access list basically lists our phone system ip addresses. Replace the ip addresses shown below with the ip addresses of your phone system.

access-list 101 permit ip any host
access-list 101 permit ip any host

Next, create a class map. This is basically a map of the match criteria. In it we add “match access-group 101. 101 is the access list that contains our phone systems’ ip addresses.

class-map match-any IPPhoneSys-to-IPPhoneSys
match access-group 101

Then, the class-map is applied to the policy map. The policy map can contain many class-maps. So in other words, it’s like a list of class-maps. It’s applied to an interface.

policy-map QoS_Policy_Priority
class IPPhoneSys-to-IPPhoneSys
bandwidth percent 20
class class-default

Once the above configuration is complete, re-check your ip address for accuracy and apply the policy map to an interface. The wan interface will work fine. In this example it was a legacy point-to-point T1 that connected the two offices. Yours may differ.

On the router change to the interface level commands by entering the interface on which you plan to apply the QoS policy map.

In this example it is a serial interface for the t1

config# interface serial0/0/0

Then run the command to apply the policy on the interface

service-policy output QoS_Policy_Priority

The above simple Cisco Modular QoS solution cleared the voice issues immediately.
In the example above the bandwidth reserved was 20 percent. You can change that percentage to fit your environment.

VMWare vpxd Failed To Initialize.

Recreating or Resetting the vCenter Server embedded DB2 database repository for the vCenter Server Appliance 5.0 solved the problem. 

VPXD Failed to Initialize


Waiting for vpxd to initialize

After importing the ovf file in vmware for Vcenter Server appliance, the vmware-vpxd failed to initialize. One of the most simplest causes for this if this is a new vcenter server is the time and timezone not matching the host on which the vcenter server is operating on does not match. You may have to deploy another vcenter server virtual appliance to get around that. You can try the following fix if you continue to have a problem after you have set the time and timezones to match and re-deployed a new vcenter server.

Resetting the database worked to solve the problem for a vCenter Server version 5 installation.  This was done after the time matched and the correct timezone was set.

You can reset the embedded DB2 database through the:
  • Web Console
  • Command line

The command line method does not reset the license. At a command prompt on the vcenter server enter the following :

As mentioned, this method does not remove license key information from the vCenter Server database.
To reset the embedded DB2 database:
  1. SSH or open a virtual machine Console to vCenter Server Appliance and log in as root.
  2. Run the commands:
    • # service vmware-vpxd stop
    • # /usr/sbin/vpxd -b
    • # service vmware-vpxd start
    • service vmware-vpxd statusFor example:vmware-vpxd is running
      tomcat is running