We are looking to use MDOP and AppV in conjunction with the Win10 Ent rollout.
> On Jul 12, 2016, at 10:30 AM, Krueger, Jeff <[email protected]> wrote: > > Well just off the top of my head for the desktops, is do you use the MDOP > toolkit at all? MBAM is huge for us, we encrypt all endpoints and having > MBAM makes managing that a lot easier. > > -----Original Message----- > From: [email protected] [mailto:[email protected]] > On Behalf Of Michael Roach > Sent: Tuesday, July 12, 2016 10:50 AM > To: [email protected] > Subject: [mssms] Looking for justification to maintain SA on SCCM and > win7/Win10 Ent Ed skus > > Hi all, > > It's that time of year again and I have a half day to come up with > justification for maintaining SA on our licenses of ConfigMgr (we're running > latest 1602) and our desktop OSE (currently Windows 7 Enterprise with a > planned implementation of Windows 10 Enterprise to begin in early 2017 and > Server 2016 shortly after RTM later this year). > > Today we purchase SA with the desktop OS and the ConfigMgr licenses. For > ConfigMgr we have a mix of Client ML, Data Center, and Standard licenses as > we manage both server and desktop with it. > > The bean counters feel that the support incidents provided by SA (roughly 1 > per 20k spend) is not enough to justify it. > > What I need to articulate are all the other benefits that SA provides and was > hoping someone on the list might have recently gone through this exercise and > could share their list. > > So what justification would you give to maintain SA for ConfigMgr and the > enterprise sku of the desktop OS? > > Thanks for your help! > > > > > ________________________________ > > 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. > > > >
