Jump to content

whitefern

Members
  • Posts

    19
  • Joined

  • Last visited

  • Days Won

    1

whitefern last won the day on September 9 2023

whitefern had the most liked content!

About whitefern

  • Rank
    Newbie
    Newbie

Profile Information

  • Location
    USA

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. @Marcos Let me ask you this? Was there "Big Demand" to disable LICENSING notification/status? Which is the core part of your App. Did a lot of users write into to ESET HQ stating that we desire and "demand" to disable all licensing related notifications?? Tell me. I am sure I will hear cricket sounds. Then why did ESET give users the option to disable licensing notification/status? What was the rational explanation? If ESET can users the options for licensing, they should also provide the option to disable "Missing Support for Azure Code Signing".
  2. @Aryeh Goretsky Thank you for your reply. But that is not a acceptable answer. Why should I upgrade to "business" version when home is also a "business" product? It is not just me who needs it. It is everyone who needs it. The disabling of notifications/status is a little stupid. Don't you think?? You allow disabling of notifications/status of LICENSING which is a crucial part of the software. But you won't allow disabling the notifications/status of "Missing Support for Azure Code Signing", is just annoying and stupid. And calling it "Business" only option is not acceptable. Please provide this options for the users in the next update.
  3. @Marcos @Aryeh Goretsky Again, I am posting the request of disabling of the status/notification of "Missing Support for Azure Code Signing". Please give the end users the option. https://forum.eset.com/topic/37708-allow-disabling-of-status-missing-support-for-azure-code-signing/ This was suggested by @itman
  4. Seriously? Are you employed by ESET or do you speak on behalf of ESET corporate? This is a forum where are users are posting valid and legitimate request and concerns. It is a bit Oxymoronic isn't it? EXAMPLE : LICENSING is crucial part of the software. If the LICENSING expires the App would not be activated and renewed. ESET allows the user to suppress the License status/notifications for such a core and fundamental function of the Application. But ESET would not allow disable of the status/notification of "Missing Support for Azure Code Signing"? But they allow in in ESET Endpoint? It does not makes sense. When both products are used in Business environments. @Marcos I have no way to reach out to ESET corporate. Isn't this forum is a place for that where you get user's request and send it to ESET HQ? I am not the only one in this thread. There are other users as well.
  5. BTW, it was not a question. It is BECAUSE it is a legitimate request. And the ESET Developers are ignoring a legitimate request from their user. While giving the users of ESET Endpoint the option and ignoring ESET "Home" products users is not acceptable. When clearly both are using in enterprise/business environments. Thank you.
  6. Yes. It is if this page exist. There are many several business and organisation that uses ESET "home" products. I will ask again. All I/We are asking is to give users the option to disable of the status/notification of "Missing Support for Azure Code Signing". It is just a Check Box. Users who disables the notification knows fully of the consequence. Please make it happen.
  7. @Marcos For several years (10+) we have been using using ESET "home" products in my organisation. Yes, we initially consider ESET Endpoint for all our client PCs several years back. But after careful analysis within our internal team and protocols, we decided to use ESET "home" product for my company. Although this is "Unmanaged" centrally, we decided to choose this route for several reasons. ESET "home" products is also a "business" product. All I/We are asking is to give users the option to disable of the status/notification of "Missing Support for Azure Code Signing". Please make it happen. It is just a Check Box. Users who disables the notification knows fully of the consequence. Thank you.
  8. It is great that you are adhering to the "Standards" of Microsoft. And I understand that other vendors are also requiring ACS support to be installed. But that has NOTHING to do with giving the users the option to disable of the status/notification of "Missing Support for Azure Code Signing". Please give users the option. Please provide an update where users can disable the notification. Thank you.
  9. As I have mentioned. Windows Update is disabled for our entire organisation for various factors and crucial reason. We can't able to install the ACS update. Unless, there is a "standalone/offline ACS Support" installer where we can apply to our clients. That is the reason why I/we are asking to release an update where we can disable of the status/notification of "Missing Support for Azure Code Signing". It is just a check box to make the status/notification disappear. Please provide this. Thank you.
  10. @Marcos It has be 2 plus weeks. We have been requesting the option to disable of the status/notification of "Missing Support for Azure Code Signing" ? When would you be releasing it? Please give users the options.
  11. It is not an acceptable answer. On ESET's website for business users, they also recommending "Home" products for business users who wants to lets users manages their endpoints/client PCs individually. The word "administrator" has a broad term for different organisation. Even for small business who are letting users manages their endpoints individually, there is an IT administrator. Hence the lines are blurred. Hence, "Home" products is/can be a ""Business" Product. @Marcos Please give the end users the option. When can I/We expect to receive the update where we can disable of the status/notification of "Missing Support for Azure Code Signing" ? Thank you.
  12. @Marcos When can I/We expect to receive the update where we can disable of the status/notification of "Missing Support for Azure Code Signing" ? Thank you.
  13. @Marcos Now that I/We have established all the valid reasons, could you please allow the disabling of the status/notification in the next update. Thank you.
  14. Users who don't update to the latest version of ESET Apps, knows fully of the consequence. Just give the users the choice to disable the status. You can also prompt a explicit dialogue box letting users of the consequence. Since it would be after Dec 2023, you should release an update to the app to let suppress the notification. Thank you.
  15. @Peter Randziak @Marcos We are not "Home" Users. Isn't it oxymoronic? On your very website for business users, you also recommending "Home" products for business users who wants to lets users manages their endpoints/client PCs individually. The word "administrator" has a broad term for different organisation. Even for small business who are letting users manages their endpoints individually, there is an IT administrator. Hence the lines are blurred. It is administrator's and business owners choice when to upgrade their Apps and OS. There are various mission critical factors. We are not on the same timeline as everyone. I strongly believe there tons of business who are in the same position. If your "Home" products can be using in small and medium business environment, then the "Home" automatically becomes a "business" product. If currently the users of "Home" products are able to suppress the notification the notification for Windows Update, ESET developers can definitely allow the users to suppress the notification the notification for "Missing Support for Azure Code Signing" If you can let business users disabled the notification, due to "administrator" are "responsible" for the system and it's security, you can certainly and definitely let administrator of small and medium business environment who uses "Home" product. Which technically becomes a "business" product. Which is by you own admission. Those who disable it, knows fully the consequence. Please and simply allow disabling of status - Missing Support for Azure Code Signing. It is not rocket science. Thank you!
×
×
  • Create New...