Resetting Profile Manager

OS X Server.app is having trouble reading profile manager's setting and when I try to reset Profile Manager by running /Applications/Server.app/Contents/ServerRoot/usr/share/devicemgr/backend/wipeDB.sh and I get these errors.
$ /Applications/Server.app/Contents/ServerRoot/usr/share/devicemgr/backend/wipeDB.sh
devicemgr:state = "STOPPED"
postgres:state = "RUNNING"
(in /Applications/Server.app/Contents/ServerRoot/usr/share/devicemgr/backend)
NOTE: Gem.source_index is deprecated, use Specification. It will be removed on or after 2011-11-01.
Gem.source_index called from /Applications/Server.app/Contents/ServerRoot/usr/share/devicemgr/backend/config/../vendor/rails/railties/lib/rails/gem_dependency.rb:21.
NOTE: Gem::SourceIndex#refresh! is deprecated with no replacement. It will be removed on or after 2011-11-01.
Gem::SourceIndex#refresh! called from /Applications/Server.app/Contents/ServerRoot/usr/share/devicemgr/backend/config/../vendor/rails/railties/lib/rails/vendor_gem_source_index.rb:34.
NOTE: Gem::SourceIndex#load_gems_in is deprecated with no replacement. It will be removed on or after 2011-11-01.
Gem::SourceIndex#load_gems_in called from /Library/Ruby/Site/1.8/rubygems/source_index.rb:322.
NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01.
Gem::SourceIndex#add_spec called from /Library/Ruby/Site/1.8/rubygems/source_index.rb:127.
NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01.
Gem::SourceIndex#add_spec called from /Library/Ruby/Site/1.8/rubygems/source_index.rb:127.
NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01.
Gem::SourceIndex#add_spec called from /Library/Ruby/Site/1.8/rubygems/source_index.rb:127.
NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01.
Gem::SourceIndex#add_spec called from /Library/Ruby/Site/1.8/rubygems/source_index.rb:127.
NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01.
Gem::SourceIndex#add_spec called from /Library/Ruby/Site/1.8/rubygems/source_index.rb:127.
NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01.
Gem::SourceIndex#add_spec called from /Library/Ruby/Site/1.8/rubygems/source_index.rb:127.
NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01.
Gem::SourceIndex#add_spec called from /Library/Ruby/Site/1.8/rubygems/source_index.rb:127.
NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01.
Gem::SourceIndex#add_spec called from /Library/Ruby/Site/1.8/rubygems/source_index.rb:127.
NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01.
Gem::SourceIndex#add_spec called from /Library/Ruby/Site/1.8/rubygems/source_index.rb:127.
NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01.
Gem::SourceIndex#add_spec called from /Library/Ruby/Site/1.8/rubygems/source_index.rb:127.
NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01.
Gem::SourceIndex#add_spec called from /Library/Ruby/Site/1.8/rubygems/source_index.rb:127.
NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01.
Gem::SourceIndex#add_spec called from /Library/Ruby/Site/1.8/rubygems/source_index.rb:127.
NOTE: Gem::SourceIndex#initialize is deprecated with no replacement. It will be removed on or after 2011-11-01.
Gem::SourceIndex#initialize called from /Applications/Server.app/Contents/ServerRoot/usr/share/devicemgr/backend/config/../vendor/rails/railties/lib/rails/vendor_gem_source_index.rb:100.
NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01.
Gem::SourceIndex#add_spec called from /Library/Ruby/Site/1.8/rubygems/source_index.rb:91.
NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01.
Gem::SourceIndex#add_spec called from /Library/Ruby/Site/1.8/rubygems/source_index.rb:91.
NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01.
Gem::SourceIndex#add_spec called from /Library/Ruby/Site/1.8/rubygems/source_index.rb:91.
NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01.
Gem::SourceIndex#add_spec called from /Library/Ruby/Site/1.8/rubygems/source_index.rb:91.
NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01.
Gem::SourceIndex#add_spec called from /Library/Ruby/Site/1.8/rubygems/source_index.rb:91.
NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01.
Gem::SourceIndex#add_spec called from /Library/Ruby/Site/1.8/rubygems/source_index.rb:91.
NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01.
Gem::SourceIndex#add_spec called from /Library/Ruby/Site/1.8/rubygems/source_index.rb:91.
NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01.
Gem::SourceIndex#add_spec called from /Library/Ruby/Site/1.8/rubygems/source_index.rb:91.
NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01.
Gem::SourceIndex#add_spec called from /Library/Ruby/Site/1.8/rubygems/source_index.rb:91.
NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01.
Gem::SourceIndex#add_spec called from /Library/Ruby/Site/1.8/rubygems/source_index.rb:91.
NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01.
Gem::SourceIndex#add_spec called from /Library/Ruby/Site/1.8/rubygems/source_index.rb:91.
(in /Applications/Server.app/Contents/ServerRoot/usr/share/devicemgr/backend)
NOTE: Gem.source_index is deprecated, use Specification. It will be removed on or after 2011-11-01.
Gem.source_index called from /Applications/Server.app/Contents/ServerRoot/usr/share/devicemgr/backend/config/../vendor/rails/railties/lib/rails/gem_dependency.rb:21.
NOTE: Gem::SourceIndex#refresh! is deprecated with no replacement. It will be removed on or after 2011-11-01.
Gem::SourceIndex#refresh! called from /Applications/Server.app/Contents/ServerRoot/usr/share/devicemgr/backend/config/../vendor/rails/railties/lib/rails/vendor_gem_source_index.rb:34.
NOTE: Gem::SourceIndex#load_gems_in is deprecated with no replacement. It will be removed on or after 2011-11-01.
Gem::SourceIndex#load_gems_in called from /Library/Ruby/Site/1.8/rubygems/source_index.rb:322.
NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01.
Gem::SourceIndex#add_spec called from /Library/Ruby/Site/1.8/rubygems/source_index.rb:127.
NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01.
Gem::SourceIndex#add_spec called from /Library/Ruby/Site/1.8/rubygems/source_index.rb:127.
NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01.
Gem::SourceIndex#add_spec called from /Library/Ruby/Site/1.8/rubygems/source_index.rb:127.
NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01.
Gem::SourceIndex#add_spec called from /Library/Ruby/Site/1.8/rubygems/source_index.rb:127.
NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01.
Gem::SourceIndex#add_spec called from /Library/Ruby/Site/1.8/rubygems/source_index.rb:127.
NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01.
Gem::SourceIndex#add_spec called from /Library/Ruby/Site/1.8/rubygems/source_index.rb:127.
NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01.
Gem::SourceIndex#add_spec called from /Library/Ruby/Site/1.8/rubygems/source_index.rb:127.
NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01.
Gem::SourceIndex#add_spec called from /Library/Ruby/Site/1.8/rubygems/source_index.rb:127.
NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01.
Gem::SourceIndex#add_spec called from /Library/Ruby/Site/1.8/rubygems/source_index.rb:127.
NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01.
Gem::SourceIndex#add_spec called from /Library/Ruby/Site/1.8/rubygems/source_index.rb:127.
NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01.
Gem::SourceIndex#add_spec called from /Library/Ruby/Site/1.8/rubygems/source_index.rb:127.
NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01.
Gem::SourceIndex#add_spec called from /Library/Ruby/Site/1.8/rubygems/source_index.rb:127.
NOTE: Gem::SourceIndex#initialize is deprecated with no replacement. It will be removed on or after 2011-11-01.
Gem::SourceIndex#initialize called from /Applications/Server.app/Contents/ServerRoot/usr/share/devicemgr/backend/config/../vendor/rails/railties/lib/rails/vendor_gem_source_index.rb:100.
NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01.
Gem::SourceIndex#add_spec called from /Library/Ruby/Site/1.8/rubygems/source_index.rb:91.
NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01.
Gem::SourceIndex#add_spec called from /Library/Ruby/Site/1.8/rubygems/source_index.rb:91.
NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01.
Gem::SourceIndex#add_spec called from /Library/Ruby/Site/1.8/rubygems/source_index.rb:91.
NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01.
Gem::SourceIndex#add_spec called from /Library/Ruby/Site/1.8/rubygems/source_index.rb:91.
NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01.
Gem::SourceIndex#add_spec called from /Library/Ruby/Site/1.8/rubygems/source_index.rb:91.
NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01.
Gem::SourceIndex#add_spec called from /Library/Ruby/Site/1.8/rubygems/source_index.rb:91.
NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01.
Gem::SourceIndex#add_spec called from /Library/Ruby/Site/1.8/rubygems/source_index.rb:91.
NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01.
Gem::SourceIndex#add_spec called from /Library/Ruby/Site/1.8/rubygems/source_index.rb:91.
NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01.
Gem::SourceIndex#add_spec called from /Library/Ruby/Site/1.8/rubygems/source_index.rb:91.
NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01.
Gem::SourceIndex#add_spec called from /Library/Ruby/Site/1.8/rubygems/source_index.rb:91.
NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01.
Gem::SourceIndex#add_spec called from /Library/Ruby/Site/1.8/rubygems/source_index.rb:91.
(in /Applications/Server.app/Contents/ServerRoot/usr/share/devicemgr/backend)
NOTE: Gem.source_index is deprecated, use Specification. It will be removed on or after 2011-11-01.
Gem.source_index called from /Applications/Server.app/Contents/ServerRoot/usr/share/devicemgr/backend/config/../vendor/rails/railties/lib/rails/gem_dependency.rb:21.
NOTE: Gem::SourceIndex#refresh! is deprecated with no replacement. It will be removed on or after 2011-11-01.
Gem::SourceIndex#refresh! called from /Applications/Server.app/Contents/ServerRoot/usr/share/devicemgr/backend/config/../vendor/rails/railties/lib/rails/vendor_gem_source_index.rb:34.
NOTE: Gem::SourceIndex#load_gems_in is deprecated with no replacement. It will be removed on or after 2011-11-01.
Gem::SourceIndex#load_gems_in called from /Library/Ruby/Site/1.8/rubygems/source_index.rb:322.
NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01.
Gem::SourceIndex#add_spec called from /Library/Ruby/Site/1.8/rubygems/source_index.rb:127.
NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01.
Gem::SourceIndex#add_spec called from /Library/Ruby/Site/1.8/rubygems/source_index.rb:127.
NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01.
Gem::SourceIndex#add_spec called from /Library/Ruby/Site/1.8/rubygems/source_index.rb:127.
NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01.
Gem::SourceIndex#add_spec called from /Library/Ruby/Site/1.8/rubygems/source_index.rb:127.
NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01.
Gem::SourceIndex#add_spec called from /Library/Ruby/Site/1.8/rubygems/source_index.rb:127.
NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01.
Gem::SourceIndex#add_spec called from /Library/Ruby/Site/1.8/rubygems/source_index.rb:127.
NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01.
Gem::SourceIndex#add_spec called from /Library/Ruby/Site/1.8/rubygems/source_index.rb:127.
NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01.
Gem::SourceIndex#add_spec called from /Library/Ruby/Site/1.8/rubygems/source_index.rb:127.
NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01.
Gem::SourceIndex#add_spec called from /Library/Ruby/Site/1.8/rubygems/source_index.rb:127.
NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01.
Gem::SourceIndex#add_spec called from /Library/Ruby/Site/1.8/rubygems/source_index.rb:127.
NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01.
Gem::SourceIndex#add_spec called from /Library/Ruby/Site/1.8/rubygems/source_index.rb:127.
NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01.
Gem::SourceIndex#add_spec called from /Library/Ruby/Site/1.8/rubygems/source_index.rb:127.
NOTE: Gem::SourceIndex#initialize is deprecated with no replacement. It will be removed on or after 2011-11-01.
Gem::SourceIndex#initialize called from /Applications/Server.app/Contents/ServerRoot/usr/share/devicemgr/backend/config/../vendor/rails/railties/lib/rails/vendor_gem_source_index.rb:100.
NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01.
Gem::SourceIndex#add_spec called from /Library/Ruby/Site/1.8/rubygems/source_index.rb:91.
NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01.
Gem::SourceIndex#add_spec called from /Library/Ruby/Site/1.8/rubygems/source_index.rb:91.
NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01.
Gem::SourceIndex#add_spec called from /Library/Ruby/Site/1.8/rubygems/source_index.rb:91.
NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01.
Gem::SourceIndex#add_spec called from /Library/Ruby/Site/1.8/rubygems/source_index.rb:91.
NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01.
Gem::SourceIndex#add_spec called from /Library/Ruby/Site/1.8/rubygems/source_index.rb:91.
NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01.
Gem::SourceIndex#add_spec called from /Library/Ruby/Site/1.8/rubygems/source_index.rb:91.
NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01.
Gem::SourceIndex#add_spec called from /Library/Ruby/Site/1.8/rubygems/source_index.rb:91.
NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01.
Gem::SourceIndex#add_spec called from /Library/Ruby/Site/1.8/rubygems/source_index.rb:91.
NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01.
Gem::SourceIndex#add_spec called from /Library/Ruby/Site/1.8/rubygems/source_index.rb:91.
NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01.
Gem::SourceIndex#add_spec called from /Library/Ruby/Site/1.8/rubygems/source_index.rb:91.
NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01.
Gem::SourceIndex#add_spec called from /Library/Ruby/Site/1.8/rubygems/source_index.rb:91.
rake aborted!
no such file to load -- json/ext
(See full trace by running task with --trace)
devicemgr:state = "STARTING"
Any idea what is wrong?

