Re: Side by Side Upgrade - Need Assurance

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

From: Desparate Dan (anonymous_at_discussions.microsoft.com)
Date: 06/08/04 

Date: Tue, 8 Jun 2004 14:33:08 -0700

Thanks Evan - much obliged.

Hopefully this post will also help a few others out there.

>-----Original Message-----
>That should work. Upgraded clients should automatically
reassign to the new
>site and deassign from the old site. You can verify this
by checking the sms
>applet on the client and seeing which site it's assigned
to. They will still
>appear in the old site but won't send ddrs or inventory
to the old site
>anymore. You should always carry out your planned
upgrade scenario on a test
>bench before trying it on your real site. That way, you
could verify that
>everything actually works as you expect it will.
>
>--
>This posting is provided "AS IS" with no warranties, and
confers no rights.
>"Desorate Dan" <anonymous@discussions.microsoft.com>
wrote in message
>news:19b1d01c44d56$a843fa50$a101280a@phx.gbl...
>> SMS Guru's
>>
>> Thanks for all the input so far.
>>
>> My current SMS 2.0 install is not in good health and
the
>> hardware is not up to much either.
>>
>> This is why I'm thinking side by side install.
>>
>> I'm thinking
>>
>> - Install New SMS 2003 on powerful hardware platform
>> using a different Site Code
>>
>> - Configure SMS 2003 appropriately with same IP
>> boundaries as before and add AD site name to boundary
>> list. (There are no legacy clients to worry about)
>>
>> - Then do a site discovery
>>
>> - Then push out the SMS 2003 advaced client to existing
>> SMS 2.0 clients that are members of the SMS 2.0 site in
>> the hope that they will be upgraded to the advanced
>> client automatically and then automatically move to the
>> new SMS 2003 site.
>>
>> (All servers and clients are Windows 2000 and above)
>>
>> Does this sound right?
>>
>> Be great if you could let me know.
>>
>> TIA
>>
>> Dan
>>
>
>
>.
>

Relevant Pages

  • Re: SMS Advance Client not assigned to the site
    ... added 3 subnets individually on top of that. ... In the Roaming Boundaries tab, ... all clients in our network are XPs so I don't need to worry ... Sms 2003 has 2 types of clients: ...
    (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 ... 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: Preventing Users who travel from switching SMS sites
    ... SMS 2003 Configuration and Operation of Advanced Client Roaming ... boundaries, ever, so the client can't get confused about which site it ... the next generation of "quarantining" clients. ... within the site boundaries of Primary1. ...
    (microsoft.public.sms.admin)
  • Re: SMS Advanced Clients not seeing protected Distribution Point - Using the wrong Distribution
    ... If so then its IP addresses should be defined as belonging to SMS ... If it's a Primary have the clients been reassigned or do they still ... How are you defining the Roaming boundaries of Site 2? ... Check out the client boundaries at Site2, ...
    (microsoft.public.sms.admin)