I am experiencing the same error message and symptoms. I have NIS 2009 as well as Ghost 10 - And suspect NIS 2009 as the root cause, as the problem surfaced only after upgrading to it from NIS 2007, and then re-installing Ghost 10.
Qurkily, each product seems to use a different version of LiveUpdate. At least, visually they look different, and the one in NIS 2009 does not give any errort message, and does not appear to attempt to update Ghost. So it's only the Ghost version that fails with the error messsage about a pre-release or Beta version of a 2005 product. The message does not specify which product, but it's the update to Symantec Common CLient that fails. So I guess that is the down level item.
If NIS liveupdate is updating common client properly (I assume it is), then I may be OK. But I seem to have to run liveupdate in NIS 2009 and in Ghost. I'd have thought I should only need to run one of them and it would update both products.
LiveUpdate was completely re-architected for the 2009 products. It is indeed very different than previous versions and is designed to update 2009 only. It is required to run LiveUpdate seperately in both products.
That said, what steps have you tried to resolve the LiveUpdate error? Also, with Ghost you may not need the common client update. Have you had any other issues with Ghost?
I don't have any other issues with Ghost now. I did for a while, just recently, after re-installing. I kept getting error message "internal error 2753 vprocsvc.exe", but managed to overcome that with the help of a live chat with Norton technical assistance. It involved using the removal tool, and RUNning "regsvr32 vbscript.dll". (That latter part was from a Microsoft tech forum page and is what I think cured the 2753 problem). I then re-installed NIS 2009 and then Ghost 10.
As with the other people with the problem, the first liveupdate in Ghost after re-installing ran OK. The later ones hit the "Beta version" issue.
I've taken all of the steps that were outlined earlier in this thread. It made no difference.
From your reply, it sounds as if, despite the message from Liveupdate in Ghost, I can ignore the matter, and just accept that each product runs its own Liveupdate and one produces a spurious error message. That's fine by me.
If I choose to update to Ghost 14.0, will this get me back to a single version of liveupdate - and so eliminate the problem? I've not updated as I've nor seen a need to .