This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Configuration Management – User Group (formerly: Marimba Users Group)
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
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.
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
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
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’)
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
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
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