The Documentation Library for System Center 2012 Configuration Manager has been updated on the web and the latest content has Updated: July 1, 2012 at the top of the topic. There are no changes this month for the Configuration Manager 2007 Documentation Library.
We value customer feedback and try to incorporate it when possible. Although we can’t promise to make the docs perfect for everybody, we are committed to continual improvement. So, keep that feedback coming, and feel free to contact us about anything related to the documentation by using our usual address of SMSDocs@Microsoft.com.
What's New in the Documentation Library for System Center 2012 Configuration Manager, July 2012
The following information lists the topics that contain significant changes since the June 2012 update.
Update System Center 2012 Configuration Manager
- New topic that supports installing update bundles if you require hotfixes to System Center 2012 Configuration Manager.
Accessibility Features of Configuration Manager
- New topic that contains the same information in the product Help file. This topic outlines accessibility features for Configuration Manager and provides links to more information.
How to Install Clients on Computers in Configuration Manager
- Updated to correct the information in the section How to Install Configuration Manager Clients for Internet-based Client Management. Previously, this section said that clients on the intranet are automatically configured with the Internet-based management point. As in Configuration Manager 2007, you must still assign the Internet-based management point to the client in System Center 2012 Configuration Manager by using the CCMHOSTNAME Client.msi property during installation, or by manual configuration, or by deploying a script. The information about automatic configuration is also removed from What’s New in Configuration Manager and an entry in the Frequently Asked Questions for Configuration Manager topic.
Introduction to Client Deployment in Configuration Manager
- Updated the Considerations for Managing the Configuration Manager Client in a Virtual Desktop Infrastructure (VDI) section for information about the randomization delay (also known as the “activation delay”) for scheduled actions on clients. This change of behavior was introduced to support VDI but applies to all clients, and is not configurable in the Configuration Manager console. For example, you might schedule a software update to install at midnight and on one computer it installs at 12.10 am and on another computer it installs at 1.30 am. Another example is when clients don’t immediately see a new application in Software Center after downloading their scheduled client policy and instead, the application displays in Software Center at different times on different clients. This delay is up to 2 hours for software updates and software applications, and up to 4 hours for inventory. For customers who want to change this behavior, we are looking into SDK configuration.
Update October 2012: For a script to disable the randomization delay for software updates, see How to Disable the Software Updates Post-Deadline Randomization Delay on the Script Center. In Configuration Manager 2012 SP1, there will be a new client setting that disables this behavior by default for software updates and required applications.
Frequently Asked Questions for Configuration Manager
Updated for the new entries:
-- The Configuration Manager Writing Team
This posting is provided "AS IS" with no warranties and confers no rights.
Regarding: For example, you might schedule a software update to install at midnight and on one computer it installs at 12.10 am and on another computer it installs at 1.30 am
Are you telling me that Microsoft has hard-coded that I cannot begin patch installation or software installation at a given time? Even if I set a deadline at 10 PM, it may not kick off until 11:30? This is one of the major selling points I was using to get our server administrators to switch over from their current patching product to SCCM once we migrated to 2012. Why on Earth would you force me into a randomization schedule???
I'm hoping that I am totally off based, but please respond.
To answer "Even if I set a deadline at 10 PM, it may not kick off until 11:30?" - that's correct, unless you have also configured a maintenance window for this deployment. However, you can disable this behavior by using the script we've provided in the Script Center (gallery.technet.microsoft.com/.../How-to-Disable-the-c3b29b29). In addition, it will be disabled by default in Configuration Manager Service Pack 1, with a new client setting to control this behavior. I've updated the blog post with this information.