Anmelden
 
HomeLibraryDownloadsSupportWebcasts & EventsCommunityForenBlogs
Ressourcen für IT-Professionals >
> 
> 
Removing WSUS 3.0 SP2 from a domain controller?

Answered Removing WSUS 3.0 SP2 from a domain controller?

  • Freitag, 7. Dezember 2012 21:11
     
     
    Anmelden
    0

    Yes, yes, I KNOW you're not supposed to installed MS SQL on a Server 2008 R2 domain controller.

    Someone else set up the domain controller this way, and so I am trying to correct the situation, and move WSUS to a different non-DC server.

    ,

    If I just want to remove WSUS and not reinstall it, and not preserve any data in it, is it as simple as uninstalling WSUS in the control panel?

    Will that automatically remove the databases that it uses?

    ,

    Apparantly, the Windows Internal Database is used by the 2008 R2 domain controller, so should I NOT remove it?

    http://en.wikipedia.org/wiki/Windows_Internal_Database says, it is used by:

    Active Directory Rights Management Services

    Windows System Resource Manager

    UDDI Services

    Active Directory Federation Services 2.0

    Windows SharePoint Services

    ,

    Also, this server has Faronics Core 3 on it along with SQL Server 2005. I also intend to remove both of these. I do not know if WSUS stuck its databases in SQL 2005, or in the Internal Database.

    I can not find any management consoles to tell me what databases use SQL Server 2005 or the Windows Internal Database.

    In the Start menu, there is a "SQL Server Configuration Manager" for SQL Server 2005, but it does not list databases, only service startup information and database connection methods. The "Server Manager" console also has nothing related to SQL Server.

     

