Back in SCCM 2007, it was simple enough – you could either run your program directly from the distribution point or get the client to download the content and then run it locally. Due to the way the SCCM 2012 Content Library works (see this post for a great explanation http://blogs.technet.com/b/hhoy/archive/2012/05/31/an-adventure-in-the-sccmcontentlib-single-instance-store.aspx), by deault when you deploy (aka advertise) a task sequence you will find that the ‘Access content directly from a distribution point when needed by the running task sequence’ option isn’t available. In some scenarios you will want to use this option, so here is how to get it.
For each package referenced in your task sequence (including SCCM client, images, driver packages), you need to select the following option on the Data Access tab:
At this point you will start to see package shares (eg smspkgc$) start to appear on the distribution points, just like they would in SMS & SCCM ‘07. Once all of the packages have had the above option enabled, open up your task sequence deployment (aka advertisement) and on the Distribution Point tab you will now see an additional option in your drop down box:
Of course you should have a think about and understand the effect this is going to have, for example this may used up to double the amount of storage space for each package on your DP as the files will be stored in the Content Library as well as the Package Share location.
More Microsoft documentation on SCCM 2012 Task Sequences here – http://technet.microsoft.com/en-us/library/gg712685.aspx
In SCCM 2012 I had issues when deploying the DP role to a Windows 7 x86 machine. When I checked the distmgr.log on the primary site server I saw:
CWmi::Connect() failed to connect to \<<DPNAME>>rootSCCMDP. Error = 0x800706BA
On the Windows 7 machine that I was trying to add the DP role to, the WMI Name space rootSCCMDP did not exist.
After copying smsdpprov.mof from Program FilesMicrosoft Configuration ManagerbinX64 I ran ‘mofcomp.exe smsdpprov.mof’ and this recreated the WMI name space and the DP role install continued.
Had a client today whos SCCM 2012 PXE enabled DP wouldn’t work. Upon inspection of the SMSPXE.log file I saw:
Warning: Matching Processor Architecture Boot Image (0) not found
SCCM PXE requires you to have both x64 and x86 images deployed even if you aren’t going to use both of them.
For both of your boot images, ensure ‘Deploy this boot image from the PXE service point’ is ticked and then make sure you ‘Distribute Content’ to your PXE enabled DPs.
Then check your RemoteInstallSMSImages directory for the new WIM and the SMSPXE.log file to see if the new WIM is loaded.
More info here – http://technet.microsoft.com/en-us/library/hh397288.aspx
While most of the time you are going to be installing the System Center Virtual Machine Machine 2012 console on a domain joined machine, I had a requirement to install the console on a non-domain joined machine. You can’t do this via the regular VMM setup as the installer does a check for domain membership as a pre-req and there is no way around this.
So this is how I got it working:
- Enable the ‘.NET Framework 3.5.1’ feature (pre-req as per http://technet.microsoft.com/en-us/library/gg610640.aspx)
- Set PowerShell execution policy to Unrestricted (set-executionpolicy unrestricted)
- Browse to the amd64SetupmsiClient folder from the VMM 2012 media and run AdminConsole.msi
You should now have a working VMM 2012 console on your non-domain machine.