Jump to content

Testeur09

Members
  • Content Count

    714
  • Joined

  • Last visited

2 Followers

About Testeur09

  • Rank
    Commentator

Recent Profile Visitors

183 profile views
  1. 2012 R2 with Cluster is not supported by KES 10 MR1. You have to wait for the new version of Enteprise Edition.
  2. FSEE has significantly less functionalities than KES which makes it more reliable and much faster. I guess it also benefits from a better QA from Kaspersky's engineering teams. It also support specific server configurations (like clustering) which are not supported by KES.
  3. Some more tips : - Read the Administrator Manual, it contains extremely valuable information especially if you are new to the product. I've seen too many persons install first then ask questions later. - In-place upgrade never works correctly. Want to update yu agent, client, migrate from another third-party product ? Always uninstall first, then a fresh install after that. - Install Network Agent and Antivirus separately (one task for each). - Do not start to install Antivirus clients unless all agents are up and running. Stay in control is the key. - Choose the right product for the right computer. Too many people still ignore FSEE editions. - If you are in charge, make sure your infrastructure is healthy. If you AD/DNS is a mess, do not expect your deployment to go smoothly. - Separate computers by type (servers and workstations) and roles (AD, Hypervisor, DB etc...). It will allows you to create for each group custom policies and exclusions rules without worrying about inheritance and stuff. - Performance is a HUGE concern, be sure you thoroughfully test it before deploying clients and policies. - Do not trust default exclusions provided by Kaspersky - most of them do not match. Dig Technet and your vendor documentation for knowledge about what to exclude. It's a huge work but you will have to do it only one time, and it can be reused no matter what antivirus solution you choose. - TEST, TEST and TEST again before deploying into production ! Updates, Maintenance Pack, new policies, everything - in worst cases, you can brick an entire IT infrastructure if you are too trustful. - If possible, use Microsoft built-in solutions when applicable - WSUS, Applocker, encryption, etc... Do not put all our eggs into the same basket. I would strongly advise against using IP instead of DNS for network agent however, it's gonna be hell when you migrate your server or antivirus solution.
  4. Sorry but this is the business forum. Unless you are running a very small company with no IT (in such case, using a personal antivirus client is enough), you won't upgrade to 8.1 right now.
  5. Wait, you deploy a new OS before checking application compatibility ? And you think Kaspersky is the problem ? Seriously :/
  6. If you are in a big environment (let's say 50K users at least) here is what happens from my field experience : - You deploy a new OS once every 7-8 years or so. The new OS is being deployed gradually. - You deploy a new antivirus only when End of Life is near, along with a new master. Should be roughly every 4-5 years. - All of this is fully automated and done outside of working hours. For plants running 24*7, either they are never upgraded (and that's why I have customers with 2K workstations, or even NT4) because they have no internet/USB access (those are linked to very specific industrial machines) or you have spare machines you can test your master on. I'm not sure I understand your point - if you try to do an in-place upgrade, it doesn't matter if it's Windows, an antivirus client, or a third-party app - chances are significantly high that something wrong will happen. And if in-place upgrade isn't supported by the product editor, you will be all alone to try to solve the issue (might aswell look for another job right away). As for antivirus client, they keep having a deeper and tighter implementation on the OS/hardware side, especially with UEFI and Secure Boot by example, which makes them in-place upgrade even more harder and dangerous. Feel free to continue this with private messages if you wish.
  7. Microsoft always recommended to slipstream a service pack then reinstall from scratch instead of simply applying a service pack. It also works for their applications, for Exchange by example installing a Service Pack is not supported since 2010 SP2 (?), and starting with 2013 when downloading a Service Pack you download the full software instead. Wipe and load works, in-place upgrade doesn't, it is just as simple as that.
  8. Refreshing an AV client using an in-place upgrade is a bad practice anyway.
  9. They request it when logs aren't sufficient, which happens extremely rarely.
  10. FYI other companies, including Microsoft, do this. Of course the third-party vendor has to make sure the issue isn't linked to a hardware/hardware driver failure.
  11. Thanks for the feedback Mr Medvedev, but the issue here is Datacenter Edition support. It is becoming the mainstream Windows edition for most mid to large companies out here and it is never supported in due time as it should. Maybe Kaspersky intends to scrap Enteprise Edition in the future, and maintain a single product ? It would make sense, but from field experience FSEE is a lot more stable and reliable than KAV/KES products :/
  12. Pas de version de KES compatible pour l'instant.
  13. It's the opposite, for an OS server there are is a significant supplementary amount of tests required compared to a client OS - specific conditions like clustering, virtualization, failover etc... and because you won't encounter them on client OS you have to start from scratch again (where for you client antivirus you can capitalize on feedback and hotfixes from your consumer client version, if they are build onto the same code base). Also, performance and stability issues will be more critical on a server (which is a centralized system) than on a client. And you have to test also compatibility with several enterprise-level applications (AD, Exchange, SAP etc...) at least. But yes it isn't an excuse for a lack of 2012 Datacenter Edition yet. Also 2012 R2 is coming in a few days and no feedback at all from the developer team still.
  14. Well you got an exception amongst third-party vendors. Most software companies out there doesn't have the same amount of developers, support teams, and/or the will to be able to support an OS the day after the release, and provide a well-tested version of top of that. Also this new version is not always free. And for most companies this isn't an issue because, amongst other things (budgets, politics etc.), technically implementing a new OS properly is a huge work, which takes usually one or two years for big ones. I wouldn't hold my breath about Symantec products however, last time I worked with them it was with Backup Exec 2010 and we had to wait two years and half to have a stable version (the third release !). Releasing a antivirus client at the same time of a new OS is one thing, and robust one is another. Even Microsoft is unable with a this faster release cycle they created themselves for now.
×
×
  • Create New...

Important Information

We use cookies to make your experience of our websites better. By using and further navigating this website you accept this. Detailed information about the use of cookies on this website is available by clicking on more information.