Company merger scenario - two seperate WSUS

Discussion in 'Update Services' started by Ian Rowley, Oct 8, 2008.

  1. Ian Rowley

    Ian Rowley Guest

    I have the following scenario:

    Company A & Company B have merged. They each have their own WSUS services.

    Comp A's is configured for manual approvals and a large variety of update
    types & software.

    Comp B's is configured for automatic approval/install of OS critical and
    security updates only.

    They are effectively on the same network and there is a trust between the
    two AD forests.

    The plan is for everything to eventually migrate to Comp B. Can Comp A just
    change the GPO to point to the WSUS server in Comp B? My reading so far
    suggests not. If not, then how to "migrate" clients to WSUS in Comp B?
    Bearing in mind this is before any AD migration - that's a headache for
    another time!

    Any help, info or tips appreciated

    cheers

    IAn
     
    Ian Rowley, Oct 8, 2008
    #1
    1. Advertising

  2. "Ian Rowley" <> wrote in message
    news:...
    >I have the following scenario:
    >
    > Company A & Company B have merged. They each have their own WSUS services.
    >
    > Comp A's is configured for manual approvals and a large variety of update
    > types & software.
    >
    > Comp B's is configured for automatic approval/install of OS critical and
    > security updates only.
    >
    > They are effectively on the same network and there is a trust between the
    > two AD forests.
    >
    > The plan is for everything to eventually migrate to Comp B. Can Comp A
    > just
    > change the GPO to point to the WSUS server in Comp B?


    Absolutely. The auto-approval rules of Company B are applied by GROUPNAME.
    The auto-install rules are applied by POLICY.

    As long as you create the Company A GROUPNAMEs on the Company B WSUS Server,
    it is as simple as redirecting the clients to the new server.

    Remember this: WSUS knows *nothing* about Active Directory or AD/domain
    membership.

    Group Policy is used merely as a mechanism for loading configuration data
    into the registry of the client.

    Once the client is configured, the WSUS Server and the client are oblivious
    to the presence or absence of Active Directory.

    --
    Lawrence Garvin, M.S., MCITP(x2), MCTS(x5), MCP(x7), MCBMSP
    Principal/CTO, Onsite Technology Solutions, Houston, Texas
    Microsoft MVP - Software Distribution (2005-2009)

    MS WSUS Website: http://www.microsoft.com/wsus
    My Websites: http://www.onsitechsolutions.com;
    http://wsusinfo.onsitechsolutions.com
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
     
    Lawrence Garvin, Oct 8, 2008
    #2
    1. Advertising

  3. Ian Rowley

    Ian Rowley Guest

    thanks for the quick reply

    clearly i misunderstood a couple things;)

    cheers

    IAn
    "Lawrence Garvin" wrote:

    > "Ian Rowley" <> wrote in message
    > news:...
    > >I have the following scenario:
    > >
    > > Company A & Company B have merged. They each have their own WSUS services.
    > >
    > > Comp A's is configured for manual approvals and a large variety of update
    > > types & software.
    > >
    > > Comp B's is configured for automatic approval/install of OS critical and
    > > security updates only.
    > >
    > > They are effectively on the same network and there is a trust between the
    > > two AD forests.
    > >
    > > The plan is for everything to eventually migrate to Comp B. Can Comp A
    > > just
    > > change the GPO to point to the WSUS server in Comp B?

    >
    > Absolutely. The auto-approval rules of Company B are applied by GROUPNAME.
    > The auto-install rules are applied by POLICY.
    >
    > As long as you create the Company A GROUPNAMEs on the Company B WSUS Server,
    > it is as simple as redirecting the clients to the new server.
    >
    > Remember this: WSUS knows *nothing* about Active Directory or AD/domain
    > membership.
    >
    > Group Policy is used merely as a mechanism for loading configuration data
    > into the registry of the client.
    >
    > Once the client is configured, the WSUS Server and the client are oblivious
    > to the presence or absence of Active Directory.
    >
    > --
    > Lawrence Garvin, M.S., MCITP(x2), MCTS(x5), MCP(x7), MCBMSP
    > Principal/CTO, Onsite Technology Solutions, Houston, Texas
    > Microsoft MVP - Software Distribution (2005-2009)
    >
    > MS WSUS Website: http://www.microsoft.com/wsus
    > My Websites: http://www.onsitechsolutions.com;
    > http://wsusinfo.onsitechsolutions.com
    > My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
    >
     
    Ian Rowley, Oct 8, 2008
    #3
    1. Advertising

Want to reply to this thread or ask your own question?

It takes just 2 minutes to sign up (and it's free!). Just click the sign up button to choose a username and then you can ask your own questions on the forum.
Similar Threads
  1. Donald

    Merger question

    Donald, Feb 27, 2006, in forum: Windows Server
    Replies:
    1
    Views:
    233
    Marc Everlove
    Feb 28, 2006
  2. CNC

    Restructure Domains - Company Merger

    CNC, Sep 21, 2005, in forum: Active Directory
    Replies:
    5
    Views:
    172
    Paul Williams [MVP]
    Sep 21, 2005
  3. UselessUser

    Multiple company merger

    UselessUser, May 10, 2009, in forum: Active Directory
    Replies:
    2
    Views:
    240
    Ace Fekay [Microsoft Certified Trainer]
    May 10, 2009
  4. Ray
    Replies:
    2
    Views:
    1,031
    Jeff Cochran
    Jan 13, 2004
  5. Tim_S

    Open IE seperate process and seperate window

    Tim_S, Dec 9, 2009, in forum: Internet Explorer
    Replies:
    1
    Views:
    818
    rob^_^
    Dec 9, 2009
Loading...

Share This Page