Windows CE Programming » Blog Archive » Windows Server 2. RDS and Windows Mobile: connection error.

1. The International Space Station (ISS) might be the perfect laboratory for developing antidotes to gases used in chemical warfare. Nerve agents such as sarin and VX.
2. Let me begin by saying, I am aware of this thread and others around the web that seek to trouble shoot this issue. The solutions posted there do not apply to my issue.
3. Free downloads, tools, how-to guides, best practices, and community forums to help you upgrade, deploy, manage, and support Windows devices and PCs.

InformationWeek.com: News, analysis and research for business technology professionals, plus peer-to-peer knowledge sharing. Engage with our community.

For whatever reason MS decided to make Windows 2. RDS (former Terminal Services, now Remote Desktop Services) not compatible with Windows Mobile 6.

Windows CE 5. 0 based handheld devices. Fortunately, if you activated Remote Desktop License Server using . Check if you activate the Licensing server via “Web Browser” connection or directly. My 2. 00. 8 R2 server is running OK for Windows Mobile, as a stand- alone server, with 1. Web Browser”. But let start at the beginning. Basic RDS setup. When you installed Windows 2.

Exchange 2010 Mailbox Database Backup and Restore with Windows Server Backup.

Server within an existing or new Active Directory and then add the Remote Desktop Server role, you have different choices: You may go on with “Remote Desktop Services scenario- based installation” and then just follow the wizard after selecting “Quick Start”. The wizard will install everything onto one server. Virtual Desktop Infrastructure makes no sense for Windows Mobile clients. They do not need a full virtual windows machine based on a virtual machine. So we select “Session Virtualization”.

The wizard will then deploy all the services and roles and create one default “Session Collection” and “Remote Apps”. At the end you should get following screen: Now check the setup and look at the RDS Overview: You see we have RD Web Access (unused by Windows Mobile but cannot be removed), no RD Gateway (not needed here), no RD Licensing (we will install that later), the RD Connection Broker, no RD Virtualization Host (as we do not provide virtual machines here) and a RD Session Host with a Quick. Session Collection. At this stage we can not connect using Windows Mobile client. The NLA setting dis- allows that and we get an error in Remote Desktop Mobile. Just change the NLA setting of the Collection and your Windows Mobile clients can connect.

You can access the above Properties using the TASKS menu of Remote Desktop Services- Collections- Collection. Name and selecting “Edit Properties”.

If there is no Collection, we can not change the setting! Windows Desktop PCs can connect to that RDS without a Collection installed. We (Windows Mobile client) need a collection to disable NLA.

Setup Remote Desktop License Server. Now setup a Remote Desktop License server, activate it (or better read my later note about the activation method: see “RD License Server Activation Connection Method”) and install some CALs or DALs (licenses per User or Device).

Ensure the License Manager shows your License Server without any error. And also check with RD License Diagnoser! The licensing mode must match the general Collections properties setting: If everything is in place and activated and licensed Windows Mobile Clients can no longer connect! The certificates generated by the License Server are not compatible with Remote Desktop Mobile. They use 4. 09. 6 bit key- length and SHA2.

The certificates are stored in the registry at . Extracted and converted these certs look like this: Certificate.

Version: 3 (0x. 2). Serial Number. 0b: 1c: 0. Signature Algorithm: sha. With. RSAEncryption. Issuer: C=US, ST=Washington, L=Redmond, O=Microsoft Corporation, CN=Microsoft Assurance Designation Root 2. Validity. Not Before: Mar 2.

GMT. Not After : Mar 2. The Colour Out Of Space Pdf Documents. GMT. Subject: C=US, ST=Washington, L=Redmond, O=Microsoft Corporation, CN=Microsoft Assurance Designation Root 2.

Subject Public Key Info. Public Key Algorithm: rsa. Encryption. Public- Key: (4. Modulus. 0. 0: a. In RD Licensing Manager right- click the server name and select Properties.

Change the Connection Method to “Web Browser”. Close Properties with OK and again right click the server and then Advanced- Reactivate. Follow the process to reactivate the server using the web browser.

After reactivation delete the following registry keys and reboot the server! HKEY. RDM will not connect, if SHA2.

RDM does not support NLA nor SSL/TLS! What MS says. RDS 2. R2, and 2. 01. 2 will not allow connections from older RDP 5. Possibly they mean, does not support 4. Use. 51. 2Len. Prop.

Cert?). Test your installation. If you like to check the certificates of your installation you may use the attached demo application: “RDS2. It will just read the registry and show the certificates data. The code (included in the attachment) just reads the registry and extracts the certification data. The data is stored binary with some extra data at the beginning.

There are twelve bytes to remove to get the raw certificate (all these certs start with 0x. So the reg might look like this.