Forum Discussion

SteveDahlberg's avatar
SteveDahlberg
Icon for Neophyte rankNeophyte
27 days ago

New to LM: How do I refer to the local filesystem in an embedded PowerShell script of a DataSource?

How do I refer to the local filesystem in an embedded PowerShell script of a DataSource? The below works fine from a PowerShell session console on a Collector server, but fails when running embedded ...
  • Mike_Moniz's avatar
    Mike_Moniz
    25 days ago

    Yes, and you see it worked for me in my screenshot with a full path. The only thing I'm aware of that LM will do to a powershell script is do a search-and-replace of ##TOKEN## but I didn't see any of that in your code. Even your error message isn't show the path getting screwed up and it's powershell telling you the file doesn't exist there.

    I would 100% make sure the script is actually running on the server you think it's running on. Does "Write-Output $env:computername" show the name of the server with the file?

SteveDahlberg's avatar
SteveDahlberg
Icon for Neophyte rankNeophyte

Our LM person who handed this task over to me (and I'm glad for it because I've learned a ton about LM in the past weeks), was strongly under the impression that the setting was that AD would run ONLY if the user manually ran it, and therefore I thought the same, and the wording of the option is compatible with that. However, once I got into creating this DataSource, I definitely noticed felt it had run unexpectedly a few times, so I realized that technically that setting wording could also be interpreted more ambiguously.

So it's interesting to hear you say that. I wish I knew for sure about the items you mention, but primarily also whether any of the following could potentially trigger Active Discovery even with that setting applied:

A script updating a property on a resource-level or instance-level property?

Manually creating or editing a resource's property?

Saving changes to the script in the DataSource, but not running "Force DataSource Re-Match" or "Run Active Discovery"?

Same but with doing the "Force DataSource Re-Match" but not "Run Active Discovery"?

-Steve

 

Mike_Moniz's avatar
Mike_Moniz
Icon for Professor rankProfessor
9 days ago

I never really used that option so never really thought of it as a possible 100% manual process. It might not even been an option when I started using LM (unsure), which may be why it didn't really come up.

You may want to reach out to LM support or your rep to see if they can provide more technical details on exactly when it runs.