Re: Migrating SMS 2.0 content to SMS 2003

Tech-Archive recommends: Fix windows errors by optimizing your registry

Terri,



I saw your post regard a script that you created that will export old items
from a SMS 2.0 site to a new SMS 2003 site. I would be forever grateful if
you could share this with me as we are undergoing the same sort of migration
with little to no success.





Thanks



Robert Ronan




"Terri" wrote:

> I too would like to review the VBS script you mentioned.
>
> We have a location that created an SMS 2003 primary site independent of the
> Corporate requirements. We want to create a new SMS site and migrate the
> packages and collections of the old environment to the new. I checked
> MyITForum but it was for SMS 2.0 PDFs. I wasn't sure if it would be
> compatible with SMS 2003.
>
> Thanks for your help
> Terri
> "Kim Oppalfens" wrote:
>
> >
> > Mikey,
> >
> > If you sent me an email at kimoppalfens-nospam-@xxxxxxxxxx, I will reply
> > with a vbs script I created to export package definition files from a
> > server.
> >
> > I used this in a test environment to export packages, and reimport them.
> > If you would like to take if for a test run, I would be more than happy
> > to sent it to you.
> >
> > Keep in mind that this has undergone very limited to no testing at all.
> > Kim
> > In article <9AE5FAF1-4885-4B9A-84C6-3FC2AAC54020@xxxxxxxxxxxxx>,
> > Mikey@xxxxxxxxxxxxxxxxxxxxxxxxx says...
> > > In the midst of migrating our current SMS 2.0 hierarchy to SMS 2003 (side by
> > > side upgrade) and have been dumbstruck that there is no utility to migrate
> > > the SMS 2.0 content to the new SMS 2003 environment. I know I can export /
> > > Import the collections, but found nothing that will bring over the associated
> > > Packages, Avertisements, queries, Etc., etc. etc....
> > >
> > > Is this really the case? That I have to manually recreate everything from my
> > > old SMS environment?
> > >
> > > Thanks!
> > >
> >
> > --
> > Kim Oppalfens
> > Proud father of Lennart Oppalfens
> > Since 05/11/2004 08.53 GMT+1
> >
.

Relevant Pages

  • Request for Discription of ProgramFlags Bits - SMS 2003
    ... WMI object in the SMS 2003 SDK v2. ... I've customized the create Packages ... / Program script to read from a text file or prompt for the required ...
    (microsoft.public.sms.swdist)
  • Re: SMS upgrade Side-By-Side 2.0 to 2003
    ... Being able to migrate queries and packages can prove to be valuable though. ... I still don't have a package import script because most of the time you ... MVP Windows Server System - SMS ...
    (microsoft.public.sms.setup)
  • Re: Using vbs scripts with maintenance wizard
    ... If you are running the program in admin context then SMS ... will run the program in LocalSystem context which is different environment ... If you run the script from the command line and don't assume that there are ...
    (microsoft.public.sms.swdist)
  • Re: Making sure Office apps are closed
    ... you need to make sure that for dependent programs SMS doesn't ... package that had two programs in it. ... Popup-n-kill-Office script and the second one would be the actual Office ... and the actual Office 2003 install script to run whether logged on or not. ...
    (microsoft.public.sms.swdist)
  • Re: Distributing Software "Quickly" to Bare Metal Installs
    ... >> Nope, never seen any script like it, I just tought it would be a feasible ... >> ' Script By Kim Oppalfens - MVP SMS ... >> Dim objSWbemServices ... Set objCollection = objSWbemServices.ExecQuery _ ...
    (microsoft.public.sms.swdist)