• How To Crack Windows Server 2012 R2
• How To Crack Windows Server 2003
• Microsoft Windows Server 2000

Applicable Products

Members of a terminal server farm must be running Windows 2003 Enterprise Edition. If you want to confirm the licensing server that a terminal server is using, run the lsview.exe utility, which you'll find in the Windows 2003 Resource Kit. The figure shows the results of running the tool. You can also see the. Aug 06, 2013 In Windows 2000, Terminal Services only included a “Per Device” licensing mode. This means if you have 5 people sharing 1 workstation and they all use TS on a server, they only require 1 TS CAL. However in today’s world of throw away computers and telecommuting, the reality is most companies will have more than 1 “device” (computer) per employee.

• XenApp 6.5
• XenApp 6.0 for Windows Server 2008 R2
• XenApp 5.0 for Windows Server 2008

Information

Summary

This article contains information on troubleshooting 1003 and 1004 Terminal Server licensing errors. Users attempting to connect to a XenApp server might experience the following Terminal Services related errors in the Event Log:

Event ID: 1003
Source: TermService
Type: Information
The terminal service client has provided an invalid license.

Event ID: 1004
Source: TermService
Description: Unable to acquire a license for user name, domain name.

For more information, see Microsoft TechNet articles - TS Licensing Step-by-Step Guide and Troubleshooting Terminal Server Licensing.

Background

With Microsoft (both regular Client Access License (CAL) and Terminal Services CAL) licenses, before an ICA connection is established (the GINA logon pop-up), the client license must be confirmed to exist and be valid.

Note: Windows XP Professional workstations do not have built-in CALs with respect to Windows 2003 Terminal Server License Servers.

How To Crack Windows Server 2012 R2

When there is insufficient permissions to the following registry key, connection failures occur. Investigate the Microsoft Terminal Services License manager to see if the workstation is enumerated. If the workstation is not enumerated, then this issue is on the Windows OS level. For more information, contact Microsoft Technical Support and verify that your Windows 2003 Terminal Licenses are activated.

Symptom-1

When connecting with a Citrix ICA Client after downloading a Remote Desktop Protocol (RDP) web client, the RDP client might not exhibit any issues and continue to connect.

Cause-1

The Event Log does not specify the client device that provided the invalid license. Insufficient permissions are being applied to the Microsoft license key in the registry for the Authenticated Users group. When testing, attempt to create an RDP connection after removing the MSLicense key in the registry as a user (no Domain Admin or Power User Group); the RDP connection also fails.

Solution-1

It might be useful to investigate the Cryptography registry keys in HKEY_LOCAL_MACHINE and HKEY_CURRENT_USER on both the server and workstation. See Microsoft TechNet and the usage of RegMon and FileMon for additional information. In addition, see Windows Sysinternals. These changes will be reflected from the client device.

If you are making a desktop connection, then opening ICA connection inside the desktop session (Pass-through) and the subsequent ICA connection will fail. The affected workstation in this case is the server.

Complete the following procedure if you experience licensing errors previously mentioned:
Caution! Refer to the Disclaimer at the end of this article before using Registry Editor.

1. Open the Registry Editor through regedit32.exe command.

2. Navigate to HKEY_LOCAL_MACHINESOFTWAREMicrosoftMSLicensing.

3. Highlight this key, select Security on the toolbar, and select Permissions.

4. Click the Advanced key.

5. Verify that the Authenticated Users group is in Permissions Entries.

   Note: If this group is not found, click Add, select the Users Group, and click OK.

   - In Permission Entry for MSLicensing, provide full control to the UsersGroup and click OK.
   - In the Access Control Settings for MSLicensing, click Apply, and OK.
   - In Permission Entry for MSLicensing, click Apply and OK.

6. Attempt to connect using the 32-bit ICA Client for Windows.

Note: If using a non-native Windows client (Macintosh, Linux, or a Thin Terminal) without a local registry, the permission changes must be made to the following registry key:
HKEY_LOCAL_MACHINESOFTWARECitrixMSLicensing

Symptom-2

After moving the Terminal Services Licensing Server, RDP clients do not exhibit any problems and continue to connect.

Cause-2

A potential race condition between the Icaapi.dll and the Rdpwsx.dll might cause the private certificate key on the Terminal Services server to become unsynchronized.

Solution-2

For Windows 2003 Terminal Server, follow Microsoft TechNet article How to override the license server discovery process in Windows Server 2003 Terminal Services to add the Terminal Server License Server. For Windows 2008 Server follow Microsoft TechNet article - TS Licensing Step-by-Step Guide.

1. Click Start > Run, type regedit, and click OK.

2. Locate and click the following key in the registry:
   HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesTermServiceParameters

3. On the Edit menu, go to New and click Key.

4. Name the new key LicenseServers.

5. Locate and click the following key in the registry:
   HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesTermServiceParametersLicenseServers

6. On the Edit menu, go to New and click Key.

7. Name the new key ServerName where ServerName is the NetBIOS name of the license server that you want to use, and then press Enter.

8. Restart the computer.

   Notes: The new key name can be any of the following designations that represent the license server:

   • The NetBIOS name of the server.

   • The fully qualified domain name (FQDN) of the server.

   • The IP address of the server.

     If you use Windows Server 2003 SP1 and later or Windows Server 2008, you can set this in the Terminal Services Configuration administrative tool. The following screen shot shows the interface in Windows Server 2003:

