Skip to main content

Filtering Images for User-Initiated Deployment

Thread needs solution

1. Is there a way to filter the shown Images for User-Initiated Deployment via Mac adress or group?

 

2. Is there a way to let a deployment task run every minute? Or everytime the machine is getting attached to the network?

 

Thanks for all answers!

 

 

0 Users found this helpful

Not that I'm aware of for either question - you should contact support directly to see if they can offer any additional informaiton or suggestions though.

The deployment process is based off of the local subnet.  Any machine that has PXE booted or used the offline recovery media to boot can have an image deployed to it.  However, if you have an image respository, you still have to pick the image you want to use either by using a template or by manually picking it. To make things easier for yourself, you should categorize your images into their own subfolders so they are easily identifiable by users. Have your main folder, and then create subfolders with unique names (like OfficeA images, OfficeB images).  Likewise, save your images with names that also make it easy to identify who they are intended fro.

I don't think most people would want a deployment to run everytime a system is attached to the network.  AFter you deploy the image, if the system is part of the same network, it would just get overwritten again so would not be ideal in many cases.  Snap Deploy can simplify the deployment process, but it's not 100% automated as you need to be able to pick the correct image to deploy and when you want it deployed.  Perhaps the Acronis technicians can offer some different/better advice though, so give them a shout.   

Thanks for your answer! I will get in touch with the support, if they can offer me a solution i will post it here.

 

 

I had a feeling, but good to have verified.  

For #1 - you should be able to help alleviate the user choices by using well worded folders and backup file names to direct people to the correct images.

For #2 - I just don't see it being an option.  There's too much liklihood that if you had such an automated process, users would potentially have the opportunity to continually wipe and load their system (unintentionally). It could technically work (if it was supported) as long as the deployment network was completley segregated from the primary network, but if you're having users connect to the network to restore their own systems from remote, I'm assuming they'd be on the same network where the images are located as well so that wouldn't work very well since they would reinstall every time they rebooted (or anytime somone PXE-booted). 

Yeah we have a very special envoirment where we use Snap Deploy, there is nearly zero risk that people are accidently wiping their data. The only solution i found was that i now do the hourly deployment for every image 12 times every hour so that you need to wait about 5 minutes till a deployment starts. Not a great solution but the only possible at the moment.