getting started with user-centric management in ... web viewgetting started with user-centric...

Getting Started with User-Centric Management in Configuration Manager v.NextPublished: June 2010

Send suggestions and comments about this document to [email protected]. Please include the name of the document with your feedback.

mailto:[email protected]

This document is provided “as-is”. Information and views expressed in this document, including URL and other Internet Web site references, may change without notice. You bear the risk of using it.

Some examples depicted herein are provided for illustration only and are fictitious. No real association or connection is intended or should be inferred.

This document does not provide you with any legal rights to any intellectual property in any Microsoft product. You may copy and use this document for your internal, reference purposes. You may modify this document for your internal, reference purposes.

© 2010 Microsoft Corporation. All rights reserved.

Microsoft, Access, Active Directory, ActiveSync, ActiveX, Authenticode, BitLocker, Excel, Hyper-V, Internet Explorer, JScript, Microsoft Press, MSDN, Outlook, SharePoint, SoftGrid, SQL Server, Visio, Visual Basic, Visual C++, Visual Studio, Win32, Windows, Windows Mobile, Windows Server System, and Windows Vista are trademarks of the Microsoft group of companies.

All other trademarks are property of their respective owners.

Revision History

Release Date Changes

May 2010 First publication.

June 2010 Updated the “Deployment Purpose” section to further explain the differences in behavior for the Available and Required deployment purpose.

ContentsGetting Started with User-Centric Management in Configuration Manager v.Next.........................4

In This Section............................................................................................................................. 4

Introduction..................................................................................................................................... 4

Terminology.................................................................................................................................... 5

Concepts......................................................................................................................................... 7Applications in Configuration Manager v.Next.............................................................................7

Deployment Types in Configuration Manager v.Next................................................................8Requirement Rules and Global Conditions..............................................................................8User Device Affinity.................................................................................................................. 9Deployments..........................................................................................................................10Deployment Purpose..............................................................................................................10Monitoring Deployments........................................................................................................10Using Packages and Programs with Configuration Manager v.Next.......................................11The User Experience and Configuration Manager v.Next Application Management..............12

Planning........................................................................................................................................ 13

Example........................................................................................................................................ 15

Appendices................................................................................................................................... 17

Frequently Asked Questions for User-Centric Management in Configuration Manager v.Next.....17

Terminology Differences between Configuration Manager v.Next User-Centric Management......20

This is pre-release documentation and is subject to change in future releases.

Getting Started with User-Centric Management in Configuration Manager v.Next

In This SectionIntroduction

Terminology

Concepts

Planning

Example

Appendices

IntroductionUser-centric management in Configuration Manager v.Next provides Configuration Manager administrative users and users of Configuration Manager client devices with tools to manage applications in the enterprise. Unlike previous versions of the product, Configuration Manager v.Next is built around user-centric principles. This means that the product is designed to meet the needs of administrative users and users of client devices rather than forcing them to modify their processes to suit the product. For example, Configuration Manager v.Next allows you to associate users with devices, so instead of having to remember the name of a user’s device, you can now distribute software to the user as well as to the device. Applications can also be distributed based on the user’s needs without the user needing to intervene. For example, on a computer a user works on every day, you might install a local copy of a software package. On a computer a user works on occasionally, you might deploy a virtual copy of the software package that is then removed when the user logs off. Additionally, in Configuration Manager v.Next, users are given much more control over what software is installed on their devices and when it gets installed.

A device in Configuration Manager v.Next refers to a computer or a mobile device, such as a Windows phone.

Benefits for administrative users include the following:

Software deployments can target users or groups of users and devices.

Important

4


A relationship between a user and the devices on which they most often work can be established to ensure that critical software is always available on users’ devices.

If a user gets a new computer, it can be configured automatically with their applications and settings. If a relationship has been established between the user and the computer, the user does not have to be logged in to receive these applications and settings.

Administrative users can control the deployment of applications to computers based on rules. For example, an administrative user could specify that an application can only be installed on computers with more than 2 GB RAM. Any computer that does not meet this requirement will not install the application. Configuration Manager v.Next contains a set of built-in rules. You can also define custom rules.

Users can request their software, and administrators can approve or deny those requests.

An administrative user can specify a deployment purpose for an application. This controls whether the application is required or optional. The state of the deployment is periodically monitored, so, for instance, if an application has a deployment purpose of Required and is later removed, Configuration Manager will reinstall the application. You can also change the deployment purpose of an application.

Benefits to the user include the following:

A new client interface, Software Center, provides a user-friendly interface that allows the user of a client computer to perform common administrative tasks.

A self-service application Web site, the Software Catalog, allows users to search for and request applications.

Users can configure when software and updates are installed by specifying their own work hours.

This guide is an introduction to the new features of application management in Configuration Manager v.Next.

TerminologyThis section lists the main terms used in user-centric management in Configuration Manager v.Next.

Term Definition

application approval An additional action that is required after an end user requests an application and before the application becomes available to install.

Software Catalog The Configuration Manager Web-based view of the applications that are available for a user to search, browse, request, and install.

5


Term Definition

Software Center The Configuration Manager Software Center allows a user to set preferences for how their software is installed. End users can also use Software Center to request, install, remove, and monitor the software that is deployed by using Configuration Manager v.Next.

deployment purpose An action that is associated with the deployment of software, such as Available and Required.

deployment type A technology that is used to deploy an application to devices. A deployment type is contained within an application. For example, Visio 2007 MSI could be a deployment type for the Visio 2007 application.

global conditions A setting that allows an administrative user to define rules that specify if or when an application is installed on client devices. Global conditions can be used by multiple deployment types. They can also be used throughout the hierarchy.

See also: requirement rules

primary device A device that is used most often by a user. A user can have more than one primary device.

primary user The main user of a device. A device can have more than one primary user.

requirement rules A setting that allows an administrative user to define rules for a single deployment type that specifies how the application is provided and installed on client devices.

See also: global conditions

software A collective term for all of the following: software updates, applications, scripts, task sequences, device drivers, configuration items, and configuration baselines.

Software Catalog Web service point A Configuration Manager site system role that provides software information from the Software Library to the Software Catalog Web

6


Term Definition

site.

Software Catalog Web site point A Configuration Manager site system role that provides users with a list of available software.

Software Library The administrator repository that holds software so that it can be deployed by using Configuration Manager v.Next.

user device affinity The mapping of a user to a device, which enables deployment conditions and simplifies the complexity of the deployment.

ConceptsUser-centric management in Configuration Manager v.Next introduces new terms and concepts you must understand before you can begin to deploy applications. This section introduces many of these concepts.

Applications in Configuration Manager v.NextAn application in Configuration Manager v.Next contains the files and information necessary to deploy a software package to a computer or mobile device and the information about the software shared by all deployment types. Applications are similar to packages in Configuration Manager 2007, but contain more information to support smart deployment. An application can contain a range of information about a software installation, including the following:

Information shared by all deployment types, such as the application name, manufacturer, and version number, as well as a description of the application as it will appear to users. This information can be displayed in the Software Catalog in different languages based on client settings.

Contact names of users who can supply information and provide support for the application.

One or more deployment types, which contain information about methods used to install or uninstall the application and the location of files required by the application.

Keywords and categories to help users search for items in the Software Catalog.

When you make changes to an application, a new revision of the application is created. Previous versions of the application are stored and can be retrieved at a later time.

You can also import and export applications from Configuration Manager to a file. This allows you to make a backup of an application independently from Configuration Manager or to move applications to another Configuration Manager v.Next site.

7


Applications are configured with the Create Application Wizard in the Software Library from the Configuration Manager console.

Deployment Types in Configuration Manager v.NextA deployment type is contained within an application and contains details about the files, commands, and programs used to install software. It also contains rules that specify if and how the software is deployed. Deployments types are similar to programs in Configuration Manager 2007. An application can contain multiple deployment types that each installs a package by using a different method. A single application can have multiple deployment types that use the same technology, for example a single application might have multiple Windows Installer (.MSI) deployment types. The following deployment types are available in Configuration Manager v.Next:

Windows Installer – Creates a deployment type from a Windows Installer (MSI) file. Configuration Manager can retrieve information from the MSI file to automatically populate some fields of the Create Deployment Type Wizard.

Script Installer – Creates a deployment type that specifies a script that will run on client devices to install content or to perform an action.

Microsoft Application Virtualization – Creates a deployment type from a Microsoft Application Virtualization manifest. Configuration Manager can retrieve information from the manifest file to automatically populate some fields of the Create Deployment Type Wizard.

Windows Mobile Cabinet – Creates a deployment type from a Windows Mobile Cabinet (CAB) file. Configuration Manager can retrieve information from the CAB file to automatically populate some fields of the Create Deployment Type Wizard.

