Jump to content


  • 0
TronixS

Updates for Workstation with SCCM 2007 ?!?!?

Question

Hello,

 

we are testing SCCM 2007 SP1 R2 to installing Clients (WXP SP 1 / SP 2 / SP 3 and Vista) but there are many Problems.

 

We have a little Group of Maschines they are installing with no Problems and other doesn´t run, the find many updates (60 - 75) but they do nothing.

 

the Logs are not really helpful. The SCCM Client for our Test i deploy per GPO what goes fine.

 

Now i would find anyone where has same Problems or Tipps to fix it.

 

A College tells me i should create more Update Packages for the deploy but i don´t will do this, it is more Work for me.

 

Big thx for helpful informations..... ;)

 

with best regards........

 

André

Share this post


Link to post
Share on other sites

Recommended Posts

  • 0

you'll need to provide us with logs from a failing machine, do all the machines have the same version of the SCCM client installed ? are all the working machines in the same collection ?

Share this post


Link to post
Share on other sites

  • 0

Ok,

 

i install directly a new Workstation with XP SP2 and Office 2003 SP1, then i will try a automaticly update and post the Reports.

 

The ConfigMgr Clientversion 4.0.0.6221.1000

 

our Consulting tells us that is normal to deploy not all Updates (28max Patches) as one Pak, we must do more Groups for Deployupdates in more Steps.

 

i can´t believe this, in my test with WSUS 3.01 i don´t have this Problems but our Firma would take SCCM 2007 and in background runs WSUS 3.01......

 

Okay, in ca. 60Min, the Client is Ready and i will Post the Logs...

 

Big thx for this time.

Share this post


Link to post
Share on other sites

  • 0

Okay,

 

this is strange, now i had a "normal" Windows Update Message to Install KB898461 per Express or from Hand.

 

but i have now enough logs and post them as files in a ZIP.

 

in the SCANAGENT.LOG is this a Part of Error.

 

*****WSUSLocationUpdate received for location request guid={8140EB31-A06D-4B91-AF27-D4BA388472B5} ScanAgent 10.11.2008 12:07:01 3060 (0x0BF4)

- - - - - -Scan completed successfully for ToolUniqueID={7C7DE67C-8C3A-42EA-A627-039624445B7C}, ScanType=1, ContentVersion=59 ScanAgent 10.11.2008 12:10:58 3796 (0x0ED4)

- -ScanJob (Online scan request) is completed for ToolUniqueID={7C7DE67C-8C3A-42EA-A627-039624445B7C}. ScanAgent 10.11.2008 12:10:58 3796 (0x0ED4)

- -Reporting Scan request complete to clients... ScanAgent 10.11.2008 12:10:58 3796 (0x0ED4)

- - Calling back to client on Scan request complete... ScanAgent 10.11.2008 12:10:58 3076 (0x0C04)

CScanAgent::ScanComplete- Scan completion received. ScanAgent 10.11.2008 12:10:58 3076 (0x0C04)

- -Processing Scan tool history removal request ScanAgent 10.11.2008 12:17:35 4080 (0x0FF0)

*****ScanByUpdates request received with ForceReScan=0, ScanOptions=0x00000008, DownloadPriority = 2, LocationTimeout = 604800, DownloadTimeout = 864000, PerDPInactivityTimeout = 0, TotalInactivityTimeout = 0, DPLocalityFlags = 10, ForceInventory=0 ScanAgent 10.11.2008 12:17:36 3692 (0x0E6C)

-Scan will be requested for ToolUniqueID={6BFFF379-09FE-4BFC-B853-2F38804D2AD7} ToolVersion=4.00.6221.1000 ToolName=ConfigMgr-Überprüfungsprogramm für Microsoft Updates ToolContentVersion=5 ScanAgent 10.11.2008 12:17:36 3692 (0x0E6C)

-Scan will be requested for ToolUniqueID={7C7DE67C-8C3A-42EA-A627-039624445B7C} ToolVersion=3.0 ToolName=WSUS Enterprise Server ToolContentVersion=59 ScanAgent 10.11.2008 12:17:36 3692 (0x0E6C)

