Hi Tim,
Yes, this is what we are seeing. And, in fact, I read the whole
README... and even remember now reading this part. Guess it was a long
day. My apologies to the list for sending unnecessary mail. And thank you
Tim for bringing this back to my attention.
Do you know if it is targetted to be fixed in future patches or
releases? The obvious concern is that it may cause confusion for our user
population.
Thanks!
Jennifer
At 06:27 PM 1/9/2001, you wrote:
The following is in the readme:
- IMPORTANT NOTE REGARDING A KNOWN UNINSTALL ISSUE:
- Issue: Grey desktop on uninstall. There is an issue that has been
seen on some systems with Active Desktop installed. The symptoms
are that after an uninstall the desktop will turn grey and the
desktop icons will not be visible. The system will continue to work
otherwise. The desktop is restored as soon as you log off and log
back on. The problem is that Installshield will attempt to remove
the All Users desktop folder if the TSM desktop icons are the only
items in the folder. The problem is that the desktop folder is a
protected system folder and can't be removed. This issue will be
addressed in the future. For now, if you see this problem, simply
log off and log back on to reset the desktop.
Is this what you are experiencing?
Tim Rushforth
City of Winnipeg
[EMAIL PROTECTED]
-Original Message-
From: Jennifer I. Moore [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, January 09, 2001 4:26 PM
To: [EMAIL PROTECTED]
Subject: Client v4.1.2 -- Uninstall on NT results in blank desktop?
Gentle Greetings,
We've noticed a strange behavior when uninstalling TSM client v4.1.2 on an
NT 4.0 Workstation system (SP5). When the Add/Remove Programs process
finishes, the desktop goes to a blank grey screen with only the Start menu
and Task Bar showing. Right-clicking in the grey area results in a Desktop
message as follows:
C:\WINNT\Profiles\All Users\Desktop is not accessible. Access is
denied. Retry. Cancel.
Retry results in the same message. Cancel returns to the blank grey
screen. The only way we've found to get out of this is to restart the
machine. (Fortunately, the Start menu still works fine, so it's not
necessary to be brutal about the restart.)
Has anyone else noticed this behavior?
Thank you in advance for any help, information, and/or shared experiences.
Jennifer
