Microsoft Security | Intune | Configuration Manager | Other
Other Configuration Manager-related features and issues
Since the install wrapper was an Application, I set it run as a 32-bit process and it installed.
Skip
Cannot install Store app in OSD
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(278.4, 54%, 36%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EBJ%3C/text%3E%3C/svg%3E)
Benninghouse, John D - DOT
115
Reputation points
I am trying to install the RSA Authenticator app (v6.2.6) in an OSD task sequence but it will not install.
I have tried an application, package with no program, and copying the files msix and dependencies locally and then running a Powershell command to install.
All methods complete successfully but the app is not present and does not show up in the list of Installed Apps despite C:\Program Files\WindowsApps being populated with 3 folders.
When using dism, we copy the files to C:\temp\RSAC and the command is:
dism.exe /Online /Add-ProvisionedAppxPackage /PackagePath:C:\Temp\RSAC\4dcf280be1f6444ea7d81e4ae1d49c69.msixbundle /DependencyPackagePath:C:\Temp\RSAC\Microsoft.NET.Native.Framework.2.2_2.2.29512.0_x64__8wekyb3d8bbwe.appx /DependencyPackagePath:C:\Temp\RSAC\Microsoft.NET.Native.Runtime.2.2_2.2.28604.0_x64__8wekyb3d8bbwe.appx /DependencyPackagePath:C:\Temp\RSAC\Microsoft.VCLibs.140.00_14.0.33519.0_x64__8wekyb3d8bbwe.appx /LicensePath:C:\Temp\RSAC\4dcf280be1f6444ea7d81e4ae1d49c69_License1.xml
With Powershell:
Add-AppxProvisionedPackage -online -PackagePath "C:\temp\RSAC\4dcf280be1f6444ea7d81e4ae1d49c69.msixbundle" -DependencyPackagePath "C:\Temp\RSAC\Microsoft.NET.Native.Framework.2.2_2.2.29512.0_x64__8wekyb3d8bbwe.appx","C:\Temp\RSAC\Microsoft.NET.Native.Runtime.2.2_2.2.28604.0_x64__8wekyb3d8bbwe.appx","C:\Temp\RSAC\Microsoft.VCLibs.140.00_14.0.33519.0_x64__8wekyb3d8bbwe.appx" -LicensePath "C:\Temp\RSAC\4dcf280be1f6444ea7d81e4ae1d49c69_License1.xml"
If I run the installer with a wrapper manually outside of OSD it works fine; running the commands above from a prompt manually works fine. It only has a problem during OSD. Running it manually as the local system account is fine.
Anyone have any idea where to go next? Perhaps try running the step as a different account with local admin rights?
Skip
Microsoft Security | Intune | Configuration Manager | Other
2 answers
Sort by: Most helpful
-
-
Q&A Assist2025-12-23T14:34:11.64+00:00 AI generated content. This question contains an answer created with AI from Q&A Assist. Learn moreIt appears that you are encountering issues with installing the RSA Authenticator app during the Operating System Deployment (OSD) task sequence. Here are a few considerations and troubleshooting steps that might help:
- Application Type: Ensure that the RSA Authenticator app is compatible with the OSD installation requirements. According to the documentation, applications must have a deployment type of Windows Installer or Script installer. MSIX applications may not be supported in certain scenarios during OSD.
- Silent Installation: The application must run silently or in an unattended mode. If the installation process requires user interaction or does not support silent installation, it may fail during the OSD.
- Restart Behavior: Ensure that the application does not initiate a restart on its own. It should only request a restart using the standard restart code (3010) to allow the task sequence to handle the restart appropriately.
- Task Sequence Configuration: Review the task sequence configuration to ensure that it is set up correctly to install applications. If the task sequence is not configured to continue on error, any failure during the installation could cause the entire task sequence to fail.
- Logs Review: Check the logs generated during the OSD process, particularly the SMSTS.log, for any errors or warnings that could provide more insight into why the installation is failing.
- Testing Outside OSD: Since you mentioned that the installation works fine when run manually, consider testing the installation within a controlled environment that mimics the OSD conditions to identify any discrepancies.
- Local System Account: If you are running the installation as the local system account and it works, ensure that the task sequence is indeed executing under the Local System context and that there are no permission issues affecting the installation.
If the issue persists, you may want to explore using a different method for deploying the application or consult with Microsoft support for further assistance specific to your environment.
References: