Peter van der Woude

No network blocking traffic?

Same as before: Serverlogs <installationdirectory>\Logs Clientlogs a level lower \SMS_CCM\Logs

Did you check the logs that should be created?

The client files and logs are now a level higher - C:\Windows\CCM

You can find it with Monitoring > Deployments.

Is there anything back at all?? It sounds like it's not capturing/restoring at all...

Is the Client Push Installation account local admin on the remote machine? Is the Firewall open to/ on the clients?

Did you try if the 2008 workaround works? Another option is to use DISM.

The actions mentioned in this article can certainly NOT do that. Main reason is that there are also hardlinks used. These are local pointers to the data and the reason why this proces is so quick. Back to your question. If you want to use a networkstorage why NOT using a SMP?

How did you configure your inventories?

I would first take a look at the clientlocation.log and the locationservices.log.

Take a look here: http://ccmexec.com/?p=787

Did you use a new Site Code? Did you create Boundaries? Is the new Site allowed to write in the AD?

For what purpose? As this is still a BETA product...

You need to take a look at part 7 of the guides. Did you follow all those step? If so, then at what point does it go broke? And what's in the smsts.log?

ConfigMgr 2007 does NOT support a Secondary Site in a remote/ separate forest. Take a look here for more information: http://technet.microsoft.com/en-us/library/bb694003.aspx

That is probably caused by the WDS/ PXE Cache. By default the cache is being held for 60 minutes. Take a look here for more information: http://support.microsoft.com/kb/2019640

You will also need to use SCUP for that.

Take a look at the guides here: http://www.windows-noob.com/forums/index.php?/forum/92-v-nextsccm-2012/

Just use the (un)installation wizard (see also: http://technet.microsoft.com/en-us/library/bb680572.aspx)

Then you need to extract it. Most times this can be done with <installer>.exe /extract , if it doesn't work then try <installer>.exe /? to see what the possibilities are.

Not being able to push to Domain Controllers is almost always a rights issue. The Push account is probably not a Local Admin on the Domain Controller

Take a look here: http://www.systemcentercentral.com/Forums/tabid/60/indexId/71344/Default.aspx?tag=Forums+Config_Manager#vindex71388

As an addon to Eswar. As the laptops are not in the domain, did you create a Boundary for those machines?

You indeed need to Sysprep the machine, because that takes care of things like the computername / SID's / Caches etc.