Rather than push. Pull the client - I realize this is a hassle
but from the begining - Veritas has had issue's pushing the client
from One server to the next - expecially 3.1.4.
Copy the entire Veritas CD to one drive on a server that has at least
465MB free space for this CD. Then share the CD folder - the logon
to any 2003 and select start\run the cd share name - then run the
launch.exe then the client install that should work unless you don't have
admin rights on the local machine?
A push of the client some-times fails - a Pull always works depending on
Network traffic,
You may want to wait until Network traffic is down and try and push the
client - All computers need to be restarted after the client install -
WOL works great for restarting or turning on computers from a schedules task
or script just prior to backups - you can actually turn on any computer
within the WAN with WOL "Wake on LAN" providing the NIC has a connection
with the old mother-hubbard board.
-----Original Message-----
From: Bobby Williams
To: Williams, Kristopher L; Ross, Charles D (Charlie);
veritas-bu AT mailman.eng.auburn DOT edu
Sent: 1/10/2005 3:45 AM
Subject: RE: [Veritas-bu] Windows 2003 Client Install Problem
Is there not a way to push the software to the Windows servers from
within Veritas? I thought that if you had a Windows master, you could
push the client software to the windows clients (like you do from a Unix
master to the Unix clients).
Bobby Williams
Sr. Systems Engineer
4250-A Benton Drive
Chattanooga, Tennessee 37406
Pager: 423-819-3336
Phone: 423-624-2600 x122
________________________________
From: veritas-bu-admin AT mailman.eng.auburn DOT edu on behalf of Williams,
Kristopher L
Sent: Sun 1/9/2005 11:05 PM
To: Ross, Charles D (Charlie); veritas-bu AT mailman.eng.auburn DOT edu
Subject: RE: [Veritas-bu] Windows 2003 Client Install Problem
There was/is a problem with installing NetBackup using the batch files
while logged into terminal server. It has something to do with the
install package trying to write to console0, but since your logged in
via terminal server you can't get the console message.
For 2003, you can get to the console remotely if your using a Windows XP
client. Try going to a command prompt on the XP machine and run mstsc
/?. One of the options is /console. For Win2k, the only answer is to
install from the console. I don't like this one bit, but until Veritas
gets their act together and learns how to make the install package work
I'm afraid that were stuck with it. Hope this helps
Thanks,
Kris
________________________________
From: veritas-bu-admin AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-admin AT mailman.eng.auburn DOT edu] On Behalf Of Ross,
Charles D (Charlie)
Sent: Sunday, January 09, 2005 4:57 PM
To: veritas-bu AT mailman.eng.auburn DOT edu
Subject: [Veritas-bu] Windows 2003 Client Install Problem
I'm having issues trying to install the Veritas client on Windows 2003
servers. When the batch file is running against the servers, the W2K
servers will install fine, but the 2003 servers fail. This also happens
when I try to select the 2003 servers from the client msi file on the
CD. If I log onto the console of the 2003 server, I can install the
client just fine from the install point, using the client msi file and
selecting install to this pc only.
I have heard there is a registry hack to allow Veritas batch files to
run on a 2003 server, has anybody heard of this?
Thanks
_______________________________________________
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
|
