Failed to Login to Management Console

Description

This setting determines the machine names, also known as NetBIOS names, of the target machines; it also determines the name of the workgroup or the Active Directory domain to which the target machines will be added after the deployment.

Steps

  1. The preset is: The same name and membership as those of the machine in the master image
  2. By default, all deployed machines will have the same name as the machine in the master image. Alternatively, you can specify a name pattern for themachines.
  3. Specify whether the machine will be a member of a workgroup or an Active Directory domain. If you have selected the domain membership, specify the user name and password of a domain administrator.

Name patterns

A name pattern determines the names that the target machines will have after the deployment.
To specify a single name for all target machines, type that name in Machine name pattern. For example, type: DeployedMachine
To generate different names for the target machines, include either of the following wildcards or their combination.
{start}
Generates consecutive numbers starting with start. Each machine name will have its unique number.
For example, the pattern {1} generates the names 1, 2, 3, and so on up to the number of target machines. Similarly, the pattern {5} generates the names 5, 6,7, and so on.
It makes sense to use only one such wildcard in the pattern.
{start,count}
Generates count consecutive numbers starting with start.
For example, the pattern {1,5} generates the names 1, 2, 3, 4, and 5. Similarly, the pattern {8,5} generates the names 8, 9, 10, 11, and 12.
Make sure that the value of count is big enough. If the number of target machines exceeds count, deployment to the remaining machines will fail.
You can use two or more of these wildcards. See examples later in this section.
In the wildcards, the value of start must be 0 or greater. The value of count must be 1 or greater.
You can use the wildcards alone or accompany them with text, as in the following examples.

Examples

Machine{1}
This pattern generates the names Machine1, Machine2, …, MachineN, where N is the number of target machines.
Name{1,3}
This pattern generates the names Name1, Name2, and Name3.
{1,3}{1,4}
This pattern generates the names 11, 12, 13, 14; 21, 22, 23, 24; 31, 32, 33, and 34
{1,9}{0,10}
This pattern generates 90 names: 10, 11, 12, …, 19; 20, 21, 22, …, 29; …; 90, 91, 92, …, 99
Machine{2,3}{5,4}
This pattern generates the names Machine25, Machine26, Machine27, Machine28, Machine35, Machine36, Machine37, Machine38, Machine45,Machine46, Machine47, Machine48
Name{0}{0,10}
This pattern generates the names Name00, Name01, …, Name09, Name10, Name11, Name12, …, Name100, Name101, and so on. Each machine will have a unique name.
Considerations when using name patterns
Patterns are most effective when you need to easily create different names for the target machines, no matter which machine gets which name. If you need to specify a particular name for a particular machine, you may want to use an individual deployment setting for that machine instead.
There is no order in which the names from the pattern are assigned to the machines. The same machine may be assigned a different name the next time you perform deployment.

Imaging and Deployment Software trusted by