Remote OS X Server administration

Good day,
I did today the OS Upgrade form OS X Mavericks to OS X Yosemite successfully.
After that I have to upgrade my OS X Server from Mavericks Server to 4.0. All Services (Calendar, Contact, Web and Wicki are up and running. I did also update OS X Server on my OS X Yosemite workstation to remote admin the server.
So but after the upgrade I cannot connect to the server remotely. "Allow remote administration using Server" is checked. I cannot see any hint in the System Log.
Is there anything I have to double check?
I did install a second server in VM (Fusion) to compare both server...Cannot find any different...Just that I can connect to my VM server remotely just fine. And the VM OS X Server was not an upgrade form Maverichs Server.
Where do I have to start debugging?
Thanks crazyx

Workaround posted by kirdes on this other thread (https://discussions.apple.com/message/26902374?ac_cid=tw123456) - the thing I was missing was rebooting the server (which I usually don't do as part of troubleshooting).
sudo security set-identity-preference -n -s com.apple.servermgrd /Library/Keychains/System.keychain
sudo security delete-certificate -c com.apple.servermgrd /Library/Keychains/System.keychain
+ reboot gets a non-expired self-signed certificate back and I can connect.

Similar Messages

Windows Server 2012 Used: Error Message from Windows 7 PC: Remote session was disconnected because there are no remote desktop license servers available to provide a license. Please contact the server administrator.

We are using Windows Server 2012 Standard installed in VMWare / Virtual machine and to access this we use vSphere client and Remote Desktop Connection / service was already enabled and was working fine with User PCs / laptops remote desktop into the server
2012, until it gave an error message of: Remote session was disconnected because there are no remote desktop license servers available to provide a license. Please contact the server administrator. whilst logging into the server.
We DON'T use Active Directory nor and we don't use domain and not looking to use it any-time soon.
I checked the RD Licensing Diagnoser and it says the grace period has expired and the licensing mode for the remote desktop session host server is not configured. I have checked the Remote Desktop Gateway has been stopped and I tried to start it and it
resumed to stop, here I assume its where the licensing part comes in to re-enabled this.
I have been trying to follow these articles online: http://ryanmangansitblog.com/2013/03/27/deploying-remote-desktop-gateway-rds-2012/ and http://www.concurrency.com/blog/rds8-add-a-licensing-server-2/#Install the overview part that I cannot get into,
because I think we have to be is AD DS for this which we don't. Is there a way around this for non domain / just standalone set-up? Is it a must / requirement we need to be in a domain in order for Remote Desktop Connection to work?
Also, we have a Windows Server 2012 RDS CALs - 10 (software and licence key), will the licence key work for the Windows 2012 Server Standard? We do not want to install the other Server mentioned which comes with CAL / licence key as its time consuming
to reinstall other programs. I have installed Server role service of Remote Desktop Licencing and automatically installed other associated services needed. in the RD Licencing Manager, the Server had a red cross and I "Activate Server"
where I followed: http://www.concurrency.com/blog/rds8-add-a-licensing-server-2/#Install in Install Licences section and I have used the licence key of CAL - 10 mentioned above; it stated I have successfully completed the install licences wizard and displayed:
10 Windows Server 2012 - RDS Per User CAL installed, and in the RD Licensing Manager the server turned into a green tick and added the licence.
I then tested the Remote desktop connection from my PC and the same error message was there and checked the RD Licensing Diagnoser and the same error messages was there. I haven't restart the services of Remote Gateway / the server itself; do I really
need to reboot server?
Any advice / guidance would be very much appreciated and this is a urgent matter.
Thank you for your time.

Hotfix Released here:
http://support.microsoft.com/kb/2916846

Upgrade to Windows 8.1 Pro from Windows 8 Pro causing issues with Remote Server Administration Tools

Last night I received the Windows 8.1 update and it has caused Remote Server Administration Tools to stop working. I tried to reinstall the tools using Windows8.1-KB2693643-x64.msu but get the following error:
Windows Update Standalone Installer
Installer encountered an error: 0x8007000d
The data is invalid.
In the event log I have the following error
Windows update could not be installed because of error 2147942413 "The data is invalid." (Command line: ""C:\WINDOWS\system32\wusa.exe" "C:\RSAT\Windows8.1-KB2693643-x64.msu" ")
System
Provider
[ Name]
Microsoft-Windows-WUSA
[ Guid]
{09608C12-C1DA-4104-A6FE-B959CF57560A}
EventID
3
Version
0
Level
2
Task
0
Opcode
0
Keywords
0x8000000000000000
TimeCreated
[ SystemTime]
2014-11-05T12:14:18.035865000Z
EventRecordID
1562
Correlation
Execution
[ ProcessID]
5224
[ ThreadID]
5132
Channel
Setup
Computer
removed
Security
[ UserID]
S-1-5-21-1644491937-764733703-854245398-1794
EventData
UpdateTitle
ErrorCode
2147942413
ErrorString
The data is invalid.
CommandLine
"C:\WINDOWS\system32\wusa.exe" "C:\RSAT\Windows8.1-KB2693643-x64.msu"
I did have the Remote Server Administration Tools installed previously when I was running windows 8 pro and everything was fine. I've tried to remove the older version but according to the below it isn't even installed and Remote Server Administration
Tools doesn't appear in Turn Windows features on or off.
c:\RSAT>dism /online /Get-Packages
Deployment Image Servicing and Management tool
Version: 6.3.9600.17031
Image Version: 6.3.9600.17031
Packages listing:
Package Identity : Microsoft-Windows-Client-LanguagePack-Package~31bf3856ad364e35~amd64~en-US~6.3.9600.16384
State : Installed
Release Type : Language Pack
Install Time : 24/09/2014 06:33
Package Identity : Microsoft-Windows-Embedded-EmbeddedLockdown-Package-TopLevel~31bf3856ad364e35~amd64~~7.3.9600.17116
State : Installed
Release Type : Update
Install Time : 24/09/2014 10:03
Package Identity : Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~6.3.9600.16384
State : Installed
Release Type : Foundation
Install Time : 22/08/2013 14:46
Package Identity : Package_for_KB2891214~31bf3856ad364e35~amd64~~6.3.1.0
State : Installed
Release Type : Update
Install Time : 05/11/2014 01:39
Package Identity : Package_for_KB2902816~31bf3856ad364e35~amd64~~6.3.1.0
State : Installed
Release Type : Update
Install Time : 05/11/2014 01:39
Package Identity : Package_for_KB2919355~31bf3856ad364e35~amd64~~6.3.1.14
State : Installed
Release Type : Update
Install Time : 24/09/2014 10:03
Package Identity : Package_for_KB2920189~31bf3856ad364e35~amd64~~6.3.1.1
State : Installed
Release Type : Security Update
Install Time : 24/09/2014 10:03
Package Identity : Package_for_KB2931358~31bf3856ad364e35~amd64~~6.3.1.2
State : Installed
Release Type : Security Update
Install Time : 24/09/2014 10:03
Package Identity : Package_for_KB2931366~31bf3856ad364e35~amd64~~6.3.1.4
State : Installed
Release Type : Security Update
Install Time : 24/09/2014 10:03
Package Identity : Package_for_KB2932046~31bf3856ad364e35~amd64~~6.3.1.5
State : Installed
Release Type : Feature Pack
Install Time : 24/09/2014 10:03
Package Identity : Package_for_KB2934018~31bf3856ad364e35~amd64~~6.3.1.5
State : Installed
Release Type : Feature Pack
Install Time : 24/09/2014 10:03
Package Identity : Package_for_KB2937220~31bf3856ad364e35~amd64~~6.3.1.0
State : Installed
Release Type : Update
Install Time : 24/09/2014 10:03
Package Identity : Package_for_KB2937592~31bf3856ad364e35~amd64~~6.3.1.0
State : Installed
Release Type : Feature Pack
Install Time : 24/09/2014 10:03
Package Identity : Package_for_KB2938439~31bf3856ad364e35~amd64~~6.3.1.0
State : Installed
Release Type : Feature Pack
Install Time : 24/09/2014 10:03
Package Identity : Package_for_KB2938772~31bf3856ad364e35~amd64~~6.3.1.0
State : Installed
Release Type : Update
Install Time : 24/09/2014 10:03
Package Identity : Package_for_KB2939153~31bf3856ad364e35~amd64~~6.3.1.1
State : Installed
Release Type : Update
Install Time : 24/09/2014 10:03
Package Identity : Package_for_KB2939576~31bf3856ad364e35~amd64~~6.3.1.1
State : Installed
Release Type : Security Update
Install Time : 24/09/2014 10:03
Package Identity : Package_for_KB2949621~31bf3856ad364e35~amd64~~6.3.2.0
State : Installed
Release Type : Hotfix
Install Time : 24/09/2014 10:03
Package Identity : Package_for_KB2950153~31bf3856ad364e35~amd64~~6.3.1.0
State : Installed
Release Type : Update
Install Time : 24/09/2014 10:03
Package Identity : Package_for_KB2954879~31bf3856ad364e35~amd64~~6.3.2.0
State : Installed
Release Type : Update
Install Time : 24/09/2014 10:03
Package Identity : Package_for_KB2955164~31bf3856ad364e35~amd64~~6.3.1.3
State : Installed
Release Type : Update
Install Time : 24/09/2014 10:03
Package Identity : Package_for_KB2956575~31bf3856ad364e35~amd64~~6.3.1.3
State : Installed
Release Type : Update
Install Time : 24/09/2014 10:03
Package Identity : Package_for_KB2958262~31bf3856ad364e35~amd64~~6.3.1.2
State : Installed
Release Type : Update
Install Time : 24/09/2014 10:03
Package Identity : Package_for_KB2958263~31bf3856ad364e35~amd64~~6.3.1.2
State : Installed
Release Type : Update
Install Time : 24/09/2014 10:03
Package Identity : Package_for_KB2959626~31bf3856ad364e35~amd64~~6.3.3.0
State : Installed
Release Type : Update
Install Time : 24/09/2014 10:03
Package Identity : Package_for_KB2959977~31bf3856ad364e35~amd64~~6.3.1.1
State : Installed
Release Type : Update
Install Time : 24/09/2014 10:03
Package Identity : Package_for_KB2961072~31bf3856ad364e35~amd64~~6.3.1.1
State : Installed
Release Type : Security Update
Install Time : 24/09/2014 10:03
Package Identity : Package_for_KB2962140~31bf3856ad364e35~amd64~~6.3.1.0
State : Installed
Release Type : Update
Install Time : 24/09/2014 10:03
Package Identity : Package_for_KB2962872~31bf3856ad364e35~amd64~~6.3.1.4
State : Installed
Release Type : Security Update
Install Time : 24/09/2014 10:03
Package Identity : Package_for_KB2964718~31bf3856ad364e35~amd64~~6.3.1.0
State : Installed
Release Type : Security Update
Install Time : 24/09/2014 10:03
Package Identity : Package_for_KB2965142~31bf3856ad364e35~amd64~~6.3.1.0
State : Installed
Release Type : Update
Install Time : 24/09/2014 10:03
Package Identity : Package_for_KB2965500~31bf3856ad364e35~amd64~~6.3.1.0
State : Installed
Release Type : Update
Install Time : 24/09/2014 10:03
Package Identity : Package_for_KB2966407~31bf3856ad364e35~amd64~~6.3.1.0
State : Installed
Release Type : Update
Install Time : 24/09/2014 10:03
Package Identity : Package_for_KB2966870~31bf3856ad364e35~amd64~~6.3.1.4
State : Installed
Release Type : Update
Install Time : 24/09/2014 10:03
Package Identity : Package_for_KB2967162~31bf3856ad364e35~amd64~~6.3.1.1
State : Installed
Release Type : Update
Install Time : 24/09/2014 10:03
Package Identity : Package_for_KB2968296~31bf3856ad364e35~amd64~~6.3.1.0
State : Installed
Release Type : Security Update
Install Time : 04/11/2014 17:56
Package Identity : Package_for_KB2968599~31bf3856ad364e35~amd64~~6.3.1.1
State : Installed
Release Type : Update
Install Time : 24/09/2014 10:03
Package Identity : Package_for_KB2969817~31bf3856ad364e35~amd64~~6.3.1.0
State : Installed
Release Type : Update
Install Time : 24/09/2014 10:03
Package Identity : Package_for_KB2971203~31bf3856ad364e35~amd64~~6.3.1.1
State : Installed
Release Type : Update
Install Time : 24/09/2014 10:03
Package Identity : Package_for_KB2971850~31bf3856ad364e35~amd64~~6.3.1.2
State : Installed
Release Type : Security Update
Install Time : 24/09/2014 10:03
Package Identity : Package_for_KB2972103~31bf3856ad364e35~amd64~~6.3.2.0
State : Installed
Release Type : Security Update
Install Time : 04/11/2014 17:56
Package Identity : Package_for_KB2972280~31bf3856ad364e35~amd64~~6.3.1.1
State : Installed
Release Type : Security Update
Install Time : 24/09/2014 10:03
Package Identity : Package_for_KB2973201~31bf3856ad364e35~amd64~~6.3.1.3
State : Installed
Release Type : Security Update
Install Time : 24/09/2014 10:03
Package Identity : Package_for_KB2973351~31bf3856ad364e35~amd64~~6.3.2.0
State : Installed
Release Type : Security Update
Install Time : 24/09/2014 10:03
Package Identity : Package_for_KB2974008~31bf3856ad364e35~amd64~~6.3.1.0
State : Installed
Release Type : Update
Install Time : 24/09/2014 10:03
Package Identity : Package_for_KB2975061~31bf3856ad364e35~amd64~~6.3.1.0
State : Installed
Release Type : Update
Install Time : 24/09/2014 07:11
Package Identity : Package_for_KB2975719~31bf3856ad364e35~amd64~~6.3.1.8
State : Installed
Release Type : Update
Install Time : 24/09/2014 10:03
Package Identity : Package_for_KB2976978~31bf3856ad364e35~amd64~~6.3.2.1
State : Installed
Release Type : Update
Install Time : 24/09/2014 10:03
Package Identity : Package_for_KB2977292~31bf3856ad364e35~amd64~~6.3.1.0
State : Installed
Release Type : Security Update
Install Time : 04/11/2014 17:56
Package Identity : Package_for_KB2978041~31bf3856ad364e35~amd64~~6.3.1.0
State : Installed
Release Type : Security Update
Install Time : 04/11/2014 17:56
Package Identity : Package_for_KB2979573~31bf3856ad364e35~amd64~~6.3.1.1
State : Installed
Release Type : Security Update
Install Time : 04/11/2014 17:56
Package Identity : Package_for_KB2979576~31bf3856ad364e35~amd64~~6.3.1.1
State : Installed
Release Type : Security Update
Install Time : 04/11/2014 17:56
Package Identity : Package_for_KB2979582~31bf3856ad364e35~amd64~~6.3.1.0
State : Installed
Release Type : Update
Install Time : 24/09/2014 10:03
Package Identity : Package_for_KB2980654~31bf3856ad364e35~amd64~~6.3.1.2
State : Installed
Release Type : Update
Install Time : 24/09/2014 10:03
Package Identity : Package_for_KB2987107~31bf3856ad364e35~amd64~~6.3.1.4
State : Installed
Release Type : Security Update
Install Time : 04/11/2014 17:56
Package Identity : Package_for_KB2989542~31bf3856ad364e35~amd64~~6.3.1.2
State : Installed
Release Type : Update
Install Time : 04/11/2014 17:56
Package Identity : Package_for_KB2990532~31bf3856ad364e35~amd64~~6.3.1.0
State : Installed
Release Type : Update
Install Time : 24/09/2014 10:03
Package Identity : Package_for_KB2993651~31bf3856ad364e35~amd64~~6.3.1.2
State : Installed
Release Type : Update
Install Time : 24/09/2014 10:03
Package Identity : Package_for_KB2998174~31bf3856ad364e35~amd64~~6.3.1.0
State : Installed
Release Type : Update
Install Time : 04/11/2014 17:56
Package Identity : Package_for_KB3000061~31bf3856ad364e35~amd64~~6.3.1.2
State : Installed
Release Type : Security Update
Install Time : 04/11/2014 17:56
Package Identity : Package_for_KB3000869~31bf3856ad364e35~amd64~~6.3.1.0
State : Installed
Release Type : Security Update
Install Time : 04/11/2014 17:56
Package Identity : Package_for_KB3000988~31bf3856ad364e35~amd64~~6.3.1.0
State : Installed
Release Type : Update
Install Time : 04/11/2014 17:56
The operation completed successfully.
Any help on this issue would be appreciated, if you need any further information please let me know.
Thanks

SeniorInternet,
I’ve seen this issue in the past and it occurred because the file was corrupted.
It’s possible that something went wrong when downloading it originally on your newly upgraded machine.
Try downloading
KB2693643 again from another machine and install it.
Hope this helps!
Mike
Windows Outreach Team – IT Pro
Windows for IT Pros on TechNet

Unable to install Remote Server Administration Tools for Windows 8 Release Preview on RTM 8 Enterprise

Unable to install Remote Server Administration Tools for Windows 8 Release Preview on RTM 8 Enterprise
Standalone installer available here
http://www.microsoft.com/en-us/download/details.aspx?id=28972
fails with error code 0x80004005
Is this because my installation has issues, or would the admin pack files be updated for RTM?
Thank you in advance for any insight

Found the solution here:
http://social.technet.microsoft.com/Forums/en-US/w8itprogeneral/thread/6d8745e0-c4c1-463a-b4bb-09f6c9c22527
Workaround:
Download the RSAT package intended for Windows 8 Release Preview: http://www.microsoft.com/en-us/download/details.aspx?id=28972
Extract the .msu file with a tool such as 7-Zip.
Open an Admin command prompt and change directory to where you extracted the .msu.
Run the following command to install (if x86 you probably have a different .xml filename): pkgmgr /n:Windows6.2-KB2693643-x64.xml
Wait a while. You can look in task manager for pkgmgr. When it disappears, the installation is done.
Use the tools as per usual.

Failure in Installing Remote Server Administration Tools on Windows 8.0

I have recently download
Remote Server Administration Tools (64 bit) for Windows 8,but unfortunately I couldn't Installed it & an error message appeared on the screen after I tried to
Install the tools, saying; "The update is not applicable to your computer".
Then I followed the instructions available on the same page, but there in Turn windows feature
on or off's list in the Control panel, the
Remote Server Administration Tools option is not available. After that I have updated the OS completely, from Windows update option on the Control panel, but the problem is still exist. So therefore I need help regarding this matter in order to solve
this unexpected problem, that I am currently facing.
Thank you .
Abdur Rahman

if youre using win 8.1 you have to install this one
http://www.microsoft.com/en-us/download/details.aspx?id=39296
Darshana Jayathilake

Can't enable Remote Server Administration Tools

I have seen many people around the net having what seems to be this issue, but there are a few nuances that differ in my particular situation.
I have 2 'Windows 7 Sp1' machines on an AD domain. Functional level is 2003.
I downloaded and installed "Windows6.1-KB958830-x64-RefreshPkg.msu" on both PCs and the installation seemed to finish without errors, but when I go to enable the features it throws the error: "An error occurred, not all the features were successfully
changed."
I came across a solution that claimed I needed to reinstall the KB, I did so to no avail. I thought perhaps my download might be corrupt, so on the 2nd machine I downloaded directly to that PC, but got the same behavior.
I doubt that it is Group Policy related, because other machines (although they're XP) are in the same OUs as these machines and can run the admin tools. <Users are members of a Help Desk & frequently reset certain users' passwords.>
I'm not sure what to do next, especially since both of these computers are acting the same way.
# When I wrote this script only God & I knew what I was doing. # Now, only God Knows!
Don't retire technet
http://social.technet.microsoft.com/Forums/en-US/e5d501af-d4ea-4c0f-97c0-dfcef0192888/dont-retire-technet?forum=tnfeedback

Hi,
Please go to event log to check more information about this operation, you could find something under Windows Logs---Setup log.
According to your description, I suspect there would be some common issue existed in your both Windows 7 computers. Just boot into clean boot mode to check if you can turn on Remote Server Administration Tools components. This will avoid the software conflicts
during configuration.
If you have any feedback on our support, please click
here
Alex Zhao
TechNet Community Support

DHCPMGMT.MSC in Remote Server Administration Tools (RSAT) won't remember DHCP server

I'm running Remote Server Administration Tools (RSAT) on Windows 7 Professional 64-bit and I've noticed that when I run the DHCP Management tool (DHCPMGMT.MSC) and I add our DHCP Authorised server then close the console, it forgets the DHCP server and I
have to re-select it next time I use the console.
On the other hand, the DNS console remembers that I've used a particular DNS server even after I close the console.
Wondering why the DHCP Management console is so forgetful?

Where there's a will there's a way. Here's what I did because it annoyed me so much to have to re-add the server each time.
1. Open the DHCP Managment console in author mode using the following command:
mmc /a c:\windows\system32\dhcpmgmt.msc
2. Add the server(s) you want to see
3. Click File > Save As...
4. Save the .msc console in the c:\windows\system32\ folder with a unique name like dhcpmgmt2.msc (don't use the old name: dhcpmgmt.msc)
5. Edit your adminstrative menu shortcut by:
       a. Browsing to Control Panel >
Administrative Tools (you may have to change the view to small icons to see all items).
       b. Right click on DHCP > Choose
Properties
       c. Change the Target to:
%windir%\system32\dhcpmgmt2.msc
(be sure you point it at whatever you named the new DHCP console my example was dhcpmgmt2.msc)
Cheers-
Josh

Remote Server Administration Tools for Windows 10 Technical Preview Not installing

When i try and install the remote server administration tools for windows 10 on my windows 10 technical preview install i get this error
Any ideas why this is happening? when i'm installing the correct version for windows 10
http://www.microsoft.com/en-us/download/details.aspx?id=44280

On Thu, 12 Feb 2015 07:33:29 +0000, samfty wrote:
Any ideas why this is happening? when i'm installing the correct version for windows 10
If you're running 9926 then you're not installing the correct version. If
you expand the Details section you'll see that version was published last
October. You'll need this one, which was published in at the end of
January:
http://www.microsoft.com/en-us/download/details.aspx?id=45520
Paul Adare - FIM CM MVP
Q. How do you solve bus problems?
A. Shoot the driver.

Unable to create a clustered VM using Remote Server Administration Tools - Failover Cluster Manager

Hi
I am using two Hyper-V Server 2012 R2 and a single WS2012 Datacenter Edition with GUI Interface for management purpose.
I have installed Failover Clustering feature on these two Hyper-V servers and remote server administration tools for Failover Clustering on WS2012 DC Edition with GUI.
I have created cluster using powershell cmdlets on Hyper-V server because I was unable to create a cluster using RSAT-Failover Clustering (May be some privileges issues).
The problem is " I am still not able to create a Hyper-VM using Failover Cluster Manager on WS2012 DC Edition server". It gives me an error "Invalid operation"
Any Help regarding this issue will be very appreciated.
Thanks in Advance.....
Abhinav | MCTS-Server Virtualization

Thanks Tim for your response but atleast I should be able to create and configure VMs for high availability.
I think this is not the issue which I am facing. It gives me an error "invalid class". There is something missing.
Please check and let me know if it can be solved. Any help will be really appreciated.
Thanks in advance.
Abhinav | MCTS-Server Virtualization

Remote session was disconnected because there are no remote desktop license servers available to provide a license. Please contact the server administrator."

I am the Server Administrator and have server 2012 Standard running on a single computer for our small (50 employee) company. It's primary role is to house one software application that manages our data. Our employees need to remotely access this
server to use this software program. For the last 4 months we have successfully done that using Remote Desktop.
Unfortunately our RDS trial period ran out on our Server, and so I have recently installed 21 RDS User CALs on to the server to still be able to access this server remotely. When I installed them, using the Install Wizard, I selected 'User CALs' as that
is what they are. However, when I try to use remote desktop and access the server remotely, I get the message: "remote session was disconnected because there are no remote desktop license servers available to provide a license"
Do I have to install the RDS User CALs as Device CALs instead even though they are USER CALs?? Did I forget to check a box or something? Please help! We are a Non-Profit and really can't afford Microsoft's $260 support fee when I have a feeling
this has got to be an easy solution.

Hi,
1. Did you create an RDS deployment or just install the RD Session Host and RD Licensing Role Services on your server?
2. If yes to #1, have you set the licensing mode and licensing server name in Server Manager -- RDS -- Overview -- Tasks -- Edit Deployment Properties -- RD Licensing tab? Did you make your RDSH server part of a collection? The RDSH server must
be part of a collection in order for the deployment settings to apply.
3. If no to #1, then please set the licensing mode/specify the licensing server name via group policy setting. For example, you could use gpedit.msc and configure the following settings:
Computer Configuration\ Administrative Templates\ Windows Components\ Remote Desktop Services\ Remote Desktop Session Host\ Licensing
Use the specified Remote Desktop licensing servers
Set the Remote Desktop licensing mode
Thanks.
-TP

Remote Server Administration Tools Win7 to Svr20212R2

Can be done, and works. Functionality is reduced, however. See—http://community.spiceworks.com/topic/439904-windows-7-remote-server-administration-toolkit-rsat

I was wondering, is it possible to use Remote Server Administration Tools to access a server running Windows Server 2012 R2 on Windows 7 Pro? Last I heard it was NOT possible. If not, is there anyway to do it another way other than RD? I would like to administer my server from my computer rather than using the KVM or RD. Thanks!
This topic first appeared in the Spiceworks Community

Error "The remote connection was disconnected because there are no Remote Desktop License Servers available to provide a license. Please contact the server administrator"

Hi,
I have been using Windows server 2012 at my company and generally take a remote access to this server. However, since last few days, I have been receiving the Error "The remote connection was disconnected because there are no Remote Desktop License
Servers available to provide a license. Please contact the server administrator".
My entire work has come to a halt because of this error as all my applications are running this server and their remote access is needed for my regular requirements.
I had tried one of the solutions proposed at one of these forums especially using gpedit.msc but to no avail.
Regards,
Aditya

Hi Aditya,
Thank you for posting in Windows Server Forum.
Agree with the words of armin, please verify that you have properly installed correctly. Verify RDS Licensing service running on License Server. Verify that the client, the RDS server, and the license server can communicate by ensuring that Domain Name System
(DNS) is configured correctly on each computer. You can run the ping command from each computer to each computer using the IP address, FQDN, and the NetBIOS name. If any of the ping commands fail, verify the DNS configuration on the network.
In addition, you can also try “GracePeriod” registry setting on this path (HKLM\System\CurrentControlSet\Control\Terminal Server\RCM) from
this article.
Hope it helps!
Thanks.
Dharmesh Solanki

Remote session was disconnected because there are no remote desktop licence servers available to provide a licence. Please contact the server administrator

Hi,
I am getting this error from windows server : remote session was disconnected because there are no remote desktop licence servers available to provide a licence. Please contact the server administrator.
Remote desktop Session Host Server Configuration Details:
The RD licensing Diagnoser(WIN-909xxxxxxxxxxx):
Number of license available for clients : 0
Remote Desktop Session Host server version: Windows server 2012 R2
Active Directory Domain : Not applicable
Licensing mode : Not configured
Now, Down I am getting this error as well shown by the system:
RD licensing Diagnoser Information- 2 errors:
Win-909xxxxxxxxxx : licensing mode for the Remode Desktop Session Host Server is not configured.
Win-909xxxxxxxxxx : The grace period for the Remote Desktop Session Host server has Expired, but the RD Session Host server has not been configured with any license servers. connections to the RD Session Host server will be denied
unless a license server is configured for the RD Session Host server.
Now my kestion is :
Do I need to buy a license key of the windows server to not getting this error or it may continue appear even if I purchased the license and not configure RDS and AD.
Do I need to configured only RDS and AD and buy the license key of windows server later because I still have 55 day of trial.
Do I just buy the RDS client access license (L).
Please could you help on this, am new in windows server?

Hi,
As the message indicates, the grace period for the Remote Desktop Session Host server has Expired, you need to purchase and install RDS CALs. Also, you need to configure related settings
to continue using Remote Desktop Services. Otherwise, you cannot connect to the server remotely.
References:
Understand the licensing grace period
http://technet.microsoft.com/en-us/library/hh553157(v=ws.10).aspx
Install and issue RDS CALs or TS CALs
http://technet.microsoft.com/en-us/library/hh553159(v=ws.10).aspx
Remote Desktop Services Client Access Licenses (RDS CALs)
http://technet.microsoft.com/en-us/library/cc753650.aspx
Specify the Remote Desktop Licensing Mode on an RD Session Host Server
http://technet.microsoft.com/en-us/library/cc754487.aspx
Specify a License Server for an RD Session Host Server to Use
http://technet.microsoft.com/en-us/library/cc770585.aspx
Meanwhile,
1. AD is not required for RDS. However, it is recommended.
2. As you do not purchase Windows Server and related licenses as well, I suggest you contacting Microsoft sales or partner firstly.
How to buy Windows Server 2012 R2
http://www.microsoft.com/en-us/server-cloud/products/windows-server-2012-r2/buy.aspx
Best Regards.
Jeremy Wu
TechNet Community Support

How do I change the URL to the Remote Web Access server in Windows Server 2012?

Hallo!
I have set up a Remote Dexktop Service using the "Quick" deployment method in Server Manager and everything is working greate internally, but I cannot start an app published in Remote Web Access from outside our network.
The problem is that it wants to start the using the internal URL, for example, server.domain.local, instead of the external one, for example remote.server.com.
I therefore want to know how I can change the default URL for the Remote Web Access server and all the Remote Web Apps in Windows Server 2012?
I have allready looked in Server Manager and I can change some of the deployment settings in server manager, but there is no way to alter the URL of the Remote Web Access server. See below images:
Pressing the internal URL only results in opening the internal URL.
This was very simple to do in Windows Server 2008 R2 using the tsconfig tool, but it does not seam to be any way of solving this in server manager.
A possible sollution would be to alter the registry someware in HKLM->Software->Microsoft->Windows NT->Terminal Services. But this can easaly lead to problems due to wrong format, etc. and is probably not supported.
Is there a simpler and supported way?

That option can be used to connect to any machine that you want. The error message indicates that the client machine cannot resolve the name "server.domain.local" to an IP address that it can connect to.
You have several options for configuring that tab on the RDweb site. You can even remove it entirely.
Customization of RD Web Site
RD Web provides a number of customization options for the RD Web interface, including the ability to control default Gateway server settings and redirection settings. These settings
are controlled by editing the web.config file located in %SYSTEMROOT%\Web\RDWeb\Pages.
Displaying Local Help
To display local help for users instead of the web-based help, edit the LocalHelp value and change the value from false to true.

<add key="LocalHelp" value="false" />
When this value is changed, a user that clicks on Help in the upper right corner of the RD Web login page will open the local help file instead of web-based help.
Hiding the Connect to a Remote PC Tab
The RDWeb page
Connect to a Remote PC tab can be hidden from users to prevent connections to any servers through RD Web other than the servers configured in a collection. By default, this setting is set to true and the
Remote Desktops tab is displayed. To hide the tab, set the value to false.

<add key="ShowDesktops" value="true" />
When the value is set to false, a user will not see the Connect to a Remote PC tab when logged on to the RD Web page
RD Gateway Settings
If the Connect to a Remote PC tab is enabled, an administrator can configure RD Web to use a Gateway server when connecting to remote computers. To specify a gateway, edit the below
value with the name of the RD Gateway server:

<add key="DefaultTSGateway" value="" />
The default authentication method for the RD Gateway server can also be configured by editing the following section of the web.config:

<add key="GatewayCredentialsSource" value="0" />
Devices and Resources
By default, only Printers and Clipboard are redirected on connections made using the Connect to a Remote PC tab. If the user clicks the
Options << button, the redirection settings for a specific connection can be modified
To configure each specified redirection option to be enabled or disabled by default, edit the following section in the web.config file:

<add key="xPrinterRedirection" value="true" />
<add key="xClipboard" value="true" />
<add key="xDriveRedirection" value="false" />
<add key="xPnPRedirection" value="false" />
<add key="xPortRedirection" value="false" />
LAN Experience Defaults
Windows Server 2012 RD Web Access can display a new user selectable option for optimizing the connection for a LAN experience. This option is displayed at the bottom of the RD Web
page and can be controlled by the administrator using the following section of the web.config file:

<add key="ShowOptimizeExperience" value="false" />
<add key="OptimizeExperienceState" value="false" />
This value is set to false by default, but when changed to true, the following checkbox will display at the bottom of the webpage. The LAN experience
checkbox can also be set as enabled by default.
Each setting can also be modified using the IIS Manager user interface:
Don Geddes - SR Support Escalation Engineer - Remote Desktop Services - Printing and Imaging

Android MS RDP - RPC Error: Your connection was denied because of a Resource Access Policy (TS_RAP). Please contact your server administrator. (2147965402).

I love iTap Mobile. Paid for the app. Sorry to see them discontinue it, but now I know why. Microsoft bought them out! But even though free, I am getting an error: RPC Error: Your connection was denied because of a Resource Access
Policy (TS_RAP). Please contact your server administrator. (2147965402). I worked with iTap to fix this so I guess they sold Microsoft their older buggy code... Microsoft, please fix!
PS: This is the Android version. Mac and iOS are both okay.
EDIT: After an update a few months ago, iOS is no longer working. Not sure if the problem is related to the Android MSRDP issue.
UPDATE - Relevant posts (need Android RDP software engineer to fix):
Event Viewer Log when using Android client:
The user
"DOMAIN\testuser", on client computer "10.x.x.x", met connection authorization policy requirements and was therefore authorized to access the RD Gateway server. The following authentication method was used: "NTLM". (This
is most likely for logging into RD Web - icons shows up).
The
user "DOMAIN\testuser", on client computer "10.x.x.x", did not meet resource authorization policy requirements and was therefore not authorized to resource"localhost".
The following error occurred: "23002". (This is after clicking on any
of the icons).
I
think the Android MS RDP client is providing the incorrect resource. It shouldn't be "localhost".
It should be the RD Connection Broker's hostname, I believe.
Here's what it should look like (connected using a Windows PC going
through the RD Web portal via Internet Explorer):
The user "DOMAIN\testuser", on client computer "10.x.x.x", met connection
authorization policy requirements and was therefore authorized to access the RD Gateway server. The following authentication method was used: "NTLM".
The user "DOMAIN\testuser", on client computer "10.x.x.x", met resource
authorization policy requirements and was therefore authorized to connect to resource "rdsfarm.domain.com".
The user "DOMAIN\testuser", on client computer "10.x.x.x", connected
to resource "rdsfarm.domain.com".
Stephan,
Do you have any way to contact the software engineer who worked on the Android version of the RDP client? Please
have them read this thread. They need to fix the hard coded "localhost" resource to be a variable (namely whatever the user put in for the server).
This is why the MS RDP app is failing in situations where the FQDN for the RD Gateway and Connection Broker uses
the same host name.
Again, this is not a configuration problem on our end as it works as intended with the native Windows RDP client
as well as the Mac and iOS version of the mobile RDP client (all based on iTap Mobile's RDP app).
This is a problem specific to the Android RDP app.
PS: No matter how hard I try, the WYSIWYG editor is not very WYSIWYG at all, and so everything here looks messed up even though it looked right when I posted it (it is deleting new blank lines I'm inserting to make it spaced out and easier to read). See
below to read the post in context.

Thanks for the bumps, everyone. I haven't check this thread in a while because I basically gave up on Microsoft's ability to respond. Unlike paid apps, there's no number to call or ticket to open when an app like this malfunctions.
Just to give you an update, iOS users started having issues connecting a few months ago. I don't remember what version started this. I'm not sure if it's the same problem.
Also, the newest version now gives a slightly different error message: RpcOverHttpEndpointException: 2, Your connection was denied because of a Resource Access Policy (TS_RAP). Please contact your server administrator.
For Android users, I am starting to recommend Xtralogic Remote Desktop Client. It's a paid app, but it works great. I don't know of any alternative for iOS.
MSRDP for Mac OSX (was also an iTap application) continues to work throughout the many updates.
We need a software engineer from MS to read my first post. All the information that will point to a fix is there. I strongly believe someone hardcoded the string "localhost" instead of using a variable to point to the FQDN of the rdsfarm
name.
Here's that info again (copied/pasted). It doesn't take an engineer to understand the issue. If you know how to decipher Event Logs, you can see where the problem is.
Event
Viewer Log when using Android client:
The
user "DOMAIN\testuser", on client computer "10.x.x.x", met connection authorization policy requirements and was therefore authorized to access the RD Gateway server. The following authentication method was used: "NTLM". (This
is most likely for logging into RD Web - icons shows up).
The
user "DOMAIN\testuser", on client computer "10.x.x.x", did not meet resource authorization policy requirements and was therefore not authorized to resource"localhost".
The following error occurred: "23002". (This
is after clicking on any of the icons).
I
think the Android MS RDP client is providing the incorrect resource. It shouldn't be "localhost".
It should be the RD Connection Broker's hostname, I believe.
Here's
what it should look like (connected using a Windows PC going through the RD Web portal via Internet Explorer):
The user "DOMAIN\testuser", on client computer "10.x.x.x",
met connection authorization policy requirements and was therefore authorized to access the RD Gateway server. The following authentication method was used: "NTLM".
The user "DOMAIN\testuser", on client computer "10.x.x.x",
met resource authorization policy requirements and was therefore authorized to connect to resource "rdsfarm.domain.com".
The user "DOMAIN\testuser", on client computer "10.x.x.x",
connected to resource "rdsfarm.domain.com".

Remote OS X Server administration

Similar Messages

Maybe you are looking for