shannon

That was it! Guess one of my team members set the value. The error messages are gone and everything seems healthy. Appreciate the help!

It should but it doesn't. Here's what I see when I launch the client. Clicking 'Ok' takes me to Home screen where I can see my entries

Here's the button I click that does nothing

Thanks.

Hi James. The upgrade to 2020.3.28 isn't working either. When I try (clicking the button) I don't get any feedback (no pop-up saying it was successful or not).

Thanks

Recently we scheduled a upgrade to version v2020.1.20. After creating a backup and verifying there were no db connections, I attempted a database upgrade to v2020.1.20 (from v2019.2.24). The client reported that the upgrade was successful; however when refreshing the datasource, it reported I needed to use client version v2019.2.24. Need some guidance on how to troubleshoot. I've forwarded our db schema. Thanks.

Thanks for the update. When the change is ready it would be helpful to know what version it will be in so I can plan an upgrade.

Thanks for the quick response.

We have a security management tool (CyberArk) we use for centralized authentication. Each of our defined RDM connections has the same "global" custom variable (defined in Administration -> System Settings -> Applications -> Custom Variables) in the 'host' entry. We would like some of our users to be able to override this variable because they need to connect to a different security management too. For these users we thought we could define the same variable in their client ( "File -> Options -> General -> Custom Variables") and it would override the "global" ones. After some testing we're not sure the app works this way. Please clarify. Thanks!

Hi. I'm looking to set a "global" custom variable (Administration -> System Settings -> Applications -> Custom Variables) but for certain users override the value. Assuming that this is possible, would the user-scoped variable be defined in "File -> Options -> General -> Custom Variables"? Thanks.

Thanks Olivier. Being able to use alternate credentials will be extremely helpful. I'm looking forward to the next release!

Excellent! Much appreciated :)

Correct. Here's the background...

Our company has a centralized Identity and Access Management (IAM) security tool that requires a special configuration to open an RDP session. The user's credentials (what's stored in RDM) are not the credentials actually used for the RDP session. For example if a user (i.e. 'CORP\bob') wants to remote to a server, he authenticates to the IAM tool and then the IAM tool establishes the connection with a different account associated with his username (i.e. 'CORP\IAM_bob'). 'CORP\bob' cannot RDP directly to the server. Our RDM sessions are set up to jump this hurdle and the end users are none the wiser.

My team uses service accounts for our automation, and these accounts have permission to connect directly to our servers (bypass IAM access) so I'd like to use these credentials for invoking 'Invoke-RDMLoadFromInventorySession'. If I can't pass in a PS credential object, the only other option I have (I think) is to duplicate our existing session tree and have all the entries use one of our automation accounts.

Awesome. Thanks Olivier. Any chance the cmdlet will support PS credential objects in the future?

Ran a few more tests. Definitely seems like there's an issues (maybe user-related) to how the cmdlet handles the different credential settings. It would be great if the cmdlet accepted PS credential objects as an option. Any chance this is on your feature roadmap?

Ok. Credentials are inherited from the parent folder. The parent folder is set to 'My Personal Credentials'. When I set the credentials to 'default', set the 'username' & 'domain' fields, and store the password in the database it works. Progress!

Hi Olivier -

I may have claimed success prematurely. After opening a new PS ISE session I tried the 'Invoke-RDMLoadFromInventorySession' again and it wasn't success (different error)

'VERBOSE: Success: False - TESTSERVER'

I tried in both 32-bit and 64-bit PS ISE sessions, rebooting my system and reinstalling RDM v12.6.6.0; no joy.

Any suggestions?

For my original testing I created a test session named 'TESTSERVER'. For your testing I would suggest using an existing session. After the v12.6.6.0 update 'Invoke-RDMLoadFromInventorySession' works as expected.

Thanks for the quick turnaround Olivier.

Thanks for the update

I installed the new client version that was released today (12.6.5.0) but unfortunately I'm still getting the 'ignored' session error.

Looking forward to it :) Thanks again for the prompt response.

Thanks for the update.

Ah ok. All of the sessions I've tried are 'RDP' sessions ('RDPConfigured')

I'm not explicitly declaring the variable so PS creates it as [System.Object[]]'

Had an opportunity to use the 'Invoke-RDMLoadFromInventorySession' cmdlet and I'm running into an odd issue. Whenever I run the cmdlet it completes almost immediately and doesn't run the inventory. Adding the '-debug' flag is showing that the session is being "ignored" (ex: VERBOSE: Ignored TESTSERVER session')

Here's the test script I've ran:

$tsObj = Get-RDMSession -GroupName 'DevOps' -IncludeSubFolders | ? {$_.Name -eq 'TESTSERVER' }

Invoke-RDMLoadFromInventorySession -Session $tsObj -Verbose -Debug

Set-RDMSession -Session $tsObj -Refresh

If I kick off the inventory manually using the UI it works fine. Any idea what could be the issue?

Also, if this isn't the best place for this question let me know the correct forum and I'll re-post.

Thanks again.

Perfect! Thanks for the quick response.

Not entirely sure if there are any other threads on the topic of exposing 'load inventory' functionality outside of the client; however, I for one would love to see this feature. In our organization we have well over 2500+ machines we're managing and manually running 'load inventory' against them individually (or even with 'batch edit') is tedious and/or unreliable for a large number of sessions. For example yesterday I kicked off an overnight 'load inventory' using 'batch edit' against a small sampling of our server farm (about 200) and it died about half way through. Might just have been my experience; however, it'd be much easier to incorporate a PowerShell cmdlet into the nightly sync and maintenance scripts we're already running.

If there has been any traction on this I'd love to hear about it. :)

Perfect. Thanks!