You receive your license server ID. On the "Connection method" page, click Telephone in the Activation method box, and then click Next. On the "Country or Region Selection" page, click your country or region, and then click Next to display the appropriate telephone number to call. Call Microsoft by using the phone number that is displayed on the "License Server Activation" page, and then provide the Microsoft customer support representative with the Product ID that is displayed on your screen.
You are also asked to provide your name, the name of your organization, and the type of licensing program that you want to use. The customer service representative processes your request to activate the license server, and creates a unique ID for your license server. Type the license server ID that is provided by the customer service representative, and then click Next.
After a license server is activated, it becomes the registrar for Terminal Services client licenses. While you are waiting to complete the activation process, your license server can issue temporary licenses for clients that allow the use of Terminal Services servers for up to days. You can change Licensing Wizard properties, such as the connection method and company information that you set during the activation process by using Terminal Server Licensing.
To do so:. Right-click the license server you want to modify, and then click Properties. To see a step-by-step guide for deploying Terminal Services Licensing, visit the following Microsoft web site:. Overview You must activate a license server before it can issue licenses to Terminal Services clients. In the console tree, expand All servers. Click Next. On the "Completing the Terminal Server Activation Wizard" page, do one of the following: To install client license key packs for your license server, click Next.
Close the Terminal Server Licensing window. Troubleshooting After a license server is activated, it becomes the registrar for Terminal Services client licenses. Need more help? This offer and the related campaign were ended on June 30, You can use one of the following methods to obtain transitional CAL licenses, depending on how you obtained the Windows XP Professional operating system licenses.
You must provide your volume licensing program information Enrollment number, Agreement number, or License and Authorization numbers, depending on the program type together with the requested number and type of terminal server CAL tokens. The information that you enter in the Terminal Server Licensing utility is validated by Microsoft Clearinghouse, and when your request for tokens is within the boundaries of the entitlement program, license tokens are installed in the Terminal Server License Server.
If you obtained your Windows XP Professional licenses through a retail or an OEM channel, these licenses will have a product key included. You can find the product key on the retail packaging or on the Certificate Of Authenticity COA sticker on the computer case. To obtain a transitional CAL license, follow these steps:.
In the License Type list, click the type of license that you want to obtain, type your e-mail address in the eMail Address box, and then click Next. In the Terminal Server Licensing utility, enter the license token s that you received. You can enter license tokens by using the Automatic connection recommended option, the Web Browser connection option, or the Telephone connection option. When you deploy Windows Server Terminal Services in a Windows domain, you have the following licensing options:.
Every aspect of Terminal Services Licensing has its share of shocks. If at least one aspect of licensing does not surprise you, then I will eat my hat. Does is slightly surprise you that Microsoft give us days to sort out the Per User licensing? Within the grace period you need to iron out your strategy and then contact your supplier to buy the required number of licenses.
Here is the outline plan. Count the users or devices then buy that number of licenses. Add the licenses to the Terminal Server Licensing interface. Install the Remote Desktop software on the clients. Have a think about who and what will use Remote Desktops. Count number of users, and then count the number of devices. If the decision is close then a per User license is cheaper.
For example, if you have geeks with a laptop, a hand held device and a palm top. Occasionally the geek even uses Remote Desktop from their workstation. Where the per Device option is more economical is if you have kiosks or communal machines.
I do believe that you can combine both per User and per Device licenses. Incidentally, the per Device licenses are help by the local operating system. Time for my warning. Microsoft has a habit of changing the licensing rules so do get confirmation of anything that I say from your trusty Microsoft supplier. I am going to get all the bad news over in one section.
0コメント