Your computer is not configured correctly for Directaccess. IPV6 is not enabled correctly

Posted by Ahmed Nabil In | 0 comments»
Few users reported recently that their DirectAccess is not working on their Laptops and its displaying the message "your computer is not configured correctly for directaccess. ipv6 is not enabled correctly"

I checked DirectAccess Group policy and the Machine certificate and they were all fine. Its mainly IPV6 in question. Microsoft added native support for IPV6 and its enabled by default starting from Windows Vista and Server 2008. Some users try to disable IPV6 by unchecking the IPV6 option/check box from the Network card properties however this won't disable IPV6.

Microsoft released several Fixit (One click file) to enable, disable or give preference for IPV6 on IPV4 or vice verse instead of digging deeply in the registry to enable or disable IPV6.

Please check these several Fixit on

In our case IPV6 was disabled and need to be enabled either by using one of the Fixit provided in the link above or by checking the registry as follows:

  1. Locate the following Registry key  HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip6\Parameters\
  2. Check for  DisabledComponents under the above key.
  3. To Enable IPV6 make sure this key has value of Zero or just delete it. If it has any other value IPV6 won't work correctly.

Hopefully this can help anyone encountering the same issue.

Power/Shutdwon button missing from my Surface Pro 3 Start Screen

Posted by Ahmed Nabil | 0 comments»
I noticed on my Surface Pro 3 device that it doesn't have the Power/Shutdown Button on the Start Menu. This Surface is fully patched with Windows 8.1 Update 1 and all other subsequent updates.

My Surface device was upgraded from the Windows Professional version to the Enterprise version and I was suspecting that its a Windows issue till I came to a recent KB by Microsoft that its not enabled on Surface Pro 3 and it will mainly depend on the device Hardware not the Windows OS.

Note: An entry of "Slate" in the Device Type column means that the hardware reported a Power Platform Role of PlatformRoleSlate. To determine what a system is reporting, run the powercfg /energy command and check the Platform Role in the output.

According to the above mentioned table Surface Pro 3 will not have a Power Button on the Start Screen.

