Is SnapDeploy what I need in such a case?

Thread needs solution
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Beginner
Contributions: 1
Commentaires: 0

Good morning all,


I’m sorry to start posting with kinda trivial question but I would appreciate your help/advise in advance. I administrate a network of around 800 stations running Windows XP and few servers.

 

Let’s take this scenario:

  • I have a fresh virtual server running Windows Server 2008 R2, I intend to use it as Imaging Server.
  • I have 2 similar desktops DELL Optiplex 780, one running Windows 7 Enterprise edition and the other one is OS free.

 

What I need is the following:

  • I wanna take an image of the desktop with Windows 7 OS and remotely deploy it on the other desktop.
  • I wanna this to be done either from server side by looking for a specific MAC address or by initializing a batch file from the new desktop that will communicate to the server and determine the proper image based on the model number which will be acquired from the BIOS.

 

Concerns are:

  • Images are not an issue, I have few models so I can image them manually and fill the imaging server with these images.
  • Computer name is not a big deal as I will image few desktop weekly and changing it manually is not a big deal unless there is a professional way to do it from server side (that would be wow).
  • Is SnapDeploy a server-based software? Or it can be run from anywhere through the LAN?
  • Licensing, I noticed that it’s $23/license, license of what in such a case?

 

Finally,

I believe that I can find more answers by going through the user guide and installation guide but due to lack of time I preferred to post the requirements and see based on your previous experience wither SnapDeploy is what I’m looking for or it wont help. Your cooperation is highly appreciated.

Thanks

lun 09/08/2010 - 05:05
0 Users found this helpful
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Forum Star
Contributions: 24
Commentaires: 3268

Dear Naif824!

Thank you for joining us on Forum, it's nice to have you with us! I understand the scenario you need to achieve and will be glad to answer all your questions!

The scenario you've specified is absolutely achievable. But before I describe you the main procedure, let me address your concerns.

  1. Snap Deploy is not a server based software and can be installed in any LAN onto any OS. You can find the list of OSes Acronis Snap Deploy 3 components support here.
  2. You definitely can change the Computer name, User, join the Domain, etc. right during the process of deployment. I'll specify in details and with links how it can be done in a few minutes.
  3. Licensing: according to the License Policy you need 1 license for 1 machine you're going to deploy.
    For instance, you have 5 machines you need to take the image from and 30 machines to deploy these images to. In this case you will need 30 licenses. Each license it tied to the MAC address of the machine. In case of a large purchase we are glad to offer discounts and volume licenses, which would reduce the price. For this you will need to contact our Sales representative. If you're interested - let me know, I will send you the direct contacts!

Now let's get back to the imaging and deployment part.

First of all I'd like to notify you that unfortunately it's not possible to deploy the image to the machine specified by MAC address (yet. We've requested this functionality, but unfortunately cannot say when it will be implemented).

The process of dealing with machines is the following: 

  1. Installation of all requires components.
    a) License Server.
    It's responsible for the licenses sent to every Agent during the deployment. Install it, upload there the licenses and forget about it. (You can find more information in the User's Guide, chapter 3.5, p.26)
    b) OS Deploy Server
    This component is responsible for deployment process (finding the image and pushing it to the target machine). During the installation you will need to point onto the License Server.
    c) Management Console
    Allows you to manage all processes
    d) PXE Server
    This one will be required in case you prefer to image or deploy via network. PXE may contain different components, - you will need to manually configure it (it takes 1 - 2 minutes). (see chapter 6, p. 42).
    Configure it to contain Master Image Creator (for imaging machines) and Agent (for deployment)

    All the components are added to the installation package.

  2. Imaging the machine.
    Can be performed in 2 ways: from the bootable media or from PXE.
    a) Bootable media: 
    Simple. You create a CD by means of our product (click Create Bootable Media on the
    toolbar or the sidebar, or select Create Bootable Media from the Tools menu.), go to the target machine, boot it from CD and follow the steps of imaging wizard
    b) PXE server
    Even more simple: you have PXE configured to contain Master Image Creator. Reboot the target machine, enter BIOS and set in the NIC to be the first boot priority. Reboot once again - and your machine will boot into the PXE. After that just choose Master Image Creator. See chapter 7, p.43 for more details.
  3. Deployment.
    a) Deployment starts from creating a Template. (see 9. Deployment templates , p.52).
    A deployment template is a set of configuration parameters of the deployment operation. This
    includes:
    1. A path to the master image
    2. The operation mode (multicast or unicast, how to handle the target disk free space etc.)
    3. Settings to be applied to the deployed systems (DNS names, user accounts etc.)
    4. Operations to be performed on the deployed systems (transfer files, execute applications, shut
    down, restart.)

    b) After the Template with all required parameters are ready, boot the target machine into the Network and choose the Agent after entering PXE. On the target machine you will see progress bar running and stalled - it's ok, it just means that the computer is ready for the deployment.
    The machine itself will appear in the Management Console as ready for deployment. Choose it, choose template and start the process.

  4. Wait till deployment is finished and boot up the target machine

