Since I haven't seen a response from you, I'm hoping it's because you've resolved your issue.  If so, could you please share what you found with the rest of the community?  If you haven't resolved the issue, please let us know how we can help. ... View more

What error(s) are you seeing?  Typically you'd see something in the App Portal website.log or the Windows event logs.  Have you applied any DLL hotfixes to the site?  Have you changed service accounts or passwords recently?  Usually when the service won't start, it's due to an incorrect account/password or because a DLL is out of sync between folders (many App Portal DLL's reside in multiple folders and must all be kept in sync). ... View more

You can configure App Portal to run over HTTPS on port 443.  You can also configure the App Portal Web Service (that gets installed on the SCCM site server) to run on a port other than 80 if you want.  You'll need to configure the web service port setting in App Portal to point to the same port it has been configured to run on within IIS on the site server.  Additionally, if the web service has been configured to only run over HTTPS instead of HTTP, you'll need to specify that as well.  You'll find these settings under Site Management > Settings > Web Site > General as Site Protocol, Web Service Protocol, and Web Service Port.  As for use of Port 80 for other things, that totally depends on the external systems you are connecting to.  In most cases, external systems (e.g. ServiceNow, AirWatch, etc.) tend to use HTTPS/443, but you'll need to figure that out, as we don't control that. ... View more

Wow!  Who knew?  Charlie, are you sure that's still active/reachable code?  If so, under what circumstances?  Given that this has potential communication and security implications, is this in the product documentation somewhere?  The implication is that you would have to have the appropriate ports open (both on network and personal firewalls), as well as making sure the App Portal service account has the necessary permissions on each managed client, in order to make such a call.  I would not expect those requirements to be met in most environments. ... View more

Can you provide a bit more context to your question?  Are you asking what the program rerun behavior setting on the SCCM advertisement does?  Are you asking what happens if someone clicks the "Reinstall" button next to a request on the My Requests page? To directly address your last question, App Portal does not directly interact with managed devices when deploying software.  App Portal only communicates with registered/configured deployment systems such as SCCM, Altiris/Symantec Client Management, AirWatch, MobileIron, and Jamf/Casper Suite to perform deployment operations.  It is those deployment systems that directly communicate with their managed devices to deploy software. ... View more

Additionally, you mentioned that it attempts reinstallation even if a newer version is already installed.  This leads me to believe that the application models in SCCM may not be properly configured for supersedence.  If the newer version of the application is configured to supersede the older version, then even if the device is left in the collection for the older deployment, SCCM should be smart enough to not attempt reinstallation of the older version when it finds the newer version already installed.  So while I agree with Charlie that you should enable collection cleanup on your catalog items in App Portal, you should also make sure that your packaging/deployment is done correctly in SCCM to avoid this scenario. Of course all of this is speculating that you are using application models.  If you're using packages, then you would need to look at the rerun behavior setting on the advertisement as well as potentially modifying the packaging to detect newer versions and not install.  Again, configuring collection cleanup on the catalog item in App Portal can help, but you should also be looking at root causes. ... View more

First, if you haven't done so already, please open a support case and submit an enhancement request for the ability to selectively display approval group names instead of individual approvers.  This comes up from time to time (for different reasons), but I don't believe any of my customers has officially requested a product enhancement to enable this.  While we can't guarantee any enhancement request will be implemented, the more customers that request it, the more likely it is to get implemented. Now, to answer your question, it is not possible to display the approval group name instead of the individual approver.  What I do in this situation is to use the App Portal service account as the approver for that step.  Alternatively, if you prefer, you could set up a separate user/mailbox with limited rights, specifically for that purpose.  Please note that during checkout, when the approval process is shown, it will display the approval group names with the individual approvers listed below each group, but when you view the list of approvals from My Requests, you'll see "Level 1"/"Level 2"/etc. with the individual approvers below each level (i.e. no mention of the approval group name). It sounds like you already have the automation piece figured out, but for others who may be interested in doing similar things, I've attached a custom web service with a few sample SOAP web methods that can be used to figure out current approval group name and approval level, as well as to approve/reject/cancel a request, or start a deployment (when using the Start via API option on the catalog item).  To use it, just remove the .txt extension (it is an .asmx file) and copy it to the <appportal>\web\ws folder on your App Portal server. ... View more

Perhaps this has been resolved now in App Portal 2019 R1 SP1? IOJ-2068842 Performance issues with My Apps - targeted devices link times out.   See the SP1 announcement here. ... View more

I know not everyone has a license/subscription for our Data Platform product, but Technopedia categorization is a much better starting point, in my opinion.  I've also seen customers categorize catalog items by publisher, by user population/business unit, and by type (which is where the Technopedia classifications come into play).  You can use any or all of these approaches simultaneously.  I've also seen customers just put everything into a generic "Software" category because their users tend to use the search function instead of navigating through the categories (though that could cause performance problems when loading the page if you have a large number of catalog items). Whatever approach you take, I generally recommend starting simple with not a lot of categories, and especially not too deep a hierarchy (i.e. not more than two levels deep).  Try to limit the number of catalog items in a category to about 100 or less.  Then after your users have been using App Portal for a while (and periodically thereafter), conduct some focus groups with a mix of people across the organization and see what they like/don't like.  This will help you get a feel for how your users think when they go looking for software, so you can adjust your category structure to help them. I know this isn't very prescriptive, but I hope it helps.   ... View more

Are you still attempting this remotely, or are you able to try it on the server now?  If you're doing this on the server with Internet Explorer, can you check Server Manager and make sure that IE Enhanced Security Mode is turned off?  Alternatively, have you tried a different browser (e.g. Chrome, or if already using Chrome, maybe try Edge or Firefox)? ... View more

It is fairly common for SMTP/IMAP servers to require SSL for incoming mail and not require it for outbound mail.  Are your App Portal inbound and outbound settings different in that regard?  Is it possible the mail server configuration changed to require SSL where App Portal wasn't configured to use SSL?  Another possibility might be if the mail server configuration was (either intentionally or inadvertently by way of a recent Microsoft update) changed to require TLS 1.2 or higher.  In such a case, even if the App Portal configuration is set to use SSL, the server itself may not be configured to use TLS 1.2 for all communication.  If that's the case, check out this post. ... View more

You can connect more than one App Portal site to the same SCCM environment.  This normally happens in situations where the customer wants both a DEV and PROD instance of App Portal, but there is only a production instance of SCCM.  In such a case, it's best practice to name catalog items such that they are unique between the two App Portal instances (e.g. "DEV - Adobe Reader XI" vs. "Adobe Reader XI").  This ensures there are no collection/deployment naming conflicts in SCCM.  Your situation sounds slightly different, so that naming approach may not work as well for you; however, one thing to note is that the collection/deployment naming is based on the catalog item title when the deployment is added to the catalog item.  If you later go back and change the title of the catalog item, it does not update the collection/deployment names.  So you could initially name your catalog items NEW-<SoftwareTitle> when creating the deployments, and then rename them without the "NEW-" in front. ... View more

I can't say that I've ever tried it remotely, but I would expect it should be possible. That browser page is simply doing an HTTP POST with base64-encoded data from the local file system. What you should see is that when you've selected a file to upload, the page normally changes very quickly to reflect the selected file information, but then it displays a "Continue" button. I will say that from time to time, even doing the upload locally on the server will just show a spinning gear after hitting the Continue button, because it tries to do a site refresh and reload http://servername/esd. In such situations, I usually just manually load http://server/esd/admin in the browser. If you see a *.license file in the Web\bin folder on your server, then the upload worked. ... View more

Did you already try an IISReset or simply recycling the application pool for the ESDWebService? I'm curious if it's something that keeps recurring after being resolved or if it's a one-off situation. ... View more