Quantcast
Channel: Remote Desktop Services (Terminal Services) forum
Viewing all 5613 articles
Browse latest View live

Windows Search changes in Server 2019 RDS

$
0
0

Hi,

So nothing like being on the cutting edge......

I have been testing Server 2019 RDS and so-far-so-good apart from an issue with the Windows Search Service.

It appears that in Server 2019 each user gets their own search database EDB file in their profile path (appdata\roaming). e.g.

C:\Users\username\AppData\Roaming\Microsoft\Search\Data\Applications\S-1-5-21-3901271148-1553943383-1671037523-1629\S-1-5-21-3901271148-1553943383-1671037523-1629.edb

When they log on and log off; this is connected to the search service and the following event log is generated

Source:ESENT
EventID: 326
SearchIndexer (10896,D,50) S-1-5-21-3901271148-1553943383-1671037523-1629: The database engine attached a database (3, C:\Users\username\AppData\Roaming\Microsoft\Search\Data\Applications\S-1-5-21-3901271148-1553943383-1671037523-1629\S-1-5-21-3901271148-1553943383-1671037523-1629.edb). (Time=0 seconds)

Unfortunately it appears that this process is not very stable and on some logons the database in the users profile does not attach and the following error is generated

Source:Search
EventID: 3057
The plug-in manager <Search.TripoliIndexer> cannot be initialized.
Context: S-1-5-21-3901271148-1553943383-1671037523-1629 Application

Source:Search
EventID: 3028
The gatherer object cannot be initialized.
Context: S-1-5-21-3901271148-1553943383-1671037523-1629 Application, SystemIndex Catalog
Details: The specified object cannot be found. Specify the name of an existing object.  (HRESULT : 0x80040d06) (0x80040d06)

And a few more similar but related errors....

No subsequent logon/off will succeed in attaching the database until the Windows Search service is restarted

I am not testing with User Profile Disks or Roaming Profiles
There is no AV on the server

Any ideas?

Andy



Andrew




Restricting Remote Desktop Gateway access via Client IP Addresses?

$
0
0
I want to restrict remote desktop (through Remote Desktop Gateway) to only specific IP addresses (client's can only connect from certain IPs). How would I accomplish this on the RDG/NPS server (not the firewall)? Everything I've tried doesn't work.

RemoteAPP after windows 10 update 1803 are slow and right mouse button is not responding (it reacts only sometimes)

$
0
0

Hi,

our workstations with Windows 10 pro are in this weekend updated to version 1803. For main system we use RemoteAPP aplications on Windows server 2012R2 (Windows server 2012R2 is full updated). After update on client station are RemoteAPP slower, and  right mouse button is unresponsive, or react verly long time... 

It is a big problem for us.

PS: after replace mstsc.exe and mstscax.dll from older version Windows 10 is all OK. but this is not a solution.

Thanks.


Disable Multiple session in windows server 2016

$
0
0

Hi,

By default all windows machine has 2 session enabled in RDP. Currently i have RDS setup with multiple client VM. here i have to restrict single user to single computer login (Allow only one session for the specific user for specific computer).

Change should be done in AD/RDS server not in client machine. Both AD & RDS are windows 2016.

Awaiting for your valuable input for this problem .

Thank you!

RDP issue on windows server 2016

$
0
0

Hi Team,

Few users are unable to RDP  to the windows server 2016 and also we can't reboot the VM. I can see the user name who have connected to VM in task-manager users tab but one user name is showing 4 instead of user name. So i tried to disconnect the user (4) it doesn't disconnected and then i try to connect the user (4) and then disconnect the other user session then all the users are able to RDP. Please let me know is there are any bugs in Windows Server 2016 Remote desktop service.

Thanks,

Ashadeep

Windows Server 2012 R2 stuck restarting on RDP but normal on vm console

$
0
0

I have windows server 2012 R2 installed on vmware. previously i restarted this server via RDP and stuck on restarting screen. but when i open this server via console vm, there is no problem and all service is ok. but until now in rdp is still stuck restarting and this is very annoying.

anyone can help me?

RDS 2019 internal server name exposed in RD Connection

$
0
0

Hello,

I have the internal RDS Server name (rds.internal.lan) exposed in the RDP-window regardless of I start it from the Web access or Remoteapps and Remote Desktops. The objective is not to eliminate Certificate mismatch warnings.

I have a 2 server setup,

1) dc.internal.lan DC/DNS with 'pinpoint' DNS A record for rds.publicdom.com pointing to the server's private ip

2) rds.internal.lan with all RDS (also RDGW)Roles. 

Only Desktop Collection is published.

All roles configured with trusted certificate for rds.publicdom.com

Role          Level          ExpiresOn                           IssuedTo                                      
----          -----          ---------                           --------                                      
RDRedirector  Trusted        01/08/2021 00:59:59                 CN=rds.publicdom.com                                 
RDPublishing  Trusted        01/08/2021 00:59:59                 CN=rds.publicdom.com                                 
RDWebAccess   Trusted        01/08/2021 00:59:59                 CN=rds.publicdom.com                                 
RDGateway     Trusted        01/08/2021 00:59:59                 CN=rds.publicdom.com 

AND 

Subject              : CN=rds.publicdom.com
SubjectAlternateName : {rds.publicdom.com, www.rds.publicdom.com}
IssuedBy             : CN=Sectigo RSA Domain Validation Secure Server CA, O=Sectigo Limited, L=Salford, S=Greate
                       r Manchester, C=GB
IssuedTo             : CN=rds.publicdom.com
ExpiresOn            : 01/08/2021 00:59:59
Thumbprint           : FDD6C6647131871F2KKK5197A29EE04FDFD90C4C
Role                 : RDGateway
Level                : Trusted

PS C:\> Get-RDDeploymentGatewayConfiguration |fl

GatewayMode          : Custom
GatewayExternalFqdn  : rds.publicdom.com
LogonMethod          : Password
UseCachedCredentials : True
BypassLocal          : True

PS C:\> Get-RDWorkspace

WorkspaceID         WorkspaceName
-----------         -------------
rds.
internal.lan Work Resources

I attempted to change the RDPublishedName with the tool from the below link, that runs fine, but makes the RDP Desktop unavailable.

Set-RDPublishedName.ps1 rds.publicdom.com

 Set-RDPublishedName Succeeded.

Old name:  rds.internal.lan

New name:  rds.publicdom.com

https://gallery.technet.microsoft.com/Change-published-FQDN-for-2a029b80

Is the HA configuration described in the very useful article below an option to configure the internal name correctly? 

https://msfreaks.wordpress.com/2018/10/06/step-by-step-windows-2019-remote-desktop-services-using-the-gui/

Any assistance will be highly appreciated.

Best regards

Tim K

Remote Desktop Services 2019 - domain users work; local users get a warning about disconnect in 60 minutes

$
0
0

We just built a new Windows Server 2019 server running Remote Desktop Services 2019, using the Quick Start install.  It's a single server so everything is on that one server including the Licensing Server.  Domain Users can connect without issues, but local users that connect remotely get an error "Remote Desktop License Issue" "There is a problem with your Remote Desktop license, and your session will be disconnected in 60 minutes".  The local user does indeed get disconnected in 60 minutes and has to reconnect.  What's wrong?

NOTE: I noticed in the Remote Desktop Licensing Diagnoser that the Remote Desktop Host Server version is Windows Server 2016 for some reason. It should be 2019.  


Window 10 Pro with Window 7 Pro.

$
0
0

Hi Everyone,

I have 20 Qty Window10 Pro FPP license.

And installed  Window10 Pro in 10 Pcs and rest 10 PCs installed with Window 7 Pro.

Can I install window 7 Pro in newly purchased computer and can get adjust/entitlement with existing window 10 Pro that purchase previously.

Do we need to buy extra Window 7 Pro for the license entitlement.

Many thanks....


Problem with Windows Server 2019 RDS License

$
0
0

We want to deploy few new rds servers on server 2019 but it seems that the per user licensing is not working correctly if in a workgroup.

Evertime when a user logs in it gets the following message:

'There is a problem with your Remote Desktop license, and your session will be disconnected in 60 minutes, Contact your system administrator to to fix this problem'

In the gpo the license server is specified and the "per user" mode is selected. 

Same issue as :

https://social.technet.microsoft.com/Forums/windowsserver/en-US/e69d9a47-1e2a-4d37-8073-97327ac91154/problem-with-windows-server-2019-rds-license?forum=winserverTS



[VDI] Cannot open session

$
0
0

Hello, I am a student who enjoys Windows Server very much. I would like to set up a VDI infrastructure at home for testing purposes. Here is a summary of my infra:

- Service Broker + Gateway = VM (Windows Server 2016 Datacenter)

- Virtualization host = Dell PowerEdge R620 physical server (Windows Server 2016 Datacenter)

- DC = Dell Precision T3610 physical server (Windows Server 2016 Datacenter)

My current problem is as follows: when I log in to the "Remote Desktop Access via the Web", I see my collection of personal desktops that I have created. But, as soon as I download the.rdp file, I enter my credentials, and I find that the RDP window allowing me to access what I assume is the VM opens for a microsecond, then closes without any error or message.

I also noticed that I sometimes connected to the Service Broker, which is problematic.

Do you have a solution?

Thank you in advance! :)


Parallel RDP connection to terminal server and LSASS.exe crash

$
0
0

Dear all,

I am having serious problems while connecting using VPN to RDP to terminal server using smartcard. While I try to log in from one machine it works flawlessly (even it is quite slow). However, when I try to login concurrently from 2 machines using smartcard, I got an error saying that there is no smartcard present, or there are no authentication certificates. Once I get such error, the terminal server is restarted (WS2012R2, WS2016, WS2019 - tested on all versions). In the event log, there is an error lsass.exe crash with status code -1073740940. As this happens only sometimes, we cannot easily reproduce it, but the chance that the server will crash on Kerberos authentication is much higher when 2 clients are connecting concurrently.

Do you have any ideas where might be a problem?

Jan

remote logon not possible - clear destination host

$
0
0

Hi there,

we have a terminal server farm with 12 hosts and on session broker.
Sometimes I want to lock one host and ask the users to re-logon to get them to a different host.

But it seems that the session broker (or the client) cached the last redirection and shows the user that no remote logons possible at the moment.

How can I clear this cache?
And where can I see to wich host the session broker redirected the client?
(I did not find the right log for that info)

Is there somebody who could help me?

Thanks in advance
Reiner

Cannot find a way to prevent a session for being stolen

$
0
0

Hallo,

my configuration is this one:

   1) Server Win2008R2

   2) RDP services configured and working, let's say, for three accounts

   3) People across the company (and from different locations) know theese accounts and use them to get access to the server via RDP  client

The problem is this one: If one user, "user1", connects with account "A" and works normally and then, if another user, "user2", connects from another location with the same acount "A" THEN the "user2" steals the session to "user1" just taking over the user1' session.

I want to prevent user2 to login with account "A" and taking over the active session of user1

Is there a way ?

thanx for the support





aldo.domini@libero.it

mix 2012 and 2019 rds farm

$
0
0

hi guys, happy new year.

we have bought new server hardware and software and i will migrate our 2012 r2 rds farm on new enviroement (vmware vsphere 6.7). So we have bought 2019 server and rds cal license and now my question, if i keep actual two connection broker server with 2012 R2, can i create a new collection with 2019 rds server host role?

i wolud keep remoteapp collection with 2012 R2 server and rds desktop with 2019

thanks

Andrea


Remote App Troubles on first start Webclient

$
0
0

we have a rds environment all windows server 2019. in this environment we deploy our software with remote apps. our customers connect to the software with html5 webclient via rdweb. now we have several times the problem, that the app won`t apper on the first click. when we press the app button on rdweb, the rd connection establish successful but the app won`t appear. now if we open another app both apps will appear and all works fine.

have anybody an idea?


RDS browse function behavior for different users

$
0
0

Hi,

Need your help to understand browse button functionality under RDS environment for different users.

