Skip to main content

PDMS-E to Poly Lens Import FAQ

The following FAQ will address the PDMS-E migration into Poly Lens.

Q1: What data can be imported into Poly Lens from PDMS-E?​

A: The following are imported today:

  • Device level policies
  • Site level policies
  • Group level policies (equivalent to group PDMS-E policies and as the top priority group in Poly Lens model level policy from PDMS-E)
  • Model level policies (equivalent to PDMS-E global policies)
  • Group membership
  • Site membership

Coming shortly:

  • Site subnet configuration

Not imported, nor planned to be:

  • User accounts
  • Devices are not redirected automatically allowing for inspection of imported data before they are pointed to Poly Lens

Q2: Import went well but I see errors of the below type, is everything ok?​

Device Identifier: 0004f2fc3260
Errors:
The log.sched.1.level setting is not a valid setting for this model.
The log.sched.1.period setting is not a valid setting for this model.
The mr.pair.uid.1 setting is not a valid setting for this model.
The reg.1.address setting is not a valid setting for this model.
The reg.2.address setting is not a valid setting for this model.
The reg.2.displayname setting is not a valid setting for this model.

A: YES, import worked fine. The above are common when importing PDMS-E policies as PDMS-E relies on device ignoring parameters not applicable to its model. Poly Lens does strict schema validation hence the errors. We will update the error log shortly to indicate the fact that these are not actual errors.
 

Q3: Some devices have not been imported as reported by import below, why?​

Device Identifier: 8g19134d5342f9
Errors:
Device not imported because it belongs to a different

A: This is expected as the device already belongs to a different account. While this will be practically nonexistent in production we see these in testing mostly due to reuse of devices across accounts.

Q4: The import didn't work for some settings and reported errors of the below type:​

The {{setting_name}} setting has not been given a value of the correct data type.

A: This means the value assigned to the setting is either of the wrong type (integer vs Boolean for example) or outside the range permitted. This indicates incorrect configuration and as such this specific setting won't be used in the policy. It again is not an import error but rather original configuration mistake.

Q5: All data seems to have been imported correctly but I get a message indicating I can download error log file but when downloaded it's empty.​

Congratulations, everything worked perfectly!

A: Empty error log indicates there were no errors. This will however be fixed in the Poly Lens UI not to point to an error log shortly.