SCCM 1610 / SCCM 1511 Clinet supported OS

Hi All,

 

Below are the Client OS are supported by SCCM 1511 and it’s higher version.

 

Windows computers	Comments
Windows Server 2012 R2 (x64)
Windows Server 2016 – Standard, Datacenter	Windows Server 2016 is supported from with Configuration Manager version 1606 with the hotfix rollup from KB3186654
Windows Storage Server 2012 R2 (x64)	1 Datacenter releases are supported but not certified for Configuration Manager. Hotfix support is not offered for issues specific to Windows Server Datacenter Edition.
Windows Server 2012 (x64) – Standard, Datacenter 1
Windows Storage Server 2012 (x64)
Windows Server 2008 R2 with SP1 (x64) – Standard, Enterprise, Datacenter 1	2 To support client push installation, the computer that runs this operating system version must run the File Server role service for the File and Storage Services server role. For information about installing Windows features on a Server Core computer, see Install Server Roles and Features on a Server Core Server in the Windows Server 2012 TechNet library.
Windows Storage Server 2008 R2 (x86, x64) - Workgroup, Standard, Enterprise
Windows Server 2008 with SP2 (x86, x64) - Standard, Enterprise, Datacenter 1
Windows 10 Enterprise LTSB (x86, x64) 3
Windows 10 (x86, x64) – Pro, Enterprise
Windows 8.1 (x86, x64) – Professional, Enterprise
Windows 8 (x86, x64) – Professional, Enterprise
Windows 7 with SP1 (x86, x64) – Professional, Enterprise, Ultimate	3 Use of this operating system requires version 1602 or later.
The Server Core installation of Windows Server 2012 R2 (x64) 2
The Server Core installation of Windows Server 2012 (x64) 2
The Server Core installation of Windows Server 2008 R2
(with no service pack, or with SP1) (x64)
The Server Core installation of Windows Server 2008 SP2 (x86, x64)
Windows Embedded	Comments
Windows 10 Enterprise (x86, x64)
Windows 10 IoT Enterprise (x86, x64)
Windows Embedded 8.1 Industry (x86, x64)
Windows Embedded 8 Industry (x86, x64)
Windows Embedded 8 Standard (x86, x64)
Windows Embedded 8 Pro (x86, x64)
Windows Thin PC (x86, x64)
Windows Embedded POSReady 7 (x86, x64)
Windows Embedded Standard 7 with SP1 (x86, x64)
WEPOS 1.1 with SP3 (x86)
Windows Embedded POSReady 2009 (x86)
Windows Fundamentals for Legacy PCs (WinFLP) (x86)
Windows XP Embedded SP3 (x86)
Windows Embedded Standard 2009 (x86)
Windows CE	Comments
Windows CE 7.0 (ARM and x86 processors)	Only below Langugages supported
	Chinese (simplified and traditional)
	English (US)
	French (France)
	German
	Italian
	Japanese
	Korean
	Portuguese (Brazil)
	Russian
	Spanish (Spain)
