Jump to content


daov

Established Members
  • Content Count

    7
  • Joined

  • Last visited

Community Reputation

0 Neutral

About daov

  • Rank
    Newbie
  1. Hello, I am deploying a PowerShell script and am wanting it to deploy using SSL. Is this something that is possible in SCCM 2012 R2?
  2. As it turns out, I answered my own question. There appears to be some prerequisites on the WIM file in question if invoking the Powershell cmdlets. This particular image, a leftover for testing these commands only, was not valid for these cmdlets. I built a new image from scratch and tried using the command on it and voila, it worked! Feel free to close this or mark as answered I suppose.
  3. 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!
  4. Howdy, What do you mean, make it mandatory?
  5. hey anyweb, Just wanted you to know that I posted a link to your excellent SCCM guide here on CrashCtrl!
  6. Cool, no worries. We discovered an issue with the audio and your readers should see that warning prior to pushing it in their build image for sure. Regarding the recovery drive, I meant if you boot from a recovery drive that is used to restore the surface to factory, does it still work correctly after wiping all partitions? As in, are you still able to put the surface back to factory after removing the partitions?
  7. Hi Anyweb, I'm one of the proprieters of CrashCtrl. Great article. Regarding the link you have to our site, you have a direct link to the download page where the drivers are being hosted. It would be best to link to the blog entry page as we have posted some updates to the driver files along with some info and warnings regarding the use of those drivers. It's fine either way but there is some info that readers of this post should see. Additionally, I am curious regarding the partition table setup. Did you just choose the default setup for UEFI and it created the three partitions? There have been some folks who have mistakenly moved this or that partition and it resulted in a Surface Pro that would not boot properly. In addition, I am curious. Did you attempt to restore from a recovery drive (created prior to installing Enterprise) after this and did it restore your Surface Pro back to factory?
×
×
  • Create New...