Reference Material | Migration Tool

The Specops Deploy / App migration tool can be used to copy, move, export, and import Specops Deploy / App settings.

Copy configuration from one GPO to another

You can copy Specops Deploy / App settings from one GPO to another using the Migration Tool. Deployments, packages, and target will be overwritten in the destination GPO if they have the same unique ID. This will be the case if they have been previously copied from the same source GPO.

To proceed with this task, you must have:

  • Write permission in the destination GPO.
  • Access to the source and destination GPO from the same environment.
  1. Open the Specops Deploy Migration Tool.
  2. Click Copy Configuration from one GPO to another.
  3. From the Domain drop-down, select the domain that contains the source Group Policy.
  4. From the Group Policy Object drop-down, select the GPO with the settings you want to move.
  5. You will be given the option to selected what is included from the source GPO:
  • Include all deployment settings from the GPO: Select this option if you want to include all of the GPO content. If any issues are detected, such as missing setup files, it will be included on the following page.
  • Select which deployments, packages, etc to include: Select this option if you want to only include part of the GPO content. You will be asked to specify which deployments, packages, and targets to include in the proceeding pages of the wizard.
  • Include the setup files: Select this option if you want to move or copy the setup files (MSI files) from their current network shares to a new location. This may be necessary if copying/moving from one domain to another. Do not select this option if the same source files, from the same network shares, are to be used from the destination GPO.
  1. If Select which deployments, packages, etc to include is selected, you will need to complete the below steps. Otherwise, skip to step 7.
    • Select the deployments you want to include.
    • Select the package you want to include. Selected deployments from the previous page will have their corresponding package selected and cannot be changed.
    • Select the targets you want to include. Selected deployments from the previous page will have their corresponding targets selected and cannot be changed.
  2. From the Domain drop-down, select the domain that contains the destination GPO.
  3. From the Group Policy Object drop-down, select the GPO you want to import the settings into. A GPO that already contains Specops Deploy settings (marked with the Specops icon) can be selected, along with those that do not. You will need to have permission to update the selected GPO.
  4. A list containing all root paths of the packages being imported will be displayed. You may need to take the appropriate action, if:
    • The settings are copied or moved from one domain to another: You may need to update the root paths where the setup files are located.
    • The import includes the setup files and you do not have write permissions to the new share: you will need to supply a corresponding path where you have write permissions.
    • The share path is, for example \\Server1\Software: You may be able to use \\server1\c$\Software as a corresponding writable path.
  1. Click Next.
  2. Verify that the required data for the import has been collected, and click Next.
  3. A message will appear. You will be required to click Yes to continue the import.
  4. Click Finish.
Move configuration from one GPO to another

You can move Specops Deploy / App settings from one GPO to another using the Migration Tool. Deployments, packages, and target will be overwritten in the destination GPO if they have the same unique ID. This will be the case if they have been previously copied from the same source GPO.

To proceed with this task, you must have:

  • Write permission in both destination GPO and the source GPO (since the selected objects will be deleted from the source).
  • Access to the source and destination GPO from the same environment.
  1. Open the Specops Deploy Migration Tool.
  2. Click Move Configuration from one GPO to another.
  3. From the Domain drop-down, select the domain that contains the source Group Policy.
  4. From the Group Policy Object drop-down, select the GPO with the settings you want to move.
  5. You will be given the option to selected what is included from the source GPO:
  • Include all deployment settings from the GPO: Select this option if you want to include all of the GPO content. If any issues are detected, such as missing setup files, it will be included on the following page.
  • Select which deployments, packages, etc to include: Select this option if you want to only include part of the GPO content. You will be asked to specify which deployments, packages, and targets to include in the proceeding pages of the wizard.
  • Include the setup files: Select this option if you want to move or copy the setup files (MSI files) from their current network shares to a new location. This may be necessary if copying/moving from one domain to another. Do not select this option if the same source files, from the same network shares, are to be used from the destination GPO.
  1. If Select which deployments, packages, etc to include is selected, you will need to complete the below steps. Otherwise, skip to step 7.
    • Select the deployments you want to include.
    • Select the package you want to include. Selected deployments from the previous page will have their corresponding package selected and cannot be changed.
    • Select the targets you want to include. Selected deployments from the previous page will have their corresponding targets selected and cannot be changed.
  2. From the Domain drop-down, select the domain that contains the destination Group Policy.
  3. From the Group Policy Object drop-down, select the GPO to move the settings into.
  4. A list containing all root paths of the packages being imported will be displayed. You may need to take the appropriate action, if:
    • The settings are copied or moved from one domain to another: You may need to update the root paths where the setup files are located.
    • The import includes the setup files and you do not have write permissions to the new share: you will need to supply a corresponding path where you have write permissions.
    • The share path is, for example \\Server1\Software: You may be able to use \\server1\c$\Software as a corresponding writable path.
  1. Click Next.
  2. Verify that the required data for the import has been collected, and click Next.
  3. A message will appear. You will be required to click Yes to continue the import.
  4. Click Finish.
