Hi,

I am getting Error code 0X8007007B while activating the office 2010

Commands used from Administrator`s Command prompt :- cscript "C:\Program Files\Microsoft Office\Office14\ospp.vbs" /act

Shailendra Dev

We have Windows 7 deployment task that works this way:

We power on the machine, hit F12, select the  Lite Touch boot we want to use (x64 vs x86), then choose one of the deployment tasks.  We select the AD domain OU machine is to go into and enter the domain joining credentials. Then we choose optional applications and then select the local administrators.  After all these manual steps, we click next one more time and the deployment starts.

This is OK for most of our deployments because we often want to manually choose and customize many of these options.

However, we have a set of computers that will be repeatedly imaged the same way.

So, for these computers only, we want a more automated install where we can just hit F12 and maybe also choose the boot image and have the rest of it run unattended from that point on.

We need it to select the deployment task automatically, select the OU, enter domain join credentials and start the deployment automatically with no further user interaction needed.  There will be no optional apps or local admins required.

Can we do this so that we have the choice of automated or manual installation on a case by case manner without having to recreate a whole separate deployment with duplicate copies of drivers, apps etc.?   We do not want every computer that we PXE boot to MDT to start automatically deploying this task sequence.

Is it possible to enter the mac addresses into the customsettings.ini and enter something that says, "If one of these mac addresses from this group of mac address connects, then run this unattended tack sequence automatically?"

What about a specific PXE WDS boot image choice that sends the computer to the unattended task sequence when it is selected?
Another way?

Hi!

Since few manipulations in my console, I'm notable to controlmy computerswith the built-inMonitoringmenubutton"DaRT Remote Control". This error message appears: "MMC has detected an error in a snap-in and will unloadt it". After many verifications and tests by importing DART Tools v7, v8 or v801 x86 and x64, and because there's no findable answer on Internet, I ask you guys to help me if it's possible and if you know what to do. I'm actually on a Windows Server 2008 R2 x64 and with a MDT x64.

Here some additionnal informations about the trouble:

Unhandled Exception in Managed Code Snap-In / The system cannot find the file specified.

Exception type: System.ComponentModel.Win32Exception
at System.Diagnostics.Process.StartWithCreateProcess(ProcessStartInfo startInfo)
at Microsoft.BDD.Workbench.MonitoringGeneral.buttonDaRT_Click(Object sender, EventArgs e)
at System.Windows.Forms.Control.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ButtonBase.WndProc(Message& m)
at System.Windows.Forms.Button.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

Thank you very much for your help in advance! And please forgive my writing mistakes ;P

Hugo

Hi

I am using MDT 2013 to migrate Windows Xp to Windows 8.1, for this i followed the below Blog  to use USMT to migrate the user data from XP to 8.1

http://blogs.technet.com/b/mniehaus/archive/2014/01/09/migrating-from-windows-xp-to-windows-8-1-using-mdt-2013.aspx

USMT taking backup properly but its dosen`t restore the user data to its original Locations. suppose that we have 2-3 (C,D,E) local disk in XP machine , after the Windows 8.1 deployment in C- drive.Data of D drive also seen in E drive and data of E drive also seen in D drive after restoring the user state. How can we solve this?

Shailendra Dev

I have a task sequence that queries the computer model and then runs a BIOS update if the model matches.

If the BIOS is already up to date, the BIOS update application doesn't update the BIOS and the deployment continues. Everything is OK, but then we get a yellow summery screen at the end saying the BIOS update task had an error code.

Is there a way to filter the BIOS update task so that it only runs when the model matches AND the BIOS version is below a certain value?

Hello,

We've recently ordered a number of HP Proliant Gen8 Microservers and I've been tasked with getting a deployment solution in place for them.

Our standard Lite touch task installs a base image of 2008r2, installs required roles and features, patches from WSUS, encrypts and finally joins the domain.

