feniks Posted April 5, 2007 Report Share Posted April 5, 2007 After installing KB925902 on all windows 2000 pro sp4 / xp pro sp2 workstations in our network, the remote management via computer management reveals problems when remotely managing all win xp sp2 workstations with KB925902 applied.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? Quote Link to comment Share on other sites More sharing options...
feniks Posted April 5, 2007 Author Report Share Posted April 5, 2007 bad news. all windows 2000 pro sp4 workstations were also affected. just performed a double check. same problems with remote Management via MMC as with win xp pro sp2 workstations.the only computer I can currently remotely manage is a Windows XP Pro SP2 that applied the KB925902 but has not rebooted yet. surely after reboot it will experience the same troubles. Quote Link to comment Share on other sites More sharing options...
Scarecrow Man Posted April 5, 2007 Report Share Posted April 5, 2007 This may be something Microsoft is unaware of.Free security patch related support - 1-866-PCSAFETYhttp://go.microsoft.com/fwlink/?LinkId=21131 Quote Link to comment Share on other sites More sharing options...
feniks Posted April 5, 2007 Author Report Share Posted April 5, 2007 yep. I spent almost 5 hours on the phone support since the morning calling the same number you posted. still they do not know what that is. will continue tomorrow. good thing that calling the mentioned phone number is free and the same support normally is paid $250. anyway they in deed were not aware of the problem. will post again soon.This may be something Microsoft is unaware of.Free security patch related support - 1-866-PCSAFETYhttp://go.microsoft.com/fwlink/?LinkId=21131 Quote Link to comment Share on other sites More sharing options...
feniks Posted April 5, 2007 Author Report Share Posted April 5, 2007 just for the record:I also post this info to Microsoft Technet forum (wchich is actually almost dead) at:http://www.microsoft.com/technet/community...b8a0c9d&p=1wanted to clarify my previous post which was a little bit too chaotic I think.First of all we have mixed windows domain environment including:a) 2 windows 2003 sp2 x86 servers (all patches applied except for April 3rdrelease)B) 2 windows 2000 sp4 x86 servers (all patches applied except for April 3rdrelease)c) 19 windows xp sp2 (both x86 and x64) workstations with all patchesapplied including the April 3rd released) 11 windows 2000 sp4 workstations with all patches applied including theApril 3rd releasee) 1 windows me workstationAll our servers are domain controllers and also DNS servers. Our PDC also isa File server & Print server.Until April 3rd all components of MMC (or Computer Management COnsole) wereworking fine for local and remote connections. There were no recent changesin firewall policy or other GPO changes.Currently the only workstation (Windows XP Pro SP2 x86) that I could connectto using remote MMC components is the one that applied the most recentcritical security patch from April 3rd, but was not rebooted yet. ALL otherswere unfortunately rebooted since applying KB925902 and therefore they refuseincoming remote MMC connections (& outgoing to other computers) for following MMC components:a) event viewerB) device managerc) performance logs and alertsd) rest, e.g. Disk Management, Shared Folders, Services still work fine withno errors.Moreover uninstalling the patch KB925902 from workstation DOES NOT solve theproblem.workstations without KB925902 I will call "clean", and those with appliedKB925902 (and rebooted afterwards) I will call "affected".It seems that a clean machine (2003 server in this case) cannot makesuccessful 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 aclean box are also rejected with same error messages as above! moreover noneof those events is being logged in Application or System log.Worst thing is that uninstalling this damn update KB925902 DOES NOT HELP, itstays discrupted!! how to fix it? how to successfully remove this "criticalsecurity update" KB925902???By the way I spent a total over 5 hours on the phone with Microsoft Product SupportServices at 1-866-PCSAFETY, telling them about the problem with this hotfixand the side-effects of it. I spoke to 5 people so far (customer service,techncial support, etc.) but my call instead of being forwarded toTroubleshooting team was put on hold for 30 minutes and finally wasdisconnected. had to call them again, but in the end had to go home, so will continue the case on tommorow. Quote Link to comment Share on other sites More sharing options...
feniks Posted April 6, 2007 Author Report Share Posted April 6, 2007 good news :)yesterday spent 5 hrs on the phone with MS Support team with no mucheffects. 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 changedto Manual instead of Automatic after KB925902 installation. That service isRemote Registry which is crucial to the remote features of MMC like EventViewer, Perf. Logs and Alerts and Device Manager :)So to all people that cannot use remote MMC features mentioned above afterinstallation of KB925902 all over their networks: double check your domainGPO Computer Configuration - Windows settings - Security Settings - SystemServices and make sure the service Remote Registry is set to Automatic andyou'll be OK :)That was the issue in our case. Thanks again and wish everybody nice weekendand Happy Easter :) Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.