Symantec telling us that they know about a problem and we will get to it eventually does not really help anyone out.--especially on a product that is on the shelves and being sold to unsuspecting customers.
I just experienced this issue with a brand new Dell T310 SBS 2008 server.
I installed BESR 2010 for SBS initially on the C:\ drive.
I did not register the product for a few days, but immediately experienced issues where it would not work after a day or so.
Jobs were not running, you could never connect fully to the agent etc if the server was on for more than a day.
I even tried registering the product with my key, which looked like it worked, but then kept getting notified my product was 'unregistered' in a popup above the systray icon every time I rebooted.
The countdown days never changed but it was annoying.
Here is my experience in getting this issue and resolving it:
Starting with a non-working instance (see above):
I uninstalled the program and did not keep any of the data when prompted for a later reinstall.
I installed the program but this time I chose to use a secondary HD as the install path. So this time I went to E:\program files (x86)... and so on.
I immediately began receiving the issues regarding not having permissions to perform the operation like the original post indicates so I could even get BESR to run correctly.
Again, I chose to uninstall BESR and live update as well--then rebooted.
I then removed the registry key for Symantec under hkey\local machine\software.
I made sure no previous instances of Symantec folders/files from my first couple of tries existed on C:\ or E:\
Rebooted again (SBS 2008 takes forever) and then installed BESR once more.
This time I immediately entered my key when that step arrived.
So far so good, the program is running and backups are working.
Perhaps the permission/rights error is related to a second install, or perhaps when its not on the C:\ drive.
In any case, the earlier mentioned 'solution' reminds me of my experience with my last Symantec purchase. SEP v11 back in 11/2007.
Waiting for a patch for a 'finished' product is just bad business.