Event ID 1001 RemoteApp and Desktop Connection

Configuration

Identify and fix configuration issues with Remote

Desktop Web Access
To resolve this issue, do the following things:

If you are using an RD Connection Broker server, you must ensure that the RD
Connection Broker server is available on the network.

If you are using one or more RemoteApp sources, you should ensure that the
RemoteApp source name is correct.

To perform these procedures, you must be a member of the Administrators group, or

you must have been delegated the appropriate authority.

Ensure that the RD Connection Broker server is available on

the network
The following are some troubleshooting steps that you can perform to help identify the
root cause of the problem:

Ping other computers on the network to help determine the extent of the network
connectivity issue.

If you can ping other servers but not the domain controller, try to ping
the RemoteApp source server from another computer. If you cannot ping the RD
Connection Broker server from any computer, first ensure that the RD Connection
Broker server is running. If the RD Connection Broker server is running, check the
network settings on the RD Connection Broker server.

Check the TCP/IP settings on the local computer by doing the following:
1. Click Start, click Run, type cmd, and then click OK.
2. At the command prompt, type ipconfig /all, and then press ENTER. Make
sure that the information listed is correct.
3. Type ping localhost to verify that TCP/IP is installed and correctly
configured on the local computer. If the ping is unsuccessful, this may
indicate a corrupt TCP/IP stack or a problem with your network adapter.
4. Type ping IP_address, where IP_address is the IP address assigned to the
computer. If you can ping the localhost address but not the local address,
there may be an issue with the routing table or with the network adapter
driver.
5. Type ping DNS_server, where DNS_server is the IP address assigned to
the DNS server. If there is more than one DNS server on your network, you

should ping each one. If you cannot ping the DNS servers, this indicates a
potential problem with the DNS servers, or with the network between the
computer and the DNS servers.
6. If the RD Connection Broker server is on a different subnet, try to ping the
default gateway. If you cannot ping the default gateway, this might
indicate a problem with the network adapter, the router or gateway device,
cabling, or other connectivity hardware.

In Device Manager, check the status of the network adapter. To open Device
Manager, click Start, click Run, type devmgmt.msc, and then click OK.

Check network connectivity indicator lights on the computer and at the hub or
router. Check network cabling.

Check firewall settings by using the Windows Firewall with Advanced Security
snap-in.

Check IPsec settings by using the IP Security Policy Management snap-in.

Ensure that the RemoteApp source name is correct

You can ensure that the RemoteApp source name is correct by using Remote Desktop
Web Access Configuration.
To ensure that the RemoteApp source name is correct:
1. On the RD Web Access server, click Start, point to Administrative Tools, point
to Remote Desktop Services, and then click Remote Desktop Web Access
Configuration.
2. Enter the appropriate user name and password.
3. Click Configuration.
4. In the Source name box, ensure that the RemoteApp source name represents a
NETBIOS name or fully qualified domain name of the RemoteApp source. If you
are using more than one RemoteApp source, ensure that each source name is
separated with a semicolon.

Verify
To verify that RemoteApp and Desktop Connection is configured correctly, you should
start a RemoteApp program that is published by using RemoteApp and Desktop
Connection.
To start a RemoteApp program that is published by using RemoteApp and Desktop
Connection:
1. On a client computer, click Start, point to All Programs, point to RemoteApp
and Desktop Connections, point to Enterprise Remote Access, and then
click a RemoteApp program.
2. Verify that the RemoteApp program opens successfully.

Event ID 6004 Windows Logon Availability

Diagnose
This error might be caused by one of the following conditions:

System resources are inadequate or unavailable.

The Windows registry is corrupted.

A service failed to start.

To perform these procedures, you must have membership in Administrators, or you

must have been delegated the appropriate authority.

System resources are inadequate or unavailable

