ClientApps and Outlook service packs
- From: "Andrew M. Saucci, Jr." <spam-only@xxxxxxxxxxxxxxxx>
- Date: Sat, 17 Dec 2005 15:42:57 -0500
Thursday night I applied Small Business Server 2003 SP 1 to a
server, which went fine. After that I ran Microsoft Update on the
workstations, which included Office 2003 SP 2. That wanted the original
installation source, which apparently was no longer in the original
ClientApps folder. Fortunately, at some point I had placed another copy of
the Outlook administrative installation on another partition, so I was able
to satisfy the Office SP by pointing its dialog box there. (I may have moved
Client Apps to F one day when C: ran out of space and then copied it back to
C: just so I would have something I know I can move/delete the next time C:
fills.) The server does have a ClientApps folder right now on C:, and it
does have a copy of Outlook 2003 on it, but that was not sufficient to make
the Office 2003 SP happy.
I've seen this sort of thing happen before. What I need to know is
this: How is this actually supposed to work? If I don't touch ClientApps, is
SBS 2003 SP1 supposed to update the administrative installation of Outlook
in such a way that Office 2003 service packs will install seamlessly
(meaning, without my intervention)? Or should I always copy the Outlook 2003
administrative installation to a safe place because I will need it later and
the SBS SP breaks it? Or am I missing something else entirely?
.
- Follow-Ups:
- Re: ClientApps and Outlook service packs
- From: Dave Nickason [SBS MVP]
- Re: ClientApps and Outlook service packs
- Prev by Date: Re: SBS FAX SERVICES BUG WHEN RUNNING EXCHANGE 2003
- Next by Date: Re: Pop3 errors after SBS SP1 / Exchange SP2
- Previous by thread: Post SP1 error on SBS2003 Standard (icw.exe crashes, but server is otherwise fine)
- Next by thread: Re: ClientApps and Outlook service packs
- Index(es):
Relevant Pages
|
