Scripts to start migration from PlugnCast G2 to PlugnCast G3

SUMMARY

The scripts provided here allow to initiate a PlugnCast G2 to PlugnCast G3 migration:

WARNING:

2019-10-09 Scripts migration PlugnCast G2 to G3 - V1.10.12 Download

BUG FIX, NEW FEATURES, MINOR UPDATES
  • Fix: the devices was installed twice, once with a MAC address with :, another occurence with -:
    • ex:
      • DMB400_1 00:1C:E6:02:FF:FE
      • DMB400_2 00-1C-E6-02-FF-FE
COMPATIBILITY
  • MS-Windows 2008, 2012, 10
    • Powershell scripts execution need to be authorized on the MS-Windows system

INFORMATION


SHARE A SAME DIRECTORY

Each script is associated to a Powershell file (.ps1). When it is executed, these scripts need to be present in the same directory. For example:

- `<Directory1>`
    - retrieveG2Config.cmd
    - retrieveG2Config.ps1
    - setG3Config.cmd
    - setG3Config.ps1

ADAPT THE SCRIPTS TO YOUR NEED

LAUNCH THE SCRIPTS

AUTHORIZE THE EXECUTION OF POWERSHELL SCRIPTS WHICH ARE NOT SIGNED

By default, your OS may not authorize to execute this Powershell script, because it is not signed. In this case, a Powershell error is returned:

PS > C:\temp\<script>.ps1
Impossible de load the file C:\temp\<script>.ps1.
C:\temp\<script>.ps1. is not digitally signed. You cannot execute the script on the current system. For further information on the script execution and the execution strategy definition, refer to the chapter about_Execution_Policies to the URL:
- https://go.microsoft.com/fwlink/?LinkID=135170.
    + CategoryInfo          : Security error: (:) [], ParentContainsErrorRecordException
    + FullyQualifiedErrorId : UnauthorizedAccess

To work around, contact your system administrator to help you to authorize such not signed Powershell scripts.

OLD VERSIONS HISTORY


2018-06-21 Scripts migration PlugnCast G2 to G3 - V1.10.11 Download

BUG FIX, NEW FEATURES, MINOR UPDATES
  • Initial version
COMPATIBILITY
  • MS-Windows 2008, 2012, 10
    • Powershell scripts execution need to be authorized on the MS-Windows system