Powershell API examples

felix

Has anyone used the two newer powershell API script examples? If anyone can share any feedback it would help me decide if they're ready for the TRMM script repo.

In my experience, the create/update script works without issue.

I've noticed the network scanner script sometimes causes issues with location id and network id updates. It also fails on a server that has hamachi installed. I know that is an implementation issue because the automation policy I'm using pulls the IP automatically and that server has 2 IPs. I'll probably rethink of how I'm supplying the IP so I don't need a custom policy for similar situations.

bhampton

felix

I setup the create/update script in my TRMM server and I keep getting that the Asset exists and it updates it but don't see it under the client Assets tab.

Now I will preface this by saying that I had a few issues getting my TRMM server stable and had to move this same test device to 1 other TRMM Server and then back again once I found my issues - so that may play a part here. But, as stated above I can't get it to be seen within my assets tab for the client I have setup.

My hunch says that there's a lingering item in the database I need to flush out, but I'm not to privy on how to do such a thing.

I will say it did work the first time I ran it on the machine but haven't been able to get it to work since.

Outside of this script I haven't tested any of your others. If you wouldn't mind linking the rest of them I'll test what I can and let you know the results!

felix

Network scanner script

If the script says "asset exists" it made the API call correctly and found the asset by mac address. For ITFlow not showing the asset, is it possible the client ID doesn't match between TRMM and ITFlow?

bhampton

I checked that and based off the scripts documentation I have the correct client ID. Not too sure why its not doing anything though.

felix

bhampton I don't think the issue is with TRMM since it only is used to send the script and run it on the PC. I just added then updated a new PC and it's being displayed so the issue is not an ITFlow update.

Can you try creating a new client in ITFlow and use the new client's ID to see if it will display there? You can try running the script in Powershell ISE, but I don't suspect it will give more clues.

felix

I have noticed some duplicates in cases where a device changes its connection interface (wired/wireless). I might add a collector script that supplies TRMM with the device ID. Then the create/update script would default to the supplied device ID and fall back to mac address if it doesn't find the device ID. This would make the script more TRMM specific. I was trying to avoid that so they can be more universal.

bhampton

I think that's what's happening because this machine is a VM within a Hypervisor. Testing again today to see what happens.

bhampton

I "think" I know what's happening now.

I have 2 hosts at different sites and locations both running "ESXi" ("Host01/02") and a "Windows 2019 Server" ("GuestVM").
I ran the update script on the "GuestVM" on "Host01" and got the following output:

GuestVM on Host01 Output:

Last Run: Apr-18-2023 - 13:38

Run Time: 3.3633212 seconds

Return Code: 0

Standard Output

ITFlow IDs - Location ID: 1 1 1 1 1 1 1 Network ID: 1 0 1 1 1 1 1

Asset already exists - Updating...

Asset updated.

When I run the script on the other "GuestVM" on "Host02" I get the following output:

Last Run: Apr-18-2023 - 13:44

Run Time: 6.4151204 seconds

Return Code: 0

Standard Output

ITFlow IDs - Location ID: 1 1 1 1 1 1 1 Network ID: 1 0 1 1 1 1 1

Asset already exists - Updating...

No changes to update.

It looks like for some reason it sees both "GuestVMs" at the same location, even though I have both Custom fields for Location ID and Network ID filled out for each site and confirmed they're different.

I also confirmed that both Client ID's are matching what's in my ITFLow instance and both are different as well.

Let me know if this helps!

felix

bhampton I've had some issues with the location and network IDs on one client. It would show the wrong location in the asset list, but no location in the edit modal. I had to delete and recreate the location and network to fix it.