The Great Content Service Swindle
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
4 weeks ago
My frustration with SAMP continues to grow. I raised a question earlier regarding Adobe Acrobat showing as non compliant because software is found on our estate when that software was installed as part of a subscription.
We raise a ticket asking why Acrobat DC 2023, DC 2024 and DC 2025 were showing as non compliant when this is software installed as part of a subscription. Also the software discovered cannot be run unless the user can log into their subscription. Support said that we needed to link the software as a child of the subscription. I challenged this because DC 2023 is 2 years old so asked why I need to amend models to make the system work. Support stated that the issue is with the Content Service.
I cannot accept that the content service has not had an update request for Acrobat DC 2023 so why is it missing. Also this software is only available as a subscription so should be operating correctly OOTB.
Given the number of glaring errors I am seeing, I am starting to think that the Content Service is just a con. SN should be all over the Tier 1 vendors but I am just not seeing it. As I said software 2 years old and not behaving correctly for what it is!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
4 weeks ago
Hi @andynewey ,
I got your point and I’m as often surprised about the content 😶.
Did you already raised a ITAM content request with the content team and not as standard case. You can find it in the support portal > automation. The team response with more insights per request.
Best, Dennis
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
4 weeks ago
Yes I already have a Content Service update request. I have sent them all the products that are not normalized. They have sent us an initial update and are continuing to work through the products.
I just do not understand why we have issues, if everyone from around the world is contributing to the Content Service then it should be almost perfect. To me its as if they have a basic Content Service that they send out to a new build and then expect the organisation implementing SAMP to send in a Content Update and SN updates that instance with the discovered software of that instance.
My personal opinion is that the Content Service described does not match the Content Service Provided.
