SCCM

Microsoft System Center 2012 R2 Configuration Manager Setup – The network path was not found

Written December 16th, 2014 by
Categories: SCCM
2 comments

This error may be old news to a lot of you, but I’m finally getting back into playing with the goodness known as Microsoft’s System Center Configuration Manager, aka ConfigMgr, aka SCCM, and went through quite a bit to get it set up in my lab.

I jumped right in and did it blindly, which, although worked fine, I did have some speed bumps along the way.

I used several PowerShell one-liners I slapped together to install all the Windows’ features & WADK; however, when I got to the SQL portion of the SCCM installer (where you point to the SQL FQDN, Insance Name, Database name, etc), I kept getting a very generic error that simply said

The network path was not found.

and the log file, ConfigMgrSetupWizard.log, said

Exception details: [System.IO.IOException: The network path was not found.

At face value, this sounds like a simple network connectivity issue. However, I could nslookup the FQDN of the SQL server, which happened to be the same box (all-in-one install), I could ping the FQDN, netstat showed port 1433 was listening, my firewall was turned off, so I started googling.

Everyone points at these as the problem:

  • Firewall
  • SPN
  • SQL Port
  • Maybe a few others I’m forgetting?

As it turned out, I forgot to enable and start the Remote Registry service. That’s all it was. I actually had this in my notes:

Set-Service RemoteRegistry -StartupType Automatic
Start-Service RemoteRegistry

But forgot to run them, lol!

Oh well, live & learn! I think I’m going to do another post regarding the different one-liners I ran to get SCCM 2012 R2 up and running.

SCCM 2007 will not auto apply drivers to newer hardware

Written March 4th, 2013 by
Categories: SCCM
2 comments

The Problem

The hardware inventory file generated by the Auto Apply Drivers step is over 100k, which is the size limit for the MatchDriversSP process SCCM runs to provide the right drivers.  The process then fails.

 

The Solution

Create individual driver packages for each model and have a WMI query to apply those drivers as needed.

 

Read the rest of this entry »

SCCM 2007 OSD Fails with Error 80070032 – Failed to make volume bootable or The request is not supported

Written October 4th, 2012 by
Categories: SCCM
1 Comment »

If you’re using a 12th Generation Dell server, disable the SD Card in the BIOS.  Keep reading for how I discovered this.

We recently received a handful of new Dell R720s and needed to lay down Windows Server 2008 x64. Got everything cabled, powered them up, PXE booted from our SCCM 2007 machine, it formatted the disks, and right when it went to deploy the OS, it failed with (taken from the SCCM Console, advertisement status):

The task sequence execution engine failed executing the action (Apply Operating System) in the group (Install Operating System) with the error code 2147942450
Action output: d-x64.xml”
Not a data image
ApplyOSRetry:
TSLaunchMode: PXE
OSDUseAlreadyDeployedImage: FALSE
Searching for next available volume:
Volume E:\ is a valid target.
Found volume E:!sSystemPart.empty(), HRESULT=80004005 (e:\nts_sms_fre\sms\framework\tscore\diskvolume.cpp,128)
Unable to locate a bootable volume. Attempting to make E:\ bootable.
volume.getDisk() == iBootDisk, HRESULT=80070032 (e:\nts_sms_fre\sms\client\osdeployment\applyos\installcommon.cpp,680)
MakeVolumeBootable( pszVolume ), HRESULT=80070032 (e:\nts_sms_fre\sms\client\osdeployment\applyos\installcommon.cpp,759)
ConfigureBootVolume(targetVolume), HRESULT=80070032 (e:\nts_sms_fre\sms\client\osdeployment\applyos\applyos.cpp,364)
System partition not set
Volume E:\ is not on the boot disk and can not be made bootable.
Failed to make volume E:\ bootable. Please ensure that you have set an active partition on the boot disk before installing the operating system.
The request is not supported. (Error: 80070032; Source: Windows). The operating system reported error 2147942450: The request is not supported.

Read the rest of this entry »

SCCM 2007 OSD – Failed to get client identity (80004005) and Signature Verification Failed

I’m working on importing drivers for Dell’s new 12G servers into our SCCM server for OSD. I got everything imported yesterday, added them to my boot image, created a new boot iso for use in non-PXE enabled networks, and went home for the day.

I get to work today and boot from my ISO I created yesterday and am greeted with the error 80004005, and some nondescript text stating it couldn’t pull a list of tasks. You know, the typical error that you have no idea what it actually means.

I googled it and found 80004005 is “Failed to get client identity”, and some pointed out the time being off may be the cause. I rebooted, BIOS time was maybe 30s off, so I tried again, but exported the smsts.log located in X:\windows\temp\smstslog\ via net use to my workstation. I opened that in SMS Trace, and here’s what I found:

SCCM 80004005

SCCM 80004005

Right there in RED is my error, plain as day, but what wasn’t shown to me in WinPE was the “signature varification failed”. I think it’s worthwhile to note Microsoft misspelled vErification, yup, that’s an A in theirs.

Now, if you google that, I found This Post stating they saw the error after moving their SCCM server to new hardware. We didn’t move to new hardware, we actually went from hardware to virtual, in that we P2V’d our SCCM server last night, which indeed changed the signature of the server.

I updated the boot image’s distribution point, which rebuilds it, then did a refresh for posterity. When that was 100% complete, I recreated the task sequence media boot ISO and all is well again.

Just thought I’d share!

Use Powershell to change SCCM cache directory & cache size

Some of our older servers are running out of disk space on C:, so I needed to change the SCCM cache directory to D:. By default, this is where I wanted it anyway on our servers, leaving C: only for OS-related files. My OSD Task Sequences all have SMSCACHEDIR set to a folder on D in the client configuration step, but I noticed it wasn’t actually working. You know I had to find a way to fix that using powershell :D It actually ended up being really REALLY easy to do…

Read the rest of this entry »

Automated deployment script builds VM, registers in SCCM

This is a follow-up to my last post about fully automated deployment

Below is the script. After it pulls the information from you, it creates the VM, adds the second disk, sleeps for 15 seconds, pulls the MAC from the new VM, creates the computer object in SCCM, adds it to the collection, sleeps for 15 seconds, refreshes the collection, sleeps for 15 seconds, then powers on the VM. If you’ve got a mandatory OSD advertised to the collection specified, and the OSD is fully automated, it will lay down the OS and the computername will be the name you provided to the script.
Read the rest of this entry »

Designed by ThepHuck
Wordpress Themes
Scroll to Top