Forefront UAG ISATAP hotfix KB977342 – ISATAP addresses not created for the VIP address

Recently Microsoft released a hotfix for Forefront UAG and applies to multiple Forefront UAG server scenario configured in an Array configuration.

Link Local ISATAP addresses are not created for the virtual IP address used by the Network Load Balancing (NLB) feature on a computer that is running Windows Server 2008 R2. This hinders the usage of NLB nodes as an ISATAP router.

This problem occurs because the IP Helper service does not let virtual IP address interfaces generate ISATAP tunneled addresses or 6to4 tunneled addresses as designed. For the DIP address ( Dedicated IP ) you will have an ISATAP address available but for the VIP ( Virtual IP ) there is no possibility of having Global Addresses support for the NLB VIP address ( Virtual IP) and no ISATAP addresses can be configured for a VIP.

More information can be found here

Reporting Data Warehouse Management Server is currently unavailable #sysctr

Scenario

I’m using Service Manager 2010 SP1 administrator console (7.0.6555.115) managing Service Manager 2010 SP1 (7.0.6555.115) from my personal laptop which isn’t member of the domain where Service Manager resides in.

Problem Description

We noticed that when you’re opening the Service Manager Administrator console a massage box pops up saying the Reporting Data Warehouse Management Server is currently unavailable. This behavior also occurs on domain joined workstations.

Both Reporting and Data Warehouse ‘wunderbars‘ are not shown. Normally this might indicate the Data Warehouse server is unavailable. This behavior can have several reasons (network, SQL, etc.) but when available both ‘wunderbars‘ appears automatically within time. But unfortunately not in our scenario.