Re: SMS 2.0 to SMS 2003 Upgrade

From: darb (darb_at_discussions.microsoft.com)
Date: 07/19/04 

Date: Mon, 19 Jul 2004 15:48:02 -0700

Your refer to site boundries and accounts. Maybe this is a bad thing, but I am just using the default SMS accounts created during setup of 2.0, are there others I should be aware of? Also I have all my computers within a single site. Out of the 70+ machines only 15 or so are NT 4.0 so I am not to concerned about them. On the remainder I want to run the advanced client. I have just a single SMS 2.0 installation so it seems that this senario of the New Primary site on new hardware would work for me. Your thoughts?
Thanks,
darb

"Jeff Harbaugh [MSFT]" wrote:

> 1. You would have a new primary site. The advertisements etc will nto
> replicate up but because this is the parent site it will be able to see all
> exisiting packages and information that relates to the child site.
> 2. Yes for the SMS 2003 you woudl ahve to setup all site boundaries and
> accounts over again. Make sure once you add a boundary to the SMS 2003 that
> you remove it from the SMS 2.0. Overlapping the boundaries could cause
> client issues, these will be reduced by using the advanced client.
> 3.You would be able to push the clients since you will be able to see the
> collections and clients from the child site. This would then start having
> the clients report to the SMS 2003 and the information from the clients will
> be populating the SMS 2003 database. You can also start creating all new
> ads, packages, etc on the SMS 2003 site which would replicate to the child
> site. This will start your process of fading out the SMS 2.0 site. By this I
> mean all the clients and packages, ads, etc will all start reporting to the
> SMS 2003 and be created on that site as well.
> 4.You cannot make the SMS 2003 site a child of the SMS 2.0 the newest
> version must be the top site.
>
> I would definitely suggest doing some planning and reading before you
> attempt either direction that you wish to go. You may also want to install
> in a test environment so you can see any pitfalls or problems encountered
> before entering production. I cannot suggest which is right for you but if
> you want to install new hardware and change the name of the SMS Server
> machine. Also this leaves your 2.0 site still running until you can safely
> ensure that everything is now migrated. I hope this helps.
>
> Thanks,
> Jeff Harbaugh [MSFT]
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> "Jody Williams" <HomeBoy@discussions.microsoft.com> wrote in message
> news:2ce9501c469b3$ad479ab0$a501280a@phx.gbl...
> > Thank you for the quick reply. Yes, we will be using the
> > advanced client as we will not offer support to pre
> > Windows 2000 PCs.
> >
> > I want to make sure I understand this process a little
> > better. We have a new server that we can install SMS 2003
> > and SQL server 2000 on. You are suggesting to make a
> > completely new site on our new hardware and then add the
> > existing SMS 2.0 site as a child site in the new site,
> > correct?
> >
> > I have a few questions:
> >
> > 1. If we do as you suggest, we will have a new primary
> > site (with a new name). The existing SMS 2.0 site will be
> > a child and we can set this up so that settings for
> > Advertisements, Packages, collections etc. from the
> > existing site will be "replicated" up to the new SMS 2003
> > parent site? If that is true, that would be great.
> >
> > 2. On the new SMS 2003 primary site, we would need to
> > manually confiure site boundaries and top level site
> > settings again?
> >
> > 3. You mentioned "moving/migrating" clients to the new
> > site. Will we have to manually do this or is thier a
> > method to automate this process (is that the Targeted Push
> > Installation Wizard you mentioned)?
> >
> > 4. Just curious if this is the best direction to do this?
> > We had discussed doing this in a similar fashion but
> > making the SMS 2003 site a child site in the existing SMS
> > 2.0 site. I wasn't sure if this would be a valid method or
> > not.
> >
> > Thanks for your assitance!
> >
> >
> >>-----Original Message-----
> >>If you are installing new hardware for the SMS 2003 site
> > and SQL server then
> >>you probably do not want to install SMS 2003 on your
> > exisitng hardware.
> >>What you may want to look into. (please evaluate this
> > solution before doing
> >>it to make sure it make sense for you and your company).
> >>Install the new server hardware. Install SMS 2003 and SQL
> > server on the new
> >>hardware. Then make the SMS 2.0 site a child of the new
> > SMS 2003. This way
> >>you can get the information populating the Central site.
> > From there you can
> >>start addign site boundaries and moving/upgrading the
> > clients to the new
> >>site. Are you going to use the advanced client? If so
> > this would be an easy
> >>upgrade as you woudl be able to use the targeted push
> > installation wizard to
> >>upgrade/migrate the clients.
> >>
> >>--
> >>Thanks,
> >>Jeff Harbaugh [MSFT]
> >>This posting is provided "AS IS" with no warranties, and
> > confers no rights.
> >>
> >>"Jody Williams" <HomeBoy@discussions.microsoft.com> wrote
> > in message
> >>news:2c04e01c4691a$87b0e5c0$a501280a@phx.gbl...
> >>>I have searched through the documentation and the forums
> >>> about this and think I know what we have to do but
> > wanted
> >>> some additional feedback to make certain :-)
> >>>
> >>> We have an existing SMS 2.0 SP5 site on a Windows 2000
> >>> Advanced Server. We are using SQL Server 2000. We would
> >>> like to upgrade to SMS 2003. However, we also want to
> >>> install a new Windows 2003 server and move/migrate the
> >>> existing SMS 2.0 site to the new Windows 2003 server
> >>> during the SMS upgrade process.
> >>>
> >>> From what I have read, we would want to use the Recovery
> >>> Expert to do this. Unfortunately, we will NOT be able to
> >>> leave the PC names for the old SMS 2.0 server and the
> > new
> >>> SMS 2003 server the same.
> >>>
> >>> So, my questions are as follows:
> >>>
> >>> 1. Would we want to upgrade the exisitng SMS 2.0 site to
> >>> SMS 2003 on the existing hardware?
> >>>
> >>> 2. Is there a way to use the Recovery Expert on a new
> >>> server with a different name to recover/migrate the
> >>> exisitng SMS 2.0 site to the new server and then perform
> >>> the upgrade to SMS 2003?
> >>>
> >>> I hope this makes sense :-) Any ideas would be
> > appreciated.
> >>>
> >>
> >>
> >>.
> >>
>
>
>

