/build/static/layout/Breadcrumb_cap_w.png

Application deployment on re-images

Just like to know what other users of the Kbox use as a method of installing applications when there pc/laptop needs a rebuild.

I'll give you an example.

User X has a standard image the same as everyone else in the company that has things like Lotus Notes, Office Standard, Winzip, Acrobat Reader....all setup as post install tasks. User X also has non standard image applications such as Visio, Adobe CS3, Autocad.

How would you go about making sure the non standard apps are installed on his rebuild the easiest possible way? I was thinking of setting up application labels and assigning machine names to particular labels however when a user gets a new machine the PC name would be different so that's not really the best way to go about things i'm guessing!

I guess what i'm looking for is a solution where I rebuild a users machine and it justs knows what applications they need are...obviously there has to be some manual input somewhere in setting this up. Hopefully you guys have some ideas!

Ben.

0 Comments   [ + ] Show comments

Answers (3)

Posted by: airwolf 10 years ago
Red Belt
0
Do you have the Asset Management and Help Desk modules? If so, you can create User assets using custom SQL rules to automatically create them based on your KBOX users (whether you're using local accounts, LDAP, etc.). You can then link those User assets to Computer assets, and then using custom SQL rules you can automatically add machines to your deployment labels by linking Computer assets to Inventory items.
Posted by: ncmonag 10 years ago
Senior Yellow Belt
0
We are doing something similar to what airwolf suggests but before that we used the computer description to accomplish something similar so that might be a way w/o Asset Management. Either way you have to remember to set the appropriate information but it's nicer than manually adding machines to labels/distributions.
Posted by: lindsamw 10 years ago
Orange Senior Belt
0
I just have my labels Auto Populated by OU, and people get all their software that way (I have pulled off most of my scripted install post install tasks and moved them to be MI's, because I seem to have a lot of timing issues and no issue tracking if a post install task failed. Basically my scripted installs are just a default install of XP that names, reboots, joins the domain, reboots, then gets a ton of software pushed to it.
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

Share

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