Hello @shayn_parker - Thanks for the post. Unfortunately, this is a known issue with the OS Snapshot Wizards that of which our Development team is aware; we're tracking it under Issues IOJ-1831138 and IOJ-2209296. This issue is planned to be addressed in a future release of AdminStudio. For now, may I ask for what you are looking to use the OS Snapshot Wizard? If you're looking to performing application compatibility testing against Windows 10, we have built-in compatibility rules that don't require the creation of an OS Snapshot.  More info on this testing can be found here (AdminStudio 2021 is the current release as of this posting). Please let us know if there is a specific use case you're looking for AdminStudio for which to provide a solution and if there is any further guidance we can provide for you here. ... View more

Hi @eimhoff - You can move the shortcuts from the individual user's Desktop folder to the Public Desktop folder. I tried this with just creating a shortcut to the Windows Calculator, then I moved it to C:\Users\Public\Desktop folder. While logged into my machine as a standard user, when I choose to delete the shortcut it requires that the user have Administrative privileges' before they can complete the procedure: In the InstallShield Editor within AdminStudio, you can open your MSI project or MST (transform) project, go to (1) Shortcuts and then right-click (2) on the Shortcuts top root node in the middle frame, and under Show Folder choose (3) [ALLUSERSPROFILE]. Then, create a new directory called "Desktop" underneath that folder and put the shortcut there. like I've done with Notepad++: Add ALLUSERSPROFILE With the shortcut under this Public Desktop folder, when it gets installed it shows up under C:\Users\Public\Desktop: Moved Shortcut to Public Desktop and Result after Install This leads to the shortcut residing on the Public Desktop directory, which will block any user without admin privileges' to be able to delete it successfully. ... 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

Hello @HelenTA  -  To confirm, when you say you're migrating your "server", is this server the Microsoft SQL Server that is hosting your AdminStudio Application Catalog?  If so, there is information around how to change the default Application Catalog connection information so the Application Manager and the rest of AdminStudio connects to the correct server each time it's launched. Info around this configuration can be found for AdminStudio 2020 here: https://docs.flexera.com/adminstudio2020/Content/helplibrary/ASUPTaskDefaultApplicationCatalog.htm If you need further help on this,  you may reply to this thread. I also see in our system that our Tech Support is reaching out now to assist you. They'll be able to assist you further as well. ... View more

@shashikiran has detailed the four licensing options AdminStudio provides you when you first install the product.  As mentioned, select the option that corresponds to your licensing model, with majority of customers would license AdminStudio using Method #1 - Activation with Activation Code (which is found in your order confirmation or by logging into our Product and License Center. More detail around  activation methods can be found in the AdminStudio product help, with the current version's info here: https://docs.flexera.com/adminstudio2020/Content/helplibrary/VerificationOverview.htm ... View more

The first application errors appears to be related to a character set that's not supported without enabling UTF-8 encoding on the MSI in the InstallShield Editor. Don’t build the MSI option in Repackager, only build the Editor (.ISM) project file Open that Editor project with the InstallShield Editor Go to: MEDIA > Releases Click on the release (likely Release1) Click on Build tab Select Build UTF-8 Database, change it to Yes The second error for the first application is likely related to this first error. There is a limit to how long the file path in MSIs can be, at 260 characters (see more info here); this appears to be related to the second application error message. The path should be modified, if possible, to a shorter length. ... View more

AdminStudio can convert suitable application installations in MSI and EXE format into MSIX, but MSIX is different enough from App-V that an App-V to MSIX conversion is not something that is supported.  If this application can be converted to App-V, however, than it is likely convertible to MSIX as well. As you likely know, Word 2003 is no longer officially supported by Microsoft. As this US-Cert alert states, there are no longer any security patches or other updates available for this software: https://us-cert.cisa.gov/ncas/alerts/TA14-069A-0  Be careful when it comes using unsupported and potentially vulnerable applications within your environment. Flexera has partnerships with several service provides and other organizations around the world that can help you with packaging complex applications and scenarios. You can search for partners that help with this field of Application Readiness here. Feel free to private message me your contact information if you'd like to be connected to some partners that can help. ... View more