Does Adaxes scripting recognize Powershell comments and does it allow for the use of custom modules?

Question

I'm seeing this error when I run a user deprovision. It still executes the script but nobody likes errors!

Run PowerShell Script 'DuoDeprovisionExport' For the user. The term '#this' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again. Stack trace: at <ScriptBlock>, <No file>: line 1 Run external program 'DuoDeprovision' for the user

Below is the first few lines of the DuoDeprovisionExport script I am running. I am running this script within Adaxes. I am not calling powershell.exe with the file path.

#this is required for the external script "DuoDeprovision.ps1" to run.
#That script reads the info from the csv this script creates.
#Adaxes doesn't let us use import-module for custom modules from what I've tested.

My first question is: Does Adaxes recognize Powershell comments? Does it only recognize the block comments like this? <# This is a comment #>

On that note... My second question is: does Adaxes allow for the use of custom powershell modules for the in-house script editor? It is installed in the Program Files directory, but even after calling Import-Module Duo (the custom module) it still doesn't recognize the cmdlets. (This is why I'm running an export script in the first place for my Duo user info. )

Thanks.

Answer 1

Hello,

Does Adaxes recognize Powershell comments? Does it only recognize the block comments like this? <# This is a comment #>

You can use both approaches in PowerShell scripts executed in Adaxes - comment each line with a leading # character or place comment blocks as in your example. In both cases, the comments should not affect the script execution.

According to the error message, the issue occurs because there is a non-printable character before text #this. Most probably, it was kept when you copied the text from another editor. To remedy the issue, you need to remove the character (just delete everything in front of the word this and then add the # character).

My second question is: does Adaxes allow for the use of custom powershell modules for the in-house script editor?

Yes, using custom modules is allowed. The modules should be installed on the computer where Adaxes service is running. If there are multiple instances of Adaxes service sharing common configuration, the modules should be installed on each of the computers where the services run. Also, if a module location differs from the default one, use the -CimResourceUri parameter of the Import-Module cmdlet to specify the alternative location.

Comments

Figures that it would be that easy! Thank you very much, that's working now. I was trying to install the modules to the $env:psmodulepath locations previously. You've saved me a lot of trouble.

You're pretty good!