Hi all,
I've setup the policy "Do not allow passwords to be saved Enabled" and the users can no more save their credential/password in the authentication windows.
But in the "logon setting" they always can select "Allow me to save credentials" even if it doesn't work.
How can I remove the option from GUI interface?
Thanks in advance
Hello all,
I've just started reading up on RDS services since Windows Server 2012.
I've already found a lot of documentation on how to setup the different components, but from the user side it is still unclear how an enduser should connect to in internal server through an RD Gateway?
I've got a test setup with 1 RD Gateway in the DMZ and 1 connection broker and 1 RD Session host in the internal LAN.
What should a user do from his homemachine?
I've read that connections are initiated over 443 from the homecomputer towards the RD Gateway.
Should he surf to a specific website then? Or should he open his RDP client and add the external address of the RD Gateway under the "advanced > Connect from anywhere section" settings of the RDP client?
Does this setting trigger the RDP client to connect over port 443 towards the RDP client?
If the enduser has to connect using his RDP client and has set the RD Gateway in the 'Connect from anywhere' setting, which hostname should he then enter to connect to? My session host IP address nor hostname is known from the outside..
Many thanks for clarifying this to me!
Filip
Hi, I am
setting up a new Citrix farm and have few questions about Terminal Services. We
have an existing Citrix farm which I will retire when new farm is up and
running. We have 2 Windows 2008 R2 DC and 1 Windows 2003 Standard DC
Where
should I install TS licenses (MS recommendation)? Can I have two license
servers in the environment? As there will two Citrix farms.
Also, do I
need Terminal Services on Citrix server? Can I install TS licenses and Terminal
Services on one server which will also be Citrix server?
Thank you
Hello,
I have recently setup RemoteApp and a RD Gateway on a 2008 R2 Standard server. The server is in the DMZ and has 80/443 open to the internet. I have created a self signed cert with the name rdweb.mycompany.com which matches the public DNS entry that was created for the site.
I am able to access the site internally and externally, launch RDP sessions successfully, as well as connect RemoteApps that I have deployed via both RDP files and MSI files. The only piece missing is when I attempt to click on a RemoteApp Program from the site I get the error "RemoteApp Disconnected - Your computer can't connect to the remote computer because an error occurred on the remote computer that you want to connect to..."
No error logs are created on either the server side or client side. As far as I can tell my setup is correct according to technet articles that I have followed in order to get everything up and running.
One note, the RemoteApp Programs work fine internally if I check the box "Bypass RD Gateway server for local addresses." With this unchecked the RemoteApps fail to launch internally with the same error.
I have read through the forums as well as explored the net and have yet to find a solution.
Hi
Is it possible to logoff disconnected sessions from TSE 2003 on specific time, for example, everyday at 20.00? I didn't find in GPO any rule which allow to logoff sessions on specific time.
I have installed RDS Services Host, Gateway and RemoteApps and RDWebAccess on a dedicated remote server that we lease from HostGator. It all works fine running hosted VB6 and VB.NET applications that our customers use.
Until I try to add another user that must have different applications than the first customer. When I try to restrict access, I am prompted that only Active Directory users can be managed in RDS...not local users? From all the Microsoft advertising hype, I thought that RDS would be perfect for our customers that don't want the expense of maintaining hardware to run our applications.
I looked into the option of installing LDAP but have discovered that it will not suffice for RDS user/application management.
So here I am faced with the prospect of creating a domain controller, on a machine with one NIC that is assigned a public IP address. NOTE: There will be no other members of the domain. I would be installing AD just for the purposes of configuring RDS. The domain would be named something like HostMachine.local to not conflict with any possible public domains.
Is this even feasible? I hear that it would make the server insecure. How could it be any more insecure than it already is as a standalone server without active directory? At least with AD I can create policies to restrict access to the disk resources.
Does anyone have suggestions so that I can administer RemoteApps properly? Or is this highly touted RDS technology only meant to be used in a closed LAN environment?
Thanks for any help.
I have a server setup as a DC with AD and RDServices installed.
I have a second server with the GW and CB and IIS and licensing and whatever else it installed.
I am using no-ip.biz to provide the external name / DNS for RDWeb.
I am using DSL and have the ports 443; 3389; and 3391 open.
_______________________
Internally, I can open RDWeb, click on an app and VOILA! It opens just fine.
Externally, I can open RDWeb, login with my credentials, click on an app . . . . then wait for it... wait for it andBOOM! The really helpful "...gateway unavailable..." message appears. At this point, it might as well be theBlue Screen of Death.
I am not an ordinary dummy but I am extraordinarily challenged. LOL.
DNS is my biggest weakness - but I am almost at wits end, thinking there has to be something I need to do in DNS to make this work. Many of you say (in other posts) create an A record for external and internal and etc etc etc. I am supposed to be a professional and "get it"...... but I don't. That's my weakness. I am a DNS Flunky.
But alas, I hope my brothers and sisters who are great at quantum physics and algebraic triginometric pi-alpha equations can help me out here.
Embarrassed? Sure... but at least I am asking for some help.
Hell, I'd even open up a rescue session so I could watch what the hell you do to fix this damn thing.
_________________
In all seriousness, guys, I am really stuck and need some guidance and help. Anything someone will do to resolve this would be more than appreciated.
Chris
I have Windows Server 2012 RDS setup with RD Gateway, same VeriSign certificate configured for all RD Connection Broker, RD Web Access, and RD Gateway.
From internal, access to RDweb works fine, from internet, I can log on and see the published applications, but when I double click any published application, and type credential, it try to connect to my session broker with internal FQDN and fails.\
What I missed? How to correct it?
Thanks for you help.
I have a VM running windows 2003 or 2008 and it is locked by the customer in console mode(on vcentre console)
RDP does not work and the customer often complains regarding this.Also ping to server gives request timed out at this point.
Upon logging to console mode and unlocking the service id under which the console for server is locked,ping starts giving response
instantly the next second and RDP also works fine.
It is to be notes that this customer has apps running in that is suspected to cause such issues.
Any way to find root cause.Please guide me the right way to find ways to fix this once for all.
Hello all,
I now have a late 2012 Mac Mini with Windows Server 2012 installed. It ships an Intel i7-3720QM CPU, with Intel HD 4000 Graphics Processor.
As is claimed by Intel, HD 4000 supports DirectX 11.0, but I cannot enable RemoteFX with an error of "None of your GPUs support RemoteFX".
So, is RemoteFX blocked on Intel HD 4000 by MS or Intel, or do I need to reinstall Windows 2012? Is there a certain sequence of installing RDS, Hyper-V role, and the Intel display driver?
Driver version:9.17.10.2932(Dec 2012)
How do I stop this without deleting all my printers on the server?:
Driver Send to Microsoft OneNote 15 Driver required for printer Send To OneNote 2013 is unknown. Contact the administrator to install the driver before you log in again.
(I am not a fan of this solution http://social.technet.microsoft.com/Forums/en-US/officeitproprevious/thread/fdb951e5-82a4-46a0-8a74-5677b18094d6)