Agree with you there Gerry.
> On 18 Nov 2014, at 20:21, Gerry Hampson <[email protected]> wrote: > > I’ve always embraced the policy that I can use the database for System Center > integrated products – MDT, SUSDB, MBAM. Am I skating on thin ice with that? > > From: [email protected] [mailto:[email protected]] > On Behalf Of Paul Winstanley > Sent: 18 November 2014 19:58 > To: [email protected] > Subject: Re: [mssms] Windows and sql auth on a ConfigMgr database server > > Cheers mate. > > > > On 18 Nov 2014, at 19:52, Jason Sandys <[email protected]> wrote: > > It's in the Product Use Rights documentation: > > http://www.microsoftvolumelicensing.com/userights/DocumentSearch.aspx?Mode=3&DocumentTypeId=1 > > > > J > > From: [email protected] <[email protected]> on > behalf of Paul Winstanley <[email protected]> > Sent: Tuesday, November 18, 2014 11:21 AM > To: [email protected] > Subject: Re: [mssms] Windows and sql auth on a ConfigMgr database server > > Jason > > This is interesting to know. I always advise customers not to use the > database for any other reason beyond Configmgr and susdb, normally through > common sense rather than licencing. > > Do you a link to the MS support statement on this so I can fire at will at > customers? > > Thanks > Paul. > > > > On 18 Nov 2014, at 17:14, Jason Sandys <[email protected]> wrote: > > Enabling SQL auth does not affect Windows auth, it just enables SQL auth in > addition to Windows auth. SQL auth is less secure than Windows Auth by its > very nature of not being centrally controlled or managed so that's why it's > considered not a best practice to use or enable. > > > > Also note that based on the licensing agreement, you are not allowed to use > non-System Center applications with your instance of SQL Server used for > ConfigMgr. > > > > J > > From: [email protected] <[email protected]> on > behalf of Paul Winstanley <[email protected]> > Sent: Tuesday, November 18, 2014 3:00 AM > To: [email protected] > Subject: Re: [mssms] Windows and sql auth on a ConfigMgr database server > > Yes Windows auth is best practice however you can run in mixed mode if there > is a requirement. > > > > On 18 Nov 2014, at 07:32, David O'Brien <[email protected]> wrote: > > I can’t talk about supported, but I had a lot of customers requiring SQL > auth, because that’s what they used for their backup/maintenance tools on the > DB. Never had an issue and can’t really see why there should be one. > > Cheers > David > > From: [email protected] [mailto:[email protected]] > On Behalf Of Corkill, Daniel > Sent: Tuesday, 18 November 2014 6:26 PM > To: [email protected] > Subject: [mssms] Windows and sql auth on a ConfigMgr database server > > On my ConfigMgr site server (which is also my database server), I have a > requirement to enable SQL auth. I’ve reviewed the SQL Server requirements > section of the ConfigMgr supported configurations documentation and it states > Windows auth is required but I just want confirm there won’t be any issues by > having both SQL and windows auth enabled. > > Daniel. > > > ********************************************************************* > This email, including any attachment, is confidential to the intended > recipient. It may also be privileged and may be subject to copyright. If > you have received this email in error, please notify the sender immediately > and delete all copies of the email. Any confidentiality or privilege is not > waived. Neither the Council nor the sender warrant that this email does not > contain any viruses or other unsolicited items. > > This email is an informal Council communication. The Council only accepts > responsibility for information sent under official letterhead and duly signed > by, or on behalf of, the Chief Executive Officer. > > Privacy Collection Notice > Logan City Council may collect your personal information, e.g. name, > residential address, phone number etc, in order to conduct its business > and/or meet its statutory obligations. The information will only be accessed > by employees and/or Councillors of Logan City Council for Council business > related activities only. If your personal information will be passed onto a > third party, Council will advise you of this disclosure, the purpose of the > disclosure and reason why. Your information will not be given to any other > person or agency unless you have given us permission or we are required by > law. > > > > > > > > > >
