Databases
StackOverflow2013
Postsdbo
POios 7 MDM Server
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POios 7 MDM Server
    primarykey
    data
    text
    <p>We built our own MDM server using OSX Server and an apple mini to manage about 100 iPads. Everything worked great then ios 7 was released.</p> <p>We have various pads that have different things happening to them.. some are getting the app push but the app never installs, some never recive the push at all, and some pad's have our apps disappearing... </p> <p>Has anyone found what needs to be done to update the server so that it will function again? I've found 150+ page document on the apple developer site that walks you though setting up the entire process but most of it we have already, that document does not call out the changes so it's certianly not ideal at all to try to pick out what needs to be updated (I did also update the OSX Server software to the newest version)</p> <p>The only real errors I have to run on right now are from the device logs.. here is what is happening.</p> <pre><code>Oct 2 11:51:14 iPad mdmd[477] &lt;Notice&gt;: (Note ) MDM: Transaction completed. Status: 200 Oct 2 11:51:14 iPad mdmd[477] &lt;Notice&gt;: (Note ) MDM: Attempting to perform MDM request: InstallApplication Oct 2 11:51:14 iPad mdmd[477] &lt;Notice&gt;: (Note ) MDM: Handling request type: InstallApplication Oct 2 11:51:15 iPad mdmd[477] &lt;Notice&gt;: (Error) MDM: Enterprise app installation failed. Error: NSError: Desc : The app “com.app.Damages” is already scheduled for management. US Desc: The app “com.app.Damages” is already scheduled for management. Domain : MCMDMErrorDomain Code : 12026 Type : MCFatalError Params : ( "com.app.Damages" ) Oct 2 11:51:15 iPad mdmd[477] &lt;Notice&gt;: (Error) MDM: Command Status: Error Error: NSError: Desc : The app “com.app.Damages” is already scheduled for management. US Desc: The app “com.app.Damages” is already scheduled for management. Domain : MCMDMErrorDomain Code : 12026 Type : MCFatalError Params : ( "com.app.Damages" ) </code></pre> <p>Anyone know what needs to be changed? There can't be that much.. we are still pushing the apps just the device is not communicating with the server now</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USMichael
    1. USMonergy
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POios 7 MDM Server
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POios 7 MDM Server
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POios 7 MDM Server
      1. USlidsinker
      1. VTFavorite
    1. COIt seams this problem of 'already scheduled for management' is showing up on a number of the devices we are managing. When you connect to the device you get this same error. Somehow the app is stuck in the install process however is not appearing on the screen so we can't delete it or cancel it... but the mdm thinks that the app is allready on the device.. We've tried deleating the app from the device using the mdm and we've tried turning it off then on but does not clear the app.. how can we delete this app so that it will install?
      singulars
      1. POios 7 MDM Server
      1. USMonergy
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload