Posted on September 10th, 2009
Windows 2008 has some icons that appear in the systray by default. The network icon is an example that appears even in a terminal server or Citrix session, as shown:
It is un-necessary clutter that would be best to remove in the terminal server session. However, there is no Group Policy option to do this in a Windows 2003 domain.
The following registry keys are available and can be used to remove all the systray icons:
These can be added as a REG_DWORD and set to 1 to enable the setting.
They can also be added to the HKCU hive if required.
Posted on July 8th, 2009
I have been experiencing some strange crashes of the following services:
- Citrix Independent Management Architecture (IMA) – ImaSrv.exe
- Citrix Print Manager Service – CpSvc.exe
These were happenning on a Windows 2003 x64 Standard Edition R2 server with Citrix XenApp 4.5 R04.
While investigating the problems I also noted the following error while trying to open task manager. Either CTRL-SHIFT-ESC, CTRL-ALT-DEL and selecting it or right click taskbar and selecting gave the same results. The task manager icon appeared in the systray but task manager never appeared. For every attempt to open task manager added another icon in the systray but never opened it.
Waiting for anywhere from a few minutes to several hours, eventually task manager opened.
Associated problems appeared to be that WMI was breaking regularly. The MOF databases could be rebuilt to resolve this (as per this article RP492)
All of these problems appeared to be a result of the following registry setting:
reg_dword: 120 (dec)
Changing this value back to it’s default of
reg_dword: 2592000 (dec)
Resovled all the issues and after a week none of them have re-occurred.
If I get any more info about why this is happenning, I will add to this post.
File Name Warning: There is a file or folder on your computer called c:\program causing problems. Rename?
Posted on June 26th, 2009
Have seen the following error while logging onto a server:
File Name Warning
There is a file or folder on your computer called “c:\program” which could cause certain applications to not function correctly. Renaming it to “c:\program1″ would solve this problem. Would you like to rename it now?
Rename | Ignore
This error occurred on a server that has previously been a Citrix License server and the tool lmdiag.exe had been run on the server creating the following file:
in the root of the c: drive.
Opening this file in notepad shows:
lmdiag – Copyright (c) 1989-2006 Macrovision Europe Ltd. and/or Macrovision Corporation. All Rights Reserved.
FLEXlm diagnostics on Thu 9/6/2009 09:46
To resolve the problem, simply remove or rename the file
It seems that lmdiag has a bug or coding error which generated this rogue file.
Posted on June 17th, 2009
By default, when Office 2003 is installed, the Microsoft Office document image writer appears in the printers folder, as shown:
Here is a really easy way of removing the Microsoft Office document image writer printer via a script.
- cscript c:\windows\system32\prnmngr.vbs -d -p “Microsoft Office Document Image Writer”
This can be added to a build sctipt if needed.
Posted on May 15th, 2009
The symbols paths need to be set correctly to correctly identify the relevant information. This can be done for Microsoft and Citrix symbols as their symbols paths are in the public domain. Other associated companies, such as Appsense, do not publicly release their symbols so you are unable to link to them. The entry in windbg needs to be set for the following to set the MS and Citrix symbols paths:
To open a crash dump file, select file | open crash dump
Select the file in question
After a few seconds the dump loads and the entry bar at the bottom of the window will become active. The following commands may be useful:
Will show a verbose analysis of the dump file. The important information is at the end of the text that appears. The process that caused the fault will be listed along with the errors.
To get more information about the module use the following command:
lmv m “module name”
It is also possible to use windbg to force a dump of a running / crashing process.
File | Attach to process & Select the process
Chose to save the workspace
A white dialog box is then generated
In the command window of the debugger, enter the following:
.dump /ma c:\mydump.dmp
If I find any more public symbol paths, I will update this entry.