RE: 2.0 CAP and 2003 MP on the same server

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: Bill (Bill_at_discussions.microsoft.com)
Date: 03/01/05 

Date: Tue, 1 Mar 2005 07:27:03 -0800

Yes, I'm doing a side-by-side. I have already installed the MP on my 2003
Site Server (as I saw 2.0 and 2003 were obviously not going to work together,
as you have confirmed) and will migrate all clients to 2003 before
uninstalling 2.0 on that particular server and upgrading it to 2003.

Thanks, Matt.

"Matt Goedtel [MSFT]" wrote:

> Bill,
>
> On a SMS 2003 Site Server the CAP and MP role can co-exist. However, if you
> are trying to use a SMS 2.0 Site Server with the CAP role serve as a SMS 2003
> MP - not possible. Only SMS 2003 can have the CAP and MP role co-exist,
> mainly for supporting legacy clients in an SMS 2003 site and during migration
> effort from 2.0 to 2003.
>
> I assume you are looking to do a side-by-side migration?
> If so you should review the "Scenarios and Procedures for SMS 2003:
> Planning and Deployment". There are sections specific to Upgrading/Migrating
> from SMS 2.0 that can help you.
>
> Regards,
>
> Matt Goedtel [MSFT]
> "This posting is provided AS IS with no warranties and confers no rights."
> "Bill" wrote:
>
> > I was lead to believe that a 2.0 CAP and a 2003 MP could exist on the same
> > server. I have a server that is serving as a 2.0 CAP/DP and have tried to
> > install it as a 2003 MP (side-by-side migration) and am receiving the
> > following message in the SMS_SITE_COMPONENT_MANAGER log:
> >
> > "SMS Site Component Manager has detected that site system TORSMSDIST is
> > currently in use by SMS site TOR."
> >
> > Was I misled? Can they not co-exist? If so, should I use the Primary Site
> > server as an MP for now and move it once I migrate all clients and then tear
> > down the 2.0 site?
> >
> > I have two servers at the Primary Site - one acting as the Primary Site
> > server with the SQL database and provider, and the other acting as a CAP/DP.
> >
> > Thank you.

Relevant Pages

  • Re: Clients Discovered but not assigned to site
    ... role on the SMS Site Server you're using. ... Advanced Clients and an MP. ... > that only the subnet of the primary site server is included. ...
    (microsoft.public.sms.setup)
  • SMS 2003 Hierarchy Design
    ... I'm looking for some help with my SMS hierarchy design. ... Main European Location = 100 clients ... needs to be able to manage all systems globally and the asia and europe main ... I originally planned a primary site server at each of the 3 main locations ...
    (microsoft.public.sms.setup)
  • RE: Upgrade SMS 2.0 to SMS 2003
    ... clients on our intranet. ... We would like to upgrade our current SMS 2.0 infrastructure to ... Run the DRW on the central site server and secondary site server and ... Do an in-place upgrade of the primary central site server to SMS 2003 ...
    (microsoft.public.sms.setup)
  • Re: Upgrade from 2.0 and new AD
    ... > I am introducing new AD structure followed by new SMS 2003 site server. ... SP0 will update all clients to the sms 2003 legacy client. ...
    (microsoft.public.sms.admin)
  • Re: Client installation frustration.
    ... Your site server cannot resolve the computer names to ip addresses. ... MVP Windows Server System - SMS ... By design advanced clients only assign to primary sites. ... At this secondary site there are nearly ...
    (microsoft.public.sms.admin)