Hi Keith,
I actually commented out the following line in ZTIGather.wsf and tried again
with the same result.
oLogging.CreateEvent 41000, LogTypeInfo, "Processing the " &
oEnvironment.Item("Phase") & " phase.", oLogging.GetDiscoveryArray
In the BDD.LOG I see the following:
Connection succeeded to MicrosoftVolumeEncryption
There are no encrypted drives
Property IsBDE is now = False
From: [email protected] [mailto:[email protected]] On
Behalf Of Hedges, Dustin
Sent: Wednesday, November 6, 2013 4:53 PM
To: [email protected]
Subject: RE: [MDT-OSD] ZTIGather.wsf "Freezing"
I don't have either of those configured. Only thing I have configured is
SLShare for Copying Log Files.
From: [email protected]<mailto:[email protected]>
[mailto:[email protected]] On Behalf Of Keith Garner
Sent: Wednesday, November 6, 2013 4:31 PM
To: [email protected]<mailto:[email protected]>
Subject: RE: [MDT-OSD] ZTIGather.wsf "Freezing"
The very next step after isBDE is a CreateEvent call.
Are you posting events to a server using EventShare or EventService? What
happens when you remove the values?
From: [email protected]<mailto:[email protected]>
[mailto:[email protected]] On Behalf Of Hedges, Dustin
Sent: Wednesday, November 6, 2013 1:22 PM
To: [email protected]<mailto:[email protected]>
Subject: [MDT-OSD] ZTIGather.wsf "Freezing"
Ok, so this is a strange issue and I'm hoping I'm not the only one having this
issue.
Randomly (because I haven't figured out the root cause yet) I'll have systems
hang during the Gather phase on Getting Local Computer Information: BitLocker.
When manually executing ZTIGather.wsf /debug:true during the Task Sequence, I
can see that the property IsBDE is set to False, however the ZTIGather.wsf
script won't proceed with any other checks. It just hangs there indefinitely.
The really strange part of this, is that during my Task Sequence ZTIGather gets
ran multiple times. In some instances, the first call to ZTIGather will cause
it to hang, in other causes is will process the first couple of ZTIGather calls
but fail later on in the Task Sequence.
I've also experienced this with various types of hardware and different
Operating Systems. In addition, I've seen this in SCCM 2007 w/ MDT 2010 update
1, SCCM 2012 SP1 with MDT 2012 Update 1.
I'm not going crazy, it happened to a coworker of mine at a different site also.
Any help would be appreciated. I've exhausted Google/Bing.
-Dustin Hedges
