Page 1 of 1

TM1 SSL update for client- best wayout

Posted: Tue Oct 11, 2016 11:45 am
by zodiacviv
Hi Everyone,

As we know IBM has given Updater Kit for TM1, we have already applied updates on TM1 server as well as client side (TM1 Architect and Perspecvtive) and we see this work after moving clock after 24th Nov 2016.

So, now just curious to know from everyone, what would be best approach to apply updater for all users who are using TM1 clients given that most of them are purely from business and don't know where is default TM1 client installation folder and there is chance they might mess up things. We are thinking to create an automated script which would take care of everything from start till end and users just have to run that script with admin right. Any kind of suggestion is welcomed. :)

Viv

Re: TM1 SSL update for client- best wayout

Posted: Tue Oct 11, 2016 12:14 pm
by jim wood
How did you deploy the software to start with? Do you have a package deployment system? The best person to ask is your IT department for me.

Re: TM1 SSL update for client- best wayout

Posted: Tue Oct 11, 2016 1:10 pm
by zodiacviv
Hi Jim,

I have admin rights on servers where TM1 instances are hosted. For test purpose, I did apply Server side updater on Test server and also for client, I applied updater on my desktop where I have TM1 architect and Tm1 Perspective installed. And both updates worked fine.

For any software changes or installation, we have IT team and they generally take care of it. But, here as update is restricted to few TM1 users, going to IT doesn't seems to be the first option as they generally takes a lot of time for any new installation (and also given that they seek a lot of approvals first)and this is certian that they won't be accomplishing this before 24th Nov.

Re: TM1 SSL update for client- best wayout

Posted: Fri Oct 14, 2016 4:36 pm
by Jefflinde
Do you mind me asking what "option" you chose? I have been testing the V2 option and so far it seems to be the simplest. it has minimal impact for our perspective users but i have not tested our contributor logins yet.

Do you have any experience with how contributor behaves with the update?

Cheers.