If you want to create a dependency for any SCCM applications that have dependent packages, select them and then select SCCM > Apply SCCM Dependency. The dependencies appear in the Dependencies tab on the far right of the screen.
To add an application that the current application depends on, click Manage Links in the top section:
Some applications could create circular dependencies, and are therefore read-only, and displayed in pink.
Select the appropriate Dependency Type for each newly added application: Prerequisite, Functional or Middleware and then click Save.
In addition, in the main grid, the Is Dep column will be checked for any application that has a dependency, and the Has Dep column will be checked for any application that is dependent on other applications. If these columns are not visible, right click any column header and choose Show Column Chooser.
Click Save to save your changes, or Revert to leave the Manage Links mode without saving your changes.
You can add applications that depend on the current application in the same way - by clicking Manage Links in the bottom section of the Dependencies tab.
If you double-click on any application in the right-hand panel, the focus is set to that application, and the dependencies are recalculated. This lets you create a dependency hierarchy or tree.
Let us suppose that you have a number of geographical divisions or reporting groups (EMEA, North America, etc.) with a number of departments, or subgroups, within those divisions (Finance, Marketing, etc.). ChangeBASE allows you to set up this structure and associate applications with the reporting subgroups.
You may also have a number of product groups or families ('Adobe Reader', 'Microsoft Office', etc.) by which you wish to group your applications (MS Word and MW Excel into 'Microsoft Office', etc). ChangeBASE allows you to set up these families and associate applications with them.
Note: To create a report showing applications with their Reporting Subgroups, refer to Creating Custom Reports.
You need at least one subgroup per reporting group.
To create reporting groups with subgroups
Click Save to save your changes, or Revert to leave the Manage Groups mode without saving your changes.
To link applications to reporting subgroups
Click Manage Links at the top of the Reporting Groups window.
Select the subgroup(s) to which the application(s) is/are to be linked, and then click Save.
To create a product group
To link an application to a product group
Select the required Product Group to which you want to add applications, and press Add.
In each group, at least one of the applications must be the Primary Application. Check it as such in the Primary Application column.
Legacy application files (for example, EXEs) are not assessed - they are given a neutral (grey) RAG status. You can repackage them selectively using Convert > Repackage at the top of the screen. Refer to The Repackaging Process.
You can also initiate the Virtualization of any of the MSIs or EXEs via Convert > Virtualize at the top of the screen. Refer to The Virtualization Process.
The Checks window provides you with a detailed view of the issues that have been generated following import, grouping the issues by assessment group under the different platforms created via Platform Setup. It allows you to apply automatic fixes to those Amber and Red issues that can be remediated.
The Next Steps tab on the right at the bottom of the screen provides more detailed guidance.
You select the required platform tab at the top of the display, and then, within the left hand panel, the type of checks that you want to fix or investigate. All the individual issues relating to those checks are displayed in the right hand panel, with the details of selected issues displayed at the bottom of the panel.
Where there are multiple platforms under a platform tab, each individual platform has a '3-state' check box at the top:
For details, see: