To add to @kmantagi 's comment above, when new versions of Microsoft Endpoint Configuration Manager (ECM/SCCM/ConfigMgr) come out, it doesn't typically break the existing support AdminStudio has for previous versions of the product and will almost always continue to operate as before. Microsoft purposefully does not make huge changes to their support and APIs for creating a new Application or Package from build to build, so the functionality AdminStudio supports when it was developed will very likely continue to operate.  New functionality that gets added, however would not be supported until the next release of AdminStudio. This is why our Development team is constantly testing and evaluating new builds of ConfigMgr and verifying support for the latest public build when we release a new version of AdminStudio. I hope this adds a bit more information into our continued support for our AdminStudio customers that rely on ConfigMgr for application deployment. ... View more

Hi @juhanpad  Yes, as of the AdminStudio 2021 R2 release (coincidently, released today at the time of this post), you can both wrap Win32 applications into .intunewin wrappers and publish them to Intune. See more from the release notes here. ... View more

Hello @mloftis Click-to-Run refers to a technology that Microsoft has developed to deploy their Office suite to their end users. Click-to-Run utilizes both streaming and virtualization technology to accomplish this.  These methods don't work well for repackaging using AdminStudio or any other installation capturing solutions out there. For configuring and deploying Office, you should look at using Microsoft's own Office Deployment Tool in order to download and deploy the Click-to-Run version of Office deploy to your users.  In general, for any application with a complex installation process where the app's vendor has provided a tool to help with this complexity and support for enterprise-wide deployment, Flexera recommends you use those native tools that the vendor provides you.  For the 90%+ of enterprise apps that don't give you such a tool, you can turn to AdminStudio to help prepare these applications. ... View more

Hi @paul_mcevoy - Sorry for a delay. We're looking into this issue now and should have something to share soon.  ... View more

Hi @MoSpartan  Just to review: Software Repository requires the full path to the root of a folder share (UNC path is best) as well as a proxy account that everyone that connecting and using that associated Application Catalog will connect to and use to read to and write from the share.  As the help article indicates on the dialog box (also found online here) : IMPORTANT: The Proxy Account needs full control on the Software Repository Location folder at the directory level as well as at the sharing level. I would double-check that the proxy account you've provided is setup per those requirements for that location. ... View more

Hi @MoSpartan - There is not a direct installer-using-PowerShell to MSIX conversion process. Whatever the installation technology used, you need to first capture the end result of what that application's installer is doing to the machine. From here, you can create a new MSIX package that can replicate that end result. As Microsoft details in their overview for MSIX , applications packaged in MSIX run in app containers, which separate it's file system, registry, etc. off from other applications. As a result, the configuration of an application as an MSIX container will be different than traditionally installed software. AdminStudio can first capture the existing installer, watching and logging where all the files, registry keys, INI file changes, shortcuts, etc. are added to the capture machine using the Repackager.  You can review this capture, exclude anything that you no longer need (e.g. the legacy installer's uninstaller), and build that into an MSI package. You can then convert that directly into an MSIX package if you don't need further customizations and changes, or first make those changes in the included InstallShield Editor.  You can also make changes to the MSIX package itself after its created using the included MSIX Editor. Custom actions are not supported in MSIX itself and causes issue with the direct conversion from MSI to MSIX because the converter doesn't execute those actions. In this case, don't include the PowerShell script as a custom action in the MSI itself and then attempt to convert that MSI to MSIX. Rather, the PowerShell script should be run as part of the initial installer and captured as part of the overall installation using the Repackager initial capture time. The result of that capture, encapsulating what the PowerShell script's output actions along with the rest of that installer, is then included and built into a "pure" MSI without custom actions, allowing you to then converted it directly into MSIX. This applies to (many) vendor MSIs that utilize custom actions over performing work using the standard actions that MSI supports directly; repackage these first into a pure MSI before converting to MSIX. Hope this guidance helps! (Note: all links to product documentation point to the current release at the time of this posting) ... View more

Hello @asteele  Yes, Flexera Technical Support can assist you here. Please visit the Support option at the top of this page and submit a case online or give our team a call  and they can assist you further. ... View more

Hello @jesse_22 , thanks for your post. Here's a simple infrastructure diagram of AdminStudio Enterprise that includes external internet access out to Flexera for the Package Feed Module: The main AdminStudio Client Tools (#3 above) would be installed on the workstation of each IT admin performing packaging, testing, and publishing work with AdminStudio. Those workstations can connect directly to the SQL Server that hosts your Application Catalog database (#4) or via the AdminStudio Enterprise Server (#5) as a proxy (optional). The repackaging / run-time testing virtual machines (#1) can be hosted in Hyper-V or VMware vSphere for AdminStudio to automate spin up/down and snapshot/checkpoint setting packaging use. The File Server (#2) is likely already in place in your environment and stores the MSI/EXE/MSIX/Virtual packages and their associated files. Flexera has thousands of vendor application installer packages, install & uninstall command-line switches, and detection methods in hosted in our cloud-hosted Package Feed Module (#6); this is an optional subscription add-on for AdminStudio Professional and Enterprise.  You can choose to opt out of the Customer Experience Improvement Program in AdminStudio, which sends anonymized usage data back to Flexera to help understand what our customers use most/least to better determine what areas of the solution to improve next. AdminStudio connects to ConfigMgr (SCCM) over the multiple different ports that ConfigMgr itself utilizes; more info here. AdminStudio connects to Intune over Port 443. Intune itself requires any external applications connecting to it to be registered. More info on configuring that application registration can be found in the AdminStudio product help here. AdminStudio would require specific access to the Flexera cloud-hosted Package Feed Module system. It would require that network access to https://dl.csi7.secunia.com/ over Port 443 is accessible for both outbound and inbound traffic. Let us know if that helps.  (links to product documentation current as of this posting) ... View more