Peter van der Woude

For an application the AppEnforce.log is the most important and for the old-school packages the execmgr.log is the most important.

Are you sure it doesn't copy anything? Did you try the copy action in SYSTEM context and see were it will end up?

A content validation will only validate the content... By default an application has a retry of a 100 (which will take a couple of days), so if you discovered it in time it will still redistribute. Also, what you could do is take it out of the group (this will leave the existing content) and add it again (this will add any missing content).

Never been in a situation like that, but in general a newer client is not supported. Not with ConfigMgr, not with anything other product...

There is no (supported) way to do something like that. The only way is to do a fresh deployment of Windows 7 Enterprise an capture user files and settings with USMT. After that (or during that) make sure to deploy the applications.

No, you can just use a custom image as well. It's just that in case of a default image the problem is usually that you have to use OSDPreserveDriveLetter. From what drive did you capture the image?

You forgot to mention the problem you;re having. Theoraticaly this should work the same as with ConfigMgr 2007.

Did you configure the distiribution point certificate?

You can't do Multicast without OSD (Operating System Deployment). In case of a classroom that requires a fresh operating system, I would defenitely try to use multicast. The download of the image file will definitely benifit of this.

That should be possible. Are you using the default install.wim?

If there's anything left behind, it will be overwritten by a new installation.

I would start with the ClientIdManagerStartup.log.

Check the IIS log file, it will provide more information about the exact 403 error.

Did you write information about the ConfigMgr 2012 environment to the AD?

Did you check the client log files? It should provide some more details on why it;s failing.

I like to keep my base image up-to-date, either via offline servicing (in case of only os related updates), or via a build and capture task sequence.

You could look at dynamic variables.

Can you share the solution in case somebody is searching for the same?

That should be the folder that contains the IIS log files of the Default Website, yes.

Updates during the task sequence come from a software update group, of which the deployment is targeted to a collection in which the computer object exists. Often this is the same collection as the collection to which the task sequence is deployed.

That's possible, but you have to create a custom script for that.

In this case I would go for an old-school package and program. You could also try to use the run from distribution point option.

The link was indeed incorrect... sorry... Second try: http://www.scconfigmgr.com/2013/10/11/get-dell-warranty-status-within-configmgr-2012-console/ The tool in the link creates a right-click option to show that information.

I can't think of a way to do that (not even with PowerShell)....

Putting all drivers of a vendor together will give you a lot of problems with for example different driver versions.