Windows 10: How to include system var in MSI log path

Hi,I need to create a GPO to update 50 computers and, to keep a log of in case something goes wrong I need to create a log for all the computers instalation.Bellow is the line I was trying:/VERYSILENT /SUPRESSMSGBOXES /LANGUADE="Português" /LOG=\\srvdi\Temp\__install\%COMPUTERNAME%.logBut the file created gets the name: %COMPUTERNAME%.logIs there anyway to name the file using the computer name?TIA

:)

 

MSI BUG in Windows 10?: PATH env var not updated by MSI after s/w install finishes until user log out/in (or reboot).

Done:

https://social.technet.microsoft.co...nishes-until-user-log?forum=win10itprogeneral

 

MSI BUG in Windows 10?: PATH env var not updated by MSI after s/w install finishes until user log out/in (or reboot).

I'm seeing different behavior when installing a software package under Windows 10 versus under previous versions of Windows. The software package is installed via a Windows Installer (MSI) package that is invoked by a setup.exe bootstrapper application
(which requires elevated privileges to run). The MSI package updates the %PATH% environment variable during installation (using the MSI Environment Table). The MSI package ONLY runs in the per-machine context so the environment variables for all users should
be updated by the installation. However, that is not the case on Windows 10 (until after the user logs out and back in or reboots the system).

MSI Behavior on Windows 8.1 or earlier:

After the MSI installation completes, the %PATH% environment variable is properly updated for all users. This is evidenced by opening a non-elevated command window and running "echo %PATH%" to display the value of the %PATH% environment variable. Running
the command in BOTH a non-elevated command window and in an elevated command window (context under which the MSI ran) shows the same results: in both cases the %PATH% environment variable was properly modified by the MSI installation.

MSI Behavior on Windows 10 (build 10240):

After the MSI installation completes, the %PATH% environment variable is only updated for the user who ran the installation (the elevated user credentials used to run setup.exe). If I open a non-elevated command window and examine the %PATH% environment variable
it was NOT updated. However, if I then log out and log back in (or just reboot), then the %PATH% environment variable is properly set for all users (as seen in both a non-elevated command window and in an elevated command window).

Is this a bug with MSI on Windows 10?

 

Add a path to $PATH?

what exactly do you need to decipher about that path line? also, what are you installing? perhaps i can help.