I have customer who has same RDS profile setup for all users, but when ever browse function used from a particular application to attach documents :

- For some users, it keeps in memory last location used and open that location with last few attachments done.

- For some user it shows blank list and user have to re-direct to original location to make attachment.

On user profile below configuration done :

- Default save location of documents in application.

- Task Bar -> Properties > this will open Taskbar and Navigation properties window -> Jump Lists tab -> check/ uncheck "Store and display recently opened items in Jump Lists". 

Please share your valuable thoughts on above.

Warm regards

Tejinder Dass

Remote desktop licenses not being issued, cannot connect using remote desktop.

$
0
0

We are/have upgraded from a terminal server using Server 2008 R2 to a new server with Server 2019

I have loaded the 15 RDS user licenses and everything was working fine until this morning. I briefly lost the VPN tunnel from the remote office, and after it reconnected, none of the workstations are connecting. earlier connection said it was in grace period.

I have checked the new server and it shows 15 total licenses, 15 availalbe, 0 issued.

The remote stations connected fine yesterday, and were connecting to the old 2008 server last week. Is there something I need to do to get the remote computers to get a license from the new server?


John Mason

Fresh Install of Windows Server 2019, Unable to connect to Session Host Servers

$
0
0

Hi,

I've been facing this issue since Windows Server 2016 and now this problem has happened to me again on Server 2019, I am not sure what the issue is and how I can fix this, if someone can help me on this then it would be great.

Scenario:

DC01 - Active Directory Domain Controller, RD Licensing and File Server on Windows Server 2016
10.10.10.150/24

RDSH01 - RD Connection Broker, RD Session Host, RD Gateway, RD Web Access - Server 2019 (updated)
10.10.10.151/24

RDSH02 - RD Session Host, RD Gateway - Server 2019 (updated)
10.10.10.152/24

Windows Firewall is disabled on all 3 servers. Everything installs fine no errors or warning, certificates are installed as well.

The 3 servers are VM's running on seperate servers, I have done a fresh install of Operating system and not cloned them (as i heard there would be issues with cloning)

When connection with both Session hosts, I as the first user I am connected to RDSH01 without any problems let's call this user1, now when i try connecting as user2, since there is 50-50 load balancing by default, it tries to connect me to RDSH02 and it fails with the below error

 

And the Event logs have the following events

EVENT ID 1280:

Remote Desktop Services failed to join the Connection Broker on server RDSH01.domain.com.
Error: Current async message was dropped by async dispatcher, because there is a new message which will override the current one.

EVENT ID 1306:

Remote Desktop Connection Broker Client failed to redirect the user Domain\user2 . 
Error: NULL

EVENT ID 1296:

Remote Desktop Connection Broker Client failed while getting redirection packet from Connection Broker.
User : Domain\user2
Error: Remote Desktop Connection Broker is not ready for RPC communication.

EVENT ID 2056:

The Remote Desktop Connection Broker server could not enumerate the targets for the provider named NULL from the database.

Pooled virtual desktop collection name: NULL
Error: Logon to the database failed.

I installed SQL Management studio and am able to connect to the Windows Internal Database without any problems, All services related to Remote Desktop are also running.

Ping and DNS lookups are working fine as well each server can ping and reverse lookup the other 2 servers without any issues. The 3 servers are also added in the Server pool in Server Manager.

Can someone help me figure this out please? I am scratching my head over here for over 2 days. I mean this is a fresh install after all, shouldn't be creating such problems.


MCITP:Server Administration|MCTS: Server 2008| MCSE: Server 2003| MCSA + M: Exchange Server 2003| MCP: Windows XP|

RD Gateway manager issue

$
0
0

Hello,

I have just installed RDS on windows server 2019, I am trying to configure RDS gateway manager but not really getting it to work.

When I try to add gateway address (full FQDN address) I am getting error message that RD Gateway manager is unavailable.

I have a SSL certificate that is *.domain.com and my server name is FQDN remote.domain.com

I still get that the rdp connection is untrusted even though I choose the SSL certificate and I am not able to connect to the RD gateway manager externally.

Viewing all 5613 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>