.
In fact, using only the information that TSM captures, Windows Vista and
Windows Server 2008 will appear identical. They will both have:
PLATFORM_NAME WinNT
CLIENT_OS_LEVEL 6.00
Fortunately, for the greatest reason I use this information, Vista and
2008 behave the same. That is, they bo
Subject
Re: [ADSM-L] window OS, SP version
and TSM client version
10/03/2008 03:26
PM
Please respond to
"ADSM: Dist Stor
Manager"
<[EMAIL
[ADSM-L] window OS, SP version
and TSM client version
10/03/2008 03:26
PM
Please respond to
"ADSM: Dist Stor
Manager"
<[EMAIL PROTECTED]
.EDU>
ailto:[EMAIL PROTECTED] Behalf Of
Avy Wong
Sent: Friday, October 03, 2008 12:20 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: window OS, SP version and TSM client version
Thanks Doug. Is there a way to also capture the Window Service pack version
into the select statement?
Avy Wong
Business Conti
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
e-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of
Avy Wong
Sent: Friday, October 03, 2008 12:08 PM
To: ADSM-L@VM.MARIST.EDU
Subject: window OS, SP version and TSM client version
Hello,
Is there anyway I can run a select statement to capture the node
names, TSM client version
ent: Friday, October 03, 2008 12:08 PM
To: ADSM-L@VM.MARIST.EDU
Subject: window OS, SP version and TSM client version
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, an
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
