Product Documentation

Extract Data from ConfigMgr

Jun 15, 2016

This topic provides step-by-step instructions for running the stand-alone AppDNA AD and ConfigMgr Data Extraction Tool to extract data from Configuration Manager for loading into AppDNA.

This topic assumes that you have received the ADConfigMgrExportTool.zip package from the AppDNA administrator and that you have stored it in a suitable location in your file system.

Important: The package also contains the synchronization data that is used to identify the latest changes to the Configuration Manager data. You therefore need a fresh package every time you extract Configuration Manager data from one or more sites. If necessary, contact the AppDNA administrator to request a fresh package.
  1. In Windows Explorer, locate the ADConfigMgrExportTool.zip package.
  2. Right-click the ADConfigMgrExportTool.zip package, and from the shortcut menu, choose Extract All.
  3. In the Extract Compressed (Zipped) Folders dialog box, select a suitable location, and then click Extract.
  4. When the extraction is complete, in Windows Explorer navigate to the folder that contains the extracted files.
  5. Double-click the ADSCCMExportTool.exe file.

    This starts the wizard.

  6. In the Source Selection step in the wizard, choose System Center Configuration Manager (ConfigMgr), and then click Next.
  7. In the ConfigMgr Connection Details step, enter the details as follows:
    Option Description
    Server Enter the Configuration Manager server hostname or IP address.
    Site Enter the Configuration Manager Site Code. If you want to extract data from multiple sites, you need to run through the wizard for each site.
    Username If you are running this tool on the Configuration Manager server, leave this blank. Otherwise, either leave this blank to use the credentials of the logged on Windows user or specify a user name to use to connect to the Configuration Manager server. Typically this is a domain-qualified user name of the form: domain\username.
    Password If you entered a user name, specify its password here.
  8. Click Next.
  9. In the Extraction Mode step, select one of the following options:
    Option Description
    Standard Select this option if you want to automatically extract all of the relevant Configuration Manager changes since the last data extraction.
    Advanced Select this option if you want to manually select the Configuration Manager packages and applications to extract. Use this option the first time data is extracted from a large Configuration Manager site – that is, a site that has a total of more than 5,000 packages and applications, and/or more than 50,000 users or computers. Then extract the applications and/or packages in batches of, for example, 1,000 applications and 1,000 packages.
  10. Click Next.
  11. If you chose the Advanced option, in the Advanced Selection step, select the packages, applications, or both packages and applications, that you want to extract for loading into AppDNA (see ConfigMgr Advanced Selection for more on this step). Citrix recommends that you select no more than a total of 2,000 applications and packages. Then click Next.

    (This step does not appear if you chose Standard in the Extraction Mode step.)

  12. Check the details in the Summary step, and then click Next.
  13. In the Save As dialog box, enter a suitable name and location for the extracted data, and then click Save.
    Note: Ensure the file has an .sgz filename extension.

    The wizard then starts extracting the data and displays information that provides an indication of the progress. Depending on how much data you are extracting, this process can take a considerable amount of time (several hours, for example).

  14. When the Progress step shows that the operation is complete, click Finish.
  15. If you want to extract another batch of data, or data from another Configuration Manager site, repeat steps 5 to 14 for the next site.

You now need to send the (.sgz) file or files containing the extracted data to the AppDNA administrator for loading into AppDNA.