March 2013 (BMC: 32/64 bit channel discussion)

Configuration Management – User Group (formerly: Marimba Users Group)

www.CM-UG.com

© Copyright March 29, 2013 [email protected]

CM-UG Meeting Minutes – March 28th 2013

NEW

Conference Call Information

All CM-UG calls unless otherwise noted will use

the following dial in information:

US Conferencing Number: 1-855-747-8824

NEW CODE: 239 – 774 – 3116 Toll: 1-719-325-2630

India: 000 800 100 7687

Germany: 0800 588 9225

Agenda:

1. Upcoming CM-UG Events

2. Issues/Concerns

3. 32/64 bit meeting (March 28th)

4. Marimba roadmap

5. BBCA Training classes

6. User Interaction

7. ADDM Users?

http://www.linkedin.com/groups?gid=1774296


www.CM-UG.com


Upcoming CM-UG 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

Upcoming 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

http://calendar.cm-ug.com/





www.CM-UG.com

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

http://cm-ug.com/files/3264-3-28-2013.wrf










http://www.webex.com/play-webex-recording.html





32/64 bit Behavior

BBCA 8.2.02.001

© Copyright 3/29/2013 BMC Software, Inc 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



Behavior with 8.2.02, while Installation – System32 vs. SysWoW64 and Registry WoW6432Node

Pkg Version Pkg Arch Tuner Version Tuner Arch OS Arch Registry Hive System32 vs SysWOW64

8.2.02 64-bit 8.2.02 32-bit 64-bit Inside Wow6432Node Files assigned with target as $SYS.SYSTEM gets deployed in SysWOW64

8.2.02 64-bit 8.2.02 64-bit 64-bit Bug Files assigned with target as $SYS.SYSTEM gets deployed in System32

8.2.02 32-bit 8.2.02 32-bit 64-bit Inside Wow6432Node Files assigned with target as $SYS.SYSTEM gets deployed in SysWOW64

8.2.02 32-bit 8.2.02 64-bit 64-bit Bug Files assigned with target as $SYS.SYSTEM gets deployed in System32

8.2.02 64-bit pre-8.2.02 32-bit 64-bit Inside Wow6432Node Files assigned with target as $SYS.SYSTEM gets deployed in SysWOW64

pre-8.2.02 64-bit 8.2.02 32-bit 64-bit Inside Wow6432Node Files assigned with target as $SYS.SYSTEM gets deployed in SysWOW64

pre-8.2.02 64-bit pre-8.2.02 32-bit 64-bit Outside Wow6432Node Files assigned with target as $SYS.SYSTEM gets deployed in SysWOW64

pre-8.2.02 64-bit 8.2.02 64-bit 64-bit Inside Wow6432Node Files assigned with target as $SYS.SYSTEM gets deployed in System32

8.2.02 32-bit pre-8.2.02 32-bit 64-bit Inside Wow6432Node Files assigned with target as $SYS.SYSTEM gets deployed in SysWOW64

pre-8.2.02 32-bit 8.2.02 32-bit 64-bit Inside Wow6432Node Files assigned with target as $SYS.SYSTEM gets deployed in SysWOW64

pre-8.2.02 32-bit pre-8.2.02 32-bit 64-bit Outside Wow6432Node Files assigned with target as $SYS.SYSTEM gets deployed in SysWOW64

pre-8.2.02 32-bit 8.2.02 64-bit 64-bit Inside Wow6432Node Files assigned with target as $SYS.SYSTEM gets deployed in System32



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

8.2.02.001 64-bit 8.2.02.001 32-bit 64-bit Outside Wow6432Node Files assigned with target as $SYS.SYSTEM gets deployed in System32

8.2.02.001 64-bit 8.2.02.001 64-bit 64-bit Outside Wow6432Node Files assigned with target as $SYS.SYSTEM gets deployed in System32

8.2.02.001 32-bit 8.2.02.001 32-bit 64-bit Inside Wow6432Node Files assigned with target as $SYS.SYSTEM gets deployed in SysWOW64

8.2.02.001 32-bit 8.2.02.001 64-bit 64-bit Inside Wow6432Node Files assigned with target as $SYS.SYSTEM gets deployed in SysWOW64