CScanTool::RequestContentFromCAS - failed at RequestContent for ToolUniqueID {6BFFF379-09FE-4BFC-B853-2F38804D2AD7} with Error=0x80070057 ScanAgent 10.11.2008 12:17:36 3692 (0x0E6C)

Raising event:

[sMS_CodePage(850), SMS_LocaleID(1031)]

instance of SMS_SUMScanAgentError_ContentDownloadFailed

{

ClientID = "GUID:3290F89E-192D-425B-9164-62587CA5852E";

ContentID = "";

ContentVersion = "5";

DateTime = "20081110111736.703000+000";

MachineName = "W14739";

ProcessID = 1804;

SiteCode = "NDH";

ThreadID = 3692;

UpdateSourceUniqueID = "{6BFFF379-09FE-4BFC-B853-2F38804D2AD7}";

UpdateType = "Microsoft Update";

};

ScanAgent 10.11.2008 12:17:36 3692 (0x0E6C)

CScanTool::Scan- failed at RequestContentFromCAS for ToolUniqueID={6BFFF379-09FE-4BFC-B853-2F38804D2AD7} with Error=0x80070057 ScanAgent 10.11.2008 12:17:36 3692 (0x0E6C)

CScanToolManager::CreateNewScanTool- failed at CScanTool::Scan() with Error=0x80070057 ScanAgent 10.11.2008 12:17:36 3692 (0x0E6C)

CScanToolManager::AddScanTool- failed to create new ScanTool for ScanToolsID={6BFFF379-09FE-4BFC-B853-2F38804D2AD7} with Error=0x80070057 ScanAgent 10.11.2008 12:17:36 3692 (0x0E6C)

CScanJobManager::Scan- failed at AddScanTool for ToolUniqueID={6BFFF379-09FE-4BFC-B853-2F38804D2AD7}, with error=0x80070057, skipping this tool ScanAgent 10.11.2008 12:17:36 3692 (0x0E6C)

CScanTool::Scan- Requesting Offline Scan for ToolUniqueID={7C7DE67C-8C3A-42EA-A627-039624445B7C} with last known location and version=59 ScanAgent 10.11.2008 12:17:36 3692 (0x0E6C)

- - - -Scan request is queued for ToolUniqueID={7C7DE67C-8C3A-42EA-A627-039624445B7C} ScanAgent 10.11.2008 12:17:36 3692 (0x0E6C)

- -1 Scan requests added, creating Scan-Job to track these scan requests. ScanAgent 10.11.2008 12:17:36 3692 (0x0E6C)

Message received: '<?xml version='1.0' ?> <UpdateSourceMessage MessageType='ScanByUpdateSource'>

<ForceScan>TRUE</ForceScan>

<UpdateSourceIDs>

<ID>{7C7DE67C-8C3A-42EA-A627-039624445B7C} </ID>

</UpdateSourceIDs>

</UpdateSourceMessage>'

ScanAgent 10.11.2008 12:17:51 2268 (0x08DC)

 

 

Big Thx for help and sorry for my bad english ;)

 

André

Logs.zip

Share this post


Link to post
Share on other sites

  • 0

Okay, Error Code 0x8007057 is a Probleme when a client becomes a lot of Updates or Patches.

 

