Rebuilding a Windows Remote Desktop Licensing Server
Temporary Profiles ( /admin and NT Service logins)
Client has a three server Remote Desktop Services environment running on Server 2016 (3 Session Hosts, 1 License Server/Connection Broker/Gateway). Server 1 runs all services, Servers 2 & 3 run only Session Host. Also running on Server 1 is a SQL Server 2012 instance. Logins currently disallowed on Server 1; Servers 2 and 3 service user logins currently. User Profile disks are enabled, pointing to a common share mountpoint on Server 2.
Client requested installation of a second SQL Server 2012 instance, Reporting Service Native mode only, to host another reporting services site.
Things I noticed right off hand:
mstsc /admin /v:server1 logs me in with a temporary profile. I figure I'll tackle this problem later, since getting the new RS instance is the "priority". I go through a typical SQL 2012 RS installation, apply service pack 4, and then go through the configuration process. New RS instance use a different host header to direct traffic to, server1alias.mydomain.com, rather than server1. All of this seems to work as expected.
All this appears to work as I expect... until I attempt to connect to http://server1alias.mydomain.com/Reports or http://server1alias.mydomain.com/ReportServer, I am repeatedly prompted to login credentials (yes, I am supplying the correct username and password ;) when I attempt this).
Upon further investigation, it appears the "NT SERVICE\ReportServer$INSTANCENAME" account, when the Reporting Services instance is started, like the Administrator account, "logs in" with a temporary profile. I see a "Temp.NT Service.001" directory under c:\users. Also, if I attempt to restore a encryption key through the RS configuration utility, I receive an error message telling me the profile is "temporary".
If I go into the user profile list (Control Panel -> System and Security -> System -> Advanced -> User Profiles) I can see "NT Service\ReportServer$INSTANCENAME" is listed as a "Local" "Temporary" profile.
I am assuming this has something to do w/ this server also being a Remote Desktop Services Session Host, since I have installed dozens of MSRS instances over the years and have never seen this issue before. This is the first time I've been asked to establish a new MSRS instance on a server which also serves in a RDS capacity.
Short of uninstalling the session host service, does anyone have a suggestion on how I can go about fixing this problem?
New Windows Server 2019 RDWeb Webclient connection issue
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.
Windows Server 2019 with Remote Desktop Services standalone
Hi,
I would like to install an RDS on Windows Server 2019 for 20 users. They will have a full desktop with two or three applications.
I have per-user CALs licenses.
What is the best way to do this, considering I have only one server (cloud based) ?
Many thanks !
RDS with the Azure MFA Plugin..Help! AuthZ Event ID 3
Hi Everyone,
We have a 2016 RDS Platform we'd like to start using with Azure MFA. I've created an extra two NPS servers and installed the powershell plugin for MFA. Everything is configured as per:
https://docs.microsoft.com/en-us/azure/active-directory/authentication/howto-mfa-nps-extension-rdg
When attempting to connect, the gateways simply timeout and do not authenticate. Looking through the NPS logs I'm seeing this:
NPS Extension for Azure MFA: CID: 8bacef42-b3ac-49be-872b-99b3eca79302 :Exception in Authentication Ext for User DOMAIN\username :: ErrorCode:: CID :******** ESTS_TOKEN_ERROR Msg:: Verify the client certificate is property enrolled in Azureagainst your tenant and the server can access URL in Registry STS_URL.Error authenticating to eSTS: ErrorCode:: ESTS_TOKEN_ERROR Msg:: Error in retreiving token details from request handle: -895352831 Enter ERROR_CODE @ https://go.microsoft.com/fwlink/?linkid=846827for detailed TroubleShooting steps. Enter ERROR_CODE @ https://go.microsoft.com/fwlink/?linkid=846827for detailed TroubleShooting steps.
I've ran numerous powershell commands to check the certificates are in azure which they are
for users not yet enabled for MPA I have added this to the registry
REQUIRE_USER_MATCH = FALSE
on the gateway servers I'm seeing an Event ID 6274
The remote RADIUS (Remote Authentication Dial-In User Service) server did not respond.
Those users are also unable to login to RDS....I've had to revert all settings to restore service
any ideas?
Thanks!!
Switching users on RDS
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
Deploying Managed Pool Breaks Adobe Reader 11
I am trying to set up managed pools for VDI in RDS. I have RDS installed and functional on a Windows Server 2012 Datacenter machine, and I have successfully created Windows 7 template machines and deployed pools from them. I have even managed to make changes to the pools with the recreate functions. I have done most of this without finding great documentation. That having been said, I am having an issue that I'm not sure how to deal with thatadequate documentation probably wouldn't help with. I have installed Adobe Reader 11 on a virtual desktop template and created a pool from it. When I connect to that pool and try to launch Adobe Reader, I get an error that says only: "An internal error occurred." Adobe Reader does not launch. I assumed this was a problem with the installation or something sysprep did, so I booted up the template and went through the OOBE. Once booted, I could launch Adobe Reader with no problem. IOW, this issue only exists when I deploy a managed pool, but not on the base image the managed pool was deployed from. Note that I would prefer to keep everything on the VDI image and not mess with RDSH or App-V. Does anyone have any suggestion on how to deal with this?
Issue with Credential Manager in RDS
I have a issue with a server 2019 server that is running sessions host only (1 server environment, only accessible from the inside)
This environment has been migrated from an old SBS 2008, everything has been upgraded.
Exchange moved into O365.
AD moved from 2008>2012r2>2019
Remote desktop has been created with new fileshares and using UPD disks.
So the issue we are running into is that it is refusing to store anything in the Credential manager for all the users, our prime example that we are having issues with is that every time users log on they have to reauthenticate to outlook since its not stored in the credential manager.
Any suggestions what might be causing the issue?
Server 2012 Remote Web Access Port changed to 8443 but RDP Deployment file not working
Server 2012
I changed the Remote Web Access Port to 8443 but RDP Deployment file not working. The only way I can get it to work is by creating a custom one with the :8443 at the end of it. Is there anyway I get it to add that automatically to the download when I click on a computer that I would like to connect to through the Remote Web Access?
See what application users have open on RDS
Hi All,
So we currently have a collection on our 2012 RDS infrastructure where we have 10 applications published to business.
I just want to find out if there is a means in which I can determine which application the users currently have open? The reason for this is we need to do a deployment to one of the published applications back-end application servers and need to ensure no users are connected to that specific application.
At the moment I have a total of 254 connections, yet I cannot determine if they are accessing App-1, App-2, App-3 etc.
Thanks,
Specify a Program to Start Automatically When a User Logs On Does Not Work in 2016 Server
By default, Remote Desktop Services sessions provide access to the full Windows desktop, unless a program has been specified to start when the user logs on to the remote session.If an initial starting program has been specified, it will be the only program that the user can use in the Remote Desktop Services session. The Start menu and the Windows Desktop are not displayed when the user logs on to the remote session, and when the user exits the program the session is automatically logged off. This feature does not work 2016 server it ignores whatever we specify and always starts a Desktop Session. We are running a work group so group policy is not an option as a workaround. In the 2012 server, 2008 Server it works. Kindly please advise how to get this basic feature to run in Server 2016.
Migration Of RDS License from Windows server 2012R2 to 2016
Hi,
I need information.
We have 50 license RDS per user installed on 2012R2 and 12 license are used , remaining 38 needs to be migrated to 2016 CAL's ....is it possible ?? if possible how we can proceed.
Please provide information with steps.
RemoteApp logon takes 60 sec more than standard Remote Desktop logon
Hi everybody,
I have stand-alone Windows Server 2012 configured as DC (for further scalability) with appropriate domain and valid SSL Certificate. The machine is VIRTUAL.
Therefore, it's the same machine for every role (RD Gateway, RD Licensing etc).
Logging on as remote desktop user takes a few seconds and is quite OK.
Logging on of the same user(s) as a remote app always adds 60 secs of extra time.
I talk about the time after password prompt pops up, which happens almost immediately.
The following minute after confirming the password the logon dialog presents the message
"configuring remote desktop".
Those 60 seconds are well documented in the Event Log and the sequence is always the same.
It looks like two consecutive time-outs of 30 seconds each.
Below is an example of events sequence:
Event 1: Log Name: Microsoft-Windows-TerminalServices-Gateway/Operational Source: Microsoft-Windows-TerminalServices-Gateway Date: 02/06/2019 09:53:51 Event ID: 312 Task Category: (3) Level: Information Keywords: User: NETWORK SERVICE Computer: computer_name.domain.example.com Description: The user "user@domain", on client computer "xx.xxx.xx.xxx:58554", has initiated an outbound connection. This connection may not be authenticated yet. Event Xml:<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"><System><Provider Name="Microsoft-Windows-TerminalServices-Gateway" Guid="{4D5AE6A1-C7C8-4E6D-B840-4D8080B42E1B}" /><EventID>312</EventID><Version>0</Version><Level>0</Level><Task>3</Task><Opcode>30</Opcode><Keywords>0x4000000000000000</Keywords><TimeCreated SystemTime="2019-06-02T06:53:51.283267000Z" /><EventRecordID>31003</EventRecordID><Correlation ActivityID="{F9A66720-F292-459D-9E6D-40D1A86A0000}" /><Execution ProcessID="4696" ThreadID="15348" /><Channel>Microsoft-Windows-TerminalServices-Gateway/Operational</Channel><Computer>computer_name.domain.example.com</Computer><Security UserID="S-1-5-20" /></System><UserData><EventInfo xmlns="aag"><Username>user@domain</Username><IpAddress>xx.xxx.xx.xxx:58554</IpAddress></EventInfo></UserData></Event> Event 2: Log Name: Microsoft-Windows-TerminalServices-Gateway/Operational Source: Microsoft-Windows-TerminalServices-Gateway Date: 02/06/2019 09:53:51 Event ID: 313 Task Category: (3) Level: Information Keywords: User: NETWORK SERVICE Computer: computer_name.domain.example.com Description: The user "user@domain", on client computer "xx.xxx.xx.xxx:58558", has initiated an inbound connection. This connection may not be authenticated yet. Event Xml:<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"><System><Provider Name="Microsoft-Windows-TerminalServices-Gateway" Guid="{4D5AE6A1-C7C8-4E6D-B840-4D8080B42E1B}" /><EventID>313</EventID><Version>0</Version><Level>0</Level><Task>3</Task><Opcode>30</Opcode><Keywords>0x4000000000000000</Keywords><TimeCreated SystemTime="2019-06-02T06:53:51.971015500Z" /><EventRecordID>31004</EventRecordID><Correlation ActivityID="{F9A66720-F292-459D-9E6D-40D1A86A0000}" /><Execution ProcessID="4696" ThreadID="3132" /><Channel>Microsoft-Windows-TerminalServices-Gateway/Operational</Channel><Computer>computer_name.domain.example.com</Computer><Security UserID="S-1-5-20" /></System><UserData><EventInfo xmlns="aag"><Username>user@domain</Username><IpAddress>xx.xxx.xx.xxx:58558</IpAddress></EventInfo></UserData></Event> Event 3: Log Name: Microsoft-Windows-TerminalServices-Gateway/Operational Source: Microsoft-Windows-TerminalServices-Gateway Date: 02/06/2019 09:53:52 Event ID: 313 Task Category: (3) Level: Information Keywords: User: NETWORK SERVICE Computer: computer_name.domain.example.com Description: The user "user@domain", on client computer "xx.xxx.xx.xxx:58558", has initiated an inbound connection. This connection may not be authenticated yet. Event Xml:<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"><System><Provider Name="Microsoft-Windows-TerminalServices-Gateway" Guid="{4D5AE6A1-C7C8-4E6D-B840-4D8080B42E1B}" /><EventID>313</EventID><Version>0</Version><Level>0</Level><Task>3</Task><Opcode>30</Opcode><Keywords>0x4000000000000000</Keywords><TimeCreated SystemTime="2019-06-02T06:53:52.033537700Z" /><EventRecordID>31005</EventRecordID><Correlation ActivityID="{F9A66720-F292-459D-9E6D-40D1A86A0000}" /><Execution ProcessID="4696" ThreadID="15348" /><Channel>Microsoft-Windows-TerminalServices-Gateway/Operational</Channel><Computer>computer_name.domain.example.com</Computer><Security UserID="S-1-5-20" /></System><UserData><EventInfo xmlns="aag"><Username>user@domain</Username><IpAddress>xx.xxx.xx.xxx:58558</IpAddress></EventInfo></UserData></Event> Event 4: Log Name: Microsoft-Windows-TerminalServices-Gateway/Operational Source: Microsoft-Windows-TerminalServices-Gateway Date: 02/06/2019 09:53:52 Event ID: 200 Task Category: (2) Level: Information Keywords: Audit Success,(16777216) User: NETWORK SERVICE Computer: computer_name.domain.example.com Description: The user "domain\user", on client computer "xx.xxx.xx.xxx", met connection authorization policy requirements and was therefore authorized to access the RD Gateway server. The authentication method used was: "NTLM" and connection protocol used: "HTTP". Event Xml:<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"><System><Provider Name="Microsoft-Windows-TerminalServices-Gateway" Guid="{4D5AE6A1-C7C8-4E6D-B840-4D8080B42E1B}" /><EventID>200</EventID><Version>0</Version><Level>4</Level><Task>2</Task><Opcode>30</Opcode><Keywords>0x4020000001000000</Keywords><TimeCreated SystemTime="2019-06-02T06:53:52.174207400Z" /><EventRecordID>31006</EventRecordID><Correlation ActivityID="{F9A66720-F292-459D-9E6D-40D1A86A0000}" /><Execution ProcessID="4696" ThreadID="3132" /><Channel>Microsoft-Windows-TerminalServices-Gateway/Operational</Channel><Computer>computer_name.domain.example.com</Computer><Security UserID="S-1-5-20" /></System><UserData><EventInfo xmlns="aag"><Username>domain\user</Username><IpAddress>xx.xxx.xx.xxx</IpAddress><AuthType>NTLM</AuthType><Resource></Resource><ConnectionProtocol>HTTP</ConnectionProtocol><ErrorCode>0</ErrorCode></EventInfo></UserData></Event> Event 5: Log Name: Microsoft-Windows-TerminalServices-Gateway/Operational Source: Microsoft-Windows-TerminalServices-Gateway Date: 02/06/2019 09:53:52 Event ID: 300 Task Category: (5) Level: Information Keywords: Audit Success,(16777216) User: NETWORK SERVICE Computer: computer_name.domain.example.com Description: The user "domain\user", on client computer "xx.xxx.xx.xxx", met resource authorization policy requirements and was therefore authorized to connect to resource "computer_name.domain.example.com". Event Xml:<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"><System><Provider Name="Microsoft-Windows-TerminalServices-Gateway" Guid="{4D5AE6A1-C7C8-4E6D-B840-4D8080B42E1B}" /><EventID>300</EventID><Version>0</Version><Level>4</Level><Task>5</Task><Opcode>30</Opcode><Keywords>0x4020000001000000</Keywords><TimeCreated SystemTime="2019-06-02T06:53:52.236734600Z" /><EventRecordID>31007</EventRecordID><Correlation ActivityID="{F9A66720-F292-459D-9E6D-40D1A86A0000}" /><Execution ProcessID="4696" ThreadID="1984" /><Channel>Microsoft-Windows-TerminalServices-Gateway/Operational</Channel><Computer>computer_name.domain.example.com</Computer><Security UserID="S-1-5-20" /></System><UserData><EventInfo xmlns="aag"><Username>domain\user</Username><IpAddress>xx.xxx.xx.xxx</IpAddress><AuthType></AuthType><Resource>computer_name.domain.example.com</Resource><ConnectionProtocol></ConnectionProtocol><ErrorCode>0</ErrorCode></EventInfo></UserData></Event> Event 6: Log Name: Microsoft-Windows-TerminalServices-Gateway/Operational Source: Microsoft-Windows-TerminalServices-Gateway Date: 02/06/2019 09:53:52 Event ID: 302 Task Category: (3) Level: Information Keywords: (16777216) User: NETWORK SERVICE Computer: computer_name.domain.example.com Description: The user "domain\user", on client computer "xx.xxx.xx.xxx", connected to resource "computer_name.domain.example.com". Connection protocol used: "HTTP". Event Xml:<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"><System><Provider Name="Microsoft-Windows-TerminalServices-Gateway" Guid="{4D5AE6A1-C7C8-4E6D-B840-4D8080B42E1B}" /><EventID>302</EventID><Version>0</Version><Level>4</Level><Task>3</Task><Opcode>30</Opcode><Keywords>0x4000000001000000</Keywords><TimeCreated SystemTime="2019-06-02T06:53:52.252342300Z" /><EventRecordID>31008</EventRecordID><Correlation ActivityID="{F9A66720-F292-459D-9E6D-40D1A86A0000}" /><Execution ProcessID="4696" ThreadID="1984" /><Channel>Microsoft-Windows-TerminalServices-Gateway/Operational</Channel><Computer>computer_name.domain.example.com</Computer><Security UserID="S-1-5-20" /></System><UserData><EventInfo xmlns="aag"><Username>domain\user</Username><IpAddress>xx.xxx.xx.xxx</IpAddress><AuthType></AuthType><Resource>computer_name.domain.example.com</Resource><ConnectionProtocol>HTTP</ConnectionProtocol><ErrorCode>0</ErrorCode></EventInfo></UserData></Event> Event 7: Log Name: Microsoft-Windows-TerminalServices-SessionBroker/Operational Source: Microsoft-Windows-TerminalServices-SessionBroker Date: 02/06/2019 09:54:05 Event ID: 819 Task Category: RD Connection Broker processes connection request Level: Verbose Keywords: User: NETWORK SERVICE Computer: computer_name.domain.example.com Description: This connection request has timed out. User could not log on to the end point within the alloted time. Remote Desktop Connection Broker will stop monitoring this connection request. Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"><System><Provider Name="Microsoft-Windows-TerminalServices-SessionBroker" Guid="{D1737620-6A25-4BEF-B07B-AAC3DF44EFC9}" /><EventID>819</EventID><Version>0</Version><Level>5</Level><Task>101</Task><Opcode>11</Opcode><Keywords>0x2000000000000000</Keywords><TimeCreated SystemTime="2019-06-02T06:54:05.832911900Z" /><EventRecordID>534539</EventRecordID><Correlation ActivityID="{F420F4EE-0602-48B0-BB7C-BEDE86130000}" /><Execution ProcessID="4596" ThreadID="13724" /><Channel>Microsoft-Windows-TerminalServices-SessionBroker/Operational</Channel><Computer>computer_name.domain.example.com</Computer><Security UserID="S-1-5-20" /></System><EventData></EventData></Event> Event 8: Log Name: Microsoft-Windows-TerminalServices-Gateway/Operational Source: Microsoft-Windows-TerminalServices-Gateway Date: 02/06/2019 09:54:22 Event ID: 303 Task Category: (3) Level: Information Keywords: (16777216) User: NETWORK SERVICE Computer: computer_name.domain.example.com Description: The user "domain\user", on client computer "xx.xxx.xx.xxx", disconnected from the following network resource: "computer_name.domain.example.com". Before the user disconnected, the client transferred 229 bytes and received 156 bytes. The client session duration was 30 seconds. Connection protocol used: "HTTP". Event Xml:<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"><System><Provider Name="Microsoft-Windows-TerminalServices-Gateway" Guid="{4D5AE6A1-C7C8-4E6D-B840-4D8080B42E1B}" /><EventID>303</EventID><Version>0</Version><Level>4</Level><Task>3</Task><Opcode>44</Opcode><Keywords>0x4000000001000000</Keywords><TimeCreated SystemTime="2019-06-02T06:54:22.319436200Z" /><EventRecordID>31009</EventRecordID><Correlation ActivityID="{F9A66720-F292-459D-9E6D-40D1A86A0000}" /><Execution ProcessID="4696" ThreadID="15348" /><Channel>Microsoft-Windows-TerminalServices-Gateway/Operational</Channel><Computer>computer_name.domain.example.com</Computer><Security UserID="S-1-5-20" /></System><UserData><EventInfo xmlns="aag"><Username>domain\user</Username><IpAddress>xx.xxx.xx.xxx</IpAddress><AuthType></AuthType><Resource>computer_name.domain.example.com</Resource><BytesReceived>156</BytesReceived><BytesTransfered>229</BytesTransfered><SessionDuration>30</SessionDuration><ConnectionProtocol>HTTP</ConnectionProtocol><ErrorCode>1226</ErrorCode></EventInfo></UserData></Event> Event 9: Log Name: Microsoft-Windows-TerminalServices-Gateway/Operational Source: Microsoft-Windows-TerminalServices-Gateway Date: 02/06/2019 09:54:22 Event ID: 300 Task Category: (5) Level: Information Keywords: Audit Success,(16777216) User: NETWORK SERVICE Computer: computer_name.domain.example.com Description: The user "domain\user", on client computer "xx.xxx.xx.xxx", met resource authorization policy requirements and was therefore authorized to connect to resource "computer_name.domain.example.com". Event Xml:<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"><System><Provider Name="Microsoft-Windows-TerminalServices-Gateway" Guid="{4D5AE6A1-C7C8-4E6D-B840-4D8080B42E1B}" /><EventID>300</EventID><Version>0</Version><Level>4</Level><Task>5</Task><Opcode>30</Opcode><Keywords>0x4020000001000000</Keywords><TimeCreated SystemTime="2019-06-02T06:54:22.397561300Z" /><EventRecordID>31010</EventRecordID><Correlation ActivityID="{F9A66720-F292-459D-9E6D-40D1A86A0000}" /><Execution ProcessID="4696" ThreadID="5640" /><Channel>Microsoft-Windows-TerminalServices-Gateway/Operational</Channel><Computer>computer_name.domain.example.com</Computer><Security UserID="S-1-5-20" /></System><UserData><EventInfo xmlns="aag"><Username>domain\user</Username><IpAddress>xx.xxx.xx.xxx</IpAddress><AuthType></AuthType><Resource>computer_name.domain.example.com</Resource><ConnectionProtocol></ConnectionProtocol><ErrorCode>0</ErrorCode></EventInfo></UserData></Event> Event 10: Log Name: Microsoft-Windows-TerminalServices-Gateway/Operational Source: Microsoft-Windows-TerminalServices-Gateway Date: 02/06/2019 09:54:22 Event ID: 302 Task Category: (3) Level: Information Keywords: (16777216) User: NETWORK SERVICE Computer: computer_name.domain.example.com Description: The user "domain\user", on client computer "xx.xxx.xx.xxx", connected to resource "computer_name.domain.example.com". Connection protocol used: "HTTP". Event Xml:<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"><System><Provider Name="Microsoft-Windows-TerminalServices-Gateway" Guid="{4D5AE6A1-C7C8-4E6D-B840-4D8080B42E1B}" /><EventID>302</EventID><Version>0</Version><Level>4</Level><Task>3</Task><Opcode>30</Opcode><Keywords>0x4000000001000000</Keywords><TimeCreated SystemTime="2019-06-02T06:54:22.397561300Z" /><EventRecordID>31011</EventRecordID><Correlation ActivityID="{F9A66720-F292-459D-9E6D-40D1A86A0000}" /><Execution ProcessID="4696" ThreadID="5640" /><Channel>Microsoft-Windows-TerminalServices-Gateway/Operational</Channel><Computer>computer_name.domain.example.com</Computer><Security UserID="S-1-5-20" /></System><UserData><EventInfo xmlns="aag"><Username>domain\user</Username><IpAddress>xx.xxx.xx.xxx</IpAddress><AuthType></AuthType><Resource>computer_name.domain.example.com</Resource><ConnectionProtocol>HTTP</ConnectionProtocol><ErrorCode>0</ErrorCode></EventInfo></UserData></Event> Event 11: Log Name: Microsoft-Windows-TerminalServices-Gateway/Operational Source: Microsoft-Windows-TerminalServices-Gateway Date: 02/06/2019 09:54:54 Event ID: 302 Task Category: (3) Level: Information Keywords: (16777216) User: NETWORK SERVICE Computer: computer_name.domain.example.com Description: The user "domain\user", on client computer "xx.xxx.xx.xxx", connected to resource "computer_name.domain.example.com". Connection protocol used: "UDP". Event Xml:<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"><System><Provider Name="Microsoft-Windows-TerminalServices-Gateway" Guid="{4D5AE6A1-C7C8-4E6D-B840-4D8080B42E1B}" /><EventID>302</EventID><Version>0</Version><Level>4</Level><Task>3</Task><Opcode>30</Opcode><Keywords>0x4000000001000000</Keywords><TimeCreated SystemTime="2019-06-02T06:54:54.123103000Z" /><EventRecordID>31012</EventRecordID><Correlation ActivityID="{F9A66720-F292-459D-9E6D-40D1A86A0000}" /><Execution ProcessID="4696" ThreadID="3132" /><Channel>Microsoft-Windows-TerminalServices-Gateway/Operational</Channel><Computer>computer_name.domain.example.com</Computer><Security UserID="S-1-5-20" /></System><UserData><EventInfo xmlns="aag"><Username>domain\user</Username><IpAddress>xx.xxx.xx.xxx</IpAddress><AuthType></AuthType><Resource>computer_name.domain.example.com</Resource><ConnectionProtocol>UDP</ConnectionProtocol><ErrorCode>0</ErrorCode></EventInfo></UserData></Event> Event 12: Log Name: Microsoft-Windows-TerminalServices-Gateway/Operational Source: Microsoft-Windows-TerminalServices-Gateway Date: 02/06/2019 09:54:54 Event ID: 205 Task Category: (2) Level: Information Keywords: (16777216) User: NETWORK SERVICE Computer: computer_name.domain.example.com Description: The user "domain\user", on client computer "xx.xxx.xx.xxx", successfully connected to the remote server "computer_name.domain.example.com" using UDP proxy. The authentication method used was: "Cookie". Event Xml:<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"><System><Provider Name="Microsoft-Windows-TerminalServices-Gateway" Guid="{4D5AE6A1-C7C8-4E6D-B840-4D8080B42E1B}" /><EventID>205</EventID><Version>0</Version><Level>4</Level><Task>2</Task><Opcode>30</Opcode><Keywords>0x4000000001000000</Keywords><TimeCreated SystemTime="2019-06-02T06:54:54.123103000Z" /><EventRecordID>31013</EventRecordID><Correlation ActivityID="{F9A66720-F292-459D-9E6D-40D1A86A0000}" /><Execution ProcessID="4696" ThreadID="15808" /><Channel>Microsoft-Windows-TerminalServices-Gateway/Operational</Channel><Computer>computer_name.domain.example.com</Computer><Security UserID="S-1-5-20" /></System><UserData><EventInfo xmlns="aag"><Username>domain\user</Username><IpAddress>xx.xxx.xx.xxx</IpAddress><AuthType>Cookie</AuthType><Resource>computer_name.domain.example.com</Resource><BytesReceived></BytesReceived><BytesTransfered></BytesTransfered><SessionDuration></SessionDuration><ConnectionProtocol></ConnectionProtocol><ErrorCode>0</ErrorCode></EventInfo></UserData></Event> Event 13: Log Name: Microsoft-Windows-TerminalServices-Gateway/Operational Source: Microsoft-Windows-TerminalServices-Gateway Date: 02/06/2019 09:54:54 Event ID: 302 Task Category: (3) Level: Information Keywords: (16777216) User: NETWORK SERVICE Computer: computer_name.domain.example.com Description: The user "domain\user", on client computer "xx.xxx.xx.xxx", connected to resource "computer_name.domain.example.com". Connection protocol used: "UDP". Event Xml:<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"><System><Provider Name="Microsoft-Windows-TerminalServices-Gateway" Guid="{4D5AE6A1-C7C8-4E6D-B840-4D8080B42E1B}" /><EventID>302</EventID><Version>0</Version><Level>4</Level><Task>3</Task><Opcode>30</Opcode><Keywords>0x4000000001000000</Keywords><TimeCreated SystemTime="2019-06-02T06:54:54.123103000Z" /><EventRecordID>31014</EventRecordID><Correlation ActivityID="{F9A66720-F292-459D-9E6D-40D1A86A0000}" /><Execution ProcessID="4696" ThreadID="3132" /><Channel>Microsoft-Windows-TerminalServices-Gateway/Operational</Channel><Computer>computer_name.domain.example.com</Computer><Security UserID="S-1-5-20" /></System><UserData><EventInfo xmlns="aag"><Username>domain\user</Username><IpAddress>xx.xxx.xx.xxx</IpAddress><AuthType></AuthType><Resource>computer_name.domain.example.com</Resource><ConnectionProtocol>UDP</ConnectionProtocol><ErrorCode>0</ErrorCode></EventInfo></UserData></Event> Event 14: Log Name: Microsoft-Windows-TerminalServices-Gateway/Operational Source: Microsoft-Windows-TerminalServices-Gateway Date: 02/06/2019 09:54:54 Event ID: 205 Task Category: (2) Level: Information Keywords: (16777216) User: NETWORK SERVICE Computer: computer_name.domain.example.com Description: The user "domain\user", on client computer "xx.xxx.xx.xxx", successfully connected to the remote server "computer_name.domain.example.com" using UDP proxy. The authentication method used was: "Cookie". Event Xml:<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"><System><Provider Name="Microsoft-Windows-TerminalServices-Gateway" Guid="{4D5AE6A1-C7C8-4E6D-B840-4D8080B42E1B}" /><EventID>205</EventID><Version>0</Version><Level>4</Level><Task>2</Task><Opcode>30</Opcode><Keywords>0x4000000001000000</Keywords><TimeCreated SystemTime="2019-06-02T06:54:54.123103000Z" /><EventRecordID>31015</EventRecordID><Correlation ActivityID="{F9A66720-F292-459D-9E6D-40D1A86A0000}" /><Execution ProcessID="4696" ThreadID="12344" /><Channel>Microsoft-Windows-TerminalServices-Gateway/Operational</Channel><Computer>computer_name.domain.example.com</Computer><Security UserID="S-1-5-20" /></System><UserData><EventInfo xmlns="aag"><Username>domain\user</Username><IpAddress>xx.xxx.xx.xxx</IpAddress><AuthType>Cookie</AuthType><Resource>computer_name.domain.example.com</Resource><BytesReceived></BytesReceived><BytesTransfered></BytesTransfered><SessionDuration></SessionDuration><ConnectionProtocol></ConnectionProtocol><ErrorCode>0</ErrorCode></EventInfo></UserData></Event> Event 15: Log Name: Microsoft-Windows-TerminalServices-Gateway/Operational Source: Microsoft-Windows-TerminalServices-Gateway Date: 02/06/2019 09:54:54 Event ID: 303 Task Category: (3) Level: Information Keywords: (16777216) User: NETWORK SERVICE Computer: computer_name.domain.example.com Description: The user "domain\user", on client computer "xx.xxx.xx.xxx", disconnected from the following network resource: "computer_name.domain.example.com". Before the user disconnected, the client transferred 637 bytes and received 4567 bytes. The client session duration was 0 seconds. Connection protocol used: "UDP". Event Xml:<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"><System><Provider Name="Microsoft-Windows-TerminalServices-Gateway" Guid="{4D5AE6A1-C7C8-4E6D-B840-4D8080B42E1B}" /><EventID>303</EventID><Version>0</Version><Level>4</Level><Task>3</Task><Opcode>44</Opcode><Keywords>0x4000000001000000</Keywords><TimeCreated SystemTime="2019-06-02T06:54:54.466828900Z" /><EventRecordID>31016</EventRecordID><Correlation ActivityID="{F9A66720-F292-459D-9E6D-40D1A86A0000}" /><Execution ProcessID="4696" ThreadID="3132" /><Channel>Microsoft-Windows-TerminalServices-Gateway/Operational</Channel><Computer>computer_name.domain.example.com</Computer><Security UserID="S-1-5-20" /></System><UserData><EventInfo xmlns="aag"><Username>domain\user</Username><IpAddress>xx.xxx.xx.xxx</IpAddress><AuthType></AuthType><Resource>computer_name.domain.example.com</Resource><BytesReceived>4567</BytesReceived><BytesTransfered>637</BytesTransfered><SessionDuration>0</SessionDuration><ConnectionProtocol>UDP</ConnectionProtocol><ErrorCode>1226</ErrorCode></EventInfo></UserData></Event> Event 16: Log Name: Microsoft-Windows-TerminalServices-Gateway/Operational Source: Microsoft-Windows-TerminalServices-Gateway Date: 02/06/2019 09:54:54 Event ID: 303 Task Category: (3) Level: Information Keywords: (16777216) User: NETWORK SERVICE Computer: computer_name.domain.example.com Description: The user "domain\user", on client computer "xx.xxx.xx.xxx", disconnected from the following network resource: "computer_name.domain.example.com". Before the user disconnected, the client transferred 1641 bytes and received 7160 bytes. The client session duration was 0 seconds. Connection protocol used: "UDP". Event Xml:<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"><System><Provider Name="Microsoft-Windows-TerminalServices-Gateway" Guid="{4D5AE6A1-C7C8-4E6D-B840-4D8080B42E1B}" /><EventID>303</EventID><Version>0</Version><Level>4</Level><Task>3</Task><Opcode>44</Opcode><Keywords>0x4000000001000000</Keywords><TimeCreated SystemTime="2019-06-02T06:54:54.529322500Z" /><EventRecordID>31017</EventRecordID><Correlation ActivityID="{F9A66720-F292-459D-9E6D-40D1A86A0000}" /><Execution ProcessID="4696" ThreadID="15808" /><Channel>Microsoft-Windows-TerminalServices-Gateway/Operational</Channel><Computer>computer_name.domain.example.com</Computer><Security UserID="S-1-5-20" /></System><UserData><EventInfo xmlns="aag"><Username>domain\user</Username><IpAddress>xx.xxx.xx.xxx</IpAddress><AuthType></AuthType><Resource>computer_name.domain.example.com</Resource><BytesReceived>7160</BytesReceived><BytesTransfered>1641</BytesTransfered><SessionDuration>0</SessionDuration><ConnectionProtocol>UDP</ConnectionProtocol><ErrorCode>1226</ErrorCode></EventInfo></UserData></Event> Event 17: Log Name: Microsoft-Windows-TerminalServices-SessionBroker/Operational Source: Microsoft-Windows-TerminalServices-SessionBroker Date: 02/06/2019 09:54:54 Event ID: 800 Task Category: RD Connection Broker processes connection request Level: Verbose Keywords: User: NETWORK SERVICE Computer: computer_name.domain.example.com Description: RD Connection Broker received connection request for user domain\user. Hints in the RDP file (TSV URL) = tsv://MS Terminal Services Plugin.1.RemoteApps Initial Application = rdpinit.exe Call came from Redirector Server = computer_name.domain.example.com Redirector is configured as Virtual machine redirector Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"><System><Provider Name="Microsoft-Windows-TerminalServices-SessionBroker" Guid="{D1737620-6A25-4BEF-B07B-AAC3DF44EFC9}" /><EventID>800</EventID><Version>0</Version><Level>5</Level><Task>101</Task><Opcode>11</Opcode><Keywords>0x2000000000000000</Keywords><TimeCreated SystemTime="2019-06-02T06:54:54.669933800Z" /><EventRecordID>534540</EventRecordID><Correlation ActivityID="{F420EE10-A030-485A-8B06-EFE8C1E30000}" /><Execution ProcessID="4596" ThreadID="13724" /><Channel>Microsoft-Windows-TerminalServices-SessionBroker/Operational</Channel><Computer>computer_name.domain.example.com</Computer><Security UserID="S-1-5-20" /></System><UserData><EventXML xmlns="Event_NS"><param1>domain\user</param1><param2>tsv://MS Terminal Services Plugin.1.RemoteApps</param2><param3>rdpinit.exe</param3><param4>computer_name.domain.example.com</param4><param5>Virtual machine redirector</param5></EventXML></UserData></Event> Event 18: Log Name: Microsoft-Windows-TerminalServices-SessionBroker/Operational Source: Microsoft-Windows-TerminalServices-SessionBroker Date: 02/06/2019 09:54:55 Event ID: 801 Task Category: RD Connection Broker processes connection request Level: Verbose Keywords: User: NETWORK SERVICE Computer: computer_name.domain.example.com Description: RD Connection Broker successfully processed the connection request for user domain\user. Redirection info: Target Name = COMPUTER_NAME Target IP Address = XXX.X.XX.XXX, a000:b000:c000::d000:e000 Target Netbios = COMPUTER_NAME Target FQDN = computer_name.domain.example.com Disconnected Session Found = 0x0 Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"><System><Provider Name="Microsoft-Windows-TerminalServices-SessionBroker" Guid="{D1737620-6A25-4BEF-B07B-AAC3DF44EFC9}" /><EventID>801</EventID><Version>0</Version><Level>5</Level><Task>101</Task><Opcode>11</Opcode><Keywords>0x2000000000000000</Keywords><TimeCreated SystemTime="2019-06-02T06:54:55.091773200Z" /><EventRecordID>534541</EventRecordID><Correlation ActivityID="{F420EE10-A030-485A-8B06-EFE8C1E30000}" /><Execution ProcessID="4596" ThreadID="6204" /><Channel>Microsoft-Windows-TerminalServices-SessionBroker/Operational</Channel><Computer>computer_name.domain.example.com</Computer><Security UserID="S-1-5-20" /></System><UserData><EventXML xmlns="Event_NS"><param1>domain\user</param1><param2>COMPUTER_NAME</param2><param3>XXX.X.XX.XXX, a000:b000:c000::d000:e000</param3><param4>COMPUTER_NAME</param4><param5>computer_name.domain.example.com</param5><param6>0x0</param6></EventXML></UserData></Event>
I have numbered the events for ease of reference.
As can be seen from event #7 and #14 the user disconnects twice after 30 sec timeout.
From some research it seems like a possible problem may be in the VM settings, which is not in my control so if it is the case I would have to know what exactly to ask from the hosting service.
Any idea/solution will be greatly appreciated!
NetSh AdvFirewall Reset crash the server
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?
Detecting an active Remote Connection using Windows RDP
Hello,
I am currently working on a feature that programmatically(using Java) detects whether a system running Windows RDP has any active established connections. To make this distinction my current approach is to interrogate Windows Registry (HKey.CURRENT_USER\\Volatile
Environment) for the environmental variable SESSIONNAME which has the value "Console" when the machine is not in sharing mode and "RDP-Tcp#0"when connected remotely from another machine.
However, I have only tested this solution using Windows 7 and Windows 10 and I would like to know if there could be possible issues in the case of other versions or other discrepancies that would make this solution not viable. Also, if the current solution is overly complicated, are there simpler alternatives that I could use?
Thank you for your time and best regards,
iulia_paniti
Remote desktop collection is missing properties I would like to add
Hello everyone,
I am using Server 2012 Datacenter in a VMware environment. What I am trying to do is have one of our Remote Desktop collections, when clicked on through RD Web Access, already have the computer name and the RD gateway server when open/launched (custom .rdp file).
I have seen articles saying in 2008 server you could do this through a GUI, but with Server 2012, Server Manager doesn't allow you to add the custom properties I am looking for. Instead, it is suggested, well implied, to use powershell. Below are the options I'd like to add but while trying to use powershell, I receive the overly posted, "You cannot call a method on a null-valued expression." At looking at the Set-RDSessionCollectionConfiguration command, no where on the page does it say it returns an object/value/something, and all variables I pass accept strings. I know I am missing something but I am unsure what. Here is a how I am trying to use the above command:
Set-RDSessionCollectionConfiguration -CollectionName "Faculty" -CustomRdpProperty "full address:s:Server.SomeDomain.ORG"
Below are several other properties I'd like to add where I have found that by adding `n in between commands, it should work, but I wanted to start with one property before jumping ahead. In addition, I'd like to add a custom certificate but that isn't as important as getting the computer name and default gateway addresses to show up, and not have the end user type it in.
gatewayusagemethod:i:2
gatewayprofileusagemethod:i:1
gatewaycredentialssource:i:0
full address:s:Server.SomeDomain.ORG
gatewayhostname:s:Server.SomeDomain.org
I appreciate everyone for reading this and look forward to any help and/or insight. I had links to articles/technet but because my account is not verified yet, I couldn't link to them. If you have any questions, I will be more than happy to assist.
Sincerely,
Mike
goto specific Terminalserver when haveing farm
Hello,
- Customer has one Windwos 2016 Server as RDP Broker
- and also two Windows 2016 Std. Servers as Terminalserver Farm.
- Customer asked if there is a way to connect to a specific Terminalserver (because sometimes the 3rd Party ERP Client has Problems so only a Admin can solve it)
- mstsc /admin is not working for Domain-Users without admin-rights
- The point is, that customer is working 24/7 without SLA and we are talking only about 2-4 Persons who need to work 24/7
- Solutions-Ideas:
create a batchfile with "shutdown -r -t 0 and create second (local) admin to do it via right click...
create a batchfile for change logon /drainuntilrestart (and find a solution about admin credentials for it...)
Thx for your Opinion
2nd Session host problems
I've recently added a 2nd session host server that we are going to put off site. We got it setup in our lab here and it's on it's own router with a site to site vpn connection setup between it and our main RDS servers router. When both sites are up it works just fine. But if I kill the vpn connection to test the failover I run into problems.
When the Dell Wyse terminal tries to connect to "server" we've put both servers in DNS with a records and named them both server, it connects and ask for a username and then it starts to login and freezes. It then fails and if you look at the Wyse logs it initially connects to 192.168.90.3 (IP of failover server) but then after you type in your username and password it tries to connect to 10.16.1.3 (primary rds server) which it can't because that servers unreachable.
Any ideas on where I've went wrong?
Thanks
RDS Servers Events 7011, 7046 - BSOD rdbss.sys
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 :)
Office Licenses with Terminal Services
I am trying to find out what is the most economical licensing for Office for a Remote Desktop Server.
I apologize if this is better in the office forum but thought it was more specific to terminal services.
I have a client who needs a server that will run 15 users using Quickbooks.
The only app they need is Excel to be able to output reports from Quickbooks to Excel.
So they question are
1. What is required? An Open License for just Excel? Does that exist for just Excel?
2. What if only 10 of the 15 users need to be able to export to Excel, can I just get 10 licenses and assign them to those users only?
Thank you.
Bob Karon Computer Solutions www.INeedBob.com