To customize or change this behavior by adding the power button you will need to follow the following steps:

  1. Open the Registry (regedit)
  2. Navigate to HKEY_CURRENT_USER
  3. Create a new Key and name it "Launcher"
  4. In the Launcher key create new DWORD value named Launcher_ShowPowerButtonOnStartScreen
  5. Right click on the new DWORD - Properties
  6. Change the Decimal Value to 1 (0=default which means it won't appear)
  7. Reboot the machine

This issue was weird since Surface Pro 2 will get this Power button. Anyways hopefully this blog post can clear this issue.

Microsoft Minimal Server Interface tips, tricks and common tasks

Posted by Ahmed Nabil In | 0 comments»
Microsoft started back with Windows Server 2008 offering the server core interface versus the normal full GUI interface. Server core is server installation with No GUI and just normal command prompt as your interface. The main idea is to reduce the attack surface on Microsoft servers by removing all GUI options, Internet explorer..........etc which have been the target of several attacks during the last couple of years.

By default when you install the full blown server (Full GUI) you get the binaries and files of all features and services even if you are not using them. Server Core limits the roles and features installed (You can't install all roles on server core) and it strips any service or feature that is not needed by the core networking roles allowed on the Windows core version.

Starting with Windows server 2012 Microsoft introduced an intermediate solution which is the windows server  with minimal interface. Its an intermediate option between Full Windows GUI and Server core. Its not an option wen installing (you only get option for Windows server with GUI or Windows Core).

In order to configure your server with minimal interface you will either install server core then add features on it or install the Full GUI windows server then remove the Graphical Shell using the Remove Roles and Features Wizard as shown below.

This will remove the server graphical shell and Internet Explorer which will enhance the server safety and reduce the security attack surface and at the same time give you the command prompt (You get in server core) plus the Server Manager which is an added value for people who didn't like the pure server core with just bold command prompt.

Warning: You might have installed 3rd party software or special Microsoft application that depend on the server graphical shell. When you do the uninstall it will warn you. Also you may run Whatif option from the powershell if you are not sure what might be affected as shown below.

Uninstall-WindowsFeature Server-Gui-Shell -WhatIf

To check Windows Server Installation options, please refer to the following link

Common Scenarios after you go for the server with minimal interface:

1. What if you mistakenly closed the CMD Prompt and/or Server Manager? How can you get them back ?

If you are connected physically on the server you can hit ALT+CTL+Del and then open Task Manager or if you are connected remotely (RDP/MSTSC) then you need to press CTL+ALT+END or Shift+CTL+ESC to open Task Manager then Click Run New Task under File Tab

Now you can type CMD or Server Manager to open them back.

2. How to run Windows Update on the server with minimal interface?

Since the control panel is not available in the windows with minimal interface we can use the sconfig.cmd from the command prompt as follows:

  • Type sconfig.cmd in the CMD prompt
  • When you get the below window, type 6 and press enter to search for updates then type "A" to download all updates and follow the next steps.

3. How to Log off, Reboot or Shutdown the Minimal Interface server ?

  • This can be done from the SCONFIG.CMD mentioned in the earlier Scenario. You have option "13" to Restart the Server and option "14" to Shutdown the server.
  • From a Normal Command Prompt you can shutdown or Reboot the server using the "Shutdown" Command. The below example will reboot the computer (/t switch) after 0 seconds.

Hopefully this post will be informative for the ones looking to tighten their servers security by moving to minimal interface.

Windows Media Player 12 Crash with EMET 5.0

Posted by Ahmed Nabil | 0 comments»
I am currently running Microsoft EMET (Enhanced Mitigation Experience Toolkit) version 5.0 (Latest Version) with the popular software list which protects other well known software as Google Chrome, Firefox, Windows Media Player............etc.

After upgrading EMET to the latest version 5.0, I noticed that the Windows Media Player (Latest Version 12) crashes and the below event log is reported.

My first suspect was EMET, I removed all mitigation for the Windows Media Player from the Apps Section as shown below.

Windows Media Player started working normal after removing all mitigation, I started checking them one by one till it crashes back again with the StackPivot Mitigation.

The StackPivot Mitigation is used to detect if the stack is pivoted and used to validate the stack register present in the context structure of certain APIs. For some reason its triggered with Windows Media player and you need to un-check it to work it out till Microsoft finds a solution since they are both Microsoft Products.

UAG Direct Access client Fail to connect. DA is configured and disabled.

Posted by Ahmed Nabil In , | 0 comments»
I got couple of users using Windows 7 reporting that they can't connect using Direct Access anymore whether its HTTPS or Teredo, DA just won't work. Upon further discussing the issue with them they mentioned that they enabled and disabled the Direct Access Connectivity assistant (DCA) Use Local DNS couple of times in an effort to work it out.

We started troubleshooting by checking the Name Resolution Policy table and we noticed that the NRPT was not getting applied on the DA client as shown below.

The next step was checking the DA resolution using the netsh dns show state command and it turned to be disabled.

Name Resolution Policy Table Options

Query Failure Behavior                : Always fall back to LLMNR and NetBIOS
                                        if the name does not exist in DNS or
                                        if the DNS servers are unreachable
                                        when on a private network

Query Resolution Behavior             : Resolve only IPv6 addresses for names

Network Location Behavior             : Never use Direct Access settings

Machine Location                      : Outside corporate network

Direct Access Settings                : Configured and Disabled

DNSSEC Settings                       : Not Configured

The DA client already has the correct group policies, certificates but its disabled.

The next step was checking the below registry key:

"HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\DNSClient EnableDAForAllNetworks"

The value of the key was set to 2 which means that DA is disabled !

Upon deleting the registry key, the DA started working normally without any problem.

For more information about the EnableDAForAllNetworks and its different values please check the below URL. 

On both cases that i have seen so far the reason was playing with the DCA settings (Use local DNS) which triggered the flipping of this registry key from Automatic to disabled.

Hopefully this could help someone with the same problem.

Publish RDS 2012 R2 VDI Pool on Microsoft UAG 2010 SP4

Posted by Ahmed Nabil In | 0 comments»
Unfortunately there is no much information (almost nothing) available from Microsoft regarding publishing Virtual Desktop Infrastructure (VDI) Pool on Microsoft UAG 2010. Two years ago i published an article on this same topic but it was targeting publishing the VDI pool from 2008 R2 Virtualization Host server to UAG 2010. You may check it on the following link

Lately we updated all our Remote Desktop services servers and upgraded everything to 2012 R2 including the VDI pool (Updating the pool with Windows 8.1 machines). I followed the same steps in my previous article but it didn't work.

The main trick is that in the old RDS version 2008/2008R2 the Session Host (RDSH) was the redirection server. This architecture changed in 2012/2012 R2 servers and the Connection Broker is the component that do the redirection (RDCB).

Since publishing the 2012 R2 VDI is not officially certified with UAG 2010 and to get around this issue,  our team checked the below old article to bypass checking resources.

All We need to do is to adjust the Registry key on the UAG server as shown below:


DWORD Value: TSDontCheckResources
Value data: 1

So what does this Registry key will actually do ?

When connecting to the Remote Desktop Server, the Broker returns the resources list it receives from the RDSH and it picks up all IP addresses on all interfaces on the server. Now the UAG server needs to resolve all the IP addresses returned in the resource list to names and verify if they resolve to the same server. If the resource list contains IPV6 addresses, this lookup fails and hence the security check fails and the connection fails to launch one of the VDI machines in the pool.

To Make it work, i followed my earlier article and then added this key and its working fine.

Event 1096, The Processing of Group Policy failed.

Posted by Ahmed Nabil In | 0 comments»
Recently i came across a group policy processing failure when a user tries to do a gpupdate /force, it works for the User Policy and fails for the computer policy with an error that group policy failed processing. As a result any computer policy on this device will fail.

Upon checking the Event viewer, the system log was filled with the Event ID 1096 as attached below.

As per the Event ID 1096, Windows couldn't apply the registry-based policy settings for the LocalGPO. The first place to check was the Registry.pol file located locally on the computer.

Steps to resolve this issue:

  1. Delete or rename the registry.pol file under c:\windows\system32\grouppolicy\machine\registry.pol
  2. Configure any administrative template settings in the local Computer settings GPO. This will re-generate automatically a new registry.pol file.
  3. Gpupdate /force will run normally without any problem.

For more info about Local GPO and corrupted Registry.pol, please check the below links:

EMET detected Caller mitigation and will close the application: Chrome.exe

Posted by Ahmed Nabil | 0 comments»
Recently users with EMET 4.1 installed on their machines started getting problems with Google Chrome. When users try to open Google Chrome they get an EMET Caller mitigation violation and Chrome crash and get closed. The Following event will be logged in the Application Event Viewer.

This issue started Late May, 2014 (20/21) after Google released the latest version of Chrome (35.0.1916.114). This issue was addressed on several other sites as Chromium

as well as EMET Application compatibility Forum

The temporary Solution for this issue was to remove the Google Chrome from the list of Protected applications in EMET or disabling the caller mitigation for Chrome.exe.

Final Resolution:

Microsoft Released EMET 4.1 Update 1 on 29/5/2014

This update added new functionality and updates which includes fixing this compatibility issue and other false positive reporting as per attached documentation.

After applying this update and rebooting the machine users were able to open the Chrome.exe without any problem.

Note: When applying this update make sure to keep your existing settings.

Users Expired Certificate Warning-Lync Certificate

Posted by Ahmed Nabil In , | 1 comments»
Several users started receiving certificate expiration warning messages on their computers regarding specific user certificates. Upon checking this certificate it turned out to be Lync Communication certificate as per the below screen shot.

This message is a normal Windows Warning Notification regarding a user certificate stored in the personal certificate store of the user account logged on this machine. In this specific case it was Microsoft Lync Communication certificate. When the Lync communication certificate expires, the client will just receive new certificate for the user SIP URI and everything should work normal.

However to manually stop receiving the warning shown above the user can check the box near the certificate and click done.

The question is why all users in the domain started getting these warning messages. To identify the root cause, i ran a GPRESULT from one of the client computers and i noticed a group policy configured across the domain with these warning settings. These specific settings are located under

User Configuration/Windows Settings/Security Settings/Public Key Policies/Certificate Services Client – Auto-Enrollment Settings”

There is a checkbox as shown below for the Expiration Notification when the the given percentage of certificate lifetime is reached. To avoid getting these warning you can remove/uncheck this option and users won't receive this notification.

It should be noted that if there is no group policy set, the users won't get any notification and won't even notice that the certificate expired and they got a new one.