The meeting minutes discussed the following topics: 1. Upcoming CM-UG events in 2013 and conference call information. 2. Issues with 32-bit and 64-bit applications and how the Application Packager handles redirection between folders and registry hives. 3. How custom channels behave depending on the tuner and operating system architecture, and how to check if a custom channel contains native DLL files.

1. www.CM-UG.com
Configuration Management – User Group (formerly: Marimba Users Group)
CM-UG Meeting Minutes – March 28th 2013
Agenda:
NEW
1. Upcoming CM-UG Events
Conference Call Information
2. Issues/Concerns
All CM-UG calls unless otherwise noted will use
3. 32/64 bit meeting (March 28th) 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 March 29, 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 March 29, 2013 Chris@CM-UG.com

3. www.CM-UG.com
Configuration Management – User Group (formerly: Marimba Users Group)
32/64
32/64 bit call recording:
Webex recording: http://cm-ug.com/files/3264-3-28-2013.wrf
WebEX player: http://www.webex.com/play-webex-recording.html
© Copyright March 29, 2013 Chris@CM-UG.com

4. BBCA 8.2.02.001
32/64 bit Behavior

5. Application Packager – Redirection Behavior
 Background
 Recent changes,
– Support for 64-bit tuners
– 64-bit related changes in Application Packager
 Change of behavior in the way files are deployed to
– Registry: WoW6432Node
– Folder: System32 and Program Files
© Copyright 3/29/2013 BMC Software, Inc 5

6. Application Packager – Redirection Behavior
 Behavior with 8.2.02, while Installation – System32 vs. SysWoW64 and Registry
Pkg Version WoW6432Node Version
Pkg Arch Tuner Tuner Arch OS Arch Registry Hive System32 vs SysWOW64
Files assigned with target as $SYS.SYSTEM
8.2.02 64-bit 8.2.02 32-bit 64-bit Inside Wow6432Node gets deployed in SysWOW64
Files assigned with target as $SYS.SYSTEM
8.2.02 64-bit 8.2.02 64-bit 64-bit Bug gets deployed in System32
Files assigned with target as $SYS.SYSTEM
8.2.02 32-bit 8.2.02 32-bit 64-bit Inside Wow6432Node gets deployed in SysWOW64
Files assigned with target as $SYS.SYSTEM
8.2.02 32-bit 8.2.02 64-bit 64-bit Bug gets deployed in System32
Files assigned with target as $SYS.SYSTEM
8.2.02 64-bit pre-8.2.02 32-bit 64-bit Inside Wow6432Node gets deployed in SysWOW64
Files assigned with target as $SYS.SYSTEM
pre-8.2.02 64-bit 8.2.02 32-bit 64-bit Inside Wow6432Node gets deployed in SysWOW64
Files assigned with target as $SYS.SYSTEM
pre-8.2.02 64-bit pre-8.2.02 32-bit 64-bit Outside Wow6432Node gets deployed in SysWOW64
Files assigned with target as $SYS.SYSTEM
pre-8.2.02 64-bit 8.2.02 64-bit 64-bit Inside Wow6432Node gets deployed in System32
Files assigned with target as $SYS.SYSTEM
8.2.02 32-bit pre-8.2.02 32-bit 64-bit Inside Wow6432Node gets deployed in SysWOW64
Files assigned with target as $SYS.SYSTEM
pre-8.2.02 32-bit 8.2.02 32-bit 64-bit Inside Wow6432Node gets deployed in SysWOW64
Files assigned with target as $SYS.SYSTEM
pre-8.2.02 32-bit pre-8.2.02 32-bit 64-bit Outside Wow6432Node gets deployed in SysWOW64
Files assigned with target as $SYS.SYSTEM
pre-8.2.02 32-bit 8.2.02 64-bit 64-bit Inside Wow6432Node gets deployed in System32
© Copyright 3/29/2013 BMC Software, Inc 6

7. Application Packager – Redirection Behavior
 Behavior with 8.2.02.001 – System32 vs. SysWoW64 and Registry WoW6432Node
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 3/29/2013 BMC Software, Inc 7

8. Application Packager – Redirection Behavior
 Changes with BBCA Application Packager - 8.2.02.001
 Handle Redirection between,
– Folder : Program Files vs. Program Files(x86)
– Folder : System32 vs. SysWoW64
– Registry : Outside WoW6432Node vs. Inside WoW6432Node
© Copyright 3/29/2013 BMC Software, Inc 8

9. Application Packager – Redirection Behavior
 Redirection - Program Files vs. Program Files(x86)
 Based on the package architecture
 Will be controlled only for File Packages and Custom Packages – just a file deployment
 In case of other packages like, MSI and Shrink-wrap
– Redirection based on the application being deployed
– Application and OS decides which folder to be used for deployment
 New macro will be added - $SYS.PROGRAMFILES
– Can be used while creating File and Custom packages
– Application Packager will decide the appropriate folder to use for the macro
© Copyright 3/29/2013 BMC Software, Inc 9

