I've just run into an interesting problem. We're still running NOD32 v2.7. I just moved from RAS 1.0.x to ERAS 3.0.105. It was not an upgrade - it was installed on another server, all new configuration files were created, tied to policies, etc. When we were ready to move the clients, we created a new configuration task on the old server that removed scheduled events, and pointed it at the new ERAS for remote administration, where they picked up the new configurations. I set our laptops to scan every Sunday, and if missed, scan as soon as possible. That, and a dual-profile update are all that I scheduled. Now, a scan is performed every time a user logs on. Anyone run into this before or have any pointers? I've checked the schedule a number of times, and everything appears correct.