Email your TAM, they can give you everything you need for this. -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Michael Roach Sent: Tuesday, July 12, 2016 9: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 e-mail is from a law firm and may be protected by the attorney-client or work product privileges. If you have received this message in error, please notify the sender by replying to this e-mail and then delete it from your computer.
