problems when remote management of all win xp pro sp2 workstations

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

After installing KB925902 on all windows 2000 / xp workstations in our
network remote management via computer management, it reveals problems when
remotely

managing all win xp sp2 workstations from any computer.


Computer Management - Connect to another computer: (select any Windows XP
SP2 x86 or x64 based machine that has KB925902 applied):

- Event Viewer - "Unable to connect to the computer ComputerName. the error
was: The network path was not found." after KB925902 was installed on remote

Computer. Event viewer on remote computer still cannot connect even if both
local and remote firewalls are turned off.

- Device Manager - "Unable to access the computer ComputerName The error
was: Access is denied."

- Performance Logs and Alerts - "The version of the operating system on the
computer named COmputerName is later than that on the local computer. This

operation is not available from the local computer."

- at the same time other remote management features, e.g. Disk Management,
Shared Folders, Services etc. still work fine.


That will not happen if you connect to any Windows 2000 SP4 based machine
with applied KB925902. What is the problem? why so many features of remote

management fails after installing the latest critical update to Windows XP
OS family?
 
wanted to clarify my previous post which was a bit to chaotic I think.

First of all we have mixed windows environment including:
a) 2 windows 2003 sp2 x86 servers (all patches applied except for April 3rd
release)
b) 2 windows 2000 sp4 x86 servers (all patches applied except for April 3rd
release)
c) 19 windows xp sp2 (both x86 and x64) workstations with all patches
applied including the April 3rd release
d) 11 windows 2000 sp4 workstations with all patches applied including the
April 3rd release
e) 1 windows me workstation

All our servers are domain controllers and also DNS servers. Our PDC also is
a File server & Print server.

Until April 3rd all components of MMC (or Computer Management COnsole) were
working fine for local and remote connections. There were no recent changes
in firewall policy or other GPO changes.

NEW: in my previous post I made a mistake saying that windows 2000
workstations were not affected by remote MMC component problem. In fact they
ARE as well as all Windows XP family workstations.

Currently the only workstation (Windows XP Pro SP2 x86) that I could connect
to using remote MMC components is the one that applied the most recent
critical security patch from April 3rd, but was not rebooted yet. ALL others
were unfortunately rebooted since applying KB925902 and therefore they refuse
remote connections for following MMC components:
a) event viewer
b) device manager
c) performance logs and alerts
d) rest, e.g. Disk Management, Shared Folders, Services still work fine with
no errors.

Moreover uninstalling the patch KB925902 from workstation DOES NOT solve the
problem. Please advise.
 
sorry to reply myself, but this forum does not have EDIT option!
anyway I am still digging the issue of MMC problems after installing
KB925902 on windows 2000 / xp systems.

workstations without KB925902 I will call "clean", and those with applied
KB925902 (and rebooted afterwards) I will call "affected".

It seems that a clean machine (2003 server in this case) cannot make
successful MMC connection to affected Event Viewer, Device Manager, etc -
incoming connections are refused for mentioned above components.
Just discovered that also outgoing MMC connections from affected box to a
clean box are also rejected with same error messages as above! moreover none
of those events is being logged in Application or System log.

Worst thing is that uninstalling this damn update KB925902 DOES NOT HELP, it
stays discrupted!! how to fix it? how to successfully remove this "critical
security update" KB925902???

By the way I spent over 2 hours on the phone with Microsoft Product Support
Services at 1-866-PCSAFETY, telling them about the problem with this hotfix
and the side-effects of it. I spoke to 5 people so far (customer service,
techncial support, etc.) but my call instead of being forwarded to
Troubleshooting team was put on hold for 30 minutes and finally was
disconnected.

My troubleshooting case number is srx070405601164. I request someone call me
back, since after I was transferred a dozen times between MS departments, I
don't even know what number to call back...
 
good news :)

yesterday spent 5 hrs on the phone with MS Support team with no much
effects. Fortunately today after about 1.5 hrs a MS Tech found the cause!!
Thanks to Nikhil Sharma it came up that one service startup type was changed
to Manual instead of Automatic after KB925902 installation. That service is
Remote Registry which is crucial to the remote features of MMC like Event
Viewer, Perf. Logs and Alerts and Device Manager :)

So to all people that cannot use remote MMC features mentioned above after
installation of KB925902 all over their networks: double check your domain
GPO Computer Configuration - Windows settings - Security Settings - System
Services and make sure the service Remote Registry is set to Automatic and
you'll be OK :)

That was the issue in our case. Thanks again and wish everybody nice weekend
and Happy Easter :)
 
Back
Top