Quantcast
Channel: Forum Remote Desktop Services (Terminal Services)
Viewing all 27650 articles
Browse latest View live
↧

We can't sign in to your account

May 27, 2019, 7:43 am
$
0
0

Hi!

I build a RDS deployment based on server 2016. After I finished building my session host and users tested it successfully, I cloned and sysprept the server in VMware vCenter.

Everything works fine and user can login and work on the servers without any problems.

When me and my colleague admins login to the cloned servers with our admin accounts, we always get a message like below;

User profile disks are configured in the environment. Folder redirection is enabled to redirect profile folders to H:\. This is inherited from the original RDS 2008 setup that we are migrating from.

I already tried to delete the entry from the profilelist key in the registry. But this didn't solve anything.

How can I fix this?

↧
Search

RDS 2019 deployment - unable to add second RD Broker -

June 17, 2019, 5:29 am
$
0
0

We are running a seperate RDS deployment for our 2019 servers. We had 2 brokers, gateways and RDWeb, with the three roles on one machine each. On our SQL cluster we have a database, where the nodes connect to. One of the brokers started acting up after some Windows updates, and finally it refused to work anymore. Do I just removed it from the deployment, updated our load balancers and currently we are running on one broker/gateway/rdweb just fine. But I want to add a second node again.

When I do so I get the following error:

The list of joined nodes could not be retrieved on <the machine I try to add as second broker>. Privilege not held.



So far I've tried:

- With the broker-dns entry with and without the second node in;

- after removing the old node (new one has the same name) I verified in the SQL database, the old server is NOT in there anymore;

- Firewalls all wide open while adding the node; even if no blocks were logged at al;

- Added the computer account of the new node to SQL and allowed it access to the DB, even we use username/pass as seems to be required in a HA setup.

The SQL connection string is fine by the way, for one the remaining node works fine and until recently it worked fine for the seconde node as well.

How to fix this? Any clue?

↧
↧

RDS Connection Shadowing

June 12, 2019, 1:30 pm
$
0
0

Hi,

I have a Server 2016 RDS deployment with two servers.  One server is the connection broker, gateway and a session host.  The other server is just a session host.  I have found that I am unable to shadow a connection on one of the session host servers.  The server that contains the broker, gateway and session host, is able to shadow connections just fine.  If I try to do the same (I am doing this from the server manager GUI) on the other session host, it does not work.  If I view the list of connections, every connection shows an ID of zero, instead of the actual session ID.  Viewing the list of connections on the other server does properly display the ID of each connection.  So if I right click a connection and choose to shadow it, it displays an error "The specified session is not connected."  I am sure this is related to the fact that the session ID is not being displayed properly.  Can someone offer some assistance in getting this resolved?

↧

Cannot install the Hotfix KB3047296 on Server 2012 R2 while prerequisite updates are installed

May 9, 2016, 12:35 pm
$
0
0
Hi 

I am trying to install the kb3047296 on Server 2012 R2 RDS server, but it shows me The Update is not applicable to your computer error.

I checked the  prerequisite and can confirm the kb2919355 shows installed on the server.

Any idea how to resolve this?

Here is the Hotfix I need to install: KB3047296 



↧

CVE-2019-0708 patch - Gateway and Connection Broker compatibility?

June 17, 2019, 9:27 am
$
0
0

Does anyone know if the patched can be rolled out? Ex: Patching only a few of the session hosts (not all), or the gateway and/or connection broker, etc?

We are not in an environment that we can patch all of the servers at once.

I ask because in our last experience with updating asynchronously, we had an issue where some users were not able to RDP into servers (CredSSP errors, etc).  We don't want a repeat of this.

↧
↧

RDP hangs on Welcome with Windows 7 64 bit

June 3, 2011, 3:10 pm
$
0
0

Does anyone know what is going on with RDPing to a Windows 2008 R2 Ent server?  I have about 20 of them and majority of the time anymore, I cannot RDP to them.  The screen stays on the Welcome screen or the Applying users' settings screen.  I cannot use Terminal Services to connect to the box if it is having the RDP issue.

My servers are always a few weeks behing on updates and they are 64 bit.  As is mt workstation, 64 bit and currently up to date with patches, updates, etc.  Good thing I have the DRAC access, but rebooting a server everytime I want to RDP to it is NOT a solution for the issue.  Anyone?

