Towards a Unified View of IT Infrastructure | The Official Device42 Blog
  + 
    - 
* Partners
* Resources
  + Tools / Utilities
Search for:
# Deeper Cloud Metadata, Bitlocker Discovery, and JAMF Integration v19.02 MA
! 
!
Release Date: August 1, 2024
## The 19.02 MA release contains the following main features:
#### Autodiscovery type for JAMF discovery
Previous Device42 MA versions integrated with JAMF using an add-on script. In the 19.02 release, this functionality is now part of native Device42 Discovery as a new cloud discovery type. Users can create and manage JAMF Cloud Discovery jobs without additional integration or configuration.
#### AWS scans retrieval of Vendor Metadata
Administrators can now read and store AWS metadata tags as Device42 Tags. When configuring the Cloud Discovery Job, set the option ‘Add vendor metadata as:’ to ‘Tags.’ The metadata will be stored in Device42 in key/value pairs and can be displayed alongside other Custom Fields.
#### Google Cloud Discovery can now store vendor metadata within Labels or Custom Metadata
Similar to AWS tags, Google Cloud Administrators use labels for tracking cloud resource details. In the 19.02 release, users can choose to retrieve values from Custom Metadata or the default label using the ‘Source Device Vendor Metadata From:’ setting.
#### Bitlocker Discovery
WDS/WinRM discovery now highlights mountpoint properties for Protection Status, Conversion Status, Encryption Method, and Persistent Volume ID, providing valuable insights for security and operations.
## Additional Features of 19.02 MA
#### RU Sampling standardized to allow for a 5 minute interval.
Similar to Hypervisor/\*nix periodic jobs, all periodic discoveries can now be set to a 5-minute sampling interval. Previous SNMP and Storage jobs with polling intervals of 15 seconds, 30 seconds, or 1 minute will be updated to the new 5-minute interval upon upgrade.
#### Standard guided report for Lifecycle Events
The standard guided report for Lifecycle Events now includes columns and filters for Device and end-user data fields.
#### Global search can now be performed on Tags associated with SSL Certificates.
Users can now perform global searches using tags associated with SSL Certificates. This feature streamlines searches with specific tags, particularly useful for managing SSL certificates.
#### Expanded Executive Summary Dashboard
The Insights+ Executive Summary Dashboard provides enhanced information on cloud resources, storage metrics, and mobile devices. Look for details about Storage Arrays by Vendor, Cloud Instances, OS type analysis for desktops, and mobile information.
#### Ability to ignore logical ports with SNMP jobs
The SNMP discovery job can now exclude logical ports. In previous versions of Device42, both logical and physical ports were displayed in the Connectivity view, which could be confusing. Use the “Discovered port types to ignore” option to exclude logical ports.
#### Ability to discover and determine the primary **interface**for a device with multiple interfaces
Windows devices often have multiple IP interfaces. Now, Device42 can identify the primary interface for a device. Look for the “Is Default” field, marked with either a green checkmark or a negative red x symbol.
#### Last login retrieval for Linux full characters
Linux discovery can populate the last login username upon discovery. However, this username is truncated to the first 8 characters. With the 19.02 release, the system will utilize the lastlog command, which can return usernames greater than 8 characters.
## Bug Fixes and other minor changes
* When performing both a cloud and OS discovery, the virtual subtype can be changed by a second WMI discovery.
* Remote collector services now run under less privileged user space.
* Collapse the internal refinement as DoQL AI builds the query.
* (Alert email message generated from Insights+ text changed from “Report” to “Alert”
* Discovery Scores dashboard altered to show Discovery Type that matches terminology in the application.
* API for Device Get updated to return the hardware model and allow filtering using “hardware=” within the Get call.
* Upon upgrade duplicate subnets will be removed.  These duplicate subnets could have been created prior to 19.01 SNMP scans.
* Ability to clear and replace customer during discovery
* Ability to filter saved DoQL queries by First Added and Last Updated
* Ability to use Get API to download building image files
* Deletion of a building within the system will delete devices associated with the deleted building
* Enlogic PDU previously discovered Model number as the Serial Number.
* Hyper-V auto discovery does not update device names to reflect any VM name changes.
* Dell warranty sync not updating for some Gen 16 Dell servers
* Tintri brand storage SNMP discovery now succeeds and populates name, model, serial #, and Operating System information
* AWS Advanced Feature Selection will now populate upon AWS Discovery
* Netapp appliances discovered using SNMP will now detect hardware names and serial numbers in addition to hardware models.
* Room layouts did not allow resizing when the door was positioned on the right side of the room and sizing moved the door too close to the border.
* Deletion of an image file caused an error and prevented subsequent uploads.
* Radware SNMP discovery did not populate serial number
* Azure tags that contain spaces do not discover correctly
* Virtual machines associated with HPE Oneview were cleared upon autodiscovery.
* Azure FrontDoors will now have the category name of FrontDoor
* Patch panel port names can now be searched using basic search capability.
## Latest Device42 Update
For current customers, grab the latest update file @ 
If you haven’t tried Device42 yet, !
#### Share this post
## Post navigation
!Previous articleNext article!
About the author
### 
### Related posts
#### 
Categories
Select Category
ADM
AI
Articles
Auto-Discovery
Automation
Cloud
CMDB
DCIM
Did you know?
Disaster Recovery
Engineering
Free utility
From the Field
Integration
ITAM
ITSM
Migration
News
Product
Release
Storage
Uncategorized
**Latest Releases**
## Recent Posts
## SOLUTIONS
© 2025 Freshworks Inc. All rights are reserved.
## PARTNERS
## QUICK NAVIGATION
600 Saw Mill Road
West Haven, CT 06516
## COMPARE
1 (844) 424-2422
1 (203) 409-7242
* Rick Johnston
# Rick Johnston
## 
As organizations increasingly depend on endpoint devices including smart phones, laptops, and […]
Release Date: December 04, 2024 Release Overview The 19.04 MA release contains […]
Release Date: October 4, 2024 19.03.10 – New MA EBF Release: The […]
Banks and financial institutions provide critical infrastructure that supports consumers, businesses, and […]
Configuration management databases (CMDBs) provide a living record of IT operational processes, […]
Release Overview: The Remote Collector (RC) v19.02.01 release introduces several new supported […]
Release Date: August 1, 2024 The 19.02 MA release contains the following […]
Businesses today are highly regulated. They must comply with industry, governmental, regional, […]
## Posts navigation
1
…
* Ido Benmoshe
# Ido Benmoshe
SVP, Product Management
Device42, A Freshworks Company
As the number of assets and relationships mapped in the Configuration Management […]
Another upgrade incident has been identified, only a week after the well-publicized […]
A faulty software update, in a seemingly standard, routine IT operating procedure […]
# What Are the Steps of CMDB Deployment Best Practices?
Implementing a CMDB isn’t an all-or-nothing proposition. Gradual deployment is important – move too quickly and you’re likely to end up overwhelming your department or committing configuration errors that could leave you blind to changes in your infrastructure. Here are the best practices for deploying a CMDB in a sustainable manner that gives you an accurate infrastructure portrait.
### **Step One: Find an Angle**
As we mentioned, there’s a strong temptation to integrate your CMDB broadly and immediately across the enterprise. What we’ve learned, however, is that it’s best to start in areas where a little effort yields a lot of positive change.
For example, you might want to start with . Without a CMDB, making a change like implementing a new application or an improved feature can have ripple effects which are difficult to imagine, because there’s little way to understand how these changes will affect countless other application dependencies. With the right CMDB tool, you’ll be able to chart the organizational impact of any change.
You may also want to look at patch management. Patches often cause unforeseen consequences, which make many organizations shy away from patching – and as a result,  have an unpatched vulnerability. If your CMBD gives you the ability to predict and trace the effects of a patch, then you’ll be able to patch with confidence.
Data center migrations, cloud strategies, asset management, and other use-cases are all good scenarios as well. The point is to find the situation that’s both relevant and immediately addressable via CMDB and start there first.
### **Step Two: Recruit Stakeholders**
Building a CMDB the right way means keeping its team separate from day-to-day maintenance, if possible. This is because the CMDB itself is supposed to ease or eliminate a lot of day-to-day maintenance tasks. In addition, getting early buy-in from executives to create this team and give it autonomy will lend a great deal of credibility to your efforts.
In addition, you want to give this team the authority to ensure that your CMDB implementation stays focused on the use-case you decided on in step one. No scope creep allowed. This ensures that the CMDB will always continue to deliver value for the organization. Once the first project is complete, your steering group can make sure that the CMDB project moves on in ways that maximize its utility.
### **Step Three: Choose a Vendor**
Choosing a CMDB vendor means evaluating many factors. We freely admit to  – we believe that a CMDB should be on the cutting edge. It should be more than a simple inventory or asset tracking tool, and it should be able to understand the relationships between asset types – including asset types like VMs, cloud instances, and containers. In addition, the discovery process itself should be fairly lightweight – agentless is preferred – and should integrate with existing processes in order to provide additional data.
### **Step Four: Configure**
Now that you’ve chosen a CMDB product, you now need to understand how you’ll customize its features and functions in order to match your unique infrastructure deployment. This means creating configuration items (CIs) to support your primary use-case. Your chosen CMDB will have several pre-configured CIs by default, but you should be able to create others. It’s possible – and certainly recommended – to use default CIs at least to start with, but some of your infrastructure might not be discoverable using your default CI classes. These will need some customization. Depending on the product you choose, you may need to manually define relationships between discoverable and non-discoverable CIs.
### **Step Five: Expand**
You’ve chosen a project, a product, a governance team, and a configuration plan – well done! What’s more, you’ve been able to demonstrate ROI – less work, for better results. Now is the time to begin expanding your CMDB throughout the enterprise.
Integrating your CMDB with other departments should be relatively frictionless, assuming that you’ve proven your ability to generate value. Within the support department, your CMDB can be integrated with the ticketing system to find dependent applications and trace the source of outages. Within information security, you can find applications and infrastructure that are most vulnerable to data breaches. In project management, you can lend heightened visibility to ongoing development.
With Device42, you can do all of those things and more. Our advanced CMDB lets you rapidly gather detailed information about your assets, applications, and dependencies, while our range of easy integrations lets you promote your CMDB across the entire enterprise. What’s more, our helpful support specialists will always help you find out where to start. If you need more information or would like to start seeing value right away, just  and learn how we can help!
Previous articleNext article