Probably been asked many times before - but im yet to see any reasonable answers for it.
We have a 100+ server farm about to go live, and the helpdesk has just noticed that the connecting computername is not show in the management interface.
I've done some searching and found that no native powershell commands seem to display this information.
How does everyone else get this information?
I am trying to run remote apps in W10 Enterprise LTSB.
I can run the explorer.exe without any problem.
But the rest of the programs all give a error message saying unable to open program or file (but the remote session is started i can see it in the details)
Can anyone help me?
Thanks
**** edit
the server is the W10 Enterprise LTSB
hello i have 2 servers to use for rds build.
can i install the broker on one of the hosts? or can these roles not be combined with session host role? or better yet can i install the broker on both session host for high availability of the broker role?
obviously best practice dictates to use dedicated server for the broker .
thanks.
Hello,
I can not beleive that we are the only one with this problem. I started a question about this issue a long time ago. (see https://social.technet.microsoft.com/Forums/windowsserver/en-US/03d614d5-5fb8-44ed-a2f7-3e439a62d265/web-passwords-not-saved-in-credential-manager?forum=winserverTS)
For now we had a workarround by using google chrome but because they will end the java and silverlight plugins we need to go back to Internet Explorer.
The problem:
When using Roaming Profiles in an RDS environment the Profiles are deleted at logoff (policy setting). The credential manager saves encrypted files in the directory "%USERPROFILE%\Appdata\Local\Microsoft\Vault . So when the profile is deleted at logoff the vault directory is lost and so are all the saved website passwords. So when we login to another server no saved website passwords are there.
So now we are testing with Universal Profile Disks. With UPD the localappdata folder is retained when logging into another server. BUT the credential manager is still not working properly.
When you save the passwords on server1 the passwords are saved in encrypted files in the users vault directory . When you login to server2 the files are still there but credential manager will not read them UNTIL you restart the credential manager service on that server. When restarting the service then Credential manager will read the vault directory and show the saved passwords.
I think the solution is that when a user logs on to a server then credential manager will need to read the password files in the vault directory. But that is not the case.
I hope that someone can help because this is crazy. I also contacted MS support but had no luck finding a engineer that understands the problem.
Hi,
I have assigned message permission to a remote desktop user but still he is getting access denied message when he tries to send a message. He is able to send message only to the administrator user but not any other rdp user.
Windows 2008 R2 RDP
Any Suggestions?
we have RDS installed in Windows 2016 standard edition and use session-base desktop deployment.
It was working fine for about one year. About two weeks ago, we started to have the following issue:
This computer can't connect to the remote computer.
The two computers couldn't connect in the amount of time allotted. Try connecting again. If the problem continues, contact your network administrator or technical support.
When this issue happens, we find some users are disconnected in the RDS-Collections-QuickSessionCollection. But we cannot log/sign off those users, they are always showing there.
BTW, we can sign of those users in the Task Manager-Users.
We can solve this issue by restarting the server. How to fix it without restarting the server?
Thanks!
It shows that a user has previously logged out of a RDS session, and then tries to log back in, however the UPD for that user was “in use” so the user receives a temporary profile instead. Im using 2016 windows server
Also please don’t forget that at the same time we started experiencing these errors, we started having performance issues for the users as well.
When a user first connects, there is a delay (sometimes up to 3-7min) to get a desktop. Then the user will usually open Outlook to check their emails. There is a large delay doing this as well.
It seems like for about 15 min or so after a user logs in, the system/session is EXTREMELY slow. Then after the first 15 min or so, it picks up and runs like normal (speeds).
Hi all,
I am getting confusing answers so I am hoping a licencing expert can help me.
I have a client that requires 6 staff to be able to access a server at any time. They then also require us to be able to log in as their support provider if/when issues arise. This would be up to 7 concurrent logins.
I am told you get 2 RDP licences includes with Windows server.
We have decided already that user licences are what is required as the staff at their organisation can log in from 3 different locations.
I want to know in the above how many RDP licences need to be purchased.
Do we only need 5 as there are the two provided on Windows servers?
Do we need 6 as their are 6 staff and one administrator needed?
Do I need 7 as there will be seven concurrent logins?
We are connected to a Windows 2016 RDS server using Windows 10. Any time we try to copy a file from a connected drive that is passed through in the session it causes the session to disconnect for about 10-15 seconds and then it will reconnect and shows"Error 0x800703E3: The I/O operation has been aborted because of either a thread exit or an application request."
We have tried changing SMB settings, disabling RemoteX on the RDS server and changed the RDP client to use limited bandwidth. Any suggestions would be greatly appreciated.
After installing 2018-11 Cumulative Update for Windows Server 2016 (1709) for x64-based Systems (KB4467681) on our RDS servers the outlook 2013 search bar does not work, clicking on the magnifying glass does nothing.
Going to advanced find and searching there works.
Search works again after uninstalling update.
When I run a 'query user' command to get the idle time for each user, I have noticed that it gets reset back to 0 when a new user logs in. This is a problem because our session timeouts never kick in, even if a user actually is idle. Every single time a user logs on it resets the counter for everyone.
Has anyone seen this behavior before or know how to prevent it? We have idle users who are never kicked off the server because the counter keeps getting reset.
A few users are experiencing this problem.
Event ID: 5973
Activation of app Microsoft.Windows.Cortana_cw5n1h2txyewy!CortanaUI failed with error: The remote procedure call failed. See the Microsoft-Windows-TWinUI/Operational log for additional information.
And event ID: 1000
Faulting application name: ShellExperienceHost.exe, version: 10.0.14393.2125, time stamp: 0x5a990817
Faulting module name: Windows.UI.Xaml.dll, version: 10.0.14393.2125, time stamp: 0x5a9909e5
Exception code: 0xc000027b
Fault offset: 0x00000000006d710b
Faulting process id: 0x6b78
Faulting application start time: 0x01d3c1fbf1890ced
Faulting application path: C:\Windows\SystemApps\ShellExperienceHost_cw5n1h2txyewy\ShellExperienceHost.exe
Faulting module path: C:\Windows\System32\Windows.UI.Xaml.dll
Report Id: 7c1dae0b-eec7-416c-b5c9-5148b1bc7ba6
Faulting package full name: Microsoft.Windows.ShellExperienceHost_10.0.14393.2068_neutral_neutral_cw5n1h2txyewy
Faulting package-relative application ID: App
When this happens the start menu will not work. This corresponds with me enabling the roaming of C:\Users\user\AppData\Local
I'm wondering if there is a folder I should exclude from roaming.
If it's not being caused by roaming the local folder then it may be caused by some GPO settings I also changed. I did this because windows search was out of control and consuming too many resources. Unfortunately I cannot disable search completely because of Outlook. My discussion on Outlook and search I had to re enable indexing outlook.
Any guidance on this is appreciated.
So far the only fix I've come up with is temporary, which is to delete the local profile and on the next login the start menu works. After a day or 2 it stops working again. I haven't totally recreated the user profile and I'm hoping this is not the ultimate fix because that would be a PITA to have to do that for all the users that have this happen.
Hi,
I'm just carrying out some experiments with Remote App (which I've not used before).
Basically it seems to work with at least some of the apps I need to publish, but I have found that non-admin users can still log into the full desktop using the RDP client - I understood it was either remoteapp or full desktop, but my test system seems to allow either.
Have I missed a setting somewhere? I won't want the users to be able to log into the full desktop.
Thanks
p.s. it's Server 2016
David
Satya
I have 2 different customers that both have 1 PC each that will not run RemoteApps from their terminal server. This started on about 4/15/2018 for the first customer, and the second customer had the issue since at least 4/23/2018. These are established Remote Desktop Services installations with other PCs able to run the apps fine, and these PCs were able to successfully run the RemoteApps previously.
When they attempt to run the RemoteApps, it immediately pops up an error message stating "Your computer was unable to connect to the remote computer. Try to reconnect. If the problem continues, contact the owner of the remote computer or your network administrator." However, both workstations can still successfully open a Remote Desktop Session to their respective terminal servers.
I have gone through Event Viewer on the Remote Desktop Services servers and could not find any correlating events. I searched through Application, System, Security, and all of the Remote-Desktop*, RemoteApp*, RemoteDesktop*, and TerminalServices* logs in Applications and Services Logs/Microsoft/Windows/.
On the client PCs, I do find a correlating event in Microsoft-Windows-RemoteApp and Desktop Connections/Operational. Example:
Log Name: Microsoft-Windows-RemoteApp and Desktop Connections/OperationalAt the first client, the Remote Desktop Services server is Windows Server 2016 and the workstation is Win 10 Pro.
At the second client, the Remote Desktop Services server is Windows Server 2012r2 and the workstation is Win 7 Pro.
Any and all help would be appreciated.
Thanks,
jeff
I have randomly only Black Screen, when a User logs on to a Windows 2016 Terminal Server. Sometimes, I am able to log off the User, but sometimes not even this is working and I have to reboot the Server - in this case the server crashes on Reboot after a longer time out in the shutdown progress.
The Server ist fully patched trough Windows Update. I tried already lot of suggestions that I have found in forums on the internet - nothing helped. As lots of other Admins are facing a similar problem with in different configuration, I think this should be addressed by Microsoft - or does anyone have an idea on how to solve it?
- The Terminal Server is running on a Hyper-V Server 2012 R2 in my case - but I have seen other Admin having the same problem on hardware install as well
- Antivirus is Symantec Enterprise, but I have other Admins seen having same problem with other Antivirus
- Firefox is installed on my Terminal Server
- Only two Users are working on this Terminal Server
- The problem seems to occur at least one time a week - but I also have made 50 logins and logouts in a row with the user and it did not happen one time
- All Users (in my case both Users) can be affected by the problem
- Ctrl+Alt+End does not work (so the User could logoff himself or start Task Manager
Hi,
As per this Google bug page: here
We cannot use the legacy browser extension in our session host environment.
It seems the work around is to exclude the temp and tmp directories of a user profile, from their user profile disk.
Can someone advise the appropriate syntax to use in the Remote Desktop deployment properties section of server manager to exclude these folders? Everything I have tried thus far has not worked, and my only working way of doing this is to change their environment variables at login via a script deployed using group policy. This is not ideal, as this does not complete before the user's session is initialised, meaning it is not effective until their second login.
Excluding the folder via deployment properties would be far neater, and more effective from the get go.
Thanks
Eds
