1927 How to correct issue where User cannot take ownership of Azure AD-joined device with provisioning package (Key Files are not being stored in E

How to correct issue where User cannot take ownership of Azure AD-joined device with provisioning package (Key Files are not being stored in Endpoint device)

Issue: Where AzureAD users attempt taking ownership of AzureAD-joined endpoint devices that are synchronized to SecureDoc Enterprise Server, the requisite Boot and Personal Key Files are not being placed into the endpoint devices so ownership is not finalized.

Work-Around:

1. Add Azure AppID
   1. Login SES Web
   2. At the top right corner, Click on “NewUI” hyperlink near top-right corner of panel

• 1. On the left panel, select the Configuration icon.
  2. If not in the General menu (at left edge of panel), click General.
  3. On the right panel, scroll down to the “Azure AppID” option
  4. Enter your Azure Application ID (as shown in image below)
  5. Click the Save button

1. Restart SDConnex
   1. Launch the SecureDoc Services Configuration.
   2. Click on SDConnex Service in the left-edge navigation to display SDConnex settings and Actions menu.
   3. Click the Stop option in the Actions list at the right edge of the panel.
   4. Wait a minute, then click Start