How to modify logging to our requirements

The Toolkit General Discussion
1

We are currently evaluating PSADT for our software delivery (at the moment we are using Client Automation by Broadcom) and we have an logging issue.

For the procedures (Install/Uninstall...), we can set a parameter ($rf) which returns the content of the logfile to our job output.

Job-Parameter-RF
Job-Parameter-RF616×543 11.9 KB

For further information see Broadcom documentation

The standard PS Script with logging looks like this:

param (
[Parameter(Mandatory=$true)][string]$logfile
)

Function LogWrite
{
Param ([string]$logstring)
$mydate = $((get-date).ToString("yyyy-MM-dd hh:mm:ss"))
$logging = $mydate + " " + $logstring

Add-content $Logfile -value $logging

}

$rf gets all content from $logfile an pipe it into the job output of our software delivery.

Is there a way to do this with PSADT?

2

I am not sure I understand.

  1. Currently you are using Client Automation to install software on clients.
  2. Client Automation uses a $LogFile parameter in the standard Installation script to set the location and name of the log file.
  3. When installation is complete, Client Automation gets the contents of the log file.

Are you asking if PSADT will take $LogFile as parameter when launching the installation?

3

I believe this is (yet another) rebranding of the Altiris product once owned by Symantec and now owned by $$Broadcom$$

While most users of PSADT (a PowerShell scripting and packaging tool) probably use Intune or SCCM (ConfigMgr / MECM), to deploy their PSADT wrapped application deployments, it should be possible to use Client Automation by Broadcom, but unfortunately from my quick web search I've not found any hits that mention both PSADT and Client Automation by Broadcom.

N.B. PSADT has it's own built in Logging which may solve some of your question, the guidance for this can be found here: