The information contained in this presentation is the confidential information of BMC, Inc. and is being provided to you with the express understanding that without the prior written consent of BMC, you may not discuss or otherwise disclose this information to any third party or otherwise make use of this information for any purpose other than for which BMC intended.
All of the future product plans and releases described herein are at the sole discretion of BMC and are subject to change and/or cancellation, and in no way should these future product plans be viewed as commitments on BMC’s part.
8.2.02.002 channels can be obtained from channel store under following category :- - Current - 8.2.02 - Current and - 8.2.02.002
List of released channels - Application Packager - Channel Manager - Infrastructure Service - Patch Manager - Patch Service - Windows Patch Source - Channel Store - Marimba Eclipse Plugin - Common Management Services - Infrastructure Administration - Report Center - Schema Manager - Transmitter
Following features are planned* - Channel store - Session Isolation - Native Command Interface - Configuration Setting Remediation - Patch Simplification - Enhancement to User Centric Deployment - Software title and license scanner - Version independent packaging
Please send email to [email protected] if you want to participate in beta
Phase 1 : To be delivered in 2 weeks from now - Project is in progress. On track so far - We are trying to optimize the way repository is built - Offers ‘sync’ capability that allow WPS to sync repo from our server (cloud).
And at any point, customer can fall back to ‘creating’ their own repository
Phase 2 : 8.3 - To use Shavlik latest SDK that offers
Latest platform coverage more stability Customization
Not everything is managed through agents. Every organization uses a ‘parallel’ method to distribute packages / binaries. These binaries (mostly MSI) go down to machines that may or may not have agent installed. This gives IT admins more flexibility on managing their heterogeneous environment. It comes with limitation though. IT admins need parallel infrastructure.
Think about a case when you can still have this ‘parallel process’ but it uses Marimba Infrastructure. Your team uses same packager to create installers. One common installer for machine with or without agent. And it uses the same infrastructure (Mirror/repeater). The download comes from the ‘right repeater’ and it uses global definition (bandwidth etc)
