How to fix MDM client issues on MacBook Pro

Question

Level 1

4 points

How to fix MDM client issues on MacBook Pro

I recently bought a logicboard for my 2020 Macbook pro A2338 from ebay. It had no account or mdm on it. I wiped out the old OS and installed a clean MacOS Sequoia 15.1 without a problem. it has no profiles in settings and when I run the command - profiles status -type enrollment it says:

Enrolled via DEP: No

MDM enrollment: No

But when I check launchd.log it shows on boot and also later such messages and other also:

2024-11-14 10:11:09.898224 (system/com.apple.mdmclient.daemon) <Notice>: internal event: WILL_SPAWN, code = 0

2024-11-14 10:11:09.898296 (system/com.apple.mdmclient.daemon) <Notice>: service state: spawn scheduled

2024-11-14 10:11:09.898301 (system/com.apple.mdmclient.daemon) <Notice>: service state: spawning

2024-11-14 10:11:09.898342 (system/com.apple.mdmclient.daemon) <Notice>: launching: xpc event

2024-11-14 10:11:09.900220 (system/com.apple.mdmclient.daemon [1008]) <Notice>: xpcproxy spawned with pid 1008

2024-11-14 10:11:09.900252 (system/com.apple.mdmclient.daemon [1008]) <Notice>: internal event: SPAWNED, code = 0

2024-11-14 10:11:09.900257 (system/com.apple.mdmclient.daemon [1008]) <Notice>: service state: xpcproxy

2024-11-14 10:11:09.900337 (system/com.apple.mdmclient.daemon [1008]) <Notice>: internal event: SOURCE_ATTACH, code = 0

2024-11-14 10:11:09.905126 (system/com.apple.UserEventAgent-System [301]) <Notice>: job state = running

2024-11-14 10:11:09.924911 (system/com.apple.mdmclient.daemon [1008]) <Notice>: service state: running

2024-11-14 10:11:09.924935 (system/com.apple.mdmclient.daemon [1008]) <Notice>: internal event: INIT, code = 0

2024-11-14 10:11:09.924977 (system/com.apple.mdmclient.daemon [1008]) <Notice>: Successfully spawned mdmclient[1008] because xpc event

2024-11-14 10:11:09.939200 (pid/1008 [mdmclient]) <Notice>: uncorking exec source upfront

2024-11-14 10:11:09.939266 (pid/1008 [mdmclient]) <Notice>: created

2024-11-14 10:11:09.964121 (gui/501 [100017]) <Warning>: failed lookup: name = com.duckduckgo.macos.DBP.backgroundAgent, requestor = DuckDuckGo[654], error = 3: No such process

2024-11-14 10:11:09.964538 (gui/501 [100017]) <Warning>: failed lookup: name = com.duckduckgo.macos.vpn, requestor = DuckDuckGo[654], error = 3: No such process

2024-11-14 10:11:09.974317 (system/com.apple.ManagedClient) <Notice>: internal event: WILL_SPAWN, code = 0

2024-11-14 10:11:09.974333 (system/com.apple.ManagedClient) <Notice>: service state: spawn scheduled

2024-11-14 10:11:09.974336 (system/com.apple.ManagedClient) <Notice>: service state: spawning

2024-11-14 10:11:09.974356 (system/com.apple.ManagedClient) <Notice>: launching: ipc (mach)

2024-11-14 10:11:09.975435 (system/com.apple.ManagedClient [1009]) <Notice>: xpcproxy spawned with pid 1009

2024-11-14 10:11:09.975456 (system/com.apple.ManagedClient [1009]) <Notice>: internal event: SPAWNED, code = 0

2024-11-14 10:11:09.975459 (system/com.apple.ManagedClient [1009]) <Notice>: service state: xpcproxy

2024-11-14 10:11:09.975475 (system/com.apple.ManagedClient [1009]) <Notice>: internal event: SOURCE_ATTACH, code = 0

2024-11-14 10:11:09.996685 (system/com.apple.ManagedClient [1009]) <Notice>: service state: running

2024-11-14 10:11:09.996707 (system/com.apple.ManagedClient [1009]) <Notice>: internal event: INIT, code = 0

2024-11-14 10:11:09.996753 (system/com.apple.ManagedClient [1009]) <Notice>: Successfully spawned ManagedClient[1009] because ipc (mach)

2024-11-14 10:11:10.009096 (pid/1009 [ManagedClient]) <Notice>: uncorking exec source upfront

2024-11-14 10:11:10.009124 (pid/1009 [ManagedClient]) <Notice>: created

2024-11-14 10:11:10.040576 (pid/1008 [mdmclient]) <Notice>: uncorking domain

2024-11-14 10:11:10.054608 <Notice>: Remove subscription with token 403

2024-11-14 10:11:10.056072 <Notice>: Remove subscription with token 1285

2024-11-14 10:11:10.064830 (system) <Notice>: Disabling service com.apple.mdmclient.daemon.runatboot

My question is how can I get rid of these. I was told that the logic board has no MDM but I guess there is something left on kernel level or something else. It activated normally and installed normally.

[Re-Titled by Moderator]

MacBook Pro 13″, macOS 15.1

Posted on Nov 14, 2024 12:38 AM

Reply

Answer 1

Owl-53

Level 10

107,565 points

Nov 14, 2024 7:18 AM in response to fnx195

The only other solution I can think of right now

Would require a Visit to an Apple Genius Bar or Certified Apple Service Centre

The would have to re-serialize to LogicBoard to match the Computer Serial Number listed on the Bottom Plate of the computer

Reply

Answer 2

Owl-53

Level 10

107,565 points

Nov 14, 2024 2:16 AM in response to fnx195

Running a Brand New, Directly from Apple, M4 machine with the Original Factory Installed Logicboard

When I run the below command

The results are exactly the same

profiles status -type enrollment

Enrolled via DEP: No

MDM enrollment: No

The 2020 Macbook pro A2338 was purchased, Brand New from Apple , Refurbished by Apple , Private Sale, Auction or anywhere else other than from Apple or Apple Authorized Service Centre ?

Reply

Answer 3

Owl-53

Level 10

107,565 points

Nov 14, 2024 5:05 AM in response to fnx195

Not that I am aware of

As Log as Serial Number of the Computer is Listed in the MDM Service

They can, at any time, take control of this computer - full stop

Reply

Answer 4

Owl-53

Level 10

107,565 points

Nov 14, 2024 4:27 AM in response to fnx195

fnx195 wrote:

Yes, thats ok. but do you have logs in Console/Log reports/launchd.log about mdmclient and managedclient as the above

No.

This brings us back to.

From where has this Computer been purchased from ?

Sorry if may seem pushy, until that question is clearly answered, we can guess

But guessing for a solution to Technical issue, really is not productive

Reply

Answer 5

fnx195 Author

Level 1

4 points

Nov 14, 2024 5:05 AM in response to fnx195

the motherboard itself was bought from a company which is breaking macs for parts. Probably the computer was sold to them by another company who used MDM profiles for their employees. I could possibly ask them for more information. Since I have no profile installed, but recieve such logs I can guess there is something leftover or the company still has this S/N to their apple profile.

Are there any commands that can disable mdmclient agent?

Reply

Answer 6

fnx195 Author

Level 1

4 points

Nov 14, 2024 3:56 AM in response to Owl-53

Yes, thats ok. but do you have logs in Console/Log reports/launchd.log about mdmclient and managedclient as the above

Reply