Re: Upgrade Questons

From: Hello all (Helloall_at_discussions.microsoft.com)
Date: 11/15/04 

Date: Mon, 15 Nov 2004 03:09:01 -0800

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.

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.

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.

"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>,
> Helloall@discussions.microsoft.com says...
> > Thanks for your reply
> >
> > I'll be abit more specific
> >
> > I Know all about standard and advance security regarding sms 2003 however I
> > read somewhere that if you want to utilise advance security after you have
> > upgraded form sms 2.0 to sms 2003 you have to upgrade sql 7 to sql 2000 with
> > sp3.
> >
> > If this is the case does this mean you have to upgrade sql prior to the sms
> > 2003 upgrade or can you do it during the sms 2003 upgrade itself. However,
> > what I read my be nonsense and advance security has nothing to do with the
> > type of database itself, just need clarification on this point.
> >
> > The second question
> >
> > Prior to upgrading to sms 2003 we are going to consolidate two sites. Lets
> > say they are called site 1 and site 2. We are planning on adding the site
> > boundaries of site 2 to site 1. Site 1 will then manage resources in both
> > sites and we will turn off site 2. We will then upgrade site 1 with sms 2003
> > and install the advance client to all the resources in the site. Now the
> > question is both sites have travel mode laptop users, are there any issues we
> > need to think about regarding these users or can we treat them like any other
> > client resource.
> >
> > I hope this clarifies things abit more
> >
> > "Kim Oppalfens" wrote:
> >
> > >
> > > Inline
> > > > I have ready somewhere that if you want to utilise advance security with sms
> > > > 2003 then you have to upgrade sql from sql 7 to sql 2003 sp3.
> > > >
> > > > Does this mean you have to upgrade sql first prior to upgrading sms or does
> > > > it happen during the sms upgrade process
> > > Neither, you can upgrade in advance if you want, or you can upgrade sms
> > > 2.0 to sms 2003 in standard security and swith to advanced security when
> > > you filled the requirements.
> > >
> > > >
> > > > We are also thinking about consolidating a couple of our sites prior to the
> > > > sms 2003 upgrade. However the two sites we are thnking about have a large
> > > > number of travel mode laptop users. Will this be an issue or is the
> > > > consolidation process still the same.
> > > >
> > > I am not really sure what you want to as far as consolidation goes, but
> > > sms 2003 can handle laptop users much better than sms 2.0 did.
> > >
> > > > In other words overlapping site boundariess, waiting for a site to then
>
> --
> Kim Oppalfens
> Proud father of Lennart Oppalfens
> Since 05/11/2004 08.53 GMT+1
>

Relevant Pages

  • Need guidance on SMS 2.0 to 2003 Upgrade approach
    ... We are belatedly upgrading from SMS 2.0 to SMS 2003. ... the Primary Site Server hardware as it is old and under spec. ... secondary sites as some of them are throwing errors under SMS 2.0. ... Upgrade secondary sites OR consolidate (by re-homing clients via Site ...
    (microsoft.public.sms.admin)
  • SQL Database connection failed
    ... new collection in sms 2003 and suddently the connection with the ... a subordinated primary site and about 20 child secondary ... Unable to update parent collection due to SQL error. ...
    (microsoft.public.sms.admin)
  • Re: Primary vs Secondary
    ... I personally would tend to go with a primary site unless I have a good ... Check out the SMS Technical FAQ: ... Aside from the sql and server license. ... Advanced Clients cannot be assigned to Secondary Sites. ...
    (microsoft.public.sms.admin)
  • Re: SMS 2003 SP3
    ... SP3 supports SQL 2005. ... it requires SMS 2003 SP2. ... Upgrade your SMS 2003 to SP3 first, then upgrade to SQL Server 2005. ...
    (microsoft.public.sms.admin)
  • Re: Upgrading remaining SMS Clients.
    ... We are planning to upgrade to ITMU rev 3 at work, before this, we upgraded ... all Primary and Secondary SMS servers to SMS 2003 SP2. ... upgrading all machines with the SMS Advanced SP2 Client. ... secondary site that links off the Primary site. ...
    (microsoft.public.sms.admin)
Loading