Tuesday, November 17, 2009

Troubleshooting SCCM Software package distribution

Disclaimer… while writing this post I noticed a lot of errors all over the place under system status. These issues I encountered were encountered yesterday without all of these errors occurring. I will start looking into the errors however from first glance they appear to be WSUS related which is not what I’m writing about here. I did notice a management point error explaining it’s not responding to HTTP requests (I just installed the Reporting Point yesterday so there might be a conflict between the two items using port 80?).

What I am trying to figure out is why my test machine isn't responding to advertisements... I am trying to figure this out because obviously the software isn't installing from the pack.

Here's what I have configured...

I followed The instructions from here to configure SCCM however I did it on a windows 2003 server instead of 2008. It is a virtual Server running on VMWare ESXI. I have not extended the schema or added anything via adsi edit.

I have successfully setup deployment of Windows XP for multiple versions of hardware which include software and driver installation specific to the hardware.

This software package I created is the first package so far. It is adobe reader 9. I set the package up by creating a transform file through Adobe's Customization Wizard 9.




Here is the command line listed in the software pack which works if I run it manually from a computer... *(I mean from the command line I can run this command but obviously because it is remotely and manual I have to designate the full network paths of the files)

- What I am noticing is that the PC’s Configuration manager does not know what SCCM site it is in.























- I am not seeing any advertised software from "Run Advertised Programs


















- I am also getting a lot of warnings on the client when I try to run the “repair” from the configuration manager.



Event Type: Warning
Event Source: WinMgmt
Event Category: None
Event ID: 63
Date: 11/16/2009
Time: 4:47:30 PM
User: NT AUTHORITY\SYSTEM
Computer: THIRDIMAGE

Description:
A provider, PolicyAgentInstanceProvider, has been registered in the WMI namespace, root\ccm\Policy\S_1_5_21_1504005034_1371222036_1539857752_8570, to use the LocalSystem account. This account is privileged and the provider may cause a security violation if it does not correctly impersonate user requests.


Event Type: Warning
Event Source: WinMgmt
Event Category: None
Event ID: 63
Date: 11/16/2009
Time: 4:47:30 PM
User: NT AUTHORITY\SYSTEM
Computer: THIRDIMAGE

Description:
A provider, PolicyAgentInstanceProvider, has been registered in the WMI namespace, root\ccm\Policy\Machine, to use the LocalSystem account. This account is privileged and the provider may cause a security violation if it does not correctly impersonate user requests.

Event Type: Warning
Event Source: WinMgmt
Event Category: None
Event ID: 63
Date: 11/16/2009
Time: 4:47:30 PM
User: NT AUTHORITY\SYSTEM
Computer: THIRDIMAGE
Description:

A provider, AMTInvProvider, has been registered in the WMI namespace, root\cimv2\SMS, to use the LocalSystem account. This account is privileged and the provider may cause a security violation if it does not correctly impersonate user requests.






Event Type: Warning
Event Source: WinMgmt
Event Category: None
Event ID: 63
Date: 11/16/2009
Time: 4:47:29 PM
User: NT AUTHORITY\SYSTEM
Computer: THIRDIMAGE

Description:
A provider, AMTProvisionProvider, has been registered in the WMI namespace, root\CCM, to use the LocalSystem account. This account is privileged and the provider may cause a security violation if it does not correctly impersonate user requests.

Event Type: Warning
Event Source: WinMgmt
Event Category: None
Event ID: 5603
Date: 11/16/2009
Time: 4:47:29 PM
User: NT AUTHORITY\SYSTEM
Computer: THIRDIMAGE
Description:
A provider, BcdProv, has been registered in the WMI namespace, root\wmi, but did not specify the HostingModel property. This provider will be run using the LocalSystem account. This account is privileged and the provider may cause a security violation if it does not correctly impersonate user requests. Ensure that provider has been reviewed for security behavior and update the HostingModel property of the provider registration to an account with the least privileges possible for the required functionality.

Event Type: Warning
Event Source: WinMgmt
Event Category: None
Event ID: 63
Date: 11/16/2009
Time: 4:47:27 PM
User: NT AUTHORITY\SYSTEM
Computer: THIRDIMAGE

Description:
A provider, AAInstProv, has been registered in the WMI namespace, root\cimv2\sms, to use the LocalSystem account. This account is privileged and the provider may cause a security violation if it does not correctly impersonate user requests.






- Now from the server side what I did was create a collection with this query to designate the security group I created for this package named adobe reader 9.
select.

SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,SMS_R_SYSTEM.SMSUniqueIdentifier,SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client from SMS_R_System where SMS_R_System.SystemGroupName = "RMS\\Adobe Reader 9"




















- This is what I am seeing with regard to the Advertisement status for this package.











- When I look at a report of the active advertisements I see this
Report Name:
Status of a specific advertisement
Category:
Software Distribution - Advertisement Status
Comment:





- This report shows the status summary of all resources that have been targeted by an advertisement. The summary is broken into two parts. Acceptance status will summarize how many resources have received, rejected, or not yet received the advertisement. Delivery status will summarize the resources that have run or attempted to run the program being advertised.
Parameters:
Advertisement ID
RG62000B
Status of a specific advertisement
Top of Form
11/17/2009 9:31:34 AM
(Number of Records: 0)
No matching records could be found.

11/17/2009 9:31:34 AM
(Number of Records: 0)

Bottom of Form

Monday, November 02, 2009

Setting up a build and capture on SCCM2007 for Windows XP SP3

Originally following this guide http://www.windows-noob.com/forums/index.php?/topic/1064-sccm-2007-guides/


Found HRESULT=8007005 and "failed to connect to tstsccm but investigating that error didn't get me anywhere.

The error 0x80040103 combined with LOG[Failed to connect to "\\tstsccm\smspkge$\rc00006 which was the package for the client install that I installed before. per this comment

"if that package definetly exists and you can browse to it from another computer then simply try to recreate the package again (remove old one, delete it from DPs and recreate the package,

sometimes I've seen times where a package looks ok, can be accessed ok but fails in OSD and sometimes the only fix is to rebuild and redistribute the package"

From http://social.technet.microsoft.com/Forums/en-US/configmgrosd/thread/14732dc4-5f5d-4019-8c10-f45f5c5f09cc

I removed and recreated the package and then removed and recreated the task sequence and advertisement. I tried again and got the same error but this time on the package for the boot image.

Researching that error on the boot image led me to this comment
"i think i have cracked it.

i did not set the network access account in the client agent setting initially. once i set that, the task sequence has started. "

from http://www.windows-noob.com/forums/index.php?/topic/587-task-sequence-not-working/page__hl__0x80040103__fromsearch__1

which then gave a link on instructions on how to do this here http://www.windows-noob.com/forums/index.php?/topic/491-how-can-i-configure-sccm-2007-sp1-in-windows-server-2008/

I followed the instructions to configure the client agent properties. I added an account for read access and made it a basic user then added that user.

Tried it again and that worked.

About Me