Relevant Pages

  • Re: SMS2003 parent with sms 2.0 children and SUS
    ... version in those packages. ... If you do all of that, then your 2.0 clients at the child sites will ... work when advertised from a 2003 site to clients of a child 2.0 site. ... The Dell Update scan tool will only work on SMS 2003 SP1 advanced clients. ...
    (microsoft.public.sms.setup)
  • Re: SMS2003 parent with sms 2.0 children and SUS
    ... I believe the status messages are generated by the clients. ... You'll need to update any of your patch packages ... The Dell Update scan tool requires SMS 2003 SP1 advanced clients I believe ... >>> replicated to the child sites and run. ...
    (microsoft.public.sms.setup)
  • Re: MP, DP or new Site???
    ... Advertise very small packages. ... I want to set these servers up as distribution points to help me ... making these locations SMS secondary sites, then for each activate them as ... or where you centrally admister these clients the Central site. ...
    (microsoft.public.sms.admin)
  • RE: software distribution issue
    ... My SMS logs are clean and the package apears to be ... ready to go, but no clients have requested, i suspect its a policy problem ... > - Created multiple packages for testing ... but I can not see the applicaiton advertisements in the ...
    (microsoft.public.sms.swdist)
  • Re: SMS 2.0 to SMS 2003 Upgrade
    ... "3.You would be able to push the clients since you will be able to see the collections and clients from the child site" ... > you remove it from the SMS 2.0. ... >> Installation Wizard you mentioned)? ...
    (microsoft.public.sms.setup)