Links to sources for Terminal Server printing issues/fixes

Microsoft Technet - Configure settings for mapping client devices - link

Brian Madden - The Ultimate Guide to Terminal Server Printing - Design and Configuration - link

Brother Printers - Universal print drivers for Terminal Servers and Citrix - link

MS Terminal Services Blog - Windows Terminal Services Printing - link

Microsoft - Terminal Server Printer Redirection Wizard Tool - link

Microsoft - Choosing the right printer drivers - link

KTS - Terminal Server category - link

I recently experienced an issue where my Motorola Q9c from Verizon was hanging up for 1 - 2 minutes when I would try to unlock the screen.  Normally, you press the unlock soft key and the screen will display a prompt to press the * key to complete the unlock process.  With the problem I experienced, it was hanging before showing me that prompt and my phone would be unusable for about 1 - 2 minutes.  After this happened, I checked my task manager and found the “Text Messages” process consuming a good chunk of resources.  I forced this to quit and my phone would be fine until I wrote another text messsage and that process respawned. 

After trying a few things, I found that this issues was actually caused by the text prediction feature and the size of the text prediction history cache.  If you are having the same problem, try turning this feature off, or at least clearing the history.  Here’s how:

1. Select “Text Input Settings” from the main settings menu.
2. To Disable this feature, clear the “Suggest words when typing” option
3. To clear the history, access the menu by using the right soft key and select “Clear Input History”

I recently experienced a strange issue with a client where office documents from Word and Excel (.doc and .xls) would open very slowly when double clicked.  If you first opened the respective application and then selected the document from the open menu, it would open almost instantly.  After exhaustive research, I found the issue was related to the Dynamic Data Exchange (DDE) settings for those applications.  More on DDE can be found here.

The corrective action was to modify the “Application used to perform this action” string in the DDE settings.  Here it is step-by-step:

1. Open folder options from within the control panel.
2. Select the tab for file types.
3. From the list, select the document extension you are having trouble with (.doc or .xls)
4. Click the advanced button
5. Append the string “%1″ including the quotes to the end of the existing “Application used to perform this action” string.  If the existing string ends with a “/dde” remove that.
6. Click OK and try again.

With the newer versions of Backup Exec and Exchange 2007, Granular Recovery Technology (GRT), a requirement of the Microsoft Exchange Server MAPI Client and Collaboration Data Objects needs to be downloaded and installed on the Exchange/Media server. Microsoft has updated the Mapi and CDO to 1.2.1 to include Windows Server 2003 and Windows Server 2008. 64bit servers have no problem installing.

Link to download.