Windows Server Group Policy automated-program installation requires client computers that are running Microsoft Windows or a later version. To publish or assign a computer program, create a distribution point on the publishing server by following these steps:. To assign a program to computers that are running Windows Server , Windows , or Windows XP Professional, or to users who are logging on to one of these workstations, follow these steps:.
Click the Group Policy tab, select the policy that you want, and then click Edit. Right-click Software installation , point to New , and then click Package. Don't use the Browse button to access the location.
Make sure that you use the UNC path of the shared installer package. Click Assigned , and then click OK. The package is listed in the right-pane of the Group Policy window. To publish a package to computer users and make it available for installation from the Add or Remove Programs list in Control Panel, follow these steps:. Click the Group Policy tab, click the policy that you want, and then click Edit.
In the Open dialog box, type the full UNC path of the shared installer package that you want. Because there are several versions of Windows, the following steps may be different on your computer. If they are, see your product documentation to complete these steps. In some cases, you may want to redeploy a software package for example, if you upgrade or change the package. This is document akck in the Knowledge Base.
Last modified on Skip to: content search login. Knowledge Base Toggle local menu Menus About the team. Knowledge Base Search.
Log in. Options Help Chat with a consultant. The client installation properties are used to install the client. These properties might be overwritten with new settings from its assigned site after the client is installed and has successfully been assigned to a Configuration Manager site. Use the details in the following sections to determine which Configuration Manager client installation methods use Active Directory Domain Services to obtain client installation properties.
Client push installation does not use Active Directory Domain Services to obtain installation properties. Instead, you can specify client installation properties in the Installation Properties tab of the Client Push Installation Properties dialog box. These options and client-related site settings are stored in a file that the client reads during client installation. You do not have to specify any CCMSetup properties for client push installation, or the fallback status point, or the trusted root key in the Installation Properties tab.
These settings are automatically supplied to clients when they are installed by using client push installation. In addition to Client. These settings are read by client installations where CCMSetup is run with no installation properties. The software update point-based installation method does not support the addition of installation properties to the CCMSetup command line.
The Group Policy installation method does not support the addition of installation properties to the CCMSetup command line. If no command line properties have been provisioned on the client computer, CCMSetup searches Active Directory Domain Services for installation properties.
These client computers cannot read or access the published installation properties from Active Directory Domain Services.
0コメント