Peter van der Woude

Then it has to be that this is still your problem: [LOG[CLibSMSMessageWinHttpTransport::Send: URL: RIO.SINT-MARIA.LOCAL:80 CCM_POST /ccm_system/request]LOG] [LOG[Error. Received 0x80072ee7 from WinHttpSendRequest.]LOG] [LOG[unknown host (gethostbyname failed)]LOG] [LOG[hr, HRESULT=80072ee7 (e:\nts_sms_fre\sms\framework\osdmessaging\libsmsmessaging.cpp,7714)] [LOG[sending with winhttp failed; 80072ee7]LOG] Did you try to resolve the FQDN of RIO.SINT-MARIA.LOCAL on the client? Did you also try to connect to the share of the DP?

I see that I didn't copy the link good.... This link is about How to Configure the Network Access Account: http://technet.microsoft.com/en-us/library/bb632397.aspx This link is About the Network Access Account: http://technet.microsoft.com/en-us/library/bb680398.aspx

Failed to access the share \\RIO.SINT-MARIA.LOCAL\SMSPKGC$\SMS00029\ with network access account --> Did you set up a Network Access Account (as described here: http://technet.microsoft.com/en-us/library/bb632397.aspx)? If so, did you verify that you could connect to the share with that account?

As you are not running in Native Mode, the certificates can't be a problem either. In your log I see gethostbyname failed, this most times indicates problems with DNS and/or DHCP

Are you running Native or Mixed Mode?

That explains a lot. The File Contents option will show from the moment that you start a search.

Ehmm... Maybe I just don't get your question, but it (your screenshot) just says Search again in: Libraries Custom Internet File Contents

It's indeed not possible to remove a computer from the All Systems Collection. That's one of the reasons why I would never advise to Advertise to the All Systems Collection.

Check your Program Properties. Make sure that on the Advanced tab Allow this Program... ...being Advertised is selected.

Well.. it's pretty straight foward. Just create a new custom Task Sequence and add the Programs that you want to install.

A Task Sequence can also be a good solution. When there are a lot of dependencies I would use a Task Sequence (keep in mind that a Task Sequence can only be deployed to computers and not to users). When there are just one or two programs then I would use the solution of jamitupya.

Well... My honest opinion is that if somebody wants to test SCCM they should run in Mixed Mode... That doesn't mean that you (we) shouldn't make Installation Guides for setting up Certificate Services, but it does mean (at least for me) that when you make a guide for Certificate Services you should do it "good". I think that when somebody wants to setup SCCM in Native Mode they should be an advanced user allready and they should know about Certificate Services. I would at least mention the basic Certificates as described here: http://technet.microsoft.com/en-us/library/cc872789.aspx Keep up the good work!

Ehmm... Are you using the Root Certificate all the different types of communication???

That's why you can install WebDAV as a part of your IIS installation in Windows Server 2008 R2 (by adding Roles and Features)

I've got no clue if there is any way to tell, whether or not the certs are correct... The only thing you can do is check with the Microsoft documentation... Most of the times when you get the error Signature verification failed for PolicyAssignmentID it has to do with a mismatch between the Client certificate and the Site Signing Certificate.

I know that setting up a Site in Native Mode can be really frustrating... and when I am looking at the first error that you mentioned Signature verification failed for PolicyAssignmentID it looks like you've got some certificate problems...

The image that you use, is that created in a different domain? If so, then take a look here: http://www.petervanderwoude.nl/post/Prepare-ConfigMgr-Client-for-Capture-doesne28099t-remove-the-AllowedRootCAHashCode-value.aspx

I saw this error before... I don't know what causes this error, but I do know that pointing the package specifically to or x86 or x64 works arround it...

Take a look here: http://www.windows-noob.com/forums/index.php?/forum/63-deploy-7/

MPSetup.log <12-02-2009 08:56:41> mp.msi exited with return code: 1603 <12-02-2009 08:56:41> Backing up C:\Program Files (x86)\Microsoft Configuration Manager\logs\mpMSI.log to C:\Program Files (x86)\Microsoft Configuration Manager\logs\mpMSI.log.LastError <12-02-2009 08:56:41> Fatal MSI Error - mp.msi could not be installed. mpMSI.log (always search for "Return value 3") [14:45:20] @@ERR:25006 MSI (s) (7C!40) [14:45:20:952]: Product: SMS Management Point -- Error 25006. Setup was unable to create the Internet virtual directory CCM_Incoming The error code is 80070005 Error 25006. Setup was unable to create the Internet virtual directory CCM_Incoming The error code is 80070005 CustomAction CcmCreateIISVirtualDirectories returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox) MSI (s) (7C:14) [14:45:20:993]: User policy value 'DisableRollback' is 0 MSI (s) (7C:14) [14:45:20:993]: Machine policy value 'DisableRollback' is 0 Action ended 14:45:20: InstallFinalize. Return value 3. [...] [14:45:24] The service 'ccmexec' is not installed MSI (s) (7C:14) [14:45:24:927]: Note: 1: 2318 2: MSI (s) (7C:14) [14:45:24:928]: No System Restore sequence number for this installation. MSI (s) (7C:14) [14:45:24:928]: Unlocking Server MSI (s) (7C:14) [14:45:24:931]: PROPERTY CHANGE: Deleting UpdateStarted property. Its current value is '1'. Action ended 14:45:24: INSTALL. Return value 3.

Did you already get it to work? If not, what are your IIS and WebDAV Settings?

Did you also edit the Bindings in IIS to add the/ a certificate? And did you already deploy a different OS, or is this the first try?

By installing a PXE Service Point, SCCM will configure WDS for you. So do not configure WDS yourself.

Did you install the PXE Service Point on the same server as WDS? And did you also let SCCM configure WDS?

I indeed installed SQL 2008 SP1 locally including SQL Reporting. Keep in mind that since ConfigMgr 2007 R2 you 've got two types of reporting in ConfigMgr. There is the basic Reporting Point and there is the Reporting Service Point. The Reporting Services Point uses (and needs) SQL Reporting. See also: http://technet.microsoft.com/en-us/library/cc161824.aspx