Mac Server Profile Manager - settings

Similar Questions

• Energy saver settings missing from the Profile Manager

  I'm under Server.app 5.1 on a MacPro El Capitan (10.11.4) running. I am trying to create a fake profile in the Profile Manager to distribute to my class to illustrate patterns of school boards and want to create one for the energy-saving settings. Unfortunately, this option is missing! Where would it be? That's all I see for the operating system parameters:

  

  Elementary my dear Watson!

  • Ensure that you have a group of devices for the appropriate devices, whether it is portable Mac or iOS devices.

  

  • Register at least a device in this group

  

  • And continue to change the settings for this group
  • You will find savings on OS X to change

  

  • The same would be the procedure for iOS payload found in the part of the iOS.

  Hope that helps

  Leo

• Settings of the proxy in Profile Manager

  Hello

  I have a Mac client where already the proxy settings have been entered (including authentication).

  Now for this client, I create a custom in OSX Profile Manager setting and push it to that client (push is successful). I also see the profile applied in settings > profile.

  But for some reason that the proxy settings are not applied. In the settings > network > and so on the 'old' proxy is always present.

  My proxy (with a weird name like blablabla.bla.com) is not, therefore, apply, I would not be able to browse the internet.

  How the * does this work?

  Is there some good manuals about except "enter proxy here and push it. "Now, little magic and maybe it will work" Apple as 'server administrator manual "?

  I want to change the proxy server on all network connections (Ethernet 1/2, Thunderbolt bridge, WiFi,...) on all clients of my Mac without touching the authentication.

  How can I do?

  Thanks for your help!

  It does not answer your question, but in general I would say that the best way to get the proxy settings is as follows.

  1. Implement a DHCP 252 option code to set the address of a web server that "serves" a proxy.pac aka. WPAD.dat file
  2. Optionally, define a DNS record for your internal network, this might be a record, but more generally would be a CNAME and would be for wpad.yourdomain.com
  3. Create a proxy.pac aka. WPAD.dat file
  4. Do the proxy.pac aka. WPAD.dat file is available via a web server internal and given 2. above ideally via the address http://wpad.yourdomain.com/wpad.dat

  Note: the proxy.pac file contains not only the address of your proxy server, but also rules on websites can bypass the proxy server and sites that can go through the proxy server but bypass authentication.

  The foregoing is a network standard called WPAD - discovery automatic Web Proxy which was originally designed by Microsoft and incorporated originally in Internet Explorer. The advantage of this approach is that if you take your laptop out of Office that does not reconfigure not to use your LAN proxy server.

  It is found that I got Apple to add support not only to set DHCP option codes in their own DHCP server and thus be able to set the option 252 necessary for this purpose, but also separately I got Apple to add support for OS X to act as a client for WPAD to 'learn' which proxy server to use. Apple calls this "Automatic Proxy Discovery" in their proxies in the network settings tab.

  For more information about WPAD, see this article - https://en.wikipedia.org/wiki/Web_Proxy_Autodiscovery_Protocol

  For more information about the current configuration of the leading CAP see - https://en.wikipedia.org/wiki/Proxy_auto-config the proxy.pac and wpad.dat files are really exactly the same thing.

  Note: The authentication settings are not provided via WPAD. It is possible to not use any authentication at all, or if you do what will happen is that the first time that the user gets asked a dialog box is presented asking the name of user and password and it is then saved in the keychain of connection of users - if your using Safari or other Apple applications. If your using Firefox it stores itself. It is a setting by user to another user, even on the same Mac would ask for their own authentication credentials.

