Not really true. Yes, there are some limitations, but these are mostly lesser used things and mostly coincide with what isn't supported over IBCM (because CMG is just IBCM hosted in Azure). You get all of the core functionality like software updates, software distribution, and inventory. Yes, I'ts technically pre-release, but a lot folks are using it already in the production environments.
J From: [email protected] [mailto:[email protected]] On Behalf Of Lindenfeld, Ivan Sent: Monday, June 5, 2017 4:32 PM To: [email protected] Subject: [mssms] RE: Intune standalone vs hybrid. According to current documentation you only get a few features with CMG. The only ways to get full SCCM client functionality is IBCM or Remote Access. From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of SCCM FUN Sent: Monday, June 05, 2017 3:04 PM To: [email protected]<mailto:[email protected]> Subject: [mssms] Re: Intune standalone vs hybrid. Great article. Sounds like if you go either version standard or hybrid you don't get the rich functionality of SCCM client. I also read somewhere Intune only has like 10 built it reports and if you want more reports you need to go hybrid? Cloud management gateway in conjunction with cloud DP would be pretty great for us I think. CMG seems to only be pre-release, curious when that will be production. ________________________________ From: [email protected]<mailto:[email protected]> <[email protected]<mailto:[email protected]>> on behalf of Jason Sandys <[email protected]<mailto:[email protected]>> Sent: Monday, June 5, 2017 11:05 AM To: [email protected]<mailto:[email protected]> Subject: [mssms] RE: Intune standalone vs hybrid. Domain joined is irrelevant. Hybrid implies MDM management though which isn't generally suited for enterprise systems (yet). Why not use Internet Based Client Management that's built into ConfigMgr? See https://home.configmgrftw.com/managing-remote-systems/ for a mostly complete rundown of your options. The only thing missing is the ability to host the IBCM components in Azure as an Azure service using he new Cloud Management Gateway introduced with 1610. [https://i1.wp.com/home.configmgrftw.com/wp-content/uploads/2016/12/RemoteWorker.jpg?resize=580%2C387&ssl=1]<https://home.configmgrftw.com/managing-remote-systems/> Remote Systems Management in Configuration Manager ...<https://home.configmgrftw.com/managing-remote-systems/> home.configmgrftw.com<http://home.configmgrftw.com> Managing remote systems, i.e., those not directly connected to your internal network, is a challenge best not overlooked for multiple reasons including security. With ... J From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of SCCM FUN Sent: Monday, June 5, 2017 8:59 AM To: mssms <[email protected]<mailto:[email protected]>> Subject: [mssms] Intune standalone vs hybrid. Read bunch of stuff and I'm more confused then when I first started looking. We have 25k Windows devices and out of that number we have about 2k domain joined laptops who are in the field. They are always an issue for everything (patching, software deployment, etc). I thought I read somewhere saying intune stand alone can't manage domain joined devices so we would need by default to go hybrid. I don't like the idea if we did intune standalone we would need to use sccm console for sccm devices and intune for intune devices so I think we would need to go hybrid either way. Am I right about domain joined means hybrid right away? Also it looks like with stand alone you only get like 10 reports compared to sccm which has lots of reports. ________________________________ NOTICE: The information contained in this message is proprietary and/or confidential and may be privileged. If you are not the intended recipient of this communication, you are hereby notified to: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately.
