Because of an error in data encryption, this session will end. Please try connecting to the remote computer again

Cause:
Microsoft says  this is a potential race condition between the Icaapi.dll and Rdpwsx.dll dynamic-link libraries (DLLs) may cause the private certificate key on the Terminal Services server not to be synchronized.

Resolution:
Important: This procedure involve modifying the registry of the server, please take extra caution by backing up your registry key before proceeding

To resolve this issue, follow these steps:

1.    Start Registry Editor.
2. Locate and then click the following registry subkey:
         HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\TermService\Parameters
3. Under this registry subkey, delete the following value (s):
             * Certificate
             * X509 Certificate
             * X509 Certificate ID
4. Quit Registry Editor, and then restart the server.

I hope this helps!

1. Visio web Shapes - Web server error. Try your search again later

Many Visio users who are trying to search for Shapes features in Visio 2003 or 2007 have been getting the above error message.

The reality is that the online search portion of Search for Shapes feature is being discontinued and the servers are being shut down. Users of Visio 2002 and later versions will only be able to search for shapes locally. The above  dialog appears to be a side effect of the attempt to contact those servers. 

In order to prevent the dialog, you will want to disable the attempt to search the Internet shapes in Visio 2003 / 2007.  This issue doesn't impact Visio 2010, as it only searches locally.

To disable the Internet search option, follow these steps:

    * Select the Tools menu, then choose Options, then select the Shape Search tab
    * Expand the Search Locations
    * Uncheck the box for "The Internet" location
    * Click OK to save the options

Installing Office 2007 on Terminal Server and removing user information

For those Systems Administrator (like me) or Helpdesk who have experience in installing Microsoft Office 2007 on the Terminal Server, their first big disappointment/frustration is the fact that after installing Office 2007 on the Terminal Server, the user information of the account used to install Office is replicated to all users who then run an Office application. For example, if you install office 2007 on the Terminal server using “XYZ” account, this account (XYZ) will be the owner of all the office documents/files users (on the terminal server) will then create. This fact has been a big frustration for both users and the IT administrators.

In this post, I will be describing how to delete identifying information recorded to the Terminal Server shadow registry key by Setup during Office 2007 installation and to make sure that user information of the account used to install Office is not replicated to all users.

(Note: As you can see, this procedure involve modifying the registry of the server, please take extra caution by backing up your registry key before proceeding.)

1. After installing Office 2007, make sure you DO NOT open/run  any office applications.
2. Go to “Run” and type “Regedit” command and perss “Enter” (this will open the registry).
3. Go to:
   “HKLM\SOFTWARE\Microsoft\WindowsNT\CurrentVersion\Terminal Server\Install\Software\Microsoft\Office” and delete “Office” subkey.
4. Reboot the Server.

Hope this helps!

New Exchange Server 2007 mailbox stamped as legacy mailbox

If you use the Exchange Server 2003/2000 extensions to Active Directory Users & Computers (ADUC) console to create mailboxes residing on Exchange Server 2007 servers, these mailboxes get stamped as legacy mailboxes.
Exchange Server 2007 mailboxes should be created using the Exchange (2007) console or shell.
To remove the legacy tag from mailboxes created using ADUC, use the following command:

Set-Mailbox "John Doe" -ApplyMandatoryProperties

This is documented in KB 931747: A mailbox that is located on an Exchange Server 2007 server may be identified as a legacy mailbox in Exchange Server 2007.
To get a list of legacy mailboxes:

Get-Mailbox | where {$_.RecipientTypeDetails -eq "legacymailbox"}

Note, not all legacy mailboxes reside on Exchange Server 2007 servers, so it's not a good idea to use the ApplyMandatoryProperties command to all of these. Mailboxes residing on Exchange Server 2003/2000 servers are also legacy mailboxes, and you may see some mailboxes moved from Exchange Server 2003/2000 servers carry this tag as well.
Let's filter the above list of legacy mailboxes to only the ones located on Exchange 2007 servers:

Get-ExchangeServer | Where {$_.IsExchange2007OrLater} | Get-Mailbox | where {$_.RecipientTypeDetails -eq "legacymailbox"}

Apply mandatory properties:

Get-ExchangeServer | Where {$_.IsExchange2007OrLater} | Get-Mailbox | where {$_.RecipientTypeDetails -eq "legacymailbox"} | Set-Mailbox -ApplyMandatoryProperties

No Terminal Server client access licenses available for this computer

I had a situation recently when some users tries to connect to the Terminal Server they received the following error message: The remote session was disconnected because there are no Terminal Server client access licenses available for this computer. Please contact the server administrator.

There are many options to workaround this issue. To see more of these workarounds, you can visit Microsoft website. However, I opted for the solution I am going to describe below which works wonderfully.

Note: Please note that this solution requires modification of the system’s registry. So take an extra caution (back up your registry) before proceeding.

Problem: The remote session was disconnected because there are no Terminal Server client access licenses available for this computer. Please contact the server administrator.

Solution: Create a backup of the MSLicensing registry key and its subkeys on the client, and then remove the original key and subkeys by doing the following:

1. On the client, navigate to the following registry subkey:
   HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSLicensing.
2. Click MSLicensing.
3. On the Registry menu, click Export Registry File.
4. In the File name box, type mslicensingbackup, and then click Save.
5. On the Edit menu, click Delete, and then click Yes to confirm the deletion of the MSLicensing registry subkey.
6. Close Registry Editor, and then restart the computer.

(Note: If you need to restore this registry key in the future, double-click mslicensingbackup.reg.)

When the client is restarted, the missing registry key is rebuilt.