Install and configure Cloud Extender

This chapter describes how to install and configure Cloud Extender. The tool consists of several “extensions”.

Install Cloud Extender

  1. Double-click the file SDMCloudExtender_versionXX.msi to start the setup.

    The Snow Cloud Extender Setup dialog box appears.

  2. Click Next.

  3. Read and select the checkbox to accept the End User License Agreement, and then click Next.

  4. Click Install, and then click Next.

  5. Click Install, and then wait for the installation to finish.

  6. Select the Run Snow Cloud Extender check box, and then click Finish.

    The Snow Cloud Extender Setup dialog box appears.

Configure Cloud Extender

  1. In the Snow Cloud Extender Setup dialog box, perform one of the following actions:

    • If you have a configuration file, click Load Config and select the configuration file.

      The Settings dialog box appears and the Server Connection settings are automatically loaded.

    • If you don’t have the configuration file, click Settings.

      The Settings dialog box appears. Type the Server Connection settings in the dialog box. The Settings are provided by Snow server administrator.


      If you click Skip in the Snow Cloud Extender Startup dialog box, Cloud Extender will open, but it will not start.

      To manually configure Cloud Extender, click Settings on the menu and manually type the Server Connection settings in the Settings dialog box.

  2. In the Settings dialog box, select the User Directory check box and click Configure.

  3. In the LDAP User Directory Explorer dialog box:

    1. According to your directory infrastructure, type one of the following in the LDAP box:

      • LDAP://<FQDN>

      • LDAP://<HostName>

    2. If needed, select an additional connection option in the list to the right of the LDAPbox.


      If you have connectivity issues, try with SSL since some companies require LDAP traffic to be signed and/or encrypted.

      If you select IP as the LDAP address, LDAP signing and encryption might fail to work.

    3. Type the Username and Password.

    4. Click Connect.

      You will now connect to the directory server and the content will be displayed in the AD window to the right.

      The content that will be synchronized to Snow Device Manager is displayed in the Preview box.

    5. If you want to connect to another directory, for example eDirectory, click Schema and define the settings in the dialog box.

Configure selections

To configure and view the selections for the synchronization, perform one or more of the following actions in the LDAP Active Directory Explorer dialog box:

  • To add an object from the Active Directory to the selection:

    • Select the object in the AD window, right-click and then click Add Include.

    • If needed, an object can be manually defined. Click Add and define the object in the Selection dialog box.

  • To change the order of the objects, select an object and then click Up or Down. The order of the selections is important because the selections will be applied in an up to down order.

  • To update the Preview box, click Refresh.

  • To find more information about a specific object, right-click the object in the AD window and then click Properties.

Add paths

A path is used for exclusive Active Directory queries, for example the path to an OU. Once a path has been defined, the selections will be applied for that path only or for several paths.

There are two different procedures to add a path in the LDAP Active Directory Explorer dialog box:

  • In the AD window, right-click an object and then click Add path.

  • If needed, a path can be manually defined:

    • Click Add and type the path, for example “OU=ExchangeUsers,DC=dev3,DC=local”, in the Path box.

    • Type an appropriate Display name. The name will be the name of the path in Snow Device Manager.

Synchronize Cloud Extender

Cloud Extender is synchronized daily. To manually synchronize Cloud Extender, click Update on the menu bar.


If there is an error message in the synchronization log, it is probably caused by a misspelled account user name or key.

Logs are found in: C:\log