My Version was .784 but i must upgrade to .788 (it´s WindowsUpdater x86 http://support.microsoft.com/kb/949104 )

 

I did it but after a Reboot with the new installer is there a same Error in UpdaterHandler.log

 

Updates scan completion received, result = 0x80070057. UpdatesHandler 10.11.2008 14:02:49 2400 (0x0960)

 

omg

Share this post


Link to post
Share on other sites

  • 0

No,

 

all Systems are the Same Problem, when i make a Big ALLUPDATES File find the Client over 30 or more Patches, it looks fine but the Client makes nothing.

 

When i split many Updates in little Parts runs this, the Client detect Updates and install them.

 

The Windows Update Agent is the last and ends with .788 (from Oktober).

 

thx.

Share this post


Link to post
Share on other sites

  • 0

i've tested this and it works fine with lots of updates in the update list

 

have a look at my software update point howto

 

maybe you've missed some steps ?

 

in your WUAhandler.log file I see this

 

<![LOG[Group policy settings were overwritten by a higher authority (Domain Controller) to: Server and Policy NOT CONFIGURED]LOG]!><time="11:21:34.140+-60" date="11-10-2008" component="WUAHandler" context="" type="3" thread="2004" file="sourcemanager.cpp:1107">

 

<![LOG[Failed to Add Update Source for WUAgent of type (2) and id ({7C7DE67C-8C3A-42EA-A627-039624445B7C}). Error = 0x80040692.]LOG]!><time="11:21:34.140+-60" date="11-10-2008" component="WUAHandler" context="" type="3" thread="2004" file="cwuahandler.cpp:2358">

 

so, do you have a group policy setup pointing to the WSUS server ? if so that is not correct and needs to be disabled.

 

SCCM must handle all the updates itself not wsus

 

cheers

anyweb

Share this post


Link to post
Share on other sites

  • 0

Hi Anyweb,

 

a great start to 2009.

 

big thanks for your help, i have fixed the GPO but the Problem is the same.

 

i have installed a Vista Client and he would now 91 Updates but the computer do nothing. 15 Updates are installed and now he do nothing.

 

In Wuahandler.log is no actual error but in the CAS.LOG is Error called 0x80070057

 

CachedContentInfo::InitializeFromWmi	ContentAccess	06.01.2009 11:27:17	2756 (0x0AC4)
CachedContentInfo::InitializeFromWmi succeeded	ContentAccess	06.01.2009 11:27:17	2756 (0x0AC4)
Loaded CacheInfo for d760d61f-1684-4b14-a93f-dc76b285e90f and 1 from Wmi	ContentAccess	06.01.2009 11:27:17	2756 (0x0AC4)
Cached CCM (user, session) is: (S-1-5-21-8915387-44578016-1575050150-1086,1).	ContentAccess	06.01.2009 11:27:17	2756 (0x0AC4)
::GetSMSConsoleSessionId - SMS Console Session ID is: 1	ContentAccess	06.01.2009 11:27:17	2756 (0x0AC4)
WTSQueryUserToken[2](SessionID=1) retried 0 times!	ContentAccess	06.01.2009 11:27:17	2756 (0x0AC4)
No linked token found	ContentAccess	06.01.2009 11:27:17	2756 (0x0AC4)
wcslen(pwszContentId) > 0, HRESULT=80070057 (e:\nts_sms_fre\sms\client\softmgmtagent\contentaccess\contentaccessservice.cpp,553)	ContentAccess	06.01.2009 11:27:17	2756 (0x0AC4)
RequestContentEx2(pwszContentId, pwszContentVersion, eContentType, dwSource, dwContentSizeInKiloByte, guidNotifyClsId, bProgressNotificationReqd, pwszUserSid, ulCallerState, ulHashListSize, pwszSourceContentHash, eDownloadPriority, dwLocationTimeout, dwDownloadTimeout, dwPerDPInactivityTimeout, dwTotalInactivityTimeout, guidRequestHandle, bDoNotRunFromCache, dwPersistInCache, L""), HRESULT=80070057 (e:\nts_sms_fre\sms\client\softmgmtagent\contentaccess\contentaccessservice.cpp,493)	ContentAccess	06.01.2009 11:27:17	2756 (0x0AC4)
RequestContentEx2 failed with the error code 0x80070057	ContentAccess	06.01.2009 11:27:17	2756 (0x0AC4)

 

 

did you have another idea to fix it?!

 

I have read your Guideline for Updates, great Stuff, and i do it so, many of them but i don´t know my Problems.

 

cya.

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Answer this question...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...


×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.