A typical deployment type contains the following information:

General information about the deployment type, which will be displayed to users in the Software Catalog.

The installation method used by the deployment type, such as the installation program or installation content location.

The required installation command line.

The required uninstall command line.

Requirement rules that must be met for the deployment type to install.

Dependencies that are additional deployment types that this deployment type requires.

Deployment types are configured with the Create Deployment Type Wizard in the Software Library from the Configuration Manager console.

Requirement Rules and Global ConditionsRequirement rules allow administrative users to define one or more rules that represent business or technical conditions that specify how an application is provided and deployed on client devices.

The following are examples of requirement rules:

Do not install this MSI deployment type on computers with less than 2 GB RAM.

8


Only deploy this virtual application deployment type to a user’s primary device.

Do not install this application deployment type if the client computer has less than 500 MB free disk space.

Requirement rules are evaluated by the Configuration Manager v.Next client to determine the correct deployment type that will be used to install an application. The rules are re-evaluated (by default, every seven days) to ensure compliance. The administrative user can define a custom evaluation period.

You can define requirement rules that are used by a single deployment type, or you can define global conditions that are available to use with any deployment type.

Requirement rules are configured by using the Deployment Type tab of the application properties or the Deployment Type page of the Create Deployment Type Wizard in the Software Library.

Global conditions are configured by using the Global Condition dialog box in the Software Library from the Configuration Manager console.

User Device AffinityUser device affinity is a method of associating a user with specified devices. This can remove the requirement to know the names of a user’s devices when you deploy applications. You can define primary devices that are typically the device that a user uses on a daily basis to perform their work. When you create an affinity between a user and a device, this provides further options for deploying software. For example, if a user requires Microsoft Office Visio, you can install it on the user’s primary device by using a Windows Installer deployment. However, on a nonprimary device, you might deploy Microsoft Office Visio as an App-V virtual application. You can also use user device affinity to pre-deploy software on a user’s device when the user is not logged in.

User device affinity can be defined by using any of the following methods:

The user specifies that the device is a primary device in the Software Catalog.

A file is imported containing a list of users and devices.

The site can be configured to automatically create user device affinities based on collected usage statistics. The administrator can then approve the detected user device affinity.

An administrative user can manually create affinities.

During mobile device enrollment, a mobile device is associated with the user who enrolls it.

User device affinity can include the following:

A single user to a single device.

Many users to a single device.

A single user to many devices.

User device affinities are managed in Assets and Compliance from the Configuration Manager console.

9


DeploymentsDeployments in Configuration Manager v.Next are used to distribute applications to devices in your organization. The Deploy Software Wizard allows you to specify information about the application, including the following:

The name of the application.

The Configuration Manager collection to which you want to deploy the application.

The distribution points or distribution point groups that will host the content associated with the application.

The purpose of the deployment; for example, whether installation is Required or Available.

Scheduling information for the deployment.

The client notification and restart settings for the deployment.

Monitoring and System Center Operations Manager alert settings for the deployment.

The Deploy Software Wizard can also be used to deploy imported Configuration Manager 2007 packages.

The Deploy Software Wizard in Configuration Manager v.Next replaces the New Advertisement Wizard in Configuration Manager 2007.

Deployment PurposeWhen you deploy an application in Configuration Manager v.Next, you can choose settings that define what the deployment should do and that represent the administrator’s intent. The available settings are as follows:

Available – If the application is deployed to a user, the user sees the published application in the Software Catalog and can request it on demand. If the application is deployed to a device, the user will see it in the Software Center and can install it on demand.

Required – The application is deployed automatically, according to the configured schedule. However, a user can track the application deployment status and install the application before the deadline by using the Software Center.

When you specify the purpose of a user-targeted deployment, you can specify whether users need to request approval from an administrative user before they can install the application.

The purpose of a deployment is specified by using the Deploy Software Wizard in the Software Library from the Configuration Manager console.

Monitoring DeploymentsUnlike Configuration Manager 2007, which used the separate Status Message Viewer to track the installation of software, in Configuration Manager v.Next, you can monitor the deployment of all software (software updates, compliance settings, applications, task sequences, packages and programs) by using the Monitoring navigation button in the Configuration Manager console.

Note

10


In Configuration Manager v.Next Beta 1, monitoring is limited to applications, packages and programs.

