RE: Deploying Office XP SP3 using SMS Feature Pack

["Orhan O. Bag" <[EMAIL PROTECTED]>]

 Or,

Just use Shavlik HFNetChkPro, and forget about 'to do's, controls and all
audits of SMS.

SMS is a management tool, and ofcourse it manages patches; but it is not the
main target of SMS, thus it manages you more then let you manage patches.

A tool like Shavlik's HFNetChkPro downloads & deploys ALL with a few
'clicks'. You donot control and query any job. But just control and watch
how is it going, if there is any error...

This is why I belive that it is better to use a tool which is designed and
dedicated for patch management.

Best Regards...


Orhan O. Bag 
General Manager 

 

--------------------------------------------------------------------- 
Issos Enterprises Co. Ltd.     Tel      : ( +90 ) 312 441 27 88 
Cinnah Caddesi 44 / 6          Fax     : ( +90 ) 312 441 27 88 
06680 Cankaya,                   Url      : www.issos.com  
Ankara - TURKEY                 E-mail : [EMAIL PROTECTED]  
---------------------------------------------------------------------


-----Original Message-----
From: Threlkeld, Richard [mailto:[EMAIL PROTECTED] 
Sent: Friday, April 02, 2004 10:34 PM
To: Patch Management Mailing List
Subject: RE: Deploying Office XP SP3 using SMS Feature Pack

Office updates are currently done by tweaking ohotfix.ini.  A good resource
and toolset for automating this can be found at
http://www.myitforum.com/articles/20/view.asp?id=7080 .  

If the inventory for Office is not showing up (for office depending on the
status of an Admin point being set it will show as 'Applicable' or
'AdminApplicable') please ensure that the Office Scan Tool Advertisement is
completing successfully on your clients by looking at SMS Status messages in
the console and by viewing the %Temp%\OfficePatch.log.  Also make sure that
Hardware Inventory is processing the new class in WMI properly by looking
for "CLASS - Process Class: Win32_PatchState" in
%windir%\ms\sms\logs\hinv32.log on the client and verifying that
MICROSOFT|PATCHSTATE is uploading on the server in the
..\SMS\Logs\dataldr.log.

You'll also want to read the Microsoft Systems Management Server Software
Update Services Guide which has a lot of good information and resources to
deploying Office Updates:

http://www.microsoft.com/technet/prodtechnol/sms/sms2/smssusgd.mspx

Richard Threlkeld
Microsoft MVP - SMS
[EMAIL PROTECTED]

Looking to get more involved in the SMS community?
Join the SMS email discussion list today:
http://lists.listleague.com/mailman/listinfo/mssms


-----Original Message-----
From: Matt Will Fix It [mailto:[EMAIL PROTECTED]
Sent: Thursday, April 01, 2004 11:44 PM
To: Patch Management Mailing List
Subject: Deploying Office XP SP3 using SMS Feature Pack

Has anyone had any experience deploying Office XP SP3 using the SMS Feature
Pack?

We are using a patched administrative point, therefore can't install the
client version (OfficeXpSp3-kb832671-client-enu.exe, 16MB) of Office XP SP3.

See http://support.microsoft.com/?kbid=837826

We would like to deploy the full file version
(OfficeXpSp3-kb832671-fullfile-enu.exe, 59MB) to our clients, however the
office patch scanning engine reports that no patches are available.
i.e. its detecting that the client install must be applied, however can't
because the admin point is patched.

Has anyone successfully got the full file patch to work using the Distribute
Software Updates wizard in SMS? Any comments would be great!

Matt

_________________________________________________________________
Find a cheaper internet access deal - choose one to suit you. 
http://www.msn.co.uk/internetaccess


---
To unsubscribe send a blank email to
[EMAIL PROTECTED]


---
To unsubscribe send a blank email to
[EMAIL PROTECTED]


---
To unsubscribe send a blank email to [EMAIL PROTECTED]