G
goldmanj
At our university we install Office 2003 from a network share point and
then use Group Policy to force it to update itself. Last week, we
updated our install point to include Office 2003 SP2 and used GP to
force to upgrade (technically it does a full reinstall I believe when
modifying the install point). Since then, we have ran into a problem
where after the update if a user tries to do something that pulls from
multiple office products (for example, doing a mail merge from within
word from an excel spreadsheet) it crashes out. We found that by
running a detect and repair, the problem is fixed but now I have around
1200 machines that need this ran on it. I was wondering if there was a
way to script an automatic detect and repair when windows boots so we
can get this fixed before the phones start ringing off the hook. I
also have the ability through group policy to add startup scripts quite
easily so if there is a way to script it, that would be an option.
Thanks,
Josh
then use Group Policy to force it to update itself. Last week, we
updated our install point to include Office 2003 SP2 and used GP to
force to upgrade (technically it does a full reinstall I believe when
modifying the install point). Since then, we have ran into a problem
where after the update if a user tries to do something that pulls from
multiple office products (for example, doing a mail merge from within
word from an excel spreadsheet) it crashes out. We found that by
running a detect and repair, the problem is fixed but now I have around
1200 machines that need this ran on it. I was wondering if there was a
way to script an automatic detect and repair when windows boots so we
can get this fixed before the phones start ringing off the hook. I
also have the ability through group policy to add startup scripts quite
easily so if there is a way to script it, that would be an option.
Thanks,
Josh