Can confirm as well. The only issue we have seen is with RTM clients on a R2 site, it works….but has a high chance for corruption. Upgrading to the R2 client resolves it for us.
Daniel Ratliff From: [email protected] [mailto:[email protected]] On Behalf Of Chris Nackers Sent: Monday, November 02, 2015 7:21 PM To: [email protected] Subject: Re: [mssms] SCCM client version I would think any 2012 client version should work more or less… you can certainly have non R2 clients communicate with a R2 site… seen it plenty of places as things take time to get upgraded. Chris Nackers Microsoft MVP – Enterprise Client Management From: <[email protected]<mailto:[email protected]>> on behalf of "Heaton, Joseph@Wildlife" Reply-To: "[email protected]<mailto:[email protected]>" Date: Monday, November 2, 2015 at 3:00 PM To: "[email protected]<mailto:[email protected]>" Subject: [mssms] SCCM client version I’m digging through Technet, but thought I’d ask here as well. What is the minimum client version that can communicate to 2012 R2 SP1 server? Joe Heaton Information Technology Operations Branch Data and Technology Division CA Department of Fish and Wildlife 1700 9th Street, 3rd Floor Sacramento, CA 95811 Desk: (916) 323-1284 Every Californian should conserve water. Find out how at: [SaveOurWater_Logo]<http://saveourwater.com/> SaveOurWater.com<http://saveourwater.com/> · Drought.CA.gov<http://drought.ca.gov/> The information transmitted is intended only for the person or entity to which it is addressed and may contain CONFIDENTIAL material. If you receive this material/information in error, please contact the sender and delete or destroy the material/information.
