Using Remote Desktop
Applies To: Windows Server 2008 R2
To allow remote connections for administrative purposes only, you do not have to install the RD Session Host role service. Instead, you enable Remote Desktop on the computer that you want to remotely administer.
|Remote Desktop supports only two concurrent remote connections to the computer. You do not need Remote Desktop Services client access licenses (RDS CALs) for these connections.|
You can use the following procedure to enable Remote Desktop on a Windows Server 2008 R2 computer.
Membership in the local Administrators group, or equivalent, on the computer that you plan to configure, is the minimum required to complete this procedure.
- Start the System tool. To start the System tool, click Start, click Run, type control system and then click OK.
- Under Tasks, click Remote settings.
- In the System Properties dialog box, on the Remote tab, click either of the following, depending on your environment:
- Allow connections from computers running any version of Remote Desktop (less secure)
- Allow connections only from computers running Remote Desktop with Network Level Authentication (more secure)
For more information about the two options, click the Help me choose link on the Remote tab.
- Click Select Users to add the users and groups that need to connect to the computer by using Remote Desktop. The users and groups that you add are added to the Remote Desktop Users group.
Note Members of the local Administrators group can connect even if they are not listed.
What is a CSR? A Certificate Signing Request or CSR is a specially formatted encrypted message sent from a Secure Sockets Layer (SSL) digital certificate applicant to a certificate authority (CA). The CSR validates the information the CA requires to issue a certificate. A CSR must be created before ordering and purchasing an SSL certificate (or activating an SSL certificate already purchased through your domain registrar). How a CSR is generated depends on the web server software used. Once the CSR is generated, it can be submitted to the CA. If the request is successfully validated, the CA will issue the SSL certificate.
Here are the steps to generate a CSR in IIS7 on Windows Server 2008 R2. Why might this be necessary? Well, you may want to install Microsoft Exchange and connect to it via Outlook or Outlook Web Access (OWA) which would require Secure Socket Layer (SSL).
- Click Start
- Select Administrative Tools
- Start Internet Information Services (IIS) Manager
- Click the Server Name
- Double click on the “Server Certificates” button in the “IIS” section, located int he center menu
- Choose the “Actions” menu (on the right)
- Click on “Create Certificate Request (Note: Even if you are renewing an SSL certificate that may be about to expire, use the CREATE Certificate Request and do NOT select renew).
- The Request Certificate wizard will be opened. From here, you will need to enter the information required for the CSR code (details and example listed below):
Common Name: e.g. yourdomain.com or, if you are creating a CSR for your mail server’s subdomain, then enter something like this containing your server’s host header: mx.yourdomain.com or mail.yourdomain.com
Organization: MyCompany Ltd
Organization Unit (eg, section): Communications, IT, Support, Sales etc.
City/ Locality Name: Los Angeles
State or Province Name (full name): California
Country Name (2 letter code): US
- Specify a filename and location to save your CSR code (e.g. c:\certificate\certreq.txt)
- Click Finish
You may view the CSR file using a text editor such as Notepad++ and the certificate request should appear like this:
Image Omitted for security reasons.
Note: When Installing the newly issued (renewal) certificate issued to you by your CA, you must first REMOVE the existing certificate from IIS7 because there will be an installation conflict (between the new certificate and the existing certificate that is still installed on the server. In other words, an error will occur during installation of the new certificate if the existing certificate is not first removed.
This article is based substantially upon Namecheap.com support knowledge base article:
After your new or renewal SSL certificate is issued to you and arrives via email, you may follow these instructions to install it on IIS7, but watch out for the known bug in IIS7.
When you click “Complete Certificate Request” in IIS7 management console, and then browse to find your newly issued *.cer file, when you click Open, you may receive an error message about a “Conflict” explaining that the CSR may not have been issued by the server where you are installing the *.cer file, which is nonsense.
Just continue hitting Retry or OK button a couple times, then hit the cancel button. Refresh the screen in IIS7 Management Console and see if your new certificate is listed there without a Friendly Name associated with it. That is GOOD. Do not remove the installed certificate. Now go to do the Bindings on the IIS7 Default Web Site. See the Second Link (last article) listed two paragraphs above.
Once the bindings are established to https on port 443, then you must restart the default website from within the management console.
Go test that your website can be viewed via https://
The last few lines of the tutorial say:
Click ‘OK’ on the ‘Web Site Bindings’ Window to complete the install.
Important: You must now restart IIS / the website to complete the install of the certificate.
You have downloaded and installed Open Source Filezilla FTP Server on Windows Server 2008 R2. You have configured it in the passive mode to connect only on TCP Port 21 by entering in the port range From 21 To 21, which is the standard FTP port. You are behind the NAT on your Router so, when configuring Filezilla after installation, you have entered the static public IP address of your router on which port forwarding is configured to forward from port 21 on the public IP to port 21 on your server’s bind local IP.
You fire-up your FTP client and try connecting to the Filezilla server to no avail. You already setup a user and password and default directory on the Filezilla server. However, it might not be connecting because your Windows Firewall is likely blocking ftp reception on port 21 at the server.
Let’s use the Microsoft Management Control (MMC) Snap-in to open TCP port 21 inbound.
Click “START” button, and point to “Programs,” “Administrative Tools,” and select “Windows Firewall with Advanced Security.”
In general, Windows firewall is enabled and, by default, inbound connection that do not match a firewall rule are blocked. By default, all outbound connections that do not match a firewall rule or allowed (not blocked). So, we may need to add and inbound rule.
Right-click “Inbound Rules” and left-click “add New Rule,” or select “Inbound Rules” on the left and click “New Rule” under the actions section on the right.
Rule TYPE: Select “Port” and click Next.
Rule PROTOCOL: Select “TCP,” Select “Specific local ports” and enter “21” and click Next.
In the “ACTION” section, select “Allow the Connection” and click Next.
In the “PROFILE” section, make sure that all 3 check boxes are checked for Local, Domain, and Public.
In the ‘NAME” section, type something like “TCP port 21 for FTP service.” In the DESCRIPTION text box, you may add whatever explanation you wish, such as “Custom Inbound Firewall Rule to Allow FTP communication on standard TCP port 21 — MyRule.”
Test your connection from FTP client to Filezilla server now.
Use Coupon Code WGSPECIAL to purchase or renew WhoisGuard at NameCheap dot com for only $0.99 (99 cents).
Annual Registration of Dot Com Domains are ordinarily $10.69 Plus $0.18 ICANN Fee. Dot Net annual registrations or renewals are $12.48 plus the ICANN Fee.
Go to: http://www.namecheap.com
Here are the Novacom Drivers for Windows 32-bit and 64-bit operating systems. There are two zip files and select the correct file download for your operating system. Extract the Zip files to a known folder. The Zip file includes the Novacom.MSI installer file the HP License Agreement PDF (Date Modified August 2011).
Here is a Video:
How to install Android 5.0.x/4.4.x on the HP TouchPad the Super Easy Way (Idiots Guide 4.0)
By: Roland Deschain. This video explains using the Touchpad Toolbox (TP Toolbox) by J.C. Sullins.
TPToolbox by J.C. Sullins
Here: http://forum.xda-dev…d.php?t=2756314 and
CM11/Android 4.4.2 by J.C. Sullins
The CM11 link above says:
[ROM] [4.4.4] [CyanogenMod 11 by Jcsullins] [DM] [01/13/15]
Downloads: [See 1., A., B., and C. below]
1. TPToolbox: V40 released on 2014-05-18
It can be downloaded from:
Note: To load TPToolbox, you will need novacom to be installed on your PC. See Novacom Links above.
THE TPToolbox will help you load A, B, and C below onto your HP Touchpad:
A. ROM: CyanogenMod 11 by JcSullins find the latest one to download. I used cm-11-20141015-Snapshot but there is a more recent at the bottom of the file download list.
B. DATA MEDIA: (KitKat) Data Media Install files [Note: I used Philz-CWM]
Download Philz-CWM: [I used this one]
C. G-Apps: KitKat Google Apps
https://goo.im/gapps/gapps-kk-20140105-signed.zip/ Standard Gapps
Paranoid Android Gapps Choose the Micro or Nano Modular Packs
I either used the (i.) pa-gapps-stock-4.4.4-20141110-signed or the (ii) Gapps-kk-20140606-signed (less trusted). Need to figure out which works and is compatible with the ROM that you will use. Try searching for gapps as there may be some on Google Apps in developers sections. Get an inclusive g-apps base package for KitKat.
My Self Notes from Above Resources (no warranties): Download PDf: Installing-Android-on-Touchpad
Having your email collected using a perimeter server and forwarded to your local network exchange server?
Did you get this error yet when sending to your exchange domain?
Reason: Remote SMTP Server Returned: 550 5.7.1 Unable to relay
Then, try adding a Receive Connector like this.
To permit a non-Exchange server to relay mail to your internal exchange server, create a new Receive Connector on the Hub Transport server.
- Launch the Exchange Management Console, expand +”Server Configuration” and select “Hub Transport.” Click Add new receive connector.
- in the wizard dialog, under “Name:” enter the a descriptive name, like RelayFromPerimMail, and for Intended use, select “Custom” and click Next.
- Enter the FQDN response from the exchange server to any ELLO or EHLO from the perimeter relay server: such as ExchMail.YourDomain.com (rather than .lan or .local). Next.
- Delete the 0.0.0.0-255.255.225.0 network setting offered.
- Click +Add, select IP Address. Enter the IP address of the perimeter server that is relaying mail to this exchange server. Click OK, click Next, click New, and click Finish.
- Your Receive Connector is created but it is not ready to allow the perimeter server to relay incoming mail to the exchange server. You must finish configuration as follows:
- Return to the Exchange Management Console and right click this new Receive Connector and select Properties. Select the “Permission Groups” tab and check the box next to “Exchange servers.” Then, select the “Authentication” tab, leave the check in the checkbox next to Transport Layer Security (TLS) and also check the checkbox next to “Externally Secured” and apply these changes.
- Now, test everything by sending a test email from gmail, yahoo or hotmail, to your local email address on the exchange server. See if it arrives using your OWA interface.
Note: Since the remote IP address (or range) has been restricted to the single IP address of the perimeter server, then any other servers trying to connect from a different IP addresses still will NOT be able to relay through the Exchange Server (which is as it is intended). In other words, relay will be denied from any other IP address not included in the remote IP address/range on the Receive Connector. If necessary, you can later try to add more IP addresses, IP ranges, or subnets to this receive connector, or possibly even add multiple IP addresses, but you may need to script this latter action.
If you have installed Exchange Server 2010 and want to send outgoing mail through your smart host or non-exchange perimeter server which already has MX records in DNS associated with the smart host, then add a Send Connector to Exchange as follows:
- Open your Exchange Management Console.
- Expand +”Organization Configuration” and select the sub-item named “Hub Transport.” Select the tab entitled “Send Connectors.”
- From the menu on the right side, select the link for “New Send Connector” and the New Send Connector wizard dialog will appear.
- Enter a “Name:” such as “OutgoingHost” and under “Intended Use for this send connector” select “custom” from the list box and click Next.
- Click Add the type “SMTP” and the “SMTP Address Space” will appear. Under “Address:” insert an * (asterisk), check the box next to “Include all sub-domains” and leave the Cost: as 1. Click the OK button to close the Address space, and then Click the NEXT button.
- Network Settings appears. Click the radio button next to “Route mail through the following smart hosts”
- Click +Add and either enter the IP address of the smart host server, or select the radio button next to Fully qualified domain Name (FQDN), and enter the hostname.domainname.com of your smart host in the input text box, such as Mail1.MySmartHostnet. Click OK to close this dialog, and Click NEXT.
- Configure smart host authentication settings will appear. For many servers that won’t require exchange authentications, you can select “Basic Authentication” and input the username and password of the smart host’s postmaster or other account that has access to the postmaster outgoing smtp transport. Click Next, Next, New and Finish buttons.
- Tidy up by right clicking this new “OutgoingHost” Send Connector, and left click on properties. Under the “General” tab, insert the fully qualified “internet” hostName.domain name.com that your server will echo in response to HELO or EHLO when connecting to the smart host, for example: Exchg1.MyInternetDomainName.com (not your .lan or .local FQDN). Change the maximum message size if you like. Click Apply, and click OK.
- Test it by logging into you administrator account using OWA interface and send a test message to yourself at hotmail or gmail or yahoo.
Install Windows Server 2008 R2 64 bit version
Exchange Server 2010 is a 64 bit application and requires a 64 bit Server Operating System
After Server 2008 installation, then set the clock and set the name of the Server
The server is presently configured as standalone with default settings
Configure a static IP address because the server will be configured as a domain controller
Go to the server manager screen and click View Network Connections
Double click the icon for the active network adapter (local area connection) to display the adapter status
In the Status screen, click the Properties button
Click to highlight the Internet Protocol Version 4 (TCP/Ipv4) and Click the Properties button
Click the radio button next to “Use the following IP address:” and then enter the IP address that you want to use for this server, for example, 192.168.1.2
After entering the IP address, click the “tab” key and the subnet mask 255.255.255.0 should appear in the entry boxes of the next line (which is fine)
Click the “tab” key and enter the default gateway IP address (which is the gateway address on the local network “LAN” side of you router which provides the network address translation “NAT” over to the public IP side “WAN side” of the router). This number is usually something like 192.168.1.1
Click the radio button next to “Use the following DNS server addresses:” and, under preferred DNS server, enter the same server IP address (that you chose) for the IP address of the server. It is important to include this server’s IP in the DNS server list as the first entry in the list of DNS servers. You can add other alternated DNS servers that you maintain or as provided by your ISP. Note that later when installing Exchange Server, it may be necessary to correct the first DNS to 127.0.0.1 (your server’s localhost) and secondary DNS to the local IP assigned to the network interface of the server, such as 192.168.1.2. Otherwise, Exchange installation wizard will give you a warning that an MX record or an Address (A) record cannot be verified on the IP address 127.0.0.1 (or on 192.168.1.1 as the case may be at the time).
Note: Exchange 2010 requires that you leave IP v6 enabled. So, do NOT disable IP v6 or else the Exchange Hub Transport Service will not start when exchange is installed.
Close the network connections screen
Install Active Directory. When Active Directory is both installed and configured (a two step process), then Windows Server will be a Domain Controller
Go to “Computer Management” screen and press the “Add Roles” link. Under “Server Roles” it says “Select one or more roles to install on this server.”
Check the box next to “Active Directory Domain Services” at which time the add roles wizard says that “you cannot install Active Directory Services unless the required features are also installed. The “Features:” list will include .NET Framework 3.5.1 Features
Click the Button for “Add Required Features” and acknowledge by clicking “Next”
The installation will scan and inform of any other prerequisites. If there are other prerequisites or errors, please correct these and repeat the add roles installation
When the Setup program says that all prerequisites are met, then click the install button to commence this installation process. The setup program will now install Active Directory on your Server
When the installation is completed, there should be a message indicating that the “Installation Succeeded”
Click “Close” to close the Add roles wizard’s “Installation Results” screen in order to return to the Server Management screen.
Configure Active Directory. You should see that the role of Active Directory Domain Services is installed when you are viewing the Server Manager page. It will show a red “x” to indicate the Active Directory Domain Services have errors, namely, that these Services have not been configured.
Click on the line under Roles that is labeled “Active Directory Domain Services” and the Server Manager will show you a page about the status of the Active Directory Role.
Click on the link that says “Run the Active Directory Services Installation Wizard (dcpromo.exe)” and click “Next” when the Active Directory Domain Services Installation Wizard appears.
The Active Directory Domain Services Installation Wizard will display information about Server 2008 domain controllers having a new more secure default for the security setting named “Allow cryptography algorithms compatible with Windows NT 4.0” (which setting is disabled or not configured by default). It explains that this setting prevents Windows and non-Microsoft SMB clients from using weaker NT 4.0 style cryptography algorithms. As a result, applications that require a security channel serviced by Server 2008 domain controllers might fail, for example, certain NAS devices that do not support stronger cryptography algorithms, and certain operations on clients running versino of Windows earlier than Vista SP1 are also impacted. If this is going to be a problem, see KB Article 942564 http://go.microsoft.com/fwlink/?LinkId=104751 The following hotfix package may be applied to computers that are running Windows XP or Windows Server 2003 to resolve this issue: http://support2.microsoft.com/kb/944043 Description of the Windows Server 2008 read-only domain controller compatibility pack for Windows Server 2003 clients and for Windows XP clients and for pre-sp1 Windows Vista. CLICK NEXT.
Choose a Deployment Configuration. At this point, you can create a domain controller for an existing forest or for a new forest.
If this Exchange Server will be the first Domain Controller, then choose the radio button for “create a new domain in a new forest” and click the Next button.
If there is an existing Domain Controller and you want to continue the same domain name, then you may wish to choose the radio button “Existing Forest” and the sub-radion button for either: “Add a domain controller to an existing domain” or “Create a new domain in an exiting forest” in which case this server will become the first domain controller in the newly created domain.” Click the Next button.
Enter the name of your local Domain, which will be the domain name that Exchange will associate with all of your email. When creating a new domain name in a new forest, this domain name becomes the “Name of the Forest Root Domain” because the first domain in the forest is the forest root domain. It’s name is also the name of the forest. Note: If you are on a local network (LAN) behind a router’s NAT firewall, then you may want to distinguish your local network domain name from your public domain name by using either the suffix “.local” or “.lan” instead of a public network domain suffix like “.com” or “.net.” Once you have decided on the name of your internal domain, this name will be your Active Directory Domain and the domain that is serviced by Exchange.
You will enter this internal domain name in the input box under the heading “FQDN of the forest root domain.” Click the Next button.
Set Forest Functional Level. The Installation Wizard will now ask you about compatibility of domain controller active directory servers at the forest level. If you plan to have domain controllers running various versions of Active Directory, then you will want to chose a function level to include the lowest version of Windows Server that you are using for domain controllers. For example, if you have and plan to keep a Windows 2003 domain controller in service, then select “Windows Server 2003” from the drop down list and click Next.
Set Domain Functional Level. The Installation Wizard will now ask you a similar question about domain controller active directory server compatibility at the domain level. Include the same function level namely the lowest version of Windows you plan to use for domain controllers. For example, if you have and plan to keep a Windows 2003 domain controller in service, then select “Windows Server 2003” from the drop down list and click Next.
Additional Domain Controller Options. The installation wizard recommends to install the DNS Server service on the first domain controller. So, if this is the first domain controller, check the box to add DNS Server service and make this domain controller a DNS server running locally. Note: The first domain controller in a forest must be a global catalog server and cannot be an RODC. The Installation Wizard will also automatically make this computer a global catalog server if a new forest and first domain are being created. Press Next.
Specify Location for Database, Log Files, and SYSVOL. You can specify where you want Active Directory to store its data. If you only have one drive in your Server, then it is recommended to use the prepopulated defaults. If you have multiple drives, you can select which drive to use. Click Next.
Directory Services Restore Mode Administrator Password. The Directory Services Restore Mode Administrator account is different from the domain Administrator account. Assign a password for the Adminstrator account that will be used when this domain controller is started in Directory Services Restore Mode. Write down the password. It is different than the domain Adminstrator password, and will not change when the domain Adminstrator password is changed.
Review Your Selections. The Installation Wizard will summarize the configuration that it is about to create. To start the process of configuring your new Domain Controller, click Next.
The Installation Wizard will show its progress as it configures your Server. This will take a long time. The installation wizard dialog says “The wizard is configuring Active Directory Domain Services. This process can take from a few minutes to several hours, depending on your environmnet and the options that you selected. . . . Installing Group Policy Management Console . . . ” No need to check the box that says Reboot on completion.
When the installation is complete, you will be shown a final screen. Click Finish.
Then, restart your computer. Click “Restart Now” to restart your computer so that the changes made by the Active Directory Domain Services Installation wizard will take effect.
After restarting, Windows should show the Server Manager. The Server Manager screen should show that Active Directory and DNS Server roles are installed. Also the process of installing Active Directory will add the features “Group Policy Management” and “Remote Server Administration Tools.”
This article is for installing printer drivers and configuring a Windows 10 Technical Preview PC for printing to LAN-Shared HP LaserJet 2300 Series Printer that is connected and installed on a USB Port of a Windows XP PC and shared on a LAN from the XP PC. The Windows Technical Preview machine (that is, the Windows 10 PC) wants to use this remote printer shared from the XP PC, but the add printer wizard mechanisms on Win 10 refuses to install it as it searches but can’t find an appropriate driver on the Windows Update. And, even if you visit the HP support site and download the 32 or 64 bit Universal drivers for Win 8.1, this does not provide the necessary *.inf or printer drivers to connect to the remotely shared printer.
Here is the Fix or Work Around:
- Plug the printer directly into the Windows 10 PC.
- Allow Windows 10 to locate and install a driver from Windows Update. Once installed locally to the Windows 10 PC, then print something to test.
- Unplug the printer from the Windows 10 PC and then plug it back into the Windows XP machine. Important, you must use the same USB socket that the printer was originally connected to or you may get another 2300 Series printer detected and installed on the XP machine.
- Assuming the HP LaserJet 2300 is shared from within XP you now need to browse the network on the Windows 10 PC to find the remote XP machine and the shared HP Printer connected to it. When you see the shared printer, click the right mouse button on the remote printer and select ‘Make shortcut’ – a shortcut should appear on the Windows 10 desktop.
- Right click on the desktop shortcut and click properties. The Target box should be highlighted, so click on it and select copy. You will be copying the network shortcut of the remote Printer, for example, \\XP-PC-Name\HP-LaserJ
- On the Windows 10 machine, search for and Open the “Devices and Printers” panel. The 2300 Series that you installed locally via USB socket will still exist even though the printer has been returned to the remote XP PC on the same LAN. Right click on the Printer icon and the left click “Printer Properties.”
- Click the Ports tab. Then click “Add port” and then click ‘Local Port,” When the ‘Enter Port Name’ text input box appears, paste in the Network Shortcut target information and click next.
- Click OK or Apply until all the boxes have gone.
You should now have a working printer!
Windows 10 treats the Printer Device on the newly installed Port like its a local printer, but you have redirected it to the LAN shared printer connected to the USB port of the XP machine.
Print a test page. Set the 2300 as your default printer on Windows 10.
This fix is derived from the Microsoft Tech Net Forum answer proposed by Nic Bunting with regard to a Windows 7 install, posted on Monday, April 26, 2010, 11:52 AM. See Forum Thread at:
Apparently, something similar now works for the Windows Technical Preview.