Error in configuring remote desktop license

Question

_{Monday, September 29, 2014 2:19 PM}

Hello --

I am going through the motions of configuring remote desktop licensing through the windows powershell. The commands that I have entered are the following:

$obj = gwmi –namespace “Root/CIMV2/TerminalServices” Win32_TerminalServiceSetting

$obj.ChangeMode(2)

The following command is what I have used on other Windows 2012 servers to have the system in question point to the license server that will be servicing it:

$obj.SetSpecifiedLicenseServerList(“PHSCTXLS03”)

However, the error message that I am encountering is as follows:

Exception calling “SetSpecifiedLicenseServerList” | “”

At Line:1 char:1

$obj,SetSpecifiedLicenseServerList(“PHSCTXLS03”)

                CategoryInfo                     NotSpecified: (:) [], MethodInvocationException

                FullyQualifedErrorId       “WMIMethodException

Can someone provide help on this?

Thanks.

All replies (11)

_{Monday, September 29, 2014 3:20 PM ✅Answered}

Hi,

Are you launching PowerShell as admin?

Don't retire TechNet! - (Don't give up yet - 13,085+ strong and growing)

_{Friday, October 3, 2014 3:28 PM ✅Answered}

Hi Kaplan71,

Any update on this issue? If there is anything else regardingthis issue, please feel free to post back.

In addition, to configure the License Sever Manually with Powershell, please also check these articles:

RD Licensing Configuration on Windows Server 2012

PowerShell and RD Session Host

If there is anything else regarding this issue, please feel free to post back.

If you have any feedback on our support, please click here.

Best Regards,

Anna Wang

TechNet Community Support

_{Monday, September 29, 2014 3:08 PM}

Hello --

I made some progress on this issue. My user account is a member of the Domain Users group, and also is a member of the local Administrators group. I logged in as the local Administrator, did not encounter the error mentioned in my posting, and was able to complete the license configuration process.

Why would my account have this problem?

Thanks.

_{Monday, September 29, 2014 3:57 PM}

Hello --

I may not have done that. I'll try it again on another system, and post the result.

Thanks.

_{Tuesday, October 7, 2014 4:20 PM}

Hi Kaplan71,

Since we have not heard from you for a while, I assume that this issue is solved, if there is anything else regarding this issue, please feel free to post back.

Best Regards,

Anna Wang

_{Tuesday, October 7, 2014 4:30 PM}

Hello --

My apologies to everyone. I have been swamped with work as of late. Yes, the issue has been resolved, and please accept my thanks for the help.

_{Tuesday, October 7, 2014 4:34 PM}

Glad to help out, very happy to hear that your issue was resolved.

Don't retire TechNet! - (Don't give up yet - 13,085+ strong and growing)

_{Tuesday, October 21, 2014 11:00 PM}

FWIW I'm getting the same exact error and HAVE launched PowerShell as Admin.  As someone who provides limited administration of this multi-national enterprise AD environment, my account does not have rights to write to AD but only in a limited capacity.  The articles I've read don't seem to cover what level of priviledge your account must have.  Below is what I've seen when attempting to change the RD SH Licensing Server.

Dale Unroe

_{Friday, December 19, 2014 3:07 PM}

Start the 64bit ISE with "run as administrator" and you should be fine. the x86 version gives this error.

_{Wednesday, August 30, 2017 12:18 AM | 1 vote}

Start the 64bit ISE with "run as administrator" and you should be fine. the x86 version gives this error.

Had the exact same problem and kept hitting a wall trying to fix this.

Then ran it with 64bit ISE in admin and VOILA!

This solved the issue for me!!! (and saved my butt with our customer ;-) ) Thanks! 

_{Monday, June 25, 2018 9:36 AM}

Hi,

Almost same issue: I can SetSpecifiedLicenseServerList(), but I cannot ChangeMode(4), which gives me the exact same error. I tried with non-elevated Powershell, elevated Powershell, with my credentials, with domain admin credentials, ISE 64bit, ISE 32bit... None of them has worked out.

Any guess??