Per Server to Per Seat - operation failed!

Oh man! Ad-blocking software has been detected! :'(

This website is run by the community, for the community... and it needs advertisements in order to keep running. Blocking our ads means your killing our stats!
Please disable your ad-block, or become a premium member to hide all advertisements and this notice.

I'm runing through a scenario in my virtual lab, below are some details:

My objective was to split the tasks of an over worked very old W2K server to 3 new servers and then add in a terminal server

Old Server W2k
-DC
-DNS
-DHCP
-WINS
-F&P Sharing
-RRAS
-MS SQL

New Server 1 2003
Primary Role - DC

New Server 2 2003
Primary Role - F&P Sharing

New Server 3 2003
Primary Role - MS SQL

New Server 4 2003
Primary Role - Terminal Server

after performing all of this i had a the next day after a little :hhhmmm I realised that i had forgot to switch the licence modes from per server to per seat(user/device), so i fired up all the vm's and changed it over, all went well apart from the terminal server everytime i try to change it I get this error

{Operation Failed} The requested operation was unsuccessful

when i check the event logs there nothing relating to this error, is this becuase its a TS?

Thanks in advance

 

Yip its located on the DC(Active and issuing temps) and the TS is picking it up ok


[Added]
Screenshot of error

 

Check these pages for more info.. not sure if they will shed any light on your specific uninformative error...

http://help.lockergnome.com/windows2/Change-TS-licensing-device-user-ftopict450162.html

http://technet2.microsoft.com/windo...8857-4f07-9f45-d29488d6ab031033.mspx?mfr=true

 

Hey nice 1 blue the second link done the trick with the Run As command and the local admin details, job done (have some rep and a on me)

 

Sure was

 

indeed, was one of the reasons i dismissed it


[Edit]
at the time i was just about to install some software to the server so the server was in install mode(not sure if that made any diffrence)

 

Cool, i thought that might be the problem.. glad to be of some assistance Thomas

 

I love the word *might* as it also means, might not. Gotta love Microsoft