i wanted to try rdweb etc on my server, so i did a hyper-v install of the os on my server... however i didnt notice i still was connected to my base os... so basically i installed rdweb, gateway etcetc all of thoose and configured.

Once i realized my misstake i uninstalled all those roles from the server and now im stuck with user profile disks wich i have no use for, just annoying :)

Is there any way to revert back? cant find anything on the internet

Hello

We have provisioned an Azure VM that is used as an RDS server. The operating system for the Server is 2012r2.

We started using the server on november 7th, and it has bluescreened with the same error 6 times. Both the dump-file and google-searches indicates that the process rdbss.sys might be the cause of the problem. I will attach the dump file below.

Microsoft (R) Windows Debugger Version 10.0.14321.1024 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\*\OneDrive\Documents\113016-42796-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*
Executable search path is:
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows 10 Kernel Version 14393 MP (4 procs) Free x64
Product: Server, suite: TerminalServer DataCenter
Built by: 14393.447.amd64fre.rs1_release_inmarket.161102-0100
Machine Name:
Kernel base = 0xfffff803`71292000 PsLoadedModuleList = 0xfffff803`71597060
Debug session time: Wed Nov 30 12:13:10.387 2016 (UTC + 1:00)
System Uptime: 0 days 3:31:24.083
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
.

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

..............................................................
................................................................
.............................
Loading User Symbols
Loading unloaded module list
............................

************* Symbol Loading Error Summary **************
Module name            Error
ntoskrnl               The system cannot find the file specified

You can troubleshoot most symbol related issues by turning on symbol loading diagnostics (!sym noisy) and repeating the command that caused symbols to be loaded.
You should also verify that your symbol search path (.sympath) is correct.
*** WARNING: Unable to verify timestamp for rdbss.sys
*** ERROR: Module load completed but symbols could not be loaded for rdbss.sys
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 27, {fcb0027c, ffffdb00e2f683d8, ffffdb00e2f68010, 0}

***** Kernel symbols are WRONG. Please fix symbols to do analysis.


Followup:     MachineOwner
---------


************* Symbol Path validation summary **************
Response                         Time (ms)     Location
OK                                             C:\Users\*\Desktop
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

RDR_FILE_SYSTEM (27)
    If you see RxExceptionFilter on the stack then the 2nd and 3rd parameters are the
    exception record and context record. Do a .cxr on the 3rd parameter and then kb to
    obtain a more informative stack trace.
    The high 16 bits of the first parameter is the RDBSS bugcheck code, which is defined
    as follows:
     RDBSS_BUG_CHECK_CACHESUP  = 0xca550000,
     RDBSS_BUG_CHECK_CLEANUP   = 0xc1ee0000,
     RDBSS_BUG_CHECK_CLOSE     = 0xc10e0000,
     RDBSS_BUG_CHECK_NTEXCEPT  = 0xbaad0000,
Arguments:
Arg1: 00000000fcb0027c
Arg2: ffffdb00e2f683d8
Arg3: ffffdb00e2f68010
Arg4: 0000000000000000

Debugging Details:
------------------

DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING:  14393.447.amd64fre.rs1_release_inmarket.161102-0100

SYSTEM_MANUFACTURER:  Microsoft Corporation

VIRTUAL_MACHINE:  HyperV

SYSTEM_PRODUCT_NAME:  Virtual Machine

SYSTEM_VERSION:  7.0

BIOS_VENDOR:  American Megatrends Inc.

BIOS_VERSION:  090006

BIOS_DATE:  05/23/2012

BASEBOARD_MANUFACTURER:  Microsoft Corporation

BASEBOARD_PRODUCT:  Virtual Machine

BASEBOARD_VERSION:  7.0

ADDITIONAL_DEBUG_TEXT:
You can run '.symfix; .reload' to try to fix the symbol path and load symbols.

WRONG_SYMBOLS_TIMESTAMP: 5819bd1f

WRONG_SYMBOLS_SIZE: 820000

FAULTING_MODULE: fffff80371292000 nt

DEBUG_FLR_IMAGE_TIMESTAMP:  5819bd1f

DUMP_TYPE:  2

BUGCHECK_P1: fcb0027c