Export GPO configuration to Disk

You can export Specops Deploy / App settings from a GPO and save the exported information in the file system using the Migration Tool. This option should be used as a way to backup the content of a GPO or if the destination GPO cannot be reached from the current environment. The exported data can be moved to a disk and used in the environment where the data is to be imported.

  1. Open the Specops Deploy Migration Tool.
  2. Click Export GPO Configuration to Disk.
  3. From the Domain drop-down, select the domain that contains the source Group Policy.
  4. From the Group Policy Object drop-down, select the GPO with the settings you want to export.
  5. You will be given the option to selected what is included from the source GPO:
  • Include all deployment settings from the GPO: Select this option if you want to include all of the GPO content. If any issues are detected, such as missing setup files, it will be included on the following page.
  • Select which deployments, packages, etc to include: Select this option if you want to only include part of the GPO content. You will be asked to specify which deployments, packages, and targets to include in the proceeding pages of the wizard.
  • Include the setup files: Select this option if you want to move or copy the setup files (MSI files) from their current network shares to a new location. This may be necessary if copying/moving from one domain to another. Do not select this option if the same source files, from the same network shares, are to be used from the destination GPO.
  1. If Select which deployments, packages, etc to include is selected, you will need to complete the below steps. Otherwise, skip to step 7.
    • Select the deployments you want to include.
    • Select the package you want to include. Selected deployments from the previous page will have their corresponding package selected and cannot be changed.
    • Select the targets you want to include. Selected deployments from the previous page will have their corresponding targets selected and cannot be changed.
  2. Select the directory where the exported data should be saved, and click Next.
  3. A message will appear. You will be required to click Yes to continue the export.
  4. Click Finish.
Import GPO configuration from Disk

You can import Specops Deploy / App data from disk using the Migration Tool. The data to be imported must first be created by the export wizard.

To proceed with this task, you must have:

  • Write permission in the destination GPO.
  1. Open the Specops Deploy Migration Tool.
  2. Click Import GPO Configuration from Disk.
  3. Enter the path to the exported configuration that you want to import.
  4. From the Domain drop-down, select the domain that contains the destination Group Policy.
  5. From the Group Policy Object drop-down, select the GPO you want to import the settings into. A GPO that already contains Specops Deploy settings (marked with the Specops icon) can be selected, along with those that do not. You will need to have permission to update the selected GPO.
  6. A list containing all root paths of the packages being imported will be displayed. You may need to take the appropriate action, if:
  • The settings are copied or moved from one domain to another: You may need to update the root paths where the setup files are located.
  • The import includes the setup files and you do not have write permissions to the new share: you will need to supply a corresponding path where you have write permissions.
  • The share path is, for example \\Server1\Software: You may be able to use \\server1\c$\Software as a corresponding writable path.
  1. Click Next.
  2. Verify that the required data for the import has been collected, and click Next.
  3. A message will appear. You will be required to click Yes to continue the import.
  4. Click Finish.