Applications in Configuration Manager v.Next support state-based monitoring, which allows you to track the last application deployment state for users and devices. These state messages display information about individual devices. For example, if an application is deployed to a collection of users, you can view the compliance state of the deployment and the deployment purpose in the Configuration Manager console.

An application deployment state has one of the following compliance states:

Success – The application deployment succeeded.

In Progress – The application deployment is in progress.

Unknown – The state of the application deployment could not be determined.

Requirements Not Met – The application was not deployed because it was not compliant with a dependency or a requirement rule.

Error – The application failed to deploy because of an error.

You can view additional information for each compliance state, which includes subcategories within the compliance state and the number of users and devices in this category. For example, the Error compliance state contains three subcategories:

Error evaluating policy

Content related errors

Installation Errors

When more than one compliance state applies for an application deployment to a user that has more than one device, you will see the aggregate state that represents the lowest compliance. For example, if a user logs in to two devices and the application is successfully installed on one device but fails to install on the second device, the aggregate deployment state of the application for that user displays as Error.

Use these subcategories to help you to quickly identify any important issues with an application deployment. You can also view additional information about which devices fall into a particular subcategory of a compliance state.

To monitor the status of deployments in Configuration Manager v.Next, click Monitoring in the navigation pane, and then click Deployments.

Using Packages and Programs with Configuration Manager v.NextConfiguration Manager v.Next continues to support packages and programs that were used in Configuration Manager 2007. A deployment that uses packages and programs might be more suitable than using an application when deploying any of the following:

Scripts that do not install an application on a computer (such as a script to defragment the computer disk drive).

Note

11


“One-off” scripts that do not need to be continually monitored.

Scripts that run on a recurring schedule and cannot use global evaluation.

When you migrate a Configuration Manager 2007 site to a Configuration Manager v.Next hierarchy, you can migrate existing packages and deploy them in your Configuration Manager v.Next hierarchy. After migration is complete, your Configuration Manager 2007 packages appear in the Packages node in the Software Library. You can modify and deploy these packages in the same way as you did by using Configuration Manager 2007 software distribution. The Import Package from Definition Wizard remains in Configuration Manager v.Next for importing legacy packages. Advertisements are converted to deployments when migrated from Configuration Manager 2007 to a Configuration Manager v.Next hierarchy.

Packages can use some new features of Configuration Manager v.Next, including distribution point groups and the new monitoring functionality.

To deploy a package, right-click the package name, and then click Deploy.

Microsoft Application Virtualization applications can no longer be distributed by using packages and programs in Configuration Manager v.Next. To distribute virtual applications, you must create these as Configuration Manager v.Next applications.

To successfully create virtual applications in Configuration Manager v.Next, 64-bit client computers must have the App-V 4.6 or later client installed before the Configuration Manager client is upgraded.

The User Experience and Configuration Manager v.Next Application ManagementConfiguration Manager v.Next is designed to give the users of client devices more control over what software is installed and when it is installed. It also helps to ensure that the software that users need to perform their work is available wherever they log in, not just on their primary device.

Configuration Manager v.Next contains a new client interface, the Configuration Manager Software Center. Software Center allows users to manage their own software, including the following:

Install software.

View their software request history.

Configure when Configuration Manager can install software on their device.

Configure access settings for remote control, if remote control is enabled by an administrative user.

To enable the Software Catalog on client devices to let them browse for and request software and to let them share links with other users, you must configure two new site system roles on your site:

Note

12


Software Catalog Web service point – Provides software information from the Software Library to the Software Catalog Web site.

Software Catalog Web site point – Provides users with a list of available software.

The following Configuration Manager 2007 client functionality can be found in the following locations in Configuration Manager v.Next Software Center:

Configuration Manager 2007 Configuration Manager v.Next

Program Download Monitor in Control Panel Users can view and manage program download status on the Installation Status page of the Software Center.

Run Advertised Programs in Control Panel Users can view and install available software and schedule software installations from the Software Center.

The Configuration Manager client in Control Panel remains in Configuration Manager v.Next to help administrative users troubleshoot problems with the client software.

PlanningThe following steps provide an overview of the process used to create, deploy, and monitor an application in Configuration Manager v.Next.

Step More Information

1. Create an application. The Create Application Wizard helps you to create an application in Configuration Manager v.Next. You can use two methods to specify the information contained in the application:

