February 4, 2017 at 8:02 am
Comments posted to this topic are about the item Close Encounters of the CEIP Kind
February 4, 2017 at 3:35 pm
Thanks for the very timely article, Rodney. I agree that my right index finger will feel a great loss and not being able to turn it all off during installation.
It would appear that you can disable both error and feature reporting fairly easy, once made aware of it. Please see the following MS article. https://msdn.microsoft.com/en-us/library/ms143343.aspx While the write up there is all very interesting, the very last paragraph quickly summarizes how to disable both and it's done without having change a policy or registry setting. The registry setting appears to be only for the time-of-day when the feature reporting would occur if left enabled.
--Jeff Moden
Change is inevitable... Change for the better is not.
February 4, 2017 at 8:07 pm
Jeff Moden - Saturday, February 4, 2017 3:35 PMIt would appear that you can disable both error and feature reporting fairly easy, once made aware of it. Please see the following MS article. https://msdn.microsoft.com/en-us/library/ms143343.aspx
That was a very timely article for me. I just installed a WSFC and SQL 2016 and saw those new services. I wondered how I missed it in the setup, but also how there were multiple new services consuming resources I didn't want consumed.
And Jeff, thanks for so much for that link. That's a definite must-have.
February 6, 2017 at 1:38 am
I am behind the curve on this one. A server collecting telemetry per se is only useful if it can send that data back to base. Most production servers I've seen could not talk directly to the internet or send external mail.
No matter what Microsoft does internally they can only simulate what their customers actually do. That telemetry data can be a mine of information and flush out problems so they can be fixed early.
I'd be curious to know from those who have experienced various levels of paid support from Microsoft and other organisations how Microsoft rank.
I've been quite impressed with both Microsoft and AWS. Neo4j and DataStax were reasonable and certainly better than I expected given the size of company.
February 6, 2017 at 4:42 am
I am a little concerned that this is hidden. I can even understand this being fixed on for free, evaluation and developer versions. It seems a reasonable part of the deal. It is the nature of forcing this to be on for other editions that makes me feel a little uneasy. It is like they are deceiving their customers. That may or may not be their intention but unintended consequences may also occur.
Gaz
-- Stop your grinnin' and drop your linen...they're everywhere!!!
February 6, 2017 at 7:22 am
Gary Varga - Monday, February 6, 2017 4:42 AMI am a little concerned that this is hidden. I can even understand this being fixed on for free, evaluation and developer versions. It seems a reasonable part of the deal. It is the nature of forcing this to be on for other editions that makes me feel a little uneasy. It is like they are deceiving their customers. That may or may not be their intention but unintended consequences may also occur.
I think MS needs a kick in the head. Apparently they think they can do whatever they want because of their damned EULA and the way it's written. I don't care how innocent the data being collected may be. Part of "the deal" that I expect is having full and obvious notification and control of if and when any data is sent to anyone. This is like MS installing a camera in my living room.
--Jeff Moden
Change is inevitable... Change for the better is not.
February 6, 2017 at 7:34 am
Thanks. I read Brent's article ages ago and then clean forgot to do anything about it. I'm going to see if I can get a policy created.
February 6, 2017 at 8:08 am
Beatrix Kiddo - Monday, February 6, 2017 7:34 AMThanks. I read Brent's article ages ago and then clean forgot to do anything about it. I'm going to see if I can get a policy created.
A brief article would be a good share. (I thought that I would suggest before Steve asked ;))
Gaz
-- Stop your grinnin' and drop your linen...they're everywhere!!!
February 6, 2017 at 11:38 am
", maybe all of that previoustelemetry had taught Microsoft hat 98.9% of DBAs opt out of sending this data,so they gave up on the idea of collecting it! "
Absence of a checkbox should not be interpreted as not collecting. Microsoft, like many other entities (including the government) doesn't just stop collecting.. they just stop talking about it and asking permission.
You check is in the mail.
...
-- FORTRAN manual for Xerox Computers --
February 7, 2017 at 12:18 pm
MS displaying the same mind set as they did in Windows 10
February 10, 2017 at 6:32 pm
Ed Wagner - Saturday, February 4, 2017 8:07 PMJeff Moden - Saturday, February 4, 2017 3:35 PMIt would appear that you can disable both error and feature reporting fairly easy, once made aware of it. Please see the following MS article. https://msdn.microsoft.com/en-us/library/ms143343.aspxThat was a very timely article for me. I just installed a WSFC and SQL 2016 and saw those new services. I wondered how I missed it in the setup, but also how there were multiple new services consuming resources I didn't want consumed.
And Jeff, thanks for so much for that link. That's a definite must-have.
I installed a new SQL 2016 failover cluster today and can confirm that this does work. After doing the normal stuff in the configuration manager, I made the changes described in the article on both nodes. After a failover, the CEIP services were no longer running.
Many thanks again, Jeff, for that article.
May 9, 2017 at 2:24 am
Jeff Moden - Saturday, February 4, 2017 3:35 PMThanks for the very timely article, Rodney. I agree that my right index finger will feel a great loss and not being able to turn it all off during installation.It would appear that you can disable both error and feature reporting fairly easy, once made aware of it. Please see the following MS article. https://msdn.microsoft.com/en-us/library/ms143343.aspx While the write up there is all very interesting, the very last paragraph quickly summarizes how to disable both and it's done without having change a policy or registry setting. The registry setting appears to be only for the time-of-day when the feature reporting would occur if left enabled.
Sad to say, that article has disappeared - that url now redirects to https://msdn.microsoft.com/library/bb500395.aspx which contins no information at all about CEIP.
It might be useful if someone could tell whether the method in the now inaccesible article still works and if it does describe it in this thread.
Tom
May 9, 2017 at 6:27 am
TomThomson - Tuesday, May 9, 2017 2:24 AMJeff Moden - Saturday, February 4, 2017 3:35 PMThanks for the very timely article, Rodney. I agree that my right index finger will feel a great loss and not being able to turn it all off during installation.It would appear that you can disable both error and feature reporting fairly easy, once made aware of it. Please see the following MS article. https://msdn.microsoft.com/en-us/library/ms143343.aspx While the write up there is all very interesting, the very last paragraph quickly summarizes how to disable both and it's done without having change a policy or registry setting. The registry setting appears to be only for the time-of-day when the feature reporting would occur if left enabled.
Sad to say, that article has disappeared - that url now redirects to https://msdn.microsoft.com/library/bb500395.aspx which contins no information at all about CEIP.
It might be useful if someone could tell whether the method in the now inaccesible article still works and if it does describe it in this thread.
I tried the link and my bookmarked page, but both redirect to the page you have above that tells us nothing about CEIP. I read it while the page was still up and did it, so here's a condensed version of what I remember:
1. On the SQL Server, open Error and Usage Report Settings. On my Windows Server 2012 R2, it's Start...Microsoft SQL Server 2016...SQL Server 2016 Error and Usage Reporting.
2. Clear the checkboxes. There's one for error reports and one for usage reports.
3. Click OK when done.
4. If you're running a cluster, don't forget to do the other nodes.
5. I believe I failed over to make sure the settings stayed as I left them.
6. With SQL 2016, there are system services for the CEIP, one for SQL and one for SSAS. I took the extra step of disabling them.
If anyone has anything to fill, please feel free to do so. I hope this helps.
June 14, 2017 at 1:38 am
This link appears to contain the same information on disabling phone home as the 'disappeared' link.
Viewing 14 posts - 1 through 13 (of 13 total)
You must be logged in to reply to this topic. Login to reply