Communicator sip DNS issues

A couple of months ago, I stood up an Office Communications Server and it's been running flawlessly.  We mainly use it for the IM functionality but eventually I'd like to see us take advantage of all the other features.  Looking through my event logs today I notice the following entries:  

Event ID 3:

Communicator was unable to resolve the DNS hostname of the login server sipexternal.acme.com.

Resolution:

If you are using manual configuration for Communicator, please check that the server name is typed correctly and in full.  If you are using automatic configuration, the network administrator will need to double-check the DNS A record configuration for sipexternal.acme.com because it could not be resolved.

After doing some googling around I came across Jeff Schertz Blog DNS Lookups with OCS Automatic Configuration, which he basically confirms the event log entry (good job on the error logging Microsoft!).  Looking at my DNS server, I notice the sip CName missing.  I checked the certificate SAN to confirm what should be listed, then added the record and now my machine is able to resolve sip.acme.com.  Lesson of the story is make sure DNS is flawless inside and out.  DNS=Lifeblood of AD.

Hyper V Failed to add device "Microsoft Synthetic Ethernet Port"

So I came across a need to user Hyper V at one of our remote locations which has a box running Windows Server 2008 64bit.  I added the Hyper V role and launch it only to find out that the packaged version is a pre-release and that I needed to update.  So I ended up having to install the update (Get it here: http://support.microsoft.com/kb/950050) which, after installing requires a reboot......so many reboots...anyhow...I digress.  After the reboot I fire up Hyper V...cool.  Looks straight forward.  I plow through the wizard and at the last step which is creation, I get hit with the error: "Failed to add device "Microsoft Synthetic Ethernet Port".  After surfing around a bit, I found that this is caused by anti-virus software settings on the directory.  We use trend micro but apparently Forefront causes the same issue.  I would not be surprised if others fit the bill.  As soon as I excluded the directory where the VHD is stored as well as *.xml files, the VM wizard completed successfully.