I don’t publish apps myself but I do have a PowerShell script that runs PowerShell to launch my .msc file. 

This is directly from my PowerShell script that launches it. There is a little more so I can run this with my elevated rights account but it’s just a matter of prompting for a username and password to run it. ($credentials).

You should be able to pass the credentials out of BT to populate the $credentials variable.

Start-Process powershell.exe -Credential $Credentials -ArgumentList ".\Utilities.msc"

Hi ​@rhagerm , Thank you for your response.

Could you please elaborate further? Where did you place the script?

The script can run from anywhere unless you are passing the credentials from BeyondInsight as a published app. Then it is usually placed on the RDS server.

I have my script in a temp folder. (c:\temp\toolbox)

This is the script in its entirety. I did rename our production domain name in the script to “yourdomain” for security reasons.

Again, you just need to change the two variables, $UserID and $Pwd to call your account from BeyondInsight.

The first Start-Process simply opens PowerShell with the account so I have it. This allows me to run things with my elevated rights account from my PC. The second Start-Process launches utilities.msc from a PS window and then closes the PS window.

I wrote this because we do not allow admin rights on endpoints to anyone. If you need admin rights, you get an elevated account in BeyondInsight and that account is in the admin group. Since it is a pain to type a complex password into the prompt every time without the aid of copy/paste, this is the solution I came up with. When mmc kicks off, I get a yes/no prompt and not a credentials prompt since the script runs as my elevated rights account.

$UserID = Read-Host "User name"

$Pwd = Read-Host "Enter elevated password" -AsSecureString

$UserID = 'yourdomain\'+$UserID

$Credentials = New-Object System.Management.Automation.PSCredential ($UserID, $Pwd)

Start-Process powershell.exe -Credential $Credentials

Start-Process powershell.exe -Credential $Credentials -ArgumentList "utilities.msc"

This is the result

To publish this to BeyondInsight, you will need to follow the documentation to publish it on the RDS server, use AutoIT most likely to get it to launch, etc. As I mentioned in the previous post, we don’t have on-premises RDS servers that I can use to publish apps. This simply runs from my laptop and works really well. It also solves your problem of how do I publish a .msc file.