1) How smart is Group Policy installation - (even using .msi files?)
eg, if I add IE6 to deployment, and then add 2000 SP4, what order would
these get installed in - and how can I control the order?? (assuming a
test case where a client PC doesn't have either)...
Heres why: Yesterday I was testing IE6, Office 2k and 2000 SP4
deployment on a test PC, only to realise that SP4 was already installed
- actually it was a splistreamed 2000 install CD used. The install of
SP4 put a lot of errors into the install log - which as I don't speak
micro-babble I have to assume is correct in this case. Then I wondered
if it was because IE6 was installed first, and THEN I wondered how it
determines the order. I'll be retesting the SP4 with a no-SP build today...
2) Are there any tips/tricks anyone can offer for .msi usage? I've
downloaded the tools needed to modify .msi files directly, but is there
any point outside of IE6 ??
3) Microsoft pages say that the way to deploy Office Service Packs is to
a) run the update on each PC individually, or b) to update the
Administration Install point. I've installed O2K via b), so if I want
to add a SP would I 1) update the Admin Point, then 2) Add the new .msi
as an "update" to the existing one, OR remove the existing install point
and add a new one (forcing each client to uninstall office and then
re-install).
Cheers,
Adrian
|
Similar Threads
