osdbuilder-import-tool's Introduction

OSBuilder-Import-Tool

The purpose of this tool is to import OSBuilds and OSMedia created using David Segura's OSDBuilder module into SCCM. It's primary functions are as follows:

Copy the OSBuild/OSMedia into the correct content shares (wim file and optionally OS Upgrade Packages)
Import the OSBuild/OSMedia into SCCM Operating System Images (Optionally import OS Upgrade Package)
Distribute Content to a specified Distribution Point Group
Optionally update a specified task sequence step with the new OS Image

Pre-Requisites

Ensure that you have installed the latest OSDBuilder Module and the ConfigurationManger module This script needs to be run on the machine that OSDBuilder is run on The computer that this script is run on should also have the Configuration Manager Console installed (and the console needs to have been opened at least once)

Instructions

Edit the Import-OSBuild.ps1 file and set the following Global Variables: ContentShare, OSUpgradeContentShare, SCCMSite, PreferredDistributionLoc
Run the script and choose the OSBuilds you want to import
The script will automatically copy the install.wim to your specified content location, import the wim into SCCM, and distribute the content to the selected Distribution Point Group
You can also choose to run the script silently by providing an OSUploadName. See examples for more usecases

The Script will not copy wims (or import them into SCCM) if they already exist on the content share.

Imports an OSBuild wim file only

.\Import-OSBuild.ps1

Import an OSBuild wim file and the cooresponding OS Upgrade Package

.\Import-OSBuild.ps1 -ImportOSUpgrade

Import the latest OSBuild with the name like "Windows 10 Enterprise x64 1809", and import the cooresponding OSUpgrade package. This flag is helpful for automating the upload process, say... after an OSBuild is completed.

.\Import-OSBuild.ps1 -OSUploadName "Windows 10 Enterprise x64 1809" -ImportOSUpgrade

Import the latest OSMedia with the name like "Windows 10 Enterprise x64 1809", then update the step "Install Windows 10 x64" in the task sequence "DEV Task Sequence" with the newly uploaded media

.\Import-OSBuild.ps1 -OSUploadMedia -OSUploadName "Windows 10 Enterprise x64 1809" -UpdateTS -TaskSequenceName "DEV Task Sequence" -TaskSequenceStepName "Install Windows 10 x64"

Import an OSMedia wim file and the cooresponding OS Upgrade Package

.\Import-OSBuild -Import-OSMedia -ImportOSUpgrade

Import an OSBuild, but do not create a new wim on the content share, instead update an exising wim

NOTE: This flag cannot be used silently

.\Import-OSBuild -UseExistingPackages

Import an OSBuild wim file, and the cooresponding OS Upgrade Package but use an exising wim and Upgrade Package

.\Import-OSBuild -UseExistingPackages -ImportOSUpgrade

This is a work in progress, use at your own risk, I take no responsibility for any issues this may cause. :)

osdbuilder-import-tool's People

Contributors

Stargazers

Watchers

osdbuilder-import-tool's Issues

Requires both OSDBuilder and ConfigurationManager modules

It looks like this requires both the OSDBuilder module (version 19.3.12.0, not 19.1.11.0 as specified in readme.md) and the configurationmanager powershell module to both be available locally. This could be an issue since OSDBuilder may be on a dedicated computer and not on the Configmgr server.

Consider adding to the documentation that the script should be run on the OSBuilder computer, and that the SCCM Admin Console must also be installed.

Reload OS image properties when updating an existing image

It'd be helpful if the image properties were reloaded when an existing image is updated, like clicking 'Reload' on the Images tab in properties.

I believe the only way to do this is via WMI, with the ReloadImageProperties method on the image, so it means the module now has to do WMI as well.

Recommend Projects

asjimene / osdbuilder-import-tool Goto Github PK