Thanks!
Randy

 

↧

RDS User CALs invalid product key

June 17, 2019, 10:51 am
$
0
0
We have Azure based windows 2016 servers and purchased 5 Windows Server Remote Desktop Services User CALs. When we try to install we get the error "Invalid Product Key". I've come to find out the CALs are 2019. Are they incompatible with our environment? Or do we need to purchase Software Assurance for the CALs to work with our environment? We are trying to figure out why we cannot install the CALs using the purchased Product Key.
↧

Hyper-V Host Server treating direct logins as "Remote" Logins after RDS Role installed.

May 29, 2019, 2:03 pm
$
0
0

Hello All.

I'm busy with an installation for a clien using "Server 2019" as the Hyper-V Host Server.

On the host I am running two (2) Hyper-V OSEs, also Server 2019 Standard. One acts as the AD Domain Controller, the other is acting as an APP Server for their Financial software on which they need remote access. Everything runs fine through the entire configuration right up to the point after I added the Remote Desktop Services Role. From there on the whole thing goes bonkers. 

When I log back in after a restart, the profiles under C:\Users are all messed up. "domain\Administrator" is gone and there are folders like "Administrator.000", a file that looks like a VHD, I'm guessing this is a Remote Desktop User Profile.

Sometimes it would all of a sudden block my login attempts saying: "To sign in remotely, you need the right to sign in through Remote Desktop Services. By default.... blah blah bla." So I am physically logging into that server "on" Hyper-V, but it is treating the login as a "Remote" login.

I thought it might be a bug in Server 2019, so I installed 2016, and it is doing exactly the same. I am doing the RDS configuration to the letter as per Microsoft, I am just not using the RD Gateway. 

Could someone "pleaaaase" tell me why this is happening? I have to deliver the server to site in two days.

Kind Regards and thank you in advance.

Hentie

↧
Search

RemoteApp Focus Stealing Issue

December 8, 2016, 3:13 am
$
0
0

We have setup a single RDS 2012 R2 running a few published apps via RD web

Because these apps are for remote users only, we have a seperate RDS gateway server (2012 R2) setup as well for that purpose.

All remote users are on Win10.

At random times during the day (really no pattern to it) the remote apps the user has open will start stealing focus.

For example they might be typing a new email in their outlook (which is installed locally on the PC), while the remote app program is sitting in the background open, and it will steal focus and come to the foreground.

Here is what I've checked so far:

  • I cannot see any disconnections of the client on the event logs of the RD gateway or the RDS server.
  • I have tried the following fix without any changes:
  • HKEY_CURRENT_USER\Software\Microsoft\Terminal Server Client]
    "RDGClientTransport"=dword:00000001 
  • This KB doesn't really apply to this problem: https://support.microsoft.com/en-us/kb/2964832
  • This KB can't run on Windows 10: https://support.microsoft.com/en-us/kb/2862019
  • The users have written down the exact times when this focus issue happens and I can't see any event logs on the PC or the servers that would explain this.
  • With a full desktop RDS this problem doesn't happen
  • Organising some downtime so I can install November Roll Up updates (last update was done in 02/11/2016)

I'm a bit at loss here, has anyone seen this one before?

↧
↧

Remote Desktop License Manager Service not Starting

January 7, 2012, 4:31 am
$
0
0

Running on Windows Server 2008 R2, DC, AD and DHCP ,DNS server. The service for  the Remote Desktop License Mmanager wont start, log below show's what's causing it. I've tried a number fix's,( KB318116 and three others) still can't get the service to start anyone got any idea's ?

 Source:       Microsoft-Windows-TerminalServices-Licensing

 Date:         05/01/2012 21:54:47

 Event ID:     44

 Task Category: None

 Level:        Error

 Keywords:     Classic

 User:         N/A

Computer:     UTFLSERV01.UTF.Local

 Description:

 The following general database error has occurred: "Can't initialize

 ESE instance - error -1032 JET_errFileAccessDenied, Cannot access

 file, the file is locked or in use.

↧

Remote desktop deployment does not exist in the server pool (FIX)

June 17, 2019, 5:09 pm
$
0
0

