Windows Server Standard 2008 won't change TS licensing mode

I have new Dell server running "Windows Server Standard" (no 2008 in the edition name), SP2, that I'm trying to make a Terminal Server.  I've added the TS and TS Licensing roles and installed 10 user cals.  When I open the Terminal Services Configuration app, it says the "Terminal Services licensing mode" is "Personal Terminal Server".  When I try to change that a "Per User" mode I get an error

"Unable to complete operation: 8007013D".  

I get this error regardless of whether I let it discover it's licensing server or explicitly it set it.  I've been able to find lots of references to this error on SBS 2008, but nothing for Server Standard.

Thanks for the help.
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Darius GhassemCommented:
Are you sure you are using Standard and not SBS?
wanderson_purAuthor Commented:
I've pretty sure; I've attached a screenshot of the system properties screen.  I don't see any reference to SBS on there.
Darius GhassemCommented:
Well looks right.
The 7 Worst Nightmares of a Sysadmin

Fear not! To defend your business’ IT systems we’re going to shine a light on the seven most sinister terrors that haunt sysadmins. That way you can be sure there’s nothing in your stack waiting to go bump in the night.

wanderson_purAuthor Commented:
Here's a screencap of the error and the configuration settings I'm trying to change Term services config
Darius GhassemCommented:
personal terminal server: In general context, refers to a client SKU target machine that hosts remote desktop sessions. From a terminal service licensing perspective, the behavior of a personal terminal server is similar to that of a terminal server in remote administration mode. Thus any behavioral reference to a personal terminal server in this document essentially implies that the particular behavior is valid for a terminal server in remote administration mode as well. The term personal terminal server is therefore used to encompass all connections where either the end point is a client SKU operating system or is a terminal server running in remote administration mode.

You need to put the Terminal Server in Application Mode this is currently running in Remote Admin Mode
wanderson_purAuthor Commented:
Thanks for the response but I'm a little confused.  How do I put the server in Application mode, if not by assigning it a different licensing scheme (i.e. the screenshot provided with the error)?
wanderson_purAuthor Commented:
We were able to find a solution; apparently the WMI repository was corrupt.  We resolved this by running

winmgmt /salvagerepository

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
wanderson_purAuthor Commented:
No other responses provided a working solution
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2008

From novice to tech pro — start learning today.