Just wondering if anyone can shed some light on this for me? I've recently upgraded our ESET desktop clients from v4.2 to v5.0. It's all gone fine - nice and easy, but there is one small niggling problem which is irritating me: there seems to be a hangover between the options chosen in the v3/v4 section of the Config xml, and those in the v5 Desktops section. As an example, in v4.2 we had set the option to hide the splash screen at startup. In v5.0 this option is not set (i.e. it should the splash screen), but it looks like ESET is reading the old settings and applying them to the new version, as the splash screen is not showing. The same goes for other settings, like requiring a password to access the Advanced options menu. The settings we've applied to v5.0 are ignored and it uses the v3/v4 section options instead. I wasn't sure if this was because the Default Policy at the route of our ERA server was originally set up in v3, so I've created a whole new default policy which ONLY applies v5 options (the only blue config items are the ones I've changed in the v5 sections), and I think it's working. The thing is, the Default Policy only contained settings for v3/v4 clients, nothing else, so surely the new v5 clients should have ignored those settings and just applied the v5 settings from the assigned policy at the next level down? (note: 'Override any chile policy' option is NOT enabled on the default policy) Am I going mad?