RDP 6.0

[johnsolver]

I just installed RDP 6.0 for wxp sp2, regretfully, right after drive
sharing \\tsclient etc. stopped working. I checked the policy settings
localy (which aren't changed) and are OK, connecting from a different
machine to the server still works as expected (including drive
sharing).

I'm at a loss, btw I tried uninstalling the update and returning to the
previous version of mstsc but it didn't help, now even with the older
RDP drive sharing doesn't work.

Anyone?

 

[Sooner Al [MVP]]

Have you tried going back to a previous restore point to recover?

--

Al Jarvi (MS-MVP Windows Networking)

Please post *ALL* questions and replies to the news group for the
mutual benefit of all of us...
The MS-MVP Program - http://mvp.support.microsoft.com
This posting is provided "AS IS" with no warranties, and confers no
rights...

 

[johnsolver]

Nope, I did uninstall the update but I don't have the restore service
running so I can't revert.

 

[Sooner Al [MVP]]

Well, the only thing I can suggest is to...

1. Reinstall the RDP 6.0 client and see if that fixes the issue then if it
does not...
2. Uninstall the RDP 6.0 client and see if that fixes the issue.

You also might run the "sfc /scannow" command after uninstalling the RDP 6.0
client. Go to "Help and Support" and search on sfc for the exact command
syntax and options...

I would also turn on/enable system restore. It can be invaluable at times,
IMHO...

Good luck...

--

Al Jarvi (MS-MVP Windows Networking)

Please post *ALL* questions and replies to the news group for the
mutual benefit of all of us...
The MS-MVP Program - http://mvp.support.microsoft.com
This posting is provided "AS IS" with no warranties, and confers no
rights...

 

[MicroFox]

turning off the restore service is one of the biggest mistakes the self
proclaimed
"power users" do.

A knowledgeable tech never turns it off, because it can save them from
things,
just like you encountered now.

 

[Dave B.]

I would tend to disagree with that statement.

 

[Shenan Stanley]

<snipped previous conversations>

Nope, I did uninstall the update but I don't have the restore
service running so I can't revert.

turning off the restore service is one of the biggest mistakes the
self proclaimed "power users" do.

A knowledgeable tech never turns it off, because it can save them
from things, just like you encountered now.

I would tend to disagree with that statement.

It's a double-edged sword.

I have seen System Restore save people from some stupid-to-serious issues.
I have also seen System Restore fail to save people from some
stupid-to-serious issues.

System restore, without a consistant backup regime to fall back on as well,
is not as useful as one might think. I believe that a systematic backup
regime would give you more ability to return to a better state than System
Restore. Combine the two - and I would agree with a statement like...

'A person who is serious about protecting their data and who has taken the
time to understand the reasons/methods behind doing so will keep system
restore enabled (cleaning up all but the last restore point periodically)
and will maintain a full system backup on a strict schedule.'

A 'knowledgeable tech' may/may not turn off the system restore dependent on
the situation. I tend to turn it off on my machines in open access lab
environments. It is faster and easier to rollout a new installation on all
of the machines than to try and use system restore on xxxx number of
machines. I tend to leave it on for machines that will be going home with
customer x and who has my tips on how to maintain their system properly in
hand (and I have ran them through it once - usually.)

'Never' is a word that I find difficult to use.
It seems to rarely have a place when you have reality involved. =)

 

[V.J.]

My installation of RDP 6.0 for XP don't seem to have an uninstall feature,
at least none that I can find. I checked the Add/Remove Programs as well as
the Add/Remove Windows Components and couldn't find it, even after two
reboots. I installed RDP 6.0 using both the Windows Update and the setup
file itself. Any idea what went wrong?

 

[MicroFox]

system restore is ONE of the tools you use, disk imaging with a tool like
acronis
is another.

Why limit your options to save your pc

 

[MicroFox]

lol, you are one of "them"?

wisen up lad....

I would tend to disagree with that statement.

--

 

[MicroFox]

how about clicking that little show windows updates box on the add remove
window?

 

[Shenan Stanley]

<snipped previous conversations>

Nope, I did uninstall the update but I don't have the restore
service running so I can't revert.

turning off the restore service is one of the biggest mistakes the
self proclaimed "power users" do.

A knowledgeable tech never turns it off, because it can save them
from things, just like you encountered now.

I would tend to disagree with that statement.

It's a double-edged sword.

I have seen System Restore save people from some stupid-to-serious
issues. I have also seen System Restore fail to save people from
some stupid-to-serious issues.

System restore, without a consistant backup regime to fall back on
as well, is not as useful as one might think. I believe that a
systematic backup regime would give you more ability to return to
a better state than System Restore. Combine the two - and I would
agree with a statement like...

'A person who is serious about protecting their data and who has
taken the time to understand the reasons/methods behind doing so
will keep system restore enabled (cleaning up all but the last
restore point periodically) and will maintain a full system backup
on a strict schedule.'
A 'knowledgeable tech' may/may not turn off the system restore
dependent on the situation. I tend to turn it off on my machines
in open access lab environments. It is faster and easier to
rollout a new installation on all of the machines than to try and
use system restore on xxxx number of machines. I tend to leave it
on for machines that will be going home with customer x and who
has my tips on how to maintain their system properly in hand (and
I have ran them through it once - usually.)
'Never' is a word that I find difficult to use.
It seems to rarely have a place when you have reality involved. =)

system restore is ONE of the tools you use, disk imaging with a
tool like acronis
is another.

Why limit your options to save your pc

We have not disagreed. You are just limiting your scope too much in my
opinion.

In a lab environment where I have 1500 machines and 40,000+ users that have
access to those machines (limited access) - and I can redo all of them in
hours (or a single machine in a matter of minutes) - why would I have system
restore so I could save one identical machine from another sitting right
next to it? What advantage does it actualy give me in said environment?

As I said,

'A person who is serious about protecting their data and who has
taken the time to understand the reasons/methods behind doing so
will keep system restore enabled (cleaning up all but the last
restore point periodically) and will maintain a full system backup
on a strict schedule.'

However - there are places where none of that is necessary. Public use
machines that get periodically wiped and updated are prime examples. Things
should be setup in such a way that (1) the users cannot do much of anything
to the machines and (2) if something goes wrong you can - en masse - rebuild
quickly; from scratch if needed. There is no data stored on the machines
(user data) and the users cannot do anything to them.