Hi:
Will Office 2010 (32bit) work when installed on remote desktop server 2012?
Thanks
Gareth
Hi:
Will Office 2010 (32bit) work when installed on remote desktop server 2012?
Thanks
Gareth
Hi everyone,
I realise that similar questions have been asked before but I'm still having trouble. I've configured a 2012 R2 RDS farm as follows:
DC.mydomain.local-DC, RD Licensing, SQL for HA
RDCB.mydomain.local - connection broker
RDGW.mydomain.local - RD Gateway & Web Access
RDSH1.mydomain.local - Session Host (Server Desktop)
Externally, cloud.mydomain.co.uk points to the external IP of the Gateway server. I have a public certificate (GoDaddy) with cloud.mydomain.co.uk on it. I've also configured HA for the connection broker using the name cloud.mydomain.co.uk. Internally cloud.mydomain.co.uk resolves to the IP of the connection broker.
The problem is that when I connect to a resource via the RDWeb page, I get a pop-up advising that the name on the certificate doesn't match rdcb.mydomain.local. I had assumed that setting up HA would effectively hide this name from clients (i.e. they'd see cloud.mydomain.co.uk at all stages of the connection). If I ignore the certificate error it works fine but I'm sure there must be a way of getting around this, does anyone have any ideas?
Many thanks,
Matt
Matt Denham | Systems Engineer | BOM Group Ltd.
Hi,
I'm going to implement VDI solution using server 2012 R2. But it was taking too long to create the virtual desktops. Is this normal or how long does it take to create virtual desktops. I'm creating Windows 8 virtual desktops and templates are syspreped. Please see the below image for better understanding.
I've setup an RDS, RDWeb server for publishing apps, on Server 2012. Still testing.
Is it possible to set the logon screen so that a user only needs to enter in their user name and not have to reference the domain name?
I came across this link, and I think this is my solution to edit the Login.aspx,
but I'm exactly sure as this post is a bit over my head.
http://social.technet.microsoft.com/Forums/windowsserver/en-US/00434c7d-343b-45e4-8e84-9338b5d074a4/do-not-require-domain-name-when-logging-in-to-web-access?forum=winserverTS
I'm trying to simplify this as much as possible.
Any suggestions?
Hello,
we have set up a server 2012 and bought 4 User CALs for multiple acces.
RDS session host & collection deployment has been installed and configured.
however when i want to install the appropriate User CALs in RD Licensing Manager i do the following:
1) click on install license
2) enter the correct license program and agreement number
3) select product version "Windows Server 2012"
4) select license type "RDS per User CAL"
5) select quantity "4"
and then on the next screen i receive the following error message:
"the licensing agreement data provided to Microsoft is not valid. Check all the information you provided, make any necessary corrections and then resubmit your request. if the problem persists, try using a different connection method."
i have checked RD Licensing Diagnoser and see the following errors/warnings:
"Licenses are not available for this Remote Desktop Session Host server, and RD Licensing Diagnoser has identified licensing problems for the RD Session Host server"
"Number of licenses available for clients: 0"
"The Remote Desktop Session Host server is in Per User licensing mode and No Redirector Mode, but license server XXX does not have any installed licenses with the following attributes:
Product version: Windows Server 2008 or Windows Server 2008 R2
Licensing mode: Per User"
Additional information: we do not have a license server, so the same server has been specified as licensing server in RDS session host configuration.
Any help appreciated!
Best,
Sebastian
Hi,
Iam in a pickle at the moment.
My RDS 2012 R2 environment was working successfully previously, arrived from holiday and it is not longer working.
My setup:
**RDS01 ( Session Host and Connection Broker Roles )
**RDS02 ( Web Access, Gateway and Licencing Roles)
The Problem i am facing is, after successfully login to the RDWeb page, lunching the remoteapp i get the following:
1st Get Certificate mismatch ( name in the certificate RDS02.mycompany.local is not trusted )
2nd Hit YES and the following message "Windows cannot start the RemoteApp program. The following RemoteApp program is not in the list of authorized programs: WinWord"
It happens whether i do connect externally.
Internally the SSO does not work ( i did check my certificate and it is installed )
If i run the script Set-RDPublishedName and change it from remote.mycompany.com to RDS01.mycompany.local
1st Certificate name mismatch ( requrested pc RDS01, name in the certficate remote.mycompany.com )
2nd Hit Yes and the app works
It happens whether i do connect internally or externally.
Any help will be very appreciated.
cheers
Elton
Available and Issued should add up to 10, but is instead showing 0 available, 0 issued, and using “Built-in-overused” instead of the legitimate CAL.
This causes an error in the licensing diagnose:
Screenshot will not post until "verify your account" but no instructions about how to accomplish this.
Hello,
I have a 2012R2 RDS session based deployment. We have a few generic user accounts for a production environment where a group of users uses the same username to start multiple RDS sessions. This creates a bit of a challenge when support has to shadow one of those sessions because they all appear with the same name: domain\username. The Connections pane in RDS (Server manager) does not list client computer name, which would be the distinguishing factor. The old version of the RDS console (remote desktop manager) had this information. Citrix appears to have it as well. Is there a way around this limitation in 2012R2 Server Manager?
Thanks
I am currently setting up server 2012 VDI using 2 servers. A connection broker, web access, licenseing server and a VM Host server. I have followed the wizards, created my master image, created the collection, and setup group policy to add the group I want to give RDS access to Allow log on through terminal services & Remote Desktop Users group.
When I connect using my admin account everything works, it connects to the connection broker and then forwards to one of the running VMs.
When I connect using a non-admin account I am prompted with: The connection was denied because the user account is not authorized for remote login. I also get the following in the event log:
TerminalServices-SessionBroker
RD Connection Broker failed to process the connection request for user ***\****.TerminalService-SessionBroker-Client
Remote Desktop Connection Broker Client failed while getting redirection packet from Connection Broker.
--
I searched the internet high and low and I can not figure this out. I have even put the the non-admin users in the remote desktop users on the server just to see what would happen, same results if trying to connect to the pool. But I am able to connect directly to the server. I am also able to directly connect to a VM in the pool using a non-admin account.
Any help would be appreciated.
We are in the process of moving from Windows 2003 R2 and Citrix XenApp 5 to Windows 2008 R2, and Citrix XenApp6.5. About half of our users and our entire IT Department have multiple monitors. Most of our users connect to a full desktop in Citrix. We had no problem shadowing our users in the old environment but in the new environment we get an error. I understand the reason for this problem is a change in how Windows 2008 R2 supports Multiple Monitors. I know this is by design according tohttp://support.microsoft.com/kb/2484290 but the work around is not acceptable. The issue we have with the work around is that it is more time consuming and requires the user be able to accept the support request invitation. We frequently need to shadow a user when they are not at their desk, or their Citrix session is locked up.
Does anyone have a better solution or any idea when Microsoft will find a fix for Shadowing?
I have a Hyper-V Server 2012, 4 VM's, 3 are Server 2012, 1 is Server 2008 R2. One of the Server 2012 is the CAL Server, they other 2 are just remote application servers. I've got the CAL Server setup with 20 Per User licenses, The RD Licensing is setup, RD Connection Broker is setup, RD Session Host is setup and the Collection is setup. And when I state "Setup", I mean to the best of my ability...
BUT, I cannot get anyone logged into the Application Servers, keep getting "No Remote Desktop License Servers available to provide a license."
On App Server 01, RD Licensing Diagnoser DOESN'T show the CAL Server and states:
"The licensing mode for the Remote Desktop Session Host server is not configured."
On App Server 02, RD Licensing Diagnoser showes the CAL Server but states:
"The Remote Desktop Session Host server is in Per Device licensing mode and No Redirector Mode, but license server does not have any installed licenses with the following attributes:
Product version: Windows Server 2008 or Windows Server 2008 R2
Licensing mode: Per Device
License type: RDS CALs or VDI Premium Suite licenses"
Any help or guidence would be appreciated.
A couple months ago I deployed a Windows Server 2012 R2, with the intent of using RDS Gateway on it for a client. I got it working, but there is a 60 second delay during the login process to the RDS Gateway. Specifically, the RDP client hangs on "Configuring Remote Session." This happens 100% of the time from outside the network (but never when connecting to the same server on port 3389 from *inside* the same network that the server is on). It is also important to know that even though there is always a 60 second delay, it still connects successfully 100% of the time. The client is not happy with the 60 second delay though (understandably), and has asked me to to solve the problem. I have done a ton of research, but the few possible solutions I came up with ended up not solving the problem. Here is everything I have done so far:
-My problem is *most* similar to this other post: http://social.msdn.microsoft.com/Forums/en-US/20a68eec-d639-47f7-abd1-3ae10aaf4db8/remote-desktop-to-web-role-gets-stuck-on-configuring-remote-connection However, the problem in that case eventually resolved on its own, & I have already tried the only suggestion mentioned in that thread (disabling port re-direction).....either I did that improperly, or it did not help).
-100% of the time immediately after a 60 delay login, I get this warning in the server's event log:
SERVERNAME | 20499 | Warning | Microsoft-Windows-TerminalServices-RemoteConnectionManager | Microsoft-Windows-TerminalServices-RemoteConnectionManager/Admin |
"Remote Desktop Services has taken too long to load the user configuration from server \\servername.domainname.local for user XXXXXX" (where XXXXXX is an actual username).
The only recommendation I can find after researching *that* warning message is a small registry edit, which I have tried, and it did not help.
-In my research, I came across someone's theory that the problem is related to the SSL certificate, & the fact that the internal domain has a .local extension (which mine does). According to this theory, Microsoft's RDS Gateway (unfortunately) exposes the RDS Session host's computer name (including its .local extension) to the remote/external RDP client, and therefore the 60 second delay is caused by the remote/external RDP client taking time to look for the SSL certificate for the session host, which doesn't exist. The only way to determine whether this theory is the actual cause of the 60 second delay, or not, is to actually purchase a UC Certificate, which supports multiple domain names. There is an additional problem with testing this theory however, in that ICANN has mandated that certificates will no longer support .local (and similar) domain extensions come November, 2015. Therefore, even if I go through all the work to purchase & install the UC Certificate, *and* it happens to solve this 60 second login delay problem (which is a big "if"), that solution would only work for 1.5 more years from now.
I hope you can see I have tried hard to solve this problem on my own, but I am unable to. I really need some outside perspective to cut through the troubleshooting fog in my head regarding this particular problem. It is for that reason that any assistance with this problem would be greatly appreciated! Thank you in advance!
we have changed domain name.
Error below:
The Remote Desktop Session Host server could not contact the Remote Desktop license server RDP-SERVER-2008.olddomain.local. Ensure that the Remote Desktop Licensing service is running on the license server, that the license server is accepting network requests, and that the license server is registered in WINS and DNS.
I am receiving this error after adding this RDP-SERVER-2008 server to the new domain. All the licenses were installed and configured on this machine and it was all fine in the "olddomain.local"
Now in the new domain the machine is trying to contact it's old self. Any help as so far all the recommendations I've seen don't actually cover this scenario.
many thanks
Hi,
I wanted to know if it is possible to hide the Connect dialog box when you try to connect to a Remote Collection or App.
I remote to the server 2008. after I type the Username and Password, the server rdp is hang already. But I still can ping.
Then I go and reset at the server. It's happened so many times already. We still cannot solve. Pls help us. Thanks.
I have an RDG server named gw.domain.local with port 3389/tcp forwarded fromgw.example.com.
Using RDGM snap-in I created a self-signed SSL certigicate with FQDN gw.example.com.
But when I connect over RDP from outside the local network I'm getting an error:
Your computer can't connect to the computer because the Remote Desktop Gateway server address requested and the certificate name do not match
Because certificate subject name is gw.domain.local indeed.
So there question is: how to issue a certificate properly, or how to assign an existing one the name to match?
I have two TS server one for remote desktop and other for remote app. Recently I have client can't connect using RemoteApp.
The error show: The remote session was disconnected because there are no Remote Desktop License Servers available to provide a license. Please contact the server administrator.
I found few article about registery so I removed HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSLicensing key and restart, but it didn't helped.
I have a good connection to TS License server (2008 R2 Standard). RemoteApp server (2008R2 Enterprise) can ping TS license server and RD Session Host Configuration shows list of TS license server and showing available license, I only used 4 out 50. I installed RD License service on RemoteApp server and trying to connect TS license server, but it won't connect.
RD Session Host Configuration : licensing diagnosis show connection show
what is the problem????
Learn Everyday!
Here's the issue I am having.
My VPN is currently on a server 2003. I have installed it on my server 2008. I go into my sonicwall and changed the IP address from 192.168.0.11 (old VPN server) to the new IP 192.168.0.13 (new VPN server) and I am unable to connect to VPN.
However if I change the IP address of the new server to 192.168.0.11 I can connect via VPN just fine.
I'm not sure if it matters but my old VPN server is also a backup domain controller and DNS, the new server is just a file share server and has IIS enabled for our antivirus.
I've looked at every setting I can think of and I even called Sonicwall and they state everything looks good in my settings. Any help would be greatly appreciated in this!
Hi,
actually I have an issue in an Broker scenario on Windows 2008 R2.
Scenario: Windows 2008 R2 RDS
2 Session Hosts for RemoteApps and Desktop (No VD)
NLB configured for the a farm on 10.1.1.100 on both Session Hosts
Farmname = RDSFarm.xxxx.xxx
No WebAccess (IIS is installed on the Session Broker Server)
DNS Entry in place = 10.1.1.100 (nslookup works)
I moved the Session Broker from an an Domain Controller to an Member Server based on Windows 2008 R2.
I also renewed the farm certificate RDSFarm.xxx.xxx and configure it on all RDS Hosts to use this certificate.
Now the problem:
I cannot connect to my RDSFarm.xxx.xxx: Error (using Windows 7):
"The connection cannot be completed because the remote computer that was reached is not the one you specified. This could be caused by an outdated entry in the DNS cache. Try using the IP address of the computer instead of the name."
What I've checked (and double checked):
- RDS Session Hosts are in the local Group of the new Session Broker Host -> check
- Farm certificate in all required Settings on Broker and Session Hosts
- DNS Entries (Also tried with round robin and without)
- Farm Membership
- FlushDNS
- Trying to use IP - then there is a certificate warning that the computername 10.1.1.100 does not match the certificate named RDSFarm.xxx.xxx (Tis is what I expected) - and i got a connection.
I get no more error messages except that my RDP Client cannot connect. How can I find more connection information or how to troubleshoot this ? Do I miss something during the migration from a DC to a member server ? Can anyone gave me a hint ? :-)
Greetings
Tobias