u/Future_End_4089

It's so frustrating, I am seeing a failure rate of 8-10% across the board. Does anyone know how to fix this?

On ConfigMGR 2043, yes I am aware I have to upgrade, the issue is after the sccm client installs the clients don't report back to the server so imaging continues. Yet if I pxe boot the same station the task sequence finishing fine.

Is the issue DNS? I want to be sure before I bring this up to my network team.

What do you think?

I have tried.

1. Deleting the deployment, making a copy of the deployment and deploying that

2. Re-installing the sccm client

3. Deleting SCCM cache

4. Rebooting endpoints

Still 10 endpoints stuck on Program received.

He always did the same songs every tour. I would have loved to have heard, what are your deep cut wishes?

1. Old L.A. Tonight.

2.Thunder Underground

3. Aimee

So I will ask you guys with more experience in Intune?

Here's the question:. Can intune provide log in log out events per user? from event viewer on the endpoints? or is Zabbix a better tool for the data he wants?

How are you dealing with it? My number is just a tad over 18000.

Aside from deleting the advertisement and waiting for hours until Intune catches up, is there a faster way?

This is new all of a sudden pc's aren't joining the domain during OSD? Deploying Windows 11 25H2 10.0.26200.8524 is anyone else having this issue? if yes how did you fix it?

If you are, is anyone launching osdcloud via a bare metal pxe boot using sccm? are you using OSDCloud v1 or v2? Can you share how you are launching osdcloud using an sccm task sequence?

I work in a college. For the Fall 2026 semester the accounting dept has decided to go with Sage 2025 cdn edition, so this means of of two things.

1. Making a new image with Sage 50 2025 and re-image at least 300 pc's

2. Manually uninstall Sage 50 2024 that are currently on the pcs and install Sage 50 2025 on 300 pc's

I am hoping someone here has some knowledge pushing Sage 50 silently, They are notorious for not providing silent install options.

Are you using DCU, are you using Windows AutoPatch (with driver updates so the bios updates are included)

What is your method? just curious. Always trying to learn a better way to do things.

About 2 years ago I had a dev tenant but I about a year and a half ago I logged in to it and noticed all the features were locked down all my admin accounts locked, so I guess they took at back. Does anyone know if they still offer dev tenants?

Granted it found 4449 devices with a certain app but when i click on the count number to see the devices it always gives me this error.

Is there a way to suggest an application be added to the PMPC catalog?

I have been doing a lot of reading. Microsoft links and blogs etc. As I understand it You must use AutoPatch rings in conjunction with Windows Update rings for example.

In my environment, Active hours are 6am to 11pm let me clarify this is Monday to Friday, Saturday and Sunday it is a ghost town

The install day with reboot we have chosen is Sunday at 11pm this particular setting is set via a Windows Update ring.

The Active hours 6am to 11pm is set via the autopatch rings, as we don't want any random reboots during the week during active hours.

Do I have it right that I must use AutoPatch rings in conjunction with Windows Update rings? or am I over complicating things?

We have 6 devices that monitor the elevators and security gates in our environment. These devices I obviously don’t want a forced reboot in order to install updates, Also there is really no business hours to speak of due to the fact they are always in use.

Here’s my question is the a way with Windows update rings / Autopatch rings to allow the user to choose when they reboot for update purposes?

Let me understand this. What is the best way to renew it. Create a new one on my certificate authority server? or is there another way to re-new it aside from re-creating the certificate?

I have about 800 pc's that I need to update the BIOS on using Intune. Has anyone worked out a bullet proof method? for updating BIOS'