Remotely Enable Remote Desktop

Remotely Enable Remote Desktop

Remotely enable Remote Desktop in Windows 7

Overcoming firewall obstacles

by Anthony Eden / March 25, 2013 / Support Centre

Windows 7 doesn’t allow Remote Desktop connections by default – this has to be enabled by the user (or set via group policy). What happens if you’re in a bind and need quick remote access to a desktop? If you’re in a domain environment you may just be in luck. There are four steps needed to remotely enable RDP connections.

1. Open ports in the Windows firewall
2. Start the Remote Registry service
3. Change a registry setting to enable Remote Desktop
4. Start the Remote Desktop service

For this guide I assume you are on the same LAN as the remote computer you want to access (you may already have RDP’ed into a server on that LAN), and you are logged in as a Windows user with administrative privileges for the remote computer you are wishing to access.
This isn’t likely to work work if you are on the other side of an agressive firewall.
Note: If you have access to the computer, you can follow the standard procedure for enabling Remote Desktop.

Step 1: Open ports in the Windows firewall

There is no native way to change the settings of a remote Windows firewall. However, you can use PsExec from SysInternals to disable it or change some rules.
If you download the app and drop it into your c:\ drive, you can run this command and get command line access for that remote box.

c:\psexec \\remote_machine_name cmd

Once you have that command line open, you can run this command to disable the firewall:

netsh advfirewall set currentprofile state off

Alternatively you can run this command to allow only Remote Desktop while still leaving the rest of the firewall as is:

netsh advfirewall firewall set rule group=”remote desktop” new enable=Yes

Step 2: Start the Remote Registry service

Load up the Services MMC (Control Panel > Administrative Tools > Services), right click on “Services (Local)” and choose “Connect to another computer”. Enter the name of your remote machine and connect to it. You should now be able to find the “Remote Registry” service and start it.
Depending on your environment, this may already be running, but I have found it generally isn’t on fresh computers.

Step 3: Change a registry setting to enable Remote Desktop

It’s time to make use of the Remote Registry and actually enable RDP. Load up regedit and go to File > Connect Network Registry. Enter the name of your remote computer and connect to it. Navigate to HKEY_LOCAL_MACHINE > System > CurrentControlSet > Control > Terminal Server. Change the value of “fDenyTSConnections” to “0”.

Step 4: Start the Remote Desktop service

Go back to the Services MMC you used in Step 2. Find the service “Remote Desktop Services” and start it (or restart if it is already running).

Step 5: Connect

By this point you should be able to connect to a remote desktop session on your remote computer. Remember that only administrative users can connect to an out-of-the-box Remote Desktop setup. If you have got this far and still can’t connect, it is worth checking your firewall rules to ensure nothing is being blocked.

How to associate .docx with Microsoft Word in Windows 10?

How to associate .docx with Microsoft Word in Windows 10?

Open 'File Explorer'.
Browse to the .docx file you want to open but failed.
Select it by clicking it.
Click 'Home' tab in the menu on the top.
Click the downward triangle beside 'Open'.
Click 'Choose another app'.

Click 'More apps ↓'.

If there is no 'Microsoft Word', then scroll down and click 'Look for another app on this PC'. An 'Open with...' dialogue box' pops up. Current path would be 'Windows (C:) > Program Files'.

Double-click 'Microsoft Office'.

Double-click 'Office14'.

Choose 'WINWORD.EXE'. Click 'Open' button. (Tick 'Always use this app to open .docx files'.)

Done.

You cannot use Outlook to complete a Microsoft Word Mail Merge

You cannot use Outlook to complete a Microsoft Word Mail Merge

Symptoms

---

You use Microsoft Word to start a Mail Merge that is configured to send email messages to the recipients. However, Microsoft Outlook does not send the email messages. In some cases, you do not receive an error message. Or, you may receive the following error message:

Word could not load the e-mail envelope. This could be caused by a network connection problem or a problem with your Office installation.

Cause

---

If you are using Microsoft Outlook 2002, Microsoft Office Outlook 2003, or Microsoft Office Outlook 2007, this issue may occur if you install a newer version of Microsoft Office and then uninstall the newer version. This issue also occurs when you install a trial edition of a newer version of Microsoft Office.

If you are using Microsoft Outlook 2010, this issue may occur if you install the 64-bit version of Microsoft Office 2010 or of Microsoft Outlook 2010, you uninstall the 64-bit version, and then you install the 32-bit version.

Resolution

---

Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:

322756 How to back up and restore the registry in Windows

Outlook 2002, Outlook 2003, or Outlook 2007

To resolve this issue for Outlook 2002, for Outlook 2003, or for Outlook 2007, follow these steps:

1. Exit all Microsoft Office applications.
2. Start Registry Editor:
   • In Windows Vista or in Windows 7, click Start, type regedit in the Start Search box, and then press Enter.
     
     
     If you are prompted for an administrator password or for confirmation, type the password, or provide confirmation. 
   • In Windows XP, click Start, click Run, type regedit in the Open box, and then click OK.
3. Locate and then click the following registry subkey: 
   
   HKEY_CLASSES_ROOT\TypeLib\{00062FFF-0000-0000-C000-000000000046}
4. On the Edit menu, click Delete.
5. Exit Registry Editor.
6. Repair or reinstall the Microsoft Office program.

Outlook 2010

To resolve this issue for Outlook 2010, follow these steps:

1. Exit all Microsoft Office applications.
2. Start Registry Editor:
   • In Windows Vista or in Windows 7, click Start, type regedit in the Start Search box, and then press Enter.
     
     
     If you are prompted for an administrator password or for confirmation, type the password, or provide confirmation. 
   • In Windows XP, click Start, click Run, type regedit in the Open box, and then click OK.
3. Locate and then click the following registry subkey:
   HKEY_CLASSES_ROOT\TypeLib\{00062FFF-0000-0000-C000-000000000046}\9.4\0\win64
4. On the Edit menu, click Rename.
5. Type BAKwin64, and then press Enter.
6. Exit Registry Editor.
7. Repair the Microsoft Office 2010 or Microsoft Outlook 2010 installation.
   • In Windows Vista or in Windows 7, click Start, type programs and features in the Start Search box, and then press Enter.
   • In the list of installed programs, right-click Microsoft Office 2010 or Microsoft Outlook 2010, and then click Repair.

PowerPoint Won't open network files

PowerPoint Won't open network files

We can also try disable Protected View to see if it helps. To do this, please follow:

1. Open a PowerPoint file.

2. Click File > Options > Trust Center > Trust Center Settings.

3. Click Protected View from the left panel.

4. Clear all the three check boxes and click OK.

If above doesn't work, please also try testing with a new Windows user profile.