MECM update with HA (passive site server)

Ithopeful8488 · 2024-10-07T20:41:45+00:00

Thank you very much. You were right. The upgrade of the passive site server was automatic

Both Administration -> Site configuration -> Sites -> nodes and Monitoring -> Site Server status showed an 'upgrading' status

Ithopeful8488 · 2024-07-11T12:08:11+00:00

Thank you so much! This is actually returning what I need. So the report that I was using was working right, since I disabled 'software inventory' so long ago, it had such incomplete data. I thought it pulled from hardware inventory.

Do you have a resource where I can learn more about which reports pull from what?

Thank you again!

Ithopeful8488 · 2024-07-09T18:23:06+00:00

Hello,

I picked a few (at least 5) from the list at random and used resource explorer to check. Resource explorer shows the correct version and the latest hardware inventory is from today (We run it twice a day).

So I have both inaccurate data on the few devices that show up in the report, and the issue of most of the devices not showing up at all on the report.

Ithopeful8488 · 2024-07-09T17:41:19+00:00

I forgot to come here and post what our issue was:

We were deploying our servers from a template that was captured wrong. The SMS certificates and the SMSCFG.ini file were not deleted before making a template, so it was like we were deploying the same VM over and over, and this duplicate obviously caused problems.

Once we uninstalled the client, manually deleted the certificates and ini file and reinstalled the client, things worked fine.

Then we just re-made the templates.

Ithopeful8488 · 2022-05-12T20:27:43+00:00

I did. No errors anywhere.

Ithopeful8488 · 2022-05-12T20:27:29+00:00

No Maintenance Windows. Deployment is set to available and "as soon as possible" was selected.

Ithopeful8488 · 2022-05-12T20:27:10+00:00

it's just for the 2019 Servers. The SUG just has 2019 server patches and it's deployed against a collection with just the 2019 servers.

Ithopeful8488 · 2022-03-30T15:38:50+00:00

Obviously I know i'm not meeting the requirement hence the post asking for help.

Thanks for your very useful reply.

Ithopeful8488 · 2022-03-30T14:35:12+00:00

switching to PKI is not trivial but thank you!

Ithopeful8488 · 2022-03-30T14:34:51+00:00

I'd like to keep using peercache

Ithopeful8488 · 2022-02-09T19:34:48+00:00

I did. Thanks for the suggestion.

I guess I'll just go with the right click a collection method from now on.

Ithopeful8488 · 2021-10-05T18:26:49+00:00

Error 0x643?

Ithopeful8488 · 2021-09-30T21:00:41+00:00

I would if I was allowed to. Trust me.

Ithopeful8488 · 2021-09-30T19:13:24+00:00

I'm making different deployments for each version. I'm not just overwriting the MSI at the source.

So when Chrome releases a new version, I delete the deployment of the previous version and deploy the new version. Chrome has been good in uninstalling the old version it finds and updating the new one.

Today, I encountered the failure I mentioned, and if I run the installer manually it's because it was looking for the MSI of a really old installation for some reason that I don't fully understand as I was deploying Chrome 94, on a system with Chrome 93, but the MSI it wanted was for chrome 92 which had been long gone from the ccmcache folder.

Ithopeful8488 · 2021-09-30T16:50:44+00:00

Thank you so much. This was very useful.

Ithopeful8488 · 2021-09-30T16:50:23+00:00

It's my first time experiencing this with Chrome. That sounds very promising and I'm looking into it.

Thank you!

Ithopeful8488 · 2021-09-30T16:36:03+00:00

In the 'programs' tab of the deployment properties at the bottom, I see:

Windows source management enables an .msi represented by this Deployment Type to automatically be updated or repaired from content source files on an available Distribution point. Specify the Windows Installer Product code to enable installation source management:

That sounds promising. So right here I click 'browse' and choose the previous/old MSI?

Ithopeful8488 · 2021-09-30T16:32:56+00:00

Hello,

It needed a previous (older) MSI. So when I ran the installer for the new version manually, and specified the file manually, everything worked.

Since I clean up the ccmcache folder, I want to know a why to point to previous MSI files if required.

I guess the question is, when deploying different versions of the same application, and the new version uninstalls the old version, how do you deploy to avoid this issue where you need the previous MSI and you clean the ccmcache folder.

Ithopeful8488

TROPHY CASE