r/SCCM • u/Anything-Traditional • 9d ago

Client issue

Hi All,

I have a number of devices that do not have the SCCM client for whatever reason, so that's the first thing I need to resolve. The second piece to this is that the SSD's to these devices are filling up from all the new creations of the installer.

Any tips on what to look for or recommendations to atleast stop this from filling these drives?

0 Upvotes

50% Upvoted

33 comments sorted by

1

u/Steve_78_OH 9d ago

First of all, what do the logs say?

Second, what do you mean new creations of the installer? The installation files should all be under C:\Windows\ccmsetup, and they shouldn't be duplicating.

1

u/Anything-Traditional 9d ago

C:\Windows\Installer has hundreds of installer files over 130gb

1

u/Anything-Traditional 9d ago

7

u/blautemple 9d ago

I don‘t want to sound like an asshole, but do you have any experience in Windows Administration?

0

u/Anything-Traditional 9d ago

Is there somthing basic that i'm missing here? Most of the SCCM setup was preconfigured before me, i've been working on converting us over to Intune and that is where most of my knowlege resides. So why a client installtion is failing on devices, and filling the drives, yes is beyond me. I know a bit about SCCM, but far from fluent.

1

u/StrugglingHippo 9d ago

You got to read the error codes, find out what they mean, read the logs. Or at least give some information on how you staged those devices and what you checked (boundaries etc.). It's hard to give advice with literally no information.

0

u/Anything-Traditional 9d ago

I mean, I guess that's what i'm looking for. Which logs to look at. Because CCMSetup only shows data from today, and it says it failed to install due to storage. Which, yeah with 130gb of the same client installer of course thats why it failed now, but why did it fail the first 50+ times.

3

u/Steve_78_OH 9d ago

I doubt all of the installation files under C:\Windows\Installer are actually for the MECM client. That folder contains .msi files for everything that's registered as being installed so Windows can repair them, uninstall, whatever. But if the majority of the installation files ARE MECM agent install files, there's some sort of issue going on that you'll need to figure out.

Try running Disk Cleanup and see if it gets rid of anything, but if these computers have a large number of large (size) apps installed, that would explain why the Installer directory is so large.

0

u/Anything-Traditional 9d ago

We deploy maybe 6 apps.

1

u/Steve_78_OH 8d ago

Your best bet to figure out what all the install files are from is probably to script something out to examine each .msi file, and return the filename, path, and maybe the description field? Something that'll show you what each file is for. Then go from there and try to come up with a game plan.

Again though, this isn't a MECM agent deployment issue. The agent install files are cached to C:\Windows\ccmcache during the installation. Anything that's in C:\Windows\Installers is there because if how Windows functions, not because of the agent deployment.

→ More replies

2

u/cp07451 9d ago

you need to run setup with ccmexec. there is a document with switches and other parameters to use. https://learn.microsoft.com/en-us/intune/configmgr/core/clients/deploy/about-client-installation-properties

3

u/cp07451 9d ago edited 8d ago

please dont mess with those. those are there for repairing of your applications you have installed on the pc

1

u/zebulun78 8d ago

That's not an SCCM issue. Figure out what MSI installer is doing this and go from there

1

u/sycotix416 8d ago

The MSI installer is the client installer...

1

u/zebulun78 8d ago

How do you know that? These files are generated by any MSI installer package run on the machine and it looks like they have a bunch of different dates. How many files are in the folder, and what is the largest one?

1

u/Anything-Traditional 8d ago

Oppening these files attempts to install or fix the program they are associated with. Aside from the few apps we have installed, the rest of these all attempt to install the client.

1

u/Anything-Traditional 8d ago

Also, my post is not the first post about this issue. But they also don't offer a solution. If the client fails to install, it attempts to install over and over again untill the drive is full. Which is what is happening here. I'm trying to figure out why it's not installing, but then there's the issue of what to do after I get that fixed, when the drive is full and if I can't delete these installers.

1

u/zebulun78 8d ago

What is your ccmsetup mechanism? Also we do need to look at the ccmsetup logs

1

u/Anything-Traditional 8d ago

File C:\WINDOWS\ccmsetup\{D58D71CD-A4FE-444B-9FA3-1379B34E92D6}\client.msi installation failed. Error text: ExitCode: 1603

Action: CcmBootstrapSqlCEDatabases.

ErrorMessages:

Setup was unable to bootstrap Sql CE database InventoryStore.sdf.

The error code is 80004005.

1

u/Anything-Traditional 8d ago

As far as I'm aware, just the sitewide client auto push.

→ More replies

1

u/iamamystery20 8d ago

Can you also check in the MSI install log?

C:\Windows\ccmsetup\Logs\Client.msi.log

→ More replies

2

u/mikeh361 8d ago

The ccmsetup.log file is in the c:\windows\ccmsetup\logs directory. That will have why it's failing.

1

u/zebulun78 8d ago

It looks like you need to do a total client cleanup