I have seen many threads in regards to this issue but no legit or inexpensive fixes.  Sorry Microsoft, not paying $500 for a support call of a product that is buggy.  

I've read some solutions saying to install the roles via Server Manager and choose RDS then choose quick setup, etc.  The problem is, the people who have this issue already did that.  I tried doing that multiple times with reboots but no luck.  It looks like a bug in the Server Manager where it doesn't do a complete install and no connection is made to the database.  If you run theGet-RDServer cmdlet, no server information gets returned.  

FIX:  Run the Powershell command to install the roles (yes I know that was already done in Server Manager) 

First, Run Powershell as administrator

Second, import the remote desktop module > import-module remotedesktop

Third, install the roles > 

New-SessionDeployment -ConnectionBroker FQDN Server -WebAccessServerFQDN Server -SessionHost
FQDN server

Where it says "FQDN server", fill that value in with the fully qualified domain name of your server.  That fixed my issue and the deployment is now showing in Server Manager.  

↧

A remote desktop service deployment does not exist in the server pool

April 22, 2017, 5:36 am
$
0
0

Hi,

I m running the Windows Server 2016 std edition (latest windows update). I've installed following RDS services below:

1. Remote desktop connection broker(installed)

2. Remote desktop licensing (installed)

3. Remote desktop session host(installed)

Then I go to server manager--> remote desktop services, I can only see two options on the left panel. "Overview" and " Server". If I click overview, and following error message appear on the right panel:

"A remote desktop service deployment does not exist in the server pool. To create a deployment, run the Add roles and features wizard and select the remote services installation option"

I was confused about this message because as I installed three remote desktop services above successfully.

Later I realized that when I ran the add roles and features wizard to install remote desktop services, the two options didn't exist on the left panel of the wizard window.

-Deployment type

-Deployment Scenario 

Questions why are these two options missing. I suppose this has something to do with the error message above. I have run services.msc and found that all remote desktop services show running status.

↧

VPN and Teamviewer

June 11, 2019, 5:31 pm
$
0
0

Hello,

I've been asked to replace teamviewer by the remote desktop services and set up the VPN. I've tried severals tutorials but they all seems different.

Do I need a licence for Remote desktop? How much is it?

Also, do you know any good tutoriak to replace the teamviewer vpn by the windows one.

Many Thanks,

Izak

↧
↧

New Windows Server 2019 RDWeb Webclient connection issue

June 11, 2019, 12:24 pm
$
0
0

We're currently having issues setting up our Terminal Server for our remote users.
Everything is on place: RD Web Access, RD Gateway, RD Connection Broker (Some confusion) and RD Session Host.

We are able to connect to the interface locally and remotely to servername/rdweb/webclient/index.html, we can use the Remote Apps locally but when we try to use the Remote Apps from a remote computer it gives us this error:

Oops, we couldn't connect to "Remote Desktop Connection"
The connection to the remote PC was lost. This might be because of a network problem. If this keeps happening, ask your admin or tech support for help.

Does anyone have any idea what were doing wrong? It would be really helpful.

↧

Applying a custom theme to Windows Server 2012R2 RDP Sessions

June 11, 2019, 12:10 am
$
0
0

I have a Windows Server 2012R2 Terminal Services server with over 100 users logging on (not all at the same time).
There is a GPO that sets the theme to a custom theme file (that must be used), which is stored in a directory that all users have access to.

If I log into that server as a user via the VMware console, the theme applies.
I can then log on via RDP and theme is still there.

However, if that user has never logged on before and I log in via RDP, without first logging on via the console, the theme will NOT load.  Multiple logon attempts do not help.  I can log on via the console and any point and the theme will apply, but this is not practical for 100+ users.

The GPO obviously works, otherwise I wouldn't get the theme when logging on via the console.

Why would a theme work fine if logged on locally (or via console), but not via RDP?


↧
Search

Black/pixelated screen when H.264 hardware encoding is used

June 9, 2019, 5:05 pm
$
0
0

I have a PC set up in the other room in my house (local LAN use only) that I use for surveillance camera recording. I have a persistent RDP connection from it to my main PC a few rooms over. The RDP host has an i9900k and an RTX 2060 graphics card. My client PC that I use to view it has an i4790k with a GTX 1060 graphics card. Both 32GB RAM. Less than 10% CPU usage on both. They are completely hard wired, gigabit end to end, and the host RD PC is only sending out about 20mbps constantly. It is being displayed on a 4k monitor at 60hz on the client PC.

