Hello:

I recently Bitlocker encrypted the system drive of a remote computer and afterwards lost a few of the power button options I would expect to see during a remote session of a Windows 10 1903 computer.

Here are pictures of the options seen before the encryption (during a remote session):

And here are pictures of the options after the system drive was encrypted on the remote computer:

As you can see I have lost the options of sleep, shutdown, and restart after Bitlocker encryption.  Very strange.  If I turn off bitlocker on the remote machine the options are restored, back to normal.  Is this by design or a bug?  I can reproduce problem on two differenct computers.  Not a big deal as I know I have other options to sleep, shutdown or restart, but I would like to know what is going on here.

Thanks in advance,

ssorgem

I used to be able to access Windows 7 computer from windows SBS 2008. For some reasons I can't. If I try to access it using RDC, I will get this message: "Your computer could not connect to another console session on the remote computer because you already have a console session in progress". I can telnet port 3389. What could be the problem?

http://www.ChicagoTech.net

http://www.howtonetworking.com

Hi All,

I am trying to configure multifactor authentication with Azure MFA on my remote desktop gateway. I followed this article:

https://docs.microsoft.com/en-us/azure/active-directory/authentication/howto-mfa-nps-extension-rdg

All seems ok but it is not working as expected. When I try to access a remote desktop I get the notification on my phone. When I approve, the remote desktop keeps trying to connect and I get the notification on my phone 2 more times. Eventually the RDP just times out.

On my NPS server with the NPS extension I can see in the eventlog that access has been granted. On my remote desktop gateway in the NPS logs I can see this:

The RADIUS Proxy received a response from server X.X.X.X with an invalid authenticator.

Where X.X.X.X is my NPS server.

All servers are windows server 2019. My testuser has an Azure AD Premium P1 license (and an office365 business premium).

Any ideas on what could be wrong with my setup?

I've been searching and searching but I'm not getting all the pieces together.  Here is what I need to accomplish:

1. A VM running a modern Windows OS to run a specific application suite.
2. That VM needs to be able to handle up to 5 concurrent Remote Desktop connection actively using the application mentioned above. (The application suite is designed to be able to handle this.)
3. Users will be connecting with tablets, laptops and desktops from the local network and from external connections as well.

The application suite runs a database and is normally installed on multiple desktops with one of them being the "master" running the DB.  Maintaining the multiple desktops is less practical compared to one VM that everyone connects to.  I've seen "hack" ways to run multiple remote connections to Windows 10 and such but I'm looking to do this right.  This application suite is going to be used for the foreseeable future and I don't want to hack it together waiting for an update to break the hack.

What I am asking for is help with what I need for this use case.  I'm ok with building multiple servers (in ESXi/VMware) if needed, though I would prefer only one.  I also would really rather use a per user license since the users are regularly changing out the devices they are connecting with.  

I have downloaded and build basic VMs with the eval versions of Server 2019 Essentials and Standard.

I am running a Server 2016 with RDS and it's mainly used for remote apps. Our users are getting the "The task you are trying to do can't be completed because RDS is currently busy" and looking at the task manager, there appears to be a stuck login which I cannot disconnect. When I attempt to end all processes for that stuck user, it still does not go away and I need to reboot the VM which kicks everyone off.

I am running the latest patches but I find that I have to restart the VM at least 3-4 times a week to allow our users to use their remote app when they work from home.

What could be causing this issue?

Hi there, we are experiencing an issue where we connect to one of our realtime machines and randomly (this happened about a week apart from one another) after you have authenticated, it just goes black and stays that way. I have to reboot the server to get the remote desktop services working again. 

I have noticed by logging into the console session on vmware, that after authenticating on the remote desktop client, it doesn't actually connect because my session using the same credentials on the vmware console is still active and untouched. 

Here are some errors I see : 

An error occurred when transitioning from CsrConnected in response to EvCsrInitialized. (ErrorCode 0x80070102)
&
An error occurred when transitioning from CsrConnected in response to EvCsrInitialized. (ErrorCode 0x80070057)

These logs are also accompanied by Event ID 4005 "The windows logon process has unexpectedly terminated"

I also noticed when I enter the IP for the VM in the remote desktop client and hit enter, the logon screen comes up immediately instead of the couple of ms you normally wait. 

Any idea on how to fix this permanently? 

dears,

I need your assistance with the below, i was deploying rds server. 

Configured rds hosts and rds brokers and rds licenses servers. I issued from the license server licenses per cal and per devices.

In the collection, i added a group that contains the users who are able to connect to the host.

After testing, more than one user were able to connect to the rds host therefore the testing was successful.

however when i went to test the per device cal, i did the following i added the server from where i want to access the rds host to the collection group created earlier. then i logged in to this device using anonymous user and tried to rdp the rds host from that server, however it returned an error : the connection was denied because the user account is not authorized for remote login which is true, the anonymous user is not added to any rds group but the server from where he tries to access the host is added to the group.

I need to understand the per device scenario, can anyone help me with how it its tested?

best regards

Hi all,

I found some interesting errors in the event log. They occur every time a user logs off.

The rds is a server 2016 with user profile disks enabled. The UPDs are set to take all data (no folder selection or filtering).

1) [Warning] User Profile Service 1534

Profile notification of event Delete for component {709E2729-F883-441e-A877-ED3CEFC975E6} failed, error code is The system cannot find the specified file.

2) [Error] Esent 482

svchost (2544) TILEREPOSITORYS-1-5-21-xxx-xxx-xxx-2281: An attempt to write to the file "C:\Users\xxx\AppData\Local\TileDataLayer\Database\EDB.log" at offset 950272 (0x00000000000e8000) for 4096 (0x00001000) bytes failed after 0.000 seconds with system error 21 (0x00000015): "The device is not ready. ".  The write operation will fail with error -1022 (0xfffffc02).  If this error persists then the file may be damaged and may need to be restored from a previous backup.

[Error] Esent 416

svchost (2544) TILEREPOSITORYS-1-5-21-1454471165-1303643608-839522115-2281: Unable to write to section 2 while flushing logfile C:\Users\xxx\AppData\Local\TileDataLayer\Database\EDB.log. Error -1022 (0xfffffc02).

[Error] Esent 492

svchost (2544) TILEREPOSITORYS-1-5-21-1454471165-1303643608-839522115-2281: The logfile sequence in "C:\Users\xxx\AppData\Local\TileDataLayer\Database\" has been halted due to a fatal error.  No further updates are possible for the databases that use this logfile sequence.  Please correct the problem and restart or restore from backup.

[Error] Esent 482

svchost (2544) TILEREPOSITORYS-1-5-21-1454471165-1303643608-839522115-2281: An attempt to write to the file "C:\Users\xxx\AppData\Local\TileDataLayer\Database\vedatamodel.jfm" at offset 0 (0x0000000000000000) for 8192 (0x00002000) bytes failed after 0.000 seconds with system error 21 (0x00000015): "The device is not ready. ".  The write operation will fail with error -1022 (0xfffffc02).  If this error persists then the file may be damaged and may need to be restored from a previous backup.

[Error] Esent 104

svchost (2544) TILEREPOSITORYS-1-5-21-1454471165-1303643608-839522115-2281: The database engine stopped the instance (7) with error (-510).
 
Internal Timing Sequence: [1] 0.000, [2] 0.000, [3] 0.000, [4] 0.000, [5] 0.000, [6] 0.000, [7] 0.000, [8] 0.000, [9] 0.000, [10] 0.000, [11] 0.000, [12] 0.000, [13] 0.000, [14] 0.000, [15] 0.000.

Any ideas what the reason for these could be?

Thank you!

We are seeing the following error during start up on more than one of our VMs running Windows Server 2016 Datacenter, this is prevent users from being able to RDP to the server. It seems this error resolves itself as the WID service does eventually start, but the dependent RDS services do not start thereafter, but will start with manual intervention. The following are the errors listed in the event log:

1. A timeout was reached (30000 milliseconds) while waiting for the MSSQL$MICROSOFT##WID service to connect.

2. The MSSQL$MICROSOFT##WID service failed to start due to the following error: 
The service did not respond to the start or control request in a timely fashion.

3. The Tssdis service depends on the MSSQL$MICROSOFT##WID service which failed to start because of the following error: 
The service did not respond to the start or control request in a timely fashion.

There is also the below message logged before the first error, but I'm not sure this is the actual cause, as said previously, it does eventually start, which makes me think its a timing issue.

Additionally, this does not happen each time the server starts and is seemingly random, but we are seeing similar behavior on another server with RDS installed.

I've found the following post, but this is not a fix and merely extends the timeout value for all services.

https://support.microsoft.com/en-us/help/922918/a-service-does-not-start-and-events-7000-and-7011-are-logged-in-window

Thanks

Configuration:

Hyper-V - Server 2016 Desktop Virtualization Host with all available updates as of 09/12/2019
     -nVidia Tesla M10 with newest Graphics Drivers available - fully support 1903
     -Registry setting for AVC444ModePreferred = 1
     -Registry setting for AVCHardwareEncodePreferred = 2

VDI Desktop - Windows 10 1903 with all available updates installed as of 09/12/2019
     -RemoteFX Adapter added to VM with 2x monitors with 512MB

RDP Client Endpoint - Win10 1803, Win10 1809, Win10 1903 all with all available updates as of 09/12/2019

Scenario 1: RDP from client to the VDI through RDCB or directly: Fails to connect with administrator message

Scenario 2: Connect to VM through Hyper-V Console with RemoteFX enabled - Works flawlessly

Scenario 3: Enable the 'Use WDDM graphics display driver for Remote Desktop Connections' policy - Connection works over RDP but it appears RemoteFX isn't functioning fully as graphics are sluggish. This should not be the fix as the nVidia RemoteFX drivers should be fully WDDM compatible.

Scenario 4: Remove RemoteFX Adapter - Connection works over RDP but is sluggish due to no RemoteFX

This person is having the same problem but the fixes are not working for me and since he did not respond, I'm not sure the fixes are actually working - https://social.technet.microsoft.com/Forums/office/en-US/25fa7511-c21d-44e7-9c5f-b77ffdd4d2ac/remotefx-on-hyperv-console-but-not-through-rdp?forum=winserverTS

Message Received on RDP Client:

Your Remote Desktop Services session has ended, possibly for one of the following reasons:
     The administrator has ended the session.
     An error occurred while the connection was being established.
     A network problem occurred.

Hi all,

I wonder if you could help me. I have deployed a new RDS server and everything seem to be in place. Its based on Windows Server 2016, and all licences applied, and certificate added.

Internally I can access it through the browser fine, but not externally (outside our LAN). Also everytime i try to add the server to Access RemoteApp and desktops, internally or externally, i get the message "Your credentials did not work".

This is a big project that i am working on and i find my self stuck.

So far i have tried:

• GPOs to add TERMSRV/* and thumbprint
• Bypass RD Gateway credentials for local addresses
• SSL Certificate for RD Connection Broker Enable SSO, RD connection broker Publishing, RD Web Access and RD Gateway is the same.
• Checked IIS for redirections and SSL (all off, tried on too)...all i could think of, but no luck.
• Authentication policy is set via GPO as: allow delegating default credentials with NTLM-only server authentication and Allow delegating saved credentials with NTLM-only server authentication. 

I am struggling to find a reason why it's not working.

Any help is much appreciated.

How can you prevent user profile corruption on windows server 2016 and 2019.

We have lots of RDS deployment setup according to best practice guides, it's all very straightforward no strange or complicated configuration. Just an out of the box windows server 2016/2019 installations with RDS:

a remote desktop gateway

a connection broker

a session host

then we make a rdp deployment with UPD's.

profiles keep getting corrupted. How can we prevent this? It's super annoying we have to fix the corrupted profiles all the time.

Note this is not a question how to fix corrupted profiles, rather how to prevent it. We're now fixing corrupted profiles every day, such a waste of time!

If you need more information, let me know.

PS. seeing the many google posts, it's clearly a problem many people have, so there must be a solution for that right????

PS. RDS setup is default as can be. Guide followed: https://docs.microsoft.com/en-us/windows-server/remote/remote-desktop-services/rds-deploy-infrastructure  No weird config going on, everything according to best practice but still profile corruption keeps coming back.

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

hello every one 

i have a issue with RDP redirection

the problem is i can't redirect just usb drives but not the local drives

i think of some script to run when the rdp session is created on the server and map the usb on the user's computers

but i don't know where to start

i also tried redirection policies in group policy but when you Disable drive redirection it's also assume the usb drive as a drive so i can't use the group policy or other things except some script that map detect the PnP devices on user's computers and map it and prohibit the local drives redirection.

thank you in advance

Recently I'm facing a problem with a shared HP printer. All of a sudden, the model (driver) is displayed instead of  not the share name Other printers are OK, for now.

This should be fixed since 2012...:  https://support.microsoft.com/en-us/help/2965350/shared-printer-name-displays-incorrectly-in-windows

A regression of recent patchs ?

I do the IT work for a local small business. A few months ago the owner decided to change from one software vendor to another. The previous was a web based application and the new one is accessed through Remote Desktop/Remote Access to a Windows 2008 R2 server. All of our desktops run the latest up-to-date versions of Windows 10, all are HP computers, all get about 50mbps down and 20mbps up. We went live with the system on the first of the month however since the beginning our client desktops will experience odd session hanging/freezing seemingly randomly. I will bring up another program(Google Chrome, Outlook, etc) for a few minutes and go back and it will be "frozen". Although this is inconsistent as I can do the same thing for longer and it won't hang/freeze. When this happens I'll kill the app in task manager. Then I go through the log in process again and it brings up the session just how it was before it "froze" saying something along the lines of "Are you sure you want to restart the connection" with yes and no options. I'll then hit no to continue the previous session and it is like it never happened. This only takes a minute but this happens 10-20 times a day for each of my users and they are getting frustrated.

The vendor says they are working to find a solution and that our problem is unique, however it has been a few weeks and they haven't really said much outside of normal troubleshooting efforts. I cannot do anything server side, that's on them, but on the client side I've tried just about everything I could think of or find. I've tried turning off/on just about every MSTSC setting there is, I've updated all drivers for everything(was specifically targeting network and graphics), I've disabled auto-tuning on the NIC, I've edited the registry to only only allow TCP connections in TS, I've reset our router, and I've tried other remote desktop apps. When we went live and noticed it happening we immediately did a Ping Monitor on one of our hosts for a week and ruled out network/internet issues. I've also remoted in to the server from a Windows 8 laptop from home and the issue was not present. Event viewer show nothing anywhere, it's like it isn't happening even though it is. 

If anyone has any tips or suggestions, I'm open to anything at this point. If not I'll wait around for the vendor to hopefully figure it out.