New hotfix for Remote Assistance with Windows 7 DirectAccess clients!

I’m happy to announce we have just released a new hotfix specifically for Remote Assistance on Windows 7 DirectAccess clients!  I’ve actually encountered this issue with a few DirectAccess deployments and some of you have dropped comments asking about a solution.

The core of the issue is that Remote Assistance in Windows 7 would only listen on IPv6 addresses that started with a “2” or “3” as their first IPv6 nibble.  For example 2001:0::1 or 3000:0::1 would be some examples of IPv6 addresses that would work with Remote Assistance.  For new installs of Windows 2012 or Windows 2012 R2 DirectAccess, the setup wizard will check to see if you have IPv6 already deployed in your internal network.  Most environments are not running IPv6 internally so the DirectAccess install will configure an IPv6 prefix in the Unique local IPv6 range (FD00::/8) automatically.  Since the IPv6 addresses start with the nibble character “F”, this prevents Remote Assistance from working with Windows 7 clients without the hotfix below.  There were some workarounds but none of them were easy for most administrators to configure without some IPv6 knowledge.

You will need to install this hotfix on any Windows 7 DirectAccess client you want to use with Remote Assistance.  This is not needed on the DirectAccess server itself.


Tags: , , , , , , , , , , , , , , ,

Categories: Troubleshooting DirectAccess

6 Comments on “New hotfix for Remote Assistance with Windows 7 DirectAccess clients!”

  1. Christian Skoglund
    March 6, 2014 at 01:19 #

    Is the hotfix available for Windows 8.1 as well? I have the same problem there

    • March 6, 2014 at 11:17 #

      Hello Christian,

      This should be released with this month’s Windows updates for 8.1. I’ll reply back with the KB number when it’s released next week.

      • Matt
        March 20, 2014 at 21:21 #

        I’ve got the same issue on Windows 8.1 but can’t see it addressed in the March 2014 updates. Any idea how to get the hotfix?

      • March 27, 2014 at 18:17 #

        Hi Matt,

        I’m looking into this and will reply back when I get the answer from the Windows product group.

      • March 28, 2014 at 20:46 #

        HI Matt,

        I checked and it should be releasing on 8.1 with next month’s patches (April). Sorry for the confusion!

      • April 11, 2014 at 11:03 #

        Hi Matt,

        Good news, I can confirm this hotfix was included in this month’s Windows 8.1 update :

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: