April 2013 (BMC: 8.2.02 Upgrade path details)
0 likes740 views
The document discusses notes from a Configuration Management – User Group meeting on April 10th, 2013. The agenda items included upcoming CM-UG events, issues/concerns with an 8.2.02 upgrade, Marimba roadmap, training classes, and questions from ADDM users. Details were provided on the 8.2.02 upgrade process and potential issues. A workaround was presented using a custom "TunerUpgrader" channel to avoid a two-step upgrade for endpoints. Proper upgrade steps were outlined depending on the current infrastructure service version.
April 2013 (BMC: 8.2.02 Upgrade path details)
- 1. www.CM-UG.com Configuration Management – User Group (formerly: Marimba Users Group) CM-UG Meeting Minutes – April 10th 2013 Agenda: NEW 1. Upcoming CM-UG Events Conference Call Information 2. Issues/Concerns All CM-UG calls unless otherwise noted will use 3. 8.2.02 Upgrade Meeting Notes the following dial in information: 4. Marimba roadmap US Conferencing Number: 1-855-747-8824 5. BBCA Training classes NEW CODE: 239 – 774 – 3116 6. User Interaction Toll: 1-719-325-2630 7. ADDM Users? India: 000 800 100 7687 Germany: 0800 588 9225 © Copyright April 10, 2013 Chris@CM-UG.com
- 2. www.CM-UG.com Configuration Management – User Group (formerly: Marimba Users Group) Upcoming CM-UG Events Reminder: The CM-UG call is normally the 3rd Wednesday of each month at 12 noon central time. The CM-UG calendar is also located here > http://calendar.cm-ug.com Upcoming Events 2013 CM-UG meeting dates: Wednesday, April 24th, 2013 @ noon Central time – 4th Wednesday Wednesday, May 15th, 2013 @ noon Central time Wednesday, June 19th, 2013 @ noon Central time Wednesday, July 17th, 2013 @ noon Central time Wednesday, August 21st, 2013 @ noon Central time Wednesday, September 18th, 2013 @ noon Central time Wednesday, October 16th, 2013 @ noon Central time Wednesday, November 20th, 2013 @ noon Central time Wednesday, December 18th, 2013 @ noon Central time © Copyright April 10, 2013 Chris@CM-UG.com
- 3. www.CM-UG.com Configuration Management – User Group (formerly: Marimba Users Group) 8.2.02.001 8.2.02.001 Tech Bulletin: • Important upgrade notes • Many RFE’s and defects addressed http://cm-ug.com/files/mrbTB8202001.pdf © Copyright April 10, 2013 Chris@CM-UG.com
- 4. BBCA 8.2.02 – Upgrade Steps
- 5. Index Why 8.2.02 upgrade is different What are potential risks (to upgrade without following the steps) What is the solution Upgrade Steps Potential issues with the solution Workaround Summary In context to our last meeting on ‘32/64 bit package behavior’ © Copyright 4/10/2013 BMC Software, Inc 5
- 6. Index Why 8.2.02 upgrade is different What are potential risks (to upgrade without following the steps) What is the solution Upgrade Steps Potential issues with the solution Workaround Summary In context to our last meeting on ‘32/64 bit package behavior’ © Copyright 4/10/2013 BMC Software, Inc 6
- 7. 8.2.02 Comes with two segments for some channels… A new segment for Windows x64 platform is introduced into 8.2.02 for following channels : Application packager Inventory service Patch service Policy service Deployment service Content Replicator` Infrastructure Service Windows x86 segment is targeted for the Endpoint, CMS, Proxy profile Windows x64 segment is targeted for master, mirror, repeater © Copyright 4/10/2013 BMC Software, Inc 7
- 8. Index Why 8.2.02 upgrade is different What are potential risks (to upgrade without following the steps) What is the solution Upgrade Steps Potential issues with the solution Workaround Summary In context to our last meeting on ‘32/64 bit package behavior’ © Copyright 4/10/2013 BMC Software, Inc 8
- 9. Potential Issues… 1. If tuner is updated first - Tuner will get upgraded to 64 bit segment for all profiles - We only support 64 bit segment for Transmitters (master, mirror and repeater) 2. If Channels are updated before tuner - On 64 bit machine, the tuner will get 64 bit channels - But the tuner (pre 8202) is a 32 bit tuner only - Things will fail because 32 bit tuner attempts to start a 64 bit channel © Copyright 4/10/2013 BMC Software, Inc 9
- 10. Index Why 8.2.02 upgrade is different What are potential risks (to upgrade without following the steps) What is the solution Upgrade Steps Potential issues with the solution Workaround Summary In context to our last meeting on ‘32/64 bit package behavior’ © Copyright 4/10/2013 BMC Software, Inc 10
- 11. Solution added in most recent patches for every release Solution for this is added in Infrastructure Service (i.e. Tuner) We added required change in most recent release on every supported version. i.e. 8.1.01.009f 8.2.00.006 8.2.01.002 Technical Details A new property ‘marimba.tuner.depricate64bitsegment’ is introduced, by using this property you can toggle between a 64-bit and 32-bit segments – If the value is true, the tuner brings x86(32-bit) segments from the transmitter. – If the value is false, the tuner brings x64(64-bit) segments from the transmitter. This property will help users to get the appropriate segments on the tuner. We will set it to ‘false’ on the server profiles, it will be true by default. © Copyright 4/10/2013 BMC Software, Inc 11
- 12. Index Why 8.2.02 upgrade is different What are potential risks (to upgrade without following the steps) What is the solution Upgrade Steps Potential issues with the solution Workaround Summary In context to our last meeting on ‘32/64 bit package behavior’ © Copyright 4/10/2013 BMC Software, Inc 12
- 13. 8.2.02 Upgrade Steps ONE STEP PROCESS - If your Infrastructure Service is on one of the following versions 8.1.01.009f 8.2.00.006 8.2.01.002 Set the property marimba.tuner.depricate64bitsegment to false on the Server Tuners (Master, Mirror and Repeater). You can set the property through Policy or Profile Update. Update the 8.2.02 infrastructure service and start it. The tuner starts in the 64-bit mode. TWO STEP PROCESS – If your Infrastructure Service is not on the above mentioned release then you need to follow 2 step process 1. Upgrade Infrastructure Service to above mentioned release and 2. Then upgrade to 8.2.02 © Copyright 4/10/2013 BMC Software, Inc 13
- 14. Index Why 8.2.02 upgrade is different What are potential risks (to upgrade without following the steps) What is the solution Upgrade Steps Potential issues with the solution Workaround Summary In context to our last meeting on ‘32/64 bit package behavior’ © Copyright 4/10/2013 BMC Software, Inc 14
- 15. Reported issues with 2 step upgrade process Infrastructure Service upgrade for server machines is not that big issue But upgrading it on endpoint takes longer. The intermediate rollout itself would take longer And so the final rollout would be delayed further © Copyright 4/10/2013 BMC Software, Inc 15
- 16. Index Why 8.2.02 upgrade is different What are potential risks (to upgrade without following the steps) What is the solution Upgrade Steps Potential issues with the solution Workaround Summary In context to our last meeting on ‘32/64 bit package behavior’ © Copyright 4/10/2013 BMC Software, Inc 16
- 17. WORKAROUND Custom channel ‘TunerUpgrader’: workaround in place of “two step” upgrade (no intermediate upgrade required) ‘TunerUpgrader’ should be used only on the Client, CMS, Proxy profiles running on 64-bit Windows OS. There will be 3 versions of this channel, one for each “current” customer version 1. For 8.1.01.X 2. For 8.2.00.X 3. For 8.2.01.X Prerequisite: - Admins need to publish 8.2.02 Infrastructure Service on the transmitters first. - This channel needs to run before the next Infrastructure Service update kicks off (i.e. before schedule kicks in). Steps to use this channel: - Admins need to publish 8.2.02 Infrastructure Service on the transmitters first - Admin will then deploy and start this channel - Once this channel is started, it will update Infrastructure Service automatically to the 8.2.02 release © Copyright 4/10/2013 BMC Software, Inc 17
- 18. WORKAROUND How this channel will work? Channel contains “specific” tuner binaries (tuner.zip and marimba.zip) which “support” depricate out of the box On channel start, it automatically configures tuner to replace the existing binaries with the channel files whenever the next tuner restart occurs (only happens once, behaviour controlled by a channel property ‘customupgrader.switchedbinaries’) Next, the channel restarts the tuner, which “applies” the tuner binaries correctly; tuner restarts in a position to “upgrade” subsequently to 8.2.02 32-bit version On tuner restart, channel starts again, locates Infrastructure Service on the tuner and starts it (behaviour controlled by a channel property ‘customupgrader.switchedbinaries’). Result: Infrastructure Service x86 segment is brought down by tuner on the Client, CMS, Proxy profile Subsequent starts of TunerUpgrader does nothing, thus avoiding re-execution of above use case (behaviour controlled by a channel property ‘customupgrader.upgradedonce’) © Copyright 4/10/2013 BMC Software, Inc 18
- 19. WORKAROUND Upgrade on Master /Mirror / Repeater tuner: We should not use ‘TunerUpgrader’ on Master /Mirror / Repeater tuners. On these profiles set the property marimba.tuner.depricate64bitsegment to false through Policy or Profile Update and start infrastructure service from old release to 8.2.02. Tuner will upgrade to 64- bit. Note: ‘TunerUpgrader’ should be used only on the Client, CMS, Proxy profile running on 64-bit Windows OS. © Copyright 4/10/2013 BMC Software, Inc 19
- 20. Index Why 8.2.02 upgrade is different What are potential risks (to upgrade without following the steps) What is the solution Upgrade Steps Potential issues with the solution Workaround Summary In context to our last meeting on ‘32/64 bit package behavior’ © Copyright 4/10/2013 BMC Software, Inc 20
- 21. Summary If your Infrastructure Service is on one of the following versions 8.1.01.009f 8.2.00.006 8.2.01.002 Set the property marimba.tuner.depricate64bitsegment to false on the Server Tuners (Master, Mirror and Repeater). You can set the property through Policy or Profile Update. Update the 8.2.02 infrastructure service and start it. The tuner starts in the 64-bit mode. If your Infrastructure Service is not on the above mentioned release then you can use BBCA ‘TunerUpgrader’ channel (in the order mentioned in this presentation) and go to 8.2.02 directly If two-step endpoint upgrade is not an issue, you can go to above mentioned versions and then upgrade to 8.2.02 © Copyright 4/10/2013 BMC Software, Inc 21
- 22. Index Why 8.2.02 upgrade is different What are potential risks (to upgrade without following the steps) What is the solution Upgrade Steps Potential issues with the solution Workaround Summary In context to our last meeting on ‘32/64 bit package behavior’ © Copyright 4/10/2013 BMC Software, Inc 22
- 23. Application Packager – Redirection Behavior : Proposed behavior in 8.2.02.001 Pkg Version Pkg Arch Tuner Version Tuner Arch OS Arch Registry Hive System32 vs SysWOW64 Files assigned with target as $SYS.SYSTEM 8.2.02.001 64-bit 8.2.02.001 32-bit 64-bit Outside Wow6432Node gets deployed in System32 Files assigned with target as $SYS.SYSTEM 8.2.02.001 64-bit 8.2.02.001 64-bit 64-bit Outside Wow6432Node gets deployed in System32 Files assigned with target as $SYS.SYSTEM 8.2.02.001 32-bit 8.2.02.001 32-bit 64-bit Inside Wow6432Node gets deployed in SysWOW64 Files assigned with target as $SYS.SYSTEM 8.2.02.001 32-bit 8.2.02.001 64-bit 64-bit Inside Wow6432Node gets deployed in SysWOW64 Files assigned with target as $SYS.SYSTEM 8.2.02.001 64-bit old tuners 32-bit 64-bit Outside Wow6432Node gets deployed in System32 Files assigned with target as $SYS.SYSTEM older packages 64-bit 8.2.02.001 32-bit 64-bit Outside Wow6432Node gets deployed in System32 Files assigned with target as $SYS.SYSTEM older packages 64-bit old tuners 32-bit 64-bit Outside Wow6432Node gets deployed in System32 Files assigned with target as $SYS.SYSTEM older packages 64-bit 8.2.02.001 64-bit 64-bit Outside Wow6432Node gets deployed in System32 Files assigned with target as $SYS.SYSTEM 8.2.02.001 32-bit old tuners 32-bit 64-bit Inside Wow6432Node gets deployed in SysWOW64 Files assigned with target as $SYS.SYSTEM older packages 32-bit 8.2.02.001 32-bit 64-bit Inside Wow6432Node gets deployed in SysWOW64 Files assigned with target as $SYS.SYSTEM older packages 32-bit old tuners 32-bit 64-bit Inside Wow6432Node gets deployed in SysWOW64 Files assigned with target as $SYS.SYSTEM older packages 32-bit 8.2.02.001 64-bit 64-bit Inside Wow6432Node gets deployed in SysWOW64 © Copyright 4/10/2013 BMC Software, Inc 23
- 24. Application Packager – Redirection Behavior : Limitations and Known Issues Limitations SW00450179: Redirection from SysWow64 to System 32 folder fails in Windows 8 and Windows 2012 – The Microsoft API used for redirection is supported only on specific technologies on Windows 8 and Windows Server 2012 – Ref: http://msdn.microsoft.com/enus/library/windows/desktop/aa365743(v=vs.85).aspx – So, the redirection does not work in these cases. SW00450180: 32-bit packages fail to install Registry Keys on 64-bit OS – This is due to a bug in Microsoft API used in Application Packager – Ref: http://microsoft.public.platformsdk.security.narkive.com/B7kbfiy3/se-registry-wow64-64key – Workaround: Packages can be created with 64-bit architecture and the same can be to perform registry operation Known Issues Packages created/repackaged with Application Packager versions 8.1.01.009d, 8.2.00.006 and 8.2.01.002, will fail on 8.2.02 and above versions on 64-bit tuners Workaround: Before the packages are deployed, it is required to repackage these packages using Application Packager 8.2.02.001 © Copyright 4/10/2013 BMC Software, Inc 24
- 25. Questions ??? Nitish_Shrivastava@bmc.com © Copyright 4/10/2013 BMC Software, Inc 25
- 26. www.CM-UG.com Configuration Management – User Group (formerly: Marimba Users Group) BBCA Training classes © Copyright April 10, 2013 Chris@CM-UG.com
- 27. www.CM-UG.com Configuration Management – User Group (formerly: Marimba Users Group) CM-UG – Mailing List › User Email Group: – Sign up for the group email and subgroup emails here: http://Subscribe.CM-UG.com © Copyright April 10, 2013 Chris@CM-UG.com
- 28. www.CM-UG.com Configuration Management – User Group (formerly: Marimba Users Group) CM-UG - User Interaction Join the LinkedIn Group = http://www.linkedin.com/groups?gid=1774296 © Copyright April 10, 2013 Chris@CM-UG.com
- 29. www.CM-UG.com Configuration Management – User Group (formerly: Marimba Users Group) CM-UG - User Interaction › BMC Developer Network Please register an account on the new BMC developer network. These forums are very nice and provide a single place now for all BMC products. BBCA Forums © Copyright April 10, 2013 Chris@CM-UG.com
- 30. www.CM-UG.com Configuration Management – User Group (formerly: Marimba Users Group) Marimba Jobs ›Jobs.CM-UG.com I know of a few app package jobs right now Message Me ›Look for CM related positions ›Post Req’s for CM related positions © Copyright April 10, 2013 Chris@CM-UG.com
- 31. www.CM-UG.com Configuration Management – User Group (formerly: Marimba Users Group) Upcoming CM-UG Events Potential Meeting Topics/Demos Open to presentations from CM-UG Members and Vendors. – Member Presentations: – Stopping channel shopping (Josh L) Suggest a topic: – Custom inventory scanning (Jason M) – Custom Reporting interfaces – Custom ARS interfaces If you have a topic you would like to discuss as a – Vendor Presentations: monthly feature please – Marimba 8.2 Roadmap (BMC) – AdminStudio Info (Flexera) send an email to – Marimba/Matrix42 VDI Solutions Chris@CM-UG.com – BMC Product Roadmaps © Copyright April 10, 2013 Chris@CM-UG.com
- 32. www.CM-UG.com Configuration Management – User Group (formerly: Marimba Users Group) BMC Consulting Consulting.CM-UG.com Find the best consultants for your next BMC project. © Copyright April 10, 2013 Chris@CM-UG.com
- 33. www.CM-UG.com Configuration Management – User Group (formerly: Marimba Users Group) BMC ADDM Users group If you are actively using or just interested in BMC ADDM please join the ADDM UG http://addm.cm-ug.com Meets 3rd Weds of each month at 11:00 AM Central. © Copyright April 10, 2013 Chris@CM-UG.com