Re: Office 2003 SP3 deploy?
- From: Cliff <cgaliher@xxxxxxxxx>
- Date: Thu, 24 Apr 2008 16:03:14 -0700 (PDT)
On Apr 23, 2:00 pm, Guillermo Lovato
<GuillermoLov...@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
Hello,
thanks for the responses but it isn't exactly was i was asking, my question
is specific to the generation of an administrative install of SP3, i don't
want to use WSUS for this because it takes too much HD space to download all
service packs for deployment(WSUS already takes too much space as is because
it downloads tons of obsolete fixes, i.e.: my network will only have Win XP
sp2(slipstreamed), all same language, so i only need patches AFTER SP2, WSUS
has no simple way to select this level of basic baseline, and it downloads
2001 patches).
what i need to know is of those files i listed that are generated using the
admin install, what do they do?, apart from the main, are the others used?
"Terence Liu [MSFT]" wrote:
Hello Customer,
Thank you for posting here. Let's also thank Larry for the good input.
According to your description, I understand that you want to deploy the
office 2003 sp3 to clients thru group policy on SBS 2003. If I have
misunderstood the problem, please don't hesitate to let me know.
The WSUS is a good resolution. Additionally, I want to add two SBS methods:
For deploying the customize applications to SBS clients, generally, you
have two methods.
Method 1: Use 'Client Application Wizard'
=====================================
1. Create a server share and store client application on this server share.
Set at least read & execute permission to proper users.
2. Open Server Management and Click Client Computers node
3. Click 'Setup Client Applications' links in the right panel
4. In the available application page, please click Add
5. Input Click Application Name, such as "Client Application #1". Click
'Browse' and locate the application package. It could be exe file, msi or
msp file or other executable file. Finish the wizard.
6. Click 'Assign application to Client computers' link
7. In the Client Computers page of this wizard, choose the computer that
you want to apply the application and click Add. Add all computers you want.
8. In the Client applications page, please confirm that "Client application
#1" is checked. Finished Wizard.
9. On the client computers, log off and log on again to apply the
application
However, with this method, a shortcut for your customized application will
be put on the client computer desktop when they logon, instead of
installing directly. This is exactly a design of "Assign application" to
give the users a period of time to prepare their client computers before
the installation begins. If you want the application be installed on
clients forcedly, you can try the method 2.
Method 2: Use GPO
=================
You can perform the following steps in the KB:
How to assign software to a specific group by using Group Policy in Windows
Server 2003
http://support.microsoft.com/?kbid=324750
As described in the above article, you have to create MSI package for your
application. EXE file is not available for deployment. For detailed
information, please refer to the following article.
HOW TO: Create Third-Party Microsoft Installer Package (MSI)
http://support.microsoft.com/kb/257718
I hope these steps will give you some help.
Thanks and have a nice day!
Best regards,
Terence Liu(MSFT)
Microsoft CSS Online Newsgroup Support
Get Secure! -www.microsoft.com/security
=====================================================
This newsgroup only focuses on SBS technical issues. If you have issues
regarding other Microsoft products, you'd better post in the corresponding
newsgroups so that they can be resolved in an efficient and timely manner.
You can locate the newsgroup here:
http://www.microsoft.com/communities/newsgroups/en-us/default.aspx
When opening a new thread via the web interface, we recommend you check the
"Notify me of replies" box to receive e-mail notifications when there are
any updates in your thread. When responding to posts via your newsreader,
please "Reply to Group" so that others may learn and benefit from your
issue.
Microsoft engineers can only focus on one issue per thread. Although we
provide other information for your reference, we recommend you post
different incidents in different threads to keep the thread clean. In doing
so, it will ensure your issues are resolved in a timely manner.
For urgent issues, you may want to contact Microsoft CSS directly. Please
checkhttp://support.microsoft.comfor regional support phone numbers.
Any input or comments in this thread are highly appreciated.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------
| Thread-Topic: Office 2003 SP3 deploy?
| thread-index: Acijtgi0PsgTVdjfQTqf1kfqAsY1Mw==
| X-WBNR-Posting-Host: 207.46.19.168
| From: =?Utf-8?B?R3VpbGxlcm1vIExvdmF0bw==?=
<GuillermoLov...@xxxxxxxxxxxxxxxxxxxxxxxxx>
| Subject: Office 2003 SP3 deploy?
| Date: Mon, 21 Apr 2008 06:46:00 -0700
| Lines: 11
| Message-ID: <16215BA8-143A-420F-9125-73A453514...@xxxxxxxxxxxxx>
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="Utf-8"
| Content-Transfer-Encoding: 7bit
| X-Newsreader: Microsoft CDO for Windows 2000
| Content-Class: urn:content-classes:message
| Importance: normal
| Priority: normal
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.2992
| Newsgroups: microsoft.public.windows.server.sbs
| Path: TK2MSFTNGHUB02.phx.gbl
| Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.windows.server.sbs:104121
| NNTP-Posting-Host: tk2msftsbfm01.phx.gbl 10.40.244.148
| X-Tomcat-NG: microsoft.public.windows.server.sbs
|
| Hello,
| i want to deploy SP3 so that office 2k3 installations and the included
| outlook are upgraded.
| i did an extraction of the SP3 files but i don't have a single MST like
the
| included SP1, i have 5 files:
| the main one, 3 of a hotfix and OWC11SP3.msp OWC102003SP3.msp
|
| how do i use them?,
|
| is there a problem if i install office 2003 over the installed outlook on
| client computers?
|- Hide quoted text -
- Show quoted text -
Actually, WSUS3, when properly configured, only downloads approved
patches. It also has a cleanup wizard that will delete old patches
previously approved, but later made obsolete by superceded updates.
So, in short, WSUS won't take up significantly more space that hosting
the patches you desire individually anyways. You lose a small amound
of space for the MSDE database to *track* those updates, but the trade-
off for manageability is, I think you'll find, more than worth it. I
hope this helps ebb your concerns with using WSUS.
-Cliff
.
- References:
- Office 2003 SP3 deploy?
- From: Guillermo Lovato
- RE: Office 2003 SP3 deploy?
- From: Terence Liu [MSFT]
- RE: Office 2003 SP3 deploy?
- From: Guillermo Lovato
- Office 2003 SP3 deploy?
- Prev by Date: Re: New SBS3003 to existing Domain
- Next by Date: Re: ICMP error when trying to access OWA on SBS 2003 Premium
- Previous by thread: RE: Office 2003 SP3 deploy?
- Next by thread: Local user profile cannot be loaded.... (etc etc)
- Index(es):
Relevant Pages
|
Loading
