Imaging vs. Pushing Software

ElwoodBlues

I am relatively new to Active Directory and Imaging alike. Therefore I do not have a long trend for pros and cons in the deployment of software. I know that you can install and uninstall software (such as MS Office, browser plug-in, etc.) thru active directory. I also know that you can factor it into the image as well.

So my question is how do most people handle common apps like this?

Thanks

sprkymrk

You would include any software that is used by the majority of your network in a baseline image. Any software that needs to be used by only a fraction of your network would be deployed via AD and applied based on GPO's linked to OU's. So for example, the image might include a full Office Installation, but you might only deploy MS Money to computers that are in your Accounting OU.

Claymoore

It all depends on your infrastructure and personal preference. I am a fan of thick images which include software that doesn't change much, such a terminal emulator, or has a way of updating itself such as Office. Then I will deploy software that changes frequently, such as Acrobat Reader or Java. Thick images are more work because you have to mantain all the applications on them in addition to the base OS, but the workstation can be re-imaged and deployed faster.

For a good and thorough discussion regading imaging and software deployment, try Creating the Secure Managed Desktop. Moskowitz is a fan of thin images and he makes some very convincing arguments why you should consider them. Once you understand theprocess a bit more, you will be able to decide which method to use based on your specific needs.

Kasor

There are many tools that can help you to accomplish your objective, but depending on your network, company requirement and budget (important issue).

ElwoodBlues

And updates thru AD will simply upgrade/update the apps themselves? That sounds easier to manage. One thing is for sure, there are many options; almost too many.

Thanks