Can you help with these SBS 2011 Winrm errors

Here's a bunch of errors SBS 2011 is giving (even though it seems to work normally). Could you spot any known quick fixes, and patterns in these problems? Often these seem very obscure, but if you've seen these errors, we can often pick them off quick, I hope!

WinRM      142      5/25/2011 2:00:24 PM      237
Event Details:    
WSMan operation SignalShell failed, error code 995
MSExchange CmdletLogs      6      5/25/2011 2:00:24 PM      94
Event Details:    
Cmdlet failed. Cmdlet Get-User, parameters {Identity=NT AUTHORITY\SYSTEM}.
WinRM      129      5/25/2011 2:00:22 PM      66
Event Details:    
Received the response from Network layer; status: 401 (HTTP_STATUS_DENIED)
SharePoint Foundation      6398      5/25/2011 2:00:01 PM      47
Event Details:    
The Execute method of job definition Microsoft.SharePoint.Administration.SPUsageImportJobDefinition (ID c8e6fbe1-b366-443a-851e-6362573edd48) threw an exception. More information is included below. Access to the path ''C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\LOGS'' is denied.
PowerShell      32784      5/25/2011 1:03:06 PM      1
Event Details:    
Runspace Id: f8bd6bc7-c936-45b7-8364-bf2b338921f3 Pipeline Id: 00000000-0000-0000-0000-000000000000. WSMan reported an error with error code: -2144108250. Error message: Processing data from remote server failed with the following error message: The WinRM client cannot complete the operation within the time specified. Check if the machine name is valid and is reachable over the network and firewall exception for Windows Remote Management service is enabled. For more information, see the about_Remote_Troubleshooting Help topic. StackTrace: <null>
WinRM      138      5/25/2011 1:03:06 PM      1
Event Details:    
The client got a timeout from the network layer (ERROR_WINHTTP_TIMEOUT)
DCOM      10016      5/25/2011 12:52:16 AM      9
Event Details:    
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID {000C101C-0000-0000-C000-000000000046} and APPID {000C101C-0000-0000-C000-000000000046} to the user DEPTHBYDISTANCE\spfarm SID (S-1-5-21-2701567934-2922216473-3843076542-1157) from address LocalHost (Using LRPC). This security permission can be modified using the Component Services administrative tool.
SharePoint Foundation      2137      5/25/2011 12:00:19 AM      1
Event Details:    
The SharePoint Health Analyzer detected an error. Product / patch installation or server upgrade required. All required products must be installed on all servers in the farm, and all products should have the same patching and upgrade level across the farm. Upgrade is required on server SERVER. Without the upgrade, the server is not in a supported state. On server CORE, once all required products and/or patches are installed, perform an upgrade by either running PSConfigUI.exe or by executing the command "PSConfig.exe -cmd upgrade -inplace b2b -force -cmd applicationcontent -install -cmd installfeatures". If a former upgrade attempt has failed, you may need to resolve upgrade specific issues before attempting upgrade again. Refer to the upgrade status page (http://core:48237/_admin/UpgradeStatus.aspx) for information about current and prior upgrade attempts, and to determine issues that may be preventing upgrade from succeeding. For more information about this rule, see "".

Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Look here these are all known Post Installation Event Log Errors and Warnings
JeReLoAuthor Commented:
Of the 5 problems listed there, just the first error in my list connects loosely with the last error on that page, but there are differences. I get a different response " 401 (HTTP_STATUS_DENIED)" instead of "503 (HTTP_STATUS_SERVICE_UNAVAIL)"

I have a series of other WinRM errors too.

Can't quite use this solution to eliminate an error.
I see most event id number come allong but the content is different,

For the Sharepoint event id 6398: look here:

The DCOM Eventid 10016 is in the link I posted, please check the link again.

And for the Sharepoint Foundation Event id 2137, look at this article:

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
IT Pros Agree: AI and Machine Learning Key

We’d all like to think our company’s data is well protected, but when you ask IT professionals they admit the data probably is not as safe as it could be.

JeReLoAuthor Commented:
Progressing through sharepoint event id 2137, when the directions say to set modify permissions for the wss_admin_wpg account, what are the specific permissions I need to use. Modify is not an option. I can allow traverse, list, read, etc. Could you clarify the set that author intends by requesting modify permission?

Thanks for the good links, I'll start to work through those soon.
JeReLoAuthor Commented:
Oops. Above, I should have written sharepoint event id 6398 or 
JeReLoAuthor Commented:
Also, I'm opening a second more detailed question, related to the WinRM issue. You're welcome to focus on that separately at winrm config
You have to try if you could do it with less security rights.
If you set modify it will work I just tested on a test server and that worked fine.
JeReLoAuthor Commented:
Oh, I see modify if I use edit, but when you use advanced edit, there's no modify.

Anyway, thanks alot for the several errors you spotted. All were corrected.
It is right that when you do advanced you don't see modify, modify is a bundle of rigths, when you do advanced you can change the rigths all seperate. So when a group had modify rights on a folder and you choose advanced, all checked rights belong to the modify set.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.