dinci5 Posted February 5, 2016 Report post Posted February 5, 2016 Hi all, Our DBA wants to disable Named Pipes on all db servers because TCP/IP method is more secure. He disabled it on our SCCM server and of course all deployments were failing. I found out in ZTIGather.log that the problem was the connection to the database. Error: ZTI error opening SQL Connection: [DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied. (-2147467259) Anyway, the problem was that Named Pipes was disabled on the SCCM server (database is on same server). Enabling Named Pipes solved the problem. Our DBA still wants to disable Named Pipes...So, is there any way that the connection method could be changed from Named Pipes to TCP/IP during the TS? If so, could you point me in the right direction where to look? My SQL skills are very limited though... Thank you Quote Share this post Link to post Share on other sites More sharing options...
ZeZe Posted February 5, 2016 Report post Posted February 5, 2016 I guess Named Pipes are a requirement to run SCCM 2012. From all installation step-by-steps that I've read, SQL Named Pipes must be enabled. Just because named pipes are "old technology" it doesn't bring necessarily a security issue. Keep your environment updated (OS and service) patched with the appropriated firewall rules, access policy, accounts permissions, etc. That's my opinion, of course ! Quote Share this post Link to post Share on other sites More sharing options...
