Lee
Hi
I am trying to run a PowerShell command to add an application from a network share onto my Remote Desktop Server 2016. When I run the command, it shows the following:
New-RDRemoteApp : A Remote Desktop Services deployment does not exist on SR1RDS002.ad.collinsco.com. 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".
At line:1 char:1
+ New-RDRemoteApp -CollectionName RD_APPS_1 -DisplayName BankLink -File ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (:) [Write-Error], WriteErrorException
+ FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorException,New-RDRemoteApp
The Remote Desktop Server is running and I have staff currently using the applications on it therefore do not understand why this is happening.
This is very frustrating as I have two applications that run from a Network share that I need to have published.
Can anyone please help me with this issue? Thanks
Hi All
I have a virtualised (VMWare) RDS 2012R2 environment with 20 Session hosts spread across 6 Dell ESXI Hosts - 2 Sets of different PowerEdge Models. Over the past 4-6 weeks we have started to get multiple event 7011's followed by a 7046.
A timeout (30000 milliseconds) was reached while waiting for a transaction response from the UmRdpService service.
The following service has repeatedly stopped responding to service control requests: Remote Desktop Services UserMode Port Redirector
At this point some existing connected users cant sign out and applications start to crash including explorer.exe. Trying to shutdown via the GUI just hangs and the only way to get the server back is to reset the power using vSphere console.
Applications on the Session Hosts are mainly MS Office 2016, Acrobat Reader, 7Zip and Webroot AV. Windows OS and applications are fully patched and up to date and Dell Firmware and drivers are fully up to date.
Users connect in via RemoteApp and local drives and printers are redirected into their sessions.
The weird thing is, like clockwork the crashes happen at the end of each day usually between 16:00 - 18:00 - To me its like a degradation symptom or perhaps its the actions of users disconnecting or logging off their session - Its affecting a couple of servers each day.
On top of this, it appears 7011, 7046 results in a BSOD. I have grabbed the Memory.dmp file and opened it with WinDbg.
Im now trying to figure out the dmp - uploaded to PasteBin here (happy to paste dmp here but didnt want to "dump" to much information in the post)
What stands out to me is rdbss.sys
Probably caused by : rdbss.sys ( rdbss!__RxAcquireFcb+1f3 )
IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0000000000000000, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80179d3ba44, address which referenced memory
BUCKET_ID: AV_rdbss!__RxAcquireFcb
PRIMARY_PROBLEM_CLASS: AV_rdbss!__RxAcquireFcb
My rdbss.sys version - 6.3.9600.18895
Can anyone help to try and decipher the above and suggest next/best cause of action?
Many thanks :)
Hello,
mstsc provides an option to connect to an existing session on remote machine. Does the Remote Desktop ActiveX Control also support this?
Thanks in Advance.
Best,
Sumit
Running all Windows Server 2016. I have server rds1.subdomain.domain.com that I can not add session host role to from server rdssvr1.domain.com. I have successfully added rds1.subdomain.domain.com to the server manager of rdssvr1.domain.com. I have added the role of RDS Session Host on rds1.subdomain.domain.com locally but it does not seem to be recognized by rdssvr1.domain.com that session host role has been added.
Any suggestions would be greatly appreciated!!
Just a preface here, I understand why this is happening, but not sure why it is happening for one situation vs. another.
I have an older 2008R2 TS farm that I inherited that is being decommissioned in favor of a new Server 2016 Setup. Note that in both situations, the TS farm is off domain to the users and has a separate Active Directory.
When connecting to the 2008R2 environment, users by default are allowed to save their credentials (Remember Me Box)
When connecting to the new 2016 environment, cached credentials cannot be used and the "Remember Me" box is missing
I know that by default if the destination RDS environment is off domain that windows blocks this by default, but is this being done on the server or client side? I'm not sure why it would allow saving credentials for one environment vs. the other if they are both off the domain.
Jay Schwegler
Hello,
Is there any reference on RDP session network requirement in term of :
Thanks
I couldn't find the Remote Desktop Services Manager snap-in in W2016 TP4
Browsing the web I understood that it is already missing from W2012. Yet I failed to find a replacing tool.
I mean, how to get an overview of who is connected to which RDS servers ?
I have numerous RDS servers, 2003R2 and 2008 R2. They are not members of a farm or alike. No broker, No roaming profiles. We kept things simple. They all are independent servers. The virtualization layer taking care of the "high availbility".
At the moment I have a MMC running in a W2008 server, where I have added all my servers (note that monitoring a W2016 TP4 RDS is OK...).
But will I monitor all my RDS servers from a W2016 or W2012 server ?
Hello, I have a legacy in-house developed application I am trying to deploy as RemoteApp. The application is installed in C:\T&N directory and some user specific configuration data is located in a couple of files inside that directory.
I deployed the application installing and it is shown in the Web gateway. I can run it remotely with no issues but the problem is that the user data is not saved on a per user basis, but the last user that runs the app have his config data saved for the next time the app run.
It is like this. The app.exe is installed in C:\T&N and there is a config file C:\T&N\user.config. This user.config have personalization settings and the location of some databases specific to the user running the app.
Is there a way I can include some files in C:\T&N directory into the user profile disk so each user will have his own copy of the config file? Everything else runs fine except this critical little thing.
Hi,
I've got 2 separate colos with the following servers setup, clients can access the Remote Apps though the cloud and the employee's can access the Servers using remote desktop connection but when I try to access with Windows 10 I get the following error from either cloud or using the rd gateway to access the servers using remote desktop connection.
Error: RemoteApp Disconnection
"Your Computer can't connect to the remote computer because an error occurred on the remote computer that you want to connect to. Contact your network administrator for assistance."
The first setup is the following
Windows 2012
4 x Servers with RD Session Host
2 x Servers with RD License and RD Connection Broker (High Availability)
2 x Servers with RD Gateway and RD Web Access
Windows 2012 R2
4 x Servers with RD Session Host
2 x Servers with RD License and RD Connection Broker (High Availability)
2 x Servers with RD Gateway and RD Web Access
The setuo is default and the error is happening on the RD Gateway computers.
I've tried to change the security of the collection but it made no difference, I've applied all the current patches to the RD Gateway computers.
On the Gateway I have a user group to access the but there are no computer groups in the connection authorization policy.
The resource authorization policy has the same user group and access to all network resources.
I've tried to find a solution but haven't been able to find much about RDP 10.0
I have RDS on one server, I am able to currently logon and RDP to other machines. I setup a new windows server "Server1" and when I try to RDP from RDS it is saying that the "Publisher of the remote connection cannot be recognized", if I click connect, I am asked to validate my account with my RDS server and then it returns an error, "Your computer can't connect to teh remote computer because the RDS Gateway server address requested and the certificate subject name do not match". When I click on view certificate, it is a cert I do not even recognize. I checked the certificated in the RDS gateway and they are all correct. What could be causing this on new RDP sessions only?
Thanks
Pat
I have a friend who needs to run 5 concurrent RD Sessions. He purchased Windows Server 2019 Standard with 5 RDS CALs and a computer to install it on. He has asked me to set it for him.
This is the situation. We have a single program that needs to run on the server. Each person needs to be able to log in and run that software on their own RDS login. Seems like a very simple setup.
My questions are:
1. Can I do this with one machine?
2. Can I do this with the Windows Server he bought?
3. Can anyone recommend a guide so I don't spin my wheels on things that aren't necessary?
Thanks.
What firewall ports need to be open between Windows 2008 R2 and RDS Liscending.
Thanks
Server 1 - Web Access/ Gateway
Server 2 - Broker
Server 3 - Host 1
Server 4 - Host 2
External and internal DNS records set. Firewall rules open Any/Any. Certs with external Web access name in place (the only names are server 1 and its alternate name). Security groups in place for CAP and RAP. Collections made. NO HA
Currently works internally for applicable users but not external.
External ERROR:
Remote Desktop can't find the computer "Broker.company.com". This might mean that "Broker.company.com" does not belong to the specified network.
Any Assistance would be appreciated.
Current Environment:
HA Connection Broker servers and about 30 RDS Servers (all virtual). What we have noticed is that when an RDS Host is having response issue (it's still online and running but in a state where it's barely responsive, but apparently responsive enough that Connection broker doesn't see it as offline). Obviously when this happens users trying to log in that have a session on that host the connection broker tries to redirect them to. The normal timeout function never kicks in because the RDS Server is still responding. We have to figure out which RDS Server is not responding and reboot it to resolve the issue.
I have seen the registry keys related to HKLM\SYSTEM\CurrentControlSet\Services\Tssdis\Parameters timeserversilentbeforeping , pingmode, etc.
My questions are:
1 - what is the actual "ping" from the connection broker to the RDS Server, is it an actual ICMP Ping or an application ping of the terminal server service?
2 - any suggestions on how to automatically resolve this issue short of having to find the offending RDS Server and manually rebooting it?
-SMB
Hello readers,
We have a server 2012R2 environment with 2 RDS servers and a Connection Broker.
When I try to export the Startdesktop (Export-StartLayout -Path "C:\Beheer\start_new.xml") -Path ", i get instead of a xml file an output in non readable format like:
LMXL@ H ÷^*xœÍ—oOAÆç£ßòç@H¬ \cªÅh«}ÁÚ"RÀj5ýîýÍs'FÛØÚX —Û›™ÝyfgwvnÛFÖ³+Û©}¶Ä¦–³oúÎìÜ.῱
+ñæìÈv¥þ†íØ6zçh^#3Ç´ËŽlNoJ›jA_ba¢Þœ1#4sÖ€3YÌxg8u‹j¼¦V€jÒ,”Äy5¸5Qmž2½ªô*ÐmÚ‚ý°.㻕•Ûع²{•ÇúؾÈ÷ð6C=³¯è8îÄŠšç&ûºf ×W(±æ›1—qÙæ¼j gÈ\MÛc Ub÷ªLÏ©¼-yÕ„n`¯È¨¼Z¯{•Îí{òfŒ½´À;‡šg‘[ŽwûðOÝï½<²{cÚ9^Ü0b„|š¿Çf¨=7ÒYÒˆ½=ÕNHV¸6'ŠÑ€þ5Üt%fìÅ9œÉ/¸®¡Ð¾G^†ióÉ™û»ø;ľCñáßµ÷´;dLžØ~âÍ
ÙêVõ1ÆŽ}´¶Ç·cïÖ£cŠh÷ÖßýPB½g5×å>7Mƒuô•<âYÊ;2t¤›+D»Í<žË Ù]ÒÆÊïžÉC$=—–Ð- õ[´åwÏ
}ì8zßW®Ï‹jÝÐ-æé>â=Œ8„SÆBþÍ«ç»Ë-]ž6õBg¢û Æ.½>6&šc@?ÎÆϾu@3²ïò¯¯¬™®ÈêvaCµÄ¥½ÕœÉâ6 »CÚĪßùuµûHZPvßêé-ïÕJ ß+˜²v…˫쓪öÃr<|>2sÅb¾†‘yí“w¦
*§úe¨jåBÞ¤5ptiM;Î*¬®bÛÔ¨2Ÿc-ÏBÜ<yÉ«êÏÿ9ÏÅ5Q\ÏU`F¯Š{ªÍÓ\qªsëÕÚqVÇ;ÿ8»åï³éºž³6c–¶bšF¿ªÓåõu¨ëv(KZ×éóÜwGË1ÚË:g/÷ÐsD‹·
æ8û7(gžOJòµÿ…’(÷¯˜ý9„ðªø±‡Ep–@ãWSÞT²ÿ¥@hZò+B¡(ÞE÷·®*Ò¯íáÓ;nsñ§›öžþ1ï˜ÙOüáe
When I ran the cmd, there was no error message.
A few years ago, the StartLayout was exported succesfully.
What I have tried so far:
- tried the export on different servers (RDS and non-RDS)
- tried the export with a different (domain) admin account
- tried the export with optie "-as bin"
I found only one other reference to this issue online, but unfortunately no solution: https://social.technet.microsoft.com/Forums/en-US/71e76f2a-2b40-466a-8046-fa191babfb9a/how-to-hide-additions-applications-from-windows-81-using-group-policy-server-win2k8-r2?forum=w8itprogeneral
Anyone an idea how to fix this?
Configuring RDS on a workgroup server creates the following additional restrictions:
You must use per-device licensing instead of per-user licensing
https://support.microsoft.com/en-ca/help/2833839/guidelines-for-installing-the-remote-desktop-session-host-role-service
You have to use Per Device licensing for RDS in a Workgroup environment.
For Windows Server 2016 client access license (non-rds license), is Per User licensing allowed in a Workgroup environment?
Hi.
We are rolling out RDS 2019 in our environment. We've got a lot of complaints about the DPI settings not being able to set in the session anymore like in 2008R2, but it has to be done on the local client, which is really cumbersome. However, when done so, we still have some applications with issues.
Now, for most of them I can fix it by setting the compatibility settings:
On a Server 2019 test machine, when set to Application, the application actually shows up fine. On RDS2019 though, it doesn't. I've been working on this for a while, until I installed a machine from scratch, do one step of our installation script at a time, and see where it started failing. It turn out as soon as we enable the RDS role, the DPI settings don't have any effect anymore, and the app is all blurry.
When I remove the RDS role, they start working again. Would anyone know how to fix this?
Hi All,
I am trying to check if we can change the default expiration days (60 days) for the RDS licenses issued. Right now we use "Windows Server 2016 -RDS Per User CAL" and we could see some old users who are not exclusively using the RDS application. I want to check if there is way to reduce the expiration days to 7 or 10 days so that we can avoid the license shortage. I also want to check if there is way to get monitoring if the license usage reached 90% or more.
Thanks in advance!