To determine if system resources are inadequate or unavailable:
1. Right-click the taskbar, and then click Task Manager.
2. Click the Performance tab to monitor the usage of central processing unit (CPU)
and memory resources.
3. Observe the top two graphs that show how much CPU is being used, both at the
moment and for the past few minutes. (If the CPU Usage History graph appears
split, your computer either has multiple CPUs, a single dual-core CPU, or both.) A
high percentage means that programs or processes are requiring a lot of CPU
resources, which can slow your computer. If the percentage remains at or near
100 percent, then a program might not be responding.
4. Observe the bottom two graphs that display how much random access memory
(RAM), or physical memory, is being used in megabytes (MB), both at the current
moment and for the past few minutes. The percentage of memory being used is
listed at the bottom of the Task Manager window. If memory use seems
consistently high or slows your computer's performance noticeably, try reducing
the number of programs you have open at one time, or install more RAM.
5. Click the Processes tab to view memory use for individual processes on your
computer. The Memory (Private Working Set) column is selected by default.
Private working set is a subset of working set that describes how much memory is
being used by each process. Private working set specifically describes the amount
of memory a process is using that cannot be shared by other processes. Check if
any processes are taking substantially large amount of memory.
6. To view additional information about how much memory and CPU resources are
being used, click Resource Monitor. Resource Monitor provides more
detailed graphical summaries. It also includes more details about resources, such
as disk use and network use.

7. If system resources are inadequate or unavailable, see the "Make more resources
available on the system" section.

The Windows registry is corrupted

If the Windows registry is corrupted, logon might be prevented and you will need to
interrupt the startup process to boot the computer into Safe Mode or the Recovery
Console. In Safe Mode, you can use System Restore to restore the Windows registry to
a restore point. In the Recovery Console, you can use the Startup Repair utility. Startup
Repair is a tool that automates common diagnostic and repair tasks of unbootable
Windows installations, such as repairing a corrupted registry.
Note: You may need to have your operating system CD/DVD available if the Startup
Repair is not a preinstalled recovery option on your computer.
If your computer will not complete the startup process, see the "Repair a corrupted
registry" section.

A service failed to start

To determine if a service failed to start:

1. Click Start, and then click Control Panel.
2. Open Administrative Tools, and then open Event Viewer.
3. In the Event Viewer (Local) pane, double-click Windows Logs.
4. Select the System log. A white exclamation point in a red circle indicates that a
service or driver is stopped or has failed to start. A black exclamation point in a
yellow triangle indicates warnings, such as low disk space. For more information
about an entry, click the entry, and read the General tab.
5. If a service failed to start, see the "Restart the service" section.

Resolve
To resolve this issue, use the resolution that corresponds to the cause you identified in
the Diagnose section. After performing the resolution, see the Verify section to confirm
that the feature is operating properly
Cause

Resolution

This computer does not have adequate system resources

Make more resourc

This computer has a corrupted registry

Repair a corrupted

Services required by the process failed to start

Restart the service

Make more resources available on the system

During Windows logon, the operating system opens the subscriber notification database
and starts the user-level processes so that user accounts can log on to the system. If
there are inadequate system resources for Windows logon to do this, the system may
start with limited functionality.

To identify the applications or services that are using too many system resources, you
can generate a System Diagnostics report by using the Reliability and Performance
Monitor.
To perform this procedure, you must have membership in Administrators, or you must
have been delegated the appropriate authority.
To make more resources available on the system:
1. Click Start, point to All Programs, click Accessories, right-click Command
Prompt, and then click Run as administrator.
2. Type perfmon /report and press ENTER. The Reliability and Performance Monitor
will start collecting data to create the System Diagnostics report.
3. When the report is ready for viewing, locate the Diagnostic Results section of
the report, and check for any Warnings. You can follow links to additional help on
resolving warnings from this section. In addition, you can expand each category in
the Basic System Checks section to see more details about why warnings
appear. ThePerformance section of the report provides process-level detail about
applications or services that are using the most resources.
4. Identify the applications or services that are not required.
5. Click Start, and type msconfig.exe to open System Configuration. If you are
prompted for an administrator password or confirmation, type the password or
provide confirmation.
6. Click the Service tab, clear the check box next to the names of the services that
you want to disable, and then click Apply. If you do not know which services you
require at startup, note the services that are currently configured to start and
then click Disable all to disable all services.
7. Click the Startup tab, clear the check box next to the names of the programs that
you want to disable, and then click OK. If you do not know which programs you
require at startup, note the programs that are currently configured to start and
then click Disable all to disable all programs.
8. Restart the computer.

Repair a corrupted registry

During Windows logon, the operating system opens the registry and reads the list of user
accounts that are configured for the computer. If that data cannot be read, the Windows
logon screen is not displayed and users will be unable to log on to Windows. Whether or
not Windows will be able to complete the startup process depends on the severity of the
registry corruption.
If the Windows registry is slightly or moderately corrupted, you may be able to restart the
computer in Safe mode and use System Restore to restore the registry of the computer
to the last known good configuration. However, if the Windows registry is severely
corrupted, all types of logon will be prevented. Attempting to log on to Windows causes
the system to fail and then to restart. In this situation, you will need to boot the system
into the Recovery Console instead of into Windows. Once in the Recovery Console, you

