Monitor said:
I sense a contradiction here. Someone who looks after 10,000 PCs knows about
scripting, so why post here? Someone who does not know about scripting could
not effectively look after 10,000 PCs. Time to align your skills with your
job requirements?
Too funny there guy (or gal), way to address the actual question instead of
taking it off in a completely different direction....oh wait......
I have an evironment where the care and feeding of workstations has been
sorely neglected for quite some time. As a result of this, workstation
registries have become bloated (well more bloated than normal). I'm not in
charge of managing the workstations but I am attempting to correct a
potential performance issue. I have no trouble creating GPOs or .reg file
pushes that add or modify the registry but in this case, we are migrating
from a Novell F&P environment where numerous legacy entries referencing the
old Novell environment exist in workstation registries. Rather than try and
map out each and every key (just a cursory investigation of a single
workstation has revealed at least 50 unique instances and I expect a lot
more), I was hoping to find the best way to find and delete these left over
entries. In most cases, these entries can just sit there but unfortunately,
in some cases it creates some performance issues as those connections (such
as printers) are attempted to be made and eventually time out.
Maybe I'm missing something but the search results I get contain a ton of
information about how to add information to or modify (i.e change values) for
existing information but not how to perform deletions using keyword
information.
Apparently, this is not the place to actually get helpful and/or useful
suggestions.
I will continue to search elsewhere.