Yes, the CMU300.Nap doesn't apply in 3.0. First, although Virusscan Enterprise 7.0 appears to be installed in the repository it really isn't. If you go to Repository, Software Repository you'll see that the 7.0 plugin is there but the actual product isn't. Go to Repository, Check In Package, Product or Update, and navigate to the location of the 7.0 software. Now when you look at Master Software Repository you'll see a second entry for 7.0 that is listed as Install.
A Deployment task is available by default if you want to deploy. To create the update task select the level applied and Schedule Task. Select ePolicy Orchestrator UpdateUpdate Task and configure. Note also that you no longer need Mirror to update DAT's. Just download the SuperDAT, go to Repository, Check In Package, and select SuperDAT. The DAT files now go into the repository itself and you can flag old SuperDAT's as Previous each time you update them.
Warnings: two things I learned that I hate. 1) ePo 3.0 requires IE 6.0. I have apps that require 5.5 and I hated being forced to go to 6.0. 2) You can't install ePo 3.0 on a domain controller. This forced me to install it on a server that I didn't want to. So far these are the only shortcomings I've found and they are far outweighed by the ease of deployment of DAT's and the new logical structure of the program.