[Chloe Hexnode 14 April 2023 Chloe Moderator]

Hello @clyde, welcome to Hexnode Community!

Yes, you got that absolutely right. This is where arguments come in handy. In the script, you can declare a variable and the value given as the argument will be passed to the variable during execution.
You can use wildcards to pass the respective value to each user.

That is, if yours is a batch script, it will look like this:

Script to shift Azure AD accounts

net localgroup administrators /add “AzureAD\%1”

1	net localgroup administrators /add “AzureAD\%1”

Where %1 is the variable.

In the Arguments field in the Hexnode UEM portal, you can enter the wildcard %username%.

Hope this helped with your query.

Regards,
Chloe Edison
Hexnode UEM

[Clyde Participant 17 April 2023 Clyde Participant]

Thank you.

Am I limited to the arguments listed on this page: https://www.hexnode.com/mobile-device-management/help/executing-custom-scripts-for-windows/

Or can I enter any text into the arguments field?

[Faustica Participant 18 April 2023 Faustica Participant]

To use arguments in your script, you need to define them at the beginning of the script using special variables called positional parameters. These variables are represented by numbers, starting from $0, which corresponds to the name of the script itself. For example, if you want to pass the username as an argument, you can define it like this:

<br />param(<br />[string]$Username<br />)<br />

This creates a parameter named “Username” that expects a string value. You can then use this parameter in your script wherever you need to reference the username, like this:

<br />net localgroup administrators /add "AzureAD\$Username"<br />

When you run the script, you can pass the username as an argument like this:

<br />.\myscript.ps1 -Username jdoe<br />

This will add the user “jdoe” to the Administrators group.

[Faustica Participant 18 April 2023 Faustica Participant]

Microsoft Docs: https://docs.microsoft.com/en-us/powershell/module/microsoft.powershell.core/about/about_functions_advanced_parameters?view=powershell-7.1
2. PowerShell Tutorial: https://www.tutorialspoint.com/powershell/powershell_script_arguments.htm
3. Pluralsight Blog: https://www.pluralsight.com/blog/it-ops/powershell-script-arguments

you can refer to this sites for refernces

[Chloe Hexnode 19 April 2023 Chloe Moderator]

@clyde, there’s absolutely no limitation, you can use the Arguments field to pass any types of values.

@faustica, thank you so much for your valuable insight. We truly appreciate it!

Regards,
Chloe Edison
Hexnode UEM

[Clyde Participant 20 April 2023 Clyde Participant]

This is really helpful, thank you everyone.

[Clyde Participant 26 April 2023 Clyde Participant]

Stuck again…

How do I deal with spaces in file and folder names in powershell?

For example, creating a new folder with this PS script:

param([string]$Dir)
New-Item -Path “$Dir” -ItemType “directory”

This works with the argument: .\newdir.ps1 -Dir c:\Test

But not: .\newdir.ps1 -Dir c:\Another Test

Did some googling and found many many different answers to this involving brackets, single quotes, and all kinds of things, and none of them seem to work. Some just outright fail, others drop odd directores into system32.

[Eren Hexnode 27 April 2023 Eren Moderator]

@clyde To pass arguments that contain a white space in a file/folder name or a path to a file/folder, you must include it in double quotes (” “).

For example, to create a new folder with folder name Another Test using your script:

Script to add new file/folder

param([string]$Dir) New-Item -Path "$Dir" -ItemType "directory"

1 2	param([string]$Dir)   New-Item -Path "$Dir" -ItemType "directory"

You can use the following argument: .\newdir.ps1 -Dir "c:\Another Test".

We hope this helps. Feel free to reach out to us if you have any more queries.

Regards
Eren Schwarz
Hexnode UEM