Masuk
 
AwalPerpustakaanWikiPelajariUnduhDukunganKomunitasForum
Resources for IT Professionals >
> 
> 
Remove WSUS, WINDOWS INTERNAL DATABASE ( brute force) and unable to REINSTALL - HELP ME JESUS

Jawab Remove WSUS, WINDOWS INTERNAL DATABASE ( brute force) and unable to REINSTALL - HELP ME JESUS

  • 26 Juli 2012 17:41
     
     
    Masuk untuk Memilih
    0
    Sorry by the English. I have a windows server 2008 R2 with ADDS. Was working normal with WSUS, however I needed to change the drive where the files were originally. (g:\wsus to z:\wsus).

    The whole problem started when I changed the location of this drive. After frustrated attempts to remove WSUS realized the procedure below, and then things just got worse.

    -Deleted the registry keys HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Update Services
    -deleted the WSUS service entries in HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services
    -deleted HKLM\Software\MicrosoftSQLServer\MSSQL.2005
    -changed the key value of 1 for 12:0 am wYukonInstalled [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Update Services\Server\Setup]
    -ran the command msiexec\/x {CEB5780F-1A70-44A9-850F-DE6C4F6AA8FB} callerid = ocsetup.exe, however reported q there was no product installed, still appears in the windows functions 2008-wsus ran the diagnostic tool and the result was: WSUS Client Diagnostics Tool
    Checking Machine State
            Checking for admin rights to run tool ... ... . PASS
            Automatic Updates Service is running ... ... .... PASS
            Background Intelligent Transfer Service is running ... PASS
    GetFileVersion (szEngineDir, & susVersion) failed with hr = 0x80070002
    The system cannot find the file specified.

    -installed windows installer clean up and removed WSUS and Windows internal database, but Wsus remains in the list of role manager functions
    -removed the keys in regedit related to Windows internal database
    -did the wsus download separately and when trying to install the following error occurs: 7\/24\/2012 12:43:14 Success MWUSSetup Validating pre-requisites ...
    7\/24\/2012 12:43:15 Error MWUSSetup WSUS is outdated. But this will not block setup (0x00000000 Error: the operation completed successfully.)
    7\/24\/2012 12:43:19 Success MWUSSetup ReportViewer is not installed on this machine
    7\/24\/2012 12:43:19 Success MWUSSetup ReportViewer is not installed on this machine
    7\/24\/2012 12:44:02 Success MWUSSetup Initializing installation details
    7\/24\/2012 12:44:02 Success MWUSSetup Skipping Asp.Net install since not running on win2k3 ...
    12:44:02 Success MWUSSetup Installing wYukon 7\/24\/2012 using ocsetup
    7\/24\/2012 12:44:02 Success MWUSSetup Installing Windows Internal database using ocsetup with command line as "\/norestart\/quiet" WSSEE "ocsetup"
    7\/24\/2012 12:44:16 Error MWUSSetup The process ocsetup "WSSEE"\/quiet\/norestart returned error: 0x643 (Error 0x80070643: fatal error during installation.)
    7\/24\/2012 12:44:16 Error MWUSSetup ExecCmd failed (Error 0x80070643: fatal error during installation.)
    7\/24\/2012 12:44:16 Error MWUSSetup Install Windows Internal database: Failed to execute "\/quiet"\/norestart WSSEE "ocsetup" (Error 0x80070643: fatal error during installation.)
    12:44:16 Error MWUSSetup CInstallDriver: 7\/24\/2012: PerformSetup: Installation of wYukon failed (Error 0x80070643: fatal error during installation.)
    Error MWUSSetup CSetupDriver: 7\/24\/2012 12:44:16: Files\installshield: Setup failed (Error 0x80070643: fatal error during installation.)

    Has anyone managed to resolve this problem, Microsoft does not have any tool to remove Windows Internal Database and WSUS or reinstall in force so that it can be solved these problems?  Or q is due to this problem will have q adopt the old method microsoft and reinstall everything from scratch?

    These stops that discourage to use MS.

    SOME LIT, MCSE, MCP, some guy can give help to resolve this problem?

    Since already thank you all.
     

Semua Balasan

  • 27 Juli 2012 6:07
    Moderator
     
     Jawab
    Masuk untuk Memilih
    0
    Hi,

    It seems that you didn't fully uninstall the DB of your previous wsus.

    Have you reviewed the Sticky Post at the top of this forum that documents comprehensive, proven procedures for cleaning WSUS out of a system?

    Try it and reinstall the whole WSUS from scratch.

    Also note:Installing WSUS on DC is not a good practice.I have encountered the case that is finally resolved by migrating FSMO roles and other critical domain information, formatted the server, installed as new and migrated everything back. I can only assume that there was something corrupt or missing in the registry.

    Best regards,

    Clarence

    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.