I don´t think I am the only one, but before in Catalina and earlier
versions, it was possible with jamf connect in DEP deployment to login
the user so a user account was created on the computer -and the user
account was mdmcapable, so user certificat...
So I try once again to understand DepNotify works and think I know the
pieces, but just miss something So what I am trying to test is not in
Dep enrollment, but just use depnotify when installing like firefox when
a user is logged in So I have downlo...
I know there is already betas available, but when first the app is in
the App Store some users will try and upgrade, which we don't want.Do
any know what process or installer name would be so I can be prepared
before hand, so I can restrict the proce...
For the new microsoft update 2019 msupdater script I found the following
#!/bin/sh # # Microsoft AutoUpdate Helper for Jamf Pro # Script Version
1.4 # ## Copyright (c) 2018 Microsoft Corp. All rights reserved. ##
Scripts are not supported under any M...
I have seen the tutorial from Paul Bowden on MSupdate, but for some
reason one command does not work for me on updating As the screenshot
show I am running an older powerpoint (15.39) version and in the
terminal try and update it to 16.19. However, t...
We using both Jamf Connect, for first authentication - but then have to
do manual account creation to get the account MDM enabled. In Catalina
Jamf Connect was enough, but as you write, if using user certs etc it
will not work on Big Sur anymore
I had some clients with issues when using DEP. They couldn´t boot up,
crashed all the time - what I noticed is that when I removed ATP the
issues where gone. But most clients work, but would gladly get rid of
ATP and instead move to Jamf protect
Old Topic - but now in big sur this command is gone So what is the
workarround ? - I used this command after DEP enrollment with Jamf
connect, but now if the user cannot be mdm capable anymore what to do ?
- skip jamf connect ) ?
@mm2270 Was this ever solved ? - I could use similar option We base our
certificates from Jamf information that is at the backend on each
client. So username like jdoe and full name John DoenCertificate in
keychain will then look like John Doen(jdoe)...