-
-
Adding target devices to the database
-
Using the Auto-Add Wizard
-
-
Setting the target device as the template for this collection
-
-
Deploying virtual desktops to VMs using the XenDesktop Setup Wizard
This content has been machine translated dynamically.
Dieser Inhalt ist eine maschinelle Übersetzung, die dynamisch erstellt wurde. (Haftungsausschluss)
Cet article a été traduit automatiquement de manière dynamique. (Clause de non responsabilité)
Este artículo lo ha traducido una máquina de forma dinámica. (Aviso legal)
此内容已经过机器动态翻译。 放弃
このコンテンツは動的に機械翻訳されています。免責事項
이 콘텐츠는 동적으로 기계 번역되었습니다. 책임 부인
Este texto foi traduzido automaticamente. (Aviso legal)
Questo contenuto è stato tradotto dinamicamente con traduzione automatica.(Esclusione di responsabilità))
This article has been machine translated.
Dieser Artikel wurde maschinell übersetzt. (Haftungsausschluss)
Ce article a été traduit automatiquement. (Clause de non responsabilité)
Este artículo ha sido traducido automáticamente. (Aviso legal)
この記事は機械翻訳されています.免責事項
이 기사는 기계 번역되었습니다.책임 부인
Este artigo foi traduzido automaticamente.(Aviso legal)
这篇文章已经过机器翻译.放弃
Questo articolo è stato tradotto automaticamente.(Esclusione di responsabilità))
Translation failed!
Using the Auto-Add Wizard
The Auto-Add Wizard automates the configuration of rules for automatically adding new target devices to the Provisioning Services database using the Auto-Add feature.
The Auto-Add Wizard can be started at the Farm, Site, Collection or Device level. When started at a level lower than Farm, the wizard uses that choice as the default choice. For example, if it is started on a particular target device, it will:
- Select the Site for that Device as the Default Site choice in the combo-box.
- Select the Collection for that Device as the Default Collection choice in the combo-box.
- Select that Device as the Template Device choice in the combo-box.
The wizard displays each page with choices pre-selected based on the location that the Auto-Add Wizard was started from.
A Farm Admininistrator has the ability to turn Auto-Add on or off and to select the default Site.
A Site Admininistrator only has the ability to select the default site if the current default site is a site in which that administrator is the Site Administrator. If the Site Administrator is not the Administrator of the currently selected default Site, then that administrator can only configure the sites they has access to.
To configure Auto-Add settings (the default collection of a site, template device for the default collection and target device naming rules):
-
On the Console, right-click on the farm, then select the Auto-Add wizard. The Welcome to the Auto-Add Wizard page appears.
-
Click Next. The Enable Auto-Add dialog appears.
Note: Only a farm administrator can change settings on this page.
-
Check the box next to Enable Auto-Add to enable this feature, then click Next. The Select Site page appears.
Note: Site administrators can only select sites to which they have permissions.
-
From the Site drop-down list, select the site where devices should be added, then select Next. The Select Collection page displays with the default collection selected.
-
Accept the default collection or select a different collection from the Collection drop-down list, then click Next. The Select Template Devices page appears.
-
Select the device to use as a template, so that new devices being added will inherit the existing target device’s basic property settings, then click Next.
-
To view the selected device’s properties, click Properties. A read-only dialog displays the selected device’s properties. Close the dialog after reviewing the properties.
-
Click Next. The Device Name page displays.
-
Enter a static prefix that helps identify all devices that are being added to this collection. For example: ‘Boston’ to indicate devices located in Boston.
Note: The prefix can be used in combination with the suffix, but is not required if a suffix is provided. The entire device name can have a maximum of 15 characters (the prefix length + number length + suffix length). For example, the following device names are considered valid:
- Boston000Floor2 (prefix, incrementing number length, and suffix provided; the maximum of 15 characters has been reached)
- Boston000 (no suffix is provided)
- 000Floor2 (no prefix is provided)
The prefix cannot end with a digit.
-
Enter the length of the incrementing number to associate with the devices being added to this collection. This number is incremented as each device is added. For example, if the number length is set to ‘3’, Provisioning Services starts naming at ‘001’ and stops naming or adding devices after the number reaches ‘999’.
Note: Enable the Zero fill option to automatically add the necessary number of preceeding zeros to a numbers length. For example, if the numbers length is set to ‘4’, than the first target device number would be assigned as ‘0001’.
The number length must have a minimum of three digits and a maximum of 9 digits.
-
Enter a static suffix that helps to identify all devices being added to this collection. For example: Boston001Floor2 might be helpful to indicate the floor where these devices reside.
The suffix can be used in combination with the prefix, but is not required if a prefix is provided.
The entire device name can have a maximum of 15 characters (the prefix length + number length + suffix length).
The suffix cannot start with a digit.
The prefix and suffix combination must be unique in each collection.
-
Click Next. The Finish dialog appears.
-
Review all Auto-Add wizard settings, then click Finish. Auto-Add is now configured.
Share
Share
In this article
This Preview product documentation is Citrix Confidential.
You agree to hold this documentation confidential pursuant to the terms of your Citrix Beta/Tech Preview Agreement.
The development, release and timing of any features or functionality described in the Preview documentation remains at our sole discretion and are subject to change without notice or consultation.
The documentation is for informational purposes only and is not a commitment, promise or legal obligation to deliver any material, code or functionality and should not be relied upon in making Citrix product purchase decisions.
If you do not agree, select Do Not Agree to exit.