Device Enrollment Program

I signed up for the Device Enrollment Program and my status has shown in review for a couple of months. When will this be resolved?

We are all just fellow users here and so will have no idea when your application will pass review. All we can suggest is that you contact your Apple account executive and see if he or she can get any information for you.
Regards.

Similar Messages

  • Don't Want To Use Apple Config, Device Enroll Program

    I have been reading a lot on how to implement profiles onto devices like the iPhone, this functionality is what I am looking for, mainly with iPhone for some businesses and schools I work with. I have red that with the new technology you don't have to us Apple Configurator, and I have red about the Device Enroll Program... for my purposes I don't want to use any Apple method (nor would the situation I have even qualify for the Device Enroll Program) I really would like to deploy custom configuration profiles, with restrictions specified by my customers.
    I have been scanning the developer guides and and slowly grasping what I need to do...it sounds like I don't need to use Apple methods if I don't want CORRECT???  If I can implement custom profiles and in some cases it might just be three iPhones... I was hoping to find the proper guidance for implementing those custom profiles, thru the webpage method  or e-mail message is more suitable for my needs.
    I found the Apple play by play on how to do that, but sometimes for myself finding another perspective helps me learn... Any places anyone has found that can give that play by play on how to deliver those custom profiles  thru web page or e-mail?
    I have looked at the Over the Air Profile Delivery and Configuration Developer Pages... I'm just looking for that alternate information source to help me out. Appreciate all the help 

    Using Get Info to change all documents to open with Pages 4.3 doesn't work. The Mac OS will always default to the newest installed version & has for as long as I can remember. It will work on individual files, but that could be a lot of files to reset.
    This is what worked for me. After I installed the new iWork updates I created a folder on an external drive & named it "Applications." I then moved the new iWork apps to this folder & renamed the applications Keynote 6, Pages 5 & Numbers 3. I have icons for two versions of Pages & Numbers (I rarely use Keynote) in my Dock. Even with two versions of Pages & Numbers running, double-clicking an existing file opens in Pages 4.3 or Numbers 2.3. This should also keep the Mac App Store from nagging you to update.
    Since the last update I've used the solution Peter Breis posted (4th post in that thread) in iWork Tips 'n' Tricks with a little "tweak."
    Making Numbers '09 the default whilst keeping Pages 5
    1. Move any new iWork apps in another clearly labelled folder (I created a new folder in Applications & named it iWork 13)
    2. Menu > Apple > System Preferences > Spotlight > Privacy > drag the above folder into the list
    2) Move the new iWork folder into the trash (temporarily)
    3) Select any Numbers file in Finder > Menu > Info (cmd+i) > Open with: > Pages '09 > Change all
    4) Re the new iWork folder from the trash (right-click > Put back)
    Pages 5 should no longer appear as a default App, and you won't have to keep a copy in a separate drive or dmg.
    IMPORTANT: Make a note of where and how Pages was installed for the next App Store update and temporarily move it back there before putting it away again in the folder concealed from Spotlight.

  • Is there any alternate solution for MDM setup without following Device Enrollment Program (DEP) ?

    Hi,
    Is there any alternate solution  for setting up the MDM Process, without following the Device Enrollment Program (DEP) and managing the devices by creating our own setup controlling through the server, Please let me know.
    Thanks for the help.

    Finally I found the solution for the MDM, after doing some research work with the Apple Configurator, iPhone configuration utility and came across with the Profile Manager after installing Mac OS Server and able to manage, configure, remote access and send the commands using push notifications.

  • Apple Device Enrolment Program

    Some months ago i saw a question about the device enrolment program.I was just wandering  if it is now available as some months have passed and i am hearing rumours.
    If so,has anyone in medium/large co-operations in the UK used this service to deploy ipads?
    Your responses will be very much appreciated?
    Cheers

    Hello kwadster,
    At this time the Device Enrollment Program is only available in the U.S.
    Only devices purchased directly from Apple in the U.S. using your enrolled and verified Apple Customer Numbers are eligible for use and assignment in the Device Enrollment Program, provided they have not been previously disowned. Device eligibility is also limited to orders placed within three years of your organization’s enrollment into the program.
    Apple - iPhone in Business
    https://www.apple.com/iphone/business/it/management.html
    Cheers,
    Allen

  • Ios7 Device enrollment program mdm api's

    Hi,
    The mdm api's (for device enrollment program) like disown Devices, define profile etc..Return responses with a dictionary of devices along with a string value like SUCCESS, NOT_ACCESSIBLE, FAILED ...What would be the reason for NOT_ACCESSIBLE and FAILED...caused based on the true reason our server would need to react differently...can we assume that NOT_ACCESSIBLE and failed means apple no longer has any information about the device in the device enrollment program?...
    Appreciate a response,
    Thanks,
    -Vikram.

    I am also getting NOT_ACCESSIBLE when trying to upload a serial number for an iPad. I was able to get 280 serial numbers uploaded successfully, but I am not able to get one particular serial number into DEP.
    Any thoughts or suggestions?
    Help here would be appreciated also..

  • UDM and Apple Device Enrollment Program

    Does anyone know if the Apple Device Enrollment Program works when integrating Microsoft Intune with SCCM 2012?  Seems all the articles I find only reference standalone Intune.
    Thanks!

    No, not yet William. This feature was only introduced in standalone Intune in March. Currently features typically follow in hybrid 90 days later (we're told that this gap should be shortened soon). Although it is possible that this one may not make
    it to ConfigMgr (I don't know the roadmap).
    Have a look at the official Microsoft Intune blog describing March's new features.
    http://blogs.technet.com/b/microsoftintune/archive/2015/03/04/march-updates-coming-this-week-to-microsoft-intune.aspx?linkId=12671375
    By the way the same applies to the Apple Configurator. There is currently no way to create Intune Device Enrolment Profiles in the hybrid solution.
    Gerry Hampson | Blog:
    www.gerryhampsoncm.blogspot.ie | LinkedIn:
    Gerry Hampson | Twitter:
    @gerryhampson

  • Regarding the November updates to the Device Enrollment Program: Am I now able to use the DEP with a much smaller deployment?

    The last time I was hip to the info, for my devices to be eligible for the Device Enrollment Program, their serial numbers had to be associated with an Apple Customer ID number. In order to have an Apple Customer ID number, you had to be on Apple Terms, which basically means a very large spend now and in the future. De Facto, in order to use DEP you effectively had to have a large number of devices.
    With the addition of 3rd party resellers and other changes made in November, is it now possible to use the DEP as a much smaller company. I'd have 13 devices to start, and those already exist so I understand they may not qualify. However, we will grow to between 40 - 60 iOS devices within the next few years. I have relationships with JAMF and the Casper Suite, so I'd be moving in that direction. Does Apple give away customer numbers more freely now, or do 3rd party resellers provide the proper credentials (per the new DEP manual) at lower purchase levels? In a nutshell, can I buy 20 devices with a company credit card and get DEP going?
    I know the other options, and I have other solutions in line, I just want to know as part of my 'sussing out' process. I know from experience the front line at Apple isn't really privy to this info, so any help is appreciated!
    Alan

    The last time I was hip to the info, for my devices to be eligible for the Device Enrollment Program, their serial numbers had to be associated with an Apple Customer ID number. In order to have an Apple Customer ID number, you had to be on Apple Terms, which basically means a very large spend now and in the future. De Facto, in order to use DEP you effectively had to have a large number of devices.
    With the addition of 3rd party resellers and other changes made in November, is it now possible to use the DEP as a much smaller company. I'd have 13 devices to start, and those already exist so I understand they may not qualify. However, we will grow to between 40 - 60 iOS devices within the next few years. I have relationships with JAMF and the Casper Suite, so I'd be moving in that direction. Does Apple give away customer numbers more freely now, or do 3rd party resellers provide the proper credentials (per the new DEP manual) at lower purchase levels? In a nutshell, can I buy 20 devices with a company credit card and get DEP going?
    I know the other options, and I have other solutions in line, I just want to know as part of my 'sussing out' process. I know from experience the front line at Apple isn't really privy to this info, so any help is appreciated!
    Alan

  • Apple Device Enrollment Program to Apple Server 3.1.2

    Our school system has enrolled in the Apple Device Enrollment Program.  We've setup a Apple Server running 3.1.2 and have Profile Manager up and running.  I have opened ports 80, 443 and 1640, registered the Push Notification Certificate, etc. 
    Whenever I assign a device on deploy.apple.com, the device appears within Profile Manager on the Apple Server, however it always shows up as a placeholder and not a functioning device. 
    Anyone have any idea what might be going on here?
    Thank you!

    Today I called Apple Support.  I had misunderstood the process.  In order for a device to enroll, the device itself must go through the enrollment process when the machine is initially unboxed and connects to the network.  If it's a brand new Mac fresh out of the box or reloaded, then having it as a placeholder in Profile Manager is generally good enough. 
    It seems that existing Macs on the network still need to be setup via the My Devices portal which requires the end-user either enroll their devices (which for me is no guarantee) or I go help them enroll.
    The other thing I didn't have setup was an Enrollment Profile which is created by clicking the icon at the bottom left corner of Profile Manager.

  • Device Enrollment Program and AD Users

    In a small to medium sized school district, I have a Mac Mini running OS X 10.10.2 with Server 4.0.3. The server is bound to multiple AD servers as we have multiple domains (Each building currently has its own domain, but we are in the process of switching to a single domain for the entire district). I have Profile Manager configured and connected to the DEP. I set the Enrollment settings as follows:
    Prompt User to Enroll Devices
    Prevent enenrollment
    Supervise
         Allow Pairing
    Require credentials for enrollment
    The problem comes in when I select the Require credentials for enrollment option. My AD users cannot login on their iPads to finish the activation of the device. If I try to log in using a local user account from the server machine, the activation completes successfully. I know that the server is communicating with the AD servers, AD users can successfully log into the MyDevices page as well as my AD admins can log into the Profile Manager website.
    Any help would be greatly appreciated.
    I know it is a lot of information, but here are the logs from the server:
    Unsuccessful Login using AD user
    1::Feb 06 15:04:57.634 [221] <10.2.45.144> {LogElapsedTime (common.php:82)} Time since script start: 111us [https://myserver.mydomain.lan/devicemanagement/api/device/dep_mdm_enroll]
    1::Feb 06 15:04:57.634 [221] <10.2.45.144> {require_once (dep_mdm_enroll.php:11)} vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv - POST dep_mdm_enroll
    0::Feb 06 15:04:57.641 [221] <10.2.45.144> {LogException (common.php:470)} EXCEPTION: 401 Unauthorized - Requesting user digest authentication at
    0::Feb 06 15:04:57.641 [221] <10.2.45.144> #0 /Applications/Server.app/Contents/ServerRoot/usr/share/devicemgr/backend/php/de p_mdm_enroll.php(172): DieUnauthorized('Requesting user...')
    0::Feb 06 15:04:57.641 [221] <10.2.45.144> #1 /Applications/Server.app/Contents/ServerRoot/usr/share/devicemgr/backend/php/de p_mdm_enroll.php(199): _request_authorization('24f8cec00e51de4...')
    0::Feb 06 15:04:57.641 [221] <10.2.45.144> #2 {main}
    1::Feb 06 15:04:57.668 [221] <10.2.45.144> {SendFinalOutput (common.php:477)} Sent Final Output (58 bytes)
    1::Feb 06 15:04:57.668 [221] <10.2.45.144> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - /devicemanagement/api/device/dep_mdm_enroll
    0::Feb 06 15:04:57.668 [221] <10.2.45.144> {SendFinalOutput (common.php:477)} Completed in 34ms | 401 Unauthorized  [https://myserver.mydomain.lan/devicemanagement/api/device/dep_mdm_enroll]
    1::Feb 06 15:04:57.696 [222] <10.2.45.144> {LogElapsedTime (common.php:82)} Time since script start: 134us [https://myserver.mydomain.lan/devicemanagement/api/device/dep_mdm_enroll]
    1::Feb 06 15:04:57.696 [222] <10.2.45.144> {require_once (dep_mdm_enroll.php:11)} vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv - POST dep_mdm_enroll
    0::Feb 06 15:04:58.195 [222] <10.2.45.144> /Applications/Server.app/Contents/ServerRoot/usr/share/devicemgr/backend/php/de p_mdm_enroll.php: Authorization failed
    0::Feb 06 15:04:58.196 [222] <10.2.45.144> {LogException (common.php:470)} EXCEPTION: 401 Unauthorized - Requesting user digest authentication at
    0::Feb 06 15:04:58.196 [222] <10.2.45.144> #0 /Applications/Server.app/Contents/ServerRoot/usr/share/devicemgr/backend/php/de p_mdm_enroll.php(172): DieUnauthorized('Requesting user...')
    0::Feb 06 15:04:58.196 [222] <10.2.45.144> #1 /Applications/Server.app/Contents/ServerRoot/usr/share/devicemgr/backend/php/de p_mdm_enroll.php(199): _request_authorization('24f8cec00e51de4...')
    0::Feb 06 15:04:58.196 [222] <10.2.45.144> #2 {main}
    1::Feb 06 15:04:58.197 [222] <10.2.45.144> {SendFinalOutput (common.php:477)} Sent Final Output (58 bytes)
    1::Feb 06 15:04:58.197 [222] <10.2.45.144> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - /devicemanagement/api/device/dep_mdm_enroll
    0::Feb 06 15:04:58.197 [222] <10.2.45.144> {SendFinalOutput (common.php:477)} Completed in 500ms | 401 Unauthorized  [https://myserver.mydomain.lan/devicemanagement/api/device/dep_mdm_enroll]
    1::Feb 06 15:04:58.212 [221] <10.2.45.144> {LogElapsedTime (common.php:82)} Time since script start: 113us [https://myserver.mydomain.lan/devicemanagement/api/device/dep_mdm_enroll]
    1::Feb 06 15:04:58.212 [221] <10.2.45.144> {require_once (dep_mdm_enroll.php:11)} vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv - POST dep_mdm_enroll
    0::Feb 06 15:04:58.219 [221] <10.2.45.144> {LogException (common.php:470)} EXCEPTION: 401 Unauthorized - Requesting user digest authentication at
    0::Feb 06 15:04:58.219 [221] <10.2.45.144> #0 /Applications/Server.app/Contents/ServerRoot/usr/share/devicemgr/backend/php/de p_mdm_enroll.php(172): DieUnauthorized('Requesting user...')
    0::Feb 06 15:04:58.219 [221] <10.2.45.144> #1 /Applications/Server.app/Contents/ServerRoot/usr/share/devicemgr/backend/php/de p_mdm_enroll.php(199): _request_authorization('24f8cec00e51de4...')
    0::Feb 06 15:04:58.219 [221] <10.2.45.144> #2 {main}
    1::Feb 06 15:04:58.219 [221] <10.2.45.144> {SendFinalOutput (common.php:477)} Sent Final Output (58 bytes)
    1::Feb 06 15:04:58.219 [221] <10.2.45.144> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - /devicemanagement/api/device/dep_mdm_enroll
    0::Feb 06 15:04:58.219 [221] <10.2.45.144> {SendFinalOutput (common.php:477)} Completed in 6ms | 401 Unauthorized  [https://myserver.mydomain.lan/devicemanagement/api/device/dep_mdm_enroll
    Successful Login Using Local user
    1::Feb 06 15:13:50.172 [2109] <10.2.45.144> {LogElapsedTime (common.php:82)} Time since script start: 130us [https://myserver.mydomain.lan/devicemanagement/api/device/dep_mdm_enroll]
    1::Feb 06 15:13:50.172 [2109] <10.2.45.144> {require_once (dep_mdm_enroll.php:11)} vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv - POST dep_mdm_enroll
    0::Feb 06 15:13:50.180 [2109] <10.2.45.144> {LogException (common.php:470)} EXCEPTION: 401 Unauthorized - Requesting user digest authentication at
    0::Feb 06 15:13:50.180 [2109] <10.2.45.144> #0 /Applications/Server.app/Contents/ServerRoot/usr/share/devicemgr/backend/php/de p_mdm_enroll.php(172): DieUnauthorized('Requesting user...')
    0::Feb 06 15:13:50.180 [2109] <10.2.45.144> #1 /Applications/Server.app/Contents/ServerRoot/usr/share/devicemgr/backend/php/de p_mdm_enroll.php(199): _request_authorization('24f8cec00e51de4...')
    0::Feb 06 15:13:50.180 [2109] <10.2.45.144> #2 {main}
    1::Feb 06 15:13:50.180 [2109] <10.2.45.144> {SendFinalOutput (common.php:477)} Sent Final Output (58 bytes)
    1::Feb 06 15:13:50.180 [2109] <10.2.45.144> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - /devicemanagement/api/device/dep_mdm_enroll
    0::Feb 06 15:13:50.180 [2109] <10.2.45.144> {SendFinalOutput (common.php:477)} Completed in 8ms | 401 Unauthorized  [https://myserver.mydomain.lan/devicemanagement/api/device/dep_mdm_enroll]
    1::Feb 06 15:13:50.223 [222] <10.2.45.144> {LogElapsedTime (common.php:82)} Time since script start: 144us [https://myserver.mydomain.lan/devicemanagement/api/device/dep_mdm_enroll]
    1::Feb 06 15:13:50.223 [222] <10.2.45.144> {require_once (dep_mdm_enroll.php:11)} vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv - POST dep_mdm_enroll
    0::Feb 06 15:13:50.273 [222] <10.2.45.144> {_dep_mdm_enroll_2 (db.php:396)} priv_result=[ {
    0::Feb 06 15:13:50.273 [222] <10.2.45.144>     'dm_expanded_privileges_for_user_id'=>'{"enroll_dep":true,"enroll_portal":true, "require_ownership":false,"require_placeholder":false,"wipe_device":true,"lock_d evice":true,"clear_passcode":true,"download_profiles":true,"access_portal":true, "enroll_configurator":false}'
    0::Feb 06 15:13:50.273 [222] <10.2.45.144>   } ]
    1::Feb 06 15:13:51.460 [222] <10.2.45.144> {SendFinalOutput (dep_mdm_enroll.php:209)} Sent Final Output (11979 bytes)
    1::Feb 06 15:13:51.460 [222] <10.2.45.144> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - /devicemanagement/api/device/dep_mdm_enroll
    0::Feb 06 15:13:51.460 [222] <10.2.45.144> {SendFinalOutput (dep_mdm_enroll.php:209)} Completed in 1237ms | 200 OK [https://myserver.mydomain.lan/devicemanagement/api/device/dep_mdm_enroll]
    1::Feb 06 15:13:54.966 [221] <10.2.45.144> {LogElapsedTime (common.php:82)} Time since script start: 312us [https://myserver.mydomain.lan/devicemanagement/api/device/mdm_checkin]
    1::Feb 06 15:13:54.966 [221] <10.2.45.144> {require_once (mdm_checkin.php:11)} vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv - PUT mdm_checkin
    0::Feb 06 15:13:55.014 [221] <10.2.45.144> checkin: 'Authenticate'
    1::Feb 06 15:13:55.070 [221] <10.2.45.144> {SendFinalOutput (mdm_checkin.php:148)} Sent Final Output (0 bytes)
    1::Feb 06 15:13:55.070 [221] <10.2.45.144> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - /devicemanagement/api/device/mdm_checkin
    0::Feb 06 15:13:55.070 [221] <10.2.45.144> {SendFinalOutput (mdm_checkin.php:148)} Completed in 104ms | 200 OK [https://myserver.mydomain.lan/devicemanagement/api/device/mdm_checkin]
    1::Feb 06 15:13:57.343 [2109] <10.2.45.144> {LogElapsedTime (common.php:82)} Time since script start: 312us [https://myserver.mydomain.lan/devicemanagement/api/device/mdm_checkin]
    1::Feb 06 15:13:57.344 [2109] <10.2.45.144> {require_once (mdm_checkin.php:11)} vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv - PUT mdm_checkin
    0::Feb 06 15:13:57.347 [2109] <10.2.45.144> checkin: 'TokenUpdate'
    1::Feb 06 15:13:57.351 [2109] <10.2.45.144> {Target_for_incoming_request (target.php:320)} Found target iOS: <'Unknown-Host'[488](OWNER:User[5])>
    1::Feb 06 15:13:57.477 [2109] <10.2.45.144> {SendFinalOutput (mdm_checkin.php:148)} Sent Final Output (0 bytes)
    1::Feb 06 15:13:57.477 [2109] <10.2.45.144> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - /devicemanagement/api/device/mdm_checkin
    0::Feb 06 15:13:57.477 [2109] <10.2.45.144> {SendFinalOutput (mdm_checkin.php:148)} Completed in 133ms | 200 OK [https://myserver.mydomain.lan/devicemanagement/api/device/mdm_checkin]
    1::Feb 06 15:13:58.774 [222] <10.2.45.144> {LogElapsedTime (common.php:82)} Time since script start: 131us [https://myserver.mydomain.lan/devicemanagement/api/device/mdm_checkin]
    1::Feb 06 15:13:58.774 [222] <10.2.45.144> {require_once (mdm_checkin.php:11)} vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv - PUT mdm_checkin
    0::Feb 06 15:13:58.776 [222] <10.2.45.144> checkin: 'TokenUpdate'
    1::Feb 06 15:13:58.780 [222] <10.2.45.144> {Target_for_incoming_request (target.php:320)} Found target iOS: <'Unknown-Host'[488](OWNER:User[5])>
    1::Feb 06 15:13:58.827 [222] <10.2.45.144> {SendFinalOutput (mdm_checkin.php:148)} Sent Final Output (0 bytes)
    1::Feb 06 15:13:58.827 [222] <10.2.45.144> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - /devicemanagement/api/device/mdm_checkin
    0::Feb 06 15:13:58.827 [222] <10.2.45.144> {SendFinalOutput (mdm_checkin.php:148)} Completed in 53ms | 200 OK [https://myserver.mydomain.lan/devicemanagement/api/device/mdm_checkin]
    1::Feb 06 15:14:00.017 [221] <10.2.45.144> {LogElapsedTime (common.php:82)} Time since script start: 264us [https://myserver.mydomain.lan/devicemanagement/api/device/mdm_connect]
    1::Feb 06 15:14:00.018 [221] <10.2.45.144> {require_once (mdm_connect.php:11)} vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv - PUT mdm_connect
    1::Feb 06 15:14:00.023 [221] <10.2.45.144> {Target_for_incoming_request (mdm_connect.php:20)} Found target iOS: <'Unknown-Host'[488](OWNER:User[5])>
    0::Feb 06 15:14:00.023 [221] <10.2.45.144> {_connect_transaction_1 (db.php:396)} Status='Idle'
    0::Feb 06 15:14:00.047 [221] <10.2.45.144> {Task_generate_next_request (mdm_connect.php:108)} Sending request 'DeviceInformation' as CommandUUID=C39A49E2-17DB-40A5-B6E5-94548E163407
    1::Feb 06 15:14:00.084 [221] <10.2.45.144> {SendFinalOutput (mdm_connect.php:133)} Sent Final Output (1984 bytes)
    1::Feb 06 15:14:00.084 [221] <10.2.45.144> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - /devicemanagement/api/device/mdm_connect
    0::Feb 06 15:14:00.084 [221] <10.2.45.144> {SendFinalOutput (mdm_connect.php:133)} Completed in 67ms | 200 OK [https://myserver.mydomain.lan/devicemanagement/api/device/mdm_connect]
    1::Feb 06 15:14:00.846 [2109] <10.2.45.144> {LogElapsedTime (common.php:82)} Time since script start: 127us [https://myserver.mydomain.lan/devicemanagement/api/device/mdm_connect]
    1::Feb 06 15:14:00.846 [2109] <10.2.45.144> {require_once (mdm_connect.php:11)} vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv - PUT mdm_connect
    1::Feb 06 15:14:00.852 [2109] <10.2.45.144> {Target_for_incoming_request (mdm_connect.php:20)} Found target iOS: <'Unknown-Host'[488](OWNER:User[5])>
    0::Feb 06 15:14:00.852 [2109] <10.2.45.144> {_connect_transaction_1 (db.php:396)} Status='Acknowledged' CommandUUID=C39A49E2-17DB-40A5-B6E5-94548E163407
    0::Feb 06 15:14:00.919 [2109] <10.2.45.144> {Task_generate_next_request (mdm_connect.php:108)} Sending request 'Restrictions' as CommandUUID=E5269CE6-C19D-47FB-8B78-DD6400F81A1F
    1::Feb 06 15:14:00.956 [2109] <10.2.45.144> {SendFinalOutput (mdm_connect.php:133)} Sent Final Output (431 bytes)
    1::Feb 06 15:14:00.956 [2109] <10.2.45.144> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - /devicemanagement/api/device/mdm_connect
    0::Feb 06 15:14:00.956 [2109] <10.2.45.144> {SendFinalOutput (mdm_connect.php:133)} Completed in 109ms | 200 OK [https://myserver.mydomain.lan/devicemanagement/api/device/mdm_connect]
    1::Feb 06 15:14:01.051 [222] <10.2.45.144> {LogElapsedTime (common.php:82)} Time since script start: 150us [https://myserver.mydomain.lan/devicemanagement/api/device/mdm_connect]
    1::Feb 06 15:14:01.051 [222] <10.2.45.144> {require_once (mdm_connect.php:11)} vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv - PUT mdm_connect
    1::Feb 06 15:14:01.057 [222] <10.2.45.144> {Target_for_incoming_request (mdm_connect.php:20)} Found target iOS: <'iPad'[488](OWNER:User[5])>
    0::Feb 06 15:14:01.057 [222] <10.2.45.144> {_connect_transaction_1 (db.php:396)} Status='Acknowledged' CommandUUID=E5269CE6-C19D-47FB-8B78-DD6400F81A1F
    0::Feb 06 15:14:01.093 [222] <10.2.45.144> {Task_generate_next_request (mdm_connect.php:108)} Sending request 'CertificateList' as CommandUUID=3540C8F6-0BF4-43F6-B023-3F95D3182B51
    1::Feb 06 15:14:01.096 [222] <10.2.45.144> {SendFinalOutput (mdm_connect.php:133)} Sent Final Output (389 bytes)
    1::Feb 06 15:14:01.096 [222] <10.2.45.144> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - /devicemanagement/api/device/mdm_connect
    0::Feb 06 15:14:01.096 [222] <10.2.45.144> {SendFinalOutput (mdm_connect.php:133)} Completed in 45ms | 200 OK [https://myserver.mydomain.lan/devicemanagement/api/device/mdm_connect]
    1::Feb 06 15:14:01.137 [221] <10.2.45.144> {LogElapsedTime (common.php:82)} Time since script start: 118us [https://myserver.mydomain.lan/devicemanagement/api/device/mdm_connect]
    1::Feb 06 15:14:01.137 [221] <10.2.45.144> {require_once (mdm_connect.php:11)} vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv - PUT mdm_connect
    1::Feb 06 15:14:01.156 [221] <10.2.45.144> {Target_for_incoming_request (mdm_connect.php:20)} Found target iOS: <'iPad'[488](OWNER:User[5])>
    0::Feb 06 15:14:01.157 [221] <10.2.45.144> {_connect_transaction_1 (db.php:396)} Status='Acknowledged' CommandUUID=3540C8F6-0BF4-43F6-B023-3F95D3182B51
    0::Feb 06 15:14:01.175 [221] <10.2.45.144> {Task_generate_next_request (mdm_connect.php:108)} Sending request 'ProvisioningProfileList' as CommandUUID=AF5B54A8-3AD7-46EB-9933-A5EC721FA7D5
    1::Feb 06 15:14:01.180 [221] <10.2.45.144> {SendFinalOutput (mdm_connect.php:133)} Sent Final Output (397 bytes)
    1::Feb 06 15:14:01.180 [221] <10.2.45.144> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - /devicemanagement/api/device/mdm_connect
    0::Feb 06 15:14:01.181 [221] <10.2.45.144> {SendFinalOutput (mdm_connect.php:133)} Completed in 43ms | 200 OK [https://myserver.mydomain.lan/devicemanagement/api/device/mdm_connect]
    1::Feb 06 15:14:01.207 [2109] <10.2.45.144> {LogElapsedTime (common.php:82)} Time since script start: 122us [https://myserver.mydomain.lan/devicemanagement/api/device/mdm_connect]
    1::Feb 06 15:14:01.207 [2109] <10.2.45.144> {require_once (mdm_connect.php:11)} vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv - PUT mdm_connect
    1::Feb 06 15:14:01.215 [2109] <10.2.45.144> {Target_for_incoming_request (mdm_connect.php:20)} Found target iOS: <'iPad'[488](OWNER:User[5])>
    0::Feb 06 15:14:01.215 [2109] <10.2.45.144> {_connect_transaction_1 (db.php:396)} Status='Acknowledged' CommandUUID=AF5B54A8-3AD7-46EB-9933-A5EC721FA7D5
    0::Feb 06 15:14:01.232 [2109] <10.2.45.144> {Task_generate_next_request (mdm_connect.php:108)} Sending request 'ProfileList' as CommandUUID=2A50F792-6486-4767-828F-B71545709CE1
    1::Feb 06 15:14:01.235 [2109] <10.2.45.144> {SendFinalOutput (mdm_connect.php:133)} Sent Final Output (385 bytes)
    1::Feb 06 15:14:01.235 [2109] <10.2.45.144> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - /devicemanagement/api/device/mdm_connect
    0::Feb 06 15:14:01.235 [2109] <10.2.45.144> {SendFinalOutput (mdm_connect.php:133)} Completed in 28ms | 200 OK [https://myserver.mydomain.lan/devicemanagement/api/device/mdm_connect]
    1::Feb 06 15:14:01.299 [222] <10.2.45.144> {LogElapsedTime (common.php:82)} Time since script start: 118us [https://myserver.mydomain.lan/devicemanagement/api/device/mdm_connect]
    1::Feb 06 15:14:01.300 [222] <10.2.45.144> {require_once (mdm_connect.php:11)} vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv - PUT mdm_connect
    1::Feb 06 15:14:01.309 [222] <10.2.45.144> {Target_for_incoming_request (mdm_connect.php:20)} Found target iOS: <'iPad'[488](OWNER:User[5])>
    0::Feb 06 15:14:01.309 [222] <10.2.45.144> {_connect_transaction_1 (db.php:396)} Status='Acknowledged' CommandUUID=2A50F792-6486-4767-828F-B71545709CE1
    0::Feb 06 15:14:01.372 [222] <10.2.45.144> {Task_generate_next_request (mdm_connect.php:108)} Sending request 'InstalledApplicationList' as CommandUUID=D9664A42-7E34-44C7-AA8C-9A2601579F68
    1::Feb 06 15:14:01.376 [222] <10.2.45.144> {SendFinalOutput (mdm_connect.php:133)} Sent Final Output (398 bytes)
    1::Feb 06 15:14:01.376 [222] <10.2.45.144> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - /devicemanagement/api/device/mdm_connect
    0::Feb 06 15:14:01.376 [222] <10.2.45.144> {SendFinalOutput (mdm_connect.php:133)} Completed in 76ms | 200 OK [https://myserver.mydomain.lan/devicemanagement/api/device/mdm_connect]
    1::Feb 06 15:14:01.407 [221] <10.2.45.144> {LogElapsedTime (common.php:82)} Time since script start: 267us [https://myserver.mydomain.lan/devicemanagement/api/device/mdm_connect]
    1::Feb 06 15:14:01.407 [221] <10.2.45.144> {require_once (mdm_connect.php:11)} vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv - PUT mdm_connect
    1::Feb 06 15:14:01.413 [221] <10.2.45.144> {Target_for_incoming_request (mdm_connect.php:20)} Found target iOS: <'iPad'[488](OWNER:User[5])>
    0::Feb 06 15:14:01.414 [221] <10.2.45.144> {_connect_transaction_1 (db.php:396)} Status='Acknowledged' CommandUUID=D9664A42-7E34-44C7-AA8C-9A2601579F68
    0::Feb 06 15:14:01.430 [221] <10.2.45.144> {Task_generate_next_request (mdm_connect.php:108)} Sending request 'ManagedApplicationList' as CommandUUID=46058966-4E97-4B2F-872C-FC80D534009A
    1::Feb 06 15:14:01.433 [221] <10.2.45.144> {SendFinalOutput (mdm_connect.php:133)} Sent Final Output (396 bytes)
    1::Feb 06 15:14:01.433 [221] <10.2.45.144> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - /devicemanagement/api/device/mdm_connect
    0::Feb 06 15:14:01.433 [221] <10.2.45.144> {SendFinalOutput (mdm_connect.php:133)} Completed in 26ms | 200 OK [https://myserver.mydomain.lan/devicemanagement/api/device/mdm_connect]
    1::Feb 06 15:14:01.458 [2109] <10.2.45.144> {LogElapsedTime (common.php:82)} Time since script start: 121us [https://myserver.mydomain.lan/devicemanagement/api/device/mdm_connect]
    1::Feb 06 15:14:01.459 [2109] <10.2.45.144> {require_once (mdm_connect.php:11)} vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv - PUT mdm_connect
    1::Feb 06 15:14:01.465 [2109] <10.2.45.144> {Target_for_incoming_request (mdm_connect.php:20)} Found target iOS: <'iPad'[488](OWNER:User[5])>
    0::Feb 06 15:14:01.465 [2109] <10.2.45.144> {_connect_transaction_1 (db.php:396)} Status='Acknowledged' CommandUUID=46058966-4E97-4B2F-872C-FC80D534009A
    0::Feb 06 15:14:01.482 [2109] <10.2.45.144> {Task_generate_next_request (mdm_connect.php:108)} Sending request 'ManagedMediaList' as CommandUUID=683038A2-539D-4393-AF61-6EB632869029
    1::Feb 06 15:14:01.485 [2109] <10.2.45.144> {SendFinalOutput (mdm_connect.php:133)} Sent Final Output (390 bytes)
    1::Feb 06 15:14:01.485 [2109] <10.2.45.144> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - /devicemanagement/api/device/mdm_connect
    0::Feb 06 15:14:01.485 [2109] <10.2.45.144> {SendFinalOutput (mdm_connect.php:133)} Completed in 26ms | 200 OK [https://myserver.mydomain.lan/devicemanagement/api/device/mdm_connect]
    1::Feb 06 15:14:01.512 [222] <10.2.45.144> {LogElapsedTime (common.php:82)} Time since script start: 139us [https://myserver.mydomain.lan/devicemanagement/api/device/mdm_connect]
    1::Feb 06 15:14:01.512 [222] <10.2.45.144> {require_once (mdm_connect.php:11)} vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv - PUT mdm_connect
    1::Feb 06 15:14:01.517 [222] <10.2.45.144> {Target_for_incoming_request (mdm_connect.php:20)} Found target iOS: <'iPad'[488](OWNER:User[5])>
    0::Feb 06 15:14:01.517 [222] <10.2.45.144> {_connect_transaction_1 (db.php:396)} Status='Acknowledged' CommandUUID=683038A2-539D-4393-AF61-6EB632869029
    0::Feb 06 15:14:01.533 [222] <10.2.45.144> {Task_generate_next_request (mdm_connect.php:108)} Sending request 'SecurityInfo' as CommandUUID=9ACEFE3A-013E-4DF0-A3FD-C3E7684922DC
    1::Feb 06 15:14:01.537 [222] <10.2.45.144> {SendFinalOutput (mdm_connect.php:133)} Sent Final Output (386 bytes)
    1::Feb 06 15:14:01.537 [222] <10.2.45.144> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - /devicemanagement/api/device/mdm_connect
    0::Feb 06 15:14:01.537 [222] <10.2.45.144> {SendFinalOutput (mdm_connect.php:133)} Completed in 25ms | 200 OK [https://myserver.mydomain.lan/devicemanagement/api/device/mdm_connect]
    1::Feb 06 15:14:01.570 [221] <10.2.45.144> {LogElapsedTime (common.php:82)} Time since script start: 118us [https://myserver.mydomain.lan/devicemanagement/api/device/mdm_connect]
    1::Feb 06 15:14:01.570 [221] <10.2.45.144> {require_once (mdm_connect.php:11)} vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv - PUT mdm_connect
    1::Feb 06 15:14:01.575 [221] <10.2.45.144> {Target_for_incoming_request (mdm_connect.php:20)} Found target iOS: <'iPad'[488](OWNER:User[5])>
    0::Feb 06 15:14:01.576 [221] <10.2.45.144> {_connect_transaction_1 (db.php:396)} Status='Acknowledged' CommandUUID=9ACEFE3A-013E-4DF0-A3FD-C3E7684922DC
    0::Feb 06 15:14:01.589 [221] <10.2.45.144> {Task_generate_next_request (mdm_connect.php:108)} Sending request 'ActivationLockBypassCode' as CommandUUID=EE1E1223-860A-474D-A3B6-4E165044FE69
    1::Feb 06 15:14:01.592 [221] <10.2.45.144> {SendFinalOutput (mdm_connect.php:133)} Sent Final Output (398 bytes)
    1::Feb 06 15:14:01.592 [221] <10.2.45.144> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - /devicemanagement/api/device/mdm_connect
    0::Feb 06 15:14:01.592 [221] <10.2.45.144> {SendFinalOutput (mdm_connect.php:133)} Completed in 21ms | 200 OK [https://myserver.mydomain.lan/devicemanagement/api/device/mdm_connect]
    1::Feb 06 15:14:01.785 [2109] <10.2.45.144> {LogElapsedTime (common.php:82)} Time since script start: 147us [https://myserver.mydomain.lan/devicemanagement/api/device/mdm_connect]
    1::Feb 06 15:14:01.785 [2109] <10.2.45.144> {require_once (mdm_connect.php:11)} vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv - PUT mdm_connect
    1::Feb 06 15:14:01.792 [2109] <10.2.45.144> {Target_for_incoming_request (mdm_connect.php:20)} Found target iOS: <'iPad'[488](OWNER:User[5])>
    0::Feb 06 15:14:01.792 [2109] <10.2.45.144> {_connect_transaction_1 (db.php:396)} Status='Acknowledged' CommandUUID=EE1E1223-860A-474D-A3B6-4E165044FE69
    0::Feb 06 15:14:01.807 [2109] <10.2.45.144> {Task_generate_next_request (mdm_connect.php:108)} Sending request 'ClearActivationLockBypassCode' as CommandUUID=78BD814B-A8F6-4911-93D8-FA9A5A8805A2
    1::Feb 06 15:14:01.810 [2109] <10.2.45.144> {SendFinalOutput (mdm_connect.php:133)} Sent Final Output (403 bytes)
    1::Feb 06 15:14:01.810 [2109] <10.2.45.144> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - /devicemanagement/api/device/mdm_connect
    0::Feb 06 15:14:01.810 [2109] <10.2.45.144> {SendFinalOutput (mdm_connect.php:133)} Completed in 24ms | 200 OK [https://myserver.mydomain.lan/devicemanagement/api/device/mdm_connect]
    1::Feb 06 15:14:01.844 [222] <10.2.45.144> {LogElapsedTime (common.php:82)} Time since script start: 154us [https://myserver.mydomain.lan/devicemanagement/api/device/mdm_connect]
    1::Feb 06 15:14:01.845 [222] <10.2.45.144> {require_once (mdm_connect.php:11)} vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv - PUT mdm_connect
    1::Feb 06 15:14:01.851 [222] <10.2.45.144> {Target_for_incoming_request (mdm_connect.php:20)} Found target iOS: <'iPad'[488](OWNER:User[5])>
    0::Feb 06 15:14:01.851 [222] <10.2.45.144> {_connect_transaction_1 (db.php:396)} Status='Acknowledged' CommandUUID=78BD814B-A8F6-4911-93D8-FA9A5A8805A2
    1::Feb 06 15:14:01.969 [222] <10.2.45.144> {SendFinalOutput (mdm_connect.php:133)} Sent Final Output (0 bytes)
    1::Feb 06 15:14:01.969 [222] <10.2.45.144> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - /devicemanagement/api/device/mdm_connect
    0::Feb 06 15:14:01.969 [222] <10.2.45.144> {SendFinalOutput (mdm_connect.php:133)} Completed in 124ms | 200 OK [https://myserver.mydomain.lan/devicemanagement/api/device/mdm_connect]

    So it looks like there is an issue with authentication when multiple domains are bound to my one server. I did some more testing and when I have a single domain bound, the authentication works correctly. As soon as I add even one more domain, the authentication fails again. Is there a config or plist file I need to modify?

  • I get an error trying to add ipads to the device enrollment program

    The error returns a csv file with all the serial numbers marked "Device Not Accessible"

    Hi all.
    If you are getting an 'device not accessible' error it is indeed because the ipad serials are not on your re-sellers portal.
    I have today had the same issue on numerous ipads when trying to add them with serial numbers on the DEP portal.
    Your apple re-seller will have to register the ipad serials on their side of the portal and you then should be able to add the ipads via the orders section of DEP.
    I shall be testing this tomorrow so will post an update...:)

  • Device Enrolment Program

    Hello,
    Got DEP setup and working with Meraki fine, now in the testing stage and wanting to add one of our iPads to DEP. I try entering the serial number into the Manage Devices on DEP and it comes up with this error.     Couldn't assign devices:     NOT_ACCESSIBLE.
    Anyone know what this error means?   - The Serial Code entered is correct, but getting this error message.  The iPad was purchased from an authorized reseller from apple (Albion), and Apple themselves said can just type in the serial code and it should work but no luck..
    Any help on this one would be much appreciated as got over 600 iPads to roll-out soon.

    I'm running into the same issue. Except in my case, it has just been particular ones, the majority has been just fine. I think I also remember hearing something about there being an issue with not buying them directly from Apple that could cause issues (maybe this one). The iPads giving me this error are the ones that I'm not sure of their origin, most Apple products we buy are buy with a quote that I generate, so I'm not for sure about these giving me the error. I'm also still looking for a solution...Have you had any progress?

  • Email profile uses Device Enrollment Manager user?

    Hello,
    I have an iOS device that was enrolled via the Apple Device Enrollment Program, using a Device Enrollment Manager account, and I have since deployed an email profile configuration policy to it.  After it received the policy now the account
    of the Device Enrollment Manager is locked in as the user in the email profile.  Is that normal behavior?  I thought that enrolling a device using a user who is a member of the Device Enrollment Management group would leave the device open for another
    user?
    Thanks!

    Hello, I was looking through TechNet a little more about this and unless I'm reading this wrong, which is certainly possible, it seems to suggest that you should be able to access company data as the end user using CYOD enrollment or a device enrollment
    manager enrollment scenario:
    User affiliation – Specifies how devices are enrolled.
    Prompt for user affinity – The device can be affiliated with a user during initial setup and could then be permitted to access company data and email as that user. This mode supports a number of scenarios:
    Corporate-owned personal device – “Choose Your Own Device” (CYOD) Similar to privately owned or personal devices but the administrator has certain privileges including permission to wipe, reset, administer, and unenroll the device. The
    device’s user can install apps and has most other permissions for device use where not blocked by management policy.
    Device enrollment manager account – The device is enrolled using a special Intune administrator account. It can be managed as a private account, but only a user who knows the enrollment manager credentials can install apps, wipe, reset,
    administer, and unenroll the device. For information about enrolling a device shared by many users through a common account, see
    Enroll corporate-owned devices with the Device Enrollment Manager in Microsoft Intune.
    No user affinity – The device is user-less. Use this affiliation for devices that perform tasks without accessing local user data. Apps requiring user affiliation are disabled or won’t work.
    With this in mind, since accessing corporate data as the user is supported with CYOD and device enrollment manager, I can't imagine that the intention of the device enrollment managers (DEM) group was designed so when a device is enrolled with a DEM
    user that only data for that DEM user is available, right?  That just wouldn't make sense.  Also, if enrolling a device using a DEM user account is only for devices that don't need access to corporate data, then what's the difference between enrolling
    a device using a DEM user, or enrolling a device with "No user affinity"?  Also, when I've enrolled a device using a DEM account, I was later easily able to install apps with no prompt for DEM credentials, TechNet seems to imply that credentials
    are needed for functions like that.  Shouldn't something have asked me for permission to install an app?

  • Cannot enter country into Individual Enrollment Program

    hi,
    i'm really a novice into Apple Store and Products for Development, so i hope to be clear.
    I'm an italian app developer, and i'm figuring a strange behaviour into Individual Apple enrollment program: when i fill in the form for billing, country field is deactivated so i can't choose anything. So that at the next step Apple shows me an error. I even tied with Safari or Chrome or Firefox, but nothing changes (i'm using a MacBook Pro).
    How to fill in the form properly?
    I remark that i tried to submit as a company but i'm wasting many days with D&B number that is always reported as wrong from Apple, even if i directly contacted D&B support to make verification and updated on my D&B account.
    Thank you in advance

    Hi,
    Thank you for posting in Windows Server Forum.
    Did you find any relevant log for this case?
    Also please try to reinstall the app or on another device and check whether you facing same issue.
    Thanks.
    Dharmesh Solanki
    TechNet Community Support

  • W8.1 User Device Enrollment - Setup.exe

    Behavior: On W8.1 Enterprise upon logging into 'portal.manage.microsoft' for the first time then proceeding to device enrollment a download link is present for the full Intune client agent (as expected). If the user closes the browser without enrolling then
    logs in again only MDM device enrollment tips are displayed. Using a private browser session also only shows MDM enrollment tips.
    Question:
    - Is this behavior a bug or by design?

    On Windows 8.1 Enterprise, the expected behavior is to only see the "Learn how to enroll" link when you click the Add Device button.
    I cannot reproduce it showing the download link on 8.1 devices.
    Please feel free to open a support case if it looks like something isn't working as expected.
    Thanks,
    Jon L. - MSFT - This posting is provided "AS IS" with no warranties and confers no rights.

  • Device Enrollment could not be installed due to an unexpected error

    Hi I just installed OSX LION Server and want to enroll devices but I keep on getting the error : Device Enrollment could not be installed due to an unexpected error :
    The profile “Device Enrollment (com.apple.ota."my-server-name-".private.bootstrap)” could not be installed due to an unexpected error.
    My devices site is running properly, I can install Profiles but I cannot install any device, not even the mini I installed OSX Lion Server upon!
    I already removed all certificates and keys for : ""my-server-name-".private" and recreated self signed certificates for SSL and code signing.
    Any ideas?
    Bert

    So I just wasted half of a day on this, and at least for my own system I figured it out *without* doing a clean install.
    1. First, check that you have opened the ports as suggested by others here.
    2. If you've done that, then the problem may be a rogue entry in your DNS server setting.  What that means is if you initially set up your server app with one name, then later switched it to a new one, the old name is still "hanging around" causing havoc.  This was the problem.  To fix, you can try the steps below. WARNING: this will wipe your open directory. Make a full backup!  I'm not 100% sure that wiping your OD is necessary, but it worked for me.  Turn off any services you're running.
    3. Download the 10.7 server admin tools here: http://support.apple.com/kb/DL1419
    4. Open up the WorkGroup manager, and select any network users you've created, then export them.  You're backing them up because you're going to wipe your open directory.
    5. Open Server Admin.app. Click on the reveal triangle for your server, and it will show an entry for "Open Directory". Click on that.
    6. Click on the Settings gear in the top of the right panel.
    7. Where it says Role: Open Directory Master, hit Change....
    8. In the panel that pops up, hit "set up a standalone directory".  It will warn you that it's going to wipe your server open directory data.
    9. Now, on the left side of the same screen, select DNS, then hit the "zones" button on top.
    10. Look for your old host name(s) there.  Select any extra entries that have your old host names, and remove. DO NOT REMOVE your current name entry (the Primary Zone) or the reverse entry (Reverse Zone).  If you remove those, you'll be totally hosed. Only remove redundant entries.
    11. Back in the Server.app, go to the menu and select Manage -> Manage Network Accounts.  It will ask you for some information as it sets up open directory again for you.  Give it what it needs.
    12. To re-import your saved account info, go to Manage -> Import Accounts From File. (I have not tried this step, but it *should* work. YMMV).
    13. Now, go reactivate your profile manager, turn on device management.  It should "think" for a bit while it churns through the new open directory data.
    14. Now, it should work!!! (at least it does for me).  I speculate that the name lookup was getting conflicting results from DNS, causing problems and confusion.  This seems to have fixed it.
    15. If that doesn't work, one other step I took (but it didn't seem to help by itself) was to wipe the device manager database.  To do that, open a terminal and use
    sudo /usr/share/devicemgr/backend/wipeDB.sh
    WARNING: this will wipe any device info that you've set up.  I don't think this is necessary, but might be used as a last ditch effort.
    Hope that helps!

Maybe you are looking for