It might be the difference between “not
supported on” vs “doesn’t work on”.
i.e. If it works for you fine but if it
doesn’t don’t expect Symantec to help because it is “not
supported”.
Vendors often do the “not supported”
as their out if you use it outside of the narrow configuration setup they
used. For some things this is rather important (e.g. You wouldn’t want
to put a Production Oracle DB on an “unsupported” platform like
Fedora Core 6 despite the fact that it works just fine because when you have your
first error at some point if they can’t resolve it via standard
troubleshooting they’ll simply say “that isn’t a supported
environment so we can’t proceed”.)
From:
veritas-bu-bounces AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-bounces AT mailman.eng.auburn DOT edu] On Behalf Of Tony T.
Sent: Monday, March 31, 2008 4:06
PM
To:
veritas-bu AT mailman.eng.auburn DOT edu
Subject: Re: [Veritas-bu] Cannot
install Admin Console: Install interrupted?
On Mon, Mar 31, 2008 at 2:37 PM, Bill Tsukahara <bill_tsukahara AT richards DOT com>
wrote:
Tony,
Unless I'm not understand what you mean by "65 admin
console", I upgraded to 6.5 a week ago and I am running the Admin
Console on Vista.
Hmmm, guess we have two different answers then? Earlier:
"
The 65 admin console doesn't work on Vista. I had
the same issue. Per Symantec, it will not work on Vista and there are no
plans for it in the next dot release.
"
But if yours is actually working, I wonder why I can't
get mine working? I have it on XP boxes all over the place so the
procedure is really not that difficult. I am running 6.5.1.a on the
master (Solaris) and have a few copies of the Admin Console on XP boxes.
Just this one Vista one giving me grief.
