>

Unable to start Hyper-V virtual machines on a Windows 2008 R2 server

When you try to to start a Hyper-V virtual machine on a Windows 2008 R2 server, you receive the following error:

An error occurred while attempting to start the selected virtual machine(s).

‘ServerName’ could not be initialized.

An attempt to initialize VM saved state failed.

‘ServerName’ could not initialize. (Virtual machine ID “Virtual Machine GUID”)

‘ServerName’ could not create or access saved state file E:\Hyper-V\ServerName\Virtual Machine\”Virtual Machine GUID”.vsv.
(Virtual machine ID “Virtual Machine GUID”)

Solution: I have no clue what caused this issue but the solution is add list permissions to the “Authenticated Users” group on the root drive where the virtual machines are placed (in this case E:). You only have to add list rights for “this folder only”.
So go to the security tab and choose advanced permissions, add Authenticated users and choose at Apply to: “This folder only”, check List permission and be sure you don’t check the replace all child object permissions with inheritable permissions from this object, otherwise you may have to restore the rights on all virtual machines permissions.

Posted in Blog, Hyper-V, Windows 2008R2 at November 16th, 2010. 12 Comments.

Event ID 10016, DistributedCOM: The application-specific permission settings do not grant Local Activation permission for the COM Server application

When you see the following evntlog error: Event ID 10016, Source:’DistributedCOM. “The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {61738644-F196-11D0-9953-00C04FD919C1} to the user NT AUTHORITY\NETWORK SERVICE SID (S-1-5-20) from address LocalHost (Using LRPC). This security permission can be modified using the Component Services administrative tool.”

Solution: If you don’t know witch application is given this error, you can copy the GUID behind CLSID and start the registry editor (regedit.exe) and search for the GUID. You will find witch application is creating this error.
After you know that you start Administrative Tools – Component Services. Expand Component Services, Computers, My Computer, DCOM Config. Then find the found application, in this case IIS WAMREG, choose properties and go to the security tab.

Then at Launch and Activation Permissions, choose customize (if not already chjoosen) and Edit.
Add the user account given in the event error, in this case Network Service account and give the account allow Local Launch and Local Activation rights. After that close all windows and restart IIS service.

Update: There is a similar error about another CLSID but the options to change permissions are greyed out. Read here how to solve this issue.

Posted in Blog, SBS 2008, Windows 2008, Windows 2008R2 at September 29th, 2010. No Comments.

Enable the use of saved credentials with remote desktop connection

When using remote desktop connection to connect to windows server 2008, 2008 R2, sbs 2008, vista or windows 7 and would use saved credentials. This doesn’t work when you start the connection you get the following error:

“Your system administrator does not allow the use of saved credentials to logon to the remote computer computername/ipadress because its identity is not fully verified. Please enter new credentials.” “The logon attempt failed”

Solution: This happens when trying to connect to a computer / server in another domain and no trust relationships exists. Windows then steps back to use NTLM and the default domain machine policy prohibits use of saved credentials. You can change this domain based or for a individual machine:

Start local group policy editor, start – run – gpedit.msc
Go to Local Computer Policy –> Computer Configuration –> Administrative Templates –> System –> Credentials Delegation
Edit “Allow Delegating Saved Credentials with NTLM-only Server Authentication”
Enable the policy, click Show and enter the value “TERMSRV/*” into the list.

Do the same thing for the following policies:
“Allow Delegating Saved Credentials”, “Allow Delegating Default Credentials with NTLM-only Server Authentication” en “Allow Delegating Default Credentials”

Close the policy editor,
open a command prompt and use “gpupdate /force” to apply the policy directly

Posted in Blog, SBS 2008, Windows 2008, Windows 2008R2 at September 21st, 2010. 33 Comments.

A network shared RemoteApp won’t start on the remote computer

When starting a windows 2008 (R2) RemoteApp from or depends on a network mapped drive you get the error “The program did not start on the remote computer.”

Solution: The problem is caused because the program is hosted on or depends on a network mapped drive. When starting a RemoteApp the program doesn’t wait till the logon script script is finished but just start the program directly and cannot find the right drive or program.
Workarround is to map the network drive persistant so it’s available before the RemoteApp program starts or create a batch file as RemoteApp so you can first map the network drive and then start the program.

Posted in Blog, Windows 2008, Windows 2008R2 at August 30th, 2010. 11 Comments.

Windows 2008 (R2) RemoteApp stays in disconnected state

When you close a Windows 2008 terminal server or Windows 2008 R2 remote desktop services RemoteApp the sessions stays in disconnected state.

Solution: Since Windows 2008 there is a local / group policy called ‘Set time limit for logoff of RemoteApp sessions’. You can set the policy for both computer as user configuration.

For windows 2008: Administrative Templates \ Windows Components \ Terminal Services \ Terminal Server \ Session Time Limits
For windows 2008 R2: Administrative Templates \ Windows Components \ Remote Desktop Services \ Remote Desktop Session Host \ Session Time Limits

Posted in Blog, Windows 2008, Windows 2008R2 at August 28th, 2010. No Comments.

Logon issues Windows 2008 R2 Remote Desktop Services

Problem 1: When logging on to a Windows 2008 R2 Remote Desktop Services (former known as Terminal Services) you get the a balloon messages saying a temporary profile is loaded. Changes to the profile are not saved by exiting.

Solution: Backup all data in “%SystemDrive%\Users\UserName” or just rename the folder with .bak at the end. (if this is the first time you try to logon with this account there will be no folder with this username.)
Then start the registry editor and browse to HKEY_LOCAL_MACHINE \ SOFTWARE \ Microsoft \ Windows NT \ CurrentVersion \ ProfileList here you will find all user SID’s logged on to this RDS server. You will find here a subkey know as SID.bak take a look probably this will be the key of the user you get this error.
Delete this key and close registry editor (If you are not sure, first make a backup/export of the key before deleteing is). Then logoff and logon again.

Problem 2: When you try to logon to a Windows 2008 R2 Remote Desktop Services (former known as Terminal Services) server, you get the error: “The Group Policy Client service failed the logon.” “Access is denied.” and you are automatically logged off.

Solution: In my case this problem was caused by a corrupted NTUSER.Dat file. I solved it by logging on as a Administrator changed the user profile to local via Control Panel\User Accounts\User Accounts Configure advanced user profile properties. Then I replaced the NTUSER.Dat from the user by the NTUSER.Dat from the temp profile.
Probably this is caused by using a Terminal Server profile that is corrupted. Another Solution could be deleting this profile and building a new profiles for this user.

Posted in Blog, Windows 2008R2 at August 25th, 2010. 8 Comments.

Windows update error on a fresh windows 2008 R2 install

After installing a fresh installation of windows 2008 R2 standard on a HP proliant dl380 g6 and turning on windows updates I got a error: code 80072F8F

Solution: Date and time range were not allright by default date and time on a hp proliant server are most of the time a few months in the past.

After downloaded all updates and installing arround 20 updates it stops with error: code 800F0902. 7 updates failed.

Solution: I restarted the server so the installed updates are configured. After restart I ran windows updates again and now the other updates are installed fine.

Posted in Blog, Windows 2008R2 at August 6th, 2010. No Comments.
Sharing Buttons by Linksku