Re: Side by side upgrade of SMS 2.0 to SMS 2003

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

This is the one time that we had "overlapping site boundaries". We kept our
entire SMS 2.0 site in place (in fact, continued to push software during the
conversion), stood up SMS 2003 Primary site (and secondary sites), used SMS
2.0 (yes, SMS 2.0) to run the SMS 2003 client installation -- we had all
advanced clients, so we just set CCMSetup and client.msi as the package
source, and rolled it out using CCMSetup.exe with the proper command-line
parameters (turned of logon discovery on the 2.0 site before we started
though). Worked like a champ! Once the clients are updated to SMS 2003 adv
client (probably legacy too, but didn't test that), the 2.0 client
installation will silenty fail if attempted.

Pretty cool to use the "old" product to upgrade to the new one . .


"Hiren Patel" <Hiren Patel@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:AE505243-A31B-4584-A791-701277389BE7@xxxxxxxxxxxxxxxx
> My company wnats to move to SMS 2003. We have a single SMS 2.0 server.
>
> We want to install SMS 2003 on a brand new server.
>
> I will be recreating the packages and adverts.
>
> Can someone please send me links that might explain in some detail how I
> can
> move my clients from SMS 2.0 to SMS 2003?
>
> Also, how would I handle the site boundaries, do i need to first disable
> them on the SMS 2.0 server and then enable them on the SMS 2003 server?
>
> Any help would be GREATLY appreciated ! :-)
>
> Thank you


.

Relevant Pages

  • Re: Secondary Sites
    ... you cannot assign clients to them. ... Check out the SMS Technical FAQ: ... Can the advanced client talk to the existing primary site server if ... You mention that you have a child domain within your LAN. ...
    (microsoft.public.sms.setup)
  • Re: Inplace Upgrade os SMS2.0 to 2003
    ... > Currently our SMS 2.0 Installation consists of a Central Site Server and one ... On the Central Site server there are roughly 700+ clients, ... > another server that is being used as a SMS Distribution Point. ... Site boundaries should be retained after the upgrade. ...
    (microsoft.public.sms.setup)
  • Re: SWD and W2K Server errors
    ... These errors point me more towards a bad HD where SMS might be trying to ... >>When you say server reboots with a stop code of 0x3F ... >>> package on Friday and am getting an Event ID: ... >>> in Toronto and the Secondary Site Server in New York ...
    (microsoft.public.sms.swdist)
  • Re: Distributing Office 2003
    ... and print server or any other member server. ... defined in the SMS Site as an assigned DP. ... transmitted, not the entire package. ... MST file after I ...
    (microsoft.public.sms.swdist)
  • Re: Help need desperately!
    ... > Have you given your SMS Server's machine account FULL CONTROL of the Systems ... > machines are already discovered or you wouldn't be able to push to them. ... > Check through the SMS Server logs, ... All clients are discovered, assigned and have successfully installed the ...
    (microsoft.public.sms.inventory)