Hi All,

I have deployed SCCM 2007 SP2 R2 for 400 computers, but before to deploy it the environment has already a WSUS infrastructure with is managed by GPO.

Now SCCM 2007 is implemented and I configured Software Update Computer Agent, but it show me 385 computers in Unknown State?

WSUS infrastructure still exist. (WSUS server is using as the Software Update Point for the SCCM as well)

Re

Hi Jose,

Can you verify that the clients are scanning correctly. Check the Last scan by collection report (found on the main website for Software Update in the ConfigMgr. console).

Hello - Also, go through the below technet article to get more information on Software Update Client settings.

http://technet.microsoft.com/en-us/library/bb632393.aspx

Checkout the SCANAGENT.LOG on the c

Do you know if those machines are real, live active computers that are on the network?

 

When I hit an Unknown PC, I always check the SCCM logs. Specifically the execmgr log to see if things are ticking over as expected. I also check the updatedeployment log to ensure that the correct number of deployments are being evaluated without any issues and also to ensure that is clear of any errors.

 

If I don't have these logs then I do a client repair (or a clean and a reistall). If I reinstall I'll then monitor the ccmsetup log file for any issues.

 

I know you have a lot of machines there, but this the trouble shotting I'd start with on one of them.

Firstly you have to check how many machines are live on the network.

Do campare SCCM machine with AD and checked is there any diabled machines which is present in SCCM

Do ping test and try to find how machine are replying .

check last scan time and date , which ever machine are giving response

Check gpresult on one of the failed machine and checck whether it is point to SCCM server.

Lastly check error in Scanagent.log, Wuahandler.log ,windowsupdate.log and post

 

Hi All,

Thanks for replying for my issue.

I was reading some "Unknown State" issues and I found that this happen when you have an existing WSUS infrastructure, which means that  you configure GPO for a all Workstations, so when there is conflict bbeween Software Update Client Agent and GPO.

In my case I've installed Software Update Point in my existing WSUS Server, so I don´t know why workstations are showed in "Unknown State", because they are configured to use my wsus server (Software Update Point) by GPO.

ScanAgent.log

--------------------------------

*****Policy Change notification received for ToolUniqueID={BF35494E-FE8B-4BEE-A74E-64EC406980F2} ScanAgent 1/16/2011 9:02:02 AM 4000 (0x0FA0)
Message received: '<?xml version='1.0' ?> <UpdateSourceMessage MessageType='ScanByUpdateSource'>
  <ForceScan>TRUE</ForceScan>
  <UpdateSourceIDs>
   <ID>{BF35494E-FE8B-4BEE-A74E-64EC406980F2}   </ID>
  </UpdateSourceIDs>
 </UpdateSourceMessage>'
 ScanAgent 1/16/2011 1:47:08 PM 796 (0x031C)
*****ScanByTool request received with ForceReScan=2, ScanOptions=0x0000000a, DownloadPriority = 2, LocationTimeout = 604800, DownloadTimeout = 864000, PerDPInactivityTimeout = 0, TotalInactivityTimeout = 0, DPLocalityFlags = 74, ForceInventory=0 ScanAgent 1/16/2011 1:47:08 PM 796 (0x031C)
-Scan will be requested for ToolUniqueID={BF35494E-FE8B-4BEE-A74E-64EC406980F2} ToolVersion=3.0 ToolName=WSUS Enterprise Server ToolContentVersion=43 ScanAgent 1/16/2011 1:47:08 PM 796 (0x031C)
- - - - - -Locations requested for ToolUniqueID={BF35494E-FE8B-4BEE-A74E-64EC406980F2} (LocationRequestID={F922681B-B9E9-4FDD-B8D2-A065F0A6B05A}), will process the scan request once locations are available. ScanAgent 1/16/2011 1:47:08 PM 796 (0x031C)
- - - -Scan request is queued for ToolUniqueID={BF35494E-FE8B-4BEE-A74E-64EC406980F2} ScanAgent 1/16/2011 1:47:08 PM 796 (0x031C)
- -1 Scan requests added, creating Scan-Job to track these scan requests. ScanAgent 1/16/2011 1:47:08 PM 796 (0x031C)
*****WSUSLocationUpdate received for location request guid={F922681B-B9E9-4FDD-B8D2-A065F0A6B05A} ScanAgent 1/16/2011 1:47:08 PM 796 (0x031C)
CScanTool::Execute- Failed at AddUpdateSource, error = 0x80040692 ScanAgent 1/16/2011 1:47:18 PM 4048 (0x0FD0)
Raising event:
[SMS_CodePage(437), SMS_LocaleID(1033)]
instance of SMS_SUMScanAgentError_UpdateSourceConfigurationFailed
{
 ClientID = "GUID:B773D8BC-3C8A-4E2C-90B6-A5BA3BB69386";
 DateTime = "20110116184718.888000+000";
 ErrorCode = 1682;
 MachineName = "ENERPELIMWDT806";
 ProcessID = 1660;
 SiteCode = "E01";
 ThreadID = 4048;
 UpdateSourceUniqueID = "{BF35494E-FE8B-4BEE-A74E-64EC406980F2}";
 UpdateType = "Microsoft Update";
};
 ScanAgent 1/16/2011 1:47:18 PM 4048 (0x0FD0)
Raising event:
[SMS_CodePage(437), SMS_LocaleID(1033)]
instance of SMS_SUMScanAgentError_ScanFailed
{
 ClientID = "GUID:B773D8BC-3C8A-4E2C-90B6-A5BA3BB69386";
 DateTime = "20110116184718.935000+000";
 ExitCode = 1682;
 MachineName = "ENERPELIMWDT806";
 ProcessID = 1660;
 SiteCode = "E01";
 ThreadID = 1948;
 UpdateSourceUniqueID = "{BF35494E-FE8B-4BEE-A74E-64EC406980F2}";
 UpdateType = "Microsoft Update";
};
 ScanAgent 1/16/2011 1:47:18 PM 1948 (0x079C)
- - - - - -Scan Failed for ToolUniqueID={BF35494E-FE8B-4BEE-A74E-64EC406980F2}, with Error=0x80040692 ScanAgent 1/16/2011 1:47:18 PM 1948 (0x079C)
- -ScanJob (Online scan request) is completed for ToolUniqueID={BF35494E-FE8B-4BEE-A74E-64EC406980F2}. ScanAgent 1/16/2011 1:47:18 PM 1948 (0x079C)
- -Reporting Scan request complete to clients... ScanAgent 1/16/2011 1:47:18 PM 1948 (0x079C)
- - Calling back to client on Scan request complete... ScanAgent 1/16/2011 1:47:18 PM 1948 (0x079C)
CScanAgent::ScanComplete- Scan completion received. ScanAgent 1/16/2011 1:47:18 PM 1948 (0x079C)

----------------------------------

Wuahandler.log

----------------------------------------

Its a WSUS Update Source type ({BF35494E-FE8B-4BEE-A74E-64EC406980F2}), adding it. WUAHandler 1/16/2011 1:47:08 PM 4048 (0x0FD0)
Enabling WUA Managed server policy to use server: http://srvwsus.enersur.isinfra.net:80 WUAHandler 1/16/2011 1:47:08 PM 4048 (0x0FD0)
Waiting for 2 mins for Group Policy to notify of WUA policy change... WUAHandler 1/16/2011 1:47:08 PM 4048 (0x0FD0)
Group policy settings were overwritten by a higher authority (Domain Controller) to: Server http://srvwsus and Policy ENABLED WUAHandler 1/16/2011 1:47:18 PM 4048 (0x0FD0)
Failed to Add Update Source for WUAgent of type (2) and id ({BF35494E-FE8B-4BEE-A74E-64EC406980F2}). Error = 0x80040692. WUAHandler 1/16/2011 1:47:18 PM 4048 (0x0FD0)

------------------------------------------

WindowsUpdate.log

-----------------------------------------------

2011-01-12 12:45:47:162 3840 6dc COMAPI WARNING: Unable to establish connection to the service. (hr=80070422)
2011-01-12 12:48:47:743 1020 b60 Misc ===========  Logging initialized (build: 7.1.6001.65, tz: -0500)  ===========
2011-01-12 12:48:47:743 1020 b60 Misc   = Process: \??\C:\WINDOWS\system32\winlogon.exe
2011-01-12 12:48:47:743 1020 b60 Misc   = Module: C:\WINDOWS\system32\wuaueng.dll
2011-01-12 12:48:47:743 1020 b60 Shutdwn FATAL: WUAutoUpdateAtShutdown failed, hr=80240FFF
2011-01-12 14:27:09:814 1020 c7c Misc ===========  Logging initialized (build: 7.1.6001.65, tz: -0500)  ===========
2011-01-12 14:27:09:829 1020 c7c Misc   = Process: \??\C:\WINDOWS\system32\winlogon.exe
2011-01-12 14:27:09:829 1020 c7c Misc   = Module: C:\WINDOWS\system32\wuaueng.dll
2011-01-12 14:27:09:814 1020 c7c Shutdwn FATAL: WUAutoUpdateAtShutdown failed, hr=80240FFF
2011-01-12 15:18:59:886 1020 ea0 Misc ===========  Logging initialized (build: 7.1.6001.65, tz: -0500)  ===========
2011-01-12 15:18:59:902 1020 ea0 Misc   = Process: \??\C:\WINDOWS\system32\winlogon.exe
2011-01-12 15:18:59:902 1020 ea0 Misc   = Module: C:\WINDOWS\system32\wuaueng.dll
2011-01-12 15:18:59:886 1020 ea0 Shutdwn FATAL: WUAutoUpdateAtShutdown failed, hr=80240FFF
2011-01-12 15:24:43:382  164 148 Misc ===========  Logging initialized (build: 7.1.6001.65, tz: -0500)  ===========
2011-01-12 15:24:43:382  164 148 Misc   = Process: C:\WINDOWS\system32\rundll32.exe
2011-01-12 15:24:43:382  164 148 Misc   = Module: C:\WINDOWS\system32\wuapi.dll
2011-01-12 15:24:43:382  164 148 ARP Connected to update session.
2011-01-12 15:24:43:382  164 148 ARP User is allowed to install published content.

-----------------------------------------------

Did we got any solution for this. Apart from GPO settings changes. I am using same procedure and don't want SCCM do deploy the software updates. it should be deployed from existing WSUS. But reporting should reflect in SCCM. Is there any way to get compliance report

I would suggest you make your own thread rather than attaching your issue here, to an old thread.

That aside, I guess I would try this but only if I used a GPO, so you are commiting to the GPO approach (and in my experience, once you done this there is no going back from using a GPO set Intranet Server Path). You've got two paths for the intranet server location; set the update server as your WSUS FQDN, and then set the reporting point as the FQDN of your Config Manaher SUP.

I would be thinking about the following:

• You'll still need a SUP for compliance data to be returned to/evaluated against.
• You'll need to set the reporting server path as the Config Manager SUP.
• You'll need to have all the updates imported into Config Manager.
• You'll need to have SUGs created containingh te updates, for ease of use.
• You'll need to specifiy the intranet server update path as the WSUS server.

Personally I wouldn't do it this way...