On our production 2012 MDT server I was not presented with the option to configure Bitlocker when beginning the deployment, so I created a new 2013 MDT server in my test environment and the Bitlocker option appeared, however when I enable Bitlocker in the task the OS got stuck in a boot loop after the first reboot when the OS is installed.

I recorded the screen to catch which Blue Screen I was getting and it is the generic 0x7000000 blue screen with no info, just saying I should check my disk controller drivers/run chkdsk etc

 When I deploy without enabling bitlocker in the task sequence, I am able to manually encrypt the servers using either the GUI or manage-bde.

I've tested the Gen8 servers out of the box, as well as with all firmware updates and the situation remains.

Does anyone have any suggestions on what I can do to remedy this? I would prefer to have encryption built into the task sequence rather than chance human error when a number of these are going out.

Thanks

Andrew

Hello,

I'm am looking for a solution to make our MDT design as effective as possible(as small as posible).

The Situation:
The company has more then 15 different computers added to the MDT console for the automated installation of Windows 7. The installations are done in 2 different ways, 1 with a local USB key installation (with the deployment folder on the USB key) and the other installation is a network USB key installation (with the deployment folder on the server).
The local USB key exists for offices in parts of the world where the internet connection is poor.

The problem:
We have machines which can use the same driver for different kinds of hardware functions (LAN, WLAN, etc..)
If we add a new machine to the MDT and we don't check the box for "Import drivers even if they are duplicates of an existing driver" we will automatic use the driver which already exists in the deployment folder. If say half a year later we stop using an older machine which "may" have drivers that are being used for other machines and we delete the machine from MDT we shouldNOT check the box "Completely delete these items, even if there are copies in other folders". The problem is that this can also lead to a lot of unused drivers in the deployment folder also because we do not know exactly how many computers are using a certain driver.

At the moment we have another deployment share with for each machine its own drivers installed (so some drivers will be multiple times in the deployment folder) as you can guess this becomes really big.(deployment folder of more then 24 GB). The advantage of this is that we can delete a machine from the MDT list without having to worry if the drivers for that machine might be used by other machines. It is now just becoming to big in size(GB).

The Question:
Is there not an option within MDT that checks automatically if the drivers connected to a certain machine in MDT are being used by other machines? In this case we would check the box "Completely delete these items, even if there are copies in other folders" and MDT would not delete the drivers which are still used for the installations of other computers.

Thanks in advance.

Greets,

Arie

Hi @all,

i have a Lenovo T520 with 8 Cores, 256SSD for OS, 750GB SSD for Data

OS is Windows 8.1 x64

Hyper-V is installed

MDT 2012 Update 1 inkl. ADK and WAIK

i have created a Virtual Machine with 2CPUs 4GB Memory

Problem is, that the Installation of Windows 7 incl. Updates take half day (Capture)

what can i do, that the harddisk perfomance, network perfomance is higher?

HELP

Hi @all,

when my Hyper-V Client try to connect to the DeployRoot it fails

when i open CMD with F8 and make a ping i got <computername>.<domain> [ip-adress]

but my notebook isnt in a domain and the ip-address is also false

what can be the failure

when i ping the ip-adress direct it works fine...

help

Hi @all,

Actually i am Using Windows 8.1 Update as OS Host System

I use Hyper-V from Windows 8.1

I use MDT 2012 Update 1 on Windows 8.1 and MDT 2013 on a Hyper-V Machine.

Is it possible to Use the same folders by MDT 2012 and MDT 2013 cause i think i will have alle double when it doenst work?

Hope you understand my Question :)

Greetz from Germany

Hello,

Does Microsoft provide a tool to migrate local user account to domain account on Windows 7/8.1? Thanks

Hello I have had trouble getting the workstation to acually lock during the task sequence. I have tried many different ways including putting the command in the task sequence or even running it form a command file. It appears to run but just doesn't lock the machine.

Any ideas. Sorry about the code dump. Its a bit messy. BTW Z: drive is mapped

ssfully completed the action (Lock Workstation) with the exit win32 code 0

SCCM Deployment Technician

