We also have a small implementation of DA (politics as well) and just stood up our IBCM service finally after a long political effort. There's no reason you can't have both services in your org, just treat your DA clients like they are on the internal network, assign a boundary to them based on the IPv6 prefix of your DA servers and they will work just like any other CM client. If for some reason your DA system goes down/away or they fail to connect they'll be able to use IBCM.
From: [email protected] [mailto:[email protected]] On Behalf Of Hyatt, Dewayne Sent: Wednesday, June 14, 2017 9:32 AM To: '[email protected]' <[email protected]> Subject: [mssms] IBCM + Direct Access = Stupid question!! Hey Guys, We have a weak implementation of DA (due to politics) so we stood up IBCM as an experiment. I thought I would be smart and block access to the MP's on the DA server thinking that if a client couldn't communicate with the MP that it would switch to Internet and try our external MP. It would seem however that if the client even has a connection to the domain that it will identify itself as Intranet and never move over to the external MP. I know that these are competing services and that it's probably not sensible to use them in conjunction but unfortunately that's what I've got.... We don't have any DA experts on staff so a lot of what DA does looks like voodoo to us. I don't suppose anyone has played with this before? Ideally we would like to keep DA (if politics allow) so that GPO's, shared folders, etc. continue to work, but I would like IBCM to handle all of the SCCM related tasks. If anything IBCM will be there incase DA goes away. Thanks for any suggestions/trolls, Dewayne ________________________________ CONFIDENTIALITY NOTICE: This email contains information from the sender that may be CONFIDENTIAL, LEGALLY PRIVILEGED, PROPRIETARY or otherwise protected from disclosure. This email is intended for use only by the person or entity to whom it is addressed. If you are not the intended recipient, any use, disclosure, copying, distribution, printing, or any action taken in reliance on the contents of this email, is strictly prohibited. If you received this email in error, please contact the sending party by reply email, delete the email from your computer system and shred any paper copies. Note to Patients: There are a number of risks you should consider before using e-mail to communicate with us. See our Privacy & Security page on www.henryford.com for more detailed information as well as information concerning MyChart, our new patient portal. If you do not believe that our policy gives you the privacy and security protection you need, do not send e-mail or Internet communications to us.
