

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
Hi Experts,
we have ucmdn 2019.02 its a fresh installation, the same UD agent version is allready installed on the servers before uCMDB for some reason.
the qustion is how we can connect the new uCMDB to the installed UD Agent without uninstall an re install the agent?
you help is appricated.
Accepted Solutions

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
Hello,
As I submitted the ER a long time ago, I created the new idea: Enhance functionality of exportCredentialsAndRangesInformation.
Happy voting,
Michael

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
This topic was escalated to Email Message on 04-19-2019 by an automatic escalation.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
Hello there,
I'm also very interested in this topic. Please someone advice.
For example, they re-install DFP and UCMDB completely, how to get the target UDAs connected to it? There maybe hundreds of such UDAs, so re-install may be problematic...
Thanks all!
Dima

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
The logical solution would be to use on the old environment the JMX method exportCredentialsAndRangesInformation to export the credentials from the old environment where the UDA credentials where created.
The initial UDA credentials were used to generate the UDA certificates for the initial UDA deployment on the remote hosts. These certificates are unique and they have a UD SHA1 ID which can be migrated with this JMX method.
This is documented at https://docs.microfocus.com/UCMDB/11.0/ucmdb-docs/docs/eng/doc_lib/Content/Jmx_reference/Hardening/JMX_ExportImportEncrypted.htm
The disadvantage is that we can't export individual credentials and it will always create a file in UCMDBServer\conf\discovery\customer_1 that will contain all the credentials from the source UCMDB. The is an older ER to allow the export of the credentials but in separate files (1 file per credential ID) https://softwaresupport.softwaregrp.com/group/softwaresupport/search-result/-/facetsearch/document/LID/QCCR1H122118
One workaround to avoid exporting all the credentials is to export all the credentials in the old env to a backup file, delete from the old env except the UDA ones, export again the credentials (the second file will contain only the UDA credentials and this can be imported in the new env) and reimport the initial backup file which will restore all the credentials.
If this https://softwaresupport.softwaregrp.com/group/softwaresupport/search-result/-/facetsearch/document/LID/QCCR1H122118 is useful then please submit it on Idea Exchange to put some more relevance on it.
Kind regards,
Bogdan Mureșan
EMEA CMS Technical Success

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
Hello,
As I submitted the ER a long time ago, I created the new idea: Enhance functionality of exportCredentialsAndRangesInformation.
Happy voting,
Michael

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
hello mate!
The main problem in UDA case is the certificate, there's a way to import the certificate from DDMI in JMX, it even can create the credentials, but it does not work for me - it says 'handshake error'. There's a reference to keystore in DDMI case - acskeystore.bin. I tried to put cacerts from ok dfp there. I suspect the problem is the SHA ID you mentioned - it is different in such new credentials.
Look here:
Thanks,
Dima