Citrix

Produktdokumentation



Ganzes Dokument herunterladen

Key Terms

Mar. 28, 2017

This topic provides brief definitions of some key terms used in AppDNA topics related to Active Directory (AD) and Microsoft System Center Configuration Manager. If a term (such as group) has different meanings in AD and Configuration Manager compared to AppDNA, it is prefixed with AD or Configuration Manager to distinguish it from the AppDNA term.

Key AppDNA integration terms

managed application
An application that is deployed through Active Directory or Configuration Manager. Once loaded into AppDNA, all managed applications are handled in a standard way, regardless of how they are deployed. In some screens, managed applications are referred to as packages (even if they are deployed using Configuration Manager).
installation
Represents an installation mechanism used to deploy an application through Active Directory or Configuration Manager. For applications that are deployed through the legacy Configuration Manager package and program mechanism, an installation represents a Configuration Manager program. Typically applications that are deployed in this way have multiple installations. For applications that are deployed through the new Configuration Manager 2012 application mechanism, an installation corresponds to a deployment type.

Active Directory terms

Active Directory
A directory service from Microsoft, which provides a central location for network administration and security, single sign-on for user access to networked resources, standardization of access to application data, deployment and update of applications, and synchronization of directory updates across servers. All of the information and deployment settings are stored in a central database.
organizational unit (OU)
A container for users, computers, and groups in Active Directory. Every user, computer, and group is located in one specific OU. The Active Directory is organized into a hierarchical tree of OUs. There is flexibility in how the OU tree is structured – some organizations structure it by function, others by geographical location, for example.
Group Policy Object (GPO)
A collection of policies that apply to selected Active Directory users or computers. GPOs are linked to OUs and targeted at users and computers. Two conditions must be met in order for a GPO to apply to a particular user or computer. Firstly, the user or computer must belong to an OU or sub-OU to which the GPO is linked. Secondly, the user or computer must be directly targeted or belong to a group to which the GPO is targeted.
AD package
A particular type of GPO policy that is used to deploy software. It provides native support for MSI deployment.
AD group
Represents a collection of AD users and computers. Membership of a group is static – members are added to a group explicitly. Groups can be nested and members can belong to more than one group.
AD computer
Represents the domain account of a computer joined to a Windows domain. This might be a physical or virtual machine or a dummy account that is used for authentication purposes.
AD user
Represents the logon account of a user who can log onto a Windows domain – some users represent real people and others represent service accounts and email recipients.

Configuration Manager terms

System Center Configuration Manager
A Microsoft systems management tool for managing large groups of Windows-based computer systems. Configuration Manager provides remote control, patch management, software distribution, operating system deployment, network access protection, and hardware and software inventory. Like Active Directory, all of the information and deployment settings are stored in a central database.
Configuration Manager collection
Represents a collection of Configuration Manager computers and Configuration Manager users. In Configuration Manager 2007 and earlier, collections can be nested. However, this is not possible in Configuration Manager 2012. Membership of Configuration Manager collections is pseudo-dynamic – members can be added explicitly. However, rules can also be defined which determine which users and computers to include in the collection. The collection is refreshed on a schedule but not each time the collection is queried.
Configuration Manager computer
Represents the domain account of a computer joined to a Windows domain. This might be a physical or virtual machine or a dummy account that is used for authentication purposes.
deployment type
Contained in a Configuration Manager application, this stores the information that is required to install the application, and rules that specify when and how it is deployed. A Configuration Manager application must have at least one deployment type. Within AppDNA, deployment types are referred to as installations.
Configuration Manager package
Represents a folder that contains files. Configuration Manager tracks packages as they are replicated between sites.
Configuration Manager program
Represents an operation that is performed on, or with, the files contained within a Configuration Manager package, such as install or uninstall. Within AppDNA, Configuration Manager programs are referred to as installations.
Configuration Manager application
Represents an application that is deployed and managed through the Configuration Manager 2012 application model.
Configuration Manager user
Represents a user within the enterprise. Typically Configuration Manager discovers users through interrogating Active Directory.

Discovery terms

SysTrack
A suite of IT business intelligence products from Lakeside Software. SysTrack includes functionality that audits and tracks application use within the enterprise. AppDNA uses the results of this tracking in the Discover Applications screen.
discovered applications
Applications whose usage has been tracked by SysTrack across the organization. Discovered applications are listed on the Discover Applications screen.

Other AppDNA terms

group
A logical container for applications in AppDNA. Groups are similar to folders in Windows Explorer – they provide a way of structuring your application portfolio by user group, location, or application type, for example. Groups make it easy to review and report on the applications in the group separately from the rest of the portfolio. A group does not have an overall RAG status and it is not shown as a separate item in reports.

See also

For a more complete glossary of AppDNA terms, see AppDNA glossary.

Back to Top