Hi all,

I realize that there are some issues with capturing a thick image that's domain joined, but I am trying to see if there are suitable solutions for what I am trying to achieve.

I am making a thick image for deployment to over 200 desktops. The image is then deployed with multicast (which fast). Some of the software I am installing, in order to configure it correctly, requires it to be domain joined.

Thus, I have a base reference image (built using a separate TS), I have a deployment share and TS that builds the thick image and captures that and then a third deployment share actually deploys the thick image and does a few small things that don't like being cloned.

The issue I run into is that after deploying the OS, the TS isn't logging on automatically as local Administrator. Instead, on the Windows logon, it shows <DOMAIN>\Administrator. When I log on manually as .\Administrator, the TS picks up and finishes successfully.

So, ideally, there is some smart workaround that would make it possible for the TS to logon as .\Administrator instead of getting stuck trying to log on as DOMAIN\Administrator...

When I used to run sysprep manually (using my previous deployment technology), sysprep removed the machine from the domain and it just got rejoined using the unattend file. This seems to be happening, because the machines are joined to the domain with their new names.

I haven't verified it, but it seems as simple as there not being a correct domain name set in the registry key for autologons?

I know I could try the alternative of installing the software, capture the image and in the actual deployment attempt to configure it, but there are some many dependent pieces of software that I wouldn't really have the thick image I am after.

Thanks for any suggestions,

SA.

windows 8.1 with all updates. MDT 2013

Hi all,

   I am getting this error when it run Tattoo in state Restore. So i ran with /debugcapture and found

I didn't changed any ztitoo.wsf script. seems like it is failing line 177, I am not scripter, does anyone know why suddenly it start failing.

When i reimage Dell Venue it reimaged fine.

Any idea? suggestion???

orion

Background:

MDT2012 only for OSD.  Configuring Win7 Enterprise x86 for Reference Image creation with Apps installed.

Configuration is being done with a VMWare VM.

Problem:

I have an issue where the sequence hangs on a later Restart Computer task. Applications finish installing successfully according to the logs. I have no idea why it stops.

I have a couple restart computer tasks earlier in the sequence that all run fine. only after some applications are installed does the Restart Computer hang up.

If I force a restart at that point I get the "dirty environment found" error.  If I select to not start a new install my previous sequence picks up and continues where it should.

When hung up the computer is responsive as I am able to check the logs.  The SMSTS log says the reboot was successful, but it didnt actually happen.

Here is the last bit of the SMSTS.LOG file.

<![LOG[Successfully complete the action (Install Microsoft Forefront) with the exit win32 code 0]LOG]!><time="14:30:03.008+360" date="06-24-2014" component="TSManager" context="" type="1" thread="3892" file="instruction.cxx:3036">
<![LOG[Sending status message . . .]LOG]!><time="14:30:03.008+360" date="06-24-2014" component="TSManager" context="" type="1" thread="3892" file="utility.cxx:292">
<![LOG[Executing in non SMS standalone mode. Ignoring send a task execution status message request]LOG]!><time="14:30:03.008+360" date="06-24-2014" component="TSManager" context="" type="1" thread="3892" file="utility.cxx:302">
<![LOG[Set a global environment variable _SMSTSLastActionRetCode=0]LOG]!><time="14:30:03.008+360" date="06-24-2014" component="TSManager" context="" type="0" thread="3892" file="executionenv.cxx:668">
<![LOG[Set a global environment variable _SMSTSLastActionSucceeded=true]LOG]!><time="14:30:03.008+360" date="06-24-2014" component="TSManager" context="" type="0" thread="3892" file="executionenv.cxx:668">
<![LOG[Clear local default environment]LOG]!><time="14:30:03.008+360" date="06-24-2014" component="TSManager" context="" type="0" thread="3892" file="executionenv.cxx:807">
<![LOG[Updated security on object C:\_SMSTaskSequence.]LOG]!><time="14:30:03.039+360" date="06-24-2014" component="TSManager" context="" type="1" thread="3892" file="utils.cpp:829">
<![LOG[Set a global environment variable _SMSTSNextInstructionPointer=74]LOG]!><time="14:30:03.039+360" date="06-24-2014" component="TSManager" context="" type="0" thread="3892" file="executionenv.cxx:668">
<![LOG[Set a TS execution environment variable _SMSTSNextInstructionPointer=74]LOG]!><time="14:30:03.039+360" date="06-24-2014" component="TSManager" context="" type="0" thread="3892" file="executionenv.cxx:386">
<![LOG[Set a global environment variable _SMSTSInstructionStackString=43 62 71]LOG]!><time="14:30:03.039+360" date="06-24-2014" component="TSManager" context="" type="0" thread="3892" file="executionenv.cxx:668">
<![LOG[Set a TS execution environment variable _SMSTSInstructionStackString=43 62 71]LOG]!><time="14:30:03.039+360" date="06-24-2014" component="TSManager" context="" type="0" thread="3892" file="executionenv.cxx:414">
<![LOG[Save the current environment block]LOG]!><time="14:30:03.039+360" date="06-24-2014" component="TSManager" context="" type="0" thread="3892" file="executionenv.cxx:833">
<![LOG[Successfully save execution state and environment to local hard disk]LOG]!><time="14:30:03.102+360" date="06-24-2014" component="TSManager" context="" type="1" thread="3892" file="engine.cxx:255">
<![LOG[Start executing an instruciton. Instruction name: Restart computer. Instruction pointer: 74]LOG]!><time="14:30:03.102+360" date="06-24-2014" component="TSManager" context="" type="1" thread="3892" file="engine.cxx:117">
<![LOG[Set a global environment variable _SMSTSCurrentActionName=Restart computer]LOG]!><time="14:30:03.102+360" date="06-24-2014" component="TSManager" context="" type="0" thread="3892" file="executionenv.cxx:668">
<![LOG[Set a global environment variable _SMSTSNextInstructionPointer=74]LOG]!><time="14:30:03.102+360" date="06-24-2014" component="TSManager" context="" type="0" thread="3892" file="executionenv.cxx:668">
<![LOG[Set a local default variable SMSRebootMessage]LOG]!><time="14:30:03.117+360" date="06-24-2014" component="TSManager" context="" type="0" thread="3892" file="executionenv.cxx:700">
<![LOG[Set a local default variable SMSRebootTimeout]LOG]!><time="14:30:03.117+360" date="06-24-2014" component="TSManager" context="" type="0" thread="3892" file="executionenv.cxx:700">
<![LOG[Set a local default variable SMSRebootTarget]LOG]!><time="14:30:03.117+360" date="06-24-2014" component="TSManager" context="" type="0" thread="3892" file="executionenv.cxx:700">
<![LOG[Set a global environment variable _SMSTSLogPath=C:\Users\ADMINI~1\AppData\Local\Temp\SMSTSLog]LOG]!><time="14:30:03.117+360" date="06-24-2014" component="TSManager" context="" type="0" thread="3892" file="executionenv.cxx:668">
<![LOG[Expand a string: smsboot.exe /target:WinPE]LOG]!><time="14:30:03.117+360" date="06-24-2014" component="TSManager" context="" type="0" thread="3892" file="executionenv.cxx:782">
<![LOG[Expand a string: ]LOG]!><time="14:30:03.117+360" date="06-24-2014" component="TSManager" context="" type="0" thread="3892" file="executionenv.cxx:782">
<![LOG[Command line for extension .exe is "%1" %*]LOG]!><time="14:30:03.117+360" date="06-24-2014" component="TSManager" context="" type="0" thread="3892" file="commandline.cpp:229">
<![LOG[Set command line: smsboot.exe /target:WinPE]LOG]!><time="14:30:03.117+360" date="06-24-2014" component="TSManager" context="" type="0" thread="3892" file="commandline.cpp:707">
<![LOG[Start executing the command line: smsboot.exe /target:WinPE]LOG]!><time="14:30:03.117+360" date="06-24-2014" component="TSManager" context="" type="1" thread="3892" file="instruction.cxx:2928">
<![LOG[!--------------------------------------------------------------------------------------------!]LOG]!><time="14:30:03.117+360" date="06-24-2014" component="TSManager" context="" type="1" thread="3892" file="instruction.cxx:2957">
<![LOG[Expand a string: WinPEandFullOS]LOG]!><time="14:30:03.117+360" date="06-24-2014" component="TSManager" context="" type="0" thread="3892" file="executionenv.cxx:782">
<![LOG[Executing command line: smsboot.exe /target:WinPE]LOG]!><time="14:30:03.117+360" date="06-24-2014" component="TSManager" context="" type="1" thread="3892" file="commandline.cpp:805">
<![LOG[========================= [ smsboot.exe ] =========================]LOG]!><time="14:30:03.601+360" date="06-24-2014" component="Reboot" context="" type="1" thread="2260" file="rebootcomputer.cpp:184">
<![LOG[Command line: '"smsboot.exe" /target:WinPE']LOG]!><time="14:30:03.601+360" date="06-24-2014" component="Reboot" context="" type="0" thread="2260" file="rebootcomputer.cpp:186">
<![LOG[SMSTSRebootDelay=60]LOG]!><time="14:30:03.601+360" date="06-24-2014" component="Reboot" context="" type="1" thread="2260" file="rebootcomputer.cpp:122">
<![LOG[SMSTSRebootMessage=Initiating system reboot]LOG]!><time="14:30:03.601+360" date="06-24-2014" component="Reboot" context="" type="1" thread="2260" file="rebootcomputer.cpp:122">
<![LOG[SMSTSRebootRequested=WinPE]LOG]!><time="14:30:03.601+360" date="06-24-2014" component="Reboot" context="" type="1" thread="2260" file="rebootcomputer.cpp:122">
<![LOG[Process completed with exit code 0]LOG]!><time="14:30:03.601+360" date="06-24-2014" component="TSManager" context="" type="1" thread="3892" file="commandline.cpp:1102">
<![LOG[!--------------------------------------------------------------------------------------------!]LOG]!><time="14:30:03.601+360" date="06-24-2014" component="TSManager" context="" type="1" thread="3892" file="instruction.cxx:3010">
<![LOG[Successfully complete the action (Restart computer) with the exit win32 code 0]LOG]!><time="14:30:03.601+360" date="06-24-2014" component="TSManager" context="" type="1" thread="3892" file="instruction.cxx:3036">
<![LOG[Sending status message . . .]LOG]!><time="14:30:03.601+360" date="06-24-2014" component="TSManager" context="" type="1" thread="3892" file="utility.cxx:292">
<![LOG[Executing in non SMS standalone mode. Ignoring send a task execution status message request]LOG]!><time="14:30:03.601+360" date="06-24-2014" component="TSManager" context="" type="1" thread="3892" file="utility.cxx:302">
<![LOG[Set a global environment variable _SMSTSLastActionRetCode=0]LOG]!><time="14:30:03.601+360" date="06-24-2014" component="TSManager" context="" type="0" thread="3892" file="executionenv.cxx:668">
<![LOG[Set a global environment variable _SMSTSLastActionSucceeded=true]LOG]!><time="14:30:03.601+360" date="06-24-2014" component="TSManager" context="" type="0" thread="3892" file="executionenv.cxx:668">
<![LOG[Clear local default environment]LOG]!><time="14:30:03.601+360" date="06-24-2014" component="TSManager" context="" type="0" thread="3892" file="executionenv.cxx:807">
<![LOG[Updated security on object C:\_SMSTaskSequence.]LOG]!><time="14:30:03.617+360" date="06-24-2014" component="TSManager" context="" type="1" thread="3892" file="utils.cpp:829">
<![LOG[Set a global environment variable _SMSTSNextInstructionPointer=75]LOG]!><time="14:30:03.617+360" date="06-24-2014" component="TSManager" context="" type="0" thread="3892" file="executionenv.cxx:668">
<![LOG[Set a TS execution environment variable _SMSTSNextInstructionPointer=75]LOG]!><time="14:30:03.617+360" date="06-24-2014" component="TSManager" context="" type="0" thread="3892" file="executionenv.cxx:386">
<![LOG[Set a global environment variable _SMSTSInstructionStackString=43 62 71]LOG]!><time="14:30:03.617+360" date="06-24-2014" component="TSManager" context="" type="0" thread="3892" file="executionenv.cxx:668">
<![LOG[Set a TS execution environment variable _SMSTSInstructionStackString=43 62 71]LOG]!><time="14:30:03.617+360" date="06-24-2014" component="TSManager" context="" type="0" thread="3892" file="executionenv.cxx:414">
<![LOG[Save the current environment block]LOG]!><time="14:30:03.617+360" date="06-24-2014" component="TSManager" context="" type="0" thread="3892" file="executionenv.cxx:833">
<![LOG[Successfully save execution state and environment to local hard disk]LOG]!><time="14:30:03.617+360" date="06-24-2014" component="TSManager" context="" type="1" thread="3892" file="engine.cxx:255">
<![LOG[Reboot to local harddisk]LOG]!><time="14:30:03.632+360" date="06-24-2014" component="TSManager" context="" type="1" thread="3892" file="engine.cxx:458">
<![LOG[Skipped RebootSystem()]LOG]!><time="14:30:03.632+360" date="06-24-2014" component="TSManager" context="" type="1" thread="3892" file="engine.cxx:587">
<![LOG[The action (Restart computer) initiated a reboot request]LOG]!><time="14:30:03.632+360" date="06-24-2014" component="TSManager" context="" type="1" thread="3892" file="engine.cxx:278">
<![LOG[Sending status message . . .]LOG]!><time="14:30:03.632+360" date="06-24-2014" component="TSManager" context="" type="1" thread="3892" file="utility.cxx:292">
<![LOG[Executing in non SMS standalone mode. Ignoring send a task execution status message request]LOG]!><time="14:30:03.632+360" date="06-24-2014" component="TSManager" context="" type="1" thread="3892" file="utility.cxx:302">
<![LOG[****************************************************************************]LOG]!><time="14:30:03.741+360" date="06-24-2014" component="TSManager" context="" type="1" thread="3892" file="tsmanager.cpp:768">
<![LOG[Execution engine result code: 2 (Success=0, Failure=1, RebootInitiated=2)]LOG]!><time="14:30:03.741+360" date="06-24-2014" component="TSManager" context="" type="1" thread="3892" file="tsmanager.cpp:770">
<![LOG[Process completed with exit code 2147945410]LOG]!><time="14:30:04.818+360" date="06-24-2014" component="TSMBootstrap" context="" type="1" thread="2768" file="commandline.cpp:1102">
<![LOG[Exiting with return code 0x80070BC2]LOG]!><time="14:30:04.865+360" date="06-24-2014" component="TSMBootstrap" context="" type="1" thread="2768" file="tsmbootstrap.cpp:1118">

Thanks!

Has anyone had issues with Sensor drivers not installing via MDT deployment?  Most importantly I need the Screen Orientation and HID Sensor collection.

We are deployinng Win 8.1 Ent via MDT to Dell tablets.  The sensor drivers are not installed with MDT deploy,  they do get installed when i install Windows manually.  I can see all the Sensor drives in the driverstore folder.  When i add try to add the HID Sensor collection manually i get an error (10) service cannot start. 

I also added them to the drivers task sequence to no avail.  No errors in the log files.  Any help would be appreciated.

Hi There,

I have created new WDS server and migrate all data from old server. It was working fine but recently I listed new task sequence and it didn't show up in task sequence under window deployment wizard. Than I log on to old server and created same task sequence on it and it show up.  IF I do any modification like rename or delete task sequence on old server it shows up when I boot to WDS on new server under task sequence. I came to know that Even though my WDS is on new server but still task sequence mapped to old server. How come this is possible?

I did change litetouch.wim file from new server but it giving me an error.

Please guide me how to resolve this issue.

MDT 2013, Windows 8.1 with all udpates in wim file.

Download all drivers and firmware http://www.microsoft.com/en-us/download/details.aspx?id=38826 to out of box. Update the Surface Ethernet Adapter in winpe. when i am booting i am getting following error, seems like its looking for "VEN_11AB&DEV_2B38&SUBSYS_045E0001&REV_00"

i search for hwdid, but didn't find anythings. Any help?

orion

HI,

I am using MDT 2010. How do i delete the existing SQL database that ins configiured in Deployment Share -> Advanced Configuration -> Database.

Because I am receiving the 

ZTI error opening SQL Connection: Login failed for user ''. The user is not associated with a trust SQL server connection

Regards,

Boopathi S

I have 3 Surface Pro 2's that all act the same. I have a docking station that I use to connect to the USB stick and the network. When I boot to the USB stick it connects to the server just fine. After I make my selections to install the Surface Pro image it starts the processing and gets to the MDT screen "Format and Partition Disk". Well it just sits there...forever if I let it. I have tried changing the MDT configuration to format the disk as GPT instead of MBR with no change in the result. I have imaged a couple of Surface Pro's (not Surface Pro 2's) without this error being displayed. I have changed the UEFI bios settings trying to find a combination that might let the disk get formatted, no luck. I can tell that the partitioning does work, just not the formatting of the disk.

If anyone has any ideas on how to diagnose this it would be greatly appreciated. I have looked at the log files but due to their size am unable to find anything of interest in there.

Hey all,

Iv been working with MDT/WDS for a while now and just trying to iron out a few outstanding issues.

We have a few PC Builds that do not use Add-In NIC's for a number of reasons (some motherboards will not boot the environment with the intel NIC) 

So I use the on-board, Once the TS gets into Windows I get an error: 

A connection to the deployment share (\\SHARE NAME) could not be made.
The following networking device did not have a driver installed.
PCI\VEN_8086&DEV_1503&SUBSYS_849C1043&REV_05

Retry: Try again to connect to the deployment share
Cancel: Give up, cancelling any in-progress task sequence

Now I have found the PNPDeviceID for the device and on http://catalog.update.microsoft.com/v7/site/Home.aspx and downloaded the correct .inf files. I have also tested this by installing the driver from these .inf files via device manager and it worked perfectly.

I imported the .inf files into out-of-box drivers

In the deployment share properties -> WinPE x64 Drivers and Patches this is set to All Drivers and Packages and Radio button -> Include all drivers from the selected profile.

In the Task Sequence:
Post Install -> Inject Drivers -> All Drivers and packages, with Radio Button -> Install all drivers from the selected profile.

I have updated the deployment share, completely regenerating the WIM, and also replaced the WIM in WDS as well.


Yet everytime I get to windows, Bang get that error again... Where am I going wrong? I can setup remote session as well for people if you want to have a look first hand.

Thanks

Hi!

I'm deploying Windows 7 32bit and most of my applications are installed by MDT, after the image is droped on the target machine. I found myself facing a very odd situation for which I couldn't find an explanation or solution:

- "sometimes" (and that it's a key word), when I dropped the same image using the same task sequence on the same type of hardware (lets 20-30 computers), on some machines all the applications will be installed, and on others I'll miss 1, 2 (usaully the same ones) or sometimes more and I'm not refering to the situation when the TS was interupted and it's aking you if you want to continue. The TS will finish without any error/warning messages but those apps will not be on all the machines. 

Did anyone had a problem like this? Can you help me please with any information/solutions regarding it?

Thank you!

We have an old server than was installed many years ago and the people who set it up at the time partitioned the drive into C and D partitions with the C drive too small to allow for future growth.  Now there is a large software package that requires a service pack and there isn't enough room to complete the service pack installation.  Not sure why the large application was installed on the small C drive to begin with.  It is very complicated and slow (days long on the slow server) to reinstall the application, so they want to avoid an uninstall and reinstall of the software.

So far, we have only used MDT 2012 to deploy Windows 7.

Is it possible to use MDT to capture both partitions of this Server 2003 machine, keeping the drivers, then do a deployment task that partitions the drives with a larger C partition and redeploys the captured image back to both new partitions?

Also since it is not being "cloned," but rather copied back to the same hardware, we do not want sysprep to be part of the process.  We want it to deploy back exactly the way it was and installed still joined to the domain with the same SID.

If so, what additional steps and command syntax are required to capture and redeploy a multipartition image?

Is there a better way to do this other than capturing and redeploying such as reliable software that can repartition a running Windows 2003 server?

Hi all,

I have a Windows 7 Enterprise edition (fully update Windows and applications) I captured this with MDT 2013 everything works well also the deployment of the image to my client no problem.

Now I have Windows 8.1 full update Windows updates also the applications we use in our place.

But now, when I try to capture Windows 8.1 sysprep run well the image gets pushed to the MDT 2013 server. But when I deploy the same Windows 8.1 image to a client it looks like that the SID is still the same. Because the computer name is the old one and the client is not joined any domain and also the administrator account is disabled.

Is that an issue of Windows 8.1 and is there a workaround for this problem?

Thanks.

Karlo

Ok I have performed Media deployment via USB thumbdrive many times over the years, so I must be overlooking something this time. Here is the what is happening:

Performing a refresh via USB executing Litetouch.vbs from the deploy\scripts folder on the USB thumbdrive. Scanstate runs and saves the data using hardlinking.(works perfect)

Then the client reboots into WINPE and then when the deployment should pick backup I see the message"Please reinsert themedia (CD, DVD, or USB) needed to complete thedeployment." While the USB drive is still plugged in I hit ok on the missing media message screen and it does nothing.

If I hit F8 and check to see if the USB drive is present I find out it is not.

But If I simply reboot the client it succesfuly picks back up and completes the deployment. My Brootstrap.ini contains the following as required for USB media deployment:

Priority=Default

[Default]
SkipBDDWelcome=YES

So the question is why do I get the "Please reinsert themedia (CD, DVD, or USB) needed to complete thedeployment

freddie

I am trying to install OS Image onto hyperV VM....so far it was working fine...after 1 month I tried again and got this error...

anyone have any idea/solution... please advise.

Thanks!

I need to configure a piece of software as part of a task sequence to direct some of its files to a specific partition.  I have the ts creating 3 partitions and I'm specifying variables for each: DataDisk = 10GB, UsersDisk = 100GB, OSDisk = 100% remaining free space.

The 100GB partition is the one I need the software to use. In the "Custom Tasks" section of the ts "Dump MDT Variables" step dumps all MDT variables to a text file on the local machine so I can see at that time UsersDisk = D:\, DataDisk = C:\ and OSDisk = V:\, but after the deployment finishes UsersDisk = E:\.  Also in the "Custom Tasks" section I'm running the "Configure Data Igloo" to configure the program.  Is there a way to set UsersDisk = E:\ before I run the "Configure Data Igloo" step when there's also an internal DVD drive likely using E:\?

My task sequence is stopping after it auto logs in to the computer the first time after staterestore. Im not sure what's going on.

Found existing task sequence state information in C:\_SMSTaskSequence, will continue
Property LTIDirtyOS is now = FALSE
Creating startup folder item to run LiteTouch.wsf once the shell is loaded)
Shortcut "\LiteTouch.lnk" created. 

that iswhere my my bdd.log is sitting at right now

Windows Server 2012
MDT 2013
DART 8.1 (msiexec /a msdart81)

C:\Program files\Microsoft Dart\v8.1

MDOP 2014

Deployment Workbench->MDT Production->Advanced Configuration->Monitoring
When Click on DarT Remote Control it crashed with following error:

MMC has detected an error in a snapin and will unload it.

Object reference not set to an instance of an object.

Event ID 1000

Faulting application name: mmc.exe, version: 6.2.9200.16496, time stamp: 0x50ece2e8
Faulting module name: KERNELBASE.dll, version: 6.2.9200.16864, time stamp: 0x531d34d8
Exception code: 0xe0434352
Fault offset: 0x0000000000047b8c
Faulting process id: 0x19c
Faulting application start time: 0x01cf922209950bfd
Faulting application path: C:\Windows\system32\mmc.exe
Faulting module path: C:\Windows\system32\KERNELBASE.dll
Report Id: 74025f73-fe15-11e3-93f7-a01d48c72535
Faulting package full name:
Faulting package-relative application ID:

Event ID 1026
Application: mmc.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.Reflection.TargetInvocationException
Stack:
   at Microsoft.ManagementConsole.Internal.SnapInMessagePumpProxy.OnThreadException(Object sender, ThreadExceptionEventArgs e)
   at System.Windows.Forms.Application.ThreadContext.OnThreadException(Exception t)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
   at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG& msg)
   at System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(IntPtr dwComponentID, Int32 reason, Int32 pvLoopData)
   at System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context)
   at System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context)
   at Microsoft.ManagementConsole.Internal.SnapInMessagePumpProxy.Microsoft.ManagementConsole.Internal.ISnapInMessagePumpProxy.Run()
   at Microsoft.ManagementConsole.Executive.SnapInThread.OnThreadStart()
   at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
   at System.Threading.ThreadHelper.ThreadStart()