Now RC is out for a few weeks, it’s time to share some experience.
1. Did you know that you cannot deploy a Task Sequence when using the Configuration Manager Client Agent Package that is created during setup?
The reference to the default client agent package is not valid in a task sequence.
You have to create a new package.
2. If you want to deploy Client Settings you can find the ADM files on your installation media: SMSSetup\Tools\ConfigMgrADMTemplates. Yes ADM files, no ADMX but there are tools to convert. I haven’t tested yet for these kind of policies.
3. How do Deployment Types get evaluated?
The deployment types will be evaluated by priority. By default this is the order when they are created but you can change that. The evaluation happens top down until a DT is found that meets the requirements and that moment the process stops.
4. Reports not visible in the ConfigMgr console, message “No items found”. When browsing to the Reports URL the “ConfigMgr_SiteCode” folder is visible but without reports below.
First of all in case of SQL reporting issues you should look into srsrp.log
In this case I found a line:
“The operation you are attempting requires a secure connection (HTTPS). “
This issue occurs when the SRS report server config file specifies that secure connections are required, but the SRS installation itself is not configured for SSL. This can be solved by doing the following:
1. Open the file rsreportserver.config in notepad (%programfiles%\Microsoft SQL Server\INSTANCE\Reporting Services\ReportServer\rsreportserver.config)
2. Find the entry for <add Key=”SecureConnectionLevel”>, the value attribute is most likely set to 2. Change the value to 0.
3. Save and close the file
4. Stop and start the report server service “net stop reportserver”, “net start reportserver”
OR you can enable HTTPS but then you need to reinstall the RSP role.
5. Did you realize that Dependencies are considered ONLY for install but not for uninstall?
If App A depends on App B. An install deployment of A will install B followed by A. An uninstall deployment of A will uninstall ONLY A and will not try to uninstall B.
6. When deploying an OSD task sequence the deployment option “Run from distribution point” is missing.
The reason for this is that for each package that you want to use for OSD you have to enable them to use a package share. At that time you can “run from DP”. All packages of the appropriate Task Sequence need to have this set before you the “Run from DP” option.
7. In Beta2 there was a setting “this site manages only ConfigMgr 2012 clients”. This check box has been renamed to “Require SHA-256″ and is on the Signing and Encryption tab of the Site Properties dialog box.
8. How to limit package storage to one drive?
During the installation of a DP you can specify a drive letter for package storage. But are you sure only that drive will be used to store packages?
Not really, the single drive will be used until it is full (disk space left of 50mb by default) and then automatically another drive will be found. The only option to avoid this is the good old NO_SMS_ON_DRIVE.SMS file as DP Server Shares do not exist anymore.
9. As mentioned in my earlier blogs Global Data and Site data is replicated via SQL Replication. In the ConfigMgr console you have the Monitoring node to troubleshoot Database Replication. The corresponding log file is rcmctrl.log and you might have a chance to see more details in there.
10. Don’t panic if your Software Inventory is blank, it does not mean your inventory does not work. By default the software scanning is not including any files or file types other than with CM07.
– UPDATE and another important one:
There is no way anymore to control the location of the .PCK files. (cf. CM07 Component Configuration\Software Distribution in Site Management). You need to use the SDK if you want to control this.
If you haven’t tried SCCM 2012 yet or you want to test one of the other tools of the System Center 2012 family you can find them here:
Till next time!