can use the Startup Repair tool. Startup Repair automates common diagnostic and repair
tasks of unbootable Windows installations.
To perform these procedures, you must have membership in Administrators, or you
must have been delegated the appropriate authority.

Repair a corrupted registry by using Startup Repair

To repair a corrupted registry by using Startup Repair:
Caution: Incorrectly editing the registry might severely damage your system. Before
making changes to the registry, you should back up any valued data.
1. During restart, select the option to restart into the Recovery Console to allow you
to restore the system. Your system may restart into the Recovery Console
automatically or you may need to start the Recovery Console manually during the
system restart process by pressing F8.
2. On the Advanced Boot Options screen, use the arrow keys to highlight Repair
your computer, and then press ENTER. If Repair your computer is not listed,
you will need to reboot your computer from the operating system CD/DVD to use
Startup Repair because Startup Repair was not configured as a preinstalled
recovery option on your computer.
3. Choose your language settings, and click Next.
4. Click Repair your computer.
5. Choose your operating system, and click Next. System recovery options are
displayed.
6. Click Startup Repair. Startup Repair diagnoses your system to identify the cause
of the failure. Once it has identified the cause, it automatically starts repairing
your computer.
7. After Startup Repair has run, a text log with diagnostic information and repair
results is generated. To view this log, click Details. The details are saved to the
log file located at %WINDIR%\System32\LogFiles\Srt\SrtTrail.txt.
8. After Startup Repair has finished the repairs, click Finish to restart your computer.

Repair a corrupted registry by using System Restore

To repair a corrupted registry by using System Restore:
1. Click Start, type systempropertiesprotection, and then press ENTER. If you
are prompted for an administrator password or a confirmation, type the password
or clickAllow.
2. In the System Properties dialog box, on the System Protection tab,
click System Restore.
3. In the System Restore dialog box, click Choose a different restore point, and
then click Next.
4. Select the restore point that you want to use, and then click Next.

5. Confirm your restore point, and then click Finish. The selected configuration is
restored, and the computer restarts.
6. Log on to the computer.
7. When the System Restore confirmation page appears, click OK.
For more information about backing up and restoring the registry, including guided help,
see article 322756 in the Microsoft Knowledge Base (http://go.microsoft.com/fwlink/?
LinkID=101847).

Restart the service

During Windows logon, Windows starts the services that support user interaction with the
system.
To perform this procedure, you must have membership in Administrators, or you must
have been delegated the appropriate authority.
To restart services that failed to start:
1. Use the error code to determine the service that failed to start.
2. Click Start, type services.msc, and then press ENTER.
3. In the Services pane, locate the service that failed to start.
4. Right-click the service, and then click Start.

Verify
To verify that Windows logon is functioning correctly, observe one or more of the
following processes:

An account is able to log on to the local computer or to the domain.

An account is able to log on during the hours of the day that the account has been
granted access.

An account is able to log on to the computer with a valid license.

A user can press CTRL+ALT+DELETE to log on to the computer or log off from the
computer.

User Profile Service event id 1530 with every remote

desktop logout
Generally speaking, event ID 1530 means there are some data in the user profile are still
be accessed when the user logoff from the Terminal Server, you have very possibly
enabled the policy to remove the user profile when logged off. In such a situation the
error appears. To troubleshoot this error, you can check if any of the data is still remained
in the user profile supposed to be deleted. That should be the data the process is using
when logoff happens. You can use Process Monitor or Process Explorer in order to find the

software which is using the data and find the solution. If there is no such data remained,
the Windows have possibly stopped the process and deleted the data when logoff. In
such a case, you can ignore the Event 1530.
Regarding EventID 1530, please also take the following KB article as reference:
(KB947238) Event ID: 1530 may be logged in the Application log on a Windows 7-based
or Windows Vista-based client computer
http://support.microsoft.com/default.aspx?scid=kb;EN-US;947238

Event ID 1003 Remote Desktop Services Client Access

License (RDS CAL) Availability

Resolve

Delete the appropriate registry subkey

