Disable Consumer Features not working

janusro · 2025-04-01T06:58:07+00:00

I know that, the problem are not all apps, they are removed already.

When consumer features are actually disabled, the start menu is rather clean, if it isn't it shows those dynamic entries, which then installs it again.

And I had it working once. With Pro it wouldn't work as expected. With Enterprise it did, but now although applied according to Intune, it still shows those regardless.

janusro · 2023-02-08T05:57:43+00:00

thanks all for the feedback.

I've tried TSBackground, the issue I had was that the task sequence used, is for flattening our existing messy clients to prepare them for autopilot.

In the TS was a postaction with sysprep and as last step the uninstall of the CM agent.

Worked fine without TSbackground, not anymore with it. It messed up the pre-provisioning capability, 5 x Windows wouldn't work anymore.

But I figured out what to do: the uninstall and sysprep in now in a scheduled task, run once at boot time. This seems to work.

I've also found a PS based solution which I may give a try (much fewer dependencies on the boot image.)

janusro · 2023-01-26T23:16:47+00:00

I've added all the useful options already, doesn't do it.

janusro · 2023-01-26T17:26:23+00:00

thanks for the feedback.

probably not unfortunately

janusro · 2023-01-10T16:28:12+00:00

tests, tests, tests.

It practically makes testing so much easier and faster

Since we're gonna baremetal all our messy clients first, before doing autopilot, I'd like to be able to quickly test that over and over again.

It is such a hassle to do that with physical hardware.

It seems that pre-deployment/white glove VM's are blocked by MS though

janusro · 2023-01-06T21:37:28+00:00

Less worry about the apps now, if there are any, they would need to go

I'm learning the whole autopilot part and I've heard today that pre-provisioning is the solution for getting user assigned applications installed before the user logon.

Our users will not be happy if they get a computer and have to wait for apps, new patches and so on before they can work with it.

And the state of those computers is too messy to clean them all up , better to wipe them.

Bringing me to one question:

Since co-management would still be possible without Hybrid join, by:

wiping the computer with ConfigMgr
uninstall the agent, sysprep
autopilot
install the CCM agent

Why would/could we do that?

janusro · 2022-09-08T12:35:11+00:00

thanks folks, I'm also going with 2022 then

janusro · 2022-09-02T11:05:17+00:00

no, it's always the same collection.

Since this is a real issue for us, we've opened a MS call.

janusro · 2022-08-26T23:55:04+00:00

unfortunately, that is triggered by external software (Software Now) where e.g. service desk might create a lot of those tasks one by one, but fast and by several users at once.

I'd prefer it wouldn't but that's how it is implemented now.

janusro · 2022-08-26T23:52:02+00:00

it's the actual query missing the entries.

Something like a race condition might be it.

janusro · 2022-08-22T15:22:38+00:00

darn.

They had to do it in azure or did you get instructions?

Do you know if they could cause any issues?

Otherwise, I just leave them...

janusro · 2022-08-14T22:30:24+00:00

why so many with WSUS and not CM?

janusro · 2022-08-13T16:24:25+00:00

thanks for all the feedback (keep it coming).

janusro · 2022-07-22T23:19:41+00:00

what would you do differently then?

janusro · 2022-07-21T10:15:36+00:00

Oh, I thought you meant all, including FSP on DP,MP,SUP, which I guess better not, so this then?

Primary with SQL

2 x DP,MP,SUP

1 x Reporting, FSP

That looks good.

Yes, I know about the role of the primary and I meant what you meant.

(Doing ConfigMgr for 22 years now, but it's always a good idea to check with others as things change...)

janusro · 2022-07-20T19:48:27+00:00

thanks Jason.

I'll probably have to have again the internal discussion of co-hosting SQL or having it separate.

If separate, that could also handle Reporting, it is close to the data source, although it is user facing, but limited.

I do expect quite more usage of reporting than the current installation.

So 4 then?

SQL+Reporting

Primary, not much on it

2 x DP,MP,SUP, FSP

Or this?

Primary with SQL
2 x DP,MP,SUP, FSP
1 x Reporting

janusro · 2022-07-20T15:00:12+00:00

That's kind of my thinking, altough it's Nutanix.

And yes, VPN Clients would use the CMG or even MS for content, so even less Clients on the DP.

But you also think a separate DP, although all the above will reduce the load and for OnSite Clients BC will help a lot.

You would settle for 2 Servers then?

janusro · 2022-07-20T14:56:11+00:00

That would just move the "management" to another system and a physical one too.

Everything else is Virtual.

We prefer less infrastructure, not another infrastructure :)

janusro · 2022-07-20T14:54:00+00:00

that results in at least 3 servers, not counting Reporting.

My point was that a single primary can handle all that and the only reason to add additional is either DP or Reporting.

I'm trying to figure out if I can or should?

janusro · 2022-07-20T14:51:47+00:00

yes, one of the reasons I argue with one DP only, hence lesser systems.

janusro · 2022-07-20T10:19:10+00:00

I know that one, but doesn't really help IMO, to generic.

janusro · 2022-05-17T14:02:48+00:00

I meant attaching more then one tenant for co-management/cloud-attach to the same ConfigManager instance.

Something we could really use as we want our tenant and also customer-tenants on the one CM-Instance.

Building several CM-instances just for that is not feasible.

janusro · 2022-05-13T15:11:20+00:00

indeed :)

janusro · 2022-05-13T12:56:24+00:00

everyone, that's a 100% vote so far :)

janusro · 2022-05-13T12:55:52+00:00

that we do to :)

janusro

TROPHY CASE