Peter van der Woude

You should download the updates to a Deployment Package and add the package to a Distribution Point. That's where the client will look for the updates.

Check the execmgr.log for more information.

Your PXE log is full with errors like this: <![LOG[still unable to delete folder C:\Windows\TEMP\PXEBootFiles\ (0x80070091) after 31 retries. Continue without further retry.]LOG]!><time="17:33:10.455+-120" date="08-30-2012" component="smspxe" context="" type="1" thread="3336" file="ccmfile.cpp:1135"><![LOG[Warning: Failed to copy the needed boot binaries from the boot image E:\RemoteInstall\SMSImages\SMSPKG\00A00037\sources\boot.wim. Cannot create a file when that file already exists. (Error: 800700B7; Source: Windows). You might want to look what's going on there, as they are pretty self explaining...

What steps did you perform to deploy the updates tp the client?

Please provide more information... Did you for example look at the client logfiles? If so, what did you see?

Have you enable the Software inventory? The default rules of Asset Intelligence are based on the inventory information...

About the logs, check AppEnforce.log for applications and execmgr.log for packages.

AFAIK it's, at this moment, only available as a part of Windows ADK

There is a building report Memory information for a specific computer. When you mean usage information than you need SCOM, SCCM doesn't collect usage information.

Did check the smspxe.log with the last try?

Did you check the client logs?

The biggest reasonis that if you have ten companies, you've got ten naming conventions for computers... There is no one solution fits all with this, not even close, that's why there are so many scripts, hta's and tools in the community for that.

Actually, I had the same error in my lab last week. A simple restart and starting the task sequence again "solved it"...

Take a look in the mpMSI.log for the real error.

You can only run loadstate with store created by a scanstate action.

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

Yes you should create new packages with the updated files.

I think you've got a big challenge there... You might be able to copy data during the loadstate to the new disk, but I have no idea how you want to copy it in to the profile then....

When you have DHCP and SCCM/WDS on one box, you should also be sure that they are not both listening to the same port..

Depends... You could create a script to trigger updates on collections, but it does generate load and it requires the computer to be member of the ad group already...

What do you mean? Roles and Features of Windows, or Roles of ConfigMgr?

Then there is nothing being installed.

See also: http://blogs.technet.com/b/mniehaus/archive/2012/07/31/mdt-2012-update-1-monitoring-for-configmgr.aspx

Did you configure Content Validation on the Distribution Point?

Things to look at are: Boudaries, make sure the clients Ip address is part of a Boundary. Management Point, make sure the client can find the MP (as it can not connect to the AD).