From: admin@lists.myITforum.com [mailto:admin@lists.myITforum.com] On Behalf Of Hemsell, Todd
Sent: Friday, July 03, 2009 11:31 AM
To: mssms@lists.myitforum.com
Subject: RE: [mssms] How do you import/export packages across separate non-connected primary sites?

I have always wanted something that will delete/remove a DP or secondary.

 

HUGE pet peeve of mine that deleting a DP does not really delete a DP

 

There is a script that will sort of do it, but it is difficult t o use.

 

From: admin@lists.myITforum.com [mailto:admin@lists.myITforum.com] On Behalf Of Ed Aldrich
Sent: Friday, July 03, 2009 9:37 AM
To: mssms@lists.myitforum.com
Subject: RE: [mssms] How do you import/export packages across separate non-connected primary sites?

Tks!

 

we’re making a concerted effort to try and get more stuff like this created and into the (free) public domain...

 

Always looking for ideas on new tools, or enhancements to existing ones...

 

         

Ed Aldrich | Solutions Engineer | 1E 

Mobile: (401) 924-2293

 

From: admin@lists.myITforum.com [mailto:admin@lists.myITforum.com] On Behalf Of Hemsell, Todd
Sent: Friday, July 03, 2009 10:29 AM
To: mssms@lists.myitforum.com
Subject: RE: [mssms] How do you import/export packages across separate non-connected primary sites?

Very COOL!

 

 

From: admin@lists.myITforum.com [mailto:admin@lists.myITforum.com] On Behalf Of Ed Aldrich
Sent: Friday, July 03, 2009 9:12 AM
To: mssms@lists.myitforum.com
Subject: RE: [mssms] How do you import/export packages across separate non-connected primary sites?

We have a free tool on our website called the 1E Migration tool designed for exactly this scenario:

 

http://www.1e.com/Downloads/FreeTools/Index.aspx

 

1E Migration Tool http://www.1e.com/App_Themes/1ETheme/images/new.gif

This tool is designed to allow an SMS Administrator to Migrate all or selected packages and programs from his SMS environment into a System Center Configuration Management (ConfigMgr) environment. The tool has the following features:-

·         The Migration of Package and Program details along with source files

·         Renaming of Package and Program names during migration

·         Direct transfer of packages from your SMS site to ConfigMgr

·         Export to flat file structure from SMS site and Import into ConfigMgr from flat file

·         Exporting of SMSNomad command line settings to new ConfigMgr Nomad tab settings.

Date: 23 Feb 2009   Size: 107 Kb

 

 

Well, almost as it was originally designed to use in an upgrade scenario going from SMS to CfgMgr, but it should work just fine going from CfgMgr to CfgMgr... these are unsupported, use-at-own-risk, blah, blah, type tools, but we are always looking for feedback around any issues or problems for the “next” unsupported version! J

 

Give it a shot and see what happens!! You must provide your own USB key, however J

 

cid:image006.gif@01C3C00A.ED2644E0          twitter3 small

Ed Aldrich | Solutions Engineer | 1E 

Mobile: (401) 924-2293

 

From: admin@lists.myITforum.com [mailto:admin@lists.myITforum.com] On Behalf Of Nathan Cook
Sent: Thursday, July 02, 2009 9:51 PM
To: mssms@lists.myitforum.com
Subject: [mssms] How do you import/export packages across seperate non-connected primary sites?

Hi,

Long term lurker here.  I support a large government SCCM R2 site and they are planning to implement two large preproduction Dev and Test domains for the first time.  They want me to install and configure SCCM in these environments.  The install is easy as this is well documented.

The kicker is these environments are air-gaped, no connection to each other or the Internet (security reasons...don't ask!).  I will be using a large USB drive to shuffle files around.  As they I need hundreds of packages synchronised between these environment, I have been researching my options.  There doesn't seem to be any third party tools and the inbuilt "Transfer site settings wizard" is such a joke, I find it hard to believe anyone would use it for packages.

Doing all these steps manually is really not a good idea as i will have to create around 500 packages in each, all with many programs and custom settings.  I know I will make typos, as well it taking me weeks to do.

I am looking at making  a .NET tool, maybe use the MOF creation method to create MOF files for each package, tweak them and then do the reverse at the other end, ensuring the package source location is updated, etc.  In the long term, packages will flow through this stsyem so i will be runing this import process untill Microsoft improves their inbuilt tools.

Before I start this journey, I was wondering if anyone else has a similar problem and has found a good solution?

Nathan

==============
Missed an email? Check out the list archive:
http://myitforum.com/cs2/blogs/smslist/



DISCLAIMER: This is a PRIVATE AND CONFIDENTIAL message for the ordinary user of this email address. If you are not the intended recipient, please delete without copying and kindly advise us by e-mail of the mistake in delivery. NOTE: Regardless of content, this e-mail shall not operate to bind 1E to any order or other contract unless pursuant to explicit written agreement or government initiative expressly permitting the use of e-mail for such purpose.


==============
Missed an email? Check out the list archive:
http://myitforum.com/cs2/blogs/smslist/


==============
Missed an email? Check out the list archive:
http://myitforum.com/cs2/blogs/smslist/


==============
Missed an email? Check out the list archive:
http://myitforum.com/cs2/blogs/smslist/


==============
Missed an email? Check out the list archive:
http://myitforum.com/cs2/blogs/smslist/

Published with BlogMailr



Trackbacks

No Trackbacks

Comments

No Comments