9. In Server Settings, double-click the License server discovery mode and either enter the NetBIOS name of the server or the IP address.

10. Restart the server to apply the changes.

    Note: In Windows Server 2008, open Edit Settings, double-click License server discovery mode, select the Licensing tab, select the Use the specified license servers option, and enter the license server name (or IP address) in the field provided. The following screen shot shows the interface in Windows Server 2008:

    Use the Microsoft TechNet article - Windows XP Clients Cannot Connect to a Windows 2000 Terminal Services Server, to repair the certificate keys on the Terminal Server.

Symptom-3

When connecting an ICA Client using a Wyse WT1200LE version 4.2.x terminal, there is a known issue that exists with the firmware shipped with the thin client device.

Some client workstations might connect to all servers while others are denied to some servers.

Resolution-3

Upgrade to the latest firmware version 4.4.079 for the discontinued Winterm model 1200LE.

Troubleshooting for Non-Windows Clients

Note: If using a non-native Windows client (Macintosh, Linux, or a Thin Terminal) without a local registry, the preceding permissions (outlined in Issue 1) must be verified on the following registry key on the XenApp Server/Presentation Server:
HKEY_LOCAL_MACHINESOFTWARECitrixMSLicensing

1. Verify the number of TSCAL servers installed and their installation location. If your Terminal Servers are members of an Active Directory domain, you should install the TS License Server on a domain controller in the root domain of the forest. There can be only one Enterprise TS License server per Active Directory site. Install one Enterprise TS License server for each site in the Active Directory forest.For the Active Directory Object to be created properly, install TS Licensing as an Enterprise Administrator or an administrator belonging to the root domain. If an empty root domain is created, the Active Directory object for the TS-Enterprise-License-Server might not be created properly.Does the object look like it is in the Active Directory Sites and Services and can it be queried using an LDAP query? If you follow this process, all Windows 2000 servers running Terminal Services will discover their site-wide Enterprise TS license server by LDAP lookup.Whether or not Active Directory is used is very important with regard to the TS License Server discovery process. For more information about the TS License server discovery process, see Terminal Services Licensing service discovery.

2. Verify how many Terminal Servers generate the error(s) and also verify if the Terminal Servers are on the same subnet/domain as the TSCAL Server. When servers were on the same subnet, changing the TCP/IP configuration on the servers to h-node for WINS, adding a WINS server to the mix, and using the DefaultLicenseServer registry key, all servers in the Active Directory were able to find the TS License server. For more information, see Symptom-2. Therefore, verify if specifying the NetBIOS name of the TS License server by modifying the following registry value help:
   HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesTermServiceParametersDefaultLicenseServer
   Note: The NetBIOS name must be resolvable.

3. Verify if it make a difference that the user on the workstation is an administrator or has user class account.This is also important to know when the server is acting as the client in pass-through mode.

4. Verify the ICA Client version.

5. Update to the latest Microsoft Service Pack.

6. Verify if in the Control Panel - MSLicensing is set to per-server or per-seat.

7. Refer to Microsoft TechNet articles - Troubleshooting Terminal Server Licensing and TS Licensing Step-by-Step Guide.

Note: Purge option can be used to clean-up licenses from the stored client access licenses assigned to clients running non-Windows operating systems. For more information, see CTX137608 - DSCheck Maintenance Assistant.

Isolation Steps

How To Crack Windows Server 2003

1. Isolate the problem server to a workgroup and/or promote it to a domain controller.

2. Enable this server as a TSCAL Server.

3. Create at least two ICA sessions to this server.

4. Disable the TSCAL Server from this server.

5. If applicable, demote the server.

6. Rejoin the original domain.

7. Attempt to create an ICA session.

Notes: These steps are known to correct the preceding issue. The preceding action items, if completed successfully, conclude:

Microsoft Windows Server 2000

• No changes were made to the XenApp Server/Presentation Server.

• The changes occurred at the operating system level.

Additional Resources

Microsoft TechNet - TS Licensing Step-by-Step Guide

Disclaimer

• The theme of my site is – ‘Getting you started,
  setting you on the right road’.
• See how easy it is to get started with PowerShell.
• Tips and advice for Windows 8.
• Logon Scripts – Examples for you to copy and modify.
• Strategies to migrate to Windows 2012 or Exchange 2010.
• Independent networking advice from an expert.
• Helping you get the most from your servers.
• Lots of ‘How to…’ tips.

About This Site – Computer Performance

I divided the site into three main sections, Windows Server, Windows Exchange and Scripting. My mission is to provide busy network managers with practical examples of how to configure their servers.

If I have a specialty then it’s getting people started. So often if I can just point new-comers to the right menu, then what to put in the boxes is relatively self evident. What I also seek is to add real-world computer experience. Therefore, I never miss a chance to include tips and tricks learnt from the hard school of knocks.

These days we need more skills than ever. Take scripting as an example, what started as a relatively simple task of creating a logon script has expanded into, VBScript, WMI, LDAP, ADSI and of course PowerShell. To be even a minor expert you need at least basic knowledge of 4 different scripting syntaxes.

Each section contains tutorials on how to optimize settings and how to troubleshoot server problems. Topics within each section range from, logon scripts to migration, and from installation to disaster recovery.

Whilst I have a string of MCT and MVP qualifications, my tips are based on experience gained from years of troubleshooting Windows servers. Moreover, I do not always toe the ‘Microsoft party line’ because I value my independent viewpoints.