pier-olivier.tremblay

Successfull migration of 12.9 to 17.1

Discussion created by pier-olivier.tremblay Champion on Apr 3, 2018
Latest reply on Apr 11, 2018 by camja06

Congratulations to the SSQ team remy.jobin Steeve_Brou STBO guiwguiw for the migration of this weekend.

 

We migrated :

 

Service Catalog 12.9 (Win 2008)

   -About 200 service options with several javascript and Java plugins

ServiceDesk-1 12.9 (Win 2008)

   -Complete workflows for incident, request, change and problem management

ServiceDesk-2 12.9 (Win 2008)

   -3 webengines

APM 14.1 (Win 2008)

   -Over 300 legal documents with complete financial workflows and reporting.

PAM-1 4.3.2 (Win 2008)

   -Over 500 workflows running per day. Several integrations to Exchange, PPM, CA Identity Minder, FileMaker.

PAM-2 4.3.2 (Win 2008)

PAM-3 4.3.2 (Win 2008)

EEM 12.51 (Win 2008)

Xtraction 15.1 (Win 2008)

   -Over 300 dashboards. Several scheduled tasks and integration to IP communications system.

MDB (SQL 2008)

 

To :

Service Catalog 17.1 (Win 2016)

ServiceDesk-1 17.1 (Win 2016)

ServiceDesk-2 17.1 (Win 2016)

APM 17.1 (Win 2016)

PAM-1 4.3.2 (Win 2016)

PAM-2 4.3.2 (Win 2016)

PAM-3 4.3.2 (Win 2016)

EEM 12.6.05 (Win 2016)

Xtraction 15.1 (Win 2016)

MDB (SQL 2016)

 

New environnment specs : 36 vCPU and 140 Gig of ram

 

 

 

We used the swingbox method for every product as we had to step on win2012 first due to compatibility issues.

 

 

We started the migration process at 8pm on friday. Everything was up and running saturday morning at 4am.

 

Everything went right on track. Users are using it in prod since saturday PM.

Outcomes