These are the general steps. We have different Deployment styles, all are described in the User's Guide, chapters  10 -14, so you can find one that will suit your needs. I would advise you to test the solution before making a decision, you can find the demo version right here. It's full functional and has no limitations except: 

  • 15 days of work
  • only 5 machines can be deployed with one trial license

Images and deployed machines don't expire after the trial version.

You can find our Installation Guide useful as well.

Should you have any further questions or concerns - please, let me know, I will be glad to answer!

Thank you!

mar 10/08/2010 - 07:47
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Beginner
Contributions: 0
Commentaires: 2

Question?  I See bellow that is Each license it tied to the MAC address of the machine. My Question is what if the motherboard or nic of a machine has to be replaced(warranty or not) do we have to purchase another license?  Also as we get rid of older machines(replacing) do the licenses transfer or do we have to purchase another license?

Thanks,

Brad 

ysavchenko wrote:

Dear Naif824!

Thank you for joining us on Forum, it's nice to have you with us! I understand the scenario you need to achieve and will be glad to answer all your questions!

The scenario you've specified is absolutely achievable. But before I describe you the main procedure, let me address your concerns.

  1. Snap Deploy is not a server based software and can be installed in any LAN onto any OS. You can find the list of OSes Acronis Snap Deploy 3 components support here.
  2. You definitely can change the Computer name, User, join the Domain, etc. right during the process of deployment. I'll specify in details and with links how it can be done in a few minutes.
  3. Licensing: according to the License Policy you need 1 license for 1 machine you're going to deploy.
    For instance, you have 5 machines you need to take the image from and 30 machines to deploy these images to. In this case you will need 30 licenses. Each license it tied to the MAC address of the machine. In case of a large purchase we are glad to offer discounts and volume licenses, which would reduce the price. For this you will need to contact our Sales representative. If you're interested - let me know, I will send you the direct contacts!

Now let's get back to the imaging and deployment part.

First of all I'd like to notify you that unfortunately it's not possible to deploy the image to the machine specified by MAC address (yet. We've requested this functionality, but unfortunately cannot say when it will be implemented).

The process of dealing with machines is the following: 

  1. Installation of all requires components.
    a) License Server.
    It's responsible for the licenses sent to every Agent during the deployment. Install it, upload there the licenses and forget about it. (You can find more information in the User's Guide, chapter 3.5, p.26)
    b) OS Deploy Server
    This component is responsible for deployment process (finding the image and pushing it to the target machine). During the installation you will need to point onto the License Server.
    c) Management Console
    Allows you to manage all processes
    d) PXE Server
    This one will be required in case you prefer to image or deploy via network. PXE may contain different components, - you will need to manually configure it (it takes 1 - 2 minutes). (see chapter 6, p. 42).
    Configure it to contain Master Image Creator (for imaging machines) and Agent (for deployment)

    All the components are added to the installation package.

  2. Imaging the machine.
    Can be performed in 2 ways: from the bootable media or from PXE.
    a) Bootable media: 
    Simple. You create a CD by means of our product (click Create Bootable Media on the
    toolbar or the sidebar, or select Create Bootable Media from the Tools menu.), go to the target machine, boot it from CD and follow the steps of imaging wizard
    b) PXE server
    Even more simple: you have PXE configured to contain Master Image Creator. Reboot the target machine, enter BIOS and set in the NIC to be the first boot priority. Reboot once again - and your machine will boot into the PXE. After that just choose Master Image Creator. See chapter 7, p.43 for more details.
  3. Deployment.
    a) Deployment starts from creating a Template. (see 9. Deployment templates , p.52).
    A deployment template is a set of configuration parameters of the deployment operation. This
    includes:
    1. A path to the master image
    2. The operation mode (multicast or unicast, how to handle the target disk free space etc.)
    3. Settings to be applied to the deployed systems (DNS names, user accounts etc.)
    4. Operations to be performed on the deployed systems (transfer files, execute applications, shut
    down, restart.)

    b) After the Template with all required parameters are ready, boot the target machine into the Network and choose the Agent after entering PXE. On the target machine you will see progress bar running and stalled - it's ok, it just means that the computer is ready for the deployment.
    The machine itself will appear in the Management Console as ready for deployment. Choose it, choose template and start the process.

  4. Wait till deployment is finished and boot up the target machine

These are the general steps. We have different Deployment styles, all are described in the User's Guide, chapters  10 -14, so you can find one that will suit your needs. I would advise you to test the solution before making a decision, you can find the demo version right here. It's full functional and has no limitations except: 

  • 15 days of work
  • only 5 machines can be deployed with one trial license

Images and deployed machines don't expire after the trial version.

You can find our Installation Guide useful as well.

Should you have any further questions or concerns - please, let me know, I will be glad to answer!

