While installing visio P2 and project P3 we are facing issue with block execution upon office apps

The Toolkit General Discussion
1

script using: PSADT 4.1.7
Deployment: Intune(userbased required/available mode deployment)
issue short description: block execution issue upon language specific devices.

Detailed description:
We have deployed Visio P2 and Project P3 applications through Intune using a PSADT 4.1.7 deployment script.

During testing on our VDI environment, the BlockExecution functionality works as expected. When a user attempts to open any Office application while the installation is in progress, a popup message is displayed stating that Office applications cannot be launched during installation and are currently blocked.

However, when testing the same package on language-specific devices (France, Germany, Greece, Japan, Brazil, etc.), we are not receiving the expected localized BlockExecution popup. Although users are still unable to open Office applications during the installation (which is the expected behavior), the popup message displayed is different. Instead of the expected BlockExecution notification, users receive an error message similar to the one shown below.

Could you please help us understand why the expected BlockExecution popup is not appearing on the language devices and why a different error message is being displayed?

adding the psadt script line used for block-execution:
Show-ADTInstallationProgress -StatusMessage 'Installing Microsoft Project Professional P3 Click-to-Run. You will not be able to open any Office applications during this time. Please wait...' -WindowLocation 'BottomRight' -NotTopMost

Show-ADTInstallationWelcome -CloseProcesses @{ Name = 'excel' }, @{ Name = 'groove' }, @{ Name = 'onenote' }, @{ Name = 'infopath' }, @{ Name = 'outlook' }, @{ Name = 'msaccess' }, @{ Name = 'mspub' }, @{ Name = 'powerpnt' }, @{ Name = 'winword' }, @{ Name = 'WINPROJ' }, @{ Name = 'winproj' }, @{ Name = 'lync' }, @{ Name = 'communicator' } -AllowDefer -DeferTimes 3 -ForceCloseProcessesCountdown 7200 -DeferRunInterval (New-TimeSpan -Hours 2)
Show-ADTInstallationWelcome -CloseProcesses @{ Name = 'excel' }, @{ Name = 'groove' }, @{ Name = 'onenote' }, @{ Name = 'infopath' }, @{ Name = 'outlook' }, @{ Name = 'msaccess' }, @{ Name = 'mspub' }, @{ Name = 'powerpnt' }, @{ Name = 'winword' }, @{ Name = 'WINPROJ' }, @{ Name = 'winproj' }, @{ Name = 'lync' }, @{ Name = 'communicator' } -BlockExecution

error we are getting:
Brazil device:

image
image835×223 5.96 KB

2

I'll let others comment on the use of PSADT in multi-language / VDI environments (I vaguely recollect there are a few issues to be aware of)
But, I am unsure why you have the -BlockExecution command on a second Show-ADTInstallationWelcome command, you can combine this in the 1st command so you have just a single line as follows:

Show-ADTInstallationWelcome -CloseProcesses @{ Name = 'excel' }, @{ Name = 'groove' }, @{ Name = 'onenote' }, @{ Name = 'infopath' }, @{ Name = 'outlook' }, @{ Name = 'msaccess' }, @{ Name = 'mspub' }, @{ Name = 'powerpnt' }, @{ Name = 'winword' }, @{ Name = 'WINPROJ' }, @{ Name = 'winproj' }, @{ Name = 'lync' }, @{ Name = 'communicator' } -AllowDefer -DeferTimes 3 -ForceCloseProcessesCountdown 7200 -DeferRunInterval (New-TimeSpan -Hours 2) -BlockExecution
3

Hi @Adrian_Scott,

This is Acknowledged.

Yes, we can keep the installation welcome and block execution on the same line. We tried the two-line method as a trial to overcome the block execution issue.

Regards,

Asha

Desktop Engineering – App Packaging

Team DL-DesktopEngineeringPackaging@aig.com