Any suggestions would be greatly appreciated. I find it hard to believe that our company is the first to try and do something of this nature, so there must be some solution out there. If the above is not possible, do I have any other options? The only other thing I can think of would be to make our Updater app a Desktop app that way I could use PowerShell to install/update the POS metro app, but I believe that Surface RT devicesĭon't support desktop apps (is that correct?), so it would drastically increase the price point for our clients, as they would have to buy Surface Pros instead of Surface RTs. Updater app and POS app into one single app, is it possible to have the app check for and download it's update from our servers, and then update itself? Basically we would really like our app to auto-update itself, rather than our clients having to manuallyĭownload and sideload the app on all of their devices every time there is an update, which is typically every 1 - 4 weeks. Is PowerShell.exe even installed on Surface RT devices? So I'm not sure how I would have the Updater app install/update the POS app. for me to spin up a new process to run the PowerShell.exe. It looks like it's not possible to run PowerShell in metro apps it doesn't support me referencing the assembly in my Windows 8.1 metro app, and doesn't include Just an update on things I've tried in my prototype metro app. Version of the POS app installed, and have the Updater App launch the POS App.Īny suggestions, ideas, or comments are appreciated. If the above is possible to do, another lesser concern is, is it possible to "hide" our POS App so that our clients cannot launch it directly? We want them to always have to go through the Updater App to ensure they always have the proper I was hoping to be able to run PowerShell code from my Metro app to use cmdlets like Add-AppxPackage, but it looks like this is not possible. The concept behind this seems pretty straightforward, but is this something that is technically supported by The other (ideal) option of course is to just have one metro app that checks and auto-updates itself. appx file from our servers and side-load it onto the device (of course the client device would need to have a sideloading If the correct version is not installed, it would download the proper. Is already installed, it would simply launch the POS App. The purpose of this app would be to check what version of the POS App is installed on the Windows tablet, and check which version of the POS App the client should have. We would sideload an Updater App to the client's tablet. We have come up with a strategy for deploying multiple versions of our metro app, but I wanted to check with the experts (you) to see if what we want to accomplish is technically possible. We can't do this from the Windows Store and would need to sideload our apps. Must correspond to their database version. The problem is, we will require having multiple versions of our Metro app in production the version of the app that the client uses We are looking at making a Metro app that acts as a light-weight POS app that clients can use to sell their products. As you would expect, the database schema for each of these versions is different, so each of these clients also use a different version of our client-side app. We do not force all of our clients to be on the same version of our software i.e. The problem is, if I remove the config profile thousands of machines will get the stupid data use policy popup, so neither are good solutions.The company I work for creates Point Of Sale (POS) software using Software As A Service (SAAS), so we host our clients' databases. I have to completely remove any changes to the plist or they cannot run autoupdate. I have played with different settings in the config profile to no avail. If you install from one account you cannot run it from another. Seems to need to be run on every user profile. Download the latest version of autoupdate and run it on each user account. I downloaded the latest standard installer yesterday and it produces the same issue when installed via Jamf Pro. Sudo chmod -R 775 /Library/Application\ Support/Microsoft/MAU2.0/Microsoft\ AutoUpdate.app Tried the following: sudo chown -R root:wheel /Library/Application\ Support/Microsoft/MAU2.0/Microsoft\ AutoUpdate.app Have tried permission repairs with Disk Utility. This is happening on every new install of office for the last couple of weeks. There is no config profile blocking permissions. Office installs via Jamf Pro, but when any account tries to run the Autoupdate they get a permissions error. Is anyone else seeing issues with MS Office Autoupdate on the latst couple versions of Big Sur? This is recent for us.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |