Currently Being ModeratedSep 20, 2013 12:57 PM (in response to Mel7713)
you might want to look into something called configurator: https://itunes.apple.com/us/app/apple-configurator/id434433123?mt=12
Currently Being ModeratedSep 20, 2013 8:32 PM (in response to Mel7713)
Or, if the devices aren't regularly "checked in" with the computer running Apple Configurator, then Profile Manager may make sense as it can remotely manage machines over the air:
Currently Being ModeratedSep 21, 2013 10:54 PM (in response to William Lloyd)
Will Profile Manager allow you to control the new Activation Feature in iOS 7? We have a deployment of a couple hundred iOS devices but do not run any type of MDM solution. Basically the phones are deployed for phone calls and e-mail access. Any app purchases are up to the employee. Now that the device will be registered to the user's AppleID, I can no longer wipe a device and redeploy it without knowing what the AppleID credentials are from the previous user. The previous user may no longer even be with the company.
Currently Being ModeratedSep 22, 2013 1:17 PM (in response to t_penn)
A workaround is to institute a policy that the cost of 'lost' or locked
iPhones are deducted from the employee's last paycheck. Consult
with your legal department and human resources for wording. A company
I am familiar with experienced a large drop in the number of employee devices
and garments being reported lost when the cost was deducted from paychecks.
Include a step in the exit interview (employee turns in ID, company
issued uniforms or safety gear, etc.) that has the employee clear any
security he/she has set on the iPhone/iPad.
If not legal in your country or there is no pay lag at your company, you
will have to wait for Apple to come up with a solution.
Currently Being ModeratedSep 23, 2013 7:03 PM (in response to t_penn)
There is no way around Activation Lock *except* on devices managed by Apple Configurator.
If employees turn in phones but refuse to disassociate the Apple ID from their iCloud account, they will be unusable. You'll need an HR policy to deal with this, as there is no technical solution.