SCCM 2012 - System Center 2012 Configuration Manager Best Practices
Ecco il link di riferimento:
http://social.technet.microsoft.com/wiki/contents/articles/11215.system-center-2012-configuration-manager-best-practices.aspx
Best Practices for Client Deployment
Ecco il link di riferimento:
http://social.technet.microsoft.com/wiki/contents/articles/11215.system-center-2012-configuration-manager-best-practices.aspx
Best Practices for Client Deployment
- Extend the Active Directory schema and publish the site so that you can run CCMSetup without command-line options
- When you have many clients to deploy, plan a phased rollout outside business hours
- Enable automatic upgrade after your main client deployment has finished
- Use SMSMP and FSP if you install the client with client.msi properties
- If you want to use client languages other than English, install the client language packs before you install the clients
- Do not use incremental updates for a large number of collections
- Do not modify the built-in collections and instead, copy and then modify the pasted collection
- Create a control collection of computers with no power plans applied
- Run the Power Settings report before you apply a power management plan
- Exclude computers that you do not want to manage
- First, apply power plans to a test collection of computers
- Apply power plan settings individually
- Regularly monitor computers to see if they have multiple power plans applied
- Save or export power management information during the monitoring and planning phase of power management
- For best performance, install the reporting services point on a remote site system server
- Optimize SQL Server Reporting Services queries
- Schedule report subscription processing to run outside standard office hours
- When Configuration Manager and WSUS use the same SQL Server, configure one of these to use a named instance and the other to use the default instance of SQL Server
- Use a custom website for the WSUS installation
- Specify the Store updates locally setting for the WSUS installation
- Create a new software update group each time an automatic deployment rule runs for “Patch Tuesday” and for general deployment
- Use an existing software update group for automatic deployment rules for Endpoint Protection definition updates
- Other Languages