![]() ![]() Use the system proxy settings in the device browser. In Server and Proxy Details, select Use Proxy to deploy Client check box to select further the proxy type mentioned below:ġ. Select No if you want to generate a token for the AD/LDAP or Azure deployment method. Go to Endpoints > Mass Deployment > Edit > Deploy without device mapping. Using the email construct formats defined in Mass Deployment Settings. For more information, see Manage device mapping. Go to Endpoints > Device Mapping > Import Device Map CSV. Using device mapping CSV file that contains user and device mapping details. Select Yes if you want to generate a token to Deploy: Use the Device Mapping or the Email Construct Format for Client Deployment Under the Deployment Details section select the following: On the Mass Deployment tab, select Generate New Command. The mass deployment command consists of a parameter (with a token) used as a security mechanism to ensure that the inSync Cloud processes activation requests only from authentic inSync Clients. Step 03: Generate a command for mass deployment If you want to change the priority order in which you want inSync to search the users, modify the settings as desired. Upon successfully saving, the Settings page displays the configured settings. Select the Find email match in AD checkbox if you want to search the user in the organization's Active Directory in case the user is not located using the email addresses in inSync as defined in Step 6. InSync forms an email address of the user using the logged-in username in combination with the domains that you have entered.įor example, the following listed domains provide an example of the priority order you can select as desired: The option is only applicable if you do not have AD/Non-AD/AzureAD or SCIM Provisioning to onboard users. In the Domain field, enter the Domain as per the priority order you want inSync to look up for the user. Any resemblance in the username can cause the user's data to get accessed by another user.įor Windows Device: InSync queries for "Set U" command and checks the logged in user name.įor MAC devices: InSync queries "printenv" command and checks for $User and get the logged-in user details. Ensure that users cannot modify the username on the device. Therefore, ensure that the users do not have permission to modify their username on their devices if you select this method to mass deploy inSync Client on user devices.ĭeployment without device mapping utilizes ‘username’ as the unique device identifier to deploy inSync Client on user devices. Select the Deploy without device mapping checkbox when you want to perform mass deployment of inSync Client on user devices that are not mapped in the inSync Management Console.ĭeployment without device mapping method uses the user's logged-in username to form the user's email address. InSync Client users can either replace an old device or add a new one as an additional one. ![]() Select the Prompt user if device mapping not defined checkbox to enable the following when the user-to-device mapping is not defined on the Console:Īdministrator and the inSync Client user can define the device behavior. Uncheck this field, the inSync Client will be activated on all the devices the user logs on. Select Activate only the first device for every user if you want to activate inSync Client on the first device the user only logs on. The Mass Deployment settings window appears. Go to Endpoint -> Mass Deployment tab from the left navigation bar. If you activate the inSync Client only on the first device, then users with multiple laptops have to log on manually and activate inSync Client on their subsequent devices. Step 02: Configure mass deployment settingsīefore configuring the mass deployment settings, make sure if you want to activate the inSync Client only on the first laptop that the user logs on to or on all the devices that the user logs on. Set the expiry period in the Expire date box.Ĭlick Create New Token. Select Enable Expiry Date check box to set the expiry date. The Mass Deployment Token Window appears. ![]() On the Endpoint workload page, select Mass Deployment. inSync Cloud does not authenticate any request that has an expired token attached to it. You can enable an expiry date for a mass deployment token. Always add the most recently generated mass deployment token while deploying inSync Client. Once you generate a mass deployment token, all previous tokens become invalid. You can generate a mass deployment token considering the following guidelines: During integrated mass deployment (IMD), when installing inSync Client on user devices using an automated installation tool, you must include the mass deployment token as a parameter for installation. The mass deployment token is a security mechanism used to ensure that Druva Cloud processes activation requests from authentic clients. ![]() Step 01: Generate mass deployment activation Token ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |