After Deploy, computer name isn't being renamed

Eric wrote:

Hi,

I am new to Acronis Snap Deploy so please forgive if this is basic.

I have created a master Win 7 x64 image. I deploy the image to a pc through a template job and the deploy goes off fine. When I check the newly deployed pc, I find the computer name is the same as the master computer the image was taken from. In the general settings of the Snap Deploy 4 server there was a place to enter in what acronis would rename the image to be.
It also said that if I applied a name to the machine account in the management window that it would take that name instead.

Acronis didn't use any of these, and the name is the same as the master.

What am I doing wrong?

Thanks!
Eric

I am having the same issue. Im running a trail version and have imput the name on the individual properties on one machine. When i enter the imput it tells me that I should use a proper naming conventions but the guide says the opposite, that i wont be able to in that section.

Im looking around for a imaging solution and Snap deploy will fit the bill if i am able to keep the comptuers named the same as before they are imaged. Thanks

Don

Hello Eric, don flinton,

the machine names for target machines are determined in deployment settings, namely in "Machine name and membership" window.

Please check, which settings you have in the relevant tab. Should any questions remain unanswered, please post here screenshots of your settings.

Thank you.

Thank you Anna,
I will grab some more screen shots this morning but this is what I get when I try to add the unique machine name.
I can see getting that warning message when entering any unique names in the Deployment Template section but I would think
this error would not pop up in this section where I am supposed to enter a unique name.

I had made this change in the general machines section. I imported a mac list and edited only one computer, gave it a label and changed that one part to give it a unique name. saved .. entered passwords .. launched the image. It keeps the name of the master image computer. I had left the deployment task - machine naming scheme blank thinking it would just rename the pc the original name but I am imaging again now after adding a scheme sar-machinename{1} to the deployment task general settings(still leaving the unique machine name) to see if that will affect the outcome.

thanks for your help.

Don

{update}
The new image just finished with adding a naming scheme to the Deployment task and it did name the computer sar-machine1, so that part is working but it skipped the unique name again. Also i hadn't mentioned that I am attempting this with an 8.1 image 64 bit imaging from 2012 Server.

Thank you.
Don

I didn't know which message to reply to, but I resolved the issue.

There are two places to check to have the machine use a unique name. The first is in the Deployment template you create there is a check to allow the selective overrides- Under Settings Preferences.

Then you also have to check the box in the Individual Settings for Machine name and membership then fill in the info appropriately with the unique name.

That worked for me i was able to image the machine and it configured the name and domain properly.

So one last question is there a way to, once the image is done have it skip the PXE or recognize that it was just imaged and boot to the OS rather than boot again into the Deployment task and stall there... I can turn off the PXE server after the push has started which is acceptable but just wondering if there was another solution.

Thanks again.
Don

Hello don flinton,

there is no way to skip PXE after deployment.

But there is one trick that you might want to use if you deploy the image to a clean machine without installed OS. You can set on the first place in the boot order HDD disk and PXE on the second. In this case after deployment the target machine will be booted in Windows.

Thank you.