jelliston

Lots of good things in the update, however, there are a couple thing which have created some major headaches for us. We run in FIPS mode. 1. With 2020.2 we can no longer push agents from the orion core. 2. Neither the Gold Master nor the GPO agent install work properly as the agent configuration utility fails to run due to…

It appears there may be a permissions issue with the update query. I am using python with the API and a "select *" from the table works while the "update" fails. Tested the following: - Connection using: Local account and the domain account used to connect to the DB (same results) - Via the SQL UI in the create reports UI.…

I will look at adding this into our account setup. I had not seen that verb, could be very useful for those DB interactions where SWQL either doesn't facilitate any access or permissions block. Powerful but dangerous. Thank you.

I have looked in numerous SWQL locations and not found anything. The only place I have found what looks like the setting is in the SQL db itself. I was hoping NOT to have to touch that directly.

I can, and do, create Orion accounts, including admin accounts via the SDK. What I don't see is a way to annotate/update a new Orion account to have SAM "admin" rights. Simply setting the new account to be an admin does not give it admin access to all modules and I don't see SWQL access to the SAM table which manages…

Apparently there are different kinds of accounts and some can be edited some cannot. Accounts which are internally created (users allowed in due to AD or SAML) cannot, however, the base AD or SAML group can be edited for most, but not all, properties. The SWQL Studio settings above are simply misleading and don't reflect…

You may also be able to escape the @ with the "\" character so your query would be something like: SELECT TOP 50 'Asset Manager' AS [Full Name], 'example\@work.com' AS [Email], N.Caption as [ItemName] From Orion.Nodes N Sorry I can't test it for you.

My suspicion is the account used to run the script does not have sufficient permissions. I suggest you start with a very simple script which writes to a log file to ensure you are triggering the script correctly then add complexity with the invoke-command being one of the last things to add back, be sure to log any…

The scripts run locally on the remote system and do not utilize any explicit encryption.

Lots of good things in the update, however, there are a couple thing which have created some major headaches for us. We run in FIPS mode. 1. With 2020.2 we can no longer push agents from the orion core. 2. Neither the Gold Master nor the GPO agent install work properly as the agent configuration utility fails to run due to…