|
|||
1. Introduction to the Automated Installer 2. Automated Installer Task Map 3. Automated Installer Setup Instructions 4. How to Administer an Automated Install Server 5. How to Administer a Custom Install Client 6. How to Administer the Manifest Files for an Install Service How to Create New AI Manifests How to Create Custom SC Manifest Files How to Customize Client Installations Using Manifests 7. How to Manage Client Installations |
How to Assign Manifests to a ClientIf you want to create new AI manifests and SC manifests, you need to assign the manifests for use with a particular client. Use the following basic procedure:
Criteria Manifest ExamplesThe following examples show options for creating a criteria manifest. Each example below is a complete criteria manifest. Criteria Based on the Client IP AddressYou can use this example as the first draft of a new criteria manifest. Use the other examples to modify your draft. The following example assigns ai_manifest1 and sc_manifest1 to the client with IP address, 10.6.68.127. <ai_criteria_manifest> <ai_criteria name="IPV4"> <value>10.6.68.127</value> </ai_criteria> <ai_manifest_file URI="./ai_manifest1.xml"/> <sc_manifest_file name="AI" URI="./sc_manifest1.xml"/> </ai_criteria_manifest> Note - In criteria manifests, include the full path for any manifest file names that are referenced. In the examples in this section, the referenced manifest files reside in the current directory. The path for a manifest file in the current directory uses the format, ./ai_manifest1.xml. Criteria Based on the Client MAC AddressThe following example assigns ai_manifest1 and sc_manifest1 to the client with MAC address 0:14:4f:20:53:94. <ai_criteria_manifest> <ai_criteria name="MAC"> <value>0:14:4F:20:53:94</value> </ai_criteria> <ai_manifest_file URI="./ai_manifest1.xml"/> <sc_manifest_file name="AI" URI="./sc_manifest1.xml"/> </ai_criteria_manifest> Criteria Based on the Client IP Address RangeThe following example assigns ai_manifest1 and sc_manifest1 to clients in the IP address range, 10.6.68.1 to 10.6.68.200. Since there is more than 1 value, the tag, <range>, should be used. <ai_criteria_manifest> <ai_criteria name="IPV4"> <range> 10.6.88.1 10.6.68.200 </range> </ai_criteria> <ai_manifest_file URI="./ai_manifest1.xml"/> <sc_manifest_file name="AI" URI="./sc_manifest1.xml"/> </ai_criteria_manifest> Criteria Based on the Client MAC Address RangeThe following example assigns ai_manifest1 and sc_manifest1 to clients in the MAC address range, 0:14:4F:20:53:94 to 0:14:4F:20:53:A0. Since there is more than 1 value, the tag, <range>, should be used. <ai_criteria_manifest> <ai_criteria name="MAC"> <range> 0:14:4F:20:53:94 0:14:4F:20:53:A0 </range> </ai_criteria> <ai_manifest_file URI="./ai_manifest1.xml"/> <sc_manifest_file name="AI" URI="./sc_manifest1.xml"/> </ai_criteria_manifest> Criteria Based on the Client Memory SizeThe following example assigns ai_manifest1 and sc_manifest1 to clients that have at least 2 Gbytes memory. The None keyword is used to express no bounding value. The value in the <range> tag is expressed in megabytes, in this case, 2048 MB. <ai_criteria_manifest> <ai_criteria name="MEM"> <range> 2048 unbounded </range> </ai_criteria> <ai_manifest_file URI="./ai_manifest1.xml"/> <sc_manifest_file name="AI" URI="./sc_manifest1.xml"/> </ai_criteria_manifest> Criteria Based on the Client ArchitectureThe following example assigns ai_manifest1 and sc_manifest1 to clients with an architecture of i86pc. <ai_criteria_manifest> <ai_criteria name="ARCH"> <value>i86pc</value> </ai_criteria> <ai_manifest_file URI="./ai_manifest1.xml"/> <sc_manifest_file name="AI" URI="./sc_manifest1.xml"/> </ai_criteria_manifest> |
||
|