Mac computers
Mac OS X 10.9 (Mavericks)
Mac OS X 10.10 (Yosemite)
Mac OS X 10.11 (El Capitan)
Linux and UNIX servers
AIX
Version 5.3 (Power)	ccm-Aix53ppc.<build>.tar
Version 6.1 (Power)	ccm-Aix61ppc.<build>.tar
Version 7.1 (Power)	ccm-Aix71ppc.<build>.tar
CentOS
Version 5 x86	ccm-Universalx86.<build>.tar
Version 5 x64	ccm-Universalx64.<build>.tar
Version 6 x86	ccm-Universalx86.<build>.tar
Version 6 x64	ccm-Universalx64.<build>.tar
Version 7 x64	ccm-Universalx64.<build>.tar
Debian
Version 5 x86	ccm-Universalx86.<build>.tar
Version 5 x64	ccm-Universalx64.<build>.tar
Version 6x86	ccm-Universalx86.<build>.tar
Version 6 x64	ccm-Universalx64.<build>.tar
Version 7 x86	ccm-Universalx86.<build>.tar
Version 7 x64	ccm-Universalx64.<build>.tar
Version 8 x86	ccm-Universalx86.<build>.tar
Version 8 x64	ccm-Universalx64.<build>.tar
HP-UX
Version 11iv2 IA64	ccm-HpuxB.11.23i64.<build>.tar
Version 11iv2 PA-RISC	ccm-HpuxB.11.23PA.<build>.tar
Version 11iv3 IA64	ccm-HpuxB.11.31i64.<build>.tar
Version 11iv3 PA-RISC	ccm-HpuxB.11.31PA.<build>.tar
Oracle Linux
Version 5 x86	ccm-Universalx86.<build>.tar
Version 5 x64	ccm-Universalx64.<build>.tar
Version 6 x86	ccm-Universalx86.<build>.tar
Version 6 x64	ccm-Universalx64.<build>.tar
Version 7 x64	ccm-Universalx64.<build>.tar
Red Hat Enterprise Linux (RHEL)
Version 4 x86	ccm-RHEL4x86.<build>.tar
Version 4 x64	ccm-RHEL4x64.<build>.tar
Version 5 x86	ccm-Universalx86.<build>.tar
Version 5 x64	ccm-Universalx64.<build>.tar
Version 6 x86	ccm-Universalx86.<build>.tar
Version 6 x64	ccm-Universalx64.<build>.tar
Version 7 x64	ccm-Universalx64.<build>.tar
Solaris
Version 9 SPARC	ccm-Sol9sparc.<build>.tar
Version 10 x86	ccm-Sol10x86.<build>.tar
Version 10 SPARC	ccm-Sol10sparc.<build>.tar
Version 11 x86	ccm-Sol11x86.<build>.tar
Version 11 SPARC	ccm-Sol11sparc.<build>.tar
SUSE Linux Enterprise Server (SLES)
Version 9 x86	ccm-SLES9x86.<build>.tar
Version 10 SP1 x86	ccm-Universalx86.<build>.tar
Version 10 SP1 x64	ccm-Universalx64.<build>.tar
Version 11 SP1 x86	ccm-Universalx86.<build>.tar
Version 11 SP1 x64	ccm-Universalx64.<build>.tar
Version 12 x64	ccm-Universalx64.<build>.tar
Ubuntu
Version 10.04 LTS x86	ccm-Universalx86.<build>.tar
Version 10.04 LTS x64	ccm-Universalx64.<build>.tar
Version 12.04 LTS x86	ccm-Universalx86.<build>.tar
Version 12.04 LTS x64	ccm-Universalx64.<build>.tar
Version 14.04 LTS x86	ccm-Universalx86.<build>.tar
Version 14.04 LTS x64	ccm-Universalx64.<build>.tar

 

 

SCCM 2016 / SCCM CM1511 Planning work Sheet

SCCM 2016 / SCCM CM1511 Planning work Sheet

 

Active Directory Planning
Active Directory Planning	Example Data Needed, Where Applicable, and by Location	Collected Data
Do you plan on using your Active Directory Sites to define your Configuration Manager  boundaries?	If yes, list the Active Directory sites that you will use.
Do you plan on extending your Active Directory schema for Configuration Manager ?	If yes, determine whether you have the appropriate permissions to extend the schema.
Do you need to manage Configuration Manager  sites across multiple forests?	If yes, be aware of limitations across forests.
Discovery Planning
Discovery planning	Example data needed, where applicable, and by location	Collected Data
Active Directory System Discovery. Active Directory System Discovery retrieves details about the computer, such as computer name, Active Directory container name, IP address, and Active Directory site. It generates a DDR for each computer it discovers in Active Directory.	Active Directory container and location (local domain, local forest, custom LDAP or GC query) Polling schedule
Active Directory System Group Discovery. Active Directory System Group Discovery works only for systems that are already discovered and assigned to the local primary site and any direct child secondary sites. Active Directory System Group Discovery is not available for secondary sites. If a resource has been discovered and is assigned to the Configuration Manager  site, Active Directory System Group Discovery extends other discovery methods by retrieving details such as organizational unit, global groups, universal groups, and nested groups.	Active Directory container and location (local domain, local forest, custom LDAP or GC query) Polling schedule
Active Directory User Discovery. The Active Directory User Discovery method discovers users and the user groups of which they are members. Active Directory User Discovery returns more information from Active Directory domains than Windows User Account Discovery or Windows User Group Discovery and it continues to work with those domains when you switch them to native mode.	Active Directory container and location (local domain, local forest, custom LDAP or GC query) Polling schedule
Network Discovery. The Network Discovery method can be configured to discover the topology of your network, as well as potential client computer information. By querying specified network routers, network discovery retrieves information about the network topology and routers in use. Using discovered router information, or specified Microsoft DHCP server IP address lease information, network discovery can also discover potential client computer information such as IP address and operating system version.	Type of Discovery (Topology, Topology and client, Topology, client, and client operating system), IP subnets to search, and Microsoft DHCP server names to query.
Active Directory Forest Discovery Unlike other Active Directory discovery methods, Active Directory Forest Discovery does not discover resources that you can manage. Instead, this method discovers network locations that are configured in Active Directory and can convert those locations into boundaries for use throughout your hierarchy.	Account requied with permissions to the non-trusted forest
Boundaries Planning
Boundary Type	Example data needed, where applicable, and by location	Collected Data
IP subnet	What subnets will you assign as site boundaries for this site?
Active Directory site name	What Active Directory sites will you use as site boundaries for this site?
IPv6 prefix	What IPv6 prefixes will you use as boundaries for this site?
IP range	What IP ranges will you use for this site?
Site Systems  Planning
Site name	Site code	Primary site? (Note if the site is the central site.)	Secondary site? (Indicate parent site name and site code)	Potential number of clients managed by this site:	IP subnet(s) or Active Directory sites associated with this site.
Site Planning Summary Worksheet
Computer name	Site server	Management point?Indicate whether it is the default or proxy.	Site database server?	Reporting point?Primary site only.	Distribution point and other Roles Servers
Configuration Manager Console
Computer Name	Location	For Which Users / Groups going to Use
Client Installation Planning
Client installation methods	Explanation	Configuration parameters
Install Clients Using Software Update Point Based Installation	The Software update point (SUP) client installation method installs the Configuration Manager  client software on any computer that can communicate with the site's software update point.	To specify the setup parameter information for the client installation you will need to create the SetupParameters registry string value in the following registry key: HKey_Local_Machine \Software \Policies \Microsoft \CCMSetup
		CCMSetup.exe will locate the setup parameters using this registry string value. For example: the registry string value information /mp:[ServerName] is read by CCMSetup.exe and the Configuration Manager client is directed to the server name specified. Specifying parameters through the registry key SetupParameters is the equivalent of specifying the installation parameters using the command line.
Client imaging	You can load client software components on the computer when it is originally prepared for service in your organization. Typically, computer preparation work is done by an IT team in a staging area. The client is installed on a computer master image by installing core client components without specifying a site code for assignment. The computer is ready to be assigned to a site when it arrives at the location where will be used in production.	Identify the CCMSetup.exe command line options you will use when installing the client on the master computer to be imaged.
		Identify any registry modifications that need to be made for the preferred client type.
		Identify the site code that the client should be assigned to.
Client Push installation	Client Push Installation is useful for installing the client software on computers that:	Enabled?
	Have been discovered by Configuration Manager  but do not have the client software installed.	For computers running Windows Vista you must enable the remote registry service or the client push installation will fail on those clients.
	Rarely log on to the network because the users lock their Windows sessions instead of logging out.	Identify the client push installation account that will be used.
	Log on with a user account that does not run a logon script or does not have administrative permissions on the computer.	Identify whether you will push the client to servers, workstations, or domain controllers.
	Are servers that users might not log on to for a long period of time.
Manual installation	You can use CCMSetup.exe to manually install the Configuration Manager  client software to a computer. CCMSetup.exe uses the Client.msi program to install the client software. CCMSetup.exe copies all the files necessary to complete the client installation, including the Client.msi and language-specific files and folders, to the computer.	Identify how and when CCMSetup.exe will be run on each client
		Identify any specific command line options required.
Active Directory Group Policy	You can distribute the Configuration Manager  client software using Active Directory Group Policy. Because of the limitations with customizing this installation method, Group Policy installations should be used for targeting small groups of computers. You can publish or assign the client installation program to computers based on their organizational unit location in Active Directory.	Identify the name(s) of any Group Policy objects.
		Name(s) of OU, domain, or site the Group Policy object is linked to.
		Identify any additional Group Policy object settings such as No Override or group filtering.
		Identify Group Policy object security settings
Logon scripts installation	You can use the file CCMSetup.exe in a login script to trigger the client installation.	Identify any logon scripts being used and the commands being processed.
	Logon script installations can be configured using the same method that you would configure a manual client installation. You can specify the /logon switch with CCMSetup.exe which will cause CCMSetup.exe to skip the installation if there is already a Configuration Manager Client installed.
	If no installation source is specified using the /Source switch and no management point is specified using the /MP switch, CCMSetup.exe can locate the management point if there is a server locator point and Active Directory Services has been extended.
Software distribution	Software distribution can be used to upgrade existing SMS 2003 Advanced Clients.	Identify how and when CCMSetup.exe will be distributed on each client
	Outline your plan to distribute CCMSetup.exe to run on each client.
		Identify any specific command line options required.
Client Installation Planning
Agent	Example Data Needed, Where Applicable, and by Location	Client Agent Settings Name	Target Collections Name
Background Intelligent Transfer	Enabled?
Client Cache Settings	Enabled?
Client Policy	Enabled?
Compliance Settings	Enabled?
Computer Agent	Enabled?
Computer Restart
Endpoint Protection	Enabled?
Hardware Inventory	Enabled?
Metered Internet Connections	Enabled?
Power Management	Enabled?
Remote Tools	Enabled?
Software Deployment	Enabled?
Software Inventory	Enabled?
Software Updates	Enabled?
User and Device Affinity	Enabled?
Mobile Devices	Enabled?
Enrollment	Enabled?
User and Device Affinity	Enabled?