8.2.02.001 64-bit old tuners 32-bit 64-bit Outside Wow6432Node Files assigned with target as $SYS.SYSTEM gets deployed in System32

older packages 64-bit 8.2.02.001 32-bit 64-bit Outside Wow6432Node Files assigned with target as $SYS.SYSTEM gets deployed in System32

older packages 64-bit old tuners 32-bit 64-bit Outside Wow6432Node Files assigned with target as $SYS.SYSTEM gets deployed in System32

older packages 64-bit 8.2.02.001 64-bit 64-bit Outside Wow6432Node Files assigned with target as $SYS.SYSTEM gets deployed in System32

8.2.02.001 32-bit old tuners 32-bit 64-bit Inside Wow6432Node Files assigned with target as $SYS.SYSTEM gets deployed in SysWOW64

older packages 32-bit 8.2.02.001 32-bit 64-bit Inside Wow6432Node Files assigned with target as $SYS.SYSTEM gets deployed in SysWOW64

older packages 32-bit old tuners 32-bit 64-bit Inside Wow6432Node Files assigned with target as $SYS.SYSTEM gets deployed in SysWOW64

older packages 32-bit 8.2.02.001 64-bit 64-bit Inside Wow6432Node Files assigned with target as $SYS.SYSTEM gets deployed in SysWOW64



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



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



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



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



Package Title – (x86) vs. (x64)

Based on the package architecture


Custom Channels Behavior with 32/64 bit

Channel Segment arch

Tuner Version Tuner Arch OS Arch Custom channel with native DLL files. (DLL files arch and channel segment have same

arch)

Custom channel without native DLL files

64-bit 8.2.02 32-bit 64-bit Channel will not run as java code will try to 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

Channel will work properly

64-bit 8.2.02 64-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 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).



64-bit pre-8.2.02 32-bit 64-bit Channel will not run as java code will try to 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


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

http://marge.labs.bmc.com:5282/qatools/IndexExplorer

http://marge.labs.bmc.com:5282/qatools/IndexExplorer


Thank You For any further queries or feedback, write to - [email protected]

mailto:[email protected]


www.CM-UG.com

BBCA Training classes


http://e2.ma/click/b5twb/rd70vb/7hp6s


www.CM-UG.com

CM-UG – Mailing List

› User Email Group:

– Sign up for the group email and subgroup emails here: http://Subscribe.CM-UG.com


http://subscribe.cm-ug.com/




www.CM-UG.com

CM-UG - User Interaction

Join the LinkedIn Group = http://www.linkedin.com/groups?gid=1774296





www.CM-UG.com

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


https://communities.bmc.com/communities/community/bmcdn/bmc_service_automation/client_configuration_automation?view=discussions

https://communities.bmc.com/communities/community/bmcdn/bmc_service_automation/client_configuration_automation?view=discussions


www.CM-UG.com

Marimba Jobs

›Jobs.CM-UG.com

›Look for CM related positions

›Post Req’s for CM related positions


I know of a few app package jobs right now

Message Me

http://jobs.cm-ug.com/




http://www.linkedin.com/in/chrisarmstrongtx

http://www.linkedin.com/in/chrisarmstrongtx


www.CM-UG.com

Suggest a topic:

If you have a topic you

would like to discuss as a

monthly feature please

send an email to

[email protected]

Potential Meeting Topics/Demos

Open to presentations from CM-UG Members and Vendors.

Upcoming CM-UG Events

– Member Presentations:

– Stopping channel shopping (Josh L)

– Custom inventory scanning (Jason M)

– Custom Reporting interfaces

– Custom ARS interfaces

– Vendor Presentations:

– Marimba 8.2 Roadmap (BMC)

– AdminStudio Info (Flexera)

– Marimba/Matrix42 VDI Solutions

– BMC Product Roadmaps





http://www.cm-ug.com/files/4-20-2011_CM-UG_Minutes.pdf



http://www.cm-ug.com/files/ds_AS10_5-18-2010.pdf






www.CM-UG.com

BMC Consulting

Consulting.CM-UG.com Find the best consultants for your next BMC project.


http://consulting.cm-ug.com/





www.CM-UG.com

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.


http://addm.cm-ug.com/





Technology

March 2013 (BMC: 32/64 bit channel discussion)