I'm setting up a Task Sequence in MDT 2013 to try out installing Windows 8.1 for the first time. We need to add .NET Framework 3.5 so I thought I'd add a Install Roles and Features step in the State Restore section to take care of that.

When I kick off the Task Sequence, I now see a new dialog that shows the Install Roles and Features for me to choose from. Didn't I just create a step for this? Why is it showing up asking me for my choices when I already specified what I needed? I thought maybe I messed up adding the step in my Task Sequence but after checking, it's still there enabled. Will .NET try and install twice now?  I have never seen the new dialog before.

After some testing I found that if I disabled the step I added, I no longer get the Install Roles and Features dialog at the beginning. Is this expected behavior or am I missing something?

Orange County District Attorney

Guys - how are you handling deleting/adding desktop shortcuts of 3rd party applications installed from your task sequence? In the past I've done my desktop modifications by calling a script in the startup (run once).

Is there a better way?

I tried deleting a adobe shortcut from public desktop using the /A:H switch in a cmd line step from my TS, but it still does not see the hidden folder for some reason..

thanks!

-PD

Environment:

2008r2 Standard, MDT 2012 Update 1, Windows PE3

Hello,

I'm attempting to reduce my Microserver deployment procedure by a few more steps.

Out of the Box I need to configure RAID, Enable TPM and License/add a user to ILO (For simplicity I'm just going to concentrate on RAID in this post).

From research I decided the best method to go about this was to use the Extra Directory method in Windows PE.

My Extra Directory is T:\Extra which contains Windows\System32\Drivers\HPSSTKIO?.sys & Scripting which contains HP Scripting Toolkit 9.6 & my three config files.

I placed a 'Configure RAID' command line in the PreInstall stage (testing) both before and after the Gather Script, however when the task sequence failed each time.

cmd /c "x:\scripting\hpssascripting.exe -i x:\scripting\gen8msraid.ini"

The strange thing is the command executes and actually configures RAID as you would expect, MDT is able to format the hard drive, install the OS, however it fails at Postinstall 'Restart Computer'  (smsts.log failure section below).

Any assistance would be appreciated.

Thanks

![LOG[!--------------------------------------------------------------------------------------------!]LOG]!><time="23:08:19.335+000" date="04-27-2014" component="TSManager" context="" type="1" thread="996" file="instruction.cxx:2957">
<![LOG[Expand a string: WinPEandFullOS]LOG]!><time="23:08:19.335+000" date="04-27-2014" component="TSManager" context="" type="0" thread="996" file="executionenv.cxx:782">
<![LOG[Executing command line: smsboot.exe /target:WinPE]LOG]!><time="23:08:19.335+000" date="04-27-2014" component="TSManager" context="" type="1" thread="996" file="commandline.cpp:805">
<![LOG[========================= [ smsboot.exe ] =========================]LOG]!><time="23:08:19.351+000" date="04-27-2014" component="Reboot" context="" type="1" thread="1276" file="rebootcomputer.cpp:184">
<![LOG[Command line: '"smsboot.exe" /target:WinPE']LOG]!><time="23:08:19.351+000" date="04-27-2014" component="Reboot" context="" type="0" thread="1276" file="rebootcomputer.cpp:186">
<![LOG[SMSTSRebootDelay=30]LOG]!><time="23:08:19.351+000" date="04-27-2014" component="Reboot" context="" type="1" thread="1276" file="rebootcomputer.cpp:122">
<![LOG[SMSTSRebootMessage=Initiating system reboot]LOG]!><time="23:08:19.351+000" date="04-27-2014" component="Reboot" context="" type="1" thread="1276" file="rebootcomputer.cpp:122">
<![LOG[SMSTSRebootRequested=WinPE]LOG]!><time="23:08:19.351+000" date="04-27-2014" component="Reboot" context="" type="1" thread="1276" file="rebootcomputer.cpp:122">
<![LOG[Process completed with exit code 0]LOG]!><time="23:08:19.351+000" date="04-27-2014" component="TSManager" context="" type="1" thread="996" file="commandline.cpp:1102">
<![LOG[!--------------------------------------------------------------------------------------------!]LOG]!><time="23:08:19.351+000" date="04-27-2014" component="TSManager" context="" type="1" thread="996" file="instruction.cxx:3010">
<![LOG[Successfully complete the action (Restart computer) with the exit win32 code 0]LOG]!><time="23:08:19.351+000" date="04-27-2014" component="TSManager" context="" type="1" thread="996" file="instruction.cxx:3036">
<![LOG[Sending status message . . .]LOG]!><time="23:08:19.351+000" date="04-27-2014" component="TSManager" context="" type="1" thread="996" file="utility.cxx:292">
<![LOG[Executing in non SMS standalone mode. Ignoring send a task execution status message request]LOG]!><time="23:08:19.351+000" date="04-27-2014" component="TSManager" context="" type="1" thread="996" file="utility.cxx:302">
<![LOG[Set a global environment variable _SMSTSLastActionRetCode=0]LOG]!><time="23:08:19.351+000" date="04-27-2014" component="TSManager" context="" type="0" thread="996" file="executionenv.cxx:668">
<![LOG[Set a global environment variable _SMSTSLastActionSucceeded=true]LOG]!><time="23:08:19.351+000" date="04-27-2014" component="TSManager" context="" type="0" thread="996" file="executionenv.cxx:668">
<![LOG[Expand a string: %_SMSTSMDataPath%\Logs]LOG]!><time="23:08:19.351+000" date="04-27-2014" component="TSManager" context="" type="0" thread="996" file="executionenv.cxx:782">
<![LOG[Deleting file without retry]LOG]!><time="23:08:19.351+000" date="04-27-2014" component="TSManager" context="" type="1" thread="996" file="ccmfile.cpp:1015">
<![LOG[Clear local default environment]LOG]!><time="23:08:19.366+000" date="04-27-2014" component="TSManager" context="" type="0" thread="996" file="executionenv.cxx:807">
<![LOG[User did not specify local data drive]LOG]!><time="23:08:19.366+000" date="04-27-2014" component="TSManager" context="" type="0" thread="996" file="utils.cpp:1008">
<![LOG[Volume C:\ has 996337958912 bytes of free space]LOG]!><time="23:08:19.366+000" date="04-27-2014" component="TSManager" context="" type="1" thread="996" file="utils.cpp:364">
<![LOG[Volume C:\ is not bootable]LOG]!><time="23:08:19.366+000" date="04-27-2014" component="TSManager" context="" type="1" thread="996" file="utils.cpp:370">
<![LOG[Volume W:\ has 476471296 bytes of free space]LOG]!><time="23:08:19.366+000" date="04-27-2014" component="TSManager" context="" type="1" thread="996" file="utils.cpp:364">
<![LOG[Volume W:\ is not bootable]LOG]!><time="23:08:19.366+000" date="04-27-2014" component="TSManager" context="" type="1" thread="996" file="utils.cpp:370">
<![LOG[Volume X:\ is not a fixed hard drive]LOG]!><time="23:08:19.366+000" date="04-27-2014" component="TSManager" context="" type="1" thread="996" file="utils.cpp:345">
<![LOG[Volume Z:\ is not a fixed hard drive]LOG]!><time="23:08:19.366+000" date="04-27-2014" component="TSManager" context="" type="1" thread="996" file="utils.cpp:345">
<![LOG[TSM root drive = ]LOG]!><time="23:08:19.366+000" date="04-27-2014" component="TSManager" context="" type="1" thread="996" file="utils.cpp:380">
<![LOG[We do not find an available volume to store the local data path]LOG]!><time="23:08:19.366+000" date="04-27-2014" component="TSManager" context="" type="1" thread="996" file="utils.cpp:1023">
<![LOG[Set a global environment variable _SMSTSNextInstructionPointer=49]LOG]!><time="23:08:19.366+000" date="04-27-2014" component="TSManager" context="" type="0" thread="996" file="executionenv.cxx:668">
<![LOG[Set a TS execution environment variable _SMSTSNextInstructionPointer=49]LOG]!><time="23:08:19.366+000" date="04-27-2014" component="TSManager" context="" type="0" thread="996" file="executionenv.cxx:386">
<![LOG[Set a global environment variable _SMSTSInstructionStackString=42]LOG]!><time="23:08:19.366+000" date="04-27-2014" component="TSManager" context="" type="0" thread="996" file="executionenv.cxx:668">
<![LOG[Set a TS execution environment variable _SMSTSInstructionStackString=42]LOG]!><time="23:08:19.366+000" date="04-27-2014" component="TSManager" context="" type="0" thread="996" file="executionenv.cxx:414">
<![LOG[Save the current environment block]LOG]!><time="23:08:19.366+000" date="04-27-2014" component="TSManager" context="" type="0" thread="996" file="executionenv.cxx:833">
<![LOG[pszPath[0] != L'\0', HRESULT=80070057 (c:\qfe\nts_sms_fre\sms\framework\core\ccmcore\path.cpp,58)]LOG]!><time="23:08:19.366+000" date="04-27-2014" component="TSManager" context="" type="0" thread="996" file="path.cpp:58">
<![LOG[Filesystem::Path::Add(sEnvPath, EnvDataFileName, sEnvPath), HRESULT=80070057 (e:\nts_sms_fre\sms\framework\tscore\environmentlib.cpp,639)]LOG]!><time="23:08:19.366+000" date="04-27-2014" component="TSManager" context="" type="0" thread="996" file="environmentlib.cpp:639">
<![LOG[Failed to save environment to  (80070057)]LOG]!><time="23:08:19.366+000" date="04-27-2014" component="TSManager" context="" type="2" thread="996" file="environmentlib.cpp:657">
<![LOG[TS::Environment::SharedEnvironment.saveEnvironment(szPath), HRESULT=80070057 (e:\nts_sms_fre\sms\client\tasksequence\executionengine\executionenv.cxx,842)]LOG]!><time="23:08:19.366+000" date="04-27-2014" component="TSManager" context="" type="0" thread="996" file="executionenv.cxx:842">
<![LOG[Failed to save the current environment block. This is usually caused by a problem with the program. Please check the Microsoft Knowledge Base to determine if this is a known issue or contact Microsoft Support Services for further assistance.
The parameter is incorrect. (Error: 80070057; Source: Windows)]LOG]!><time="23:08:19.366+000" date="04-27-2014" component="TSManager" context="" type="3" thread="996" file="executionenv.cxx:842">
<![LOG[SaveEnvironment(), HRESULT=80070057 (e:\nts_sms_fre\sms\client\tasksequence\executionengine\executionenv.cxx,420)]LOG]!><time="23:08:19.366+000" date="04-27-2014" component="TSManager" context="" type="0" thread="996" file="executionenv.cxx:420">
<![LOG[Failed to persist execution state. Error 0x(80070057)]LOG]!><time="23:08:19.366+000" date="04-27-2014" component="TSManager" context="" type="2" thread="996" file="executionenv.cxx:426">
<![LOG[Failed to save execution state and environment to local hard disk]LOG]!><time="23:08:19.366+000" date="04-27-2014" component="TSManager" context="" type="2" thread="996" file="engine.cxx:250">
<![LOG[Reboot to local harddisk]LOG]!><time="23:08:19.366+000" date="04-27-2014" component="TSManager" context="" type="1" thread="996" file="engine.cxx:458">
<![LOG[FALSE, HRESULT=80004005 (e:\nts_sms_fre\sms\client\tasksequence\executionengine\engine.cxx,584)]LOG]!><time="23:08:19.366+000" date="04-27-2014" component="TSManager" context="" type="0" thread="996" file="engine.cxx:584">
<![LOG[The task sequence execution engine can not reboot the machine because we failed to persist execution environment]LOG]!><time="23:08:19.366+000" date="04-27-2014" component="TSManager" context="" type="3" thread="996" file="engine.cxx:584">
<![LOG[CheckForRebootRequest(&bRebootInitiated), HRESULT=80004005 (e:\nts_sms_fre\sms\client\tasksequence\executionengine\engine.cxx,274)]LOG]!><time="23:08:19.366+000" date="04-27-2014" component="TSManager" context="" type="0" thread="996" file="engine.cxx:274">
<![LOG[Fatal error is returned in check for reboot request of the action (Restart computer).
Unspecified error (Error: 80004005; Source: Windows)]LOG]!><time="23:08:19.366+000" date="04-27-2014" component="TSManager" context="" type="3" thread="996" file="engine.cxx:274">
<![LOG[An error (0x80004005) is encountered in execution of the task sequence]LOG]!><time="23:08:19.366+000" date="04-27-2014" component="TSManager" context="" type="3" thread="996" file="engine.cxx:349">
<![LOG[Sending status message . . .]LOG]!><time="23:08:19.366+000" date="04-27-2014" component="TSManager" context="" type="1" thread="996" file="utility.cxx:292">
<![LOG[Executing in non SMS standalone mode. Ignoring send a task execution status message request]LOG]!><time="23:08:19.366+000" date="04-27-2014" component="TSManager" context="" type="1" thread="996" file="utility.cxx:302">
<![LOG[m_TSEngine.Execute(& m_eExecutionResult), HRESULT=80004005 (e:\nts_sms_fre\sms\client\tasksequence\tsmanager\tsmanager.cpp,763)]LOG]!><time="23:08:19.366+000" date="04-27-2014" component="TSManager" context="" type="0" thread="996" file="tsmanager.cpp:763">
<![LOG[Task Sequence Engine failed! Code: 80004005]LOG]!><time="23:08:19.382+000" date="04-27-2014" component="TSManager" context="" type="3" thread="996" file="tsmanager.cpp:763">
<![LOG[****************************************************************************]LOG]!><time="23:08:19.382+000" date="04-27-2014" component="TSManager" context="" type="1" thread="996" file="tsmanager.cpp:789">
<![LOG[Task sequence execution failed with error code 80004005]LOG]!><time="23:08:19.382+000" date="04-27-2014" component="TSManager" context="" type="3" thread="996" file="tsmanager.cpp:790">
<![LOG[Cleaning Up. Removing Authenticator]LOG]!><time="23:08:19.382+000" date="04-27-2014" component="TSManager" context="" type="1" thread="996" file="tsmanager.cpp:578">
<![LOG[!sVolumeID.empty(), HRESULT=80004005 (e:\nts_sms_fre\sms\framework\tscore\resolvesource.cpp,467)]LOG]!><time="23:08:19.382+000" date="04-27-2014" component="TSManager" context="" type="0" thread="996" file="resolvesource.cpp:467">
<![LOG[!sVolumeID.empty(), HRESULT=80004005 (e:\nts_sms_fre\sms\framework\tscore\resolvesource.cpp,467)]LOG]!><time="23:08:19.382+000" date="04-27-2014" component="TSManager" context="" type="0" thread="996" file="resolvesource.cpp:467">
<![LOG[!sTSMDataPath.empty(), HRESULT=80070002 (e:\nts_sms_fre\sms\framework\tscore\resolvesource.cpp,1395)]LOG]!><time="23:08:19.382+000" date="04-27-2014" component="TSManager" context="" type="0" thread="996" file="resolvesource.cpp:1395">
<![LOG[There is no TSM local data path being set]LOG]!><time="23:08:19.382+000" date="04-27-2014" component="TSManager" context="" type="1" thread="996" file="utils.cpp:1400">
<![LOG[Successfully unregistered Task Sequencing Environment COM Interface.]LOG]!><time="23:08:19.382+000" date="04-27-2014" component="TSManager" context="" type="1" thread="996" file="environmentlib.cpp:869">
<![LOG[Command line for extension .exe is "%1" %*]LOG]!><time="23:08:19.382+000" date="04-27-2014" component="TSManager" context="" type="0" thread="996" file="commandline.cpp:229">
<![LOG[Set command line: "X:\Deploy\Tools\X64\TsProgressUI.exe" /Unregister]LOG]!><time="23:08:19.382+000" date="04-27-2014" component="TSManager" context="" type="0" thread="996" file="commandline.cpp:707">
<![LOG[Executing command line: "X:\Deploy\Tools\X64\TsProgressUI.exe" /Unregister]LOG]!><time="23:08:19.382+000" date="04-27-2014" component="TSManager" context="" type="1" thread="996" file="commandline.cpp:805">
<![LOG[==========[ TsProgressUI started in process 1196 ]==========]LOG]!><time="23:08:19.398+000" date="04-27-2014" component="TsProgressUI" context="" type="1" thread="1388" file="winmain.cpp:327">
<![LOG[Command line: "X:\Deploy\Tools\X64\TsProgressUI.exe" /Unregister]LOG]!><time="23:08:19.398+000" date="04-27-2014" component="TsProgressUI" context="" type="0" thread="1388" file="winmain.cpp:330">
<![LOG[Unregistering COM classes]LOG]!><time="23:08:19.398+000" date="04-27-2014" component="TsProgressUI" context="" type="1" thread="1388" file="winmain.cpp:202">
<![LOG[Unregistering class objects]LOG]!><time="23:08:19.398+000" date="04-27-2014" component="TsProgressUI" context="" type="1" thread="1388" file="winmain.cpp:503">
<![LOG[Shutdown complete.]LOG]!><time="23:08:19.398+000" date="04-27-2014" component="TsProgressUI" context="" type="1" thread="1388" file="winmain.cpp:520">
<![LOG[Process completed with exit code 0]LOG]!><time="23:08:19.398+000" date="04-27-2014" component="TSManager" context="" type="1" thread="996" file="commandline.cpp:1102">
<![LOG[Successfully unregistered TS Progress UI.]LOG]!><time="23:08:19.398+000" date="04-27-2014" component="TSManager" context="" type="1" thread="996" file="utils.cpp:1963">
<![LOG[g_TSManager.Run(), HRESULT=80004005 (e:\nts_sms_fre\sms\client\tasksequence\tsmanager\tsmanager.cpp,657)]LOG]!><time="23:08:19.398+000" date="04-27-2014" component="TSManager" context="" type="0" thread="996" file="tsmanager.cpp:657">
<![LOG[Error Task Sequence Manager failed to execute task sequence. Code 0x80004005]LOG]!><time="23:08:19.398+000" date="04-27-2014" component="TSManager" context="" type="3" thread="996" file="tsmanager.cpp:689">
<![LOG[Sending error status message]LOG]!><time="23:08:19.398+000" date="04-27-2014" component="TSManager" context="" type="1" thread="996" file="tsmanager.cpp:690">
<![LOG[In non SMS staqndalone mode.Ignoring SendStatusMessage request]LOG]!><time="23:08:19.398+000" date="04-27-2014" component="TSManager" context="" type="1" thread="996" file="tsmanager.cpp:1541">
<![LOG[Finalizing logging from process 576]LOG]!><time="23:08:19.398+000" date="04-27-2014" component="TSManager" context="" type="1" thread="996" file="tslogging.cpp:1736">
<![LOG[Finalizing logs to root of first available drive]LOG]!><time="23:08:19.398+000" date="04-27-2014" component="TSManager" context="" type="1" thread="996" file="tslogging.cpp:1578">
<![LOG[LOGGING: Setting log directory to "C:\SMSTSLog".]LOG]!><time="23:08:19.398+000" date="04-27-2014" component="TSManager" context="" type="1" thread="996" file="tslogging.cpp:1803">
<![LOG[Process completed with exit code 2147500037]LOG]!><time="23:08:19.398+000" date="04-27-2014" component="TSMBootstrap" context="" type="1" thread="512" file="commandline.cpp:1102">
<![LOG[Exiting with return code 0x80004005]LOG]!><time="23:08:19.398+000" date="04-27-2014" component="TSMBootstrap" context="" type="1" thread="512" file="tsmbootstrap.cpp:1118">
<![LOG[==========[ TsProgressUI started in process 1884 ]==========]LOG]!><time="23:08:19.429+000" date="04-27-2014" component="TsProgressUI" context="" type="1" thread="464" file="winmain.cpp:327">
<![LOG[Command line: "X:\Deploy\Tools\X64\TSProgressUI.exe"  /Unregister]LOG]!><time="23:08:19.429+000" date="04-27-2014" component="TsProgressUI" context="" type="0" thread="464" file="winmain.cpp:330">
<![LOG[Unregistering COM classes]LOG]!><time="23:08:19.429+000" date="04-27-2014" component="TsProgressUI" context="" type="1" thread="464" file="winmain.cpp:202">
<![LOG[Unregistering class objects]LOG]!><time="23:08:19.429+000" date="04-27-2014" component="TsProgressUI" context="" type="1" thread="464" file="winmain.cpp:503">
<![LOG[Shutdown complete.]LOG]!><time="23:08:19.429+000" date="04-27-2014" component="TsProgressUI" context="" type="1" thread="464" file="winmain.cpp:520">

If I install MDT 2013 on a Windows 7 desktop or laptop and WDS is on a 2008 R2 server, will multicasting work or does the deployment share need to be on a server or even the same server as WDS?

If multicasting will work with the deployment share stored on a Windows 7 workstation, what additional steps are needed?

I tested an MDT 2013 installed on a Windows 7 laptop and it works.

So now I am trying to move it to a Server 2008 R2 server so we can put it into production and the same workstation crashes in Win PE with a generic IRL not equal error.

I installed the same ADK version 8.100.26629 and MDT 2013  6.2.5019.0 on the server along with the.net framework 4.5 and Windows Management Framework 3.0.  Both are showing the same PowerShell version 3 0 -1 -1

I updated the deployment share to point to the new paths and regenerated the boot image and copied it into WDS.

When I boot the laptop and try to run it from the server, it crashes in Win PE before the deployment task ever starts.

The same workstation still boots fine when I boot with the old boot image that points to the test laptop.  So it does not seem to be a problem with the laptop.  

Since I copied the entire deployment share over, I assume it must be using all the same drivers.

What could be causing this problem?

Hello. My environment is SCCM 2012 SP1 with MDT 2012 Update 1 integrated. We will be moving to R2 and MDT 2013 in the near future. I have a question about the summary page. I have built several custom pages for my deployments. I have noticed that one of the pages display it's selected value on the summary screen but the other two do not. For example, I have a custom page that asked the builder to pick an application suite. When the builder gets to the summary page, the friendly display name for the application suite and their selected value is present. I have another page that asks for the location of the machine. When the builder gets to the summary pages, neither the friendly display name or selected value are present. Both custom pages, use combo boxes with friendly display names configured in the settings of each page.

Everything else works well otherwise but I would like for the builders to see the values they picked on the summary page. Is there something I am missing on my custom pages that is preventing it from appearing in the summary page?

Thank you for the assistance.

I am attempting to run a Refresh scenario to migrate systems from Windows 7 to Windows 8.1 Update.  I am running MDT 2013 and WADK for Windows 8.1.  I am using a Standard Client Task Sequence.  However, the restore of the userstate with loadstate.exe is not processing.

My Log files are at https://onedrive.live.com/?cid=437e847ec515b556&id=437E847EC515B556%21119&action=Share#cid=437E847EC515B556&id=437E847EC515B556%21119

If you look at BDD.LOG at 04/24/2014 2:38:05 PM you will see that it builds the Base Arguments line to pass to loadstate.exe, but then it does not run loadstate.  Same with the SMSTS.LOG file at 4/28/2014 2:38:04 PM, you will see that it says it is executing ZTIUserstate.wsf /restore, but it does not.

Any ideas?  Thanks