Thanks very much Aaron ! (has anyone got 2012 R2 SP1 / 2012 SP2 clients being managed OK by v1511 sites? ) I've pulled out bits from those links to get a deeper understanding of the situation the customer may find themselves, which at the moment will not be temporary (long story but "upgrading the Client to v1511 on these existing XPe devices is not really feasible", but they want to do an in-situ (full hierarchy) upgrade from 2012 to v1511). Similarly, the following clients and the following Virtual Private Network (VPN) connection are not supported: •Any System Center 2012 Configuration Manager or earlier computer client version Am I reading this correctly ? A 2012 Client is not supported to be assigned to a v1511 site/hierarchy ? System Center Configuration Manager clients check the version of the Configuration Manager site before they complete site assignment and cannot assign to a pervious version when site if boundaries overlap. However, System Center 2012 Configuration Manager clients might incorrectly assign to a System Center Configuration Manager site. Seems to imply that a 2012 Client can be assigned to a v1511 site ? (although above is talking about boundaries & assignment, and different site versions, yet in this customers circumstance all sites/roles in the hierarchy will be v1511 and clients assigned using site code (not auto))
When different sites in a single hierarchy run different versions, some functionality is not available. This can affect how you manage Configuration Manager objects in the Configuration Manager console, and what functionality is available to clients. Typically, functionality from the newer version of Configuration Manager is not accessible at sites or to clients that run a lower service pack version. Seems to imply that 2012 Clients can be managed by v1511, yet newer functionality will not be available ? When different System Center Configuration Manager sites in a single hierarchy use different versions, some Configuration Manager functionality is not available. Typically, functionality from the newer version of Configuration Manager is not accessible at sites or by clients that run a lower version. Again, seems to imply that 2012 Clients can be managed by v1511, yet newer functionality will not be available ? Thanks, Shane From: [email protected] To: [email protected] Subject: RE: [mssms] Older 2012 R2 SP1 clients, and ConfigMgr v1511 Date: Wed, 16 Dec 2015 21:36:39 +0000 Interop is available while the sites and clients are upgraded. But this should be temporary. See https://technet.microsoft.com/en-us/library/mt622773.aspx https://technet.microsoft.com/en-us/library/mt613175.aspx Aaron From: [email protected] [mailto:[email protected]] On Behalf Of Shane Alexander Sent: Tuesday, December 15, 2015 6:16 PM To: [email protected] Subject: [mssms] Older 2012 R2 SP1 clients, and ConfigMgr v1511 Hi all, A customer currently has SCCM/ConfigMgr 2012 R2 SP1 with CU1. Windows XP Embedded 2009 devices (and many other OS's) with above Client installed & working. The customer is considering upgrading to ConfigMgr v1511. Does anyone know of any risks/issues/limitations/considerations in having 2012 R2 SP1 CU1 Clients being managed by ConfigMgr v1511 ? (aside from support for XPe being removed in 12 months, when they'd no longer have XPe anyway) (upgrading the Client to v1511 on these existing XPe devices is not really feasible) Thanks, Shane
