Monday, October 31, 2016

The User Profile Service Failed The Logon

In this case, there was a Windows 8.1 workstation with corrupted Default profile. All domain users with or without previously created profile on that machine were unable to logon with following error message:
"The User Profile Service failed the logon. User profile cannot be loaded."
I've logged on to the workstation with local admin account, and opened the Application Event Log, a warning event with id 1509 was logged, from source Microsoft-Windows-User Profiles General with following description:
Windows cannot copy file \\?\C:\Users\Default\AppData\Local\Microsoft\Windows\WER to location \\?\C:\Users\TEMP\AppData\Local\Microsoft\Windows\WER. This error may be caused by network problems or insufficient security rights.

In order to resolve the issue, I've forced permission propagation to all child objects on C:\users\Default:

After successful permission replacement on all child object of C:\Users\Default, domain users were able to successfully log on to the workstation, again.

Wednesday, October 26, 2016

Error message when adding MPIO Devices

In this case, Window Server 2012 Hyper V failover cluster LUNs were scheduled for storage migration from different vendors. Hyper V hosts were using fiber channel for accessing the SAN LUNs. These Hyper V hosts were using PowerPath as their multipathing software. This software was not recommended for use with the new SAN provider. So, after successful VM storage migration, PowerPath had to be removed, and Hyper V server hosts had to be configured with native MPIO.
After successful uninstallation of  PowerPath, I've tried to add MPIO devices using native MPIO tool, but there was error message "The system cannot find the file specified":

Similar error was prompt, when using the new powershell cmdlet for adding MPIO devices

So, currently Hyper V server hosts were using single path for accessing the SAN LUNs, and obviously something went wrong with "successful" uninstallation of Powerpath. In order to create redundancy for SAN LUN access, I've reinstalled the MPIO feature on all Hyper v hosts.
After successful reinstallation of MPIO feature, I was able to add MPIO devices using native MPIO tool and enabled multiple paths for accessing SAN LUNs from Hyper V server hosts.

Friday, October 21, 2016

Windows Server 2016 Hyper V requirements

Windows Server 2016 Hyper V has introduced great features (for more info, please checkout the official article What's new in Hyper-V on Windows Server 2016 ), but before jumping in and formatting the disk with previous version of Windows Server operating system with Hyper V installed, please make sure that your hardware has the needed requirements. The easiest way is to run systeminfo.exe from command prompt or Powershell, and checkout the Hyper V requirements part from the command output (for example: this is the output from supported hardware):

In my case, I was having one test box HP DL380 G5 with Windows Server 2012 Hyper V role installed, and the output from systeminfo.exe for Hyper V part, looked like this:

For Windows Server 2016 Hyper V role, Second Level Address Translation (SLAT) is requirement, instead recommendation as it was for Windows Server 2012 Hyper V. So, if you don't check these requirements and you try to install Windows Server 2016 Hyper V role, you might experience the following error message:

Conclusion: some old hardware boxes might not be able to see the "light" of the new Microsoft Windows Server 2016 with Hyper V role installed.

Thursday, October 6, 2016

Intoducing Windows Server 2016 Free Ebook

Grab a copy of free eBook "Introducing Windows Server 2016" on .

This ebook is available in pdf format for standard and mobile readers.