We have a small W2K12R2 Domain with roaming profiles.
I believe that using the "Remote Desktop Services Profile" path option prevents the roaming profiles from being inherited when users log onto the RDS.
Do User Profile Disks also provide a separate profile for an RDS session or do they interact with the domain roaming profiles in some way?
Thanks >> Joe
I have a Windows 2008 Server that I have been connecting to once a month remotely to apply OS updates. Often, I reboot that server and it uses auto-logon to login and run an application.
Today, I rebooted the server and when I try to connect with RDP, I get the login prompt and enter my credentials, I see a few expected messages fly by on the host OS (the last one I see is the word Welcome), but then the screen goes black.
The apps on the server are running successfully because our applications can connect to them, we just can't logon to the desktop of the Windows Server 2008.
I made no configuration changes (I NEVER do) other than to apply the latest Windows Server updates.
I would prefer not to drive to the computers location, or try to coordinate a time to have the server hosting company assist me with troubleshooting; but is there anything else I can do? Any ideas about what might cause this?
Hello,
We are working with Windows Server 2012 R2 RDS. We also implemented User Profile Disks. This is all working fine without problems. The only issue I have is that normal users are unable to delete files from their desktop. They are getting a message: you'll need administrator permission to delete this file, with the prompt for administrator access.
They can edit, copy, rename, cut and paste files. But they cannot delete a file from their desktop.
I checked the security permissions of the files on the desktop (for example a normal self-created PDF file) and the users are owner and have "Full Control" over the files.
I checked the file permissions and took a look under "Advanced", selecting the specific domain user and checked the "Advanced Permissions" and the user has the "Delete" option checked. So he should be able to delete the file.
I am guessing this is UPD related issue, or something in GPO. But I already unlinked the GPO objects, that I felt could be the source of this problem, but without results.
Could someone give me a hint on where to look? It's kinda annoying to users, that they can't delete their own files.
This was a well-known issue with Server 2008 R2 however I cannot find a fix for Server 2012 R2 (which is what we are running. This is a random issue where a user will get the following error when trying to launch any remote app or desktop:
"The task you are trying to do can't be completed because Remote Desktop Services is currently busy. Please try again in a few minutes. Other users should still be able to log on."
Affects random users who were previously having no issues. I do not see any process for the users, no disconnected sessions, etc. Occurs when trying to launch a desktop or a remote app. Occurs whether going through RDWeb or through the control panel applets.
This happens to clients running Windows 7 Professional or Windows 8.1 Professional.
Hello,
Virtual Server - Windows server 2012 R2 latest updates w/ Exchange 2013 Update 11.
If I add an RD Gateway Certificate, it relates itself to the IIS Exchange Back End 443 certificate. Exchange Back End doesn't have a 443 port, only a 444 port so RD Gateway automatically creates a 443 port in the Exchange Back End site. There is already a 443 in the Default Web Site so the Exchange Back End won't start. I can get the Exchange Back End to start by removing the 443 binding but next time I open RD Gateway, it gives me the error below.
So the question is, is there a way to get RD Gateway to look at the Default Web Site for its associated 443 port and certificate instead of looking at, and automatically creating the port and certificate in the Exchange Back End site?
Thank for all your help,
Robert
Hi,
I have an RDS Implementation using 2012 R2 with HA Brokers. 4 VM's The first pair are each configured as Web/Brokers(HA), and Gateways. The other two VM's are just App Servers.
I am just in the POC phase, and looking to have a clean login from the Remote App Website which allows an app to start without any additional login. The Cert for the external FQDN's is applied to all 4 functions, Web/Broker(single signon and publishing)/Gateway.
I continually get a double login to start an app... One from the Web Site and the other before the app starts. I am beginning to suspect this is because public cert (applied at all 4 cert levels) doesn't work for each of the internal RDS Session Hosts. The external FQDN of the brokers/web/gateway's is apps.domain.com while the internal AD domain is [servername].corp.domain.com. I am wondering if I am seeing the double login because of this.
Is this the compelling argument for purchasing a wildcard cert as *.domain.com and will this work when apps.domain.com is the external FQDN and the internal servers are [servername].corp.domain.com?
Arjan Mensch wrote a great 2 part article about advanced RDS deployments, but I am just not entirely sure the wildcard cert is causing the snag I am experiencing. I get that other prompts can appear about trusting the publisher, but the double login is really a big deal.
Thanks in advance for any insights.
Jeff
Hi
I have several users that are having issues with caps lock being out of sync with their local keyboard when in a Server 2008 R2 RDP session. Their local keyboard shows the caps lock light as on but they type in lower case, when they press the caps lock key and the light goes off they are then typing in upper case.
Our set up is Wyse Z90 (2nd Gen) Thinclient which has the most recent firmware/drivers and image from the Wyse website installed.
Can anyone help?
Thanks in advance.
I am struggling to get my Windows Server 2012 R2 standalone system to successfully deploy VDI quick start deployment for Virtual Machine - Based Desktop Deployment.
Hardware:
I was able to successfully install Microsoft Windows Server 2012 R2 Standard on the PCIe SSD along with drivers and windows updates. Set static ips for both adapters and installed ADDS and DNS roles to create domain controller successfully.
Next I try to deploy VDI Quick Start for Virtual Machine-Based Desktop Deployment using a sysprep Win10 VHD (mode:vm).
I am really struggling to get this system up and running with personal virtual machines that clients can connect to. I have tried installing VDI with standard deployment as well as individual roles even trying to MS checklist one role at a time. When I get to installing RD Virtualization Host role it fails.
Can someone please help me? I don’t know what I am missing.
Thank you for your feedback.
-- Michael Lowe Computer Engineering
I have a client that connects to his VM from a monitor with a resolution of 3440x1440 but the virtual machine is limited to 2560x1440 because the maximum that can be selected in Hyper-V settings is up to 8 displays at up to a resolution of 2560x1600. How can I use the full resolution of the display when connecting to the VM?
The hardware that is being used,
- AMD FirePro S7000 Graphics Card (Server 2012 R2 Standard)
- HP T620 Thin Client (DisplayPort)
- Samsung 34" Curved 3440x1440 Monitor (DisplayPort)
- DisplayPort to DisplayPort Cable
-- Michael Lowe Computer Engineering
I have accounting program installed on several workstations and some users have access to it's catalog, from terminal services. Problem is that, you must provide unique host name for each user, to access this program. If one user uses servers host name, another users can't access to it's catalog. i need assign to users host names like this hostname.01 and so on...
how can i do that?
Hey Everyone,
Rather strange issue we've run into in the past month or two. I just submitted a case to MS about the issue, but I'm curious if anyone here has seen this.
Environment: 5 2012R2 RDS Servers, up to date with all updates. Clients - Win 7 all up to date. Users have roaming TS profiles.
In late december, we started to see an issue where RDS servers seem "stuck", and nobody can log into them. A user will sit and wait at the RDP login screen 'Please Wait for User profile Service' indefinitely. It's not that logins are slow, they don't work at all. Even administrators can't login (RDP, RDP console, local console). The only way to 'unstick' a server is to hard-reset it. Users can log in again, but typically only for a day or two.
We noticed in January that certain users seemed to be causing the issue. When user John Doe would log into a server (often unsuccessfully), that would 'lock' a server, and then nobody else could login (as per my description above). As such, we deleted all users roaming RDS profiles. This seemed to 'fix' the issue for 3-4 weeks, but has returned today.
We've researched this issue to death! Lots of forum threads about 08R2 having this issue, but also lots of hotfixes. Apparently in 08R2 this is caused by filesystem deadlocks. Lots of people seem to have this issue with 2012R2 as well, but very little information and very few hotfixes. Most of the threads go nowhere and have no apparent fixes. We keep peoples RDS profiles very small (most under 5-20MB), so it's not like these profiles are very large. When the farm is working properly, most people can login completely within about 10 seconds).
We've seen a couple hotfixes that seem related to this issue, but none of them have worked (3047296, 3053667). We've installed all Windows updates (Except February 2016), but nothing has resolved this issue. The farm was working fine for about 8 months in up to december when we started to see this issue.
We built entirely new RDS servers from scratch mid-january. That did not fix the issue.
Event logs are pretty clean. The only major errors are group policy taking too long to apply. Again, logins aren't slow when this happens, they dont workat all. You can sit and wait all day the the 'please wait for user profile service' screen.
We've also tried the usual group policy settings (detect slow network connections, wait for network at startup, synchronous/asynchonous login, etc), nothing has helped.
There's a few other threads with seemingly similar issues, but no real fix.
Thoughts? The only hunch I have so far is it's somehow user profile or group policy based. But again, we keep profiles clean and small.
Hi,
I'm trying to found out how much data traffic is flowing from Remote Desktop Host to client.
I think it should be the counters Remote FX Network: TCP Send Rate and UDP Packets send. Does anyone know in what unit these counters show there value? is it in bits/sec?
And one other thing. I have disabled UDP by GPO, but I still see the counter UDP Packets give a value higher than 0. Is that normal? You should think all traffic would go over TCP when disabling UDP by GPO.
Hi all,
I RDP into this server, it gives me to the company security warning and has me click OK, from there it goes to the signing out screen with the rotating dots and just sits there indefinitely.
If I log into the server using the console on our VM host, after entering my credentials it immediately goes to the singing in dot circle.
I suspect this has something to do with way I may have disconnected from the server with a previous RDP session, the only fix I've found is to have someone else log in and disconnect/log me off.
Any ideas?
We are seeing an issue with the Windows Search Service on WIndows Server 2008 R2, where we use Outlook 2010 and cached mode. The index appears to start and index fine, but when a User logs off the index is removed for that User. WHen that User logs in again the "indexed files" count is back to 0.
How can we prevent this?
I see in a post on Server 2012 using UPD this is "by design", but not sure if this also applies?
https://social.technet.microsoft.com/Forums/windowsserver/en-US/e6d4e3e6-37ef-488c-86ac-d135e3f2353f/windows-search-index-and-user-profile-disks?forum=winserverTS
Hi.
I have the exact same problem as described here https://support.microsoft.com/en-us/kb/3047296 on two Windows Server 2012 R2
But I already have af newer version (6.3.9600.18167) of rdpcorets.dll and rdpudd.dll. (The hotfix is 6.3.9600.17725)
What can I do?
Regards
Thomas Hansen
Hello everyone,
We are in the middle of an Office 365 migration from Lotus Domino. As with most Lotus Domino customers, we also have some own developed applications (databases) running off the Domino server as well as the mail part. We have to keep these applications running at least til the end of the year. These applications are not web enabled so we need to use a native Lotus Notes client to access them.
So .. we did a Windows 2012 R2 installation and added the Remoteapp role and installed a basic Lotus Notes client. We enabled the Lotus Notes application as a remote app for our users and this is working fine. We have Windows 7 (x64) clients, so we had to do some regkey tricks to get the file association to work (.nsf, .ntf, ...).
Now here is the problem. One of our own developed application is sending a notification mail when you change document owner. In this notification email the application sends a link to the specified document to the new owner. The link is presented as notes://servername/<generatedUID>. This email is now delivered to the users inbox in Outlook and we want to directly open the document in the Lotus Notes remoteapp. We have done all the regkey tricks and the URL is sent to the remoteapp server, but it's refusing it. If the user logs into to the remoteapp by RDP and run "notes://servername/<generatedUID>" the Lotus Notes client is associated and works perfectly.
Does anyone have any idea how to make the remoteapp server approve the notes:// handling?
Thanks guys!
Our 2012R2 RDS is failing to install MS Updates. They are all MS Office 2003 and 2007 related.
The Error Codes: 80096004 & 80070659
We have not experienced this on other RDS servers, but all of them have Office 2013 installed.
There is a registry key that can be adjusted to lower the security on the Windows Installer, but I am reluctant to try it before polling the forum for suggestions.
HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\Installer
https://msdn.microsoft.com/en-us/library/windows/desktop/aa368304(v=vs.85).aspx
Thanks >> Joe
Recently moved users from 2003 terminal server to 2012 R2 RDS.
Users can print to their local printers fine. The issue is in 2003 user A connects via RDP with a printer. User B connects via RDP without a printer. User B used to be able to see User A's printer and print to it. In 2012 RDS they cannot see each others terminal services mapped printers.
Is there a group policy preventing users from seeing printers in other sessions?
Illustration:
Print Device --> User A PC --> User A RDS session ---> User A printer
User B PC --> User B RDS session ---> Wants to print to user A's printer, but cannot see it.
Hi,
We have a RDS Session Host desktop collection of 4 servers. All 2012 R2.
We have those servers pointing to a file server to host UPD.
During my testing phase, everything was working fine.
We have about 100 users. When they connect, we get several users a day per server that end up with a Temporary Profile, instead of their normal UPD and we don't know why?
We have a GPO which sets the normal sort of settings for this you would expect with regard to disconnects, timeouts etc.
I have deleted all the users .BAK bits from the registry (HKLM\... Win NT \...\ ProfileList)
I have checked and when a user gets their temp profile, their UPD is accessable and I can mount it and view it OK (and disconnect it once done).
To me, it looks like the sessions are shutting down normally, I don't see any .exe remaining running in task manager etc.
AV is excluded from scanning the VHDX files on the file server.
Not sure what to check next.
Any advice please?
Thanks - James
On a virtual desktop (Windows 7 Pro) I have several apps running (no services). The account I use is a network (admin) account. I access the account via Cisco VPN. For a long while I been accessing the account and RDP to that desktop without indecent. Ever
since I rebooted the desktop due to upgrades, the account will become disabled after about 15 minutes. This happened once before and by creating another account and running the apps on that new account worked for a while. Then the new account started "locking".
I moved back to the old account which stayed working for months until the next reboot. Trying to recreate the same procedure to keep the old account from locking again did not work.
What is causing the account to lock? How can I tell what may be causing the account to lock?