1. Working with NEXThink For SCCM

1.1. Summary

NEXThink for SCCM is composed of two features: NEXThink for SCCM and NEXThink SCCM Bridge.

NEXThink for SCCM is a MMC snap-in which allows monitoring systems and tracking advertisements in real-time. It runs alongside ConfigMgr, registering extensions in ConfigMgr which allow adding systems to the list of monitored systems and configuring advertisement trackings.

NEXThink SCCM Bridge is a helper application which allows creating and managing SCCM collections. It is registered upon installation into a new NEXThink Finder custom action. This makes creation/edition of SCCM collections based on investigation results possible via the custom actions context menu.

1.2. Installation

1. After receiving the setup program of NEXThink for SCCM from your NEXThink representative, execute it in your client computer by double-clicking on the MSI file (its name is nxsccm.msi). The welcome screen of the setup program is displayed. Click on Next.

   • 

2. The setup program now asks you to review and confirm your acceptance of the EULA (End User License Agreement). You can also print the EULA by clicking on the Print button. If you are satisfied with the EULA, select the checkbox "I accept the terms in the License Agreement" and click on Next.

   • 

3. The installer will now ask you what components of the product to install. Verify your choice then click on Next.

   • 

4. Once you are sure about your choice, click on Install to start the actual installation process.

   • 

5. After a few seconds, the setup is completed and NEXThink for SCCM is successfully installed. Click Finish to end the installation.

   • 

1.3. Topics

1. NEXThink For SCCM
2. Advertisement Tracking
3. NEXThink SCCMBridge

1.4. Minimum Version Requirements

NEXThink for SCCM requires an Engine with minimum version V4.0.1.2.

For NEXThink SCCM Bridge there is no specific Finder version requirement.

1.5. Known Issues

• Maximum number of sources that can be exported with NEXThink Bridge is set to 475 (this is a limitation set by SCCM).
  Workaround: Copy-Paste all the sources from the Finder and create a csv file that can be imported directly in SCCM.

• Due to the limitation in Windows cmd, user may get the following error message when exporting multiple sources with long names to SCCM : "Error execution custom action 'Export to SCCM...': The filename or extension is too long"
• Disconnecting engine when sourceview is being generated in the NEXThink for SCCM could sometimes cause the console to crash.