Inbox Scripts

[nkasco]

It would be great to ship with a base set of tools most users would find helpful. These can be new things or tools from the community that are listed on the PS Gallery.

These can be added to the Scripts XML and Categories XML as needed.

[belibug]

This sounds like something I can help with in my spare time. Do you have any sample list of tools that would need to be added.

[nkasco]

This sounds like something I can help with in my spare time. Do you have any sample list of tools that would need to be added.

Totally up to you, things that would be helpful for IT Admins from Help Desk up to more engineering type roles. Ideally you'd want them to accept a -Machine parameter so that the UI can pass input without having to prompt the user again

[belibug]

Hi nkasco, I was able to build the project and test the application. Amazing framework, I see lot of potential and use case for this tool.

Quick question though,
How do you pass machine name parameter to PowerShell script? This is what I have tried.

1. Place script in script folder (right next to sample script that you have kept)
2. Append scripts.xml with new script info.
   It does show up in the tool and works as expected.

But how do I pass the machine information (right top of the tool) info to PowerShell script. I logged all the args that are being sent to PowerShell script and it was empty, so its not sending that info at all?

[belibug]

Hi nkasco, I was able to build the project and test the application. Amazing framework, I see lot of potential and use case for this tool.

Quick question though, How do you pass machine name parameter to PowerShell script? This is what I have tried.

1. Place script in script folder (right next to sample script that you have kept)
2. Append scripts.xml with new script info.
   It does show up in the tool and works as expected.

But how do I pass the machine information (right top of the tool) info to PowerShell script. I logged all the args that are being sent to PowerShell script and it was empty, so its not sending that info at all?

scratch that, I was able to get the machine info after entering the details again.

For any future reference, its just passed as unnamed parameter. Its comma separated single argument when its multi device entry.

[nkasco]

Hi nkasco, I was able to build the project and test the application. Amazing framework, I see lot of potential and use case for this tool.
Quick question though, How do you pass machine name parameter to PowerShell script? This is what I have tried.

1. Place script in script folder (right next to sample script that you have kept)
2. Append scripts.xml with new script info.
   It does show up in the tool and works as expected.

But how do I pass the machine information (right top of the tool) info to PowerShell script. I logged all the args that are being sent to PowerShell script and it was empty, so its not sending that info at all?

scratch that, I was able to get the machine info after entering the details again.

For any future reference, its just passed as unnamed parameter. Its comma separated single argument when its multi device entry.

Yep exactly, it doesn't have to be complex to be functional :)