Yes! You can do the repackaging on Windows Sandbox as well. There you will have even fewer noise files/registries captured. The only downside is that on Sandbox you cannot create snapshots. But for most of the cases that is not a downside. Let us know if you have more questions. :)

Currently, it is not possible. You must log out and log in with a different tenant ID. But we can consider to implement such functionality. Could you let us know more about your current problem, here or by emailing us at [email protected] ? We're always looking for ways to improve the software. :)

Great suggestion. You may have some publicly available application in mind that has a licensed option?

Thank you! Have an amazing day! You already made ours amazing!💙

Thank you! We're glad it was useful. 🧙‍♂

Thank you! :)

You would need to package every time new applications version is released. By doing so enterprise is now in control of the application updates not the vendor. When packaging new version, use the same MSI UpgradeCode as for previous packaged version and configure upgrade table. It is easy with Master Packager. This will ensure that new MSI will upgrade previous packaged MSI versions.

Thank you! :)

The Master Packager Predefined action will not fix this problem. If you are concerned about it, the only solution is to copy the file with the advertised shortcut triggering MSI repair. Then it will persist during feature updates. You can even combine both solutions and then you will not have the repair before applying a feature update.

For 64bit OS, you will need the 64bit serviceui.exe. Here is good blog post that explains it: www.anoopcnair.com/use-serviceui-with-intune-to-bring-system-process-to-interactive-mode/ Let us know if you have more questions. :)

Because they are installed in Program Files folder and MSIX do not support that.

@@MasterPackager Can we use PSF to get around this?

Yes. Actually we suggest to wrap all packages in The PowerShell App Deployment Toolkit. We teach how package any application and wrap in PSADT in our courses: www.masterpackager.com/become-master-packager , but we are happy to answer specific questions here as well.

Done. Thanks for the feedback! 🧙‍♂

Please don’t.

Thank you, Paul! You made our day! 💙 Have a good one! 🙌

Hey, do you like your application packaging job. Will you suggest a fresher to start his career with application Packaging today?

@@anythinganywhereanytime1512 Sure :)

Could you please clerify the question? How do we get MyApp folder created in Master Packager software or how MyApp folder with content was created originally?

@@MasterPackager From the start you have it on your desktop. Then at 1:00 you drag it to target folder from desktop. As I figured later it is actually link to folder with executable.

If we would such functionality, what problem that would solve for you? :)

@@MasterPackager well i don't think it's a problem but it will simplify deploying packages even if in psdat mode no problem but if deployment is single file i believe it's better to hide important file like main file of powershell, for example.

C:\ProgramData\ in MSI is [CommonAppDataFolder]. Just drag and drop files in that folder from Master Packager Advanced Editor. Let us know if this helped? Cheers!

The directory structure is created in [CommonAppDataFolder]Microsoft\Windows\Start Menu\Programs and in explorer I can see the subfolder as well but it just doesn't show up in the start menu....

...OK, so it's a W10 'feature' :-s

Thank you! :)(

Done. Thanks for the feedback! 🧙‍♂

Thank you for your questions, we will be happy to answer each one. :) 1Q) PowerShell App Deployment Toolkit is free and your "Master Wrapper" is using it as a main Tool for creating those basic Packages? 1A) Yes, that is true. "Master Wrapper" is using PSADT to create application packages. 2Q) Why would someone pay you money (500$) for a free Tool? Because you have added a simple GUI? 2A) First of all the main "Master Wrapper" features are FREE. Under Pro license that costs 499 EUR includes all "Master Packager" suite with repackager and works forever you will find additional "Master Wrapper" pro features that are nice to have and will only increase convenience to create PSADT packages. 3Q) Because you have added a simple GUI? Everyone can edit the script (Deploy-Application.ps1) himself with also a free text editor (Notepad++) and get the job done in couple of a minutes. 3A) The problem what "Master Wrapper" solves is not editing the ps1. file. "Master Wrapper" helps IT administrators that are not so familiar with PowerShell script editing as others. Also, it is much faster to create a PSADT package for multiple installers than for experienced users using Notepad++. The last thing is that it removes the need to read documentation as by a simple press of a button you can enable functionality that otherwise, you would need to find in PSADT documentation. 4Q) You are also aware, that this Tool is: Copyright (C) 2017 - Sean Lillis, Dan Cunningham, Muhammad Mashwani, Aman Motazedian right? 4A) Yes, we are aware. If you would install "Master Packager" software, you would find the "Third Party Application.txt" file in our install directory that describes all the third-party software we have used to build "Master Packager" software including PSAppDeployToolkit license. We haven't violated any of the terms of the license that you can read in full in our “Third Party Application.txt" or here: github.com/PSAppDeployToolkit/PSAppDeployToolkit/blob/master/LICENSE Finally, Sean Lillis and Dan after finding out about "Master Wrapper" were really happy that you can see yourself here: twitter.com/seanels/status/1230458603976450048 Let us know if we answered all your questions and let us know if you have more questions and we will be happy to help. Cheers