Well, if they can give you a connection string they say will work, we can try to get MDT to create one the same.
On Wed, Jul 6, 2016 at 3:42 PM, Giroux, Eric J <[email protected]> wrote: > Ha! They don’t deal in WinPE. > > > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Marcum, John > *Sent:* Wednesday, July 6, 2016 4:17 PM > *To:* '[email protected]' <[email protected]> > *Subject:* RE: [mssms] CS.ini SQL without NAMED PIPES > > > > Silly question but….If they are the DBA’s and they are making the rules > why aren’t they ones figuring out how to make it work? > > > > > > > > > > *From:* [email protected] [ > mailto:[email protected] <[email protected]>] *On > Behalf Of *Giroux, Eric J > *Sent:* Wednesday, July 6, 2016 2:49 PM > *To:* [email protected] > *Subject:* RE: [mssms] CS.ini SQL without NAMED PIPES > > > > Negative. Has to be NT authentication. > > > > *From:* [email protected] [ > mailto:[email protected] <[email protected]>] *On > Behalf Of *Todd Hemsell > *Sent:* Wednesday, July 6, 2016 2:48 PM > *To:* [email protected] > *Subject:* Re: [mssms] CS.ini SQL without NAMED PIPES > > > > will they let you use a SQL user and password? > > > > On Wed, Jul 6, 2016 at 1:20 PM, Giroux, Eric J <[email protected]> wrote: > > Yes I can. I can connect into the target database and select from the > view successfully. The ID definitely has access. The problem seems to be > with the connection from WinPE trying to connect as anonymous rather than > with the NAA credentials. > > > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Todd Hemsell > *Sent:* Wednesday, July 6, 2016 1:46 PM > *To:* [email protected] > *Subject:* Re: [mssms] CS.ini SQL without NAMED PIPES > > > > Can you log into a workstation with SQL Management studio on it using > those credentials and connect to the DB? > > > > On Wed, Jul 6, 2016 at 9:44 AM, Giroux, Eric J <[email protected]> wrote: > > Confirmed those are all configured as they should be. Here is the SQL > section from my CS.ini: > > > > [DB_WIAT] > > SQLServer=MYSERVER\INSTANCE > > Database=MYDB > > Netlib=DBMSSOCN > > SQLShare=MYSHARE > > Table=MYVIEW > > Parameters=SerialNumber > > > > The SQLShare is on the SQL server and UNC connection is made successfully > in the logs. This is not the MDT database but a db for an internal app we > use to populate some deployment variables. > > > > > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Troy Martin > *Sent:* Tuesday, July 5, 2016 11:17 PM > *To:* [email protected] > *Subject:* Re: [mssms] CS.ini SQL without NAMED PIPES > > > > This message originated outside of Unum. Use caution when opening > attachments, clicking links or responding to requests for information. > > > > In the SQL server configuration tools, TCP/IP protocol is required to be > enabled on the server as well. Also, the ConfigMgr Network Access Account > needs a SQL login and granted db_datareader perms to the MDT database. > > *1E | Software Lifecycle Automation* > > > On Jul 5, 2016, at 1:05 PM, Giroux, Eric J <[email protected] > <[email protected]>> wrote: > > I need a bit of guidance to make SQL connection from CustomSettings.ini > using NT Authentication (network access account) vs named pipes. Have > always used named pipes successfully but DBAs are putting their foot down > on dis-allowing use of named pipes. > > > > Adding Netlib=DBMSSOCN to my SQL section of my CS.ini is giving me a > return of: > > > > ZTI error opening SQL Connection: Login failed for user ‘NT > AUTHORITY\ANONYMOUS LOGON’. (-2147217843). I assumed by adding > Netlib=DBMSSOCN it would authenticating using network access account > credentials but this feels as though it is needing a SQL ID and pwd to make > the connection, which I do not want to use. > > > > Is anyone using Netlib=DBMSSOCN successfully? > > > > Thanks, > > > > *Eric Giroux* > > Solutions Engineer > > Unum Group > > E-mail: [email protected] | Office: (207) 575-2482 > > Mobile: (207) 239-5190 | Fax: (207) 575-2158 > > > > > > > ------------------------------ > > > > Legal Notice: This email is intended only for the person(s) to whom it is > addressed. If you are not an intended recipient and have received this > message in error, please notify the sender immediately by replying to this > email or calling +44(0) 2083269015 (UK) or +1 866 592 4214 (USA). This > email and any attachments may be privileged and/or confidential. The > unauthorized use, disclosure, copying or printing of any information it > contains is strictly prohibited. The opinions expressed in this email are > those of the author and do not necessarily represent the views of 1E Ltd. > Nothing in this email will operate to bind 1E to any order or other > contract. > > > > > > > > > > > > > > > ------------------------------ > > > 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. > > > >
