I just began evaluating ReEnroller because we're gearing up to move to Jamf Cloud and one group of devices will need to migrate from a different server up to the cloud one.

However, from my tests it seems that ReEnroller does not respect or have a place where I can enter any proxy information. All our network traffic goes through a proxy, unless we get special exceptions to bypass the proxy. I'm not sure, but I think if ReEnroller had a place to enter the proxy address and port, it may be able to use that to get through and connect to the Jamf cloud server.

Is there a way this can be added to the tool in the near future? Because right now I'm not able to use this software. I imagine I'm not the only one in such a situation as there are a lot of highly regulated environments like ours where all traffic goes thru a proxy.

Thanks for considering this.

Just curious if this api call script would work in a policy with a normal quick add package or if I have to use it along side the ReEnroller? (IE are the policy screenshots in the help file showing the trigger that is specific to what the ReEnroller calls?)
Gabe Shackney
Princeton Public Schools

When deselecting "Call Automated Device Enrollment" it has no effect. It still executes it and also sets the key in settings.plist inside the pkg to

callEnrollment
yes

Not finding much documentation, so not sure where to go from here, but seeing repeated failures due to being unable to remove the MDM profile:

Thu Jul 16 03:10:08 my-mbp jamf[15237]: Checking for policy ID 225...
Thu Jul 16 03:10:12 my-mbp jamf[15237]: Executing Policy Utility - Migrate from
Thu Jul 16 03:10:16 my-mbp jamf[15237]: Verifying package integrity...
Thu Jul 16 03:10:16 my-mbp jamf[15237]: Installing ReEnroller-.pkg...
Thu Jul 16 03:10:20 my-mbp [ReEnroller]:  Reading settings from: /Library/Application Support/JAMF/ReEnroller/settings.plist
Thu Jul 16 03:10:20 my-mbp [ReEnroller]:  ================================
Thu Jul 16 03:10:20 my-mbp [ReEnroller]:  ReEnroller Version: 4.6.6
Thu Jul 16 03:10:20 my-mbp [ReEnroller]:  ================================
Thu Jul 16 03:10:20 my-mbp [ReEnroller]:  New enrollment: false
Thu Jul 16 03:10:20 my-mbp [ReEnroller]:  Maximum number of retries: 3
Thu Jul 16 03:10:20 my-mbp [ReEnroller]:  Found configuration for new Jamf Pro server: .jamfcloud.com, begin migration
Thu Jul 16 03:10:20 my-mbp [ReEnroller]:  No configuration profiles included for install.
Thu Jul 16 03:10:20 my-mbp [ReEnroller]:  newServer: .jamfcloud.com
newPort: 443
Thu Jul 16 03:10:20 my-mbp [ReEnroller]:  Found old Jamf Pro server: https://llc.jamfcloud.com/
Thu Jul 16 03:10:20 my-mbp [ReEnroller]:  Starting the enrollment process for the new Jamf Pro server. Attempt: 2
Thu Jul 16 03:10:20 my-mbp [ReEnroller]:  Attempting to connect to new Jamf Server (.jamfcloud.com) and download the jamf binary.
Thu Jul 16 03:10:20 my-mbp [ReEnroller]:  Performing a health check against: https://.jamfcloud.com:443/healthCheck.html
Thu Jul 16 03:10:20 my-mbp jamf[15237]: Successfully installed ReEnroller-.pkg.
Thu Jul 16 03:10:21 my-mbp [ReEnroller]:  healthCheck response code: 200
Thu Jul 16 03:10:21 my-mbp [ReEnroller]:  healthCheck response: []
Thu Jul 16 03:10:21 my-mbp [ReEnroller]:  health check result: [], looks good.
Thu Jul 16 03:10:21 my-mbp [ReEnroller]:  download URL: https://.jamfcloud.com:443/bin/jamf.gz
Thu Jul 16 03:10:22 my-mbp [ReEnroller]:  Response from server - Status code: 200
Thu Jul 16 03:10:22 my-mbp [ReEnroller]:  File successfully downloaded.
Thu Jul 16 03:10:22 my-mbp [ReEnroller]:  download result: binary downloaded
Thu Jul 16 03:10:22 my-mbp [ReEnroller]:  Downloaded jamf binary from new server (https://.jamfcloud.com:443).
Thu Jul 16 03:10:22 my-mbp [ReEnroller]:  /usr/local/jamf/bin/jamf backed up to /Library/Application Support/JAMF/ReEnroller/backup/jamf.bak.
Thu Jul 16 03:10:22 my-mbp [ReEnroller]:  Using jamf binary from the new server.
Thu Jul 16 03:10:22 my-mbp [ReEnroller]:  Re-created alias for jamf binary in /usr/local/bin.
Thu Jul 16 03:10:22 my-mbp [ReEnroller]:  Start backing up items.
Thu Jul 16 03:10:22 my-mbp [ReEnroller]:  /Library/Application Support/JAMF/JAMF.keychain backed up to /Library/Application Support/JAMF/ReEnroller/backup/JAMF.keychain.bak.
Thu Jul 16 03:10:22 my-mbp [ReEnroller]:  Successfully backed up jamf keychain
Thu Jul 16 03:10:22 my-mbp [ReEnroller]:  /Library/Preferences/com.jamfsoftware.jamf.plist backed up to /Library/Application Support/JAMF/ReEnroller/backup/com.jamfsoftware.jamf.plist.bak.
Thu Jul 16 03:10:22 my-mbp [ReEnroller]:  Successfully backed up jamf plist
Thu Jul 16 03:10:22 my-mbp [ReEnroller]:  ConfigurationProfiles is not backed up on machines with High Sierra or later due to SIP.
Thu Jul 16 03:10:22 my-mbp [ReEnroller]:  Starting the new enrollment.
Thu Jul 16 03:10:22 my-mbp [ReEnroller]:  High Sierra (10.13) or later. Checking MDM status.
Thu Jul 16 03:10:24 my-mbp [ReEnroller]:  profile list:
1

Thu Jul 16 03:10:24 my-mbp [ReEnroller]:  Unable to remove MDM using the jamf binary, attempting remote command.
Thu Jul 16 03:10:24 my-mbp [ReEnroller]:  profile list:
1

Thu Jul 16 03:10:24 my-mbp jamf[7463]: Daemon shutdown completed
Thu Jul 16 03:10:24 my-mbp jamf[7463]: Daemon exiting
Thu Jul 16 03:10:25 my-mbp jamf[15396]: Informing the JSS about login for user
Thu Jul 16 03:10:25 my-mbp jamf[15396]: Daemon starting
Thu Jul 16 03:10:26 my-mbp jamf[15397]: Upgrading jamf agent...
Thu Jul 16 03:10:27 my-mbp jamf[15396]: Unable to move /Library/Application Support/JAMF/tmp/jamfAgent to /usr/local/jamf/bin/jamfAgent: Error Domain=NSCocoaErrorDomain Code=4 "“jamfAgent” couldn’t be moved to “bin” because either the former doesn’t exist, or the folder containing the latter doesn’t exist." UserInfo={NSSourceFilePathErrorKey=/Library/Application Support/JAMF/tmp/jamfAgent, NSUserStringVariant=(
Move
), NSDestinationFilePath=/usr/local/jamf/bin/jamfAgent, NSFilePath=/Library/Application Support/JAMF/tmp/jamfAgent, NSUnderlyingError=0x7fc9f9a36460 {Error Domain=NSPOSIXErrorDomain Code=2 "No such file or directory"}}
Thu Jul 16 03:10:27 my-mbp jamf[15396]: The file “jamfAgent” doesn’t exist.
Thu Jul 16 03:10:27 my-mbp jamf[15396]: Daemon finished loading
Thu Jul 16 03:10:28 my-mbp jamf[15396]: Informing the JSS about login for user
Thu Jul 16 03:10:29 my-mbp jamf[15397]: Checking for policies triggered by "apiMDM_remove" for user ""...
Thu Jul 16 03:10:42 my-mbp [ReEnroller]:  Attempt 1 to remove MDM through remote command.
Thu Jul 16 03:10:43 my-mbp [ReEnroller]:  profile list:
1

Thu Jul 16 03:10:43 my-mbp jamf[15396]: Daemon shutdown completed
Thu Jul 16 03:10:43 my-mbp jamf[15396]: Daemon exiting
Thu Jul 16 03:10:44 my-mbp jamf[15509]: Informing the JSS about login for user
Thu Jul 16 03:10:45 my-mbp jamf[15509]: Daemon starting
Thu Jul 16 03:10:45 my-mbp jamf[15509]: Daemon finished loading
Thu Jul 16 03:10:45 my-mbp jamf[15509]: Informing the JSS about login for user
Thu Jul 16 03:10:46 my-mbp jamf[15510]: Checking for policies triggered by "apiMDM_remove" for user ""...
Thu Jul 16 03:11:00 my-mbp [ReEnroller]:  Attempt 2 to remove MDM through remote command.
Thu Jul 16 03:11:00 my-mbp [ReEnroller]:  profile list:
1

Thu Jul 16 03:11:00 my-mbp jamf[15509]: Daemon shutdown completed
Thu Jul 16 03:11:00 my-mbp jamf[15509]: Daemon exiting
Thu Jul 16 03:11:01 my-mbp jamf[15612]: Informing the JSS about login for user
Thu Jul 16 03:11:02 my-mbp jamf[15612]: Daemon starting
Thu Jul 16 03:11:03 my-mbp jamf[15612]: Daemon finished loading
Thu Jul 16 03:11:03 my-mbp jamf[15612]: Informing the JSS about login for user
Thu Jul 16 03:11:03 my-mbp jamf[15613]: Checking for policies triggered by "apiMDM_remove" for user ""...
Thu Jul 16 03:11:17 my-mbp [ReEnroller]:  Attempt 3 to remove MDM through remote command.
Thu Jul 16 03:11:17 my-mbp [ReEnroller]:  profile list:
1

Thu Jul 16 03:11:17 my-mbp jamf[15612]: Daemon shutdown completed
Thu Jul 16 03:11:17 my-mbp jamf[15612]: Daemon exiting
Thu Jul 16 03:11:18 my-mbp jamf[15715]: Informing the JSS about login for user
Thu Jul 16 03:11:19 my-mbp jamf[15715]: Daemon starting
Thu Jul 16 03:11:20 my-mbp jamf[15715]: Daemon finished loading
Thu Jul 16 03:11:20 my-mbp jamf[15715]: Informing the JSS about login for user
Thu Jul 16 03:11:21 my-mbp jamf[15716]: Checking for policies triggered by "apiMDM_remove" for user ""...
Thu Jul 16 03:11:35 my-mbp [ReEnroller]:  Attempt 4 to remove MDM through remote command.
Thu Jul 16 03:11:35 my-mbp [ReEnroller]:  profile list:
1

Thu Jul 16 03:11:35 my-mbp jamf[15715]: Daemon shutdown completed
Thu Jul 16 03:11:35 my-mbp jamf[15715]: Daemon exiting
Thu Jul 16 03:11:36 my-mbp jamf[15821]: Informing the JSS about login for user
Thu Jul 16 03:11:37 my-mbp jamf[15821]: Daemon starting
Thu Jul 16 03:11:37 my-mbp jamf[15821]: Daemon finished loading
Thu Jul 16 03:11:37 my-mbp jamf[15821]: Informing the JSS about login for user
Thu Jul 16 03:11:38 my-mbp jamf[15822]: Checking for policies triggered by "apiMDM_remove" for user ""...
Thu Jul 16 03:11:52 my-mbp [ReEnroller]:  Attempt 5 to remove MDM through remote command.
Thu Jul 16 03:11:52 my-mbp [ReEnroller]:  profile list:
1

Thu Jul 16 03:11:52 my-mbp jamf[15821]: Daemon shutdown completed
Thu Jul 16 03:11:52 my-mbp jamf[15821]: Daemon exiting
Thu Jul 16 03:11:53 my-mbp jamf[15924]: Informing the JSS about login for user
Thu Jul 16 03:11:54 my-mbp jamf[15924]: Daemon starting
Thu Jul 16 03:11:54 my-mbp jamf[15924]: Daemon finished loading
Thu Jul 16 03:11:54 my-mbp jamf[15924]: Informing the JSS about login for user
Thu Jul 16 03:11:55 my-mbp jamf[15925]: Checking for policies triggered by "apiMDM_remove" for user ""...
Thu Jul 16 03:12:09 my-mbp [ReEnroller]:  Attempt 6 to remove MDM through remote command.
Thu Jul 16 03:12:09 my-mbp [ReEnroller]:  profile list:
1

Thu Jul 16 03:12:09 my-mbp jamf[15924]: Daemon shutdown completed
Thu Jul 16 03:12:09 my-mbp jamf[15924]: Daemon exiting
Thu Jul 16 03:12:11 my-mbp jamf[16027]: Informing the JSS about login for user
Thu Jul 16 03:12:11 my-mbp jamf[16027]: Daemon starting
Thu Jul 16 03:12:11 my-mbp jamf[16027]: Daemon finished loading
Thu Jul 16 03:12:11 my-mbp jamf[16027]: Informing the JSS about login for user
Thu Jul 16 03:12:13 my-mbp jamf[16028]: Checking for policies triggered by "apiMDM_remove" for user ""...
Thu Jul 16 03:12:27 my-mbp [ReEnroller]:  Failed to remove MDM through remote command - exiting
Thu Jul 16 03:12:27 my-mbp [ReEnroller]:  Alert - There was a problem with enrolling your Mac to the new Jamf Server URL at .jamfcloud.com:443. We are rolling you back to the old Jamf Server URL at https://llc.jamfcloud.com/
Thu Jul 16 03:12:27 my-mbp [ReEnroller]:  Moved the backup jamf binary back into place.
Thu Jul 16 03:12:27 my-mbp [ReEnroller]:  Moved the backup keychain back into place.
Thu Jul 16 03:12:27 my-mbp [ReEnroller]:  Moved the backup jamf plist back into place.
Thu Jul 16 03:12:28 my-mbp jamf[16125]: MDM already enabled or not available
Thu Jul 16 03:12:28 my-mbp [ReEnroller]:  MDM Enrolled - getting MDM profiles from old JSS.
Thu Jul 16 03:12:28 my-mbp [ReEnroller]:  Exiting failback.
Thu Jul 16 03:17:28 my-mbp [ReEnroller]:  Reading settings from: /Library/Application Support/JAMF/ReEnroller/settings.plist
Thu Jul 16 03:17:28 my-mbp [ReEnroller]:  ================================
Thu Jul 16 03:17:28 my-mbp [ReEnroller]:  ReEnroller Version: 4.6.6
Thu Jul 16 03:17:28 my-mbp [ReEnroller]:  ================================
Thu Jul 16 03:17:28 my-mbp [ReEnroller]:  New enrollment: false
Thu Jul 16 03:17:28 my-mbp [ReEnroller]:  Maximum number of retries: 3
Thu Jul 16 03:17:28 my-mbp [ReEnroller]:  Found configuration for new Jamf Pro server: .jamfcloud.com, begin migration
Thu Jul 16 03:17:28 my-mbp [ReEnroller]:  No configuration profiles included for install.
Thu Jul 16 03:17:28 my-mbp [ReEnroller]:  newServer: .jamfcloud.com
newPort: 443
Thu Jul 16 03:17:28 my-mbp [ReEnroller]:  Found old Jamf Pro server: https://llc.jamfcloud.com/
Thu Jul 16 03:17:28 my-mbp [ReEnroller]:  Starting the enrollment process for the new Jamf Pro server. Attempt: 3
Thu Jul 16 03:17:28 my-mbp [ReEnroller]:  Attempting to connect to new Jamf Server (.jamfcloud.com) and download the jamf binary.
Thu Jul 16 03:17:28 my-mbp [ReEnroller]:  Performing a health check against: https://.jamfcloud.com:443/healthCheck.html
Thu Jul 16 03:17:29 my-mbp [ReEnroller]:  healthCheck response code: 200
Thu Jul 16 03:17:29 my-mbp [ReEnroller]:  healthCheck response: []
Thu Jul 16 03:17:29 my-mbp [ReEnroller]:  health check result: [], looks good.
Thu Jul 16 03:17:29 my-mbp [ReEnroller]:  download URL: https://.jamfcloud.com:443/bin/jamf.gz
Thu Jul 16 03:17:29 my-mbp [ReEnroller]:  Response from server - Status code: 200
Thu Jul 16 03:17:29 my-mbp [ReEnroller]:  File successfully downloaded.
Thu Jul 16 03:17:29 my-mbp [ReEnroller]:  download result: binary downloaded
Thu Jul 16 03:17:29 my-mbp [ReEnroller]:  Downloaded jamf binary from new server (https://.jamfcloud.com:443).
Thu Jul 16 03:17:29 my-mbp [ReEnroller]:  /usr/local/jamf/bin/jamf backed up to /Library/Application Support/JAMF/ReEnroller/backup/jamf.bak.
Thu Jul 16 03:17:29 my-mbp [ReEnroller]:  Using jamf binary from the new server.
Thu Jul 16 03:17:29 my-mbp [ReEnroller]:  Re-created alias for jamf binary in /usr/local/bin.
Thu Jul 16 03:17:29 my-mbp [ReEnroller]:  Start backing up items.
Thu Jul 16 03:17:29 my-mbp [ReEnroller]:  /Library/Application Support/JAMF/JAMF.keychain backed up to /Library/Application Support/JAMF/ReEnroller/backup/JAMF.keychain.bak.
Thu Jul 16 03:17:29 my-mbp [ReEnroller]:  Successfully backed up jamf keychain
Thu Jul 16 03:17:29 my-mbp [ReEnroller]:  /Library/Preferences/com.jamfsoftware.jamf.plist backed up to /Library/Application Support/JAMF/ReEnroller/backup/com.jamfsoftware.jamf.plist.bak.
Thu Jul 16 03:17:29 my-mbp [ReEnroller]:  Successfully backed up jamf plist
Thu Jul 16 03:17:29 my-mbp [ReEnroller]:  ConfigurationProfiles is not backed up on machines with High Sierra or later due to SIP.
Thu Jul 16 03:17:29 my-mbp [ReEnroller]:  Starting the new enrollment.
Thu Jul 16 03:17:29 my-mbp [ReEnroller]:  High Sierra (10.13) or later. Checking MDM status.
Thu Jul 16 03:17:31 my-mbp [ReEnroller]:  profile list:
1

Thu Jul 16 03:17:31 my-mbp [ReEnroller]:  Unable to remove MDM using the jamf binary, attempting remote command.
Thu Jul 16 03:17:31 my-mbp [ReEnroller]:  profile list:
1

Thu Jul 16 03:17:31 my-mbp jamf[16027]: Daemon shutdown completed
Thu Jul 16 03:17:31 my-mbp jamf[16027]: Daemon exiting
Thu Jul 16 03:17:32 my-mbp jamf[16207]: Informing the JSS about login for user
Thu Jul 16 03:17:32 my-mbp jamf[16207]: Daemon starting
Thu Jul 16 03:17:33 my-mbp jamf[16208]: Upgrading jamf agent...
Thu Jul 16 03:17:33 my-mbp jamf[16207]: Unable to move /Library/Application Support/JAMF/tmp/jamfAgent to /usr/local/jamf/bin/jamfAgent: Error Domain=NSCocoaErrorDomain Code=4 "“jamfAgent” couldn’t be moved to “bin” because either the former doesn’t exist, or the folder containing the latter doesn’t exist." UserInfo={NSSourceFilePathErrorKey=/Library/Application Support/JAMF/tmp/jamfAgent, NSUserStringVariant=(
Move
), NSDestinationFilePath=/usr/local/jamf/bin/jamfAgent, NSFilePath=/Library/Application Support/JAMF/tmp/jamfAgent, NSUnderlyingError=0x7fe964636e10 {Error Domain=NSPOSIXErrorDomain Code=2 "No such file or directory"}}
Thu Jul 16 03:17:33 my-mbp jamf[16207]: The file “jamfAgent” doesn’t exist.
Thu Jul 16 03:17:34 my-mbp jamf[16207]: Daemon finished loading
Thu Jul 16 03:17:34 my-mbp jamf[16207]: Informing the JSS about login for user
Thu Jul 16 03:17:35 my-mbp jamf[16208]: Checking for policies triggered by "apiMDM_remove" for user ""...
Thu Jul 16 03:17:49 my-mbp [ReEnroller]:  Attempt 1 to remove MDM through remote command.
Thu Jul 16 03:17:49 my-mbp [ReEnroller]:  profile list:
1

Thu Jul 16 03:17:49 my-mbp jamf[16207]: Daemon shutdown completed
Thu Jul 16 03:17:49 my-mbp jamf[16207]: Daemon exiting
Thu Jul 16 03:17:50 my-mbp jamf[16321]: Informing the JSS about login for user
Thu Jul 16 03:17:50 my-mbp jamf[16321]: Daemon starting
Thu Jul 16 03:17:51 my-mbp jamf[16321]: Daemon finished loading
Thu Jul 16 03:17:51 my-mbp jamf[16321]: Informing the JSS about login for user
Thu Jul 16 03:17:52 my-mbp jamf[16322]: Checking for policies triggered by "apiMDM_remove" for user ""...
Thu Jul 16 03:18:06 my-mbp [ReEnroller]:  Attempt 2 to remove MDM through remote command.
Thu Jul 16 03:18:06 my-mbp [ReEnroller]:  profile list:
1

Thu Jul 16 03:18:06 my-mbp jamf[16321]: Daemon shutdown completed
Thu Jul 16 03:18:06 my-mbp jamf[16321]: Daemon exiting
Thu Jul 16 03:18:07 my-mbp jamf[16424]: Informing the JSS about login for user
Thu Jul 16 03:18:07 my-mbp jamf[16424]: Daemon starting
Thu Jul 16 03:18:08 my-mbp jamf[16424]: Daemon finished loading
Thu Jul 16 03:18:08 my-mbp jamf[16424]: Informing the JSS about login for user
Thu Jul 16 03:18:09 my-mbp jamf[16425]: Checking for policies triggered by "apiMDM_remove" for user ""...
Thu Jul 16 03:18:22 my-mbp [ReEnroller]:  Attempt 3 to remove MDM through remote command.
Thu Jul 16 03:18:23 my-mbp [ReEnroller]:  profile list:
1

Thu Jul 16 03:18:23 my-mbp jamf[16424]: Daemon shutdown completed
Thu Jul 16 03:18:23 my-mbp jamf[16424]: Daemon exiting
Thu Jul 16 03:18:23 my-mbp jamf[16527]: Informing the JSS about login for user
Thu Jul 16 03:18:24 my-mbp jamf[16527]: Daemon starting
Thu Jul 16 03:18:24 my-mbp jamf[16527]: Daemon finished loading
Thu Jul 16 03:18:24 my-mbp jamf[16527]: Informing the JSS about login for user
Thu Jul 16 03:18:26 my-mbp jamf[16528]: Checking for policies triggered by "apiMDM_remove" for user ""...
Thu Jul 16 03:18:39 my-mbp [ReEnroller]:  Attempt 4 to remove MDM through remote command.
Thu Jul 16 03:18:39 my-mbp [ReEnroller]:  profile list:
1

Thu Jul 16 03:18:39 my-mbp jamf[16527]: Daemon shutdown completed
Thu Jul 16 03:18:39 my-mbp jamf[16527]: Daemon exiting
Thu Jul 16 03:18:40 my-mbp jamf[16630]: Informing the JSS about login for user
Thu Jul 16 03:18:41 my-mbp jamf[16630]: Daemon starting
Thu Jul 16 03:18:41 my-mbp jamf[16630]: Daemon finished loading
Thu Jul 16 03:18:41 my-mbp jamf[16630]: Informing the JSS about login for user
Thu Jul 16 03:18:42 my-mbp jamf[16631]: Checking for policies triggered by "apiMDM_remove" for user ""...
Thu Jul 16 03:18:55 my-mbp [ReEnroller]:  Attempt 5 to remove MDM through remote command.
Thu Jul 16 03:18:55 my-mbp [ReEnroller]:  profile list:
1

Thu Jul 16 03:18:55 my-mbp jamf[16630]: Daemon shutdown completed
Thu Jul 16 03:18:55 my-mbp jamf[16630]: Daemon exiting
Thu Jul 16 03:18:56 my-mbp jamf[16733]: Informing the JSS about login for user
Thu Jul 16 03:18:57 my-mbp jamf[16733]: Daemon starting
Thu Jul 16 03:18:57 my-mbp jamf[16733]: Daemon finished loading
Thu Jul 16 03:18:57 my-mbp jamf[16733]: Informing the JSS about login for user
Thu Jul 16 03:18:59 my-mbp jamf[16734]: Checking for policies triggered by "apiMDM_remove" for user ""...
Thu Jul 16 03:19:13 my-mbp [ReEnroller]:  Attempt 6 to remove MDM through remote command.
Thu Jul 16 03:19:13 my-mbp [ReEnroller]:  profile list:
1

Thu Jul 16 03:19:13 my-mbp jamf[16733]: Daemon shutdown completed
Thu Jul 16 03:19:13 my-mbp jamf[16733]: Daemon exiting
Thu Jul 16 03:19:14 my-mbp jamf[16836]: Informing the JSS about login for user
Thu Jul 16 03:19:14 my-mbp jamf[16836]: Daemon starting
Thu Jul 16 03:19:15 my-mbp jamf[16836]: Daemon finished loading
Thu Jul 16 03:19:15 my-mbp jamf[16836]: Informing the JSS about login for user
Thu Jul 16 03:19:17 my-mbp jamf[16837]: Checking for policies triggered by "apiMDM_remove" for user ""...
Thu Jul 16 03:19:30 my-mbp [ReEnroller]:  Failed to remove MDM through remote command - exiting
Thu Jul 16 03:19:30 my-mbp [ReEnroller]:  Alert - There was a problem with enrolling your Mac to the new Jamf Server URL at .jamfcloud.com:443. We are rolling you back to the old Jamf Server URL at https://llc.jamfcloud.com/
Thu Jul 16 03:19:30 my-mbp [ReEnroller]:  Moved the backup jamf binary back into place.
Thu Jul 16 03:19:30 my-mbp [ReEnroller]:  Moved the backup keychain back into place.
Thu Jul 16 03:19:30 my-mbp [ReEnroller]:  Moved the backup jamf plist back into place.
Thu Jul 16 03:19:31 my-mbp jamf[16934]: MDM already enabled or not available
Thu Jul 16 03:19:31 my-mbp [ReEnroller]:  MDM Enrolled - getting MDM profiles from old JSS.
Thu Jul 16 03:19:31 my-mbp [ReEnroller]:  Exiting failback.
Thu Jul 16 03:24:31 my-mbp [ReEnroller]:  Reading settings from: /Library/Application Support/JAMF/ReEnroller/settings.plist
Thu Jul 16 03:24:31 my-mbp [ReEnroller]:  ================================
Thu Jul 16 03:24:31 my-mbp [ReEnroller]:  ReEnroller Version: 4.6.6
Thu Jul 16 03:24:31 my-mbp [ReEnroller]:  ================================
Thu Jul 16 03:24:31 my-mbp [ReEnroller]:  New enrollment: false
Thu Jul 16 03:24:31 my-mbp [ReEnroller]:  Maximum number of retries: 3
Thu Jul 16 03:24:31 my-mbp [ReEnroller]:  Found configuration for new Jamf Pro server: .jamfcloud.com, begin migration
Thu Jul 16 03:24:31 my-mbp [ReEnroller]:  No configuration profiles included for install.
Thu Jul 16 03:24:31 my-mbp [ReEnroller]:  newServer: .jamfcloud.com
newPort: 443
Thu Jul 16 03:24:31 my-mbp [ReEnroller]:  Found old Jamf Pro server: https://llc.jamfcloud.com/
Thu Jul 16 03:24:32 my-mbp [ReEnroller]:  Starting the enrollment process for the new Jamf Pro server. Attempt: 4
Thu Jul 16 03:24:32 my-mbp [ReEnroller]:  Attempting to connect to new Jamf Server (.jamfcloud.com) and download the jamf binary.
Thu Jul 16 03:24:32 my-mbp [ReEnroller]:  Performing a health check against: https://.jamfcloud.com:443/healthCheck.html
Thu Jul 16 03:24:32 my-mbp [ReEnroller]:  healthCheck response code: 200
Thu Jul 16 03:24:32 my-mbp [ReEnroller]:  healthCheck response: []
Thu Jul 16 03:24:32 my-mbp [ReEnroller]:  health check result: [], looks good.
Thu Jul 16 03:24:32 my-mbp [ReEnroller]:  download URL: https://.jamfcloud.com:443/bin/jamf.gz
Thu Jul 16 03:24:32 my-mbp [ReEnroller]:  Response from server - Status code: 200
Thu Jul 16 03:24:32 my-mbp [ReEnroller]:  File successfully downloaded.
Thu Jul 16 03:24:32 my-mbp [ReEnroller]:  download result: binary downloaded
Thu Jul 16 03:24:32 my-mbp [ReEnroller]:  Downloaded jamf binary from new server (https://.jamfcloud.com:443).
Thu Jul 16 03:24:32 my-mbp [ReEnroller]:  /usr/local/jamf/bin/jamf backed up to /Library/Application Support/JAMF/ReEnroller/backup/jamf.bak.
Thu Jul 16 03:24:32 my-mbp [ReEnroller]:  Using jamf binary from the new server.
Thu Jul 16 03:24:32 my-mbp [ReEnroller]:  Re-created alias for jamf binary in /usr/local/bin.
Thu Jul 16 03:24:32 my-mbp [ReEnroller]:  Start backing up items.
Thu Jul 16 03:24:32 my-mbp [ReEnroller]:  /Library/Application Support/JAMF/JAMF.keychain backed up to /Library/Application Support/JAMF/ReEnroller/backup/JAMF.keychain.bak.
Thu Jul 16 03:24:32 my-mbp [ReEnroller]:  Successfully backed up jamf keychain
Thu Jul 16 03:24:32 my-mbp [ReEnroller]:  /Library/Preferences/com.jamfsoftware.jamf.plist backed up to /Library/Application Support/JAMF/ReEnroller/backup/com.jamfsoftware.jamf.plist.bak.
Thu Jul 16 03:24:32 my-mbp [ReEnroller]:  Successfully backed up jamf plist
Thu Jul 16 03:24:32 my-mbp [ReEnroller]:  ConfigurationProfiles is not backed up on machines with High Sierra or later due to SIP.
Thu Jul 16 03:24:32 my-mbp [ReEnroller]:  Starting the new enrollment.
Thu Jul 16 03:24:32 my-mbp [ReEnroller]:  High Sierra (10.13) or later. Checking MDM status.
Thu Jul 16 03:24:34 my-mbp [ReEnroller]:  profile list:
1

Thu Jul 16 03:24:34 my-mbp [ReEnroller]:  Unable to remove MDM using the jamf binary, attempting remote command.
Thu Jul 16 03:24:34 my-mbp [ReEnroller]:  profile list:
1

Thu Jul 16 03:24:34 my-mbp jamf[16836]: Daemon shutdown completed
Thu Jul 16 03:24:34 my-mbp jamf[16836]: Daemon exiting
Thu Jul 16 03:24:35 my-mbp jamf[17002]: Informing the JSS about login for user
Thu Jul 16 03:24:35 my-mbp jamf[17002]: Daemon starting
Thu Jul 16 03:24:36 my-mbp jamf[17003]: Upgrading jamf agent...
Thu Jul 16 03:24:37 my-mbp jamf[17002]: Unable to move /Library/Application Support/JAMF/tmp/jamfAgent to /usr/local/jamf/bin/jamfAgent: Error Domain=NSCocoaErrorDomain Code=4 "“jamfAgent” couldn’t be moved to “bin” because either the former doesn’t exist, or the folder containing the latter doesn’t exist." UserInfo={NSSourceFilePathErrorKey=/Library/Application Support/JAMF/tmp/jamfAgent, NSUserStringVariant=(
Move
), NSDestinationFilePath=/usr/local/jamf/bin/jamfAgent, NSFilePath=/Library/Application Support/JAMF/tmp/jamfAgent, NSUnderlyingError=0x7fee0b614f70 {Error Domain=NSPOSIXErrorDomain Code=2 "No such file or directory"}}
Thu Jul 16 03:24:37 my-mbp jamf[17002]: The file “jamfAgent” doesn’t exist.
Thu Jul 16 03:24:37 my-mbp jamf[17002]: Daemon finished loading
Thu Jul 16 03:24:38 my-mbp jamf[17002]: Informing the JSS about login for user
Thu Jul 16 03:24:38 my-mbp jamf[17003]: Checking for policies triggered by "apiMDM_remove" for user ""...
Thu Jul 16 03:24:52 my-mbp [ReEnroller]:  Attempt 1 to remove MDM through remote command.
Thu Jul 16 03:24:52 my-mbp [ReEnroller]:  profile list:
1

Thu Jul 16 03:24:52 my-mbp jamf[17002]: Daemon shutdown completed
Thu Jul 16 03:24:52 my-mbp jamf[17002]: Daemon exiting
Thu Jul 16 03:24:53 my-mbp jamf[17117]: Informing the JSS about login for user
Thu Jul 16 03:24:53 my-mbp jamf[17117]: Daemon starting
Thu Jul 16 03:24:54 my-mbp jamf[17117]: Daemon finished loading
Thu Jul 16 03:24:54 my-mbp jamf[17117]: Informing the JSS about login for user
Thu Jul 16 03:24:56 my-mbp jamf[17118]: Checking for policies triggered by "apiMDM_remove" for user ""...
Thu Jul 16 03:25:09 my-mbp [ReEnroller]:  Attempt 2 to remove MDM through remote command.
Thu Jul 16 03:25:10 my-mbp [ReEnroller]:  profile list:
1

Thu Jul 16 03:25:10 my-mbp jamf[17117]: Daemon shutdown completed
Thu Jul 16 03:25:10 my-mbp jamf[17117]: Daemon exiting
Thu Jul 16 03:25:10 my-mbp jamf[17220]: Informing the JSS about login for user
Thu Jul 16 03:25:11 my-mbp jamf[17220]: Daemon starting
Thu Jul 16 03:25:11 my-mbp jamf[17220]: Daemon finished loading
Thu Jul 16 03:25:11 my-mbp jamf[17220]: Informing the JSS about login for user
Thu Jul 16 03:25:13 my-mbp jamf[17221]: Checking for policies triggered by "apiMDM_remove" for user ""...
Thu Jul 16 03:25:26 my-mbp [ReEnroller]:  Attempt 3 to remove MDM through remote command.
Thu Jul 16 03:25:27 my-mbp [ReEnroller]:  profile list:
1

Thu Jul 16 03:25:27 my-mbp jamf[17220]: Daemon shutdown completed
Thu Jul 16 03:25:27 my-mbp jamf[17220]: Daemon exiting
Thu Jul 16 03:25:27 my-mbp jamf[17324]: Informing the JSS about login for user
Thu Jul 16 03:25:28 my-mbp jamf[17324]: Daemon starting
Thu Jul 16 03:25:28 my-mbp jamf[17324]: Daemon finished loading
Thu Jul 16 03:25:28 my-mbp jamf[17324]: Informing the JSS about login for user
Thu Jul 16 03:25:30 my-mbp jamf[17325]: Checking for policies triggered by "apiMDM_remove" for user ""...
Thu Jul 16 03:25:44 my-mbp [ReEnroller]:  Attempt 4 to remove MDM through remote command.
Thu Jul 16 03:25:44 my-mbp [ReEnroller]:  profile list:
1

Thu Jul 16 03:25:44 my-mbp jamf[17324]: Daemon shutdown completed
Thu Jul 16 03:25:44 my-mbp jamf[17324]: Daemon exiting
Thu Jul 16 03:25:45 my-mbp jamf[17428]: Informing the JSS about login for user
Thu Jul 16 03:25:45 my-mbp jamf[17428]: Daemon starting
Thu Jul 16 03:25:45 my-mbp jamf[17428]: Daemon finished loading
Thu Jul 16 03:25:45 my-mbp jamf[17428]: Informing the JSS about login for user
Thu Jul 16 03:25:47 my-mbp jamf[17427]: Checking for policies triggered by "apiMDM_remove" for user ""...
Thu Jul 16 03:26:01 my-mbp [ReEnroller]:  Attempt 5 to remove MDM through remote command.
Thu Jul 16 03:26:01 my-mbp [ReEnroller]:  profile list:
1

Thu Jul 16 03:26:01 my-mbp jamf[17428]: Daemon shutdown completed
Thu Jul 16 03:26:01 my-mbp jamf[17428]: Daemon exiting
Thu Jul 16 03:26:02 my-mbp jamf[17530]: Informing the JSS about login for user
Thu Jul 16 03:26:02 my-mbp jamf[17530]: Daemon starting
Thu Jul 16 03:26:02 my-mbp jamf[17530]: Daemon finished loading
Thu Jul 16 03:26:02 my-mbp jamf[17530]: Informing the JSS about login for user
Thu Jul 16 03:26:04 my-mbp jamf[17531]: Checking for policies triggered by "apiMDM_remove" for user ""...
Thu Jul 16 03:26:18 my-mbp [ReEnroller]:  Attempt 6 to remove MDM through remote command.
Thu Jul 16 03:26:18 my-mbp [ReEnroller]:  profile list:
1

Thu Jul 16 03:26:18 my-mbp jamf[17530]: Daemon shutdown completed
Thu Jul 16 03:26:18 my-mbp jamf[17530]: Daemon exiting
Thu Jul 16 03:26:19 my-mbp jamf[17634]: Informing the JSS about login for user
Thu Jul 16 03:26:19 my-mbp jamf[17634]: Daemon starting
Thu Jul 16 03:26:20 my-mbp jamf[17634]: Daemon finished loading
Thu Jul 16 03:26:20 my-mbp jamf[17634]: Informing the JSS about login for user
Thu Jul 16 03:26:21 my-mbp jamf[17635]: Checking for policies triggered by "apiMDM_remove" for user ""...
Thu Jul 16 03:26:35 my-mbp [ReEnroller]:  Failed to remove MDM through remote command - exiting
Thu Jul 16 03:26:35 my-mbp [ReEnroller]:  Alert - There was a problem with enrolling your Mac to the new Jamf Server URL at .jamfcloud.com:443. We are rolling you back to the old Jamf Server URL at https://llc.jamfcloud.com/
Thu Jul 16 03:26:35 my-mbp [ReEnroller]:  Moved the backup jamf binary back into place.
Thu Jul 16 03:26:35 my-mbp [ReEnroller]:  Moved the backup keychain back into place.
Thu Jul 16 03:26:35 my-mbp [ReEnroller]:  Moved the backup jamf plist back into place.
Thu Jul 16 03:26:36 my-mbp jamf[17742]: MDM already enabled or not available
Thu Jul 16 03:26:36 my-mbp [ReEnroller]:  MDM Enrolled - getting MDM profiles from old JSS.
Thu Jul 16 03:26:36 my-mbp [ReEnroller]:  Exiting failback.

Hi i get a "Failed to create invitation code" error.
What could be the cause?

/Applications/ReEnroller.app/Contents/MacOS/ReEnroller
health check result: ["401", "{  \"httpStatus\" : 401,  \"errors\" : [ ]}"]
health check result: ["200", "[]"]
jpversion: ("11.1.1", "success")
verifySSLCert setting from server: <verifySSLCert>always</verifySSLCert>
[func apiAction] endpoint:
[func apiAction] xml: <?xml version="1.0" encoding="UTF-8" standalone="no"?><computer_invitation><lifetime>2147483647</lifetime><multiple_uses_allowed>true</multiple_uses_allowed><ssh_username>jamf-mgmt</ssh_username><ssh_password_method>1</ssh_password_method><enroll_into_site><id>-1</id></enroll_into_site><keep_existing_site_membership>true</keep_existing_site_membership><create_account_if_does_not_exist>false</create_account_if_does_not_exist><hide_account>false</hide_account><lock_down_ssh>false</lock_down_ssh></computer_invitation>
[apiAction] response code: 401
[apiAction] response: <html> <head> 	<title>Status page</title> </head> <body style="font-family: sans-serif;"> <p style="font-size: 1.2em;font-weight: bold;margin: 1em 0px;">Unauthorized</p> <p>The request requires user authentication</p> <p>You can get technical details <a href="http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.4.2">here</a>.<br> 	Please continue your visit at our <a href="/">home page</a>. </p> </body> </html>

Previously, Ventura devices were successfully migrating from the old JAMF instance to the new JAMF instance. However, since June 3, 2024, this migration process has stopped working on macOS Ventura. Additionally, for macOS Sonoma devices, while the devices appear in the new JAMF portal after migration, but users do not receive the pop-up prompt to install the MDM profile. This issue with Sonoma devices has been occurring since March-April 2024.

Starting with macOS Ventura, the system notifies users when a new background process has been installed.

This alert identifies ReEnroller only by its identifier: Leslie Helou. This should probably be something more accurate to the purpose and meaningful to the user?

Trying to build my reenroll package from the app and getting the error...
Unable to determine verifySSLCert setting on server, setting to always_except_during_enrollment

Cloud Server address is correct, and using Amazon/Jamf provided SSL cert.

If I click okay to move past the message it eventually gives me a timeout error.
Failed to create invitation code. Message: Jamf Cloud - Timeout Jamf

I see in the code that the profiles renew -type enrollment command is used during the process. Is Automated Device Enrollment through ABM with this command attempted first and then fall back to a manual "UIE" enrollment if the Mac is not currently in ABM?

If the above is the case, does the important note in the README still apply for ABM machines enrolled with the profiles command via ABM, or even then, will the end-user be required to manually approve the enrollment profile within System Preferences?

When I run my ReEnroller policy, MDM profiles are removed, but my test machine doesn't seem to enroll into the destination server. I created a new local account with Enrollment privileges only so it should be able to enroll. The MDM profile seems to remove within minutes, which is set to be done BEFORE enrollment to the destination server. I assume the Enrollment to the destination server should occur shortly after... Is there something I am missing here? Does it take a long time to enroll into the destination server? Thank you!

Testing this out on Ventura 13.1 and ABM enrollments are working fine but UAMDM devices are left with no profile as /usr/local/bin/jamf enroll -invitation xxxxxxx -noRecon -noPolicy -noManage is used to add the jamf client. Is that expected behaviour or are my settings wrong?

<key>callEnrollment</key>
<string>yes</string>
<key>createConfSwitches</key>
<string>always</string>
<key>httpProtocol</key>
<string>https</string>
<key>jamfSchool</key>
<integer>0</integer>
<key>markAsMigrated</key>
<false/>
<key>maxRetries</key>
<string>3</string>
<key>mgmtAccount</key>
<string>jamf</string>
<key>migratedAttribute</key>
<string></string>
<key>newEnrollment</key>
<integer>0</integer>
<key>newJSSHostname</key>
<string>jamf.com</string>
<key>newJSSPort</key>
<string>443</string>
<key>postInstallPolicyId</key>
<string></string>
<key>removeAllProfiles</key>
<string>false</string>
<key>removeMDM</key>
<true/>
<key>removeMdmWhen</key>
<string>Before</string>
<key>removeReEnroller</key>
<string>yes</string>
<key>skipHealthCheck</key>
<string>no</string>
<key>skipMdmCheck</key>
<string>no</string>
<key>theNewInvite</key>
<string>xxxxxxxxxxxx</string>

Hi,

We started a migration from SimpleMDM to jamf Pro, it was going well then suddenly we now get "device signature error" trying to run the policy jpsmigrationchec. Not sure if this started due to the upgrade to 10.41.1, but we didn't change the workflow.

Any Help would be greatly appreciated

More testing to do, but I'm not sure what the problem could be.

Configured with the new Jamf Server and correct user/pass. Package and process worked fine on a Mojave machine, but on my clean test Catalina machine it reenrolls in the original server! WTH?

Watched the MDM and config profiles get removed, and then new ones get installed. The MDM profile requires user approval as expected, but it's for the old MDM server.

Looked at the settings.plist from the pkg and newJSSHostname is listed correctly.

Checked that there's not something in DNS pointing the machine to the old server with the new server's URL for some reason (not setup for that anyway).

I'll retry with the same package back on Mojave... can't think why it's pulling the old server though. The reenrollment account doesn't even exist on the old server.

Should the actual filename for ReEnroller.app/Contents/Resources/apiMDM_remove.txt be a .txt or .sh? The comments inside the file say it should be named apiMDM_remove.sh. I am definitely having issues with all the old configuration profiles being removed.