Jump to content


Search the Community

Showing results for tags 'powershell sccm 2012'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Cloud
    • Azure
    • Microsoft Intune
    • Office 365
    • Windows 365
  • General Stuff
    • General Chat
    • Events
    • Site News
    • Official Forum Supporters
    • Windows News
    • Suggestion box
    • Jobs
  • MDT, SMS, SCCM, Current Branch &Technical Preview
    • How do I ?
    • Microsoft Deployment Toolkit (MDT)
    • SMS 2003
    • Configuration Manager 2007
    • Configuration Manager 2012
    • System Center Configuration Manager (Current Branch)
    • Packaging
    • scripting
    • Endpoint Protection
  • Windows Client
    • how do I ?
    • Windows 10
    • Windows 8
    • Windows 7
    • Windows Vista
    • Windows XP
    • windows screenshots
  • Windows Server
    • Windows Server General
    • Active Directory
    • Microsoft SQL Server
    • System Center Operations Manager
    • KMS
    • Windows Deployment Services
    • NAP
    • Failover Clustering
    • PKI
    • Hyper V
    • Exchange
    • IIS/apache/web server
    • System Center Data Protection Manager
    • System Center Service Manager
    • System Center App Controller
    • System Center Virtual Machine Manager
    • System Center Orchestrator
    • Lync
    • Application Virtualization
    • Sharepoint
    • WSUS

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Website URL


Location


Interests

Found 1 result

  1. Howdy, Long time reader. windows-noob.com is one of the best resources available for using SCCM by far. Anyways, here's my issue and I'm a bit stumped. I am attempting to automate our build and capture using Powershell. Everything is working without issue so far except when I attempt to change the data source in SCCM for the image. Example: I have a reference image from three months ago: Windows7x64ENTSP1_2014_11.wim Quarterly build and capture completes and new WIM file is created and housed in the same directory as previous WIM file but with different year/month on filename: Windows7x64ENTSP1_2015_02.wim I run: set-cmoperatingsystemimage -id <ID number> -path <network path to new WIM>Result: Set-CMOperatingSystemImage : ConfigMgr Error Object: instance of SMS_ExtendedStatus { Description = "Failed to read image property from the source WIM file due to error 80070032"; ErrorCode = 2147942450; File = "e:\\nts_sccm_release\\sms\\siteserver\\sdk_provider\\smsprov\\sspimagepackage.cpp"; Line = 355; ObjectInfo = "CSspImagePackage::PreUpdatePackageHook"; Operation = "PutInstance"; ParameterInfo = ""; ProviderName = "ExtnProv"; StatusCode = 2147749889; }; At line:1 char:1 + Set-CMOperatingSystemImage -Id 40200497 -Version 2015_02 -Path "\\<path> ... + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : NotSpecified: (Microsoft.Confi...temImageCommand:SetOperatingSystemImageCommand) [Set-CMOperatingSystemImage], WqlQueryExcepti on + FullyQualifiedErrorId : UnhandledExeception,Microsoft.ConfigurationManagement.Cmdlets.Osd.Commands.SetOperatingSystemImageCommand I had thought it an access/permissions issue so I set the permissions to EVERYONE to test. This did not correct it. Tried adding SYSTEM as well to no avail. I CAN complete this process by point and click in the console without issue so my guess is that when running the command in Powershell, it is trying to use another account to complete the action or is it expecting some local resource to be available? As a further test, I updated to the latest ADK but alas, this did not correct it either. It is obviously referencing a CPP file that is in turn expecting a resource or something but I cannot find anything regarding this error. Though the error code 80070032 appears in numerous postings elsewhere, they tend to not be in relation to the Powershell command. Any help out there would be fantastic!
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.