cldpeak
Posts: 270
Score: 6
Joined: 7/11/2002
Status: offline
|
quote:
How do you have the client recache?
msiexec.exe /i "\\ServerNetBIOSName\ServerShareName\officeadmininstallpointpath\Pro11.msi" /q REINSTALLMODE=VOMU REINSTALL=ALL /lvmo C:\msaOfficerecache.log
or if you want to show the user a progress bar change /q to /qb-
or if you want a progress bar and disable the cancel button use /qb-!
Note you do not have to type the full path the msiexec.exe for the client to run it. Clients should be at Windows Installer 3.1 version 2. To get the right windows installe version, you must inventory msi.dll. Have the client run the program from the DP since there are no files and the files it will cache with are on your server. If you use run with administrative rights for advanced clients, you server share must have both SHARE and NTFS permisions to allow read for the computer account. Usually this is through using "Domain Computers" global group which should include all your client workstations.
quote:
So how can we differentiate between the RTM and a patched version? Apparently not at all.
If you are at the client you must use add/remove programs and "click here for support information" under office 2003 with the article: http://support.microsoft.com/kb/821549
In your case, it sounds like you need to update your Administrative Install Point (if you are using an AIP) to Service Pack 2. I copied ours to a new share so that I could work with it without affecting current clients.
If deploying using ITMU, then create a collection (if systems that have had the ITMU scan) where the update 887616 (office 2003 sp2) is applicable such as in the query example:
select
SMS_R_System.ResourceID,
SMS_R_System.ResourceType,
SMS_R_System.Name,
SMS_R_System.SMSUniqueIdentifier,
SMS_R_System.ResourceDomainORWorkgroup,
SMS_R_System.Client
from
SMS_R_System inner join SMS_G_System_PATCHSTATEEX
on SMS_G_System_PATCHSTATEEX.ResourceID = SMS_R_System.ResourceId
where
SMS_G_System_PATCHSTATEEX.QNumbers = "887616"
and SMS_G_System_PATCHSTATEEX.Status = "Applicable"
You can then create an ITMU package using DSUW and check off any 887616 q numbers requested. There will be more than one, and most likely, not all. Only check off the one's requested and if prompted to automate checking off more that were intended as a group, be sure to click "yes".
You can then advertise the re-cache and the 887616 ITMU package to the collection with 887616 is dependent on the re-cache program to run first and only once. This ensures that your clients are re-cached before SP2 is applied.
|
Printable Version
MSI Source Paths - multiple packages - 
New Messages
No New Messages
Hot Topic w/ New Messages
Hot Topic w/o New Messages
Locked w/ New Messages
Locked w/o New Messages
Post New Thread