Loading
Importing mobile devices?

Yesterday I asked Snow Support a question about how to import circa 750 mobile devices into SLM and assign them to users. The response was as follows:

"You are able to import mobile devices as objects however you will be unable to attach these to users via the import method. The option you have is to do it manually whereby uploading mobiles as objects and manually assigning them to users within Snow License Manager."

Does anyone here have experience of this, or recommend a more efficient method?


  • Jelle Wijndelts (Flexera Software)

    Hi Greg, this warrants a bit more clarification and a few more questions. Do you currently have a Mobile Device Management (MDM) solution(Like Mobile Iron, Airwatch)? Would you like to hold the mobiles as an asset in the mobile section of Snow License Manager(SLM)? if yes to both option above it is possible to import mobile device information into SLM as a data feed, similar as SCCM or a snow client. Please be aware that they will become a managed device in your system and as such will require a Snow License. if you don't have a MDM solution then depending on the format of the data it could be imported into the same section using a xml feed. Alternatively you have the option to import the mobiles into the objects section (this does not affect your SLM license count) if you create an attribute username against the object you could import the username into that field(this is not linked to your Snow users but you can still report on this using the object reporting, or as advised by the Servicedesk you can import the objects into SLM  and then assign them to users. They are then linked to the users in the user section( please be aware you will only see users in this list that have been discovered as part of your discovery(e.g. Snow Agent) The third option you have is create a user defined field(s) against the category users and then import the data into that. for more information see the import guide available under the help section in SLM.
    Expand Post
    • Jelle, thanks for your comprehensive reply. I'd reviewed the 'User Guide - Data Import Field Description' document yesterday but as it didn't cover mobile devices I followed through with the Snow Support team. MDM - yes, we have InTune and a separate proprietary solution with our mobile provider. The latter is the preferred data feed as it holds more mobile-specific detail such as IMEI and we can request the data nightly in the required format. SLM Asset - not necessarily. We'd like to hold the data within Snow in any useful way we can, be it objects, assets or user-defined fields.  The end goal is to be able to report on devices assigned to users, e.g. John Doe has assigned to him 1 Dell Latitude laptop, 1 iPhone and 1 iPad. Currently we are running this report as a complicated set of vlookups and pivots based on exported data from several sources such as Snow, MDM and Active Directory.
      Expand Post
      • Jelle Wijndelts (Flexera Software)

        Hi Greg, I have asked Lauren Thomas, your account manager, to give you a call to explain the options in more detail.
        • Thanks Jelle I'll update this thread with our solution once we've worked it out.
          • Greg - how is this going or how did this end for you? Thanks.
          • Jelle Wijndelts (Flexera Software)

            Hi Greg, I have taken another look at the import function for objects. it is possible to import the object and the username as well.  the high lighted fields are the fields that are linked to agreements, users and computers. Jelle
    • We use Intune as well but are looking to move phones as well as other devices into Snow as an interim solution before moving to a full CMDB solution. Is it possible to do a bulk upload of devices with their username if you have this in Excel/CSV format?
      • Jelle Wijndelts (Flexera Software)

        Hi Angelique, yes it possible to bulk import into the objects section. The steps will be to create the different abject types you want to store, against each object type you define the attributes you want to store. for example. Object type Mobile Jelle
        • Thanks Jelle! Is there a step by step guide or overview that details how to create the custom objects and then bulk import from a CSV?
          • Jelle Wijndelts (Flexera Software)

            Hi Angelique, Please see below a step by step guide on creation of objects(this is an extract from the user manual section 15. 1                               OBJECTS This chapter describes how to manage objects in Snow License Manager.   1.1                       ADD OBJECT On the Objects menu, click Add object . The Add custom object view To speed up the registration process when adding multiple objects, select the After object has been saved, open new form for same object type check When selected, the system will automatically go to Add object with the current object type selected when you save the current item. Enter information in the fields on the tabs according to the following Click Save .   1.1.1              PROPERTIES TAB Use the Properties tab to enter properties for the object: Select an Object type from the Type a Name of the Select Organization node from the list in order to attach the object to a specific part of the organization. Enter Property values of the Available property values depend on selected object type. Click the Select computer icon for Linked computer to search for a computer and link the object to Click the Select user icon for Linked user to search for a user and link the object to   1.1.2              AGREEMENTS TAB The Agreements tab is only available if the selected object type can be attached to an agreement. To attach the object to an agreement: Click the check boxes to select an   1.2                       ADD OBJECT TYPE To create a new object type: On the Objects menu, click Object types . On the context menu, click Add object type . The Add custom object type view Enter information in the fields on the tabs according to the following Click Save .     1.2.1              INFORMATION TAB Use the Information tab to enter basic information on the object type: Type a Name of the object Type a Description of the object type. To make it possible to attach objects of this type to agreements, select the This object type can be attached to agreements check   1.2.2              PROPERTIES TAB Use the Properties tab to define the fields that will be available (and mandatory) when registering an object of this type: Click Add property . A dialog box Select Type of field from the Type a Name and a Description for the To make this property mandatory for all objects of this object type, select the Mandatory check box. Click Save . Repeat for all properties   1.3                       EDIT OBJECT TYPE To edit details of an existing object type: On the Objects menu, click Object types . The Custom object types view Click the object type to be edited. The Object type tabs Edit the details for the object Click Save . To import data into SLM follow the following steps.(extract User Manual section 17) 1                               IMPORT DATA Import data is a wizard-based feature for data import. Depending on type of import, either new objects are created or existing objects are updated with new metadata. To import new or updated information, use an Excel (XLS or XLSX) or a CSV (Comma Separated Values) file with the import data. Information can be imported to the pre-defined fields and to most custom fields applicable to the category (except from custom fields of type currency).   NOTE Available import types depend on what access rights the logged on user has.   There is a dedicated wizard for each type of import/update. The wizards guide you through the steps of the import/update. The procedure is described in the 17.2 Run import and consists of the following steps: Upload a data Import Field Preview of imported   Import of Microsoft License Statement MLS files is described in 17.3 Microsoft License Statement (MLS) file import .   1.1                       INTRODUCTION To import a file, the file has to be validated and the column names of the import source file need to be mapped to the corresponding fields in Snow License Manager.   1.1.1              IMPORT FILE The import source file can be in Excel (.xls or .xlsx) or CSV format, and both source files with or without file headers can be used. To download templates for importing data to Snow License Manager: On the Home menu, click Import data . The Import data view Click Import templates . The Import templates dialog box appears. Select one import template from the list and then click Download . The template is   NOTE If the source file has a header, the column names of the file does not have to be the same as the destination field names in Snow License Manager. For a successful import of new or updated information in Snow License Manager certain information must be provided. For more detailed information on required import data, and where     the data can be found in Snow License Manager after the import, see the document Data Import Field Description.   1.1.2              VALIDATION OF DATA To verify that only allowed data types and values are included in the import source file, the Import data function validates the data before it is imported. In the preview step of the import, errors are high-lighted in red. Point to the field to see more information on the error.   Errors and conflicts that are high-lighted in red prevent import/update of data.   Data can only be updated for an object that already exists in Snow License Manager. If the import data does not match an object in the database, it is not possible to continue with the update of that particular object.   1.1.3              FIELD MAPPINGS In the Field mappings step of the import, the column names of the import source file need to be mapped to the corresponding fields in Snow License Manager. If the import source file has no header, index mapping can be used instead. This means that the fields of the import source file will be identified by index (column position 0, 1, 2, etc.) instead of text (column header).     1.2                       RUN IMPORT On the Home menu, click Import data . The Import data view Click selected import type to start the import   1.2.1              UPLOAD A DATA SOURCE Click Browse and select the import source If the import source file is a CSV file, select used Delimiter from the Otherwise, leave the default value. Click Next .   1.2.2              IMPORT  SETTINGS Manage settings for the data import according to the following Available import settings depend on type of import/update. Click Next .   S ETTINGS FOR ALL IMPORTS / UPDATES In the New organization action list, select how to handle organizations that exist in the import source file but not in the Snow License Manager database. The options are described in the following table.       Options for New organization action Description Do nothing Unknown organizations will be ignored. However, information on organization is required for a successful import. The field will be highlighted in the Preview step and it will not be possible to import data for that particular  row. Create The system will create the new organization node, either directly under the root (for example: ROOT/[new organization node]) or according to the path in the import source file (for example: ROOT/IT/[new organization node]).   L ICENSE IMPORT SETTINGS In the Identity mapping section, select which identity field to use when a license is mapped to an application: SKU (Stock-keeping unit) Application Name Application Part number C OMPUTER UPDATE  SETT
            Expand Post
10 of 11

Related  Product Forums


                     → Flexera One



                      → Snow Atlas



                      → FlexNet Manager



                      → Snow License Manager



                       → App Broker


       Need help finding an answer?


        Ask a Question →


Loading
Importing mobile devices?