BUGCHECK_P2: ffffdb00e2f683d8

BUGCHECK_P3: ffffdb00e2f68010

BUGCHECK_P4: 0

EXCEPTION_RECORD:  ffffdb00e2f683d8 -- (.exr 0xffffdb00e2f683d8)
ExceptionAddress: ffffdb00e2f683e8
   ExceptionCode: 0130ec30
  ExceptionFlags: 00000001
NumberParameters: -487160856
   Parameter[0]: ffffdb00e2f682e0
   Parameter[1]: ffffdb00e2f68010
   Parameter[2]: ffffae088a586a10
   Parameter[3]: ffffae088861e970
   Parameter[4]: ffffae088943a6b0
   Parameter[5]: 000000000e400200
   Parameter[6]: 0000000000000000
   Parameter[7]: 0000000000000000
   Parameter[8]: 0000000000000000
   Parameter[9]: ffffdb00e2f68398
   Parameter[10]: ffffdb00e2f68398
   Parameter[11]: ffffae087c33e6e0
   Parameter[12]: ffffae087c33e6e0
   Parameter[13]: 0000000001000000
   Parameter[14]: 0000000000000000

CONTEXT:  ffffdb00e2f68010 -- (.cxr 0xffffdb00e2f68010)
rax=0000000000000000 rbx=0000000000400800 rcx=0000000000000000
rdx=c040000000000004 rsi=0000000000000001 rdi=0000000000000002
rip=ffffdb00e2f68368 rsp=ffffffffffffffff rbp=ffffffffffffffff
 r8=0000000000000000  r9=0000000000000000 r10=0000000000000000
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=000c630500000000
iopl=1 vip vif ov up ei pl nz na pe nc
cs=8048  ss=e2f6  ds=e2f6  es=db00  fs=ffff  gs=8048             efl=ffffdb00
8048:8368 ??              ???
Resetting default scope

CPU_COUNT: 4

CPU_MHZ: 898

CPU_VENDOR:  GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 2d

CPU_STEPPING: 7

CPU_MICROCODE: 0,0,0,0 (F,M,S,R)  SIG: FFFFFFFF'00000000 (cache) 0'00000000 (init)

CUSTOMER_CRASH_COUNT:  1

CURRENT_IRQL:  0

ANALYSIS_SESSION_HOST:  NOOSL9XWDS32

ANALYSIS_SESSION_TIME:  11-30-2016 14:59:32.0276

ANALYSIS_VERSION: 10.0.14321.1024 x86fre

LAST_CONTROL_TRANSFER:  from 0000000000000000 to ffffdb00e2f68368

UNALIGNED_STACK_POINTER:  ffffffffffffffff

STACK_TEXT:
ffff9b00`e7679488 fffff807`3760fd19 : 00000000`00000027 00000000`fcb0027c ffffdb00`e2f683d8 ffffdb00`e2f68010 : nt+0x14a510
ffff9b00`e7679490 00000000`00000027 : 00000000`fcb0027c ffffdb00`e2f683d8 ffffdb00`e2f68010 00000000`00000000 : rdbss+0xfd19
ffff9b00`e7679498 00000000`fcb0027c : ffffdb00`e2f683d8 ffffdb00`e2f68010 00000000`00000000 00000000`00000000 : 0x27
ffff9b00`e76794a0 ffffdb00`e2f683d8 : ffffdb00`e2f68010 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfcb0027c
ffff9b00`e76794a8 ffffdb00`e2f68010 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xffffdb00`e2f683d8
ffff9b00`e76794b0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 ffffae08`8a654ed0 : 0xffffdb00`e2f68010


STACK_COMMAND:  kb

THREAD_SHA1_HASH_MOD_FUNC:  5474fa73798049031c2a0caa39d100f3f2eab020

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  87ff8d166822c95f9c36ce424701def37be42c3e

THREAD_SHA1_HASH_MOD:  5474fa73798049031c2a0caa39d100f3f2eab020

FOLLOWUP_IP:
rdbss+fd19
fffff807`3760fd19 cc              int     3

FAULT_INSTR_CODE:  cf8b49cc

SYMBOL_STACK_INDEX:  1

FOLLOWUP_NAME:  MachineOwner

BUGCHECK_STR:  5819BD1F

EXCEPTION_CODE: (NTSTATUS) 0x5819bd1f - <Unable to get error code text>

EXCEPTION_CODE_STR:  5819BD1F

EXCEPTION_STR:  WRONG_SYMBOLS

PROCESS_NAME:  ntoskrnl.wrong.symbols.exe

IMAGE_NAME:  ntoskrnl.wrong.symbols.exe

MODULE_NAME: nt_wrong_symbols

SYMBOL_NAME:  nt_wrong_symbols!5819BD1F820000

BUCKET_ID:  WRONG_SYMBOLS_X64_14393.447.amd64fre.rs1_release_inmarket.161102-0100_TIMESTAMP_161102-101703

DEFAULT_BUCKET_ID:  WRONG_SYMBOLS_X64_14393.447.amd64fre.rs1_release_inmarket.161102-0100_TIMESTAMP_161102-101703

PRIMARY_PROBLEM_CLASS:  WRONG_SYMBOLS

FAILURE_BUCKET_ID:  WRONG_SYMBOLS_X64_14393.447.amd64fre.rs1_release_inmarket.161102-0100_TIMESTAMP_161102-101703_5819BD1F_nt_wrong_symbols!5819BD1F820000

TARGET_TIME:  2016-11-30T11:13:10.000Z

OSBUILD:  14393

OSSERVICEPACK:  0

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK:  144

PRODUCT_TYPE:  3

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

OSEDITION:  Windows 10 Server TerminalServer DataCenter

OS_LOCALE:

USER_LCID:  0

OSBUILD_TIMESTAMP:  2016-11-02 11:17:03

BUILDDATESTAMP_STR:  161102-0100

BUILDLAB_STR:  rs1_release_inmarket

BUILDOSVER_STR:  10.0.14393.447.amd64fre.rs1_release_inmarket.161102-0100

ANALYSIS_SESSION_ELAPSED_TIME: 1faa

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:wrong_symbols_x64_14393.447.amd64fre.rs1_release_inmarket.161102-0100_timestamp_161102-101703_5819bd1f_nt_wrong_symbols!5819bd1f820000

FAILURE_ID_HASH:  {d82425fb-28f9-fe3c-99c4-cbc6653270b1}

Followup:     MachineOwner
---------

Hi, 

I am getting this error when I try to RDP and login to a VM (Windows 2012) server.  This VM is running off  ESXi which we have already purchased data center edition license.  

Please advise how to fix.  

Thanks.  

We have built a Windows server 2012 R2 RDS server, and setup the whole deployment on one server, Gateway, Broker, licensing, session host, and collection.

But when we go to shadow the user using Server manager or command line mstsc /shadow:n when get this very helpful error:   Unspecified error in a Window called Shadow Error

I have tested Shadowing on another networks server with a similar setup and it works fine, only difference is the Active directory server are 2008 vs this one that doesn't work being 2003.

I have also tested using local accounts and still get the same error, and there is not a lot on the web regarding this error and RDS shadowing

Hello everyone,

I have a remote desktop services server under Windows Server 2012 that only publishes one application. All of the roles are on this server. The AD domain that this server is currently a member of is in the process of being decommissioned. I need to remove this server from its current domain and add it to the main domain and get RDS to function again. All of the AD users/groups have already been recreated on the main domain.

Since the production RDS server is a VM, I cloned it and performed all of the necessary changes and added it to the main domain so that I could test reconfiguring the RDS setup. The problem that I can't seem to get by is how to add the new server name/domain to the server pool. Under Server Manager > Remote Desktop servers > Overview I see the following message: "The following servers in this deployment are not part of the server pool: 1.old-server-name.olddomain.local The servers must be added to the server pool"

Any help would be greatly appreciated.

Vossa

Vossa

Hi All,

I am trying to Retrieves a list of personal virtual desktops and associated user accounts using PS command, Export-RDPersonalVirtualDesktopAssignment -CollectionName "XYZ" -Path "c:\temp\XYZ.csv"

Now using this command I can only get the result from a specific collection, Please suggest what to do if I need to get the result from multiple collection's.

Regards

Abhinav

Abhinav

We are trying to get a published application to work on Window Server 2012 R2 that requires the %CLIENTNAME% environment variable. When logged in locally on that Remote Desktop Server the variable is available and works as expected. When we publish our application and try to reference %CLIENTNAME% we then receive an error that nothing is set for %CLIENTNAME%. I have checked the HKCU\Volatile Enviroment\ and I can see the session with the CLIENTNAME there.

If we change the application to use %USERNAME% or %COMPUTERNAME% than it will input the corresponding values, so I know it is reading some environment variables. 

Our clients are Windows 10.

Hi,

has anybody else experienced the issue with RDS Website causing IIS to throw an error 500 after installation?

Solution for me was to reconfigure the IIS AppPool to run under "NetworkService" and give "Network Service" full permissions on "C:\Windows\temp"

Is this a known issue?

Cheers
David

My blog on all about automation: www.david-obrien.net | me on Twitter: @david_obrien Please remember to mark the post(s) that helped you resolve the issue (even if it was your own)

Hello, I have a question:

does RDP protocol supports TLS 1.1. I did find similar question for TLS 1.2:

http://social.technet.microsoft.com/Forums/en/winserverTS/thread/e308a2ac-2443-4a24-abc7-fab6079fac86

I am trying to enable SSL encryption for RDP to my Windows Server 2012 servers. I have a wildcard certificate with a private key from Digicert that is good for *.mydomain.com. The Enhanced key usage is:

Server Authentication (1.3.6.1.5.5.7.3.1)
Client Authentication (1.3.6.1.5.5.7.3.2)

And key usage is:

Digital Signature, Key Encipherment (a0)

I put the cert in the Personal Store and the Remote Desktop Store. 

To force SSL Connections I enabled the following settings in Group Policy:

Recently, I switched from AT&T to TWC Road Runner for my ISP. When I had AT&T my remote desktop worked fine and I was able to remote into work. since I got Road Runner, I can VPN into the network,but when I get to Remote Desktop it gives me "This computer can't connect to the remote computer. Try connecting again If this promblem continues please contact....... The IP Addresss that the router is "getting assigned" is the same as a computer on my network. This that the problem? Since I have tried disconnecting the router, release and renewing....I don't know what else to do. Can any one offer any experience on this matter. Thank You

Server 2012 with RDS. We have an apache server that forwards (reverse proxy) 443 connections to the appropriate server. However, it appears apache does not support rpc over https. So, when we launch a remoteapp resource using the webfeed.aspx, we get remote desktop gateway is unavailable. If we change the port from 443 to x443 in remote desktop gateway manager and configure our firewall to allow port x443 to the RDS server, we get the same error. What is the correct way to setup RD Gateway in this environment?

Does the remoteapp on the client know to use the new port x443? I have removed the resources and reconfigured for the resources

I have confirmed the remoteapp piece is using 443 according to the apache ssl logs. How to use different port on remoteapp piece on client?

We have a RDS farm with a misbehaving gateway. A user can log on to RDWEB and then open a remote app but fails when authenticating. If we bypass the GW for local addresses then a user can open the app without issue. So looks like the GW tha is the problem.

One thing that we have noticed is if you open RD Gateway Manager and then open the properties of the GW (right click on the server) and then select the server farm tab, if you add the GW as a farm member it displays the following error:

Status: Error

Details: The RPC/HTTP Load Balancing service is not functioning on this RD Gateway server farm member.

However the service is running.

We have a number of farms in different domains. All but one worked. When I highlighted this to other engineers the AD engineer noticed that policy had not applied to the working GW server. When he applied policy the GW it ended up in the same state as the others.

So something in group policy seems to be breaking this but my AD experience (and access) is limited so its like a needle in a haystack.

Can anyone help point me in the direction here? Has anyone seen this error/issue before?

I'm attempting to setup a Windows 2016 RDS Standard Deployment for Session Hosting.  The layout is as follows:
RDS01 - RDS Connection Broker and Web Access
TS02 - RDS Session Host
TS03 - RDS Session Host

The domain these servers are part of has (1) Windows 2008 Server and (2) Windows 2016 Servers acting as DCs.  The domain is running at Windows 2003 Functional Level.

