Unable to add SCP for Terminal Server Licensing in Windows Server 2008 R2

Hi All,

I've installed the license in my current Windows Server 2008 R2 (activated and joined to the domain too.) but then i still cannot register the SCP ?

it gives me an error message with Event ID 85, see the attached, can anyone help me here in registering this Windows Server 2008 R2, I've logged in using DOMAIN\Administrator account already but still I cannot do it.

Cheers,

JJ
Log Name:      Microsoft-Windows-TerminalServices-Licensing/Admin
Source:        Microsoft-Windows-TerminalServices-Licensing
Date:          23/03/2010 4:01:12 PM
Event ID:      85
Task Category: None
Level:         Error
Keywords:      
User:          NETWORK SERVICE
Computer:      TermServ01.domain.com
Description:
The Remote Desktop license server could not be registered as a service connection point in Active Directory Domain Services (AD DS). Ensure that there is network connectivity between the license server and AD DS. To register the license server as a service connection point in AD DS, use Review Configuration in the RD Licensing Manager tool.

Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-TerminalServices-Licensing" Guid="{4D99F017-0EB1-4B52-8419-14AEBD13D770}" />
    <EventID>85</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x4000000000000000</Keywords>
    <TimeCreated SystemTime="2010-03-23T05:01:12.409125000Z" />
    <EventRecordID>9</EventRecordID>
    <Correlation />
    <Execution ProcessID="1116" ThreadID="1128" />
    <Channel>Microsoft-Windows-TerminalServices-Licensing/Admin</Channel>
    <Computer>TermServ01.domain.com</Computer>
    <Security UserID="S-1-5-20" />
  </System>
  <EventData>
  </EventData>
</Event>

Open in new window

TS.jpg
LVL 1
jjozAsked:
Who is Participating?
 
jjozConnect With a Mentor Author Commented:
thanks for the suggestion mate,

I ended up manually edit the AD using the instruction in this link: http://technet.microsoft.com/en-us/library/ee891215(WS.10).aspx
Publish the license server by using ADSI Edit

To perform this procedure, you must have membership in the Enterprise Admins group in AD DS, or you must have been delegated the appropriate authority.

Open ADSI Edit. To open ADSI Edit, log on to a computer where ADSI Edit is installed (for example, a Windows Server 2008 AD DS domain controller), click Start, click Run, type adsiedit.msc, and then click OK.
If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Yes.
On the Action menu, click Connect to.
Under Connection Point, select Select a well known Naming Context, select Configuration from the drop-down list, and then click OK.
Expand the Configuration container, and then expand the node that represents the domain in which the license server is a member (for example, CN=Configuration,DC=contoso,DC=com).
Expand CN=Sites, and then click the container for the AD DS site in which the license server is located (for example, CN=Default-First-Site-Name).
In the right pane, under Name, if there is an entry for CN=TS-Enterprise-License-Server, do the following:
Right-click TS-Enterprise-License-Server, and then click Properties.
Under Attributes, click siteServer, and then click Edit.
Under Value to add, type in the name of the license server that you want to publish, click Add, and then click OK.
Click OK to close the CN=TS-Enterprise-License-Server Properties dialog box.
If under Name there is no entry for CN=TS-Enterprise-License-Server, on the Action menu, point to New, and then click Object.
In the Class Object dialog box, select licensingSiteSettings, and then click Next.
In Value, type TS-Enterprise-License-Server, click Next, and then click Finish.
Open Active Directory Sites and Services. To open Active Directory Sites and Services, log on to a computer where Active Directory Sites and Services is installed (for example, a Windows Server 2008 AD DS domain controller), click Start, click Run, type dssite.msc, and then click OK.
If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Yes.
Under Sites, locate the AD DS site in which the license server is located (for example, Default-First-Site-Name), and then click the name of the AD DS site.
In the right pane, right-click TS-Enterprise-License-Server, and then click Properties.
Under Licensing Computer, click Change.
In the Enter the object name to select box, type the name of the license server, click OK, and then click OK.

Open in new window

0
 
NJComputerNetworksConnect With a Mentor Commented:
Did you read this:  http://technet.microsoft.com/en-us/library/cc770591.aspx

If the discovery scope for a license server is set to either Domain or Forest, Review Configuration checks if the license server is a member of the Terminal Server License Servers group in AD DS.

Is you computer in the terminal server license server group?
0
 
NJComputerNetworksConnect With a Mentor Commented:
For example, if the license server is not published in AD DS and you have Enterprise Admins privileges in AD DS, you can click Publish in AD DS to correct the problem.
0
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

 
jjozAuthor Commented:
Hi there, thanks for replying my thread, no this is brand new server I've just created it and joined to the domain, FYI:

  1. No firewall in between Windows Servers in my domain
  2. i can ping to all DC in my domain and vice versa
  3. the DC is: Windows Server 2003 Std. R2 SP2 x64 with Windows 2000 native mode  functionality level.
and i've attached the group in my AD, which one shall i manually add into ?

TS-Group.jpg
0
 
jjozAuthor Commented:
Yes, I'm logging in using my DOMAIN\Administrator account already.

and yes I have added this server named TERMSERV01 into the

Computer | Terminal Service server group in the AD DS but still it shows exclamation mark in the RD licensing manager of not being able to register as service connection point :-|
0
 
NJComputerNetworksConnect With a Mentor Commented:
"the DC is: Windows Server 2003 Std. R2 SP2 x64 with Windows 2000 native mode  functionality level"

You should raise the forest and domain functional levels to Windows 2003:
http://support.microsoft.com/kb/322692

0
All Courses

From novice to tech pro — start learning today.