Avy,
if you have access to the remote computers from a PC running XP xpprofessional,
you can run the command:
systeminfo /s computername(computername being the network name of machine
you are quering)
This will list all the servicepack and uptates on the machine.
I think that the command only
Ok thanks Richard.
Avy Wong
Business Continuity Administrator
Mohegan Sun
1 Mohegan Sun Blvd
Uncasville, CT 06382
(860)862-8164
(cell) (860)961-6976
Richard Sims
<[EMAIL PROTECTED]>
Sent by: "ADSM:To
I don't think that Tivoli digs any deeper than the base level.
there are windows scripts that will return that info. You
could either manually run one on each client, or set it to run as part
of a pre or post schedule command.
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAI
From my experience, the Client OS Level which TSM captures is the
basic level, which identifies the OS generation, rather than deep
details. In Unix, such basic info is obtained via the uname() system
call, and in Windows via the os() call.
Richard Sims
Thanks Doug. Is there a way to also capture the Window Service pack version
into the select statement?
Avy Wong
Business Continuity Administrator
Mohegan Sun
1 Mohegan Sun Blvd
Uncasville, CT 06382
(860)862-8164
(cell) (860)961-6976
"Thorneycroft,
Doug"
<
select node_name as node, CLIENT_OS_LEVEL as OSVer, client_version as v,
client_release as r, client_level as l, client_sublevel as sl from nodes order
by v,r,l,sl >c:\Outputfilename.txt
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of
Avy Wong
Sent: F
Hello,
Is there anyway I can run a select statement to capture the node
names, TSM client version, Window OS and SP version?
I see vss error popping out more than usual, and I want to determine the SP
version on the Window boxes without logging into each box to find out.
Thank you for y our
We had an event last night that we REALLY don't want to go through again -
we're still trying to figure out why/what happened, but the short form is that
our AD DNS entries all disappeared.
Luckily we had a Linux box running a slave DNS that we could restore to the
previous day and convert to a
All,
One BU in my company is finding the comparison of TSM55 vs
Brightstor 12d. The environment composed with 2 platforms
(Windows,Linux). I would like your suggesion or some document which
compare between that product.
Best Regards,
Wira Chinwong
Engineering Department Manager
SCSi Co.,
At this point, I think it would be useful to see the following output, just
to make sure we're all seeing the same thing..
from your library manager server:
Q DRIVE F=D
Q PATH F=D
Q LIBRARY F=D
On your library client server:
Q LIBRARY F=D
At 03:26 PM 10/2/2008, Remco Post wrote:
One other th
Normal mode does not allow for point in time recovery of the database,
but will automatically clean out the oldest entries in the log once it
gets full.
Roll forward mode does allow for point in time recovery, however, the
only way to clear it is to do a db backup as it will not automatically
clear
HEEHEE! I knew somebody else had to have wanted to do something
similar. It's exactly what I was thinking of.
It's unsupported, but if I can get it accepted into our code base(will
including the PDFs suffice to keep it tagged as not our code?)...
I'm so glad to see it wasn't a stupid idea, and t
mcunix:> onbar --
exec(): 0509-036 Cannot load program onbar because of the following
errors:
0509-150 Dependent module /usr/lib/ibsad001.a(bsashr10.o)
could not be loaded.
0509-152 Member bsashr10.o is not found in archive
I've been asked to look into fixing this error so th
TSM Server v5.3.3.1 running on AIX
Having some problems running a retrieve from TSM storage:
I run the following command
dsmc retrieve -pick "/wload/smvp/app/archive/archive/*"
"/scdhold/bamrestore/"
I see some output, but the 'pick' stops after 1098 entries and does'nt show
all of the archives
On Oct 3, 2008, at 12:19 AM, Kiran wrote:
Any more suggestions on the below query please.
I want to know the difference between normal and roll forward mode of
recovery log
Have you read the "Normal Mode versus Roll-Forward Mode" in the
Administration Guide manual? That section provides a go
Hello,
Kiran schrieb:
> Any more suggestions on the below query please.
>
> I want to know the difference between normal and roll forward mode of
> recovery log
In normal mode the transaction log is cleared from the logfile after
commit. Database recovery is only poosible to the last full/incr db
16 matches
Mail list logo
