RE: OSD SDP to cache and install application
- From: Tim Quigley <TimQuigley@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 2 May 2007 05:47:00 -0700
Thanks Matthew. I understand how you get round the issues of MSIs running at
the same time now.
I think we are going to have to do a bit more research into this. Currently
(like yourselves) we have a bare image with the applications installed
afterwards. However, we are currently using Novell ZENWorks (we are in the
process of migrating to SMS) which allows you to set the installation order
for the applications. This means we can go from a bare metal build to fully
installed build with all core applications in about 40 minutes. It also means
we can re-build 100-150 machines a night (Wake-on-LAN, PXE boot etc). Using
something like your process, we would not be able to do such numbers in the
timescales we are used too.
This maybe something we have to accept and get on with it!
Thanks for all your help and advice
Tim
"Matthew Hudson" wrote:
This is where you get into how every does their new computer provisioning,.
which is always different but I will tell you how I do mine. Here is a long
answer to a short question. I hope I answer your question and not drone on
and on and on....
First I image the computer, no applications are installed at all. Next I
place a Mif file on the computer that has office number, image date, est date
of disposal. This is used later for reports but starts my new computer
process. It is pulled into a collection that has several sub
collection(office, adobe...)
Since all the packages run in serial there is no way for MSI's to run at the
same time. Each package must finish before another can begin. I have many
new computer adv. In order to speed things up I pass a HW inventory to the
computer each hour. This gives the computer a workout but forces all the
apps to get done quicker. Since the Collection/ADv is based on add remove
programs this will update quickly. I have the collections updating every 1
for long installs and 15 mins for those quick installs.
I can have a computer imaged and all software installed in about 4 hours. I
also have all the packages restarting when they want to. Since it is a new
computer collection I let the package do anything it wants. I also send down
a restart command every 3 hours just incase something fails to restart and
the package is waiting to finish. I have them sit there for 2 days just
incase it is one of the Dept that requires lots of updates and installs. I
can start the image on Friday night and it will be done with everything by
Monday morning. I also have several programs I have written that will allow
me to watch the progress. I am working on posting a longer version on my
blog later in the month. Again everybody does it differently..
--
-----------------------
http://sms-hints-tricks.blogspot.com/
"Tim Quigley" wrote:
Thanks Matthew. Quite obvious really.
However, how do get round the issue of installs failling as one MSI is
already being installed? Do you just wait for the SMS client to refresh again
and install the next app (which could take sometime), or is there way of
forcing applications to install directly after each other. (They cache fine,
just fail the install)
Thanks Tim
"Matthew Hudson" wrote:
We simply have a new computer collection that has newly imaged machines.
Once a machine pops in the SMS aggressivly installs all the apps, downloading
first of course. This includes office, adobe, hummingbird, and many other
apps. This is because we have only the basic image, no applications in the
image. so when the new version of something comes out we simply change the
adv. The easiest way is to create a collection that looks for the lack of
office or adobe on the machine and then it run "as soon as possible" Of
course this all depends on how fast you run the inventories and machine
policy refresh.
--
-----------------------
http://sms-hints-tricks.blogspot.com/
"Tim Quigley" wrote:
We are currently investigating the use of OSD to deploy a workstation image.
Part of which, we want to install applications after the image has been
deployed using the "Software Distribution Program" in the "State Restore
Phase"
We have got this working fine; however, we want to be able to cache the
applications first. As the "download and install" option is on the
Advertisement which I gather is not used by the SDP, is there any way to
cache the application and install it as part of the OSD State Restore Phase.
Applications we are referring to include MS Office 2003, Adobe Reader,
ActiveSync, Citrix ICA etc. basically standard applications to go on a laptop
build.
Thanks in advance for any help you can provide.
Tim
- References:
- RE: OSD SDP to cache and install application
- From: Tim Quigley
- RE: OSD SDP to cache and install application
- From: Matthew Hudson
- RE: OSD SDP to cache and install application
- Prev by Date: RE: OSD SDP to cache and install application
- Next by Date: SMS MOBILE
- Previous by thread: RE: OSD SDP to cache and install application
- Next by thread: SMS MOBILE
- Index(es):
Relevant Pages
|
