Hi,
I am trying to get my logs to write to a ConfigMgr client folder. I have a subdirectory created specifically for this and the path is either:
C:\Windows\SysWow64\CCM\Logs\Packages; or
C:\Windows\System32\CCM\Logs\Packages
When I create a program and deploy the MSI how do I go input the log file path in the commandline? I cannot use the /lv C:\Windows etc as the path may not exist (obviously between x64 and x86 machines).
I am hoping that I don't have to create some sort of script to wrap the installer with logic in that.
If it is any help, the script will execute from a subfolder of either C:\Windows\SysWow64\CCM\Cache or C:\Windows\System32\CCM\Cache
Cheers.
Log File Location
0 Comments
[ + ] View comments
Answers
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.
don't worry about that. use c:\windows\system32\...
since sccm client is 32bits, windows 7 will redirect the log file under syswow64 for you.
Syntax for the msiexec.exe command line is picky. Always test first without /q and be sure it works before you test with your distribution tool. Be sure to use "%SystemRoot%\[whatever]".
For help with syntax.
http://msdn.microsoft.com/en-us/library/windows/desktop/aa370905(v=VS.85).aspx
When distributing apps with your distribution tool, keep in mind that the System account (assuming that is what you are using) is not the same as a regular user account and can't be accessed the same way. For example, the System account does not have an active desktop so you can't display a dialogue to it.
Is this for all installs?
If so, just set up MSI logging on the machines (HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Installer\Logging) and SCCM will write the logs to the 'C:\windows\temp' folder.
The 'Logs' folder is for use by the SCCM client. You have no control over the location. For installations, use the '/L' argument.I cannot use the /lv C:\Windows etc as the path may not exist Use %SystemRoot%\[whatever] if you want to use the Windows folder. I would think most people use %TEMP%, though.
You will have separate MSIs and therefore separate packages for x64 versus x86 clients, no?
Please log in to comment