cragiboy

Q: Push in Profile Manager 3.1 doesn't work

I updated our server to version 3.1. First, the Profile Manager did not start. I deleted the server app and reinstalled. Then the Profile Manager started again. All devices and groups are still present, but I can not reach the existing devices. The Push depends! But new devices i can reach.

How can I solve the problem?

 

Mac mini, OS X Mountain Lion (10.8.3), Server

Posted on Mar 19, 2014 12:44 AM

Close

Q: Push in Profile Manager 3.1 doesn't work

  • All replies
  • Helpful answers

  • by mscott_mdm,

    mscott_mdm mscott_mdm Mar 19, 2014 9:49 AM in response to cragiboy
    Level 2 (225 points)
    Mar 19, 2014 9:49 AM in response to cragiboy

    cragiboy,

     

    Please try this to see if it restores proper Profile Manager functionality:

     

    sudo psql -U _devicemgr -d devicemgr_v2m0 -h /Library/Server/ProfileManager/Config/var/PostgreSQL -c "UPDATE devices SET last_update_info_time = dm_current_timestamp() + '1 month'"

     

    Copy the above and paste it into Terminal (or remote ssh shell) on the server as an admin user. You'll almost certainly be prompted to enter your admin password.

     

    Please let me know if this seems to fix the problem for you. (It might not be immediate, but it should show signs of working within a few minutes.)

  • by mscott_mdm,

    mscott_mdm mscott_mdm Mar 19, 2014 10:36 AM in response to mscott_mdm
    Level 2 (225 points)
    Mar 19, 2014 10:36 AM in response to mscott_mdm

    I would also recommend that you run this command, to keep newly-enrolled devices from causing the same problem after a couple of days:

     

    sudo psql -U _devicemgr -d devicemgr_v2m0 -h /Library/Server/ProfileManager/Config/var/PostgreSQL -c "ALTER TABLE devices ALTER COLUMN last_update_info_time SET DEFAULT dm_current_timestamp() + '1  month'"
  • by cragiboy,

    cragiboy cragiboy Mar 20, 2014 12:52 AM in response to mscott_mdm
    Level 1 (10 points)
    Servers Enterprise
    Mar 20, 2014 12:52 AM in response to mscott_mdm

    sorry mscott_mdm, but this did not solve the problem. it only works when i reenroll the devices. but i can not do this for 550 devices.

  • by mscott_mdm,

    mscott_mdm mscott_mdm Mar 20, 2014 7:39 AM in response to cragiboy
    Level 2 (225 points)
    Mar 20, 2014 7:39 AM in response to cragiboy

    cragiboy,

     

    Do you happen to have the output of the first command (the one with "UPDATE devices", not "ALTER TABLE devices")? If so, can you paste it hee? (It's OK to run that command again and paste that output if you don't have the original.)

     

    Thanks.

  • by mscott_mdm,

    mscott_mdm mscott_mdm Apr 21, 2015 12:50 PM in response to mscott_mdm
    Level 2 (225 points)
    Apr 21, 2015 12:50 PM in response to mscott_mdm

    Please note, if you applied the "ALTER TABLE" workaround I mentioned in this thread, you will need to apply the workaround I posted in Server 4.1 Profile Manager Migration Failed before you can successfully upgrade to Server 4.1. I would recommend doing this before you install Server 4.1 if you haven't already.

     

    sudo psql -U _devicemgr -d devicemgr_v2m0 -h /Library/Server/ProfileManager/Config/var/PostgreSQL -c "ALTER TABLE mdm_targets ALTER COLUMN last_update_info_time SET DEFAULT 'epoch'"