- Extract Data from Active Directory
- Extract Data from ConfigMgr
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.
This starts the wizard.
|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.|
|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.|
(This step does not appear if you chose Standard in the Extraction Mode step.)
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).
You now need to send the (.sgz) file or files containing the extracted data to the AppDNA administrator for loading into AppDNA.