Re: SUS
From: Jennifer Lesher [MS] (jennle@online.microsoft.com)
Date: 04/11/03
- Previous message: BlueBearr: "Secedit permissions not applied"
- In reply to: Danny Sanders: "Re: SUS"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
From: jennle@online.microsoft.com ("Jennifer Lesher [MS]") Date: Fri, 11 Apr 2003 21:53:52 GMT
Hi Danny,
Thanks for the followup. Glad to hear your updates are working now :-)
Sincerely,
Jennifer Lesher
MCSE/MCDBA
Microsoft Online Support
This posting is provided "AS IS" with no warranties, and confers no rights.
Get Secure! - www.microsoft.com/security
|
| Thanks for the info I believe I got it working now.
|
|
| DDS
| ""Jennifer Lesher [MS]"" <jennle@online.microsoft.com> wrote in message
| news:TwNMO38$CHA.2380@cpmsftngxa06.phx.gbl...
| > Hello Danny,
| >
| > On SP3 installations this can be caused by update Q329414. Removing the
| > update should fix the SUS problem, but removing it can cause a security
| > problem unless you are on MDAC 2.7. If you're curious to read more
about
| > Q329414, please see:
| >
| > 329414 MS02-065: Buffer Overrun in Microsoft Data Access Components Can
| > Lead to
| > http://support.microsoft.com/?id=329414
| >
| > There is a way around this though. I would suggest that you first check
| > the MDAC version, using one of the following methods. Method 2 is
| probably
| > OK for you, because the caveat about the registry check being invalid
| > really applies only to MDAC 2.1 and previous. But, if you want to be
| > really, really sure, use Method 1:
| >
| > If you're not on MDAC 2.7, please install it before removing Q329414.
| > Get MDAC 2.7 here:
| >
|
http://www.microsoft.com/downloads/details.aspx?FamilyID=9ad000f2-cae7-493d-
| > b0f3-ae36c570ade8&DisplayLang=en
| >
| > Please check your MDAC version after the install, to make sure it truly
| > updated. Then you can remove Q329414, and, we hope, then have SUS work
| > properly.
| >
| >
| > Method 1:
| > Install and Use the Component Checker Tool
| > ------------------------------------------
| > The most reliable way to determine which version of MDAC is installed
is
| > to compare the version number of each MDAC DLL file to a list of the DLL
| > files that are shipped with each MDAC version. The Component Checker can
| > help you to do this. It checks the files on the computer, compares them
to
| > a list from each version of MDAC, and reports the closest match.
| > To install Component Checker, follow these steps:
| >
| > 1. Browse to the following Microsoft Web site:
| >
| > http://www.microsoft.com/data/download.htm#CCinfo
| >
| > 2. Click the link to download Component Checker. When you are prompted
by
| > the browser, save Cc.exe (a self-extracting executable file) to the
| desktop.
| >
| > 3. On the desktop, double-click Cc.exe; this extracts the Component
| Checker
| > files and installs to the default location, C:\Comcheck. To use
Component
| > Checker to check the MDAC version, follow these steps:
| > 1. From the Start menu, click Run.
| >
| > 2. In the Open text box, type "c:\comcheck\comcheck.exe" (without the
| > quotation marks) and then click OK.
| >
| > 3. In the Component Checker - Choose Analysis Type dialog box, select
| > Perform Analysis of your machine and automatically determine the release
| > version, and then click OK.
| >
| > 4. The program attempts to identify the MDAC version on your computer by
| > scanning all of the core MDAC files and registry settings. This process
| > normally takes several minutes. When finished, you should receive the
| > following message: The MDAC version that is closest to the version on
your
| > computer is 'XXXX'
| > 5. Click OK.
| >
| > 6. A summary of the Component Checker scan appears. Note that the Dir,
| > FileDescription, and FileSize errors can be safely ignored.
| >
| > Method 2:
| > Check the Version Information Stored in the Registry
| > ---------------------------------------------------
| > Although not the most reliable way to check the MDAC version, checking
| > the registry for the version information is an easy way to double-check
| > this information (if you are not experiencing any MDAC-related issues).
| > The version information is found in the following key:
| >
| > HKEY_LOCAL_MACHINE\Software\Microsoft\DataAccess\FullInstallVer
| > To check the registry, follow these steps:
| >
| >
| > 1. On the Start menu, click Run.
| > 2. In the Open text box, type "regedit" (without the quotation marks)
and
| > then click OK; this starts Registry Editor.
| > 3. In the Navigation pane, drill-down to the following path:
| > HKEY_LOCAL_MACHINE\Software\Microsoft\DataAccess
| >
| > 4. In the Details pane, look in the Name column for FullInstallVer and
| > Version. Each of these keys will have corresponding version information
in
| > the Data column.
| >
| > 5. When finished, click Exit on the Registry menu to close Registry
| Editor.
| >
| > Please let me know if this solves your problem or if you would like
| further
| > assistance.
| >
| > I look forward to hearing from you.
| >
| > Sincerely,
| >
| > Jennifer Lesher
| > MCSE/MCDBA
| > Microsoft Online Support
| >
| > This posting is provided "AS IS" with no warranties, and confers no
| rights.
| >
| > Get Secure! - www.microsoft.com/security
| >
| >
| > |
| > | Updates are not installing from the SUS server. GP is working properly
| > | because I can change a property in the GP controlling SUS behavior
run a
| > | secedit refresh for the machine policy on the client and see the
change
| > | passed to the client.
| > | SUS has downloaded all updates, client is Win 2k SP3. In control
Panel,
| > on
| > | the client, using the Automatic Update Icon everything is grayed out
(as
| > it
| > | should be) I can change the time in GP that the client computer is
| > supposed
| > | to download and install updates, run secedit and refresh the policy
and
| I
| > | can see the time change on the Automatic Updates app even though I can
| not
| > | change it.
| > |
| > | From this same client I have went to the Windows Update service and
had
| it
| > | scanned for updates and 23 critical updates are missing. I have been
| > | changing the update time hourly (in the GP) for testing, I can see the
| > time
| > | change on the client. After the time the client was *supposed* to
update
| > | with the SUS server, I have rebooted the client, went to MS Windows
| > Updates
| > | site, had the client scanned, and there is still 23 updates missing.
| > |
| > | Is there a log file created? How can I get this working?
| > |
| > | TIA
| > | DDS
| > |
| > |
| > |
| > |
| >
|
|
|
- Previous message: BlueBearr: "Secedit permissions not applied"
- In reply to: Danny Sanders: "Re: SUS"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
|
