Peter van der Woude

AFAIK, Software Center is added to the Start Menu by default, under Microsoft System Center 2012 (I can't verify, as I've only got Windows 8/ Server 2012 systems right now).

Error 5 = Access Denied.... So something has to be wrong with the access to the new location...

The integration with ConfigMgr allows you to use the scripts of MDT (in a task sequence) and adds options like, running PowerShell scripts and Orchestrator runbooks in a task sequence.

WebDAV is indeed NOT needed anymore. For the exact IIS requirements, per role, take a look here: http://technet.microsoft.com/en-us/library/gg682077.aspx#BKMK_SiteSystemRolePrereqs

No I mean the log files of the ConfigMgr client (C:\Windows\CCM\Logs).

Two things: The certificate is NOT expired, as it is valid from 6 /25/ 2012 to 6/ 25/ 2013. The red cross just means that the root certificate is not trusted, which is not a problem. KB2801987 is applicable on SP1.

Take a look at my post about Tweeting the Deployment Status, as the basics are the same: http://www.petervanderwoude.nl/post/tweeting-the-deployment-status-of-a-system-via-orchestrator-and-configmgr-2012/

Have a look at the client logs to see why the download timed out.

By design it is NOT possible to remove a Management Point from a Secondary Site.

Scenario 1: No, as there is no deadline the updates will stay optional. Scenario 2: Yes. Scenario 3: Yes, the updates will install in the first available Maintenance Window after the deadline. Scenario 4: No, as there is no deadline the updates will stay optional. Scenario 5: Theoretically, yes, but it needs some testing. For some information about software updates and maintenance windows, see also: http://myitforum.com/cs2/blogs/jhuston/archive/2007/12/18/sccm-maintenance-windows-and-software-updates.aspx

Take a better look at the client.msi.log to see why it gives error 1603.

You need at least SP2, see also: http://technet.microsoft.com/en-us/library/gg682077.aspx#BKMK_SupConfigClientReq

How did you configure the availability of the task sequence (see the Deployment Settings tab in the Deployment Properties)?

That's by design, see also: http://social.technet.microsoft.com/Forums/en-US/configmanagerdeployment/thread/1a039893-4a65-4dc9-9feb-e6f09ea1fc0b

During the OS deployment, to which ip-range does the client belong and to which ad site does that ip-range belong?

That error usually means "There is not enough space on the disk.". So did you change anything with sizing the disk or a new image?

I suddenly thought of another option, you could also create a custom Client Policy for those systems and configure the Install Permissions to Only Administrators (see also: http://technet.microsoft.com/en-us/library/gg682067.aspx#BKMK_ComputerAgentDeviceSettings)

Since SP1 (http://technet.microsoft.com/en-us/library/jj591552) it is possible to configure an existing WSUS server as upstream server.

A task sequence can only be deployed to system and not to users... The only things I can think of is that you build a custom check within your task sequence to check for the membership, or just make separate deployments of the different application and deploy them as available to the specific users.

Here are three options: http://www.petervanderwoude.nl/post/deploying-windows-8-including-optional-windows-features-with-configmgr-2012/

Correct. Just don't configure that, don't configure auto assignment and don't write to the AD and your completely fine in your test environment.

Did you check the ccmsetup.log?

Did you check the adxxxdis log files?

You are indeed thinking wrong. You need to advertise the new program, as that program has the run another program first setting enabled. In short that means, it advertises the new program and the clients sees that it needs the other program first. So on machines that had the other program already it will execute directly the new program and on the other machines it will first run the other program.

What action are you trying to perform with what command line?