Detect existing application settings – If the application is a Windows Installer (MSI) file, a Microsoft Application Virtualization (App-V) package, or a Windows Mobile Cabinet file, Configuration Manager can read many of the application settings automatically. If the information is available, it also creates a deployment type for this application. For existing content that is not one of the above types, use the manual configuration method.

13



Manually configure an application, specifying all settings yourself.

2. Create one or more deployment types. Although the Create Application Wizard helps you to create the first deployment type, you can add more deployment types after the application is created. For example, you can create an application virtualization deployment type for an application that already contains a Microsoft Installer deployment type.

To start the Create Deployment Type Wizard, right-click the application, and add a new deployment type. You can also modify deployment types from the <Application> Properties dialog box.

3. Add requirement rules to deployment types. Requirement rules specify the requirements the device and user must satisfy before the device can install a deployment type associated with an application. A variety of rules can be specified, for example:

The operating system on the destination device must be an x64 Windows 7 client.

The application can only be installed on a user’s primary device.

You can also create global conditions that are centrally stored rules applied to any deployment type.

Requirement rules are added to deployment types in the Create Deployment Type Wizard. You can add more requirement rules or edit existing requirement rules in the <deployment type> Properties dialog box.

4. Add dependencies to the application. Dependencies allow you to specify other application deployment types that must be installed before the deployment type can be installed. You can specify that any dependent applications in the deployment type must also be installed when this application is installed.

Dependencies are added to deployment types in the Create Deployment Type Wizard. You

14



can add more dependencies or edit existing dependencies in the <deployment type> Properties dialog box.

5. Distribute the application content. Specify the distribution points or distribution point groups that will host the application content.

6. Deploy the application. Specify general settings for the deployment, such as the collection to which you are deploying, whether to automatically install dependent applications, and a schedule for the deployment. When you deploy an application, you specify its purpose, such as whether it will be available through the Software Center or Software Catalog or whether it will be a mandatory installation on client computers.

7. Monitor the deployment. Selecting an application in the Configuration Manager console shows details of the application status in the main window.

You can also use the reports in Monitoring from the Configuration Manager console to see more detailed information about the status of the application.

ExampleThe following section provides an example scenario of how application management in Configuration Manager v.Next can be implemented to meet a typical business requirement:

Lisa Andrews works in the main office of A. Datum Corporation and uses a desktop computer to do her work. Lisa spends one day a week working in a remote office. When Lisa works in the remote office, she uses one of a shared pool of computers. Lisa frequently uses Microsoft Office Visio in her main office and at the remote office, so she needs this software to be available on multiple computers. However, company policy dictates that this application should not be permanently installed on computers in the remote office. Additionally, Lisa requires a computer that has at least 1 GB of RAM to be able to use her Visio files.

To meet this business requirement, John Woods, a Configuration Manager administrative user at A. Datum Corporation, takes the following course of action in the Configuration Manager console.

15



In Assets and Compliance, John creates a user device affinity between Lisa and her desktop computer in the main office.

The user device affinity identifies a primary device for Lisa, which allows the means to deploy different applications on this device to other devices.

In Software Library, John uses the Create Application Wizard to create an application for Microsoft Office Visio. To install this on Lisa’s primary device, he specifies the deployment type of Windows Installer (MSI).

The Windows Installer (MSI) deployment type automatically configures the application with the application name, the installation command line, and a deployment type that installs the MSI file. The deployment type is also configured with the location of the software content.

To provide the application on shared computers in the remote office, John creates a second deployment type of Microsoft Application Virtualization.

John uses the Create Deployment Type Wizard to specify the Microsoft Application Virtualization deployment type and he identifies the application manifest XML file for Visio. This configures the new deployment type and the location of its content.

John creates requirement rules to support the business requirements when deploying Visio.

The three requirement rules:

A requirement rule for the Microsoft Application Virtualization deployment type that requires that the computer has more than 1 GB of RAM.

A requirement rule for the Windows Installer deployment type to allow the deployment type to be installed only on primary devices.

A requirement rule for the Microsoft Application Virtualization deployment type to allow the deployment type to be installed only on computers that are not primary devices.

John distributes the application content. John selects the distribution points to host the application content.

John deploys the application. John uses the Deploy Software Wizard to deploy the application to a collection that contains the user resource, Lisa Andrews.

John monitors the application deployment. John selects the Microsoft Visio application and examines the deployment information

16



displayed. He sees that the application has been installed on Lisa’s main computer as a local Windows Installer file and deployed on the computer in the remote office by using Microsoft Application Virtualization.

