How to resolve the issue “Remote Desktop Disconnected” or “Unable to Connect to Remote Desktop (Terminal Server)”
termserv 10 Jan 2011 9:54 AM 0
One of the recurring issues seen in product support is why a client cannot connect.
Specifically, errors such as “Unable to RDP,” “Remote Desktop Disconnected,” or “Unable to Connect to Remote Desktop (Terminal server)” are common problems that we have seen come up in product support.
This article summarizes the various causes for Terminal Server Client (Remote Desktop Client) connection failures and how to fix them.
Some of the commonly seen Symptoms (order of frequency):
You may be limited in the number of users who can connect simultaneously to a Remote Desktop session or Remote Desktop Services session
You may have a Port assignment conflict
Associated Error messages:
Remote Desktop Disconnected.
This computer can’t connect to the remote computer.
Try connecting again. If the problem continues, contact the owner of the remote computer or your network administrator.
You may have an incorrectly configured Authentication and Encryption setting
You may have a corrupted Certificate
Associated Error messages:
Remote Desktop Disconnected.
Because of a security error, the client could not connect to the remote computer.
Verify that you are logged on to the network and then try connecting again.
Associated Event IDs:
Event ID: 50
The RDP protocol component X.224 detected an error in the protocol stream and has disconnected the client.
Additionally, you may also see this error message:
The client could not establish a connection to the remote computer.
The most likely causes for this error are:
1) Remote connections might not be enabled at the remote computer.
2) The maximum number of connections was exceeded at the remote computer
3) A network error occurred while establishing the connection
4) The remote computer might not support the required FIPS security level. Please lower the client side required security level policy, or contact your network administrator for assistance.
We have provided step-by-step documentation on how to fix these issues in the following articles.
Main article:
Troubleshooting RDP Client Connection problems:
http://support.microsoft.com/kb/186645
Please refer to any/all of the following articles based on your Remote Desktop Session Host Server OS:
Windows Server 2003: http://support.microsoft.com/kb/2477023
Windows Server 2008: http://support.microsoft.com/kb/2477133
Windows Server 2008 R2: http://support.microsoft.com/kb/2477176
More Information:
The following posts discuss symptoms 2 & 3 from above caused due to port assignment conflicts and/or encryption level settings:
http://www.techsupportforum.com/networking-forum/file-application-sharing/49577-unable-use-remote-desktop.html
http://www.computing.net/answers/windows-2003/unable-to-rdp/8257.html
http://serverfault.com/questions/47356/remote-desktop-disconnected-error-trying-to-connect-to-a-windows-xp-computer
The following article from ehow.com talks about how to troubleshoot a remote desktop disconnected problem but only covers very basic issues.
http://www.ehow.com/how_6574577_troubleshoot-remote-desktop-disconnected-problem.html
Ex: It asks you to check if the computer you are connecting to is powered ON and/or not in ‘Sleep’ mode.
It also talks about some of the basic settings to enable remote desktop sessions which are covered in symptom 1 above.
Additionally, we have more symptoms documented under the following article:
Troubleshooting General Remote Desktop Error Messages
http://technet.microsoft.com/en-us/library/cc780927(WS.10).aspx
Note: This is a work in progress and we will constantly be updating these articles to reflect the latest issues and how to fix them.
Custom Search
Tuesday, January 25, 2011
Upgrading previous versions of Office
Upgrading previous versions of Office
If you deployed a previous version of Office by assigning it to computers using Group Policy-based Software Installation, you can upgrade those installations by editing the associated GPO.
.gif) Note: |
|---|
The following procedure assumes that you deployed the previous version of Office by using Group Policy Software Installation to assign Office to computers. If you deployed Office by assigning or publishing the application to users, or if you used a deployment method other than Group Policy, the existing version of Office will not be upgraded if you use this procedure. Instead, the previous version of Office remains on the computer when the 2007 Office system is installed. To remove the previous version of Office you must uninstall Office. |
To upgrade Office using Group Policy-based Software Installation
- Open Group Policy Management console. Click Start, click Control Panel, click Administrative Tools, and click Group Policy Management.
- In the console tree, double-click Group Policy Objects in the forest and domain that contain the GPO that you want to edit. This is located in Forest name, Domains, Domain name, Group Policy Objects.
- Right-click the GPO you want to modify and click Edit. This opens Group Policy Object Editor.
- In the left pane of Group Policy Object Editor, expand the Computer Configuration tree.
- In the left pane, expand Software Settings and select Software Installation.
- Right-click in the right pane, point to New and click Package.
- In the Open dialog box, browse to the network installation point you created and select the Windows Installer (MSI) file in the main product folder of the Office product that you are installing. For example, for Microsoft Office Enterprise 2007, selectEnterprise.WW\EnterpriseWW.msi.
- Click OK.
- Select Assigned to use the default options, or select Advanced to customize these options. The Published option is disabled because you cannot publish Office to a user.
- In the details pane, right-click the Windows Installer package that will function as the upgrade (not the package to be upgraded).
- Click Properties and click the Upgrades tab.
- Click Add to create or add to the list of packages that are to be upgraded by the current package.
- Under Choose a package from, click Current Group Policy object (GPO) or A specific GPO as the source of the package to be upgraded. If you click A specific GPO, click Browse, and click the GPO that you want to use.
- Click the package for the previous version of Office that you want to upgrade.
- Click Uninstall the existing package, then install the upgrade package.
- Close all dialog boxes.
How it works
The 2007 Office system consists of a number of MSI files. None of the files by itself represents the complete installation. However, you assign the 2007 Office system by assigning only the main product MSI file. The next time the computer starts, this MSI file is accessed and a Windows Installer Custom Action recognizes that Office is deploying with Group Policy. The additional Office MSI and support files are then retrieved from the network installation point and the complete product is installed.
If a previous version of Office is being upgraded, that version of Office is uninstalled before the new installation of the 2007 Office system starts.
Applications assigned to a computer are resilient. If an administrator removes an Office application from the computer, Windows reinstalls the application the next time the computer starts. Users can repair Office applications on the computer, but only an administrator can remove applications.
Applying customizations to the Office installation
Because of the way Setup runs when Office is installed, there are some limitations on the number of installation options that you can customize when you deploy the 2007 Office system with Group Policy-based Software Installation. The following limitations apply:
- All customizations must be made in the Config.xml file. Setup does not apply Setup customization files that you create using the OCT. For more information about using the Config.xml file, see Config.xml file in the 2007 Office system.
- The customized Config.xml file must be located in the main product folder of the product you are installing. Because you cannot specify command-line options for Setup when you assign Office, you cannot specify an alternate location for the Config.xml file. For example, if you are installing Office Enterprise 2007, you customize the Enterprise.WW\config.xml file.
- You can customize only the Config.xml elements shown in the following table. These options are set when Office is assigned, and they cannot be modified later when Office is fully installed. All other elements in the Config.xml file are ignored.
| Option | Config.xml element |
|---|---|
Installation location | INSTALLLOCATION |
Feature installation states | OptionState |
Product key | PIDKEY |
Add or remove a language | AddLanguage, RemoveLanguage |
Modifying the Config.xml file OptionState element
The OptionState element of the Config.xml file specifies how individual product features are handled during installation. Administrators can modify the Config.xml file by configuring attributes for the OptionState element. Administrators can specify the following behaviors:
- The feature or sub-feature is not installed.
- The feature or sub-feature is installed the first time it is used by the user.
- The feature or sub-feature is installed locally on the user's computer.
- Sub-features of the feature are set to the specified state.
OptionState Syntax
The OptionState element uses the following syntax. The attribute and element names are case sensitive.
where:
optionId is the identifier for a feature or sub-feature to install.
Absent specifies that the feature or sub-feature is not installed.
Advertise specifies to install the feature or sub-feature on first use.
Local installs the feature or sub-feature on the user's computer.
Force sets all features or sub-features to their specified states.
OptionState Id Values
The value for the Id attribute of the OptionState element is located in the Setup.xml file in the product folder of the product you are installing. For example, if you are installing Office Enterprise 2007, the file is Enterprise.WW\setup.xml. For a list of OptionState Id Values, see Config.xml file OptionState Id values.
.gif) Tip: |
|---|
If you set the installation state of an application in Office to "Absent", the shortcut for that application is not created on the user's computer when Office is assigned. For example, the following element definition in Config.xml prevents the shortcut for Microsoft Office Word 2007 from being created and Word is not installed on the user's computer: |
To modify the OptionState element in Config.xml
- Open the Config.xml file in a text editor tool, such as Notepad.
- Locate the line that contains the OptionState element, as shown in the following example:
- Modify the OptionState element entry with the options you want to use. For example, use the following syntax if you do not want Microsoft Publisher to be installed:
- Repeat the preceding step to specify OptionState options for other features and sub-features you want to modify.
- Save the Config.xml file in the same folder that contained this file before you edited it.
For more information about the OptionState element of the Config.xml file, see the “OptionState element” section in Config.xml file in the 2007 Office system.
Download this book
This topic is included in the following downloadable book for easier reading and printing:
Deploying new installations of Office
Deploying new installations of Office
If this is a new installation of the 2007 Office system, you can deploy Office by assigning it to computers within a GPO that is associated with a particular Active Directory container such as a domain or organizational unit. Computer-assigned applications are installed the next time the computer restarts.
To deploy Office using Group Policy-based Software Installation
- Open Group Policy Management console. Click Start, click Control Panel, click Administrative Tools, and then click Group Policy Management.
- In the console tree, double-click Group Policy Objects in the forest and domain that contain the GPO that you want to edit. This is located in Forest name, Domains, Domain name, Group Policy Objects.
- Right-click the GPO you want to modify and click Edit. This opens Group Policy Object Editor.
- In the left pane in Group Policy Object Editor, expand the Computer Configuration tree.
- In the left pane, expand Software Settings and select Software Installation.
- Right-click in the right pane, point to New and click Package.
- In the Open dialog box, browse to the network installation point you created and select the Windows Installer (MSI) file in the main product folder of the Office product that you are installing. For example, for Microsoft Office Enterprise 2007, selectEnterprise.WW\EnterpriseWW.msi.
- Click Open.
- Select Assigned to use the default options, or select Advanced to customize these options.
- Close all dialog boxes.Note:If you are deploying 2007 Office in languages other than U.S. English, you should also deploy the ShellUI.MST transform file. Transforms (.mst files) are customizations that are applied to Windows Installer packages (.msi files) at the time of application assignment or publication, not at the time of installation. The following procedure explains how to add the transform to application packages. With the exception of the ShellUI.MST file, transforms are not supported in Office 2007. For information about Office Setup, see Getting started with the 2007 Office system.
To add modification to application packages
- Open Group Policy Software Installation.
- In the console tree, right-click Software installation, point to New, and then click Package.
- In the Open dialog box, click the Windows Installer package, and then click Open.
- In the Deploy Software dialog box, click Advanced, and then click OK.
- In the properties dialog box for the package, click the Modifications tab.
- To add modifications, click Add. In the Open dialog box, browse to the transform file (.mst), and then click Open.
- Click OK.Note:When you click OK, the package is assigned or published immediately. For more information about using Group Policy Software Installation, see Group Policy Software Installation on the Microsoft TechNet Web site.
Subscribe to:
Posts (Atom)