Scripted Install / Imaging Process
Hello. I was interested in getting some ideas or tips on best practices and work flows for building machines with scripted installs and/or images.
I like the modular and simple approach of scripted installs, and ideally would like to get away from the cycle of maintaining a number of various images along with applying security updates and other application changes over time. The scripted installs seem possibly a nice way to do that, but if I take traditional imaging out of the picture I'm not sure what the best way is to deal with these two issues via a scripted install process:
1. Applying Windows + MS Office updates easily and efficiently following a scripted install that has included applications, etc.
2. Dealing with default user profiles. Normally I would configure these as Administrator or by copying over a temporary accounts setting to the default user profile, but I wasn't clear if/how this might work during a scripted install?
Both of these could be rather time consuming manual tasks if done by hand, but it wasn't clear to me if there's a way to easily 'stream' these functions into a scripted build.
I'm curious as to any thoughts or ideas.
Thanks.
I like the modular and simple approach of scripted installs, and ideally would like to get away from the cycle of maintaining a number of various images along with applying security updates and other application changes over time. The scripted installs seem possibly a nice way to do that, but if I take traditional imaging out of the picture I'm not sure what the best way is to deal with these two issues via a scripted install process:
1. Applying Windows + MS Office updates easily and efficiently following a scripted install that has included applications, etc.
2. Dealing with default user profiles. Normally I would configure these as Administrator or by copying over a temporary accounts setting to the default user profile, but I wasn't clear if/how this might work during a scripted install?
Both of these could be rather time consuming manual tasks if done by hand, but it wasn't clear to me if there's a way to easily 'stream' these functions into a scripted build.
I'm curious as to any thoughts or ideas.
Thanks.
0 Comments
[ + ] Show comments
Answers (2)
Please log in to answer
Posted by:
acmccoppin
14 years ago
1) Anything from Office 2007 on will be able to packaged and setup as a silent install through the /admin switch for the Office installer. Hotfixes will need to be slipstreamed. Let me know how you make out with that.
2)Create a batch file for a post installation script that will copy/setup any kind of preferences you need.
2)Create a batch file for a post installation script that will copy/setup any kind of preferences you need.
Posted by:
timantheos
14 years ago
Office 2007 I have packaged and bundled with several other applications as post install tasks in a scripted install, so I'm ok there.
As for creating a post installation script to apply updates and default user settings, etc. ...yes that is what I'd like to do. What I'm interested in learning from others is specifically how best to do that within the Kbox.
As for creating a post installation script to apply updates and default user settings, etc. ...yes that is what I'd like to do. What I'm interested in learning from others is specifically how best to do that within the Kbox.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.