Skip to main content

Where to assign newly imaged machines new name?

Thread needs solution
Beginner
Posts: 2
Comments: 11

I don't seem to have the option anymore to state the name for the newly imaged machine. Was that moved? I can't find it for the life of me. As of right now, all machines can only have the name of the image computer. 

0 Users found this helpful
Forum Hero
Posts: 68
Comments: 8204

#1

http://www.acronis.com/en-us/support/documentation/ASD5/#13504.html  (has pictures too)

Machine name and membership

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.

The preset is: The same name and membership as those of the machine in the master image

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 the machines.

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.

Beginner
Posts: 2
Comments: 11

#2

For some reason I don't have all of the options anymore. This is all I see. (See attached screenshot)

Attachment Size
399868-135559.jpg 145.44 KB
Forum Hero
Posts: 68
Comments: 8204

#3

I don't have access to my console at the moment to verify I still have the option, but pretty sure I do.  I'll check tomorrow morning to be sure though.

What version are you running and/or did you recently upgrade?  

I'd recommend using the lastest 1666 beta for your installer.  However, if your install is currently missing features, you should probably remove the current install and run the Acronis cleanup tool for good measure - it's down below and works for snap deploy as well.  Then, reboot to update the registry and proceed with installing 1666 from the sticky section cleanly.  Don't forget to right-click and "run as administrator" even if logged in as admin already when you run the cleantool as well as the 1666 installer.

Hopefully a fresh install with the latest version will bring all options back for you.  The downside is you'll have to create a new template, but you can still use existing backup images to deploy. 

Beginner
Posts: 2
Comments: 11

#4

Thanks for the tips! The features were missing before I installed 1666. Which I did a few weeks ago as I was having the issues with newer laptops not being able to image. You actually helped me with that so thanks! 

Unfortunately I'm in a time crunch to get a lab installed by Christmas so for now I'm gonna just rename every computer, due to space I have to do these big AIOs one at a time anyway so it's not a huge issue.

Thanks for the ideas, I will give them a shot as soon as I get a chance!

Beginner
Posts: 0
Comments: 2

#5

Hi all

sorry for reopening this old topic - but I'm new in Snap Deploy, I understand what is written earlier, just wondering - isn't there some easy way how to deploy the machine from image using the previous name?

Example - I have machines INF01, INF02, INF03... INF20.. All has client installed. Image created from INF01.

Now if I need to deploy it to all remaining I need to set individual settings for all remaining, specifiing the correct name and domain (so entering the DC admin etc). I would expect it can read the original machine name before deploying the image... so previous INF03 will be INF03 even I have to do the customization for every of those.

Any hint?

 

Thanks

Jiri

Support specialist
Posts: 0
Comments: 813

#6

Hello Jiri,

sorry for a delayed reply.

In your case you can use Machine name and membership settings as listed in example Name{0}{0,10}

Thus, you should use the following pattern: INF{0}{1,10}

Beginner
Posts: 0
Comments: 2

#7

Thanks Maria for answer,

 

I will test it but till now it sounds me that the system will just assign name based on the pattern. What I was looking for is to keep the original name of the machine I'm going to deploy from image.

But let's see :D

 

Forum Moderator
Posts: 123
Comments: 4714

#8

Hello Jiri,

there is a feature request to preserve the original names (internal ID for reference RM-506), but this feature request is not in the scope for the nearest product updates. I've registered your post as a vote for the feature implementation.  

In the meantime, you can either use the predefined name patterns or configure Individual deployment settings for every machine (set the name for every machine before deployment).