Re: Upgrade Questons

From: Kim Oppalfens (kim_at_computacenter.nospam)
Date: 11/15/04


Date: Mon, 15 Nov 2004 16:04:53 +0100


Inline.
In article <1B372A3A-4428-44CD-BD57-AF1EE0D4CFD4@microsoft.com>,
Helloall@discussions.microsoft.com says...
>
> Again thanks for your reply
>
> So just to confirm when should I upgrade to sql 2000 sp3. After I have
> upgraded my sms 2.0 primary site to sms 2003 (configuring using standard
> mode) or before I upgrade to 2003.
I think I would upgrade SQL first, but I guess that is just my personal
preference because I know more about sms than about sql.

>
> Second question
>
> The reason we are consolidating sites is because the initial sms 2.0
> hierarchy was not designed properly for our organizational structure.
>
> so anyway we have a sms 2.0 primary site with 2 secondary sites hanging off
> it.
>
> What I was planning on doing is upgrading the primary site to sms 2003 and
> adding in the site boundaries of the secondary sites to the primary site
> (overlapping boundaries, then installing the advance client to the managed
> resources which would now include the resources from the secondary sites.

That is fine if you are planning to use secondary sites, advanced
clients cannot be assigned to secondary sites anyway.
>
> This would then free up hardware resource which we have allocated for other
> tasks
>
> When I talked about large numbers of travel mode laptop users I ment
> hundreds not thousands.
>
I believe a couple of hundred clients would warrant the installation of
a site server, and not work with a protected distribution point. Maybe
the capacity planner can help you out.
http://www.microsoft.com/smserver/techinfo/productdoc/default.asp

> "Kim Oppalfens" wrote:
>
> >
> > Ok, Advanced security indeed requires a sql 2000 database. We use
> > computer account authentication in advanced security. Computer accounts
> > authenticate using kerberos and kerberos authentication is not supported
> > by SQL 7.0. And as far as I know there is no possibility to upgrade the
> > database during the sms setup phase.
> >
> > On question 2, I am a bit afraid like you are putting a lot of trust
> > into the bits feature, keep in mind that this is just a client feature
> > and not suitable to eliminate a full site server. To be honest the
> > "large number of laptop users" statement worries me. Not the fact that
> > they are laptop users, but the fact that you use large number. Sites
> > with large numbers of clients should have their own infrastructure.
> >
> > What is the reason behind the consolidation If I may ask? Keep in mind
> > that secondary site server licenses are free in sms 2003. If this is not
> > what you want at the very least consider a protected distribution point.
> >
> > Kim Oppalfens
> >
> >
> > In article <45AE4CC8-BE6A-47B1-AE72-E9537BA388E5@microsoft.com>,

-- 
Kim Oppalfens
Proud father of Lennart Oppalfens 
Since 05/11/2004 08.53 GMT+1


Relevant Pages

  • Re: Need guidance on SMS 2.0 to 2003 Upgrade approach
    ... you should definately read the SMS documention throughly to make ... A site upgrade from SMS 2.0 to SMS 2003 may not succeed if SQL ... Upgrade secondary sites OR consolidate (by re-homing clients via Site ... Create an upgrade schedule for all 50 secondaries ...
    (microsoft.public.sms.admin)
  • Re: new sms installation
    ... other clients over WAN ... I am brand new to SMS and still trying to grasp it. ... Secondary sites do not require a database, ... hosted on the same sql server.. ...
    (microsoft.public.sms.setup)
  • Re: Need guidance on SMS 2.0 to 2003 Upgrade approach
    ... Upgrading from SMS 2.0 to SMS 2003 ... A site upgrade from SMS 2.0 to SMS 2003 may not succeed if SQL ... Upgrade secondary sites OR consolidate (by re-homing clients via Site ... Create an upgrade schedule for all 50 secondaries ...
    (microsoft.public.sms.admin)
  • Re: Need guidance on SMS 2.0 to 2003 Upgrade approach
    ... Upgrading from SMS 2.0 to SMS 2003 ... A site upgrade from SMS 2.0 to SMS 2003 may not succeed if SQL ... Upgrade secondary sites OR consolidate (by re-homing clients via Site ... Setup the secondaries boundaries and configure the site settings ...
    (microsoft.public.sms.admin)
  • Re: SMS 2003 and Site Names
    ... Sms 2003 sites can not report to an sms 2003 parent. ... So you would have to upgrade the primary site sms 2.0 first. ... Step 5 won't be an option since it has the secondary sites attached, ... > the Secondary Sites without migrating all the clients at the same time? ...
    (microsoft.public.sms.setup)