mhd99

Eventually, decided to ignore best advise and installed express 2014 on the DC. as well as SSMS 2018. Followed various guides and after about 4 hours the new db was updated. thanks for assistance. Martin

sadly - after 3 days trying and having installed SSMS (2014) I don't know enough to get a successful connection. I now have 12 days before licence renewal so time is running out. Look like this update is going to need to total re-install across the estate - unless other suggestions are available? Martin

yes, - however it also requires various installs (Management Studio and other requirements) , on the DC in order to export / import the DB - which I'm not keen to do as that would be more complications to process. Given this then is it better to do the fresh install ? Martin

MartinK, - thanks for the suggestion. I haven't attempted to install 2014+ (yet). I'm also considering doing to totally fresh install on another server - appreciate this will mean losing the database etc and having to visit all the client PC to repoint the proxy setting. Guessing the upside is that the new DB would not be on a DC - and up to date - downside is having to visit PC's. ? unless theres any other possible solution?

I found this out after discussing with Eset support, after the upgrade task - although it said successful, nothing changed. A resubmit was running for 23 hrs before I spoke to support who basically said … tough... https://help.eset.com/esmc_install/71/en-US/database_requirements.html

Current set up is that I our SMC Centre v 7.0.577.0 runs on our DC, has happily done so for some time. The SQL Express version though is 2008R2 - SMC is the only SQL 'application' on the server. The latest update though requires SQL 2014 upward. Therefore it wont update. In order to export the database data to another upgraded instance requires various installs - which I'm not happy to do, (as its a DC) and Eset now suggest that SMC shouldn't run on a DC. Is my only option a fresh estate wide re-install ? unless anyone has any other suggestions. …..

we use a 3rd party support company and they basically stated if we didn't install IntX then , in the vent of any crypt type infection hitting any of the kit, including servers then a inflated fee for rebuilding etc would be imposed. I did check that Eset / Sophos should co-exist and in 80% of our PC's it does. Its only the Adobe CC users which the conflict appears top affect. I need comfort in that if the designers go to web sites - and they visit all sorts - they have to - then the protection is there. Martin

We have about 25 windows PC 's with Eset 6.5 installed. As part of a better protection and also to comply with a 3rd party support contract we also installed Sophos Intercept X. This worked absolutely fine apart from 4 PC's which have Adobe CC installed. These PC's then ran very slowly when opening and saving files. illustrator & photoshop mainly - often showing not responding etc even if saving locally rather then the file server. For the last 3 weeks I've been arguing with Sophos that despite their s/w supposedly being AV independent - it isn't - as a) If I uninstall Sophos but leave ESET on then the PC's save files fine. b) if I install Sophos but without ESET they save fine. Sophos have said its Eset real time conflicting with their runtime protection. This is a bit of a problem as the designers are constantly web surfing looking for "inspiration" so are probably more of a risk then other users, yet I've had to weaken their protection. I've applied policies to both products to attempt to get the products to co-habitate, but without success. It only appears to affect Adobe CC software and I know the files are quite large (25mb upward) - anyone else in the same position and any suggestions to policies / exclusions I should apply - or should I just not use Sophos on these 4 PC's? Cheers in advance. Martin