Similar Messages

How to reset profile manager on mountain lion?

I never manager to get profile manager working on Lion Server.
I was expecting to do a clean install on my mac mini server, I couldn't.
Before reformating the partition any simpler tip?
May be I messed up the certificate as well.
When I try to enroll a compter (e.g. the mac mini server itself) via the web interface, I get the error message:
profile installation failed
could not download the identity profile from the encrypted profile service. The credentials within the device enrollment profile may have expired.
For resetting, I tried in Terminal
cd "Server HD"
sudo sh /usr/share/devicemgr/backend/wipeDB.sh
and I get :
No such file or directory
Thanks in advance

I'm having this same issue.
I can install the Trust Profile
but when I go to Enroll Device, I get:
profile installation failed
could not download the identity profile from the encrypted profile service. The credentials within the device enrollment profile may have expired.
what I've done:
backed up my Device Manager database
wiped the database
re-setup Device Manager
replaced the database
tried to Enroll Device and failed (same error)
wiped the database
re-setup the Device Manager
tried to Enroll Device and failed (same error)
I've tried recreating my ssl certs
Ive tried running it without code signing certs
I refuse to wipe my entire Open Directory
is there any to get this working or am I going to need to go third party to manage my Mac-only shop?

Is there a way to reset Profile manager to the default settings (i.e.) like it was never set up without reinstalling?

I recently set up profile manager wrong and need to reconfigure it. Any Ideas?

Brilliant! Thank you. To get this working in my case, I need to make a few tweaks to the commands:
sudo su - #Since I have a different ruby install avaliable to my local user and that breaks things.
cd /usr/share/devicemgr/backend
serveradmin stop devicemgr
serveradmin start postgres
RAILS_ENV="production" rake db:drop
RAILS_ENV="production" rake db:create
RAILS_ENV="production" rake db:migrate
serveradmin start devicemgr

Profile Manager does not recognize existing OD master

I built up a new Mountain Lion server at home, migrated all user data from an older server to it and today brought it into production in a colocation center. The nly thing I had to change in the colcocation environment was the IP address of the server. Everything else, even the hostname (DNS name), was already set in my home environment (I ran a DNS server at home for this). Profile Manager was already set up and therefore also Open Directory was running (without certificate). All users (except the admin) are stored in OD. At home I used the airport interface with a private address and in the colocation environment I use a public IP address on the ethernet interface.
After placing the server in the colocation centre verything went OK, but for Profile Manager. I was able to login as admin and as a user, but I was not able to install profiles on devices (https://server/mydevices). Therefore I did reset Profile Manager following http://support.apple.com/kb/HT5349. But now when I try to use the configure button in Profile Manager in Server.app to set up device management, it wants to create an OD master or replica. This is not what should happen according to the knowledge base article. It should use the existing OD master and just ask for the organization etc. I have a clone of the server as it was configured at home and tried the same procedure on this server, but then everything goes as expected from the knowledge base article. Does anyone have an idea how to fix this on my new colocated server?
I do not want to destroy OD, as I am not sure how to preserve all local network users.
Thanks for your help!

Open DTM and connect your BB via USB cable, then in desktop go to options and click on detect and look what it has there, if everything is ok go to main menu DTM and click on sync then on to config sync settings, make sure all is correct there, failing that in options you can check you setting in connections and PIN# are entered there.
When you accept a solution from anyone could you please select the appropriate box.
Also, select the appropriate Kudos box and click it for the person’s solution you accepted thank you.
Ian H

How to configure profile manager in Maverics when DNS is externally managed?

Are there any guides to configuring Profile Manager as a MDM?
Here is my story.
Recently installed Mac mini at a school where the DNS is externally managed by the Education departments IT group. Upgraded to Maverics and installed Server app. Configured profile manager to the point where we could generate a trust profile and enrolment profile. Doesn't work because there is no DNS entry for Mac mini server. Create entry but need to change host name and computer name and local machine name to match entry. Suddenly profile manager not working at all. Delete server app and it's configuration file in ~/Library/. Reinstall. Now Profile manager won't even activate. Speak to Apple on phone, run various commands to reinitialise Open Directory and reset profile manager. To no avail. Apple say to reinstall Mavericks, Server and try again.
Funny thing is I got profile manager to work as an MDM in a test environment, but changing DNS after doing so much configuration seems to have made a real mess of things. Vowing to make a time machine backup as soon as Mavericks re-installs.
Anyone know of any guides other than the one on krypted.com, which appears to be for the previous version of Profile Manager.
Stom

In general, either your OS X Server box has a DNS translation for its address, or it doesn't.
If you don't have valid DNS, you will have problems with various services, as DNS is fundamental to distributed authentication and encryption, among other uses.
OS X Server doesn't recover well from installations that start off with DNS errors, and the wipe and reinstallation suggested by Apple is usually easier than resolving the various issues that tend to arise within the configurations of the various services.
If your server doesn't have a valid DNS translation, then either add the DNS translation into your organization's local DNS environment, or work to retrain or replace the folks that are unwilling or unable to administer and to properly maintain local DNS services, or (far less desirably) configure and start your own parallel DNS services. There are other options, of course.
I'd escalate this discussion to management, and let them sort this out — at its core, this very likely isn't a technical issue.

Firefox crashes on start. Profile manager also crashes. Already reset.

Firefox crashes before it even fully starts. I tried to do the profile manager trick but profile manager crashes, too. I started in safe mode and did the reset Firefox thing, that didn't help.
I deleted the cache while in safe mode.
I even uninstalled and reinstalled, twice. I tried all the options in the safe mode dialog (disable addons, Reset Toolbars, etc).
Screenshots of the crashes:
http://lukes.pbworks.com/w/file/57925648/firefox%20crashes.png
http://lukes.pbworks.com/w/file/57925649/firefox%20profile%20manager%20crashes.png
about: support page:
Application Basics
Name
Firefox
Version
14.0.1
User Agent
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20100101 Firefox/14.0.1
Profile Folder
Show Folder
Enabled Plugins
about:plugins
Build Configuration
about:buildconfig
Crash Reports
about:crashes
Memory Use
about:memory
Extensions
Name
Version
Enabled
ID
Brief
1.7a1
false
[email protected]
FireGestures
1.6.16
false
[email protected]
Important Modified Preferences
Name
Value
browser.cache.disk.capacity
1048576
browser.cache.disk.smart_size.first_run
false
browser.cache.disk.smart_size_cached_value
1048576
browser.places.smartBookmarksVersion
4
browser.startup.homepage_override.buildID
20120713134347
browser.startup.homepage_override.mstone
14.0.1
extensions.lastAppVersion
14.0.1
network.cookie.prefsMigrated
true
places.history.expiration.transient_current_max_pages
104858
privacy.sanitize.migrateFx3Prefs
true
privacy.sanitize.timeSpan
0
security.warn_viewing_mixed
false
toolkit.startup.recent_crashes
3
Graphics
Adapter Description
NVIDIA GeForce GTX 560 Ti
Vendor ID
0x10de
Device ID
0x1200
Adapter RAM
1023
Adapter Drivers
nvd3dumx,nvwgf2umx,nvwgf2umx nvd3dum,nvwgf2um,nvwgf2um
Driver Version
8.17.13.142
Driver Date
5-15-2012
Direct2D Enabled
false
DirectWrite Enabled
false (6.1.7601.17789)
ClearType Parameters
Gamma: 2200 Pixel Structure: RGB ClearType Level: 100 Enhanced Contrast: 200
WebGL Renderer
Google Inc. -- ANGLE (NVIDIA GeForce GTX 560 Ti ) -- OpenGL ES 2.0 (ANGLE 1.0.0.1041)
GPU Accelerated Windows
0
JavaScript
Incremental GC
1
Library Versions
Expected minimum version
Version in use
NSPR
4.9
4.9
NSS
3.13.5.0 Basic ECC
3.13.5.0 Basic ECC
NSS Util
3.13.5.0
3.13.5.0
NSS SSL
3.13.5.0 Basic ECC
3.13.5.0 Basic ECC
NSS S/MIME
3.13.5.0 Basic ECC
3.13.5.0 Basic ECC

If you disable Hardware Acceleration, does Firefox start normally? [[Upgrade your graphics drivers to use hardware acceleration and WebGL#w_turning-off-hardware-acceleration|Turning off hardware acceleration]]?
Also, can you give some crash id's? type about:crashes into your address bar, and copy and paste the numbers there (they start with bp-)

Profile Manager to reset iPad passcode

Is it possible to use Mac OS X Lion Server Profile Manager to reset the passcode on managed iPads? I see the option to set complexity, but not an option to clea the existing passcode. Thanks.

If you go to /mydevices and log in as the profile you installed on your devices, you will see all the devices that profile is installed on. It is important that you log in as that profile and not an admin profile. You want to login as the profile name you installed on your devices.
Find the device you are looking for and click on "clear passcode"

Reset calendars and contacts and profile manager, reset calendars and contacts and profile manager

HI,
I have succesfully re setup postgres with this set of instructions...
Wki's now work, just need to re initialise calendars and contacts and maybe profile manager...
serveradmin stop postgres_server
serveradmin stop postgres
mv /Library/Server/PostgreSQL\ For\ Server\ Services/Data{,-old}
mv /Library/Server/PostgreSQL/Data{,-old}
/Applications/Server.app/Contents/ServerRoot/System/Library/ServerSetup/Promotio nExtras/58_postgres_setup.rb
/Applications/Server.app/Contents/ServerRoot/usr/share/devicemgr/backend/wipeDB. sh
serveradmin start wiki
/Applications/Server.app/Contents/ServerRoot/usr/bin/psql -U _postgres -h "/Library/Server/PostgreSQL For Server Services/Socket" -l
/Applications/Server.app/Contents/ServerRoot/usr/bin/psql -U _postgres -h "/Library/Server/PostgreSQL For Server Services/Socket" postgres -c "\dg"
bash-3.2# serveradmin stop postgres_server
postgres_server:state = "STOPPED"
bash-3.2# serveradmin stop postgres
postgres:state = "STOPPED"
bash-3.2# mv /Library/Server/PostgreSQL\ For\ Server\ Services/Data{,-old}
bash-3.2# mv /Library/Server/PostgreSQL/Data{,-old}
bash-3.2# /Applications/Server.app/Contents/ServerRoot/System/Library/ServerSetup/Promoti onExtras/58_postgres_setup.rb
WARNING: enabling "trust" authentication for local connections
You can change this by editing pg_hba.conf or using the option -A, or
--auth-local and --auth-host, the next time you run initdb.
WARNING: enabling "trust" authentication for local connections
You can change this by editing pg_hba.conf or using the option -A, or
--auth-local and --auth-host, the next time you run initdb.
bash-3.2# /Applications/Server.app/Contents/ServerRoot/usr/share/devicemgr/backend/wipeDB .sh
devicemgr:state = "STOPPED"
postgres_server:state = "RUNNING"
(in /Applications/Server.app/Contents/ServerRoot/usr/share/devicemgr/backend)
(in /Applications/Server.app/Contents/ServerRoot/usr/share/devicemgr/backend)
devicemgr:state = "STARTING"
bash-3.2# serveradmin start wiki
wiki:state = "RUNNING"
bash-3.2# /Applications/Server.app/Contents/ServerRoot/usr/bin/psql -U _postgres -h "/Library/Server/PostgreSQL For Server Services/Socket" -l
                                        List of databases
       Name        |   Owner    | Encoding |   Collate   |    Ctype    |    Access privileges
-------------------+------------+----------+-------------+-------------+-------- -----------------
caldav            | caldav     | UTF8     | en_GB.UTF-8 | en_GB.UTF-8 |
collab            | collab     | UTF8     | en_GB.UTF-8 | en_GB.UTF-8 |
device_management | _devicemgr | UTF8     | en_GB.UTF-8 | en_GB.UTF-8 |
postgres          | _postgres | UTF8     | en_GB.UTF-8 | en_GB.UTF-8 |
template0         | _postgres | UTF8     | en_GB.UTF-8 | en_GB.UTF-8 | =c/_postgres           +
                   |            |          |             |             | _postgres=CTc/_postgres
template1         | _postgres | UTF8     | en_GB.UTF-8 | en_GB.UTF-8 | =c/_postgres           +
                   |            |          |             |             | _postgres=CTc/_postgres
webauth           | webauth    | UTF8     | en_GB.UTF-8 | en_GB.UTF-8 |
(7 rows)
bash-3.2#

qwince wrote:
Yes but my point is that the device may not be able to connect to the internet for a period of time. Thus all devices will have different data on them.
So you are constantly (multiple times per hour/day) changing contacts/calendars on different devices with no internet around?
The data gets sync'd only when it changes.
So you are out in the field with no internet.
You make a change on your iPhone. It doens't get sync'd to your computer.
Who cares,? Yo have the data on your phone and you don't have your computer.
Now you drive back to town. When you get a data connection, everything sync's up.
why remove the functionality to sync everything else at the same time, should the user choose or need to do so.
The Sync Services functionality was removed from the OS, so there is nothing for iTunes to use.
It still works in Windows.

Profile Manager no longer works properly after update to FF 29.

I am a developer and I previously used the profile manager to manage 3 instances of Firefox. I had one open for Development, 1 for testing and 1 for production. Each was color coded by a theme for easy discernment of which instance I was in.
After the update to 29, the profile manager no longer seems to work properly. The theme from one profile proliferates to all the profiles and it is now very difficult to tell what instance I am in.

I found that after Firefox v29, a LOT of my settings and 
add-ons were changed / reset. Try this;
'''''[https://support.mozilla.org/en-US/kb/troubleshoot-firefox-issues-using-safe-mode Start Firefox in Safe Mode]'''''
 While you are in safe mode; 
'''''Firefox Options > Advanced > General'''''. 
Look for and turn off '''Use Hardware Acceleration'''. 
Then check ALL of your settings. Browser and add-ons. Then restart.

Firefox doesn't open with profile even after creating a profile through Profile Manager.

I created a profile of Firefox yesterday using Profile Manager. And placed it in a virtual encrypted drive created by TrueCrypt. But Firefox didn't open with the profile. Instead it opened in default setting that Firefox usually gets when newly installed. I tried to select the profile through Profile Manager and open Firefox but to no avail. Even tried placing the profile in the Profile folder in Firefox pathway in AppData. Still same thing. At last reset Firefox and the profile was deleted. Now I'm with newly default setting. Luckily I had saved my bookmarks from Bookmark Manager.
I just wanted to save a profile so that only I can only access my profile and any other person would just had to use default setting. Also to restore my settings in case I install a fresh Firefox or reset Firefox to solve a problem.
Please help me fulfill my wants as stated above and why did it not work yesterday with the Profile Manager?

Hello ams963, i think the problem is with TrueCrypt because it is not support your win 8 yet. see: http://www.truecrypt.org/
http://www.truecrypt.org/docs/version-history
see if can find a method in the next link, not too useful i think for your win 8 : [http://kb.mozillazine.org/Protect_the_profiles_contents Protecting the contents of the profile]
thank you

Remove VPP Token from Profile Manager

Hello,
I recently set up a test OSX Mavericks server and enrolled our VPP for testing purposes. To continue testing other options, I signed up for a Meraki account, and wanted to see how their VPP process compared with OSX Server. However, when I tried to enroll the VPP at Meraki I got an error...
"one or more errors occurred. No changes have been saved. VPP service token contains invalid characters."
I am trying to trouble shoot this, but not having much luck. At first I thought it might be an issue with our account name because we have Japanese in the business name. However, when I made some changes to teh OSX server during testing and re-entered the VPP it said that it was in use and that continuing would reset it. I said OK.
So no I wonder if the Meraki error is a resualt of teh VPP token already being registered with a different MDM.
Any body have experience with this error from Meraki or with how to remove the token from OSX Server.
Thanks for any help or insight you can offer.
Leon McCormick

http://krypted.com/mac-os-x/removing-apps-from-profile-manager-using-postgres/
this will leave "null" entries but clear the rest
Apple needs to fix. One of the reasons I stopped using Profile Manager and switched to Meraki.

Mozilla worked-now it won't start, nor will Profile Manager

1. Mozilla worked on Sunday but won't open on Monday - Error Message from Windows 7- "Firefox has Stopped Working".
2. Rebooted and then Deleted and Reloaded upgrade -Mozilla fails to open.
3. Reset Windows to earlier date ( one month ago) -Mozilla fails to Open.
4. Loaded complete version of Mozilla but failed to open.
4. Tried to Open Profile Manager using ; Windows key + R with the full 64 Bit Windows Address ( C: \Program Files (x86)\Mozilla Firefox\firefox.exe -p -failed to Open
5. Profile Manager opens and then immediately fails with Windows 7 message "Firefox has Stopped Working"
6. I use Vipre antivirus which has latest antivirus updates-did a full scan-no reported viruses other than cookies.
7. Checked firewall in settings of Vipre and added Firefox as a permitted program.
8. I am concerned that if I go into Safe mode I may inadvertently damage the operating Windows Program-I am not a computer technician and wish to do no harm to the system.
9. I have run out of ideas-Do you have a solution -PLEASE!

Once you click the 'Show Folder' button, a Windows Explorer window will open.
With Firefox closed, go up one folder and then you can simply '''copy/paste '''( don't drag ) the folder (should be named along the lines of *alphanumeric string*.default) to the desktop. And/or drag to another hard drive - '''it's good to have 2 copies, for safety'''.
No need to access Windows Restore.
'''Once the profile is safely duplicated''', then you can uninstall (and delete the user information (profile) and reinstall a fresh copy of Firefox. then follow the following to restore data from the saved profile - [https://support.mozilla.org/en-US/kb/recovering-important-data-from-an-old-profile recovering important data from an old profile].
You can copy extensions back, but the only irreplaceable items (imo) are bookmarks and passwords. But that's just my preference.
Of course, Firefox's problems ''could'' be a symptom of larger issues like, virus/malware or failing hard drives etc. Running a an AV and Malware scan couldn't hurt and checking Windows Event Viewer for system and application faults (take note of the times when you tried to open Firefox and check corresponding entries.

Active Directory Permissions to Profile Manager

Hopefully this will help anyone else who runs into this trouble.
OSX 10.9
Server App 3.0.1
We have a profile manager server setup using our Active Directory. After initial setup the system was working fine and all users could access the services.
In attempting to adjust the web service the permissions for service was turned on and domain users could no longer log in to enroll devices.
To resolve this issue I worked through the following steps.
In Server App > Groups found Domain Users (The group containing all users in the domain)
Clicked the Gear and choose Edit Access to Service
Checked off Profile Manager.
I then added Domain Users to the Local Workgroup and allowed the same access to services. This could be done with a different group if needed.
It may work at this point but as an additional step you can install the Workgroup manager tool from Apples Download site. http://support.apple.com/kb/DL1698
Log int to your Local Directory, I used /LDAPv3/127.0.0.1
Find the group you added the permissions to in the local domain and add your Active Directory Domain Users to that group.
Hope this saves someone else the annoyances I went through.

So after a little more trouble shooting as well I ended up using ths post after a backup of the database.
To backup the database I use this Post - https://discussions.apple.com/thread/3791994
pg_dump -U _devicemgr -h /Library/Server/ProfileManager/Config/var/PostgreSQL/ -c device_management > $HOME/device_management.sql
And resetting the server app and database.
https://discussions.apple.com/message/23925691?tstart=15#23925691?tstart=15
Interstingly this pulled my old database info back in and restored some settings that had been lost. I'm not really sure why and wouldn't trust it to happen again.
My issue is now that AD users have to log in twice. The first time they get a denyed error. Then they log out and login on the same browser or a differnt computer al together and they can get in.

PKCS12 certificate payloads in OS X Server 10.9 Profile Manager

Hi all,
I'm unable to successfully push .p12 packaged certificate identities to devices managed by OS X Server 10.9 Profile Manager. The problem is that while the file is pushed to the device, it doesn't get unpacked and hence is unable to be used.
I've identified the problem as Profile Manager setting the payload type incorrectly to "com.apple.security.pkcs1" in the profile rather than "com.apple.security.pkcs12". If I strip the profile signing data and edit it, the profile works perfectly when manually installed.
So the questions I have:
1) What's the best way of getting Apple's attention for someone to fix this bug, or is this possibly a browser JavaScript issue incorrectly identifying the payload type (using latest Safari though)?
2) Does anyone know of a workaround to allow this to still be automatically pushed out without having to manually edit and install on each device?
(SCEP is out at the moment due to another issue base64 decoding the SCEP request from Mac OS X devices that I'm taking up with the SCEP server vendor - but iOS works fine)
Thanks!
Al

I'm new to OS X Server and Radius, and have just spent way too many hours trying to figure out what I was doing wrong. I could connect to our enterprise wifi perfectly fine when selecting the certificate from the keychain, but I just couldn't get it to work when I uploaded the .p12 file and used it as the WiFi identity. I tried so many combinations of passphrase, no passphrase, pem format, pkcs12 format, resetting Radius server, resetting whole PKI... But I'd always see Certificate: ?Error_-25257? in the Settings window while I was trying to install the profile, and I couldn't see anything useful in the Radius logs when I tried to connect.
But it turns out, all I needed to do was:
sed -i '' -e '1s/pkcs1/pkcs12/;t' -e '1,/pkcs1/s//pkcs12/' wifi_profile.mobileconfig
(changes the first instance of pkcs1 to pkcs12 - don't change both! I was wondering why it was asking me for a password for our public certificate.)
Will try to update and see if that fixes the problem.

HT201334 Apple configurator vs Profile Manager

I downloaded apple configurator and have it working. Then I realized profile manager in OSX Server does the same thing. What is the difference, can I leave it as is? Any benefit of just using profile manager?

Apple configurator has its uses.
Apple configurator can be used as a "manual" standalone solution to manage you iDevices and AppleTVs.
Apple configurator can be used in blended approach with Profile Manager.
With Profile Manager you can manage iDevices , Macs , and I believe AppleTv over the AIR.
- Apple Configure Stand Alone.
When using Apple Configurator by itself you can , lock down an iPad in a way you see fit.
1. You can make an iDevice in "Supervise Mode" increasing restricting of your iDevice , Profile Manager cannot do this at the moment , this feature will be available in Mavericks.
2. Any future configuration changes to your iDevices , must be physically plugged in everytime for those changes.
3. You can distribute free and paid apps.
4. You can update your IOS updates all at once. When IOS 7 comes out this fall you probably dont want to touch every iDevice and update 1 at a time. You can use Apple Configurator to download the latest IOS , and any IDevice that you plugin will receive the update, this means downloading th IOS update one time on the mac, and pushing it out to whoever needs it. Profile Manager can't do this.
5. You can name several iDevices sequently. If you have a cart of 30 it will be easy to rename your iDevices. Profile Manager can't do this.
6. Apple configurator allows you to "backup and restore" its not a true complete image but its close. Profile Manager does not do backups or restores.
7. Apple Configurator can be used to erase an iDevice.
8. I'm probably missing some more features.
- Profile Manager Stand Alone
1. You can manage Macs not just iDevices.
2. You must enroll the device before you can manage it, this can be done by pushing out an email , via a website etc.
3. Everything happens over the Air.
4. When enrolling , users can use their Open Directory or Active Directory ( if your Apple server is bound to AD server ). You can also create a generic account for enrolling purposes.
5. You can wipe devices over the air.
6. You can make pass code resets for iDevices.
7. You can manage users in groups , even nested groups. I manage staff and student iDevices. Our wireless system is seperated for staff and students each wireless has its own SSID. I created 2 upper level Profile Manager Groups , one called WiFi Student and one called WiFi Staff, all my student iDevice groups are nested under WiFi Student group and all my staff idevice groups are nested. This makes managing my wifi a breeze. I also include my mifi wireless info , in case i need a backup emergency wireless.
8. Im sure theres other features.
- Apple Configurator And Profile Manager Blended
1. Push out initial wifi settings. I setup a simple wireless router to connect my devices ( there are types when I setup over 50 ipads , and our network runs out of IPs)
2. You can use Apple Configurator to push out Profile Managers "enrollment profile" to many iDevices. You dont want to enroll a full iDevice cart one at a time via a web browser.
Maverick and IOS 7
In the fall everything will change , it is amazing what we will be able to do. Over the Air Supervise Mode , Install Apps over the air with no user interaction, App codes become licenses , which are revokeable and reusable. Out of the box enrollment ... There may be no need for Apple Configurator come this fall. So many things are changing I recommend watching the new WWDC2013 Videos, specially the one on device management.
Back to original topic.
I value both products , they have their specilties and when you blended , you can get things done efficiently.

Resetting Profile Manager

Similar Messages

Maybe you are looking for