Not what you are looking for? Ask the experts!
NIS 18.104.22.168 (Complaint): I object!
One of four PCs received this update today.
Again I object to the fact that I, your customer (unlike almost every other product I own), have zero control over when and if your software application is updated. NIS 2010 was a real series of debacles with problematicupdates.
So far, NIS 2011 has been having a much smoother deployment. Still I object to that you deny me any control. Right now, one of my four PCs has 22.214.171.124. Seemingly, it is one of the first set, you are deploying to. But I don't want to be first. I would much rather wait to see how it shakes out for all the eager beavers to try something new, and then patch in 2-3 weeks from now when I am ready. Also, I typically update software on my own personal schedule and keep my systems in sync to reduce my work load for testing.
There will be those who will say if you allow me this control, then my window for exposure to malware infection will be significantly increased. To that I reply, that NIS 126.96.36.199 was probably sitting around internally at Symantec for weeks now, and yet I survived just fine.
Yes, I have raised this issue in the past and will continue to raise it as long as this major flaw is ignored and this matter of customer respect is ignored. (On the whole, I find NIS to be better than most of the other options. Thus, despite this issue I continue my patronage.)