We have multiple 10.2 Windchill environments (development, testing, staging) which are also clustered, some with multiple nodes.
We will compare the files being updated to make sure that we are good on our existing customizations and configurations.
We will also do some level of testing before executing the PSI on production.
1. Back up codebases on all 4 prod nodes
2. Run CPS PSI on cache master node
3. Fix permission on IE tasks (we have non default settings on some which get wiped out when running the PSI)
4. Back up modified cach master codebase
5. Move\rename pre-CPS codebases on MS nodes
6. Restore cache master codebase from step 4 on MS nodes
7. Update new MS node codebases with site.xconf from pre-CPS codebase and propagate properties
8. Fix Creo publishing configuratin on each MS node
9. Fix middleware credentials on each MS node
10. Restart and a quick technical checkout
Just focusing on these 10 steps for production it takes a good 4-5 hours.
Our management is interested in what others are doing in the area of Critical Patch Sets; how often (monthly, quarterly, etc.) and how long (in hours per environment).
Can you guys share how often and how long (please specify monolithic or clustered)?
We have two environments, production and test, and both are monolithic (with separate database servers.) Typically I will apply every CPS that comes out, so monthly. Sometimes I will apply the CPS to test first, and other times I just go straight to production (but store a snapshot of the VMs first, just in case...) I would guess that on average the whole process takes about an hour.
Like Tom I also apply every CPS, so monthly. I always apply first on a test server and then on production. I also always take zfs snapshots before applying. Takes right at an hr per environment. Our setup is monolithic with master and 3 replica servers.
Interesting discussion as we have just moved to 10.2 and are looking into our strategy with regard to this.
Our dilemma is that we obviously want to install those CPS that include security patches, however some CPS force an upgrade of the WGM for 3rd part CAD apps which means we would need to upgrade several hundred CAD machines around the group at the same time. Not something we would want to be doing on a monthly basis.
PTC Windchill Workgroup Manager for CPS is currently an optional installation in PTC Windchill 10.2 M030 CPS. This means the administrator has the option to choose whether to install PTC Windchill Workgroup Manager CPS.
• If the administrator chooses not to install 10.2 M030 PTC Windchill Workgroup Manager CPS and goes ahead with only PTC Windchill 10.2 M030 CPS, then there is no requirement to reinstall PTC Windchill Workgroup Manager on all client systems; however, the administrator would not receive any of the PTC Windchill Workgroup Manager fixes that were provided in PTC Windchill Workgroup Manager CPS.
• If the administrator chooses to install PTC Windchill Workgroup Manager CPS, then reinstallation of PTC Windchill Workgroup Manager on all client systems is mandatory.
• The administrator can also update the server installation later, if PTC Windchill Workgroup Manager CPS is required.
Product Manager - PTC
We were under the impression that the CPS WGM upgrade was not always optional - ie on occasion the CPS may insist that the WGM is updated - is this not the case?
PTC has kept the option to impose mandatory WGM update ONLY in the case where there would be dependency on server side for WGM. We understand the efforts required for re-installation of WGM on all end users system, if we impose this restriction. Hence, we sincerely try to avoid such situations. So, we cannot provide a generic statement of all future WGM CPS will be optional in 10.2 M030.
In 10.2 M030, we are at 10.2 M030 CPS13 that is being qualified, but there is no restriction until now for mandatory update of WGM along with Windchill CPS update.
Please let me know, if any further clarifications on WWGM-CPS is required.
Product Manager - PTC
We talked about this at the TCs in January some. One admin told me that it didn't take him all weekend to install the patch, only 7 to 8 hours.
We are still doing practice migrations, so no data to destroy yet. Just running the PSI has taken between 1 and 4 hours. Hopefully that will converge with experience. Add on taking backups, testing and restoring or deleting the backed up data, and I would expect to need about 4 to 6 hours per CPS.
Thank you for your input. Are you running a monolithic or clustered environment?
A monolithic environment with multiple remote file servers.