I solved this problem by publishing install instructions that point to a batch 
installer.  I control the version in the batch and the batch detects the 
Windows version and installs the correct version.

Andy Huebner

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of 
Zoltan Forray
Sent: Monday, September 16, 2013 8:34 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: [ADSM-L] Windows Clients and Non-Supported OS Levels

This is mostly a gripe at IBM..........

Why do the Windows clients allow themselves to be installed on non-supported 
OS/levels? or at least issue warnings?

My Windows folks (yes, they are being lazy and not reading all the 
readme/docs), are constantly installing miss-matched/not supported clients 
(i.e. 6.4 on W2K3 servers, which is not supported per 
http://www-01.ibm.com/support/docview.wss?uid=swg21197133).  Then of course, 
they can not be  downleveled.

When someone contacts me about issues with their client/backups and I say "not 
supported combination of OS and TSM client level", their response is, "
*then why did it let me install it if it isn't supported on this OS*"

--
*Zoltan Forray*
TSM Software & Hardware Administrator
Virginia Commonwealth University
UCC/Office of Technology Services
zforray AT vcu DOT edu - 804-828-4807
Don't be a phishing victim - VCU and other reputable organizations will never 
use email to request that you reply with your password, social security number 
or confidential personal information. For more details visit 
http://infosecurity.vcu.edu/phishing.html