Forums on Intune, SCCM, and Windows 11

Welcome to the forums. Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your topics and posts, as well as connect with other members through your own private inbox!

SOLVED Problems upgrading SCCM to 1910

  • Thread starter Thread starter Sam L-W
  • Start date Start date
  • Replies Replies 4
  • Views Views 14K
Status
Not open for further replies.

Sam L-W

New Member
Messages
4
Reaction score
1
Points
3
Hi,

I recently upgraded our site to 1910 and have a few issues even though the upgrade task seemed to have completed successfully with all green ticks!
1. SCCM MP was broken - it complained that the pre-requisite client upgrade (CCMsetup.exe) was failing. I fixed it by uninstalling (ccmsetup.exe /uninstall) then removing the MP site server role, deleting everything in HKLM\Software\Microsoft\CCM, rebooting then reinstalling. This seemed to fix the issue however now if I go to control panel -> configuration manager is pretty much blank except the "Components" tab that only lists 4 components and not what I'd expect - any ideas?
2. clients will not upgrade - I get the same error as I was seeing on the server from ccmsetup.exe: in CCMsetup.log I get:

MSI: Setup failed due to unexpected circumstances
The error code is 8000FFFF
File C:\WINDOWS\ccmsetup\{15714557-4FAA-4A6B-A33A-8F64D3FF658A}\client.msi installation failed. Error text: ExitCode: 1603
Action: CcmRegisterWmiMofFile.
ErrorMessages:
Setup failed due to unexpected circumstances
The error code is 8000FFFF
InstallFromManifest failed 0x80070643

any ideas on where I can go from here?

Thanks,
Sam
 
Ok - to answer some of my own problems:

regarding the client install: I noticed that in the log files there was an error saying that ccmsetup couldnt uninstall prepdrvr.sys. So I manually uninstalled ccm using ccmsetup.exe /uninstall. then ran RUNDLL32.EXE SETUPAPI.DLL,InstallHinfSection DefaultInstall 128 C:\WINDOWS\CCM\prepdrv.inf and then re-installed the client and hey presto - it installs fine. Got the nudge from this article:

I also ran the client setup again on the MP server and hey presto the client seems a lot healthier there too. (still monitoring it)

The problem I have is why this is happening at all - I had no such problems upgrading to 1906 so now I don't know how I'm going to upgrade 200 endpoints while this is an issue! I'm still looking into it but if anyone has any (useful) ideas I'm all ears!

Thanks,

Sam
 
Last edited:
A quick update on this problem after staring at it for a whole day!

It seems the client upgrade works fine when upgrading from client version 5.00.8853.1020 but ALWAYS fails when upgrading 5.00.8853.1006. I am not sure why most of my clients are on this older version (about 80%) but the upgrade fails every time unless I run the command to uninstall prepdrv
 
I am not sure why see that error while upgrading the client agent. Can you try running winmgmt /resetrepository before the upgrade and then check if the upgrade works ?.
 
I dont know either. I got round the issue for most of the machines by right clicking the relevant device collection in sccm and selecting install client, always install and uninstall options. That fixed all but 15 machines.

The remaining 15 I have file and printer sharing blocked by the windows firewall - no idea why, they were built from the same image and have the same policies applied as the rest. For those I did a remote powershell - to enable it through the firewall, uninstall client manually, remove prepdrv.sys and then re-install.

All devices are built from the same windows 10 image so all should have behaved the same. But I got my sledgehammer out (!!) and fixed it - all clients are now upgraded and healthy! I'll see what happens with the client upgrade when the next hotfix/upgrade comes out .
 
Status
Not open for further replies.

Forum statistics

Threads
7,171
Messages
27,989
Members
18,297
Latest member
Kahnrym

Trending content

Back
Top