• Is it possible to create a Local administrator user when you use the Profile Manager to get the configuration settings

  Hello

  We are studying the use of the Profile Manager of OS X as a way to manage our Enterprise macs.

  One of the demands made by the team, is to create an administrator user, as part of the OS X Profile which is lowered to the customer. The rationale is that this would be a way for the it team get, if the fubar user had their Mac

  I did not see this anywhere in the configuration options of the Profile Manager and so ask the people who use it as part of their everyday Toolbox, to find out if such an option is available.

  Thank you and best regards,

  Madan failed

  No, not with the Profile Manager.

  How you deploying your company Mac?  As institutionally imagery or as BYOD devices?  If image, then the image should contain a coherent local administrator account.  If the active image also the Apple Remote Desktop or SSH, you have a method of mass, control and manage the devices.  If BYOD style, then you are out of luck that the end user is the only one with the key of the device.

  You can take a look at following JAMF Casper.  Once devices are registered, you have the possibility to create accounts (However the common method is to create an account on registration).  If you deploy a BYOD approach, you should also look into DEP program Apple (https://deploy.apple.com) as more DEP JAMF (or other MDM) is a very powerful tool for light to zero touch deployment of systems.

  Reid

  Apple Consultants Network

  Author - "El Capitan Server - Foundation Services.

  Author - "El Capitan Server - Collaboration & control»

  Author - "El Capitan Server - Advanced Services '.

  : IBooks exclusively available in Apple store

• After update to 5.0.15 server, can not activate the OD service and the Profile Manager

  Hi, I have recently updated my Server 5.0.15 under El capitan 10.11.3.

  After that, Service OD and the Profile Manager can be activated server GUI.

  Of course, all users on my network are missing from the list of users; just local users remain.

  Reason: cannot be connected to the node 127.0.0.1

  How can I recreate an OD without use of app server?

  Thank you.

  P. S.

  Of course, even in the local server translates users preferences pane not connected.

  Many Open Directory problems can be solved by taking the following measures. Please test after each of them that you have not already taken it and back up the data before making any changes.

  1. the OD captain must have a static IP address on the local network, not a dynamic address. It must not be connected to the same network with more than one interface; for example, Ethernet and Wi - Fi.

  2. you must have a working DNS serviceand the host name of the server must match the FQDN name. To confirm, select the server by its name in the sidebar of the window of the server application, and then select the Preview tab click the button change on the host name line. The access that your sheet of server, the domain name must be selected. Change the host name, if necessary. The server must have at least three levels (for example, "server.yourdomain.com") name, and the name must not be in the top-level ".local" domain, which is reserved for Hello.

  3. the main DNS server used by the server must be itself, unless you use another internal DNS server. The only DNS server on the clients should be internal, they should get from the DHCP server, as appropriate.

  4. If you have accounts with basic network directories, make sure that the URLS are correct in the user settings. A return status of 45 from the demon authorizationhost in the newspaper may mean that the URL for the installation directory was not being updated after a change in the host name or the file sharing protocol (AFP, SMB, or vice versa.) If the server and the clients run all OS X 10.10 or later, directories should be shared using SMB instead of AFP.

  5. follow these instructions to recreate the Kerberos configuration on the server.

  6. If you use authenticated connection, check the validity of the certificate of the master. The common name must match the host name and domain name. Unselection and then reselect the certificate in.app was reported to have an effect in some cases. Otherwise, delete all certificates and create new ones.

  In the case of a self-signed certificate, create a trust profile in the Profile Manager and deploy it to the customers. On the server, you may need to create the folder

  /etc/openldap/certs

  and place a copy of the certificate of the server, for example:

  /etc/openldap/certs/server-name

  Also add a directive to the file

  /etc/openldap/ldap.conf

  of the form

  TLS_CACERT /etc/openldap/certs/server-name

  7 remove the link, then to connect customers in the preferences users and groups window. Use the FQDN of the master name.

  8 restart the master and clients.

  9. do not connect you to the server with the account of the user of a network.

  10 turn off the internal firewall in use, including third-party "security" software

  11. If you have created replica servers, remove them.

  12. If OD has recently stopped working while it was working before, you can be able to restore automatic backup in/var/db/backups, or a snapshot of the time of this backup Machine.

  13. If there is slapd errors in the log, try the following steps.

  Disable the Open Directory in the server application.

  Enter in a shell:

  cd /var/db/openldap

  sudo -s

  db_recover -c -h authdata

  db_recover -c -h openldap-data

  Turn on Open Directory.

  14 reset database password strategy:

  sudo pwpolicy -clearaccountpolicies

  15. as a last resort, export all users od. In the Open Directory of the server pane, delete the OD server. In some cases, you may need to use the shell to remove the server. Then recreate it and import the users. Make sure that the UID is in the range 1001 +.

• Custom Sidebar settings / profile manager / El Cap

  Hello

  This has been a bug for some time bear.  Basically, I want to customize my file sidebar.plist for my managed network users.   Manager profile account settings 'finder '.  If I upload my sidebar.plist to the profile under custom settings manager, it seems to be ignored.

  Ive tried this on users and groups of devices.  Did anyone had success with this?

  Anyone running custom framed?  I would be very surprised if everyone is happy with the default view.

• A server error has occurred, the Profile Manager after upgrade to osX - 10.11.4 server 5.1

  After the Connection Manager profile with safari and firefox, I get this error message after my upgrade to el captian 10.11.4 and upgrade to Server 5.1.

  "A server error has occurred, please reload the page and try again.

  If this error " persists, please contact your administrator"

  Someone who could give me advice where to start troubleshooting?

  THE SERVER LOG

  PROFILEMANAGER

  Service log:

  ######################################################################

  ##############     START          ###########################################

  ######################################################################

  [738] [08/04/2016 17:48:56.170] I: completed in 232ms s (view: 1, DB: 62). 200 OK [https://macserver.elcapitan.com/magic/do_magic]

  [733] [08/04/2016 18:51:53.312] I: treatment MagicController #admin_will_load (for 1.1.1.1 at 2016-04-08 18:51:53) [POST]

  [733] [08/04/2016 18:51:53.488] I: completed in 157ms (view: 1 DB: 9) | 200 OK [https://macserver.elcapitan.com/magic/admin_will_load]

  [734] [08/04/2016 18:51:54.555] I: treatment MagicController #do_magic (for 1.1.1.1 to the 2016-04-08 18:51:54) [POST]

  [734] [08/04/2016 18:51:55.346] I: completed in 790ms (views: 0dB,: 92). 200 OK [https://macserver.elcapitan.com/magic/do_magic]

  [735] [08/04/2016 18:51:55.476] I: treatment MagicController #do_magic (for 1.1.1.1 to the 2016-04-08 18:51:55) [POST]

  [737] [08/04/2016 18:51:55.712] I: treatment MagicController #do_magic (for 1.1.1.1 to the 2016-04-08 18:51:55) [POST]

  [738] [08/04/2016 18:51:55.741] I: treatment MagicController #do_magic (for 1.1.1.1 to the 2016-04-08 18:51:55) [POST]

  [735] [08/04/2016 18:51:55.773] I: completed in 296ms (view: 0, DB: 73). 200 OK [https://macserver.elcapitan.com/magic/do_magic]

  [739] [08/04/2016 18:51:55.841] I: treatment MagicController #do_magic (for 1.1.1.1 to the 2016-04-08 18:51:55) [POST]

  [738] [08/04/2016 18:51:55.892] I: completed in 151ms (view: DB, 0: 18) | 200 OK [https://macserver.elcapitan.com/magic/do_magic]

  [737] [08/04/2016 18:51:55.943] I: completed in 230ms (view: 0, DB: 60). 200 OK [https://macserver.elcapitan.com/magic/do_magic]

  [739] [08/04/2016 18:51:55.980] E: \253Magic#do_magic-> UserGroup.get_profiles\273 taken unsupported constant not initialized exception InactiveUserGroup to /Applications/Server.app/Contents/ServerRoot/usr/share/devicemgr/backend/vendor /ruby/1.9.1/gems/activesupport-2.3.18/lib/active_support/dependencies.rb:469:in 'load_missing_constant '.

  /Applications/server.app/Contents/ServerRoot/usr/share/devicemgr/backend/vendor /ruby/1.9.1/gems/activesupport-2.3.18/lib/active_support/dependencies.rb:106:in "const_missing_with_dependencies".

  /Applications/server.app/Contents/ServerRoot/usr/share/devicemgr/backend/lib/MD m_library_item_base.rb:22: in 'const_get '.

  /Applications/server.app/Contents/ServerRoot/usr/share/devicemgr/backend/lib/MD m_library_item_base.rb:22: in 'library_item_by_id '.

  /Applications/server.app/Contents/ServerRoot/usr/share/devicemgr/backend/app/Mo dels / profile .rb: 276: in 'owner '.

  /Applications/server.app/Contents/ServerRoot/usr/share/devicemgr/backend/app/Mo dels / profile .rb: 250: in "library_item_type".

  /Applications/server.app/Contents/ServerRoot/usr/share/devicemgr/backend/app/Mo dels / profile .rb: 257: in "modify_attributes".

  /Applications/server.app/Contents/ServerRoot/usr/share/devicemgr/backend/lib/MD m_record_base.rb:184: in 'get_attributes.

  /Applications/server.app/Contents/ServerRoot/usr/share/devicemgr/backend/app/he FPL / user_group_helper.rb:85: in 'get_profiles '.

  "/Applications/Server.app/Contents/ServerRoot/usr/share/devicemgr/backend/App/co ntrollers / magic_controller.rb:180: in ' block ' (5 levels) in do_magic.

  /Applications/server.app/Contents/ServerRoot/usr/share/devicemgr/backend/vendor /ruby/1.9.1/gems/activesupport-2.3.18/lib/active_support/core_ext/benchmark.rb:1 7: in "block in ms.

  /Applications/server.app/Contents/ServerRoot/usr/lib/Ruby/1.9.1/benchmark.rb:29 5: in 'real time '.

  /Applications/server.app/Contents/ServerRoot/usr/share/devicemgr/backend/vendor /ruby/1.9.1/gems/activesupport-2.3.18/lib/active_support/core_ext/benchmark.rb:1 7: in "ms."

  "/Applications/Server.app/Contents/ServerRoot/usr/share/devicemgr/backend/App/co ntrollers / magic_controller.rb:180: in ' block ' (4 levels) in do_magic.

  /Applications/server.app/Contents/ServerRoot/usr/share/devicemgr/backend/vendor /ruby/1.9.1/gems/activerecord-2.3.18/lib/active_record/connection_adapters/abstr act / database_statements.rb:136: in "transaction".

  /Applications/server.app/Contents/ServerRoot/usr/share/devicemgr/backend/config /initializers/dm_rails_monkey_patches.rb:152:in "transaction".

  /Applications/server.app/Contents/ServerRoot/usr/share/devicemgr/backend/vendor /ruby/1.9.1/gems/activerecord-2.3.18/lib/active_record/transactions.rb:182:in "transaction".

  /Applications/server.app/Contents/ServerRoot/usr/share/devicemgr/backend/lib/MD m_utilities.rb:242: in 'process_in_transaction '.

  "/Applications/Server.app/Contents/ServerRoot/usr/share/devicemgr/backend/App/co ntrollers / magic_controller.rb:163: in ' block ' (3 levels) in do_magic.

  /Applications/server.app/Contents/ServerRoot/usr/share/devicemgr/backend/app/co ntrollers / magic_controller.rb:146: in 'each '.

  "/Applications/Server.app/Contents/ServerRoot/usr/share/devicemgr/backend/App/co ntrollers / magic_controller.rb:146: in ' block ' (2 levels) in do_magic.

  /Applications/server.app/Contents/ServerRoot/usr/share/devicemgr/backend/app/co ntrollers / magic_controller.rb:137: in 'each '.

  /Applications/server.app/Contents/ServerRoot/usr/share/devicemgr/backend/app/co ntrollers / magic_controller.rb:137: in 'block in do_magic'

  /Applications/server.app/Contents/ServerRoot/usr/share/devicemgr/backend/app/co ntrollers / magic_controller.rb:127: in 'each '.

  /Applications/server.app/Contents/ServerRoot/usr/share/devicemgr/backend/app/co ntrollers / magic_controller.rb:127: in 'do_magic '.

  /Applications/server.app/Contents/ServerRoot/usr/share/devicemgr/backend/vendor /ruby/1.9.1/gems/actionpack-2.3.18/lib/action_controller/base.rb:1333:in 'perform_action.

  /Applications/server.app/Contents/ServerRoot/usr/share/devicemgr/backend/vendor /ruby/1.9.1/gems/actionpack-2.3.18/lib/action_controller/filters.rb:617:in "call_filters".

  /Applications/server.app/Contents/ServerRoot/usr/share/devicemgr/backend/vendor /ruby/1.9.1/gems/actionpack-2.3.18/lib/action_controller/filters.rb:638:in 'block in run_before_filters'

  /Applications/server.app/Contents/ServerRoot/usr/share/devicemgr/backend/app/co ntrollers / application_controller.rb:111: in 'give_session_to_models '.

  /Applications/server.app/Contents/ServerRoot/usr/share/devicemgr/backend/vendor /ruby/1.9.1/gems/activesupport-2.3.18/lib/active_support/callbacks.rb:178:in "evaluate_method".

  /Applications/server.app/Contents/ServerRoot/usr/share/devicemgr/backend/vendor /ruby/1.9.1/gems/actionpack-2.3.18/lib/action_controller/filters.rb:186:in «call»

  /Applications/server.app/Contents/ServerRoot/usr/share/devicemgr/backend/vendor /ruby/1.9.1/gems/actionpack-2.3.18/lib/action_controller/filters.rb:635:in "run_before_filters".

  /Applications/server.app/Contents/ServerRoot/usr/share/devicemgr/backend/vendor /ruby/1.9.1/gems/actionpack-2.3.18/lib/action_controller/filters.rb:615:in "call_filters".

  /Applications/server.app/Contents/ServerRoot/usr/share/devicemgr/backend/vendor /ruby/1.9.1/gems/actionpack-2.3.18/lib/action_controller/filters.rb:610:in "perform_action_with_filters".

  /Applications/server.app/Contents/ServerRoot/usr/share/devicemgr/backend/vendor /ruby/1.9.1/gems/actionpack-2.3.18/lib/action_controller/benchmarking.rb:68:in 'block in perform_action_with_benchmark'

  /Applications/server.app/Contents/ServerRoot/usr/share/devicemgr/backend/vendor /ruby/1.9.1/gems/activesupport-2.3.18/lib/active_support/core_ext/benchmark.rb:1 7: in "block in ms.

  /Applications/server.app/Contents/ServerRoot/usr/lib/Ruby/1.9.1/benchmark.rb:29 5: in 'real time '.

  /Applications/server.app/Contents/ServerRoot/usr/share/devicemgr/backend/vendor /ruby/1.9.1/gems/activesupport-2.3.18/lib/active_support/core_ext/benchmark.rb:1 7: in "ms."

  /Applications/server.app/Contents/ServerRoot/usr/share/devicemgr/backend/vendor /ruby/1.9.1/gems/actionpack-2.3.18/lib/action_controller/benchmarking.rb:68:in "perform_action_with_benchmark".

  /Applications/server.app/Contents/ServerRoot/usr/share/devicemgr/backend/vendor /ruby/1.9.1/gems/actionpack-2.3.18/lib/action_controller/rescue.rb:160:in "perform_action_with_rescue".

  /Applications/server.app/Contents/ServerRoot/usr/share/devicemgr/backend/vendor /ruby/1.9.1/gems/actionpack-2.3.18/lib/action_controller/flash.rb:151:in "perform_action_with_flash".

  /Applications/server.app/Contents/ServerRoot/usr/share/devicemgr/backend/vendor /ruby/1.9.1/gems/actionpack-2.3.18/lib/action_controller/base.rb:532:in "process".

  /Applications/server.app/Contents/ServerRoot/usr/share/devicemgr/backend/vendor /ruby/1.9.1/gems/actionpack-2.3.18/lib/action_controller/filters.rb:606:in "process_with_filters".

  /Applications/server.app/Contents/ServerRoot/usr/share/devicemgr/backend/vendor /ruby/1.9.1/gems/actionpack-2.3.18/lib/action_controller/base.rb:391:in "process".

  /Applications/server.app/Contents/ServerRoot/usr/share/devicemgr/backend/vendor /ruby/1.9.1/gems/actionpack-2.3.18/lib/action_controller/base.rb:386:in «call»

  /Applications/server.app/Contents/ServerRoot/usr/share/devicemgr/backend/vendor /ruby/1.9.1/gems/actionpack-2.3.18/lib/action_controller/routing/route_set.rb:43 8: in 'call '.

  /Applications/server.app/Contents/ServerRoot/usr/share/devicemgr/backend/vendor /ruby/1.9.1/gems/actionpack-2.3.18/lib/action_controller/dispatcher.rb:87:in 'send '.

  /Applications/server.app/Contents/ServerRoot/usr/share/devicemgr/backend/vendor /ruby/1.9.1/gems/actionpack-2.3.18/lib/action_controller/dispatcher.rb:121:in "_Appel".

  /Applications/server.app/Contents/ServerRoot/usr/share/devicemgr/backend/vendor /ruby/1.9.1/gems/actionpack-2.3.18/lib/action_controller/dispatcher.rb:130:in 'block in build_middleware_stack'

  /Applications/server.app/Contents/ServerRoot/usr/share/devicemgr/backend/vendor /ruby/1.9.1/gems/actionpack-2.3.18/lib/action_controller/string_coercion.rb:25:i n 'call '.

  /Applications/server.app/Contents/ServerRoot/usr/share/devicemgr/backend/vendor /ruby/1.9.1/gems/actionpack-2.3.18/lib/action_controller/string_coercion.rb:25:i n 'call '.

  /Applications/server.app/Contents/ServerRoot/usr/share/devicemgr/backend/vendor /ruby/1.9.1/gems/rack-1.1.6/lib/rack/head.rb:9:in «call»

  /Applications/server.app/Contents/ServerRoot/usr/share/devicemgr/backend/vendor /ruby/1.9.1/gems/rack-1.1.6/lib/rack/methodoverride.rb:24:in «call»

  /Applications/server.app/Contents/ServerRoot/usr/share/devicemgr/backend/vendor /ruby/1.9.1/gems/actionpack-2.3.18/lib/action_controller/params_parser.rb:15:in «call»

  /Applications/server.app/Contents/ServerRoot/usr/share/devicemgr/backend/vendor ruby/1.9.1/gems/actionpack-2.3.18/lib/action_controller/session/abstract_store. RB: 177: in 'call '.

  /Applications/server.app/Contents/ServerRoot/usr/share/devicemgr/backend/vendor /ruby/1.9.1/gems/activerecord-2.3.18/lib/active_record/query_cache.rb:29:in "call block".

  /Applications/server.app/Contents/ServerRoot/usr/share/devicemgr/backend/vendor /ruby/1.9.1/gems/activerecord-2.3.18/lib/active_record/connection_adapters/abstr act / query_cache.rb:34: in 'cache '.

  /Applications/server.app/Contents/ServerRoot/usr/share/devicemgr/backend/vendor /ruby/1.9.1/gems/activerecord-2.3.18/lib/active_record/query_cache.rb:9:in "cache".

  /Applications/server.app/Contents/ServerRoot/usr/share/devicemgr/backend/vendor /ruby/1.9.1/gems/activerecord-2.3.18/lib/active_record/query_cache.rb:28:in «call»

  /Applications/server.app/Contents/ServerRoot/usr/share/devicemgr/backend/vendor /ruby/1.9.1/gems/activerecord-2.3.18/lib/active_record/connection_adapters/abstr act / connection_pool.rb:361: in "call".

  /Applications/server.app/Contents/ServerRoot/usr/share/devicemgr/backend/vendor /ruby/1.9.1/gems/actionpack-2.3.18/lib/action_controller/failsafe.rb:26:in «call»

  /Applications/server.app/Contents/ServerRoot/usr/share/devicemgr/backend/vendor /ruby/1.9.1/gems/rack-1.1.6/lib/rack/lock.rb:11:in "call block".

  < internal: Prelude >: 10: in 'synchronize '.

  /Applications/server.app/Contents/ServerRoot/usr/share/devicemgr/backend/vendor /ruby/1.9.1/gems/rack-1.1.6/lib/rack/lock.rb:11:in «call»

  /Applications/server.app/Contents/ServerRoot/usr/share/devicemgr/backend/vendor /ruby/1.9.1/gems/actionpack-2.3.18/lib/action_controller/dispatcher.rb:106:in «call»

  /Applications/server.app/Contents/ServerRoot/usr/share/devicemgr/backend/vendor /ruby/1.9.1/gems/rails-2.3.18/lib/rails/rack/static.rb:31:in «call»

  /Applications/server.app/Contents/ServerRoot/usr/share/devicemgr/backend/vendor /ruby/1.9.1/gems/rails-2.3.18/lib/rails/rack/log_tailer.rb:17:in «call»

  /Applications/server.app/Contents/ServerRoot/usr/share/devicemgr/backend/vendor /ruby/1.9.1/gems/thin-1.5.1/lib/thin/connection.rb:81:in "pre_process block."

  /Applications/server.app/Contents/ServerRoot/usr/share/devicemgr/backend/vendor /ruby/1.9.1/gems/thin-1.5.1/lib/thin/connection.rb:79:in 'catch '.

  /Applications/server.app/Contents/ServerRoot/usr/share/devicemgr/backend/vendor /ruby/1.9.1/gems/thin-1.5.1/lib/thin/connection.rb:79:in "pre_process".

  /Applications/server.app/Contents/ServerRoot/usr/share/devicemgr/backend/vendor /ruby/1.9.1/gems/thin-1.5.1/lib/thin/connection.rb:54:in "process".

  /Applications/server.app/Contents/ServerRoot/usr/share/devicemgr/backend/vendor /ruby/1.9.1/gems/thin-1.5.1/lib/thin/connection.rb:39:in "receive_data".

  /Applications/server.app/Contents/ServerRoot/usr/share/devicemgr/backend/vendor /ruby/1.9.1/gems/eventmachine-1.0.3/lib/eventmachine.rb:187:in "run_machine".

  /Applications/server.app/Contents/ServerRoot/usr/share/devicemgr/backend/vendor /ruby/1.9.1/gems/eventmachine-1.0.3/lib/eventmachine.rb:187:in 'run '.

  /Applications/server.app/Contents/ServerRoot/usr/share/devicemgr/backend/vendor /ruby/1.9.1/gems/thin-1.5.1/lib/thin/backends/base.rb:63:in 'start '.

  /Applications/server.app/Contents/ServerRoot/usr/share/devicemgr/backend/vendor /ruby/1.9.1/gems/thin-1.5.1/lib/thin/server.rb:159:in 'start '.

  /Applications/server.app/Contents/ServerRoot/usr/share/devicemgr/backend/vendor /ruby/1.9.1/gems/thin-1.5.1/lib/thin/controllers/controller.rb:86:in 'start '.

  /Applications/server.app/Contents/ServerRoot/usr/share/devicemgr/backend/vendor /ruby/1.9.1/gems/thin-1.5.1/lib/thin/runner.rb:187:in 'run_command.

  /Applications/server.app/Contents/ServerRoot/usr/share/devicemgr/backend/vendor /ruby/1.9.1/gems/thin-1.5.1/lib/thin/runner.rb:152:in 'run! '

  /Applications/server.app/Contents/ServerRoot/usr/share/devicemgr/backend/thin:1 1: turnkey"< >".

  [739] [08/04/2016 18:51:55.991] F: NameError (uninitialized constant InactiveUserGroup):

  Vendor/Ruby/1.9.1/Gems/ActiveSupport-2.3.18/lib/active_support/Dependencies.RB: 469: in "load_missing_constant".

  Vendor/Ruby/1.9.1/Gems/ActiveSupport-2.3.18/lib/active_support/Dependencies.RB: 106: in "const_missing_with_dependencies".

  lib/mdm_library_item_base. RB:22: in 'const_get '.

  lib/mdm_library_item_base. RB:22: in 'library_item_by_id '.

  App/Models/Profile.RB:276:in 'owner '.

  App/Models/Profile.RB:250:in "library_item_type".

  App/Models/Profile.RB:257:in "modify_attributes".

  lib/mdm_record_base. RB:184: in 'get_attributes.

  App/helpers/user_group_helper. RB:85: in 'get_profiles '.

  App/Controllers/magic_controller. "RB:180: in ' block ' (5 levels) in do_magic.

  App/Controllers/magic_controller. "RB:180: in ' block ' (4 levels) in do_magic.

  Vendor/Ruby/1.9.1/Gems/ActiveRecord-2.3.18/lib/active_record/connection_adapter s/abstract/database_statements.rb:136:in "transaction".

  config/Initializers/dm_rails_monkey_patches. RB:152: in "transaction".

  Vendor/Ruby/1.9.1/Gems/ActiveRecord-2.3.18/lib/active_record/transactions. RB:18 2: in the "transaction".

  lib/mdm_utilities. RB:242: in 'process_in_transaction '.

  App/Controllers/magic_controller. "RB:163: in ' block ' (3 levels) in do_magic.

  App/Controllers/magic_controller. RB:146: in 'each '.

  App/Controllers/magic_controller. "RB:146: in ' block ' (2 levels) in do_magic.

  App/Controllers/magic_controller. RB:137: in 'each '.

  App/Controllers/magic_controller. RB:137: in 'block in do_magic'

  App/Controllers/magic_controller. RB:127: in 'each '.

  App/Controllers/magic_controller. RB:127: in 'do_magic '.

  Vendor/Ruby/1.9.1/Gems/actionpack-2.3.18/lib/action_controller/base. RB:1333: in 'perform_action.

  n Vendor/Ruby/1.9.1/Gems/actionpack-2.3.18/lib/action_controller/Filters.RB:617:i 'call_filters '.

  Vendor/Ruby/1.9.1/Gems/actionpack-2.3.18/lib/action_controller/Filters.RB:638:i n 'run_before_filters block '.

  App/Controllers/application_controller. RB:111: in 'give_session_to_models '.

  Vendor/Ruby/1.9.1/Gems/ActiveSupport-2.3.18/lib/active_support/callbacks. RB:178: in 'evaluate_method '.

  Vendor/Ruby/1.9.1/Gems/actionpack-2.3.18/lib/action_controller/Filters.RB:186:i n 'call '.

  n Vendor/Ruby/1.9.1/Gems/actionpack-2.3.18/lib/action_controller/Filters.RB:635:i 'run_before_filters '.

  n Vendor/Ruby/1.9.1/Gems/actionpack-2.3.18/lib/action_controller/Filters.RB:615:i 'call_filters '.

  n Vendor/Ruby/1.9.1/Gems/actionpack-2.3.18/lib/action_controller/Filters.RB:610:i 'perform_action_with_filters '.

  Vendor/Ruby/1.9.1/Gems/actionpack-2.3.18/lib/action_controller/benchmarking. RB: 68: 'block in perform_action_with_benchmark'

  Vendor/Ruby/1.9.1/Gems/actionpack-2.3.18/lib/action_controller/benchmarking. RB: 68: in "perform_action_with_benchmark".

  Vendor/Ruby/1.9.1/Gems/actionpack-2.3.18/lib/action_controller/Rescue.RB:160:in "perform_action_with_rescue".

  Vendor/Ruby/1.9.1/Gems/actionpack-2.3.18/lib/action_controller/Flash.RB:151:in "perform_action_with_flash".

  Vendor/Ruby/1.9.1/Gems/actionpack-2.3.18/lib/action_controller/base. RB:532: in 'process '.

  n Vendor/Ruby/1.9.1/Gems/actionpack-2.3.18/lib/action_controller/Filters.RB:606:i 'process_with_filters '.

  Vendor/Ruby/1.9.1/Gems/actionpack-2.3.18/lib/action_controller/base. RB:391: in 'process '.

  Vendor/Ruby/1.9.1/Gems/actionpack-2.3.18/lib/action_controller/base. RB:386: in 'call '.

  Vendor/Ruby/1.9.1/Gems/actionpack-2.3.18/lib/action_controller/Routing/route_se t.rb:438: in "call".

  Vendor/Ruby/1.9.1/Gems/actionpack-2.3.18/lib/action_controller/Dispatcher.RB:87: "send."

  Vendor/Ruby/1.9.1/Gems/actionpack-2.3.18/lib/action_controller/Dispatcher.RB:12 1: in "_Appel".

  Vendor/Ruby/1.9.1/Gems/actionpack-2.3.18/lib/action_controller/Dispatcher.RB:13 0: in 'block in build_middleware_stack'

  Vendor/Ruby/1.9.1/Gems/actionpack-2.3.18/lib/action_controller/string_coercion. RB: 25: in 'call '.

  Vendor/Ruby/1.9.1/Gems/actionpack-2.3.18/lib/action_controller/string_coercion. RB: 25: in 'call '.

  Vendor/Ruby/1.9.1/Gems/actionpack-2.3.18/lib/action_controller/params_parser. RB: 15: in 'call '.

  Vendor/Ruby/1.9.1/Gems/actionpack-2.3.18/lib/action_controller/session/abstract _store.rb:177: in "call".

  Vendor/Ruby/1.9.1/Gems/ActiveRecord-2.3.18/lib/active_record/query_cache. RB:29: in "block in the call.

  Vendor/Ruby/1.9.1/Gems/ActiveRecord-2.3.18/lib/active_record/connection_adapter s/abstract/query_cache.rb:34:in "cache".

  Vendor/Ruby/1.9.1/Gems/ActiveRecord-2.3.18/lib/active_record/query_cache. RB:9:i n "cache".

  Vendor/Ruby/1.9.1/Gems/ActiveRecord-2.3.18/lib/active_record/query_cache. RB:28: in "call".

  Vendor/Ruby/1.9.1/Gems/ActiveRecord-2.3.18/lib/active_record/connection_adapter s/abstract/connection_pool.rb:361:in «call»

  Vendor/Ruby/1.9.1/Gems/actionpack-2.3.18/lib/action_controller/Failsafe.RB:26:i n 'call '.

  < internal: Prelude >: 10: in 'synchronize '.

  Vendor/Ruby/1.9.1/Gems/actionpack-2.3.18/lib/action_controller/Dispatcher.RB:10 6: in 'call '.

  Vendor/Ruby/1.9.1/gems/rails-2.3.18/lib/rails/rack/static. RB:31: in 'call '.

  Vendor/Ruby/1.9.1/gems/rails-2.3.18/lib/rails/rack/log_tailer. RB:17: in 'call '.

  Vendor/Ruby/1.9.1/Gems/Thin-1.5.1/lib/Thin/Connection.RB:81:in 'block in pre_process ".

  Vendor/Ruby/1.9.1/Gems/Thin-1.5.1/lib/Thin/Connection.RB:79:in 'catch '.

  Vendor/Ruby/1.9.1/Gems/Thin-1.5.1/lib/Thin/Connection.RB:79:in "pre_process".

  Vendor/Ruby/1.9.1/Gems/Thin-1.5.1/lib/Thin/Connection.RB:54:in 'process '.

  Vendor/Ruby/1.9.1/Gems/Thin-1.5.1/lib/Thin/Connection.RB:39:in "receive_data".

  Vendor/Ruby/1.9.1/Gems/eventmachine-1.0.3/lib/eventmachine. RB:187: in 'run_machine '.

  Vendor/Ruby/1.9.1/Gems/eventmachine-1.0.3/lib/eventmachine. RB:187: in 'run '.

  Vendor/Ruby/1.9.1/Gems/Thin-1.5.1/lib/Thin/backends/base. RB:63: in 'start '.

  Vendor/Ruby/1.9.1/Gems/Thin-1.5.1/lib/Thin/Server.RB:159:in 'start '.

  Vendor/Ruby/1.9.1/Gems/Thin-1.5.1/lib/Thin/Controllers/Controller.RB:86:in 'start '.

  Vendor/Ruby/1.9.1/Gems/Thin-1.5.1/lib/Thin/Runner.RB:187:in 'run_command.

  Vendor/Ruby/1.9.1/Gems/Thin-1.5.1/lib/Thin/Runner.RB:152:in 'run '!

  end: 11: in "< main >".

  [739] [08/04/2016 18:51:55.992] I: rendered /Applications/Server.app/Contents/ServerRoot/usr/share/devicemgr/backend/public 500.html (500 internal server error)

  [740] [08/04/2016 18:51:55.998] I: treatment MagicController #do_magic (for 1.1.1.1 to the 2016-04-08 18:51:55) [POST]

  [741] [08/04/2016 18:51:56.060] I: treatment MagicController #do_magic (for 1.1.1.1 at 2016-04-08 18:51:56) [POST]

  [740] [08/04/2016 18:51:56.278] I: completed in s 280ms (view: 1, DB: 115). 200 OK [https://macserver.elcapitan.com/magic/do_magic]

  [741] [08/04/2016 18:51:56.368] I: completed in 307ms (views: 1, DB: 177). 200 OK [https://macserver.elcapitan.com/magic/do_magic]

  mpass1 kernel [0]: gfx: Surf 15ea9c9f: clientClose:

  8 April 18:52:14 macserver kernel [0]: gfx: Surf 15ea9c9f: SetIDMode: id = 330484187 mode = 0 x 24

  8 April 18:52:14 macserver kernel [0]: gfx: Surf 15ea9c9f: clientClose:

  ######################################################################

  ##############     END               ##########################################

  ######################################################################

  OS X Server: Troubleshooting with the Profile Manager

  How to reset the profile to its original State Manager

  Update Server 3.2.1 fail

• Firefox profile Manager automatically saves the current settings, addons, bookmarks on a profile?

  Or what I need to manually record?

  The profile that you select in the Profile Manager when Firefox starts is the profile that will keep your personal data. All profiles are independent, so if you switch to another profile, then, you will have access to the data stored in another profile.

  • http://KB.mozillazine.org/Profile_folder_-_Firefox

• Can not launch Firefox successfully because of the Mac application profile settings?

  The team, currently I am working for Oracle and must use Firefox to access our CRM applications.
  Whenever I run the firefox.app, I get the following error message?
  Could not initialize the safety component of the application. The most likely cause is problems with the files in the directory of the profile of your application. Please check that this directory has no restriction of read/write and your hard disk is not full or close to full. It is recommended that you exit the application and correct the problem. If you continue to use this session, you may see incorrect application behavior when you access security features.

  Am currently using OS X Lion - mountain
  Downloaded Firefox 21.

  Your comments would be very appreciated

  Give this command in a Terminal
  /Applications/Firefox.app/Contents/MacOS/Firefox-bin Pei

  Create a new profile as a test to see if your profile is the source of the problems.
  See "create a profile":

  • https://support.Mozilla.org/KB/Profile-Manager-create-and-remove-Firefox-profiles
  • http://KB.mozillazine.org/Standard_diagnostic_-_Firefox#Profile_issues

  Profile backup and restore

  • http://KB.mozillazine.org/Profile_backup
  • https://support.Mozilla.org/en-us/KB/back-and-restore-information-Firefox-profiles
  • http://KB.mozillazine.org/Transferring_data_to_a_new_profile_-_Firefox

• Profile Manager - failed to install the remote access profile in the domain environment &amp; multi-Active Network Directory

  Hi all

  I am a COMPUTER administrator for a college and I am trying to fix what seems to be the last hurdle in getting the Profile Manager works correctly.

  I worked for a while now trying to get the Profile Manager capable of pushing the device and profiles for Mac in our group network environment. I was able to operate intermittently, but not often. Most of the time I'm unable to install the remote management profile.

  When you try to install the remote management profile, I give myself one of the two errors-

  The first error is:

  The Installation of the profile failed.

  The «TeleManagement (com.apple.config. » profile (Server.FQDN.mdm:GUID) "could not be installed because of an unexpected error < MDMResponseStatus:500 >

  (Obviously server.fqdn and GUID are placeholders for their actual values)

  

  The second mistake is:

  The Installation of the profile failed.

  Failed to contact the Protocol SCEP server to ""http://server.fqdn: 1640/CEP / "."

  

  The server Mac OS X 10.11.4 works

  OS X Server is version 5.1

  Client Mac is for most running 10.10.4

  Here's a quick run down on the environment and the steps I have already taken to solve the problem.

  • The network is an Active Directory with several networks multi-domain environment. I mainly work with two different networks, each associated with one of the two areas.
  • The Mac server hosting the Profile Manager is a Mac Pro. The two network cards is used, each on one of the two networks. The Mac server is joined to the domain in the primary forest.
  • I opened all the ports and IP ranges for Apple's Push Notification service for two on our firewall and tested networks between the two networks to ensure that the AFN is accessible.
  • I created a static DNS entry for the server in the DNS zone for the main domain. I also have a separate DNS zone for the DNS record for the interface on the secondary network. I also confirmed that Macs see the correct IP address of the Mac server for their network.
  • I tried to change the settings for network access for the Profile Manager. The first error seems to happen when the Profile Manager are restricted to the network the Mac client is not connected. This same error also occurs if I open Manager profile access to "all networks".
  • I have experiemented with the different certificate types. In general, I use the self-signed certificates that are generated automatically. In this scenario, I install the profile Trust first (which works seamlessly regardless of network or domain). I also tried to use a certificate for Code signing signed with our own CA to sign the profile of remote management. The same errors will occur no matter what certificates are used.
  • The second error occurs when the access profile manager is limited to the same network that is connected to the Mac client
  • I ran Wireshark captures on several client computers, as well as on the Mac server interfaces and haven't seen any traffic blocked or rejected that seemed related to the Profile Manager
  • I've deleted and rebuilt my OD master
  • I also scoured newspapers for clues Profile Manager and haven't found much
  • In addition, I have also studied the problem and error codes/etc widely and have not found a lot of useful information
  • I don't know there are any other troubleshooting steps I took as well, but I've been question bout this for awhile and I don't remember everyone.

  That's a strange thing - I had it working for Mac on the main network and the domain. However, I discovered that the Mac on the secondary network and the field was unable to download the profile of remote management. This is when I started to change the Profile Manager, access network, which eventually introduce the problem on Macs connected to the primary/field of experimentation network. Change access return settings in Profile Manager does not restore functionality for pimps who worked.

  Another thing odd in this test scenario all - Mac on the network high school/area would not install remote profile unless management I temporarily moved it to the main network (I do not untie / reassign to one the main domain on these Macs) I could get the profile of remote management to install and then pushing profiles has worked. Even more strange, it's the Mac that I had to move temporarily secondary network to the main network to allow remote management profile install only works always as long as the Profile Manager are restricted to the secondary network and 'the Mac'. However, Macs in the same room, on the same network in the same field, using the exact image even get the errors described above.

  The only thing I have not yet done is delete/reconstruction Profile Manager. I would really like to avoid this if possible. Solutions that involve something like Casper or other software integration AD for Macs are also a non-starter.

  I'm happy to elaborate if necessary. I appreciate the help.

  Okay, I think I can find the root cause.

  Before this discovery, I had completely rebuilt Profile Manager. Now, I managed by pushing the management profile remote for Mac in the two fields/networks. However, many of them still refuse to install remote management profile.

  Macs who encounter the problem are all were imaged using NetRestore using an image captured from an another similar iMac. IMac even that was used to build the image has now been reassigned in a test of Mac. I found that when you attempt to register one of the Mac who had received this image it shows already as "registered" when you go to "mydevices" on my Mac server. I also noticed that they all have the serial number of the test Mac when viewing their "register". Among the issues of Macs, I activated the lock of the device from the page "mydevices" for the so-called problematic Mac registered (showing the serial number of the iMac used to create the image) and it locked the iMac used to create the image - not the Mac issue.

  This tells me that the CID (or Mac equivalent) is set on the Mac CID used to create the image for all of the Mac said image was deployed to. If it's a Windows box I have a sysprep prior to deployment or could perform a rearm after the fact. I am unaware of how to perform similar functions in OS X.

  I tested also since on some Macs that do not have this image, and they are able to register and install the profile of Managing remotely with success.

  If anyone has any suggestions on how to reset the CID (the computer ID) under OS X, I'd appreciate it. Thank you.

• Profile Manager - MDM identity certificate

  Hello

  I would like to know what exactly is the "certificate of identity MDM? I find in my managed devices (SETTINGS-> General-> management-> remote management-> details-> (identity device certificates)). It is issued by Mac OS x OpenDirectory intermediate CA.

  I don't use signed code profiles (I read it is necessary to re-register device after expiry of cert).

  I use current Apple configurator to connect to the Profile Manager. More high certificate is valid for one year from date of registration.

  I would like to know it is possible to create more than a year instead of this certificate, and what I need to do before the expiry of this certificate to be able to update all of my devices in the Profile Manager without taking devices in my hand?

  I have approximately 50 iphones (unattended) related to my Profile Manager. Now, I want to connect another 50 iPads, this time as devices supervised.

  But I'm afraid what happens when the certificate expires, want to avoid this or at least to know what (and when) I need to do to avoid losing touch with my Profile Manager.

  Kind regards

  Kacper

  While it is possible to create your own certificate for sustainable computer server any longer, and your own code signing certificate last longer, it is not possible to change the length of time for the certificate of Push Notifications generated Apple is also necessary for an MDM solution.

  So you go without worrying about being stuck at a certificate that must be renewed annually and that you have to do before you run it really means more as every 11 months.

• Group missing user profile manager

  Server 4.0 on OSX 10.11.1 using.

  I have installation manager profile and work for our students by having the mac server running as the OD server with the profile as well as related to the AD Manager to allow users.  In the Profile Manager, I have a group called student that contains all the users of the student.  He works well with the Manager to set up profile settings to customize the user experience however I noticed today that 1 student shows is no longer as in the Group of students in the Profile Manager.  In two RFAS and editor of search on the mac Server directory the user shows as a member of the student group.

  I can't understand why this appears a user is no longer in the Group Manager profile when everything clearly shows them as a member.

  Problem has to do with LDAP on our Active Directory settings.  The MaxPageSize was too weak, as mentioned in Mac OS x: first 1000 results when querying Active Directory - Apple Support

• How to export the list of devices in the Profile Manager?

  Hello

  is there a way to export the list of devices in the Profile Manager on a mini mac running OS Server 5.3?

  Thank you

  How to export data from device in the Profile Manager

  How to export a list of devices and their info?

• Lack the profile can not access the Profile Manager, cannot be continued

  Yahoo somehow accessed and changed the settings of my browsers safari and firefox, could not change the settings for search engine default for more than a minute, even remove engine from yahoo wouldn't last a minute, so I deleted firefox, re-uploaded, now my profile is missing...

  I can not access the Profile Manager via the Terminal, I can't do anything, Firefox is not operational at this time and I don't know how to fix it.

  In Mac OS X v10.7 and later versions, the ~/Library folder is a hidden folder.

  • http://KB.mozillazine.org/Show_hidden_files_and_folders#Mac_os_x
  • http://KB.mozillazine.org/Profile_folder_-_Firefox#Mac
  • < User > /users//Library/Application Support/Firefox/profiles.ini

  See also:

  • https://support.Mozilla.org/KB/how-run-Firefox-when-your-profile-missing-or-inacc

• Integration of the Mac server

  We are currently using Exchange 2008 and recently bought a Mac mini and configure the server to this topic. Please be warned, I am a newbie to this.

  My question is in 3 parts

  1. How can I know what is the address for Active Directory, because everything I try, including the IP address just don't allow me to bind to active directory or to access the directory, even on a client machine
  2. Can you suggest good online videos to help set up the server to work seamlessly with user accounts that have been created
  3. Is there a way to auto users of the registry on the server without using their machines and wrap. The India is not auto register the program so I'm a bit stuck there.

  Exchange 2007 (there was no 2008 Exchange, Exchange 2007 running on Windows Server 2008 didn't exist) is old, and as far as I know is no longer supported by Microsoft, it is also likely to have problems with compatibility with the latest Mac or Apple Mail clients in El Capitan and Outlook for Mac 2016. I highly recommend giving your IT Department a good kick to get them to upgrade to Exchange at least 2010 and preference Exchange 2013 or 2016.

  Your IT Department must also be able to tell what your Active Directory server address, this should be a fully qualified domain name address and not an IP address.

  If you mean by register/registration machines pulling a whole new machine and is it setup for a user, then there are two main approaches.

  1. DEP aka. Device registration program, what you say, it's perhaps not available in India. If it was it would involve the prior registration of the computer through DEP that would then trigger an auto-enrollment in an MDM aka. Mobile device management server, for example Apple own Profile Manager or JAMF Casper Suite. The MDM server would then drive parameters to the Mac including Mac connection to Active Directory or Open Directory.
  2. A system of NetBoot/NetRestore, it could be Apple has the NetBoot service, or DeployStudio or JAMF Casper Suite. With this, you can start a new Mac on the same network as your NetBoot server and tell it to "restore" an image from the server. I use DeployStudio myself and after that he has restored/installed the operating system he can do various configuration steps additional as you reconnect to Active Directory or Open Directory, install programs and even enroll again in an MDM server.

  Note: both DeployStudio and JAMF Casper Suite it is possible to have replica servers synchronized to the master server branch/remote offices.