BMC Atrium CMDB SCCM Adapter Guide
Note
You must first install the MSSQL JDBC driver to use the BMC Atrium CMDB SCCM Adapter.
About BMC Atrium CMDB SCCM Adapter
Introduction
Starting from BMC CMDB 9.0, BMC provides an SCCM adapter for Microsoft SCCM which you can use to retrieve, transform and import data from Microsoft SCCM into the BMC CMDB. This imported Microsoft SCCM discovered data can then be used by end-to-end ITIL Asset and Incident and Change management processes in the BMC Remedy IT Service Management Suite after you have merged your source data to the Asset Dataset.
The SCCM adapter is an Atrium Integrator based solution that provides a starting point for the SCCM integration and is intended to be modified and customized to suit your requirements.
As a best practice, BMC recommends that the data should be represented in the source dataset 'as is' from the source and then manipulated using normalization to meet your expectations. After normalization is done, reconciliation with data in other datasets should be performed before the data is merged into the production dataset. If this process is not done correctly, the AI jobs barely make data transformations.
The SCCM adapter officially supports SCCM 2007 and SCCM 2012, but it can be customized to connect and read data from any later versions SCCM DB.
When using this adapter for other SCCM releases, verify to know if the SCCM Database structure has changed, and if it has changed, you must modify the Database Tables and/or Views for some of the transformations. Contact the SCCM support person in your company who can help you with further steps.
This topic covers the following details about BMC Atrium CMDB SCCM Adapter:
Value Proposition
Integrating BMC Atrium CMDB with SCCM using the SCCM adapter provides the following business values to the customers:
- Saves cost and speeds time to value.
- Eliminates errors by prepackaging the following best practices:
- Provides a complete integration package including Reconciliation Engine / Normalization Engine rules.
- Offers end to end scenario for loading data to BMC Atrium CMDB from Microsoft SCCM.
For more details on integrating BMC Atrium CMDB with Microsoft SCCM, see the following video:
Salient Features of SCCM Adapter
The SCCM adapter which can be leveraged by both BMC Remedy ITSM suite and BMC Remedy OnDemand, provides the following features:
- Imports both configuration items (CIs) and relationship data from Microsoft SCCM.
- Includes pre-defined mappings between SCCM tables and CMDB classes/relationships.
- Mappings are configurable
- Supports both ‘full’ and ‘delta’ update.
- Includes default reconciliation and normalization jobs.
- Provides modification/extension capabilities for out-of-the-box mappings for custom attributes/classes.
- Supports compatibility with the latest version of Remedy (9.0 or later)
Supported Versions
Versions 9.0.00 and later of BMC Atrium CMDB.
Audience
Users with access to supported versions of SCCM and BMC Atrium CMDB.
Enhancements to 9.1
For BMC Atrium CMDB 9.1 release, BMC focused on the following two improvements:
- Installer framework
- SCCM 2012 Mappings
In addition, many other fixes like error handling cases, junk connection clean-up, log file path correction, and customer defect fixes are part of the enhancements.
Installer framework improvements
- Moved to a common BMC install framework.
- Enabled Java8 support.
- Removed Extension Loader Dependency.
- Moved to RIKJ.
Improvements in SCCM 2012 Mappings
- Added mapping for SerialNumber in transformation for BMC_ComputerSystem.
- Slipped and stored the comma separated IP Address stored in SCCM view to an appropriate BMC_IPEndpoint Class.
- Removed SCCMIntegration_LocalFileSystem transformation from job, as there is no appropriate table/view in SCCM 2012.
- Removed owner Information lookup from SCCMIntegration_VirtualSystemEnabler due to structure of SCCM 2012 database.
- Changed source view for BMC_LANEndpoint to v_GS_NETWORK_ADAPTER as it is the right view for this class.
SCCM Adapter Installation
Prerequisites
Install the following applications before using the integration package:
- Microsoft SCCM Application
- Microsoft SCCM 2007 OR Microsoft 2012
- BMC Applications
- BMC Remedy AR System 9.0 or later
- BMC Atrium CMDB 9.0 or later
- BMC Atrium Integrator 9.0 of later
Installing SCCM adapter using the installer
The BMC Atrium CMDB – SCCM integration package comprises the following installer components:
- New Dataset for Microsoft SCCM
- Atrium Integrator Jobs
- Initial load/Update Job
- Delete Job
- 16 transformations
- Reconciliation Job
- Normalization Job
- CMDB Extension (creating attribute for SCCM integration ID). This is necessary for mapping the integration ID with the source system.
To install SCCM Adapter
Note
The SCCM Adapter does not support the following:
- In-place upgrade.
You must manually uninstall and remove the previous SCCM Adapter version before installing another or a newer version.
- Windows authentication on CentOS and Linux.
You must use SQL Server Authentication to run SCCM Adapter on Linux and CentOS.
- Download the SCCM installer files from the following location:
ftp://ftp.bmc.com/pub/BSM/AtriumCore/9.1/Integrations/SCCM/ - Unzip the SCCM installer files.
- Run:
For Windows - setup.exe
For UNIX - setup.bin - In the Copyright panel, select a language, and click OK.
- In the Welcome panel, click Next.
- Accept the license agreement, and click Next.
- Enter the database settings, and click Next.
- Enter details of the server where BMC Remedy AR System is installed, and click Next.
- Click Install.
- View the Installation Summary and click Done.
You can view a log file of the installation in the following folder:
<USERPROFILE>/AppData/Local/Temp/sccmcmdintegration_install_log.txt
Installing SCCM adapter using silent installation
Use the following options file and make the necessary modifications to the file before running the silent installation.
Note
To edit the options.txt file, remove the comment (#) markers. In UNIX environments, ensure that no Ctrl+M characters appear in the options.txt file.
################################################################################ # Options File # # Product Name: BMC SCCM-CMDB Integration # Product Version: 9.1.00 # # To invoke the installer in silent mode with an options file: # setup -i silent -DOPTIONS_FILE=Options.txt ################################################################################ ################################################################################ # Available Features # # add a line to the options file # -A featureName # # # --featureSCCMCMDBIntegration # # ################################################################################ #-A featureSCCMCMDBIntegration ################################################################################ # Product Install Location # # The install location of the product. Specify a valid directory into which the # product should be installed. # # Default value if not set: # - %ProgramFiles%\\BMC Software\\SCCMCMDBIntegration (Windows) # - /opt/bmc/SCCMCMDBIntegration (UNIX) ################################################################################ #-P installLocation=C:/Program Files/BMC Software/SCCMCMDBIntegration #-J SCCM_CMDB_HOME=C:/Program Files/BMC Software/SCCMCMDBIntegration #-J SQL_SERVER_NAME_IP=<SQL Server Host Name> #-J SQL_SYSADMIN_USER=<SQL Server Admin User Name> #-J SQL_SYSADMIN_PASSWORD=<SQL Server Admin Password> #-J SQL_DATABASE_NAME=<SQL Server Database Name> #-J SQL_DATABASE_PORT=<SQL Server Port Number> ################################################################################ # Authentication Properties #for Windows Authentication: #BMC_SQLSERVER_WINDOWSAUTH_OR_SQLAUTH=WINDOWSAUTH # #for SQL Authentication: #BMC_SQLSERVER_WINDOWSAUTH_OR_SQLAUTH=SQLAUTH ################################################################################ #-J BMC_SQLSERVER_WINDOWSAUTH_OR_SQLAUTH=<SQLAUTH/WINDOWSAUTH> #-J BMC_AR_USER=<AR System Admin User> #-J BMC_AR_PASSWORD=<AR System User Password> #-J BMC_AR_PORT=<AR server Port> #-J BMC_AR_SERVER_NAME=<AR server name>- Run the installer with the
-i silent
option.- (Windows)
setup.exe -i silent -DOPTIONS_FILE=<path_to_txt_file_with_installation_options>
- (UNIX)
sh setup.bin -i silent -DOPTIONS_FILE=<path_to_txt_file_with_installation_options>
- (Windows)
Uninstalling SCCM adapter
- Navigate to <SCCMCMDBIntegration_HOME/UninstallBMCSCCMCMDBIntegration>.
- Launch the uninstaller.
- Complete the uninstallation steps to remove the file structure of SCCM adapter.
- Open the Pentaho Spoon client and remove the SCCM package directory.
- Remove the guid (OI-BS005056B5170DoDpHUQF4OR#gJngB1D) from the share application property form (SHARE:Application_Properties).
- Remove the SCCMIMPORT_NE job from Normalization Jobs (BMC Atrium Core Console > Advanced > Normalization).
- Remove the SCCM Identification and Merge RE job from Reconciliation Jobs (BMC Atrium Core Console > Advanced > Reconciliation).
- (Optional) Remove the following attributes from the BMC_BaseElement class using Class manager Console or CMDB driver.
- SMSParentID
- SMSCheckViewName
SMSChildID
Important
Removing the attributes may result in data loss.
Additional Resources
Microsoft has provided an Installation and Configuration guide for SCCM. Install and configure SCCM as per the guides provided. These documents are available at the following location: http://technet.microsoft.com/en-us/evalcenter/bb736730.aspx.
SCCM Adapter Maintenance Tool
The Maintenance Tool provides a common tool to access diagnostics and utilities that are useful when troubleshooting SCCM related issues. You can use the Maintenance Tool to collect diagnostic information, open and view log files, or search logs to identify issues. The SCCM Adapter Maintenance Tool also gives you access to installation and uninstallation logs.
Working with SCCM jobs
The user can work with the BMC Atrium CMDB – SCCM integration package using the following components.
Atrium Integrator Integration Package
BMC Atrium Core includes Atrium Integrator (AI), an Extract, Transform, and Load (ETL) based integration engine.
• Provides an easy-to-understand, wizard-based UI.
• Comprises Out of the box templates which encompass best practices.
• Provides a wide berth of integration technologies such as single tool standardization.
• Comprises a scalable data-warehousing proven architecture.
For the classes provided in the List of Transformations section, a transformation is created to import the class as well as the relationships. Relationships could be done in the same transformation or in a different one based on the design decision. The transformation (AI job/transformation) has both delta and initial load capabilities .In addition to the transformations, a total of 17*2=34 AI child jobs will be created. There is also a delete transformation per class.
A single top level job is designed to call the lower level child jobs that deal with individual classes/relationships. The user interacts only with top level job which is used to monitor and manage the transformation through the Atrium User Interface (AUI) for AI.
SCCM Import Job
The SCCM Import job is responsible for loading data from the SCCM database to CMDB, The job pushes both new data and changes to existing data to CMDB.
The following image provides an illustration of a SCCM Import Job.
SCCM Delete Job
The SCCM Delete job is responsible for setting the MarkedAsDeleted attribute to “Yes” in CMDB for data which no longer exists in the SCCM database.
The following image provides an illustration of a SCCM Delete Job.
Normalization Engine Integration Package
After SCCM – CMDB integration is completed, a Normalization job, along with rules, is automatically configured for the SCCM import dataset. The Normalization Engine job runs in a Continuous mode.
Reconciliation Engine Integration Package
After SCCM – CMDB integration is completed, a standard Identification and Merge job, along with its rules, is automatically configured for SCCM import dataset. The Reconciliation Engine job runs in a Continuous mode.
From 9.0 version and onwards, the following configurations are also available:
- Purge activity is added to the job.
- Reconciliation engine processes only normalized CIs. However, it is not mandatory and that option can be disabled.
Troubleshooting the SCCM Adapter
After installing Microsoft System Center Configuration Manager (SCCM), the user might encounter the following issues:
Incorrect location of error log file
If you have installed SCCM, the user may not be able to locate the error log file. All error log files related to Atrium Integrator jobs are saved in ngie/bin folder. Hence, the user must make sure that the error logging plugin has the correct file location.
Perform the steps given below to update the file location:
- In the Pentaho Integration console, open the Error Logging plugin.
- In the Filename box, update the error log file location to include ngie/bin folder.
- Click OK.
Failure when running Normalization Engine jobs
SCCM installer is shipped with Atrium Integrator, Normalization Engine, and Reconciliation Engine jobs. Normalization Engine jobs might fail to run after the Atrium Integrator jobs. In such a case, make sure that each transformation that SCCM has discovered has data mapped to Category / Type / Item / ManufactureName / Model. It is mandatory to have the data in this format in order to normalize that instances that Atrium Integrator creates.
List of Transformations
The following table lists the transformations available with SCCM.
CMDB Class | SCCM Transformation | SCCM 2007 | SCCM 2012 | Details |
---|---|---|---|---|
BMC_ CDROMDrive | SCCMIntegration_ CDRomDrive | v_GS_ CDROM | v_GS_ CDROM | |
BMC_ ComputerSystem | SCCMIntegration_ ComputerSystem | v_GS_ COMPUTER_ SYSTEM | v_GS_ COMPUTER_ SYSTEM | |
BMC_ DiskDrive | SCCMIntegration_ Diskdrive | v_GS_ DISK | v_GS_ DISK | |
BMC_ IPEndpoint | SCCMIntegration_ IPEndPoint | v_GS_ NETWORK_ ADAPTER_ CONFIGUR | v_GS_ NETWORK_ ADAPTER_ CONFIGUR | |
BMC_ LANEndpoint | SCCMIntegration_ LANEndPoint | v_GS_ DEVICE_ NETWORK | v_GS_ NETWORK_ ADAPTER | |
BMC_ LocalFileSystem | SCCMIntegration_ LocalFileSystem | v_GS_DEVICE_ FILESYSTEM | Not Applicable | Disabled for SCCM 2012 as there is no clear mapping table |
BMC_ LogicalDisk | SCCMIntegration_ LogicalDisk | v_GS_LOGICAL_ DISK | v_GS_LOGICAL_ DISK | |
BMC_ Memory | SCCMIntegration_ Memory | v_GS_X86_ PC_ MEMORY | v_GS_X86_ PC_ MEMORY | |
BMC_ Monitor | SCCMIntegration_ Monitor | v_GS_ DESKTOP_ MONITOR | v_GS_ DESKTOP_ MONITOR | |
BMC_ NetworkPort | SCCMIntegration_ Networkport | v_GS_ NETWORK_ ADAPTER | v_GS_ NETWORK_ ADAPTER | |
BMC_ OperatingSystem | SCCMIntegration_ OperatingSystem | v_GS_ OPERATING_ SYSTEM | v_GS_ OPERATING_ SYSTEM | |
BMC_ Patch | SCCMIntegration_ Patch | v_GS_ PATCHSTATE | Not Applicable | Disabled for SCCM 2012 as there is no clear mapping table |
BMC_ Processor | SCCMIntegration_ Processor | v_GS_ PROCESSOR | v_GS_ PROCESSOR | |
BMC_ Product | SCCMIntegration_ Software_Product | v_GS_ SoftwareProduct | v_GS_ SoftwareProduct | |
BMC_ | SCCMIntegration_ TapeDrive | v_GS_TAPE_ DRIVE | v_GS_TAPE_ DRIVE | |
BMC_ VirtualSystemEnabler | SCCMIntegration_ VirtualSystemEnabler | v_GS_ VIRTUAL_ APPLICATION_ PACK | v_GS_ VIRTUAL_ APPLICATION_ PACK | |
BMC_ CDROMDrive | Delete_SCCM_ CDRomDrive | |||
BMC_ ComputerSystem | Delete_SCCM_ ComputerSystem | |||
BMC_ DiskDrive | Delete_SCCM_ DiskDrive | |||
BMC_ IPEndpoint | Delete_SCCM_ IPEndPoint | |||
BMC_ LANEndpoint | Delete_SCCM_ LanEndPoint | |||
BMC_ LocalFileSystem | Delete_SCCM_ LocalFileSystem | Disabled for SCCM 2012 as there is no clear mapping table | ||
BMC_ LogicalDisk | Delete_SCCM_ LogicalDisk | |||
BMC_ Memory | Delete_SCCM_ Memory | |||
BMC_ Monitor | Delete_SCCM_ Monitor | |||
BMC_ NetworkPort | Delete_SCCM_ Networkport | |||
BMC_ OperatingSystem | Delete_SCCM_ OperatingSystem | |||
BMC_ Patch | Delete_SCCM_ Patch | Disabled for SCCM 2012 as there is no clear mapping table | ||
BMC_ Processor | Delete_SCCM_ Processor | |||
BMC_ Product | Delete_SCCM_ Product | |||
BMC_ TapeDrive | Delete_SCCM_ TapeDrive | |||
BMC_ VirtualSystemEnabler | Delete_SCCM_ VirtualSystemEnabler |
Comments
Hello
I have questions about the SCCM Adapter Maintenance Tool:
Thank you!
Hi Thomas,
Thank you for your comment. I will discuss with the technical team and keep you informed.
Regards,
Kamal
Hi Thomas,
Thank you for your comment. You may want to raise a help ticket as this is a product issue.
Regards,
Kamal
Does this adapter enable software usage via SCCM?
Is there more information about the SCCM metering connection to Atrium CMDB usage available?
Thank you!
Hi Chris,
Thank you for your comment. I will discuss with the internal team and keep you informed.
Regards,
Kamal
Hi Chris,
Thank you for your comment.
The adapter does not enable software usage via SCCM.
There is no SCCM metering connection to Atrium CMDB usage.
Regards,
Kamal
Is the SCCM Adapter Maintenance Tool backwards compatible with ARS 8.1? If not, is it possible to use the Atrium Integrator Jobs ?
Thank You,
Tom Hamill
SCCM Adapter 91 is supported only for Remedy 9.x. Maintenance tool bundled with adapter is only to collect logs.
Can you please clarify your query. #1 in what use case you are using it with 8.1 ? #2 what do you really mean by using AI Jobs ?
Hi Devendra,
Client has ARS 8.1 version - is it possible to just use the transformations and let them feed the data into CMDB ?
The Recons and NE jobs not concerned about this for now...
Thanks
Mpumi
Hi Mpumelelo,
I had a discussion with Devendra regarding your comment.
He has clarified that SCCM Adapter 91 is supported only for Remedy 9.x. For 8.1 there was older version of adapter released. Request you to get in touch with BMC Support for further resolution.
Regards,
Amol Redij
Hi Tom,
Did you ever get answer for your question on the 8.1 Version - in the same position....
Mpumi
Hi Mpumelelo,
The documentation team regularly watches the comments, and we try our best possible to address every concern of our customers.
I will discuss the issue with Devendra Yadav and get the required answers. Meanwhile, you can email me (amol_redij@bmc.com) your specific queries, and I shall be glad to help you out.
Regards,
Amol Redij
For 8.1 there was older version of adapter released. get in touch with support to get same.
SCCM Adapter 91 is supported only for Remedy 9.x.
Is it possible to filter out servers, so that only clients from SCCM is synced to the CMDB?
Hi Magne,
Thanks for your comment.
I will seek clarification on this from the SME and update you accordingly.
Regards,
Amol
Hi Magne,
Thank you for your patience.
I had a discussion with the SME about your comment. However, we seek some more information on the issue.
May I request you to please explain your concern in detail so that we can provide an apt resolution.
Regards,
Amol
Is it really necessary to give a Database Administrator privilege during the installation?
Or can we use another type of user/privilege?
If yes, please specify it
Thanks
Hi Ravian,
Thank you for your comment.
You can use any user login privileges. However, ensure that the user has access permissions to the SCCM tables.
Hope this helps.
Regards,
Amol
There are no versions of this product prior to SCCM91. The indication earlier ( above ) is incorrect.
During Installation Why Do we need SCCM SQL Server - Database Admin User Account?
our SCCM Admins are questioning this - If Remedy will have to Read the data then why Admin User?
Regards
RP
Hello Rahul,
I will discuss this with the concerned SME and will write back to you.
Regards,
Nidhi
Even a User with Read Only Access of SCCM DB - Works - Just tested the Installation. Installer Screen says DB Admin user which some time gives heart break to SCCM Admins.
Regards
RP
There is no need that level of access.
#-J SQL_SYSADMIN_USER=<SQL Server Admin User Name>
I think this may have been something the developer has used as a variable name, but it does not require Admin level.
Hi,
I get this error after filling the SCCM DB inputs: 'No SCCMSQL Server is detected please check the Host Name and Port Number'. I know the hostname and port is correct, I'm able to access the DB using SQL Management Studio and the same credentials. The user is not an DB Admin, but as many of you stated above it's not necessary.
Maybe someone else had the same difficulties, maybe some specific syntax is needed to enter the SCCM details?
I checked here as well, but the Solution did not help: https://communities.bmc.com/docs/DOC-64526
Is you SCCM database is on instanced SQL server ? if so installer doesn't gives you option to specify instance name. what you need to do is specify exact port the that particular instance.
After some more testing I found out that the installer ignores whatever you input in the User and Password fields if you select Windows Authentication. It uses the account you started the installer to access the DB. That's big problem, as the admin account on one server does not necessary have access to DB and vice versa. Is it intended to work that way or it's a bug?
This is the way it as been designed. Windows authentication mean use same credentials to login in DB using which installer is launched.
if you want different credentials go with SQL authentication.
Hi Andrius,
Thanks for bringing this to our notice. I will touch base with the SME and get back to you with the clarification. Please give us some time.
Regards,
Vinay
On Supported Versions there is written that SCCM Adapter supports Versions 9.0.00, 9.0.01, and 9.1.00 of BMC Atrium CMDB. Is the SCCM Adapter also compatible to Version 9.1.03 ?
I have this installed on my Dev 9.1.03 box, and cannot open any of the transformations, because the "CMDB Lookup" step doesn't appear to exist in the 9.1.03 version of AI.
Hello Evan,
I will discuss this with the concerned SME and will write back to you.
Regards,
Nidhi
Hi Evan SCCM Adapter supports/compatible with Atrium versions 9.1.03. If CMDBLookup step doesn't exist with 9.1.03 (after upgrading Atrium Integrator to 9.1.03 version) then the issue could be your environment specific. Could you please contact BMC Support for the same?
Yes, is is compatible. In 9.1.03 Pentaho has been iupgraded to version 6. You need to make sure you run AI installer. Essentially it is 3 installation. ARS/CMDB and AI (Server). If you are using Spoon in your local box then you need to run AI (Client) in the local machine as well.
Hello Peter,
Yes, the SCCM Adapter is compatible with version 9.1.03.
Regards,
Nidhi
Hi When installing the SCCM Adapter it is not clear what must be filled in on the 'Microsoft Discovery Database Details:' Page. Can You please add some more information of what has to be filled in. Database Name: including Database instance? Administrator User: Do you mean Admin User of SQL Database or Admin User of Windows System where the SQL Database is installed? I found that many people have problem with this connection parameters. So please provide us with some more information. Regards, Peter
Hello Peter,
I will discuss this with the concerned SME and will write back to you.
Regards,
Nidhi
Hello Peter,
I discussed this with the SME and here is some information on what must be filled in the BMC Atrium CMDB Adapter for Microsoft SCCM 9.1.00 dialog box:
instance\databaseName or databaseName
This depends on how MS SCCM database is installed.
Database administrator user
Hope this answers your query.
Regards,
Chaitanya
Hi Peter,
I have tried using the name of the sccm server and the database server as the machine name, but I am still unable to install the adapter. I keep getting the error message "No SCCMSQL Server is detected please check host name and port number"
Hi Lyde,
Let me check this with an SME and respond at the earliest.
Regards,
Maithili
Hi Lyde,
Request you to reach out to BMC Support for helping with a resolution.
Thank you for reaching out to us. Please let us know if there is any other query you need help with.
Regards,
Maithili
Good Day,
I installed the adapter using the system Demo account - somehow the Company attribute defaults to Carlbro company, which i have disabled on Company form. Question is if there is someway to change the company that the CI's pulled are linked against ?
Thanks
Your Default company is configured in the ITSM/ASSET management configuration console. It is a site wide setting and has nothing to do with SCCM. If you define a default company ALL CIs created in your CMDB will be put under it unless they have a populated company field.
Thanks Gustavo for this.... - if i may ask what relationship mapping (class) is to be used between Virtual Machine and Physical host container. Client using SCCM 2016 and nothing coming back on the Virtual System Enabler Job...
You can download this PDF: https://docs.bmc.com/docs/ac91/files/609847285/774035973/1/1509706176314/439997_CMDB9.1_MappingYourData.pdf These are guidelines for how to map your data and to which classes.
This file does not exist. Can you point us to it again? thanks
Hi Jeffrey,
Thank you for reaching out! I tried to open the link above and it seems to be working fine for me. Can you please try once again? In case you are unable to access this file, we recommend you reach out to BMC Support for assistance.
Regards,
Maithili
Hi, Could you please confirm on below points: 1. Does this adapter usage require any sparate license purchase? 2. Are there any limitations for this adapter usage ? Any Windows OS / version restrictions for enabling this integration?
Hi Anand,
There is no separate license that needs to be purchased for the adapter usage, and there are no Windows/OS/Version dependencies or limitations.
The integration is supported on Windows OS and Linux version supported by Remedy/Atrium 9.1.
Regards,
Nidhi
Hello Anand,
I will discuss this with the concerned SME and will write back to you.
Regards,
Nidhi
Is it safe to assume that this SCCM Adapter should be installed on every AR Server in the server group that is configured in the Operation Ranking form to perform the Atrium Integration Engine operation at some defined ranking level?
Hi Brent,
Thanks for your query.
I have discussed this with the SMEs and found that the SCCM Adapter does not need to be installed on every AR Server in the server group. The SCCM adapter needs to be installed only on a primary or an integration server.
Regards,
Chaitanya
To clarify more on this, the adapter is nothing more than a set of AI jobs, NE jobs and RE jobs to import, normalize and reconcile the data. Those activities will run in whatever server you configured for AI, NE, RE but since all the SCCM adapter processes are in the DB, you do not need to repeat the installation in any other server.
Hi Everybody!
Anybody knows if exists an adapter compatible with SCCM 2016?
I need it!!!
I can to do an integration with this adapter but with SCCM 2012???
Regards.
Hello Fernando,
Thanks for your comment. I will check with the SME and update you shortly.
Regards,
Kanchana
Hello Fernando,
I found out that adapter compatible with SCCM 2016 is being planned for an upcoming release. We will let you know the details when it is planned.
Hope this resolves your query.
Thanks and regards,
Kanchana
We are using current adapter with SCCM 2016 and it works. Lots of customization was needed to the Integrator workflow to meet our needs, but it's doable.
Hi Andrius Seirys,
Thanks for informing us.
Regards,
Sirisha
Hi Adrius,
I'm also using it but had to disable the transformations that didn't seem to have comparable mappings on SCCM 2016 and that was it …. Im interested on the other customization that you had to apply to get it working, if may share ?
Tx
Maybe I was not clear. Customization was needed to meet our specific data processing needs. To make it process data BMC way only little changes were needed. Some that I can remember: - SCCMIntegration_OperatingSystem transformation - need an arrow from CMDBOutput_OperatingSystem to CMDBLookup; - SCCMIntegration_OperatingSystem transformation - need to remove arrow from Filter rows to CMDBLookup; - SCCM_CMDB_Delete job - need to change direction of the arrow from Delete_SCCM_LogicalDisk to Delete_SCCM_Memory
The adapter officially support 2007 and 2012. Why? Because we tested the adapter only with these 2 SCCM Databases. This does not mean it cannot connect and read data from ANY SCCM DB. The problem when using this adapter in other SCCM releases may be that SCCM Database structure changed, and so you will need to change the Database Tables and/or Views for some of the transformations. This should not be a hard task, specially if you have an SCCM support person in your company that can help you understand what are the changes between, for ex. 2012 and 2016.
The link http://technet.microsoft.com/enus/evalcenter/bb736730.aspx does not work. thanks
Hi Jeffrey,
This link seems to be working fine; it points to the Microsoft Evaluation Center. However, let me check if we can share an alternate link to get you to the page you are looking for.
Regards,
Maithili
Yes the link opens up but I was expecting to be point to the document and still can't find the document that is mentioned above. thanks
Hi Jeffrey,
Please try this link - Resources for installing System Center Configuration Manager sites
Regards,
Maithili
Where is the SCCM Adapter Maintenance Tool located? Also I'm on Remedy On Demand. thanks
Hi Jeffrey,
Thank you for your comment. Will check with the SME and respond at the earliest.
Regards,
Maithili
Were you able to find out where the tool is located? thanks
Hi Jeffrey,
You can find the SCCM adapter maintenance tool in the SCCM adapter installer package at the following location:
<sccm9.1.00.win\SCCMCMDBIntegration\Disk1\utility\ SCCMCMDBIntegrationMaintenanceTool>
Hope this is useful.
Regards,
Maithili
Great, The next problem this is not part of our downloads since we are on Remedy On Demand. I'll have to ask for Support to put it on the FTP Site. thanks
Hi,
Is the BMC Atrium SCCM Adapter 9.1 is compatible with SCCM Application version 18.6 or later?
We are using BMC Atrium CMDB version 18.08. Is there a version of the adapter for 18.08 or we can use version 9.1?
Thanks,
Hi Moath,
we upgraded Remedy/Atrium from 9.1.04 to 18.08 and SCCM adapter still works. But I haven't found any official information from BMC about the support or new versions of SCCM adapter
Andrius
Hi Moath,
Thank you for your query. I will check this with the SME and respond at the earliest.
Regards,
Maithili
The adapter officially support 2007 and 2012. Why? Because we tested the adapter only with these 2 SCCM Databases. This does not mean it cannot connect and read data from ANY SCCM DB. The problem when using this adapter in other SCCM releases may be that SCCM Database structure changed, and so you will need to change the Database Tables and/or Views for some of the transformations. This should not be a hard task, specially if you have an SCCM support person in your company that can help you understand what are the changes between, for ex. 2012 and 2016. Also the adapter can be installer in any 9.1 version of ARS/CMDB/AI... that´s up to 1902 (Which is actually 9.1SP6).
Hi, Does BMC Atrium SCCM Adapter 9.1 compatible with SCCM 2016? Currently we are using SCCM Adapter 9.1 with SCCM 2012.next month we are planning to upgrade to SCCM 2016. is there any major mapping changes in the Pentaho spoon job? If BMC requires time to release new adapter for SCCM 2016 ?can we expect a KA\Document from BMC to change the Mappings manually?
Hi Thejas,
Currently, BMC Atrium SCCM Adapter 9.1 is not compatible with SCCM 2016. However, i will confirm this with an SME and notify you at the earliest.
Regards,
Maithili
The adapter officially support 2007 and 2012. Why? Because we tested the adapter only with these 2 SCCM Databases. This does not mean it cannot connect and read data from ANY SCCM DB. The problem when using this adapter in other SCCM releases may be that SCCM Database structure changed, and so you will need to change the Database Tables and/or Views for some of the transformations. This should not be a hard task, specially if you have an SCCM support person in your company that can help you understand what are the changes between, for ex. 2012 and 2016.
It says Supports both ‘full’ and ‘delta’ update. How is this enable/disabled? Also How can you change the date that is used? thanks
Hi Jeffrey,
The delta functionality logic is part of the transformation and is added at the beginning. It works based on the NGIE:Delta form which has a field named ARDelta for holding the date for delta. The delta updates occur based on this logic.
On checking any import transformation from the SCCM job, you will see the delta logic that is configured. Thanks.
I have already figure out the logic and you have to setup Set in run variables, IsDelta_ + Transformation Name = Y to get it to work.
Thank you, Jeffrey! I will close this comment trail in that case.
Do feel free to reach out for any other queries.
Regards,
Maithili
Hi, this page of the doc is not present in version 19.02 . Is this adapter compatible with Atrium 19.02?
thanks
Hello Amar,
Thank you for your question. Yes, this adapter is compatible with CMDB 19.02 but you may need to modify and customize it to suit your requirements. Please refer to the Introduction section of this guide for more details. Hope this helps.
Regards,
Kanchana
Hi Kanchana,
After running the SCCM job, CI's are getting created on the BMC.CORE:BMC_ComputerSystem form, however they are not showing on the AST forms... (think the corresponding AST:Attributes record is not created). Is this normal ? Tx
Hi Mpumelelo,
This could be due to pending Reconciliation job after the SCCM job was completed. Try to run a Recon job and then check if the AST forms are updated wiht the CIs.
Please let me know if this approach doesn't work.
Regards,
Maithili
Check this article out.
https://communities.bmc.com/docs/DOC-61026
Thanks Jeffrey,
@Maithili - Shouldn't the CI's be visible even before reconciliation/normalization ? Ours will fail normalization as haven't added the Product categorizations for the CI's received from SCCM
Yes, that's correct. The CIs should be visible before reconciliation/normalization.
In case this is not working properly, we recommend you reach out to BMC Support.
Regards,
Maithili