I ran into this problem on a Terminal Server configuration where the Adobe Reader X (AcroRd32.exe) process keeps using high if not all cpu capacity even after you close the program. After some searches I found this could be because the welcome screen that is opened when you start Acrobat Reader isn’t closed at all, the session stays active and keeps using a lot of cpu capacity.
I could not found a fix for the problem at this time , but there is a workaround that solves the problem. You can disable the welcome screen from starting with a registry key.
1. Open the regedit and navigate to: HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Adobe\Acrobat Reader\10.0\FeatureLockDown
2. Add a new key with the name: cWelcomeScreen
3. Add a DWORD value to the key: bShowWelcomeScreen with value 0
Now when starting Adobe Reader it will not start the welcome screen but also does not uses the high cpu.
Posted in Blog
, Windows 2008R2
at October 16th, 2012. 6 Comments
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
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.
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