SMS Upgrade horror stories.. aka what not to do..

From: Gene Siepka (gsie44_at_tsg.cbot.com)
Date: 09/26/05

  • Next message: David Foster: "Restore filesystems on Sparc 10 SunOS 4.1.x system from 'dump' files on NFS volume"
    Date: Mon, 26 Sep 2005 13:10:06 -0500
    To: sunmanagers@sunmanagers.org
    
    

    Sunmanager crew...

    I've been tasked with developing a plan to upgrade our 5 15k Frames to
    the almost latest and greatest of OS and SMS software.

    4 frames are at Solaris 8, SMS 1.3.. The 5th is Solaris 8 SMS1.2.

    We are looking all in all to end up with Solaris 9 SMS1.4.1

    I was wondering if anyone out there would be willing to share any
    "gotchas" or "Make sure you do this first" type of stuff.

    Also, I've got one specific question...

    If we do smsupgrade to go from 1.2 to 1.3 then smsupgrade again to go
    from 1.3 to 1.4.1, what do the SMS packages look like?
    I'm assuming (since smsupgrade does not actually remove the existing
    packages AFAIK) that from 1.2 to 1.3, the 1.3 packages will all be named
    like SUNWSMSxx.2 But will the 1.3 to 1.4.1 packages be named like
    SUNWSMSxx.3
    And other than that being really ugly, is there any downside to the .2
    and .3 package names? Like for instance with SMS patches later down the
    road that would come back and bite me? Or is it safer just to scrap it
    and do fresh installs of OS and SMS and smsrestore my configs?

    Thanks in advance.

    -Gene R. Siepka

    --------------------------------------------------------------------
    This message is confidential and is intended only for the
    individual(s) named. If you are not the intended recipient,
    please let us know by e-mail reply and delete it from your system;
    do not copy/save this message or disclose its contents to anyone.
    E-mail transmissions cannot be guaranteed to be secure or error-free
    as the transmission could be interrupted, corrupted, lost,
    destroyed, altered, arrive late or contain viruses. The Chicago
    Board of Trade does not accept liability for any errors or omissions
    in the contents of this message which arise as a result of e-mail
    transmission. The views expressed in this message do not
    necessarily reflect those of the Chicago Board of Trade or its
    affiliates.
    --------------------------------------------------------------------
    _______________________________________________
    sunmanagers mailing list
    sunmanagers@sunmanagers.org
    http://www.sunmanagers.org/mailman/listinfo/sunmanagers


  • Next message: David Foster: "Restore filesystems on Sparc 10 SunOS 4.1.x system from 'dump' files on NFS volume"

    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: Testing packages in SMS 2003?
      ... You must mean SMS 2.0, ... With 2000 I would advertise unassigned packages ... > 2003 and am beginning to regret the upgrade. ... > View|Refresh in Advert prog monitor in 2000). ...
      (microsoft.public.sms.admin)
    • RE: does SMS distribution support multicast?
      ... Set up a share on a client in the network you'd like to advertise packages ... Setup a "Server Share" in sms to point to that share. ... Then since you've transferred the package to a client using BITS, ... SMS server could support multicast so that not all access to the SMS server ...
      (microsoft.public.sms.swdist)
    • SMS 2003 software distribution points
      ... We deploy all our software using SMS. ... I have never used a software distribution point in SMS and I was wondering ... All of our packages are MSIs. ... I have no need for either of these features. ...
      (microsoft.public.sms.swdist)
    • RE: SMS 2003 user profile migration
      ... registry section in-place will stop further reruns of packages. ... Both domains have SMS 2003 installed and running; ... When I login with the user id in the new domain; SMS tryes to install ... bealived some how SMS keeps track of the SID and because when I ...
      (microsoft.public.sms.admin)