<TABLE BORDER=0 ALIGN=CENTER WIDTH=85%><TR><TD><font class="pn-sub">Quote:</font><HR></TD></TR><TR><TD><FONT class="pn-sub"><BLOCKQUOTE>we have more then 300 server in my company and we whats to update all the servers in a silent mode installation,
I have some servers with windows2k servers, and the other with windows 2003 servers.
</BLOCKQUOTE></FONT></TD></TR><TR><TD><HR></TD></TR></TABLE>
meirf,
you can perform silent MSI installations easily (after extracting the downloaded client file), no matter if W2K or W2K3 is running.
Following is an example installing the German version of TSM Client 5.3.2 (5.3.3 should be the same syntax). Sources are stored in "c:\programme\tsmclient\src" in this example. The given options were ment for a "clean" system with no previous version of the TSM Client installed. I have no idea if this works for updates!
TSM Client:
msiexec.exe /i "c:\programme\tsmclient\src\IBM Tivoli Storage Manager Client.msi" RebootYesNo="No" REBOOT="ReallySuppress" ALLUSERS=1 INSTALLDIR="c:\programme\tsmclient" TRANSFORMS=c:\programme\tsmclient\src\1031.mst /qn /l*v "c:\logs\tsmclient_5.3.3_MSI.log" ADDLOCAL="BackupArchiveGUI,ApiRuntime,AdministrativeCmd,Readmes,PDF"
Language Pack (if necessary; the MSI filename might be different for your language; you can skip this if you want to run the English version):
msiexec.exe /i "c:\programme\tsmclient\src\LangPack\IBM Tivoli Storage Manager Client - German.msi" RebootYesNo="No" REBOOT="ReallySuppress" ALLUSERS=1 INSTALLDIR="c:\programme\tsmclient" TRANSFORMS=c:\programme\tsmclient\src\LangPack\1031.mst /qn /l*v "c:\logs\tsmclient_5.3.3_lang_MSI.log"
You can leave out some of these options since the default values might match your needs (for example if you prefer the default installation directory; however, I prefer to have some kind of full control during installation process). I used these options (with slight differences) in our environment and it worked fine for us.
The switch "/qn" is basically what you are looking for, since this one indicates the silent installation with no user interface at all. The options "RebootYesNo" and "REBOOT" might also be interesting for you if you don't want the installation to make a reboot automatically if one is needed (since this could be painful in production environments). Nevertheless it can be necessary that you perform a manual reboot to make the TSM Client work.
Keep in mind:
You should run several test installations before updating your servers. You should also stop all TSM related services on the target system(s) before updating. Carefully check out, if the update process is successful. If (direct) update from 3.x fails, perform clean uninstallations before updating to 5.3.x. My given installation example might not match your needs.
It might be necessary to update MSI to version 2.0 on the W2K servers (checkout version of "msiexec.exe" placed in the "winnt\system32" directory).
I hope these hints can help you.
Jens