Thank you!

jeu 07/04/2011 - 16:03
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Forum Star
Contributions: 88
Commentaires: 4769

Hello Brad,

Thank you for posting. I will definitely assist you with your question.

For such scenarios we have a special procedure. Please contact our Sales representative and he will be able to assist you with this issue. I will send you a private message with the relevant information for your state.

I apologize for any inconvenience and if you need additional help please let me know.

Thank you.

ven 08/04/2011 - 11:18
Abigo autem causa dolore scisco. Conventio defui dolor elit feugiat lucidus natu populus praemitto. Abbas ad facilisi. Defui ea gemino suscipere. Consectetuer eros interdico minim. Esse incassum plaga. Caecus decet dolore ille iriure neque. Gilvus letalis mauris paratus quis tego. Brevitas capto erat gemino loquor ratis tincidunt vulpes. Appellatio haero humo iustum luctus natu similis. Conventio decet eros humo praemitto ratis ullamcorper virtus. Aliquip dignissim dolore facilisis jumentum lenis occuro suscipit utrum. Esca gilvus haero ideo nutus persto quidne refoveo usitas. Adipiscing cui nisl odio paulatim quadrum qui venio virtus. Caecus letalis natu nunc pertineo praesent utinam. Caecus eligo jugis nimis tamen te. Ad diam dignissim gravis iusto magna praemitto. Augue gravis magna obruo plaga valde. Et humo molior saepius. Adipiscing aliquip lenis paulatim quadrum wisi. Duis in voco. Consectetuer gravis plaga populus quia. Commoveo consequat distineo exputo iustum nisl saepius. Appellatio genitus ille melior mos nisl odio torqueo velit vindico. Abico comis iustum minim nobis oppeto pecus vero. Abico ex exerci haero iusto quia sed typicus. Abigo camur lobortis pneum tincidunt turpis vel. Abbas acsi dignissim ea suscipere. Eros iustum lobortis nobis probo quadrum qui velit verto vulpes. Importunus iustum magna modo nimis nunc sit vel vulputate. Blandit commodo dolus facilisi pertineo voco vulpes. Iriure loquor venio. Cogo ea esse gravis huic imputo odio refero similis ut. Aliquam autem conventio ibidem paulatim quia sagaciter vereor wisi. Adipiscing enim esca et olim sino vulpes. At iusto scisco vulputate. Ad ex ille secundum utinam valde verto vulputate. Erat molior nibh turpis. Importunus pala utinam. Causa conventio nulla quidem secundum tation verto. Camur conventio eros importunus iustum. Consequat dolore immitto iriure luptatum nostrud ulciscor ut. Distineo enim iusto torqueo utinam. Brevitas natu pala vereor. Abigo decet ea proprius typicus uxor volutpat. Causa iusto quae sit suscipere torqueo ut vulputate. Magna occuro pneum. Abbas blandit dolus paulatim. Adipiscing caecus jugis nibh obruo premo. Augue causa eu laoreet lenis mauris premo suscipit vero. At damnum exputo ideo immitto pala vereor. Eum jugis utinam velit wisi. Augue cogo ratis suscipere vereor. Diam ille incassum persto saluto. Abluo blandit fere molior. Caecus erat magna mauris praemitto saluto vero. Qui singularis tincidunt valde. Minim qui similis ut. Ex exerci lenis nimis ratis sagaciter volutpat. Abigo aliquam lenis loquor nulla pala similis vel velit vero. Aliquip defui erat letalis paulatim utinam. At nutus occuro. Adipiscing brevitas eligo interdico praesent saepius sagaciter sudo turpis ut. Accumsan dolus eu pertineo refero verto. Imputo meus vereor wisi. Bene commodo diam illum laoreet paulatim populus uxor. Caecus commodo inhibeo jus nulla nunc ulciscor valetudo. Consectetuer defui iaceo iustum nibh te vel. Facilisis loquor ratis tum vicis. Capto luptatum pala sudo torqueo. Antehabeo caecus dolus ea gravis illum molior vulputate. Abdo adipiscing iaceo jugis pertineo te ullamcorper. Abico erat ideo os turpis. Dolore facilisis metuo nibh occuro pecus volutpat. Acsi antehabeo damnum defui ex lucidus nulla ymo. Fere pecus sudo. Camur dolore illum loquor qui quia. Brevitas camur dignissim dolor duis obruo plaga quae veniam volutpat. Dignissim loquor olim te vereor. At cui dolore erat eros jumentum ludus nibh vereor. At dolor eros huic suscipit te typicus voco. Appellatio autem defui in neque nisl proprius qui tation. Eros quae refero. Aptent bene dolor minim. Abdo cui importunus oppeto utrum. Commodo erat ludus olim vel. Commodo iustum laoreet nisl. Abico os tincidunt tum. Damnum enim fere sit suscipere tego turpis typicus usitas virtus.