Skip to main content

Windows Server 2008 R2 - Remote Desktop Services

If you're looking for a Terminal Services procedure, you're in the right place. The Terminal Services name was changed to Remote Desktop Services. I like it, it is more user friendly name to use. The video link I provided here is a step by step instructions to install the Terminal Services http://www.youtube.com/watch?v=x_0oeiCTTfU. This is a detailed instructions to follow installing Terminal Services for Windows Server 2008.

Please note, I used Windows Server 2008 R2 Data Center to write this procedures for Remote Desktop Services. Though, very close configuration for Terminal Services.

Let's begin.

  1. Right click on your Windows Server, and click on Manage.
  2. In Add Roles, put check on Remote Desktop Services, Network Policy and Access Services, and Web Server (IIS). Click Next.
  3. In Role services, put check on Remote Desktop Session Host, Remote Desktop Connection Broker, Remote Desktop Gateway, and Remote Desktop Web Access. Click Next.
  4. Specify whether Network Level Authentication is required, select "Do not require Network Level Authentication", click Next.
  5. Select Configure later, click Next.
  6. In Users or User Groups, add the group you want to connect to this RD Session Host server. In Active Directory (AD), create a group name "GRP Remote Access". You will use this to assign permission for your users. Click Add, Advance, it will prompt you to enter your AD username and password, e.g. Administrator and AD password. Click Find Now, and select the GRP Remote Access, click OK. In Users or User Groups, you will see the GRP Remote Access group added. Click Next to continue.
  7. You will have the option to enable the "Audio and video playback", "Audio recording redirection", and "Desktop composition". I do not select any of these. You can come back here and enable these selection if you want. For now, click Next to continue.
  8. In Server Authentication Certificate for SSL Encryption, select "Create a self-signed certificate for SSL encryption", click Next.
  9. In User groups that can connect through RD Gateway, add the GRP Remote Access (like Step 6), click Next to continue.
  10. In RD CAP, accept the name default TS_CAP_01, choose Password, and click Next.
  11. In RD CAP, accept the name default TS_RAP_01, choose Allow users to connect to any computer on the network. Click Next.
  12. In Network Policy and Access Services, click Next.
  13. In Role services, select Network Policy Server, click Next.
  14. In Web Services (IIS), click Next.
  15. In Role services, click Next to accept default setup.
  16. Click Install to proceed installation. Wait for the installation to complete.
  17. You will receives warning messages, requesting to restart your server/services. Click Close.
  18. Do you want to restart now? Click Yest to proceed.
You just completed the Server installation of Remote Desktop Services.

Congratulation. Now, start installing the applications for your users.



Popular posts from this blog

Alternative Social Networks

If you are planning to create your social network e.g. similar to Facebook. Here's a short list of alternative software's:

Open Source and Free​
http://buddypress.org/ - Wordpress (Open Source and Free)http://elgg.org/ - (Open Source and Free)Commercial Social Networks software
http://www.socialengine.com/ ($299 Stand Alone, $29/mo Cloud)http://www.jomsocial.com/ (run with Joomla, need to know CMS)http://www.boonex.com/ (very expensive, $399 for Standard)http://www.anahitapolis.com/http://www.oxwall.org/http://sharetronix.com/http://www.moosocial.com/http://www.jcow.net/http://phpdolphin.comhttp://www.grou.ps (from free to Commercial, I left my networks and they are selling it http://www.phpfox.com/ (I used this before, it's hard to maintain. I moved to NING but left too after it was sold to another company)http://www.ning.com (I don't recommend using this service, it's hard to export your data when it's time to move)Something to check when selecting your next soc…

Example of Out of Office Reply for Terminated Employee

This is a sample message that I used for terminated employees, unless HR staff specified a different message.
=== Example for KING.NET Employee === John Doe (employee or consultant) is no longer with KING.NET effective June 1, 2008 (termination date). For matters relating to "Project Name here" please direct your concerns to John Smith at johnsmith@king.net (Manager or Supervisor). For all other matters, please direct your email to Mary Smith HR at marysmith@king.net.
Please call our main office 703-345-6789 if you have other concerns.
Thank you.
=== end of message ===

Frequent Account Lockout in Active Directory

I have a user in Windows Pro 7, and Windows Server 2003 environment that is frequently account locked out. I tried many different scenarios to resolve this account lockout issue, from resetting his password, changing a new password, remove and re-join the domain, rebooting the workstation and active directory servers.

I tried to use the command prompt utility to run "rundll32.exe keymgrdll, KRShowKeyMgr" (case sensitive) to delete the account in Windows 7 password cache, and still no luck.

Still searching for answer ... Let me know if you encounter a similar issue in Windows Pro 7 and Windows Server 2003.

Continue reading updated post here:
http://www.whaddya.com/2011/09/windows-needs-your-credentials.html