Apple Deployment Programs Thank you for participating in the Device Enrollment Program. On September 13 Apple will release updated software license agreements. Your Program Agent must go to the deployment website and accept the following agreements to continue to use the program:Note: If you’re using Casper, then the errors you’ll see will be something along the lines of:
For more information please see this support article:https://support.apple.com/kb/HT203063.
- iOS 10 Software License Agreement
- Software License Agreement for macOS Sierra
Unable to Contact https://mdmenrollment.apple.com
krypted September 12th, 2016
krypted May 6th, 2016
/usr/bin/mddiagnose -f testThe output is then test.mdsdiagnostic, a directory with a CrashReporter, spindump, Samples, DiagnosticReports, a few system.log exports, and a diagnostic.log. You can then view your log using the more command (or cat or less or whatevers)
more ~/test.mddiagnostic/diagnostic.logHere, you’ll see the output of a bunch of scripts that were run. I find that this is the most informational aspect of what I get from the mddiagnose output. Every time I’ve actually fixed an issue here, it’s been with this output. The other aspect of mddiagnose that I’ve found useful is checking permissions and paths. Here, you can answer the simple question of whether mdutil has permissions to check a path. We’ll do so using the -p option:
mddiagnose -p /Library/Application\ Support/AppifitizerEnjoy!
krypted December 15th, 2015
krypted October 24th, 2013
sudo changeip -checkhostnameThe address and host names should look correct and match what you see in the Server application’s Next Steps drawer.
Primary address = 10.0.0.1 Current HostName = mdm.krypted.com DNS HostName = mdm.krypted.com The names match. There is nothing to change. dirserv:success = “success”Provided everything is cool with the hostname, open the Server Admin application from /Applications/Server. Then click on Settings in the application’s toolbar. At the Settings screen, click on Services. Click on the checkbox for the Open Directory Service and click Save to see the Open Directory service appear in the Server Admin sidebar. Then, click on Open Directory in the Server Admin sidebar and then click on the Change… button to bring up the Open Directory Assistant. At the Choose Directory Role screen, click on Set up an Open Directory replica and then click on the Continue button. At the Replica and Certificate Authority screen, provide the name or IP address of the Open Directory master in the IP address or DNS name of master field. Actually, just use the name. If you can’t find the Open Directory Master by name, then you should really fix that before moving forward. Also provide the Open Directory administrative user name in the Domain administrator’s short name field and that account’s password in the Domain administrator’s password field. If you have any problems, make sure you can ssh into the Open Directory master using this account. Also, new in Lion, there’s a CA administrator’s email address field. Put in here, what you put into the Organization Information field back when you promoted the master (screen shown for posterity). If you’ve lost track of the email address you used, keep in mind that the SSL certificate can be used to grab that information. Open Keychain Access, click on Certificates, search for the host name of the Master (this is all from the master, btw) and then do a Get Info and you’ll see the Email Address used. Anyway, back to the Open Directory Assistant on the new Replica. Click on the Continue button and finish the wizard to complete promoting the replica. That’s it. Don’t forget to check your logs when the promotion is complete. I’ve been finding that there are a lot of issues with promoting Replicas in Lion so far. This has meant bad directory data (import + export), bad DNS, security policies, using a bad username and password combination (not the systems fault) and other issues. To fix the bad directory data, you have to import and export (in my experience not an archive and restore but an actual export and import, losing all passwords in the process). The Next Steps drawer can guide you through the host names/DNS issues. For security policies, I’ve found the following command to work for me (run on the master):
slapconfig -setmacosxodpolicy -binding enabledFor the username and password issues (the errors don’t always tell you what is or is not a password problem) I have found using dscl or even Workgroup Manager to test the login is an important step. You can also still use slapconfig for Open Directory replicas, a great way to get a lot of detailed information. For example, one time, the replica promotion was failing because the server was a member server in a domain; however, using slapconfig -getstyle the server simply reported as Standalone. To promote a replica, you will define want to make sure to include the new –certAdminEmail option, followed by the email address on that certificate of the master. This is then followed with the address and the admin username of the master. For example:
slapconfig -createreplica --certAdminEmail email@example.com odm.pretendco.com diradminWhen slapconfig runs, it will give you a detailed account of where it failed and why. Finally, I have noticed that some machines fail in the Server Admin GUI and Server Admin simply doesn’t show that the machine failed, but instead just makes the system a member to the server. When this happens, I have always had to clean install the system in order to get it to promote to a replica again, properly. To make sure a replica is indeed a replica, consult slapconfig:
slapconfig -getstyleNow is when you get to have a little more Jäger. This whole process hopefully only took about 5 to 10 minutes, so it’s about time anyways. If the process took longer, then I hope you didn’t wait until now for round 2. Later, we’ll discuss directory trees and using those as a means of building sites. For that, you might want to move onto something a bit stronger, like mescaline.
krypted March 1st, 2012
-500 = Camera agent went offline -501 = Podcast Producer agent timed out -502 = Agent failed to communicate -600 = Tunnel protocol mismatch -601 = Tunnel could not connect -602 = Tunnel timed out -603 = Tunnel failed 1 = Internal camera agent is failing 3 = Capture failed to run 4 = Capture already running 5 = Capture is not paused 6 = The locking mechanism encountered a mutex failure 7 = The unlocking mechanism encountered a mutex failure 8 = Camera agent cannot communicate with the file system 9 = Podcast Capture has no capture device available 10 = SG initialization failure 11 = Audio channel initialization failure 12 = Video channel initialization failure 13 = Video creation failed 14 = QuickTime encountered an Error 15 = QuickTime SG failed to start 16 = QuickTime SG failed to prepare 17 = QuickTime SG failed to set the data processor 18 = QuickTime compression session failed 19 = QuickTime Decompression session failed 20 = QuickTime SGIdle failed to initialize 21 = QuickTime data failed to process 22 = QuickTime sound failed to compress 23 = Writing the movie frame failed 24 = Could not start the process (a bit cryptic) 25 = Could not stop the process (a bit cryptic) 26 = Could not finalize the movie 27 = Action not supported 28 = Action could not resume processing 29 = OpenGL error 30 = Insufficient disk space for the action (or could not reach file system) 31 = Invalid/incorrect command 32 = Screen grab functionality disabled
krypted November 17th, 2009
Posted In: Mac OS X Server
krypted April 23rd, 2006
Posted In: Xsan