Windows

Microsoft Wireless Display Adapter v2 – Connection failed

Microsoft Wireless Display Adapter provides a convenient way to add public/sharing capabilities to any display that has at least one HDMI input, and preferable as a USB connection for the power requirements. The adapter utilises the Wi-Fi CERTIFIED Miracast technology, which uses Wi-Fi Direct to communicate between devices. The required stack is built into Windows 10, meaning no further installations are required. Once installed everything should work out of to box but it is advisable to install the Microsoft Wireless Display Adapter App from the Microsoft App Store. The App allows for managing the adapter settings such as renaming the adapter name, setting security features and update the firmware if available. As Wi-Fi Direct is used to communicate between the adapter and your mobile device the most common issues relate to the Wifi adapter of network settings. If you fail to connect to the display there a numerous suggestion to re-install the driver for the Wifi adapter. Before doing so or in case this is unsuccessful it is worth to look at any network security software or the built-in Windows Firewall. In my case, I had deployed the ESET Endpoint Security, which comes and enables by default an extensive set of Network security features.

Windows uses the Windows User-Mode Driver Framework Host (Wudfhost.exe) for the communication with the Wireless Display adapter. ESET will by default block all communication, cause the “Connection failed” error message with nor further indication what might be the cause. The WUDFHost process has to be able to receive inbound TCP packages on port 7236. For the ESET Endpoint Security suite a firewall rule to allow this traffic is required. Go to Setup -> Firewall (Configure Firewall) -> Advanced (Edit rules).

Once this rule as been created the inbound traffic will be allowed to go through to the WUDF process and you will be able to connect with no problems to the Wireless Display adapter. For ESET deployed in an Enterprise environment, a custom policy should be created with the above settings and assigned to clients as required.

By RZM 0 Comments

Internet Explorer 11 Group Policy Preferences GPO

With the release of Windows 10 organisations will have to look at what version of Internet Explorer will be used for internal and external services. As of now it looks like that Microsoft will ship IE11 as part of the new Windows release, mainly for backwards compatibility reason properly. Regardless, a decision might have been made to role out IE11 even for Windows 7/8.1 to get the benefit of longer support. As part of this deployment IT departments would look at customising and testing certain setting before making the update available to the entire user base. One would assume that just like it was done for IE10 there would be a template for IE11. However, even on Windows 8.1 or Windows Server 2012R2 only Internet Explorer 10 is available to choose from but not IE11.

GPO Preferencs IE10

Microsoft has slightly changed is policy and with the IE10 option, Internet Explorer 10 AND greater will be covered, meaning that IE11 will pick up the settings/customisation you have specified for IE10, making IT administrator’s life somehow easier. However, as with every Internet Explorer version there are some new features and corresponding setting that will not be covered by the preferences like the Enterprise Mode. For those Microsoft has made a IE11 Administration Templates available that should be used to customise these features as required.

By RZM 0 Comments

Fix Windows Error – User profile cannot be loaded

The correct error message you will see is “The User Profile Service service failed the logon. User profile cannot be loaded.”The User Profile Service service failed the logon There are plenty of fixed and How-to-Do’s out there, all suggestion to edit the registry and rename the profile in question. However, the error would occur the first time a user tries to logon to a machine with a newly created AD account. e.g. the user has no profile on the computer yet. The solution seems to correct the security settings for the default profile that is used to set up the user.

  1. Enable “Show hidden files, folders, and drives in Explorer” (Organise -> Folder and Search options -> View)
  2. Go to C:\Users, right mouse click on “Default” -> Properties
  3. Click on the Security Tab and then Advanced
  4. Verify that for “Include inheritable permissions from this object’s parent” the check box is checked. If it is not checked and greyed out click on Change Permissions and in the next screen check the check boxes “Include inheritable permissions from this object’s parent” and “Replace all child object permissions with inheritable permissions form this object” are checked. Press “OK” and ignore the Error Messages.
  5. Reset the Folder option for “Show hidden files, folders, and drives in Explorer

Hopefully that will have fixed the problem and the next time the user is trying to logon a profile will be created.

For further information and how to fix the the issue if the above doesn’t work look here.

Another good How-to-Fix with some background info’s and good discussion can be found here.

Also check it the Trust-Relationship with the Domain is not brocken either.

 

By RZM 0 Comments
Send a Message