Is %temp% correct in the Install Microsoft 365 Office Apps Scripted Action?

Hello, 

I was trying to find 365 App installation logs on a multi-session host, and could not find the WVDOfficeInstall directory. Should this line

<Logging Level="Standard" Path="%temp%\WVDOfficeInstall" />

be

<Logging Level="Standard" Path="$env:temp\WVDOfficeInstall" />

in the odtconfig.xml definition in the “Install Microsoft 365 Office Apps” Scripted Action? 

It's written to odtconfig.xml as "<Logging Level="Standard" Path="%temp%\WVDOfficeInstall" />".

# create a base config XML for ODT to use, this one has auto-update disabled
$ODTConfig = @"
<Configuration>
 <Add OfficeClientEdition="64" Channel="MonthlyEnterprise">
   <Product ID="O365ProPlusRetail">
     <Language ID="en-US" />
     <Language ID="MatchOS" />
     <ExcludeApp ID="Groove" />
     <ExcludeApp ID="Lync" />
     <ExcludeApp ID="OneDrive" />
     <ExcludeApp ID="Teams" />
   </Product>
 </Add>
 <RemoveMSI/>
 <Updates Enabled="FALSE"/>
 <Display Level="None" AcceptEULA="TRUE" />
 <Logging Level="Standard" Path="%temp%\WVDOfficeInstall" />
 <Property Name="FORCEAPPSHUTDOWN" Value="TRUE"/>
 <Property Name="SharedComputerLicensing" Value="1"/>
</Configuration>
"@ 

Thanks!

0

Comments (2 comments)

0
Avatar
Ben Sadler

HI Peter,

Thanks for raising this and apologies for the delay in responding.

If you are seeing an issue with using the script in Nerdio Manager, please raise a case with our team using this link - Submit a request – Nerdio Help Center

Based on what you are saying, you shouldn't need to change the logging location. Scripted actions in Nerdio are executed in the System context on the VM, so the %temp% directory is a device wide location, whereas a user's own %temp% is scoped to their profile. This means the log folder is written to C:\Windows\Temp\WVDOfficeInstall rather than anywhere under a user's AppData path, which is likely why you weren't finding it.

Thanks!

Ben Sadler, Team Lead (EMEA) | Customer Support

0
Avatar
Peter Yasuda

Hi Ben, 

Thanks, but my question was more about the use of %temp% vs. $env:Temp in the odtconfig.xml, since setup.exe is being run by PowerShell: 

Start-Process -filepath "$env:windir\Temp\odt_sa\raw\setup.exe" -ArgumentList "/configure $env:windir\Temp\odt_sa\raw\odtconfig.xml" -Wait

I don't know whether setup.exe will natively use cmd shell variables rather PowerShell variables; I don't know where the variable expansion happens. I do know C:\Windows\Temp\WVDOfficeInstall does not exist. 

I can run both versions on a test machine when I have time. I'll report back here and maybe open a support request, depending on the result. 

Thanks!

 

Please sign in to leave a comment.