Peter van der Woude

There is no real Native Mode anymore.. Now there is the choice between HTTP or HTTPS communication. It's even possible to configure it per role. The needed certificates certificates haven't changed (much) since ConfigMgr 2007. So you should be fine with the old documentation. Take a look here for somebody who already did it: http://www.jamesbannanit.com/2011/04/certificate-requirements-for-sccm-2012/

Also good to know is that, making the boot image available during PXE is now a property of the boot image.

>>> Does this mean there is no update in it at all?? It doesn't matter if they exist within your Search Folders.

Not by default... The only thing you can import (based on a CSV file) are new machines... It's possible to create your own script (based on the SDK) to add machines to a collection.

Correct, or use delta replication (a new feature that came with R3).

Does your update package, by any change, contains any expired or superceded updates?

Nope... It's not possible to create something like auto-approve rules (like in WSUS) in ConfigMgr 2007...

Pinging a computer has nothing to do with SMS or SCCM... so you won't find the needed ports for that in the documentation... to allow ping in the Windows Firewall you need to allow ICMP.

During the update did you also uninstall the old WAIK, and install the new WAIK (with SCCM 2007 SP2)?

Hmm... re-reading my answer, half of it seams to be missing.... For deploying updates via an OSD Task Sequence, can easely be done by advertising the updates to a collection in which the computer exists.

Did you also take a look at this hotfix: http://support.microsoft.com/kb/2023591

If it is with the deployment of software, take a look at the execmgr.log

In short you need an Update Package (which contains the updates), an Update Template (with the default deployment settings), an Update List and an Search Folder (to make the deployment easier)...

R3 is something different then SP2... You need SP2 (and the new WAIK) to get the versions you're looking at..

Did you look at the CAS.log?

It is possible to manage your clients in Domain B (for example with the help of a SLP), just the OSD part makes it harder... maybe even impossible, but it all depends on your demants on that part (for example the client can only join the domain of the OSD).

Take a look here: http://technet.microsoft.com/en-us/library/bb633121.aspx

First use a Build and Capture task sequence, to capture a WIM image. Then use that image to deploy (and if needed add some software to it..)

There is only one schedule alowed per package...

I think you've only got one option... and that's your first one... The other two are not supported...

Take a look at the client logs (smsts & execmgr)

Just create a Direct Membership -rule (in the properties of the Collection).

That's possible.

Copying a hardlink store to a network share is useless, pointless, or whatever word fits better A hardlinkstore is only collecting pointers to local data and not the data itself, so there is no point in saving that to a share...

So, actualy you just want to capture the data twice???