Alle Antworten

  • Montag, 10. Dezember 2012 07:00
    Moderator
     
     Beantwortet
    Anmelden
    0
    Hi,

    By default,WSUS is installed with Windows Internal Database.Of course,if necessary,you can install SQL 2005,2008 for WSUS.

    If you just want to remove WSUS and not reinstall it, and not preserve any data in it! Yes. it is as simple as uninstalling WSUS in the control panel.The uninstallation wizard will walk you thru the checkbox of whether to uninstall the DB,UPDATE FILES,LOG FILES.You can completely uninstall all of them if necessary.

    In addition,Uninstalling the WSUS will not affect any other DB if you had.

    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.

     
  • Mittwoch, 12. Dezember 2012 01:15
     
     
    Anmelden
    0

    I have successfully removed the following from the 2008 R2 domain controller using Programs and Features:

    Remove WSUS 3.0 SP2 (3.2.7600.226)
    - Remove WSUS database
    - Remove Log files
    - Removed downloaded update files

    Remove Faronics Deep Freeze Loadin (for Core)
    Remove Faronics Core 3
    - Remove databases

    --------------------------------------

    The next question is if it is safe to remove SQL Server 2005. I am not a database expert so I do not know what databases are used by default for SQL, even if nothing else is using it.

    Here is what I have found:

    How to list all database files in SQL Server:
    http://www.projectenvision.com/blog/How-to-list-all-database-files-in-SQL-Server

    SQL Server 2005 Command Line Tool "SQLCMD"
    http://www.databasejournal.com/features/mssql/article.php/3654176/SQL-Server-2005-Command-Line-Tool-147SQLCMD148-150-Part-I.htm

    --------------------------------------

    My actions:

    CD C:\Program Files (x86)\Microsoft SQL Server\MSSQL.1\MSSQL\Binn
    sqlcmd -L

    Servers:
        OTHERSERVER
        OTHERSERVER\BKUPEXEC
        MYSERVER
        MYSERVER\SQLEXPRESS

    sqlcmd -SMYSERVER\SQLEXPRESS -E

    1> select d.name, m.name, m.physical_name
    2> from sys.master_files m
    3> inner join sys.databases d
    4> on (m.database_id = d.database_id)
    5> order by 1,2
    6> go

    name    name
    physical_name

    master  master
    C:\Program Files (x86)\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\master.mdf

    master  mastlog
    C:\Program Files (x86)\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\mastlog.ldf

    model   modeldev
    C:\Program Files (x86)\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\model.mdf

    model   modellog
    C:\Program Files (x86)\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\modellog.ldf

    msdb    MSDBData
    C:\Program Files (x86)\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\MSDBData.mdf

    msdb    MSDBLog
    C:\Program Files (x86)\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\MSDBLog.ldf

    tempdb  tempdev
    C:\Program Files (x86)\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\tempdb.mdf

    tempdb  templog
    C:\Program Files (x86)\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\templog.ldf

    (8 rows affected)

    7> Exit

    ---------------------------------------

    The Programs and Features list on the domain controller:

    Microsoft Report Viewer Redist 2008                - 7/29/2012
    Microsoft SQL Server 2005                              - 7/29/2012
    Microsoft SQL Server 2008 Management Tools   - 6/7/2010
    Microsoft SQL Server 2008 Native Client            - 6/7/2010
    Microsoft SQL Server Native Client                      - 7/29/2012
    Microsoft SQL Server Setup Support Files (English) - 7/29/2012
    Microsoft SQL Server VSS Writer                        - 7/29/2012
    SQL Server System CLR Types                          - 6/7/2010

    ---------------------------------------

    I don't know why it shows SQL 2008 program components, but perhaps they were installed as part of an automatic server update.

    Do the the SQL program components need to be removed in any particular order?

    Will removing any of these potentially damage the domain controller that runs on this server?

    ,

    Thanks for any assistance.


    • Bearbeitet Dale Mahalko Mittwoch, 12. Dezember 2012 01:24 formatting
    •  
     
  • Mittwoch, 12. Dezember 2012 01:40
    Moderator
     
     Beantwortet
    Anmelden
    0

    The next question is if it is safe to remove SQL Server 2005.

    That depends on whether anything else is using that instance of SQL Server 2005. Your query (Good For You!!!) shows that there are no other USER databases present on the MYSERVER\SQLEXPRESS instance. The databases master, msdb, mode, and tempdb are part of the core SQL Server installation.

    My conclusion, based on the provided information, is that it is safe to uninstall the MYSERVER\SQLEXPRESS instance.

    Do the the SQL program components need to be removed in any particular order?

    Strictly speaking no... but you might want to verify why the SQL 2008 client components are present on this machine. It may be related to one or more of these other three instances that were reported by your sqlcmd -L command.

    OTHERSERVER
    OTHERSERVER\BKUPEXEC
    MYSERVER

    Generally speaking, when you launch the SQL Server 2005 uninstaller, it will prompt you for which instances you wish to remove, and also whether you wish to remove ancillary components. However, there is no evidence that you have any SQL 2005 ancillary components installed (only SQL2008), so you probably won't get those prompts. Select the MYSERVER\SQLEXPRESS instance in the uninstall dialog, and leave any other options alone until you perform the same validations as you did for MYSERVER\SQLEXPRESS.

    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    SolarWinds Head Geek
    Microsoft MVP - Software Distribution (2005-2012)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
    The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

     
  • Dienstag, 18. Dezember 2012 22:44
     
     
    Anmelden
    0

    At this point SQL Server 2005 and all related SQL 2005/2008 components have been removed. There was only the one SQLEXPRESS database.

    Results of DCDIAG comprehensive test: dcdiag /c

    -----------------

    Directory Server Diagnosis

    ,
    Performing initial setup:

       Trying to find home server...

       Home Server = File

       * Identified AD Forest.
       Done gathering initial info.


    Doing initial required tests

      
       Testing server: Default-First-Site-Name\MYSERVER

          Starting test: Connectivity

             ......................... MYSERVER passed test Connectivity

     ,

    Doing primary tests

      
       Testing server: Default-First-Site-Name\MYSERVER

          Starting test: Advertising

             ......................... MYSERVER passed test Advertising

          Starting test: CheckSecurityError

             [MYSERVER] No security related replication errors were found on this DC!

             To target the connection to a specific source DC use /ReplSource:<DC>.

             ......................... MYSERVER passed test CheckSecurityError

          Starting test: CutoffServers

             ......................... MYSERVER passed test CutoffServers

          Starting test: FrsEvent

             ......................... MYSERVER passed test FrsEvent

          Starting test: DFSREvent

             There are warning or error events within the last 24 hours after the

             SYSVOL has been shared.  Failing SYSVOL replication problems may cause

             Group Policy problems.
             ......................... MYSERVER passed test DFSREvent

          Starting test: SysVolCheck

             ......................... MYSERVER passed test SysVolCheck

          Starting test: FrsSysVol

             ......................... MYSERVER passed test FrsSysVol

          Starting test: KccEvent

             ......................... MYSERVER passed test KccEvent

          Starting test: KnowsOfRoleHolders

             ......................... MYSERVER passed test KnowsOfRoleHolders

          Starting test: MachineAccount

             ......................... MYSERVER passed test MachineAccount

          Starting test: NCSecDesc

             ......................... MYSERVER passed test NCSecDesc

          Starting test: NetLogons

             ......................... MYSERVER passed test NetLogons

          Starting test: ObjectsReplicated

             ......................... MYSERVER passed test ObjectsReplicated

          Starting test: OutboundSecureChannels

             ** Did not run Outbound Secure Channels test because /testdomain: was

             not entered

             ......................... MYSERVER passed test OutboundSecureChannels

          Starting test: Replications

             ......................... MYSERVER passed test Replications

          Starting test: RidManager

             ......................... MYSERVER passed test RidManager

          Starting test: Services

             ......................... MYSERVER passed test Services

          Starting test: SystemLog

             An error event occurred.  EventID: 0xC0001B7A

                Time Generated: 12/18/2012   16:29:15

                Event String:

                The SQL Server (SQLEXPRESS) service terminated unexpectedly.  It has done this 1 time(s).

             ......................... MYSERVER failed test SystemLog

          Starting test: Topology

             ......................... MYSERVER passed test Topology

          Starting test: VerifyEnterpriseReferences

             ......................... MYSERVER passed test VerifyEnterpriseReferences

          Starting test: VerifyReferences

             ......................... MYSERVER passed test VerifyReferences

          Starting test: VerifyReplicas

             ......................... MYSERVER passed test VerifyReplicas

      
          Starting test: DNS

             DNS Tests are running and not hung. Please wait a few minutes...

             ......................... MYSERVER passed test DNS

      
       Running partition tests on : ForestDnsZones

          Starting test: CheckSDRefDom

             ......................... ForestDnsZones passed test CheckSDRefDom

          Starting test: CrossRefValidation

             ......................... ForestDnsZones passed test

             CrossRefValidation

      
       Running partition tests on : DomainDnsZones

          Starting test: CheckSDRefDom

             ......................... DomainDnsZones passed test CheckSDRefDom

          Starting test: CrossRefValidation

             ......................... DomainDnsZones passed test

             CrossRefValidation

      
       Running partition tests on : Schema

          Starting test: CheckSDRefDom

             ......................... Schema passed test CheckSDRefDom

          Starting test: CrossRefValidation

             ......................... Schema passed test CrossRefValidation

      
       Running partition tests on : Configuration

          Starting test: CheckSDRefDom

             ......................... Configuration passed test CheckSDRefDom

          Starting test: CrossRefValidation

             ......................... Configuration passed test CrossRefValidation

      
       Running partition tests on : mydomain

          Starting test: CheckSDRefDom

             ......................... mydomain passed test CheckSDRefDom

          Starting test: CrossRefValidation

             ......................... mydomain passed test CrossRefValidation

      
       Running enterprise tests on : mydomain.internal

          Starting test: DNS

             ......................... mydomain.internal passed test DNS

          Starting test: LocatorCheck

             ......................... mydomain.internal passed test

             LocatorCheck

          Starting test: FsmoCheck

             ......................... mydomain.internal passed test

             FsmoCheck

          Starting test: Intersite

             ......................... mydomain.internal passed test

             Intersite

    ----------------

    So, looks like the domain controller is working properly after removing SQL Server 2005. Is there anything else that should be checked, health-wise?