Ah, I figured someone might comment on my statement.
Yes, DUA was created for updating deployed images in the field.
Historically it was created for QFE's. I'm not sure it was advertised
for adding components to an already deployed image. I thought I read
a MS statement that said that somewhere?
It is my feeling too that if one could figure out all the dependancies
that a component needs , which in some cases like IIS could be a lot
of work, then one could use DUA to add it. If you had the list of
files and registry keys especially what FBA does then it seems
possible ;-)
Possible - sure. Once you figure out all the files and registry keys
added by IIS, then you write a DUA script to copy them into place on the
live runtime and call for a reboot.
Problems - there are a lot of files involved in IIS (I don't have an
exact count, but I wouldn't be surprised to find it was over 100 files),
and a lot more registry keys. Plus all the dependencies IIS has -
you'll need to ID those and get those files and registry keys as well.
Oh yeah, there are also FBA commands and DLL/OCX registrations that need
to take place - you'll need to locate all of those and have DUA put in a
RunOnce item to do a regsvr32 for all of them. And to top it off,
there's the metabase IIS uses to store all it's settings, which needs to
be configured online, so there are more RunOnce commands to finalize all
of that (actually, when I QFE'd IIS one time, I had to put them in
RunOnceEx to make sure IIS was actually running before trying to do the
metabase operations).
Add to all of this the joys of writing DUA scripts (I've heard people
complain over writing DUA scripts for single file QFE's), and you've got
yourself a psychotic break waiting to happen.
You'll save yourself a lot of time, agony, and hairline by just
recreating the image and redploying it.
There is a slightly bright side here, though - we realize the pain this
kind of situation causes, and are working to solve this issue.