Crack the detailed steps of the win2003 "Terminal Server Authorization" activation license

one. Activate 2003 Terminal Authorization Server

First confirm whether to install Windows Components

Add Remove Programs——Add Delete Windows Components

Installation of Terminal Server I won't introduce it. Let's talk about activating the license server.

1) Click & rdquo;Start”->”Program”->”Administrative Tools”->”Terminal Server Authorization>, select the server name that is not activated, select & rdquo; attribute & rdquo;, please write down the product ID that appears in the dialog box, we will use the 20-digit ID number to register online.

2) Open the Internet Explorer browser and enter https://activate.microsoft.com

(http+s) in the address bar. It is an English interface.

Select the "Chinese(Simplified)" (Simplified Chinese) item in the drop-down box at the top left corner, and press the "GO" icon.

The Chinese web page is now available. Make sure the "Enable License Server" item is selected, and then click "Next" button

4) In the information interface that is subsequently requested, enter the "Product ID" The 20 digits, fill in your other basic information, and then select "Next" to continue.

5) At this time, the system will display the personal information you have entered. After you are sure that you are correct, "Next";

6) you can get "has successfully processed your The license server initiates the application. Your license ID is: …", which is a 35-digit number that needs to be copied into seven segments, which contains numbers and uppercase English letters; and will ask you "requires customers at this time Machine license? ", of course you should answer & rdquo; is & rdquo;;

If there is no license, then the license program selects “Enterprise Agreement", after confirming your information, you can continue & rdquo; next step & rdquo;;

8) in the next interface "license program" (in this case is to select "Enterprise Agreement", if you choose other license procedures, may be slightly There are different), "product type" one should be "Windows 2003 Terminal Services Client Access License";"Quantity" is the maximum number of users you want to connect to (for example, "100"); Enter the seven-digit number you obtained from Microsoft in the "registration number" (if you don't have a license, enter 6656792, 4954438, 6879392 or 5297992), and then "Next";

It’s time to confirm your settings; 10) It should be now " Thank you for activating Terminal Services License" Your gains include two stuff, one is the 35-digit "license server ID" you just got, and the other is a seven-segment 35-digit "license key package that is now available. ID". Congratulations! 11) Now go to ”Start”->”Program”->”Administrative Tools”->”Terminal Server Authorization> to complete the final activation, select the server name and click Right click, set the "Installation Method" in the "Properties" setting to "Web Browser>;

Note: The server is guaranteed to connect to the Internet

12) and select the server. , right click and select “Install License" (License Server ID);%

13) You can get it on the Web now. The license key ID is entered into the following input box;

14) You're done, now there is no worries for 120 days; 9 C" U5 I9 K: k1 @15) Finally we return to the terminal In the server's authorization, click on the server name, right click and select "Activate", then the task is completed;

)

This is the sequence I use to activate the "Terminal Server Authorization" No.:

Terminal Server Activation License ID: TQH9V-DGP3B-QB9V9-BBJ46-4GHR2-DWJYG-P6TFQ

License Key

ID: WJH8B-P2RDB-DMCJX-9RHCT-2WWKW-4YJQH-64C39

Server Product ID: 69713-640-9197727-45725-

Note: Change the terminal service settings.

Run —>gpedit.msc->Computer Configuration——Administrative Templates——windows Components——Terminal Services Found"Restrict Terminal Services Users to a Remote Session” , set to Disable, which is disabled.

Terminal Server Configuration ——Server Settings——Restrict each user to use a session——Modify to “No”

2 . Terminal service testing.

First of all, let's understand the difference and connection between remote desktop and terminal service: Let's take a look at the same point. They are all components of windows system, which are developed by Microsoft. Through these two components, the user can control the function of the server at the other end of the network. Operating the server and running the program is as simple as manipulating the local computer, and the speed is also very fast.

But the difference between these two components is also very obvious ——

(1) Remote Terminal Services allows multiple clients to log in to the server at the same time, whether it is device authorization or user authorization. Requires a CAL client access authorization certificate, which is required to be purchased from Microsoft Corporation; remote desktop management is only provided to the operator and administrator a graphical remote access server for management interface (from the interface, the same as the remote terminal service) ), Remote Desktop does not require a CAL license.

(2) Remote Desktop is completely free, and Terminal Services only has a 120-day usage period. More than this free usage period, you need to purchase a license.

(3) Remote Desktop allows only two administrators to log in to the process, and Terminal Services has no restrictions. As long as you purchase enough licenses, you can find out how many users can log in to one server at the same time.

(4) Remote Desktop can only allow users with administrator privileges to log in, but Terminal Services does not have this restriction. Users with such permissions can remotely control the server through Terminal Services, but the permissions are still after login. Your own permissions are consistent.

1>

Terminal services require a cal client access authorization certificate. The application is authorized per device, the maximum number of connections is 200.

2> Allow multiple users to connect at the same time.

3> Some functions in the terminal server are: connect, disconnect, reset, send message, remote control, status.

4> Terminal server settings, I will slowly understand. Note: There is also a setting in the group policy.

1> Turn on the remote.

2> Remote End User needs to be added to the Remote Desktop Users group, and members of this group are granted remote login privileges.

Installing the license client (for the 2000 client, the default is no remote desktop component, you need to install it).

The server C:\\WINDOWS\\system32\\clients\\tsclient is shared under the win32 folder.

The client then accesses the share using a UNC path or accesses it in a network neighborhood.

After letting the client install the setup.exe under win32, it will be fine.

The 2000 client can also access the terminal server through the Remote Desktop component.