|Posté le: Sam 23 Déc - 01:38 (2017) Sujet du message: BEst Practices While Working With SCCM
|Best Practices Before Installation
Why is it important ? well firstly because it is a setting that most people don't change (as it's hidden from view) and secondly it's set based on your regional settings. When you install SQL Server (which ConfigMgr needs to host it's database) the SQL Collation is 'set in stone' during setup, that's why knowing what your SQL Collation is and what it should be are important prior to running ConfigMgr setup. To learn how to identify your SQL Collation on a running SQL Server and how to change SQL Collation during SQL Server setup see this post. Having the wrong SQL Server Collation will require you to reinstall SQL Server from scratch, and that takes time and effort.
Best Practices for SQL Server Installation
A lot of early adopters of System Center Configuration Manager are having issues getting SQL Server installed correctly. Many issues are due to having the wrong supported version or cumulative update applied. For information on supported versions please see Supported Configurations for Configuration Manager : http://technet.microsoft.com/en-us/library/gg682077.aspx#BKMK_SupConfigSQLD…
SQL server issues can also be seen when having the wrong certificate applied or by misconfiguring the port. For SQL Server installation and configuration tips see the support blog http://blogs.technet.com/b/configurationmgr/archive/2012/05/03/fix-unable-t…
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 extend the Active Directory schema for Configuration Manager and the site is published to Active Directory Domain Services, many client installation properties are published to Active Directory Domain Services. If a computer can locate these client installation properties, it can use them during Configuration Manager client deployment. Because this information is automatically generated, the risk of human error associated with manually entering installation properties is eliminated. For more information, see About Client Installation Properties Published to Active Directory Domain Services in Configuration Manager.
When you have many clients to deploy, plan a phased rollout outside business hours
Minimize the effect of the CPU processing requirements on the site server by planning a phased rollout of clients over a period of time. Deploy clients outside business hours so that critical business services have more available bandwidth during the day and users are not disrupted if their computer slows down or requires a restart to complete the installation.
Enable automatic upgrade after your main client deployment has finished
Automatic client upgrades are useful when you want to upgrade a small number of client computers that might have been missed by your main client installation method. For example, you have completed an initial client upgrade, but some clients were offline during the upgrade deployment. You then use this method to upgrade the client on these computers when they are next active. For more information about client deployment method, the How to Automatically Upgrade the Configuration Manager Client for the Hierarchy section in the How to Install Clients on Computers in Configuration Manager topic.
Use SMSMP and FSP if you install the client with client.msi properties
The SMSMP property specifies the initial management point for the client to communicate with and removes the dependency on service location solutions such as Active Directory Domain Services, DNS, and WINS.
Use the FSP property and install a fallback status point so that you can monitor client installation and assignment, and identify any communication problems. For more information about these options, see About Client Installation Properties in Configuration Manager.
If you want to use client languages other than English, install the client language packs before you install the clients
If you install client language packs on a site after you install clients, you must reinstall the clients before they can use the additional languages. For mobile device clients, this means you must wipe the mobile device and enroll it again. For more information about how to add support for additional client languages, see Install Sites and Create a Hierarchy for Configuration Manager.
Source: Social TechNet Microsoft