I wanted to take advantage of the hardware encoding capabilities of my graphics card and offload that processing to the RTX 2060. When I go into Group Policy Editor and enable "Prioritize H.264/AVC 444..." and "Configure H.264/AVC 444...", the "Video Encode" on the GPU area of the task manager shows good activity, but the screen will flip out on me and cause these seizure-triggering black pixelated artifacts that take up the entire screen.

Some other info:

1) I have already read about and tried turning off bitmap caching, and deleting the cache in AppData. I tried this and it didn't work.

2)If I move the display from my 4k monitor to my 1920x1080 monitor and resize, then move it back to the 4k monitor and resize, it'll go away for a random amount of time before doing it again. Sometimes 2 days, sometimes 20 seconds. I have also tried resizing my 4k monitor to 1920x1080 and it makes no difference.

3) I swapped out the RTX 2060 with another video card I had on hand, and it does the same thing.

4) Both video cards support the encode/decode requirements. I checked the nvida matrix to verify this. I also checked the event manager and saw Event 162 and 170, verifying compatibility.

5) TCP and UDP are enabled.

6) It does this regardless of what is being viewed. I restarted the host RD PC and only opened a web browser with a news article. While scrolling, the text would be blacked out.

7) Sometimes, instead of being black, it will be pink, or will display images of previously viewed screens.

8) If I turn off the two H264 options in Group Policy Editor, everything works fine.

9) If I select one or the other of the H.264 options, it works fine (but no Video Encode activity on the GPU), but if I enable both of them, the issues arise.

Any ideas would be greatly appreciated.


↧

NetSh AdvFirewall Reset crash the server

June 14, 2019, 7:59 am
$
0
0

Hi 

I am connecting to windows server 2012 via remote desktop and I ran  NetSh AdvFirewall Reset on Powershell

this diconnect me from the server and I couldnt reconnect or even access the websites hosted in the server via web

How can this can be fixed?

↧
↧

Switching users on RDS

June 17, 2019, 6:55 pm
$
0
0
I've got some RDS servers and when a user locks the terminal the switch user button is not there. However if you login to the rds server via the hyper-v console it shows up. Maybe something to do with the Dell Wyse Terminals we are using? We are using the Wyse 3040 terminals.

I've added the GPO

Computer Configuration\Administrative Templates\System\Logon - Hide entry points for Fast User Switching and set it to disabled.

Still not luck, any ideas?

thank you

↧

RDS - Licensing issue

June 4, 2019, 3:03 am
$
0
0

I have a setup RDP setup that refuses to hand out cals. to be fair i didn't set this up and my other infrastructure deployment do not seem to have this issue.

Cals are not handed out and also in the RDS console its is displaying the error message 

The system can not determine if the Licensing server is a member of the TSLS group in Active Directory Domain Services ADDS as ADDS cannot be contacted.

I have followed an article thats confirm via ADSI edit that the permissions are correct and also confirmed permissions and group membership via the use of process explorer. Also i cvan confirm that the server is a member of the domain built in grp TSLS......

i have tested name resolution and also Firewall settings even comparing this to a working set of infrastructure  and it all seem to match. anyone have any ideas as i am not finding a deal on the web other than link that seem to remain un resolved.

↧

Black screen when connecting to Windows Server 2019 on 1 machine only...able to connect from another computer without issue

June 5, 2019, 8:11 pm
$
0
0

I'm having a hard time figuring out what's going on here. I have a desktop machine running Windows 10 (which was working fine before updating to 1903 (which for some reason made me do a fresh install)) I have another machine running Windows Server 2019 which I used to be able to use remote desktop to connect to and for some reason when I go to connect I get a black screen, it looks like it's trying to connect then it's just a black screen. I have another desktop that I'm able to connect via RDP without issue from this same machine which is weird that I'm just not able to see anything when connecting to the Windows Server machine. 

Strangely enough... I AM able to connect via remote desktop to the Windows Server machine from my Surface Pro (which I also updated to 1903)

Any suggestions anyone? 


↧
Viewing all 27650 articles
Browse latest View live
Search
<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>