Although not widely known, you can store your Lite-Touch deployment log files centrally on a network share. This can come in handy when troubleshooting or auditing.
There are 2 types of logging available. The first is standard logging, which stores the logs on a network share at the end of a deployment. The second is dynamic logging which writes the log files in real-time to a network share throughout the deployment process.
To do this simply set the property as usual in the customsettings.ini or deployment database. In this example of standard logging, the log files are copied to a share at the end of the deployment process:
SLShare=\\Scriptimus-01\Logs$
This example shows dynamic logging, where the log files are copied in real-time to a share throughout the deployment process:
SLShareDynamicLogging=\\Scriptimus-01\Logs$
In most cases you can just create a folder called logs in the deployment share itself and target that location for your logs:
SLShareDynamicLogging=\\Scriptimus-01\DeploymentShare$\Logs
Hey there, I was wondering if you can help. I understand the central logs part, but each client creates a BDD.log file, how would you tell the difference on which computer the log file came from. Is there a way to create a folder with the computer’s computer name and drop the log files in there.
LikeLiked by 1 person
Try an evironment variable eg: SLShareDynamicLogging=\\Scriptimus-01\Logs$\%computername%
Let me know how you get on.
LikeLike
hmmm… interesting. I tried %OSDComputerName% and it created a folder with that name but also create a folder with the computer name. How would I use the %computername% as a variable within the customsetting.ini file? do I have to assign it to something?
LikeLike
OSDComputername should do the trick. How odd. I’ll test this myself when I get my lab back up and running.
LikeLike
I tried using the %OSDcomputername% variable and it didn’t work as expected… Using %computername% did work as expected…
LikeLike
I believe by default it will create a folder for each deployment. The folder will be named the computer name of the machine being deployed.
LikeLike