The Snow integration is now available on the Halo Web Application. This integration will work for both internal and publically accessible instances of Snow, however you will not be able to perform any imports through the web client to internally accessible Snow instances if your Halo couldn't access it.
When navigating to the integration page you'll need to enter your snow application URL, username and password. Note that the user you use for this must have the role of "Api User" else the integration will not function.
After this you'll be able to import clients, note that the client import will also import licences but will only import licences for clients that have devices imported. Clients with no devices will not have licences imported. This means the first client import will also not import any licences so a client import, then a device import then another client import must be run to import licences. This is a limitation of the Snow API endpoints and the easiest way to access licences and link them without affecting device import speed.
Once you've imported clients you should then be able to devices as no devices can be imported before clients are imported. Before importing devices make sure to set all the mandatory fields for site, asset type and Asset-user matching type. The final setting chooses which users will be related to the asset in Halo and there are several options.
There also several miscellaneous options available for the device import shown below to prevent the updating of certain fields against devices. These were added for those who'd previously used the older snow integration with the Windows Client to prevent the creation of new devices, changing of device types and changing of device locations due to the use of a new id for the Snow Integration in the Web App.
Note that the Asset import imports both Computers and Mobile Devices as they are classified in Snow.
The Snow integration is now available on the Halo Web Application. This integration will work for both internal and publically accessible instances of Snow, however you will not be able to perform any imports through the web client to internally accessible Snow instances if your Halo couldn't access it.
When navigating to the integration page you'll need to enter your snow application URL, username and password. Note that the user you use for this must have the role of "Api User" else the integration will not function.
After this you'll be able to import clients, note that the client import will also import licences but will only import licences for clients that have devices imported. Clients with no devices will not have licences imported. This means the first client import will also not import any licences so a client import, then a device import then another client import must be run to import licences. This is a limitation of the Snow API endpoints and the easiest way to access licences and link them without affecting device import speed.
Once you've imported clients you should then be able to devices as no devices can be imported before clients are imported. Before importing devices make sure to set all the mandatory fields for site, asset type and Asset-user matching type. The final setting chooses which users will be related to the asset in Halo and there are several options.
There also several miscellaneous options available for the device import shown below to prevent the updating of certain fields against devices. These were added for those who'd previously used the older snow integration with the Windows Client to prevent the creation of new devices, changing of device types and changing of device locations due to the use of a new id for the Snow Integration in the Web App.
Note that the Asset import imports both Computers and Mobile Devices as they are classified in Snow.
