BUG: RemoteApp and Desktop Connection: An error has occurred. Contact your workplace administrator for assistance.
-
10. dubna 2010 1:44Moderátor
Hi Folks,
If you get the following error when trying to add a RemoteApp and Desktop Connection to a Windows 7 or 2008 R2 machine, and you use RD Connection Broker:
An error has occurred. Contact your workplace administrator for assistance.
I have posted a bug and the workaround here: http://blog.kristinlgriffin.com/2010/04/remoteapp-and-desktop-connection-error.html
Hope this helps,
Kristin L. Griffin
Co-Author of the Windows Server 2008 Terminal Services Resource Kit (and a SUPER BIG fan of the Microsoft RDV Team!!!)
I finally started my blog: blog.kristinlgriffin.com
Všechny reakce
-
5. května 2012 0:05
Hi Kristin, I am getting the exact same error, but your solution does not work for me. I have been trying to figure this issue out for more then six months now. Any other advice is MUCH appreciated. Thanks in advance.
-
5. května 2012 13:40ModerátorI would change the name and id to TEST and try it. Also comb the event log on the server and client. Is the RDWA website working fine?
Hope this helps,
Kristin L. Griffin
SUPER BIG fan of the Remote Desktop Virtualization Team!!!)
My RDS blog: blog.kristinlgriffin.com
The new Microsoft Windows Server 2008 R2 Remote Desktop Services Resource Kit is now available! -
7. května 2012 18:12
No glory with the name change. However, I noticed two Audit Failure events when I try to connect.
--------------------------------------
Log Name: Security
Source: Microsoft-Windows-Security-Auditing
Date: 5/7/2012 2:07:24 PM
Event ID: 4625
Task Category: Logon
Level: Information
Keywords: Audit Failure
User: N/A
Computer: RDWA Server
Description:
An account failed to log on.Subject:
Security ID: NULL SID
Account Name: -
Account Domain: -
Logon ID: 0x0Logon Type: 3
Account For Which Logon Failed:
Security ID: NULL SID
Account Name: Username
Account Domain: Computer NameFailure Information:
Failure Reason: Unknown user name or bad password.
Status: 0xc000006d
Sub Status: 0xc0000064Process Information:
Caller Process ID: 0x0
Caller Process Name: -Network Information:
Workstation Name: Computer Name
Source Network Address: IP of Computer Name
Source Port: 44398Detailed Authentication Information:
Logon Process: NtLmSsp
Authentication Package: NTLM
Transited Services: -
Package Name (NTLM only): -
Key Length: 0This event is generated when a logon request fails. It is generated on the computer where access was attempted.
The Subject fields indicate the account on the local system which requested the logon. This is most commonly a service such as the Server service, or a local process such as Winlogon.exe or Services.exe.
The Logon Type field indicates the kind of logon that was requested. The most common types are 2 (interactive) and 3 (network).
The Process Information fields indicate which account and process on the system requested the logon.
The Network Information fields indicate where a remote logon request originated. Workstation name is not always available and may be left blank in some cases.
The authentication information fields provide detailed information about this specific logon request.
- Transited services indicate which intermediate services have participated in this logon request.
- Package name indicates which sub-protocol was used among the NTLM protocols.
- Key length indicates the length of the generated session key. This will be 0 if no session key was requested.
----------------------------------------------------------Log Name: Security
Source: Microsoft-Windows-Security-Auditing
Date: 5/7/2012 2:07:24 PM
Event ID: 4776
Task Category: Credential Validation
Level: Information
Keywords: Audit Failure
User: N/A
Computer: RDWA Computer Name
Description:
The computer attempted to validate the credentials for an account.Authentication Package: MICROSOFT_AUTHENTICATION_PACKAGE_V1_0
Logon Account: Username
Source Workstation: Computer NameError Code: 0xc0000064