To resolve this issue, delete the MSLicensing registry subkey on the client computer,
restart the client computer, and then try again to connect remotely to the RD Session
Host server from the client computer. If the issue persists, delete the Certificate, X509
Certificate, X509 Certificate2, and X509 Certificate ID registry entries on the RD
Session Host server, restart the RD Session Host server, and then try again to connect to
the RD Session Host server from the client computer.

Delete the MSLicensing registry subkey

To perform this procedure on the client computer, you must have membership in the
local Administrators group, or you must have been delegated the appropriate authority.
To delete the MSLicensing registry subkey:
Caution: Incorrectly editing the registry might severely damage your system. Before
making changes to the registry, you should back up any valued data.
1. On the client computer, open Registry Editor. To open Registry Editor, click Start,
click Run, type regedit, and then click OK.
2. If the User Account Control dialog box appears, confirm that the action it
displays is what you want, and then click Yes.
3. Locate the HKEY_LOCAL_MACHINE\Software\Microsoft\MSLicensing registry
subkey.
4. Click MSLicensing.
5. Before deleting the MSLicensing subkey, back up the subkey. To back up the
subkey, do the following:
a. Right-click MSLicensing, and then click Export.
b. In the File name box, type mslicensingbackup, and then click Save. If
you need to restore this registry subkey, doubleclick mslicensingbackup.reg.
6. To delete the MSLicensing subkey, on the Edit menu, click Delete, and then
click Yes.
7. Close Registry Editor, and then restart the client.

8. After the client computer is restarted, try again to connect remotely to the RD
Session Host server from the client computer.

Delete the appropriate registry entries on the RD Session

Host server
If the issue persists, delete the Certificate, X509 Certificate, X509 Certificate2,
and X509 Certificate ID registry entries on the RD Session Host server.
To perform this procedure on the RD Session Host server, you must have membership in
the local Administrators group, or you must have been delegated the appropriate
authority.
To delete the appropriate registry entries:
Caution: Incorrectly editing the registry can severely damage your system. Before
making changes to the registry, you should back up any valued data on the computer.
1. On the RD Session Host server, open Registry Editor. To open Registry Editor,
click Start, click Run, type regedit, and then click OK.
2. If the User Account Control dialog box appears, confirm that the action it
displays is what you want, and then click Yes.
3. Locate
the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal
Server\RCM registry subkey.
4. Click RCM.
5. Before deleting the subkeys, back up the RCM subkey. To back up the subkey, do
the following:
a. Right-click RCM, and then click Export.
b. In the File name box, type rdsrcm, and then click Save. If you need to
restore this registry subkey, double-click rdsrcm.reg.
6. To delete the Certificate, X509 Certificate, X509 Certificate2, and X509
Certificate ID registry entries, right-click each entry, click Delete, and then
click Yes.
7. Close Registry Editor, and then restart the RD Session Host server.
8. After the RD Session Host server is restarted, try again to connect remotely to the
RD Session Host server from the client computer.
If the issue persists, do the following:
1. On the client computer, back up and then delete the MSLicensing registry key
and its subkeys.
2. On the RD Session Host server, back up and then delete the Certificate, X509
Certificate, X509 Certificate2, and X509 Certificate ID registry entries.

3. Deactivate and then reactivate the license server. For information about
deactivating and reactivating a license server, see the topic "Managing Remote
Desktop Licensing" in the RD Licensing Manager Help in the Windows Server 2008
R2 Technical Library (http://go.microsoft.com/fwlink/?LinkId=177615).
4. Restart the RD Session Host server and the client computer and then try again to
connect remotely to the RD Session Host server from the client computer.

Verify
To verify that the RD Session Host server can contact a Remote Desktop license server
with the appropriate type of Remote Desktop Services client access licenses (RDS CALs),
use Licensing Diagnosis in Remote Desktop Session Host Configuration.
To perform this procedure, you must have membership in the
local Administrators group, or you must have been delegated the appropriate authority.
To use Licensing Diagnosis in Remote Desktop Session Host Configuration:
1. On the RD Session Host server, open Remote Desktop Session Host Configuration.
To open Remote Desktop Session Host Configuration, click Start, point
toAdministrative Tools, point to Remote Desktop Services, and then
click Remote Desktop Session Host Configuration.
2. If the User Account Control dialog box appears, confirm that the action it
displays is what you want, and then click Yes.
3. In the left pane, click Licensing Diagnosis.
4. Under Remote Desktop Session Host Server Configuration Details, the
value for Number of RDS CALs available for clients should be greater than 0.