10. Application Packager – Redirection Behavior
 Redirection while Packaging – System32 vs. SysWoW64 and Registry WoW6432Node
 Earlier with 32-bit tuners, on 64-bit OS
– Creating a 64-bit package to capture System32 or Registry keys, will redirect to SysWoW64 folder
and Inside WoW6432Node registry hive
– Reason: a 32-bit application runs in a 64-bit OS, OS will redirect the corresponding 32-bit location
when accessing file system
 Based on the property “package.64bit.mode” configured in Application Packager, it will
decide to package 64 bit or 32 bit packages.
 This property can be configured in “application.txt” file in Application Packager channel
directory.
– package.64bit.mode=true  64bit package in 64bit machine
– package.64bit.mode=false  32bit package in 64bit machine
© Copyright 3/29/2013 BMC Software, Inc 10

11. Application Packager – Redirection Behavior
 Redirection while Packaging – System32 vs. SysWoW64 and Registry WoW6432Node
 Earlier with 32-bit tuners, on 64-bit OS
– Creating a 64-bit package to capture System32 or Registry keys, will redirect to SysWoW64 folder
and Inside WoW6432Node registry hive
– Reason: a 32-bit application runs in a 64-bit OS, OS will redirect the corresponding 32-bit location
when accessing file system
 Based on the property “package.64bit.mode” configured in Application Packager, it will
decide to package 64 bit or 32 bit packages.
 This property can be configured in “application.txt” file in Application Packager channel
directory.
– package.64bit.mode=true  64bit package in 64bit machine
– package.64bit.mode=false  32bit package in 64bit machine
© Copyright 3/29/2013 BMC Software, Inc 11

12. Application Packager – Redirection Behavior
 Package Title – (x86) vs. (x64)
 Based on the package architecture
© Copyright 3/29/2013 BMC Software, Inc 12

13. Custom Channels Behavior with 32/64 bit
Channel Segment Tuner Version Tuner Arch OS Arch Custom channel with native DLL files. (DLL Custom channel without native DLL files
arch files arch and channel segment have same
arch)
64-bit 8.2.02 32-bit 64-bit Channel will not run as java code will try to Channel will work properly
load 64 bit DLL on 32 bit JRE
Proposed solution: Add a property which will
contain list of custom channels for which we
want to deprecate the 64-bit segment
64-bit 8.2.02 64-bit 64-bit Channel will work properly Channel will work properly
32-bit 8.2.02 32-bit 64-bit Channel will work properly Channel will work properly
32-bit 8.2.02 64-bit 64-bit Channel will not run as java code will try to Channel will work properly
load 32 bit DLL on 64 bit JRE
Proposed solution: translate this custom
channel and create 64 bit segment for the
same (Which will have 64 bit DLL’s).
32-bit 8.2.02 32-bit 32-bit Channel will work properly Channel will work properly
64-bit pre-8.2.02 32-bit 64-bit Channel will not run as java code will try to Channel will work properly
load 64 bit DLL on 32 bit JRE
Proposed solution: right now we don’t have
solution for this issue. Tuner is on older
version so we cannot alter mechanism in
tuner which will bring down the channel
(segment selection algorithm)
32-bit pre 8.2.02 32-bit 64-bit Channel will work properly Channel will work properly
32-bit pre 8.2.02 32-bit 32-bit Channel will work properly Channel will work properly
© Copyright 3/29/2013 BMC Software, Inc 13

14. How to check if your custom channel has native dll
Let us consider a custom channel – http://marge.labs.bmc.com:5282/qatools/IndexExplorer
Create a folder in filesystem, with name as <custom_channel_name>.car. In this example,
“IndexExplorer.car”
Using Channel Copier, extract the
custom channel to the folder
created above(IndexExplorer.car).
Refer figure,
In the “IndexExplorer.car” folder,
search for any dll files.
If there are any dlls found, then verify the architecture of the dll, to see if matches the tuner JRE
arch. One can use any free utility tools (like Dependency Walker) available to check the
architecture of dll
- If the dll architecture matches the JRE arch, no changes will be needed for this channel
- If the dll architecture differs from the JRE architecture, the channel’s dlls need to be translated
to the required architecture and a new segment need to be published
© Copyright 3/29/2013 BMC Software, Inc 14

15. Thank You
For any further queries or feedback, write to - Nitish_Shrivastava@bmc.com
© Copyright 3/29/2013 BMC Software, Inc 15

16. www.CM-UG.com
Configuration Management – User Group (formerly: Marimba Users Group)
BBCA Training classes
© Copyright March 29, 2013 Chris@CM-UG.com

17. 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 March 29, 2013 Chris@CM-UG.com

18. 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 March 29, 2013 Chris@CM-UG.com

19. 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 March 29, 2013 Chris@CM-UG.com

20. 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 March 29, 2013 Chris@CM-UG.com

21. 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 March 29, 2013 Chris@CM-UG.com

22. 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 March 29, 2013 Chris@CM-UG.com

23. 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 March 29, 2013 Chris@CM-UG.com