That's one of the issues - these things get changed, we, the customer, don't get told why. Suddenly there's a new patch (which we find by accident as we aren't told about that, either), we go to get it - and find, "gee, our version of SNAC isn't here, but there's this starter edition instead - that is not what we use".
One of the replies I found over the months of seeking answer was "just run setup...." no way, last time I did that on an assumption, it did a full reinstall of the SEPM and I ended up having to do a full uninstall and starting over.
This time they have changed what setup does in SNAC - but are we told? "it's in the release notes". No, that isn't where it should be. That's too important to bury. That's a critical change that should be announced up front, not page 20 of 30 pages of "notes".
We IT people, even the security, antivirus, whatever, folks wear more than one hat - me it's about 10. I don't have time to read all 1500 pages of getting started, administrators guide, installation guide and so on to find buried bits that are critical in nature. When such a big change is made, it's important to us and needs to be treated as a top item in any documentation, even announced here.
I guess my thing is that as much as I like the products, and yes, even the people, the documentation from Symantec, on the other hand, has been second class since SEP started and they moved away from SAV CE.
It's poorly organized, too large - a lot of words without saying anything. Give me facts, bullet points, place the critical stuff right up at the top "IMPORTANT: SNAC is now called the starter edition - same SNAC, different name" and "IMPORTANT: If you upgrade your SEPM or have to reinstall SEPM for any reason, you will need to run SETUP in SNAC to recover the SNAC features on your SEPM server". Those simple things, at the very top of a document would have saved me several days time.
Worse - the tech support people I've worked with this year - on 4 cases, 2 people, phone calls, emails, etc. - formal cases - they did not know any of this either! In fact, I had to train one of them on how to recover SNAC abilities if you reinstalled SEPM - after I figured it out on my own. Then along comes this release and WHAM, we start over! They changed it AGAIN! Quit doing that! Once you have an install or upgrade method for the 12.1 seriies, MAKE NO OTHER CHANGES. Save the next way you install or set it up for version 12.2 or 13.0 or something, but geesh, this constantly changing how you install and set things up - ALL in the same version is just too much. That is a major change and should come with a major update, not a patch. Making such a change in a maintenance patch, then not documenting it where we can find or see it - no wonder there is much frustration. The people there don't have to deal with this on a daily basis - I do. And it's worse when there are so many bugs and issues that I have to reinstall several times, then there's a minor version change and suddenly product names change, and install methods change.
The product is fine - it's the presentation, installation, and documentation - plus the fact that support doesn't even know what's going on...... and now this is the second time in a week I've found advice that contradicts. one says copy an xml file in, another says "no, don't do that!"
A weeks or so ago, it was the same thing - one fellow - an advisor or employee, can't recall, says you don't want a space after a comma in a certain spot in an IPS sig, others say you don't want any spaces after commas in the sig in any place, another says that both are wrong, you DO want a space after each comma (and he went through the same thing I did with all the wrong or bad information)
(suggestion - if you don't have a fact, are not dead-certain you are right, please don't pass along iffy or bad advice. Others are lurking, watching, and will follow said bad advice, even passing it along to others later.)
Right - I'm not in a very good mood over this - I have spent months on cases that so far have solved nothing, I've wiped and reinstalled and created databases that didn't need wiped or recreated thanks to mistakes in support, I've ended up reinstalling SEPMs multiple times because no one there can keep track of SNAC or how to get it back after reinstalling SEPM (that's just plain dumb that the SEPM install doesn't see that you have SNAC and retain it, or let you know that if you own SNAC you need to run something else. The licenses are there - can't the install see the licenses and put it back???).
We've not had SNAC availble to work with because each SEPM reinstall blows it away and no one knew how to get it back. I've lost just a ton of time on these - It's just plain too complicated - and that's because of poor documentation and KB articles, and support simply not knowing the product.
And no offense, but the caliber and quality of answers in the connect forums for SEP has sort of dropped in the last year or so. it's getting harder and harder to find the correct answers - there are a lot of guesses out here, but few solid correct answers, and the numbers of people answering correctly seems to have dropped as well.
But then I did predict this several months ago - it's quantity vs. quality. The numbers are up, the quality of the answers, the correct answers, that's down.
Over the past several months, I've had more than one question in here go totally unanswered. Back when I was doing support in the 90s, that was not allowed! No question or post ever went unanswered, ever. Now you see a lot of them.