Re: ISP 81 Discontinued functions

Is there any list of discontinued functions for the server? I found that list only for the client... For us, a real show-stopper is the discontinued support for Windows 7. This OS is still widely used here, and we don't officially support newer versions of Windows for the client for privacy reason

Re: Reg: tsm ba client autodeploy package 7.1.4.1

Hi Andy, > We have just published this technote that describes the policy for > automatic deployment packages: > > http://www.ibm.com/support/docview.wss?uid=swg21983614 thanks for the link. So when will an autodeployment package be available that addresses e.g. CVE 2016-0201 (http://www-01.ibm

Re: Reg: tsm ba client autodeploy package 7.1.4.1

Hi Neil, hi all (especially TSM dev), I got a similar statement today from IBM support. There is no official communication for that, but support says that one reason is that they intend to publish client fixpacks about every three months in the future. So first, why is there no official statemen

Re: Antwort: ADSM-L Digest - 21 Mar 2016 to 22 Mar 2016 (#2016-56)

Hi Markus, I missed a bit that you try only client to server at the moment. This is pretty straightforward. Here's a snippet from the dsmserv.opt of our 7.1.4 server: TCPPort 1500 SSLTCPPORT 1502 TCPADMINPort 1501 SSLTCPADMINPort 1503 SSLTLS12 YES ADMINONCLIENTPORT NO The dsm.sys for the c

Re: SSL 256 on Server version 7.1.4.100

OMMUNICATION FAILS > USING CA-SIGNED CERTIFICATES is fixed in TSM server 7.1.5.0. > > David > > -Original Message- > From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of > Bjoern Rackoll > Sent: Tuesday, March 22, 2016 10:10 AM > To: ADSM-L@VM.

Re: SSL 256 on Server version 7.1.4.100

Hi Markus, > has anyone been able to use ssl with the cert256.arm? The ssl connection > using cert.arm runs fine, but we would like to move on to the cert256.arm. > We tried it on a Solaris10 server with ISP 7.1.4.100 and on a Windows 2012 > Server with ISP 7.1.4.0, but have not been able to conne

Re: Fix for privilege escalation bug

Hi Thomas! > We have a considerable number of Linux TSM clients running on 32 bit > x86 processors and currently using either 6.2.2.0 or 6.2.4.0 client > code. These client code levels have the privilege escalation bug > described in the IBM bulletin " Tivoli Storage Manager Stack-based > Buffer O

Re: AIX Upgrade TSM V6.3.4.0 to V7.1.1.0 issue

your instances manually if you can't get the installation manager working at this point (you have to tell the installation manager to skip the instance): http://pic.dhe.ibm.com/infocenter/tsminfo/v7r1/topic/com.ibm.itsm.tshoot.doc/t_pdg_manupgrade.html Regards, -- Bjoern Rackoll University of

Re: ANS9180W during client backup

JFTR: In the meantime I managed to get the backup on this client working. It it just a workaround, and that workaround is not very nice. Unfortunately I can't share the details on this list, but anybody interested can contact me by PM. Regards, -- Bjoern Rackoll University of Hamburg Regio

Re: ANS9180W during client backup

Hi Michael, > did you set "passwordaccess generate" in the dsm.sys file of that client? yes, I did. We do that by default, but I just checked it to be sure. Regards, -- Bjoern Rackoll University of Hamburg Regionales Rechenzentrum Zentrale Dienste Schlueterstr. 70 D-20146 H

ANS9180W during client backup

error and disabling the daily mails about a failed backup? Unfortunately, reinstalling the client with another OS isn't possible, either. Regards, -- Bjoern Rackoll University of Hamburg Regionales Rechenzentrum Zentrale Dienste Schlueterstr. 70 D-20146 Hamburg E-Mail: backup.rack...@rrz.uni-hamburg.de

Re: TDP Exchange indiviual mailbox restore failure

with some third-party tool), we have to look for a completely different backup solution for Exchange. Regards, -- Bjoern Rackoll University of Hamburg Regionales Rechenzentrum Zentrale Dienste Schlueterstr. 70 D-20146 Hamburg Tel.: +49 (0)40 42838 - 63 11 Fax: +49 (0)40 42838 - 62 70 Mobil: +49 (0)172 427 0301 E-Mail: bac...@rrz.uni-hamburg.de

Re: SV: TDP Exchange indiviual mailbox restore failure

Hi Christian, Have you installed the MS Exchange MAPI Client? http://www.microsoft.com/downloads/en/details.aspx?FamilyID=e17e7f31-079a-43a9-bff2-0a110307611e&displaylang=en yes, the MAPI Client is installed on the MS Exchange mailbox server. Regards, -- Björn Rackoll Universität Hamburg Re

TDP Exchange indiviual mailbox restore failure

clients from talking directly to the mailbox server). Has anyone seen the same problem, and if yes, how did you deal with it? OS: Windows 2008 Server R2, 64bit B/A-Client: 6.2.1.3 TDP Exchange: 6.1.2.1 TSM Server: 5.5.4.0 on AIX Regards, -- Bjoern Rackoll University of Hamburg Regionales

Re: Unicode on UNIX

I'd like to hear from anyone who was able make it work and survive reboots. LC_CTYPE=en_US LANG=en_US nohup /usr/bin/dsmc sched in a startup script should do the trick. At least it does here. :-) I'm wondering where do you place this line in SLES? In RHEL there is /etc/rc.local which starts la

Re: Unicode on UNIX

>>> For my users with Unicode files on UNIX clients, I recommend this be added >>> to the startup scripts for the scheduler or CAD: >>> >>> LANG=en_US >>> >>> LC_ALL=en_US >>> >>> export LANG >>> >>> export LC_ALL > > My observations indicate that this will work as long as you issue > these comma

Re: Unicode on UNIX

Hi Fred, For my users with Unicode files on UNIX clients, I recommend this be added to the startup scripts for the scheduler or CAD: LANG=en_US LC_ALL=en_US export LANG export LC_ALL However, a user running CentOS thinks that en_US does not exist in that flavor of LINUX, so he misses 10