All servers are on a single routed network with no firewall between them.  All DNS A and PTR records for all servers exist and resolve on all hosts.  All servers can be pinged by each other. In other words, there are no network connectivity issues.

I've setup the RDS deployment several times w/ the same results.

The Issue
I can login via the RDWeb interface on RDS01 from a Win10 desktop and connect to the published RDP desktop without issue (i.e. no error messages to the user) and no errors in the logs.  When I try to directly RDP to RDS01, I successfully authenticate as a user (per the event log) but get an error stating that the user doesn't have access to the system.  In the event log I get event id 1306 with the message of "Remote Desktop Connection Broker Client failed to redirect the user <domain>\<test user>.  Error: NULL".  

If I RDP to RDS01 as an administrator, I get the same error message but the RDP session opens and presents the desktop on RDS01.

I can RDP directly to TS02 or TS03 and login as a user and open the RDP session.  Redirection to some degree appears to be working in that I can disconnect a user session from TS02 and RDP to TS03 and the session is redirected back to TS02.  The event logs on RDS01 record this happening as well.

What I've tried already
1. In searching this event 1306 issue, I found several posts with this exact same behavior in WS 2012/R2.  Most "solutions" suggested point to the fact that the RDS Session Broker doesn't have sufficient authority to look up the users AD group membership via the tokenGroupsGlobalAndUniversal attribute or AuthzInitializeContextFromSid API function which leverages the tokenGroupsGlobalAndUniversal attribute.  (Example: https://social.technet.microsoft.com/Forums/windowsserver/en-US/29733a87-dbda-47bc-8b37-6eeac5ab5a0a/2012-rds-nonadministrators-can-not-access-vdi-pool?forum=winserverTS#97d883f1-7a64-4d02-9492-309638f92e79 )

