![]() Some EXE installers extract their files into the %temp% directory during installation.However, in some cases, you can extract the MSI package from the EXE installation file: ![]() Most often, developers distribute them as EXE files that are not suitable for deployment through GPO. Many apps are not provided in a form of MSI packages. You can use GPO WMI filters to filter Windows versions in Group Policies. ![]() If you still have computers running x86 versions of Windows, you will need to create a separate GPO for x86 and 圆4 computers. Anecdotal evidence from other HP users confirms my experience.Please note that there are x86 and 圆4 MS Teams versions. After two days, I can't find any combination of PS package install or re-registering which gets me a working copy. If you watch the desktop, a blank icon appears and several minutes later will correctly redraw. HPSA's background install takes about 1-2 min. Running under the User - Execution queue is not an option, because it requires UAC elevation. The installer requires a non-SYSTEM user context to properly provision everything. The user gets a blank desktop icon and a broken Start Menu link. ![]() When you run Setup or InstallHPSA in Post-Setup, user provisioning is broken. HP's download copy is actually several releases behind the Store's version. Version 9.14 is a UWP app, which is NOT available from Windows Store - but WU and Store will update it. This means you can't use a temp folder in C:\Windows\Setup, because it'll disappear before the background process finds it. Both Setup & InstallHPSA fork off a background process and immediately exit.Īny program which monitors exit status (SetupComplete) will think it's done, and move to the next app. HP devs suck, and they've made stupid design choices. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |