Windows 2003 SP1
Thank You,
Dennis Peacock
EBCA
Acxiom Corporation
501-342-6232 (office)
From: Martin, Jonathan
[mailto:JMARTI05 AT intersil DOT com]
Sent: Friday, September 24, 2010 2:56 PM
To: Peacock Dennis - dpeaco; wts AT maine DOT edu;
VERITAS-BU AT mailman.eng.auburn DOT edu
Subject: RE: [Veritas-bu] Windows Client install blows up
duringtheinstall....
“Run as Administrator” is only applicable to 2008/2008R2. Even
if you have the administrator privilege, you don’t use it automatically in
Windows 2008 by default. (This behavior can be turned off.)
Which OS version is this client?
-Jonathan
From: veritas-bu-bounces AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-bounces AT mailman.eng.auburn DOT edu] On Behalf Of Peacock
Dennis - dpeaco
Sent: Friday, September 24, 2010 3:48 PM
To: wts AT maine DOT edu; VERITAS-BU AT mailman.eng.auburn DOT edu
Subject: Re: [Veritas-bu] Windows Client install blows up
duringtheinstall....
Wayne,
Thank you. I did open a ticket and have the server rebooted
after the NBU 5.1 was uninstalled. I’ll go try the “run as administrator” but I
don’t think that that will matter any since I’m on the box as an admin. I’ll
also try the turning off of the A/V stuff.
Thank You,
Dennis Peacock
EBCA
Acxiom Corporation
501-342-6232 (office)
From:
veritas-bu-bounces AT mailman.eng.auburn DOT edu [mailto:veritas-bu-bounces AT mailman.eng.auburn DOT edu]
On Behalf Of Wayne T Smith
Sent: Friday, September 24, 2010 2:45 PM
To: VERITAS-BU AT mailman.eng.auburn DOT edu
Subject: Re: [Veritas-bu] Windows Client install blows up during
theinstall....
Judy's recommendation to "run as administrator" is
a good one. That an older version was uninstalled makes the hair on the
back of my neck tingle ... because of the uninstall, I recommend a Windows
reboot before installing 6.5 ... and if anything NBUish happens on the reboot,
reboot again. Turn Anti-Virus off temporarily and try the install again.
(I don't have a lot of Windows machines either, but these (3) actions
have allowed the NBU 6.5 install to complete for me (when it didn't on the
machine owner's first try).
I've had it suggested from someplace that defining a policy
for the client and opening the vnetd port (13724) first is needed, but that has
NOT been true for my cases (I usually open the firewalls after install and
define an NBU policy after that).
***************************************************************************
The information contained in this communication is confidential, is
intended only for the use of the recipient named above, and may be legally
privileged.
If the reader of this message is not the intended recipient, you are
hereby notified that any dissemination, distribution or copying of this
communication is strictly prohibited.
If you have received this communication in error, please resend this
communication to the sender and delete the original message or any copy
of it from your computer system.
Thank You.
****************************************************************************
