Hi @stevemba - AdminStudio uses Microsoft SQL Server for its Application Catalog database. First introduced in the AdminStudio 2022 R2 release, AdminStudio now supports Azure SQL service as an additional option for those using Microsoft Azure cloud environments. At this time, AdminStudio does not natively support AWS RDS; it may work but if you want to set up an AdminStudio environment in AWS you need to stand up a Windows Server with SQL Server installed on it.  We had enough feedback from customers that Azure was the popular cloud provider for Windows-based infrastructure, so we started offering support there initially. Flexera is always open to customer feedback. Feel free to post support for the Application Catalog to support native AWS RDS in our Ideals portal for AdminStudio here.  If other users find this suggestion helpful they can vote on it and this gives us more indication that there's enough interest to devote time and resources to adding this further. ... View more

Hi @Angersma - Sorry for the delay in my reply. Just to confirm: You've registered a new app connection in Intune for AdminStudio to connect to via Microsoft Graph APIs and you've set up the connection in AdminStudio to connect to your Intune tenant account and you're having issues publishing Win 32 Apps to Intune. Do I have that summarized correctly? To review and to help others that view this post, there is the initial Knowledge Base article we released that covers the end-to-end setup of both Intune and AdminStudio. Within the Product Documentation we also now have help articles on setting up the Intune connection, the AdminStudio Distribution system connection to Intune, and publishing applications up to Intune for deployment all found linked from here (link points to the current version of AdminStudio at the time of this posting). I also wanted to confirm that you're aware that Intune requires that Win32 app to Intune be first wrapped into the .Intunewin wrapper format. Only then can they be imported (this is for EXE applications among other use cases). AdminStudio supports wrapping EXE and MSI packages to .Intunewin natively within the Application Manager; more info can be found here. Let us know if this information helps you or if you need additional assistance. ... View more

Hi @Swapnil1989 - Let me summarize and make sure I understand the dilemma: App version 1 stored files in the user's App Data\Local folder (aka %LOCALAPPDATA%) App version 2 stores its files under the Program Files(x86)\<App> When updating machine with App v1 installed with App v2, it installs the file back to the old %LOCALAPPDATA% location instead of the new Program Files(x86)\<App> Is this a correct summary?  Applications that do not need administrator rights will installed under the current user's %LOCALAPPDATA% folder, as that folder is available to be written to by the user at any time.  To write to Program Files (x86) (or the 64-bit version Program Files), it requires elevation of user privilege's during install, as those folders are protected. It sounds like App v1 didn't require administrative rights when it was installed, but App v2 either has changes that now requires administrative rights or were installed by a System account or in an already-elevated state. You can run the App v2 in an elevated state and it should installed in Program Files(x86). Let me know if that helps or if you have additional questions.  Thanks! ... View more

Hi @normanperez - The PFM_Automation script was our initial attempt to offer automation around the Package Feed Module when AdminStudio only supported one-off search and download of applications from the Package Feed within the Application Manager UI. However, after we received further interest from customers around this automation, starting with AdminStudio 2020 release, we added the Backlog (formerly Automation) tab within the Application Manager UI to perform all the functionality the PFM_Automation PowerShell script had handled (and now more!) This way, you can set it up and let AdminStudio run without needing to update and maintain the PowerShell script. Here's a blog post from our Product Management team on the Automation Backlog functionality when it was first added in AdminStudio 2020. More info around the Backlog tab in the current version of AdminStudio can be found here. The Application Manager would need to be running on the workstation\server that would be running the automation on a scheduled basis. ... View more

Hi @normanperez  There isn't a default Requirement that can be set to apply to every application as they are imported; this is because Requirements often differ across different applications so applying the same across isn't used often.  If the use case is to limit to what devices are deployed to for a given application based on OS, that would be done instead through the use of Query rules & Include \  Exclude collection rules within SCCM\ConfigMgr.  Let me know if there is another use case of which I'm not thinking; if there is a helpful use case for having a default value we can have it submitted to the AdminStudio Ideas page here. AdminStudio does not create Collection or Deployments when it published application to ConfigMgr. It only creates the Application (or Package) itself to "stage" it for later distribution. With AdminStudio Enterprise and it's PowerShell Cmd-lets, you could have a custom PowerShell script that first calls AdminStudio to perform the publishing and then makes a call using the ConfigMgr APIs available to create the Collections and Deployment objects in one go.  ... View more

Hi @normanperez - The naming convention for applications from the Package Feed Module can have spaces in the Product Name and/or Vendor Name. There is not a way today to remove spaces from the name as it appears in the Application Catalog and when it is published to the supported distribution systems that support spaces.  This could be something we add as a product enhancement. Feel free to post this in the AdminStudio Ideas page here. As for the Application Catalog group (folder) naming, if a group with a Vendor name already exists, any new applications imported will be imported into that existing group. If a Group with the Vendor name does not yet exist, it will be created for a new application for that Vendor. Let me know if you have further questions on this point. ... View more

Hi @sharmav - If you're speaking about the Download Manager within the Flexera Product and License Center, (PLC) you have several options to download the product if the Download Manager does not work for you. More information can be found in the PLC documentation here. ... View more

Hi @normanperez - Do you have an Application Catalog set up? AdminStudio downloads a local copy of the current Package Feed Module contents to your local Application Catalog to facilitate a faster search on Import from Package Feed option on the Home tab or when performing a match up with your list of applications on the Backlog tab. This list gets updated as searches are performed. When you say that the list of applications is not getting populated, are both of the above processes not working for you? You've whitelisted the correct URL and port for Package Feed Module to reach back to Flexera for the latest contents, so the allowed network connection should enable the data to be downloaded.  The first connection can take a minute or so to perform that first download of the list of application names but it should be a quick update after that has been done. Also, you said you have activated AdminStudio and the Package Feed Module; just confirming that you're aware that each have their own activation code and both need to be applied in order for the Package Feed Module to work properly.  More info on activating the Package Feed Module after AdminStudio can be found here. I would attempt to import a single package using the Import from Package Feed cited above and perform a search for a package (Chrome, Firefox, etc.) and confirm you're receiving a list of applications returned with that search. (Note all links above are for the current version of AdminStudio at the time of this posting.) ... View more

Hi  @ericdocherty  As you may know, the Product Code in each MSI is the primary identifier for a particular application.  Different versions/releases of the application would each have a unique MSI but they could share the same Product Code. If you create a new MSI in AdminStudio, either via Repackaging or using the included InstallShield Editor, the new MSI will have a new unique product code so it is differentiated from other applications, as it is not aware that the new MSI being created is the same application as an existing application, just a new installer. Within the InstallShield Editor, under the General Information view, under the General section you can see the Product Code is shown (see green arrow below):     You may choose to replace the randomly generated GUID with the product code from you previous MSI package (just copy the GUID from the previous MSI and paste into this field on the new MSI, then save the MSI from here).  This will "link" them as the same application as seen by the Windows Installer service on the end point machine. More info on changing the Product Code can be found in the the InstallShield Editor product documentation found here. The Product Code should not be mistaken for the Package Code found under the Summary Information Stream (see red arrow above), as the Package Code must be unique. All nonidentical MSIs must have different Package Codes. A good overview of MSI Product Codes are found in Microsoft's online product documentation found here. ... View more