As a result of this course of action, Lisa has access to Microsoft Visio, whether she is in her local office or working at one of the shared computers in the remote office. There is no need for her to ask or wait for Visio to be available on the shared computers, because the software deploys as a virtual application. The business requirement is met with a single application deployment that is targeted to a user.

AppendicesThe following sections provide additional information about user-centric management in Configuration Manager v.Next.

Frequently Asked Questions for User-Centric Management in Configuration Manager v.NextThe following table provides the answers to a number of frequently asked questions about user-centric management in Configuration Manager v.Next.

Question Answer

What is an “application” and why would I use it? Configuration Manager v.Next applications contain the administrative details and Software Catalog information necessary to deploy a software package or software update to a computer or mobile device.

What is a “deployment type” and why would I use one?

A deployment type is contained within an application and specifies the installation files and method that Configuration Manager will use to install the software. The deployment type contains rules and settings that control if and how the software is installed on client

17


Question Answer

computers.

What is the “deployment purpose” and why would I use this?

The deployment purpose defines what the deployment should do and represents the administrator’s intent. For example, an administrative user might require the installation of software on client computers or might just make the software available for users to install themselves. A global condition can be set to check regularly that required applications are installed and to reinstall them if they have been removed.

What is a global condition and how is it different from a deployment requirement?

Global conditions are conditions used by requirement rules. Requirement rules set a value for a deployment type for a global condition. For example, “operating system =” is a global condition; a requirement rule is “operating system = Win7.”

How do I make an application deployment optional rather than mandatory?

To make a deployment optional, configure the deployment purpose as Available in the applications deployment type. Available applications appear in the Software Catalog from which users can install them.

Can users request applications now? Yes. Users can browse a list of available software in the Software Catalog. Users can then request an application which, if approved, will be installed on their computer.

Why would I use a package and program to deploy software rather than a Configuration Manager v.Next application deployment?

Some scenarios, such as the deployment of a script that runs on a client computer but that does not install software, are more suited to using a package and program rather than a Configuration Manager v.Next application.

Can I deploy Office so that it installs locally on a user’s main workstation but is available to that user as a virtual application from any computer?

Yes. You can configure multiple deployment types for an application. Rules that specify which deployment type is run allows you to specify how the application is made available to the user.

Does Configuration Manager v.Next help identify which computers a user uses to support

Yes. Configuration Manager v.Next collects usage statistics from client devices that can be

18


Question Answer

the user device affinity feature? used to automatically define user device affinities or to help you manually create affinities.

Can I migrate my existing packages and programs from Configuration Manager 2007 to a Configuration Manager v.Next hierarchy?

Yes. You can see migrated packages and programs in the Packages node in the Software Library. You can also use the Import Package from Definition Wizard to import Configuration Manager 2007 Package Definition Files into your site.

When you use the term “software,” does it include scripts and drivers?

Yes. In Configuration Manager v.Next, the term “software” includes software updates, applications, scripts, task sequences, device drivers, configuration items, and configuration baselines.

When I see references to “devices” in Configuration Manager v.Next, does this mean mobile devices?

The term “device” in Configuration Manager v.Next applies to a computer or a mobile device such as a Windows Mobile Phone.

What does “state-based deployment” mean in reference to Configuration Manager v.Next?

Depending on the deployment purpose you have specified in the deployment type of an application, Configuration Manager v.Next can periodically check that the state of the application is the same as its purpose. For instance, if an application’s deployment type is specified as Required, Configuration Manager will reinstall the application if it has been removed. Only one deployment type can be created per application and collection pair.

I’ve heard a lot about “user-centric management” in Configuration Manager v.Next. Does this mean that we can only deploy software to users and not to computers?

No. Configuration Manager v.Next still allows you to deploy software to computers. By creating user device affinities, you now have more control over how software is deployed.

19


Terminology Differences between Configuration Manager v.Next User-Centric ManagementThe following table compares the terms that are used in Configuration Manager 2007 software distribution and in Configuration Manager v.Next application management.

Configuration Manager 2007 Configuration Manager v.Next

Package Application

Program Deployment type

Advertisement Deployment

Collection rules Requirement rules and global conditions

Run Advertised Programs Software Center

None User device affinity

Program Download Monitor Software Center

20

getting started with user-centric management in ... web viewgetting started with user-centric...

Documents