DEP Token(s) allow your FileWave server to talk to Apple's DEP (Device Enrollment) services. This service is critical in supporting automated enrollment workflows, and is also critical in making sure your devices are able to be managed at the enterprise level.
We are going to use the DEP Accounts section of the Sources view whenever we want to add, remove or update a DEP token. Only through valid token(s) can the FileWave server talk to Apple to get device based information. This same method of communication is used to send our DEP profile information back to Apple for installation on the endpoint during the Setup Assistant phase. So, yes, it is critical!
Edit and Deletion of Tokens are done from the actions menu for any particular token as shown below. Obviously one needs to take care before deleting a token, so you will be prompted for confirmation.
Editing (aka renewing) or adding a token consists of the following 3 steps:
- Download the FileWave server's public Key and save it locally (this identifies the server to Apple)
- Login to either ASM or ABM and add or update MDM server as appropriate with above public key, and then download the generated DEP token
- Upload the DEP Token back into FileWave
Apple's DEP servers prevent communication when your external IP changes, and traffic will be blocked until you renew your token. This most often happens in the instance of your network doing some type of disaster recovery failover.
Your FileWave server synchronizes nightly with Apple DEP servers automatically. However, if you need to sync manually in the mean time you can do so from this view by clicking the (
) icon. You'll be prompted for either a Sync (recommended) or a Full Sync (use only under special circumstances) as shown below: