Logging All the Configuration Manager Task Sequence Variables

re: Logging All the Configuration Manager Task Sequence Variables

Michael Murgolo — Wed, 21 Sep 2011 14:28:09 GMT

PK, the oLogging object is initialized in ZTIUtility.vbs (a collection of utility classes used by most MDT scripts). As you can see the attached MDT-style script references this in the line "<script language="VBScript" src="ZTIUtility.vbs"/>". ZTIUtility.vbs must be in the same folder as the attached script for this to work.

re: Logging All the Configuration Manager Task Sequence Variables

PK — Wed, 21 Sep 2011 13:21:13 GMT

Seems there is a disconnect. Where are we initializing "oLogging" object before we can call "oLogging.CreateEntry". I can't see what can this object can possibly be and what is the ", LogTypeInfo" doing there. Someone has to revisit this article and write probably few more lines to make all these meaningful.

re: Logging All the Configuration Manager Task Sequence Variables

I'm 80% there — Mon, 08 Nov 2010 22:11:30 GMT

I realize that this is 2 years old, but this is exactly what I'm looking for (I think). I've downloaded the OutputTSVariable script and copied it to my Toolkit package (and updated my distribution point), but I don't know what do do now.

What do I do to my task sequence to execute this script?

Logging Configuration Manager Task Sequence Variables

Chris Nackers Blog — Sat, 05 Jun 2010 04:05:16 GMT

When troubleshooting TS’s or when you simply want to know what is all being used in the TS, it can be

re: Logging All the Configuration Manager Task Sequence Variables

Joachim — Thu, 17 Sep 2009 12:36:36 GMT

I tried to implement something very similair but in Powershell and got lost. Are you able to provide the same script snippet in Powershell?

Here is my first part to get the variables. I am able to create a list of variables but what is the syntax to get the values?

$TSEnv=New-Object -comobject Microsoft.SMS.TSEnvironment"

foreach ($TSVar in $TSEnv.GetVariables()

{

$TSVar #That's only the name!!

$TSVar._SMSLogPath # VALUE ?!????

}

Another issue is I want to set application variables. The problem is the same. I am not sure about the Syntax. In a VBScript

$TSVar("OSDComputerName") works. But what about Powershell?

$TSEnv("Variable")=xyz

$TSEnv.Variable=xvz or can I access the variables via the standard $env variable?

$env:Variable

Any suggestion would be nice.

Best Regards

Joachim

re: Logging All the Configuration Manager Task Sequence Variables

Dave — Thu, 16 Oct 2008 19:37:42 GMT

Hi,

I've tried putting this on a network share and calling from a task sequence, but it's not really working for me. It had a probem with this line "<script language="VBScript" src="ZTIUtility.vbs"/>" and even when removed, I couldn't find OutputTSVariables.log anywhere. I even tried outputting to a text file from the vbs, but it's always empty.

All I'm really looking for is a way in the task sequence to map a drive to the local DP. It shows up in smsts.log and I've found references to %SMSDP% but it doesn't work. Help?

Thanks,

Dave

re: Logging All the Configuration Manager Task Sequence Variables

DeploymentGuys — Thu, 09 Oct 2008 16:55:26 GMT

So apologies to all - credit to Frank Rojas for discovering this. The posted script had a typo - it was using a curly quote instead of straight quote and was probably when it was copied and pasted. Remember there is also a new and improved version in the second installment of this post.

BlogMS Weekly Articles Published - 25th August 2008 to 31st August 2008

BlogMS - Official Microsoft Team Blogs — Mon, 01 Sep 2008 13:56:47 GMT

183 Microsoft Team blogs searched, 87 blogs have new articles in the past 7 days. 205 new articles found

BlogMS Weekly Articles Published - 25th August 2008 to 31st August 2008

BlogMS - Official Microsoft Team Blogs — Mon, 01 Sep 2008 11:25:33 GMT

183 Microsoft Team blogs searched, 87 blogs have new articles in the past 7 days. 205 new articles found