Hello All
Is it possible collect information about user that used an application in the last 30 days?
Thanks a million
Wilsterman Fernandes
Hello All
Is it possible collect information about user that used an application in the last 30 days?
Thanks a million
Wilsterman Fernandes
I started at a manufacturing facility and they want me to get the system on the production floor back up to speed. At one time they tell me the printers used to work but for the life of me I can't figure out how.
There are two versions of Wyse terminals on the production floor UNIX and Ubuntu. Each terminal has a small Brother QL-500 label printer connected via USB to the terminal. All of the terminals connect to a Windows 2008 R2 Standard server.
I can see that the terminals recognize that the printers are plugged in, and Printing is NOT disabled on the server, but the very best I can get it to do is send a test print and the Brother printer will blink fast indicating an error.
If this was a RDP from a PC to a server I don't think this would be a problem, but the terminals are driving me crazy. As a matter of fact while you guys are chewing on this I am going to bring up a PC and test that.
I have one client machine - thin T620 Windows 7 embedded.
It uses RemoteApps. Worked fine. Suddenly fail to launch RemoteApp with the error:
The remote computer disconnected the session because of an error in the licensing protocol.
There are dozens posts with a fix of this error... all of them about the same:
"Just delete the "HKLM\Software\Microsoft\MSLicensing" registry key...then launch remote desktop using "Run as Administrator". This worked for Windows 7. I had to launch as admin, otherwise it didn't work after deleting the key."
I remember I did this a year ago on one machine...
This time, I deleted MSLicensing in HKLM\Software\Microsoft\ but it is not recreated. So nothing works...
When searched the registry I found MSLicensing in:
HKLM\SOFTWARE\Wow6432Node\Microsoft\
do I have to delete it here too?
why MSLicensing is not recreated in the place where was deleted?
Thanks.
--- When you hit a wrong note its the next note that makes it good or bad. --- Miles Davis
I have a Nano Server running as a Hyper-V host and is functioning properly. I have a Windows Server 2016 with Desktop Experience server running as an RD Connection Broker and Web Access server. I would like to add my Nano Server as an RD Virtualization Host server, but it fails the compatibility check with the message "The server must be joined to a domain." Both servers are members of the same domain.
This also generates an error in the event log when I attempt to add the server:
"Validation error: Nano1.<my_domain>.local: The server must be joined to a domain."
Log Name: Microsoft-Windows-Rdms-UI/Admin
Source: Rdms-UI
Event ID: 4099
Am I doing something wrong or is it not supported to use a Nano server as an RD Virtualization Host? I'm guessing the "UI" part of the error message means it is trying to run something on the Nano server that isn't there, but why? If I can use it as a Hyper-V host, why not Remote Desktop Services?
Thanks!
I’m trying to phase out an old 2003 Terminal Server that is now only being used by three out of state users. They only use it to access one specific application called Ramquest. We have a new Server 2012 R2 SQL box (member server, not a DC) that Ramquest runs on that I think we can Publish the app to RemoteApp using the quick setup but I haven’t done that before so wanted to get a little more info on how that would work. The server has 2 NIC’s but only one is in use. Can I accomplish this using that single NIC? I figure the those remote users can open the remote app and then I can safely decommission the 2003 Terminal Server.
Hello
We currently use 2008r2 to run a single Remote Desktop Server. Half a dozen staff or so may need to log in to it to use a couple of specific MS Access databases for brief periods of time over the course of a day, and a specific few for an accounting program.Most
are setup with an RDP file for RemoteApp mode.
I've spent about an hour searching the web for information about 2016 RDS and cannot find alot about it. References to 2012r2 describe that the .rdp file is now gone as a method for RemoteApp. And I can't seem to find any description of RemoteApp mode for Server 2016 at all? I keep encountering descriptions of needing to setup whole VDI images. I really like the simplicity of our RemoteApp mode approach because we are not a huge user base, but I don't want to go to managing all kinds of full operating system images just to deploy a single app.
Could someone point me to something that offers a clear comparison of the transition from 08 to 16? Is RemoteApp as one would know it in 08r2 completely gone?
Dear All
Please, let me know the windows server 2012R2 can deploy to users allowed?
After creating application from the RD Application Manager, how can I prevent the users from seeing/editing the client?
For example, if I create the .rdp file, he can open in notepad, view/edit the settings. How can I prevent the user from this?
Also what is the best way to restrict the user from accessing C, D drive and desktop?
Im doing some research, but the most of the material I've found is for old versions (Server 2003/2008)
Current Network
-
Server1 - Windows 2012 Essentials (DC, DNS, DHCP, AD)
Server2(Virtualized XenServer) - Windows 2012 Essentials (remote desktop only)
Laptop01 - Is my test hardware - W7 Pro
-
The connection comes from outside, and the firewall give a port forward through to internal ip (port 3389)
-
Basically I need 2 workstations accessing the server2 and printing in a local usb printer(ZEBRA GK420d), But my Remote Desktop is not showing my printers
Not successful attempts:
Turn on EasyPrint on Gpedit (Client/ Server)
Install Zebra Driver on Server2 (I installed the wizard, and I installed another printer (same model) from local network)
Framework 4.5 Installed on both(Server Client)
Printers box is ticked (Local resources)
User got administrator rights.
.
I got the "Fax" printer on local client, it's showing on the server as must be, also when I open printer properties, I can see the TS001 to TS012 ports, all empty and the the only in current use, is the "Fax(redirected)"
Any thoughts?
Thanks!!
I have a Remote Desktop Host Session setup using Windows 2016 Server and install Office 2016 Standard on to the server. I configured RDWEB on the server for client that are using Internet Explorer in Windows 10 Pro to access all RemoteApp advertised via RDWEB.
The issue is that when I launch any Office Application (e.g. Word, Excel, etc), the windows of the app is in maximize state but it is not in full screen where there is a small gap on top and left side of the windows. The windows looks a little bit off and I can see the status bar is behind the task bar of the client machine (screenshot - hxxps://1drv.ms/i/s!AkDMTDPrqMYAhagiH1G0hmXD-7V2sA).
Other RemoteApp such as Internet Explorer, Paint, and all other 3rd party application works fine and get a full screen without the gap when maximize the application window. The only issue is with all Office 2016 application.
Note that I have tried to fresh installed all the component (Windows 2016 Standard Server, Office 2016 Standard and Windows 10 Pro) to avoid any other probability.
The issue does appear if I'm using the same setup / configuration but with Windows 2012 R2 Server as Remote Desktop Host.
Appreciate some help from the expert here. Thank you. :)
Hi, I've this issue after migration of RDS server from 2012 R2 to 2016 and client have Windows 10 1709 but with Windows 10 1703 no issue.
Any suggestions?
Hello Guys,
In the last time since we upgraded our Terminal Services to Windows Server 2016, we're facing a problem.
Sometimes it happens that when a user starts a RemoteApp, he get's a black Screen on Logon and nothing more happens.
When he closes the Window and start the RemoteApp again he login successfully.
Have some of you expierienced with this problem?
Thanks for your help!
Regards,
Dominic
Hello Experts,
I am looking for guidance on how to allow RDP over TLS 1.2 only in windows 2008, 2008R2. 2012, 2012R2.<o:p></o:p>
I used IIS Crypto tool to remove all vulnerable ciphers, protocols hashes etc. but when I reboot machine I lost RDP access. I googled a lot and found many articles that state that MS has released a update to support RDP over TLS 1.2 for windows server 2008 and previous versions but I can’t see TLS 1.2 in RDP security layer level in group policy. same goes for windows 2012/R2 etc.<o:p></o:p>
so I can disable vulnerable protocols using IIS Crypto but not sure how to make sure that RDP is set to happen over TLS 1.2 only. <o:p></o:p>
Any help would be highly appreciated.
Thank you
I guess most of you know that if you use Microsoft Edge or Chrome to access the RD Web Access site (2012 R2) it will not automatically start the RemoteApps but the browser will download the .rdp file and the user have to start it "manually". Anyone solved the way around this or is it just the way it is because it's ActiveX based? I don't think 2016 solves this.
I know you can publish the RemoteApp shortcuts on the user's start menu via the Control Panel -> RemoteApp and Desktop Connections but this is not a solution for us since most of our users are BYOD users.
Looks like, we cannot use 385.54 drivers for virtual GPU, unable to run virtual GPU (Remote FX) as GPU does not show in the HyperV setting. Once they reverted to old driver 376.84, physical GPUs under Hyper-V settings can be seen.
This are not grid Software just drivers downloaded from website.
Is anyone facing the same issue with the driver version.
Thanks in advance
Folks,
Just noticed this becoming an issue on a Windows 2012 R2 Terminal Server after the last round of Patch Tuesday updates stemming from August 9th, 2016.
Typically, I'm rebooting the server every 24 hours to over-correct the issue - rebooting not being the best option here.
In previous discussions, it's advised to remove KB3002657 or KB3035132 from the server. Is this still the best option to restore full functionality even with the last round of patches and updates? Just to confirm, we are not using webroot as an AV solution.
So we have a few 2012 R2 Terminal Servers at my company that were working fine until we started the process of replacing our Domain Controllers with new Windows 2016 Servers.
Since then our users are getting intermittent "Access Denied" errors when they try to RDP to these terminal servers.
Generally the "Access Denied" error occurs when a terminal servers starts to use one of the newly added 2016 domain controllers. We can workaround the problem by sending an command telling the terminal server to use one of the older 2012 R2 domain controllers instead. Then things work again.
So the question:
Is there a misconfiguration with the new 2016 domain controllers or can an adjustment be made with the 2012 Terminal Servers?
Is the problem that Windows 2016 Domain Controllers are not compatible with 2012 R2 Remote Desktop Services servers?
We are having problems finding documentation on this.
What we do know is that if we decide to start upgrading to new 2016 Terminal Servers we will have to purchase new 2016 RDS Cals (not sure if we are budgeted for that...)
For those interested, you can find out the domain controller you are using by running the following elevated PowerShell command (this assumes the command is run remotely as you might be locked out due to the RDP access denied error):
nltest /Server:<your-terminal-server> /DSGETDC:<ad domain>
to specify the domain controller you want to be on (in our case we want to switch to back to a 2012 R2 domain controller), the command is:
nltest /Server:<your-terminal-server> /SC_RESET:<ad domain>\<specific domain controller>
We have a domain, with multiple servers and multiple users. We use a domain login script, which primarily maps drives, and everyone is setup to run the login script in Active Directory. It has been working for years. Suddenly, last week, I'm getting reports of drive letters not being mapped. I tested several users, and it wasn't running the script on login, on either our 2008R2 or our 2012R2 servers. If I manually run the script, it works fine, so there isn't anything regarding access to the script, or the locations. Temporarily, I setup group policies to map the drive letters, but that isn't really the way I'd like to have things work. Any idea what might be wrong?
Thank you.
Jeremy Heymann Market Mentor Online
Hi,
Ive recently deployed the HTML5 Web Client, at an existing RDS 2016 setup, using this guide:
https://custominterfacesolutions.com/html5-web-client-microsoft-remote-desktop-services-2016-steps-install-rd-web-client/
The setup contains 1 x RDWeb server, 2 x RDGW and 2 x Connection brokers.
A single public trusted wildcard certificate is used, for the entire RDS setup, containing the domain name, that the servers is belonging to.
Im able to login to the Web Client, and see all the published applications, that is available.
But when trying to connect, i then get an certificate error, containing the name of the Remote Desktop Session host...
Ive managed to find the certificate at the Session Host, containing the same thumbprint as the one on the picture.
Added the certificate to the trusted root cert auth, across all the frontend RDS servers (Web,GW,CB) - but that didnt help.
What seems to be the problem, since i cant find any solution to this error?