October DealsAmazon USOctober deal check: compare before you payAmazon US: current deals, useful picks and tech finds.Check DealsClean PCRecommendedOne scan can reveal what keeps slowing WindowsLook for cleanup and repair opportunities.Run ScanOctober DealsAmazon USDeal season is back - check today's better picksAmazon US: current deals, useful picks and tech finds.See Picks×
Skip to content
World desk2 min

How to Export a Legacy SCCM Package with PowerShell

Use Export-CMPackage from the Configuration Manager site drive in a .NET Framework PowerShell session to export a legacy package to a ZIP file.
Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

To export a legacy Configuration Manager (SCCM) package, use the Export-CMPackage cmdlet from a .NET Framework PowerShell session opened in the Configuration Manager site drive. Microsoft documents the PowerShell method; the exact console Package Wizard steps and labels are not established here, so use the GUI only after confirming them in your console version.

Export a legacy package with PowerShell

Open a PowerShell session that uses .NET Framework, connect to the Configuration Manager site, and run the cmdlet from that site drive. Microsoft’s example uses a network share and a ZIP destination:

As an Amazon Associate I earn from qualifying purchases.

Export-CMPackage -Id "ST120001" -FileName "\Deploy01ExportPackagesST120001.zip"

Replace the sample package ID and share path with values from your environment. The account running the command needs permission to write to the destination.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Microsoft’s Export-CMPackage reference says Configuration Manager cmdlets should be run from the Configuration Manager site drive, shown in examples as a prompt such as PS XYZ:>. The cmdlet requires .NET Framework and does not support PowerShell 7. Starting with Configuration Manager version 2103, running it in a PowerShell 7 session fails because it supports only the .NET Framework runtime.

#1 Best Overall
Sale
PowerShell for Sysadmins: Workflow Automation Made Easy
  • Book - powershell for sysadmins: workflow automation made easy
  • Language: english
  • Binding: paperback

Select the package

You can identify the package with -Id or -Name, or pass a package object returned by Get-CMPackage. See Microsoft’s Get-CMPackage reference for package lookup options.

Choose whether to include content and dependencies

Set the inclusion options explicitly for the export you need. Microsoft documents -WithContent $true to export all content for the package and its dependencies, and -WithDependence $true to export all package dependencies. The reference does not establish defaults for these options; inspect the resulting archive to ensure it contains what your migration or backup requires.

Export-CMPackage -Id "ST120001" -FileName "\Deploy01ExportPackagesST120001.zip" -WithContent $true -WithDependence $true

What to know about the Package Wizard

The exact location, page sequence, labels, and defaults for a legacy-package export wizard are not established here. Do not assume instructions for exporting applications or driver packages describe the legacy-package wizard. If you need a graphical procedure, verify the steps in the Configuration Manager console version you use.

What’s actually slowing this PC down?

Pick the symptom - the matching free tool is one click away.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Confirm you are exporting the right object type

Configuration Manager has separate export cmdlets for different object types. Export-CMPackage is for legacy packages; applications and driver packages use different cmdlets and references:

Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Support on Ko-Fi

Export is different from import

To bring an exported legacy-package ZIP into another site, use Import-CMPackage, not the export cmdlet. Microsoft documents that the import cmdlet also requires .NET Framework rather than PowerShell 7. The export cmdlet’s optional -Comment value is an administrator comment displayed in the Import Package Wizard. See Microsoft’s Import-CMPackage reference.

Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.

Leave a Reply

Your email address will not be published. Required fields are marked *

Free tools Windows power users keep installed

One-click scans. No signup required.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

More from the Wire

  1. World desk4 min
    How to Spot an AI Voice Scam Before Sending MoneyDon’t rely on how a caller sounds. Pause, call back through a known number, and verify the emergency with another trusted person before sending money.
  2. Mountain View desk4 min
    Google’s SynthID Detector: How to Check AI-Generated Images, Video and AudioGoogle’s SynthID Detector looks for an embedded watermark in supported images, video and audio. Here is what its results do—and do not—show.
  3. Redmond desk20 min
    How to create a link to File or Folder in Windows 11Windows 11 gives you several ways to point to a file or folder without moving or duplicating it. You can create a desktop shortcut,…
Recommended PC Tool
Recommended PC Tool
Crashes, No Sound, or Screen Glitches?Free driver scan
Windows Errors? Fix Them Before They SpreadFree repair scan

Two free Windows tools

One Free Minute Could Fix That PC

Before you go - each of these free tools takes about a minute and tackles what quietly slows a Windows PC down.

Special offer. View Outbyte info, uninstall instructions, EULA, and Privacy Policy.