I was asked an interesting question a few weeks ago when I was a part of an vSphere infrastructure start up after a datacenter move. What basically happened was that
Problem You have OCS 2007 R1 deployed in your environment and began noticing MOC (Microsoft Office Communicator) clients display a notification: … labeled: Cannot Synchronize Address Book … with the
Problem You have OCS 2007 R1 deployed in your environment and began noticing MOC (Microsoft Office Communicator) clients display a notification: … labeled: Exchange Connection Error … with the error
Problem You noticed that after you’ve configured your Avaya AES server in the Trusted application servers node in your Lync Server 2010 topology: … you notice that legacy OCS 2007
Cisco has just released the highly anticipated 2.0 firmware for the UCS B series infrastructure on their public download site. I’m extremely excited to test it out next week!
Problem You notice that executing one of your recovery plan errors out at the Prepare Storage step with the message: Error: Reason: Could not open/create change tracking file. The logs
Problem You notice that executing one of your VMware Site Recovery Manager recovery plan errors out at the Change Network Settings step with the message: Error: Operation timed out. The
Problem You notice that executing one of your recovery plan errors out at the Prepare Storage step with the message: Error occurred: Failed to create group image: unknown exception The