The service is running as "Network Service" which does have network access via the Computer Object's authority in AD.  So following Microsoft's instructions (https://support.microsoft.com/en-us/kb/331951), I've added RDS01 to both the Windows Authorization Access Group and Pre-Windows 2000 Compatibility Access groups and rebooted RDS01 with the same results.  

2. I've verified the Windows Authorization Access Group has rights to read the tokenGroupsGlobalAndUniversal property/attribute on my test users and the computer objects of the servers.

3. I've setup an AD Service account following Microsoft's instructions (https://support.microsoft.com/en-us/kb/842423) with a similarly described access issue.  The service account user was added to the Windows Authorization Access Group.  This was unsuccessfully as well w/ the same event 1306 error.

4. I ran the following powershell commands to verify access of the Connection Broker to the OU (https://technet.microsoft.com/en-us/library/jj215512.aspx#)

Test-RDOUAccess -Domain [redacted.domain] -OU "Computers" -ConnectionBroker rds01.[redacted.domain] -verbose

This failed so I ran the following to grant access

Grant-RDOUAccess -Domain watsons.local -OU "Computers" -ConnectionBroker rds01.watsons.local -verbose 

The Test-RDOUAccess then succeeded.

I repeated this for the OUs that contained the users and the server computer objects.

I've disabled all GPOs to ensure there's no conflicts but have seen no change in the behavior or error messages.

With all that, I've exhausted every option that I can find to resolve this error to gain the expected functionality.  As a work around for the moment, I've setup a round-robin DNS A record that points to TS02 and TS03 w/ a very short TTL.  This gives the test users the ability to login and atleast test the desktop functionality.

Sorry for being so long winded with this but I thought it better to put all the cards on the table.

I'm open to any and all suggestions.

Thx!

Hi all,

I am trying to setup our RDS Web Access to authenticate via RSA SecureID using the RSA Web agent on the RDS Web Access-server. I do not have a ISA/TMG server and i will not be able to get this. I have been looking alot arround the net for a fix for this, but the only guides and questions out there is when people are using an ISA.

I got RDS Web Access and Gateway on the same server and a RDS farm behind. It works great without the RSA authentication.

I have installed the RSA Web Agent on the server and it intergrates perfect with IIS and on a testpage it has been tested and it works.

But when i enable the "RSA SecureID Web Access Authentication" on the Default Web Site, the /RDWeb just breaks down with Internal Server error 500. When enabling i get an error with "This web site has one or more applications which have custom application pool that is incompatible with the Web Agent" I'd figure that the pool that is incompatible is the RDWebAccess-pool.

The server error 500 gives me the following information (accessed from localhost):

Module SecurIDModule
Notification BeginRequest
Handler StaticFile
Error Code 0x00000000
Requested URL https://localhost:443/RDWeb
Physical Path C:\Windows\Web\RDWeb
Logon Method Not yet determined
Logon User Not yet determined

It happens even borefore i enable the RSA Authentication for the RDWeb application.

Has anyone got RDS Web Access to work directly with the RSA Web agent?

I hope you can help me out here - thanks.

/rGjorret

I keep getting Event ID 20499 "Remote Desktop Services has taken too long to load the user configuration from server \\SERVERNAME for user USERNAME" in our event logs for multiple servers that are running 2012 R2

I noticed that when this happens the user often is missing items that get applied via group policies such as desktop wallpapers and mapped drives.  

I am also using the Microsoft Remote Desktop for Mac that was release yesterday on another Mac computer and for certain users it won't launch the redirected folder that I specified when I get this Event ID 20499

I seem to have a problem with Windows Server 2012R2 remote desktop services. From time to time i cannot manage my servers. We have several Remote desktop farms, one 4 node widows Server 2008 RTM farm, a single Node Windows Server 2012r2 farm and a 6 node Windows Server 2012r2 farm. we have no issue with the Windows Server 2008 RTM farm, but have a lot of issue's with the two other ones. the same issue occurs on both nodes, and the  issue is that i cannot manage them. In server manager i get the following error: "The WinRM client cannot process the request. It cannot determine the content type of the http response from the destination computer. the content type is absent or invalid."

When i try to manage the RD deployments via powershell i get:

PS M:\> Get-RDRemoteApp -ConnectionBroker connectionbroker.domain.group
Get-RDRemoteApp : A Remote Desktop Services deployment does not exist on connectionbroker.domain.group. This operation can be performed after creating a deployment. For information about creating a deployment, run "Get-Help New-RDVirtualDesktopDeployment" or "Get-Help New-RDSessionDeployment". 

last week i had it on the single node, but could manage the node from the other 6 node cluster. Rebooted the single node over the weekend, and the issue was resolved. This morning the issue returned, in which i was unable to manage Remote desktop deployment from all nodes, except one. All published applications are running fine, but cannot the deployment. Rebooting the node resolves the issue for that node.

Have been looking into the issue, where it could be that the kerberos ticket is to large for the logged-on user. However when i log on with a user which is only member of the domain admins, the issue isn't resolved. So think it is not related to where the kerberos, or NTLM authentication issue described here:

http://oyvindnilsen.com/solution-for-powershell-remoting-error-it-cannot-determine-the-content-type-of-the-http-response-from-the-destination-computer/

all servers are fully patched.   

Answers provided are coming from personal experience, and come with no warranty of success. I as everybody else do make mistakes.

Hi,

Is there any way to specify multiple RDS License Servers (or add an additional one) with powershell?

Tried:

$obj.SetSpecifiedLicenseServerList("srv-rds-lic01.local.net","srv-rds-lic02.local.net")

and:

$obj.SetSpecifiedLicenseServerList("srv-rds-lic01.local.net,srv-rds-lic02.local.net")

Specifying one entry works without any issues.

Thanks.

Hi,

After looking at other threads, I couldn't find an direct answer to this problem.

For a very SMB client (max 5 RDP sessions, first and only server) I'm trying to install a single box running  WS2012 Foundation  (single DC) as recommended in this KB article (http://support.microsoft.com/kb/2833839) and I'm stuck in step 8 while trying to configure the Remote Desktop Session Host role with to use the localRemote Desktop Licensing server.

The Powershell command fails with the following errors:

PS C:\Users\Administrateur> $obj.SetSpecifiedLicenseServerList("LicServer")
Exception lors de l'appel de « SetSpecifiedLicenseServerList » : «  »
Au caractère Ligne:1 : 1
+ $obj.SetSpecifiedLicenseServerList("LicServer")
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [], MethodInvocationException
    + FullyQualifiedErrorId : WMIMethodException

Thanks for any help

Jeff