Dears,

please help in the matter of running .NET 4 app (basic vb.net app on .net framework 4 base);

When I try to run an basic application on the WinPE 4 image runninng, I get the error message "This application could not be started. You must enable the .NET Framework from the Windows Features dialog box (from Control Panel, choose Programs, Turn Windows features on or off)." even if I have enabled all the features from DISM when deploying the WinPE 4 wim image (all the features present from the dism /get-features by dism /enable-feature to switch the states from "Enable Pending" to "Enabled" incl. the WinPE-NetFx4 package) I am not able to run the app.

Please help how to get the app run or when needed any further info about the image.

Thanks a lot, tad.

Hello All,

I have Windows XP Sp3 Image. last week i have captured existing Image on VM due to some Application configuration and to set windows settings. it was sucessfull captured and i used the newly created WIM in current deployment share. when i reimaged a Laptop with updated Image i found the below in summary page-

Unable to dind CoustomSettings.ini, rc=1

FAILURE(Err): 438: GetVirtualizationInfo for Gather Process- Object doesn't support this prpperty or method

FAILURE(Err): 438: GetVirtualizationInfo for Gather Process- Object doesn't support this prpperty or method

When the same image applied on VM machine, it deployed successfully without any error or warning messages.

Please suggest if this error is showing because i have captured WIM on VM or is there any issue..

Thanks in Advance.

mohd.w

got different model DELL desktops in our environment, built the reference machine with 760, the problem is now I can ONLY load the reference back to 760, but not any other model due to the driver issue ( or I should say I could load it back any model, but couldn't boot the machines up except 760), and we are getting rid of 760 now, how do I inject all models' driver to reference so I can load reference on any machines?

thanks.

Hello!

I'm using MDT 2012 update 1 Beta. I'have made a seperate Deployment share for virtual machines, imported the custom image, added windows 2008 CD files,  added the Array storage drivers for the server where the VHD wil be deployed on and all the HyperVdrivers to "Out of box drivers". I've also added "All system class drivers" under WinPE drivers and patches.

I create a new virtual machine, create av dynamic disk (VHD), mapped the liteTouchPE_x64.iso. Now i boot the virtual machine, enter the user, password, regional settings .. etc.. after that ...

What drivers do i need to add, and when/where?

Best Regards

Lars-Göran

(Took me sometime to find this little bugger.)

Change row 94 to:

If UCase(oEnvironment.Item("BdeInstallSuppress")) <> "NO" and (oEnvironment.Item("IsBDE")) <> "TRUE" Then

Needless to say - I was having the statement BdeInstallSuppress=No in the settings... :-)

Kind regards,

Christian

Is it possible to build and capture winxpsp3 in MDT 2012?

I used the standard client task sequence.

When I try to do this, the task sequence begins, disk formatted etc, the installation of Windows XP begins and before the installation finishes the system reboots and I end up with a screen requesting I insert my Windows XP SP3 disk.

I am trying to capture using VMWare if that makes any difference.

I should add that I have exactly zero experience with MDT of any version.

Hello,

I'm trying to import a captured wim file in to "deployment workbench - operating systems" but It's not wotking

I've done this many times before with no problem but when I import this wim file it can't been seen within deployment workbench but you CAN see it in C drive. I've already trying refreshing and restarting MDT & the system MDT is hosted on but the problem still persists.

Here is a screenshot of my problem, as you can see the operating system cannot be found within deployment workbench but it is within C drive,

Thank you.

I have a fresh install of MDT 2012 I have the option set in my CS to: SkipAdminAccounts=NO, SkipAdminPassword=NO to display the Local Administrators wizard page. When I run the wizard it does not disply the Local Administrators wizard page. I have read the Toolkit Library help docs and it appears that I have set everything up correctly.  I have bulit a few TS to see if it could been a bad one but they all skip this page. Here is my current CS.ini which is basic settings. Am I missing something?

[Settings]
Priority=Default
Properties=MyCustomProperty

[Default]
SkipAdminAccounts=NO
SkipAdminPassword=NO
OSInstall=Y
SkipCapture=YES
SkipProductKey=YES
SkipComputerBackup=YES
SkipBitLocker=YES

Good afternoon,

I'm attempting to use MDT 2010 to setup SCCM to deploy Windows 7, however when attempting to create a Task Sequence for MDT (this is the task sequence where it's creating packages for Windows 7, Boot Image, MDT, USMT, Settings Package, etc) in SCCM I recieve the following error:

Started processing.
Creating boot image.
Generating boot image.
Capturing new boot image WIM file.
Copying WIM image to package source directory.
Error while importing Microsoft Deployment Toolkit Task Sequence. 
Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlQueryException: The ConfigMgr Provider reported an error. ---> System.Management.ManagementException: Generic failure 
  at System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus errorCode)
  at System.Management.ManagementObject.Put(PutOptions options)
  at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlResultObject.Put(ReportProgress progressReport)
  --- End of inner exception stack trace ---
  at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlResultObject.Put(ReportProgress progressReport)
  at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlResultObject.Put()

I'm using SCCM SP2 R2, with MDT 2010 including Update 1 (V5.1.1642.01), I'm using SCCM with the SQL Server on a separate server.

I'm running MDT on the primary site server which is Windows 2003 R2 SP2 x86 and the DB is on a Windows 2008 R2 with SQL Server 2008.
I've also tried running MDT on a Windows 2008 R2 Site Server & Windows 7 (x86) client with the same error occuring.

I've run the MDT SCCM Integration utility successfully in all instances, so I'm unsure how to progress now.

I've confirmed that the Site Server Computer account (and the Database Server computer account & the PXE service point computer account) have access to the correct file shares. After the Task Sequence fails I'm left with a WinPE.wim file in the packages folder and nothing else.

Here's the error from SmsAdminUI.log

[8][8/09/2010 6:06:25 PM] :System.Management.ManagementException\r\nGeneric failure \r\n  at System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus errorCode)
  at System.Management.ManagementObject.Put(PutOptions options)
  at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlResultObject.Put(ReportProgress progressReport)\r\nManagementException details:
instance of SMS_ExtendedStatus
{
	Description = "Failed to insert OSD binaries into the WIM file";
	ErrorCode = 2152205056;
	File = "e:\\nts_sms_fre\\sms\\siteserver\\sdk_provider\\smsprov\\sspbootimagepackage.cpp";
	Line = 3321;
	ObjectInfo = "CSspBootImagePackage::InjectOSDBinaries";
	Operation = "PutInstance";
	ParameterInfo = "";
	ProviderName = "ExtnProv";
	StatusCode = 2147749889;
};
\r\n

Many thanks in advance for any assistance.

Thanks,

CJ

Hi, I am trying to deploy a captured wim image with a standard task sequence. I created the image by running a standard client task sequence and letting it capture and upload to te server.

After that I added the image  as a new OS to the deployment share, I chose the option, "no sysprep or setup files needed".

When I tried to deploy the custom image with a standard cliuent task, it installs the image correctly, even with the settings I changed in the unattend.xml.

When the installation of windows is finished, the computer restart (as specified in the task sequence) and automatticaly logs on to the administrator account.

But then nothing happens. The task sequence doesn't continue with the state restore or custom tasks, no summary or error window is displayed and there is no MININT folder to be found on the C-drive. But the _SMSTASKSEQUENCE folder is still there. 

Can anyone help me figure out what the problem could be, I have no Idea on how to ressolve it. The unnattend.xml has the runsynchonous commands in the oobe section, but the minintfolder is not present.

I continue to have issues with trying to capture data from XP machines with Duplicate/Broken profiles. It fails, I have used a execution string similar to this:

(scanstate c:\store /i:migdocs.xml /i:migapp.xml /o /c /v:5 /ue:* /ui:S-1-5-21-1120787987-3120651664-2685341087* /ui:%computername%\*)

where USMT is instructed to only capture Domain profiles, yet it still fails. Any help would be greatly appreciated

Here's the initial issue:

Build custom WIM (windows 7 x86 Enterprise)

Captured image successfully 

Created a TASK Sequence with custom applications

Deployment of OS was successful 

After booting into Windows nothing happens, no summary page etc...

I found this in another technet forum but I am unable to find the registry key that is mentioned in the solution:

if anyone has any suggestions on how to get this resolve please reply.

http://social.technet.microsoft.com/Forums/en-US/mdt/thread/2b8e018a-4e90-4588-aa02-e6c7d59fd6ae/

A series of events has led me to this point.  Without giving a huge back story, I need to be able to bypass the format & partition step of a TS, and force the TS to format the HD via the unattend.xml.

It is not possible to simply disable the step as the deployment fails straight away.  I have been playing around with the unnatend.xml, the disk configuration step is attached below:

I created this by using the default example through WSIM help files.  The TS will inject drivers and everything will work fine up until the installation of Windows.  As soon as 'Setup is starting' text appears, I get an error saying that 'Windows cannot parse the unattend answer files <diskConfiguration> setting.'

I'm pretty stuck without getting this to work.  If you need the backstory then I'll provide, just wanted to get straight to the point in the first post.

Many thanks in advance,

Doug

Hello.

I have been tasked with finishing the deployment project. I am taking over for a former employee and I have no idea where to procede.

Specify credentials for connecting to network shares.

User Name:
Password:
Domain:

My login info is correct. I can ping the server from the machine. I am also able to see that the connection is OK but invalid credentials are blocking me.

I want to be able to assign a group to be able to deploy images, but everything I have tried has failed. Here is my current bootstrap.ini and CustomSettings.ini

I have tried both FQDN and NETBIOS domain name. I have entered in my own account info. Nothing works.

[Settings]
Priority=Default

[Default]
DeployRoot=\\SHOVWDS\PetrolinkDeploymentShare$
UserID=sysmgr
UserDomain=domain
UserPassword=***

==========================

[Settings]
Priority=Default
Properties=MyCustomProperty

[Default]
OSInstall=Y
SkipCapture=YES
SkipAdminPassword=YES
SkipProductKey=YES
Administrators1=DOMAIN\Domain Users
DomainAdmin=sysmgr
DomainAdminDomain=DOMAIN
DomainAdminPassword=***
SkipComputerBackup=YES
SkipBitLocker=YES
TimeZoneName=Central Standard Time
SkipFinalSummary=YES
SkipLocaleSelection=YES
KeyboardLocale=en-US
UserLocale=en-US
UILanguage=en-US
SkipPackageDisplay=YES
SkipProductKey=YES
SkipSummary=YES
SkipTaskSequence=YES
SkipTimeZone=YES
TimeZoneName=Central Standard Time
SkipUserData=Yes

Can anyone tell me where I am going wrong? 

Hi all,

I've recently upgraded out MDT 2010 environment to MDT2012 and now whenever i attempt to do a PC refresh (running litetouch.vbs from deployment share) it gets to step 47/77 and ends up with a command prompt window spewing the following over and over:

Property Logpath is now = C:\MININT\SMSOSD\OSDLOGS

This also fills the BDD.log file and litetouch.log file.

The last few lines of BDD.log are (last line repeating until killed):

<![LOG[Property PHASE is now = STATERESTORE]LOG]!><time="10:40:23.000+000" date="04-26-2012" component="ZTINextPhase" context="" type="1" thread="" file="ZTINextPhase">
<![LOG[ZTINextPhase COMPLETED.  Return Value = 0]LOG]!><time="10:40:23.000+000" date="04-26-2012" component="ZTINextPhase" context="" type="1" thread="" file="ZTINextPhase">
<![LOG[ZTINextPhase processing completed successfully.]LOG]!><time="10:40:23.000+000" date="04-26-2012" component="ZTINextPhase" context="" type="1" thread="" file="ZTINextPhase">
<![LOG[Event 41001 sent: ZTINextPhase processing completed successfully.]LOG]!><time="10:40:24.000+000" date="04-26-2012" component="ZTINextPhase" context="" type="1" thread="" file="ZTINextPhase">
<![LOG[Command completed, return code = -2147021886]LOG]!><time="10:40:24.000+000" date="04-26-2012" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Property LTIDirty is now = FALSE]LOG]!><time="10:40:24.000+000" date="04-26-2012" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[If there is a drive letter defined, make sure we clear it now so we can *force* recalcutation.]LOG]!><time="10:40:24.000+000" date="04-26-2012" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Property OSDTargetDriveCache is now = DIRTY]LOG]!><time="10:40:24.000+000" date="04-26-2012" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[LTI initiating task sequence-requested reboot.]LOG]!><time="10:40:24.000+000" date="04-26-2012" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Event 41017 sent: LTI initiating task sequence-requested reboot.]LOG]!><time="10:40:24.000+000" date="04-26-2012" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Property LogPath is now = C:\MININT\SMSOSD\OSDLOGS]LOG]!><time="10:52:28.000+000" date="04-26-2012" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Property LogPath is now = C:\MININT\SMSOSD\OSDLOGS]LOG]!><time="10:52:29.000+000" date="04-26-2012" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Property LogPath is now = C:\MININT\SMSOSD\OSDLOGS]LOG]!><time="10:52:29.000+000" date="04-26-2012" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Property LogPath is now = C:\MININT\SMSOSD\OSDLOGS]LOG]!><time="10:52:28.000+000" date="04-26-2012" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">

The last few lines of litetouch.log are (last line repeating until killed):

<![LOG[Property TargetPartitionIdentifier is now = SELECT * FROM Win32_LogicalDisk WHERE Size = '314169094144' and VolumeName = 'OSDisk' and VolumeSerialNumber = 'C857F6E4']LOG]!><time="09:54:50.000+000" date="04-26-2012" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[About to run command: "X:\Deploy\Tools\X64\TsmBootstrap.exe" /env:SAContinue]LOG]!><time="09:54:50.000+000" date="04-26-2012" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Property LTIDirty is now = TRUE]LOG]!><time="09:54:50.000+000" date="04-26-2012" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Command completed, return code = -2147021886]LOG]!><time="10:40:24.000+000" date="04-26-2012" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Property LTIDirty is now = FALSE]LOG]!><time="10:40:24.000+000" date="04-26-2012" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[If there is a drive letter defined, make sure we clear it now so we can *force* recalcutation.]LOG]!><time="10:40:24.000+000" date="04-26-2012" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Property OSDTargetDriveCache is now = DIRTY]LOG]!><time="10:40:24.000+000" date="04-26-2012" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[LTI initiating task sequence-requested reboot.]LOG]!><time="10:40:24.000+000" date="04-26-2012" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Event 41017 sent: LTI initiating task sequence-requested reboot.]LOG]!><time="10:40:24.000+000" date="04-26-2012" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Property LogPath is now = C:\MININT\SMSOSD\OSDLOGS]LOG]!><time="10:52:28.000+000" date="04-26-2012" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Property LogPath is now = C:\MININT\SMSOSD\OSDLOGS]LOG]!><time="10:52:29.000+000" date="04-26-2012" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Property LogPath is now = C:\MININT\SMSOSD\OSDLOGS]LOG]!><time="10:52:28.000+000" date="04-26-2012" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Property LogPath is now = C:\MININT\SMSOSD\OSDLOGS]LOG]!><time="10:52:29.000+000" date="04-26-2012" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">

Any ideas?

I have tried creating a new task sequence from within MDT2012 (rather than using an upgraded one from MDT 2010), and am about to try creating a new deployment share...

Hello, everybody! I have one question about MDT 2012 beta 2

I install nvidia drivers version 285.62, i maked apllication and use quite install command setup.exe /s /noeula /nofinish include reboot,and what we are have:

after reboot install process show this attention ->

Dirty Environment found

An existing ins deployment was found but is not in an expected state.would you like to ignore this in progress deployment and start a new one?

What is is? This is mean what during installation application`s wa are can`t make reboot?right?

Strange issue that I thought I'd put out here to see if anyone has any bright ideas.

I have a custom VBscript that is used to join a doman group to a computer object to enable DirectAccess connectivity in my organization. (We limit the availability of DA based on whether or not a computer object is assigned to a specific group in AD.) The script works when it is ran manually. However, it does not work in a task sequence.

To elaborate, I've added a Run Command Line step in the Custom Tasks section of State Restore; it runs cscript.exe "%SCRIPTROOT%\EnableDirectAccess.vbs". My VB script, EnableDirectAccess, is located in the Scripts folder. Here's the real head-scratcher: After reviewing BDD.log, it doesn't even look like the task sequence was even aware it needed to run the script. There is absolutely no reference to the Run Command Line step I added in Custom Tasks. There is, in fact, no entry in any log generated during the deployment concerning that particular step of the TS or the EnableDirectAccess.vbs. I can clearly see the previous steps running; I can clearly see all of the later steps running. My Run Command Line step simply isn't there.

I have verified the TS.xml contains the Run Command Line step several times. I have verified the known-working script is located in %SCRIPTROOT%, again, several times. I'm at a loss as to what could be causing this. Right now, I'm considering importing the script as an application and seeing if it makes any kind of difference. Has anyone seen anything like this before?

-Nick O.

Hi ,

I have migrated the windows xp machine to windows 7 using MDT 2010,after migration tried to activate the Windows 7 and got the error

A problem occurred when Windows tried to activate. Error Code 0x80072F8F.
For a possible resolution, click More Information.
You can also contact Microsoft by phone to help resolve this problem.

So tried the Activation by phone and was succesful. Please help me to figure out why i could'nt activate and got the above mentioned error.I checked the Date and time settings and everything was fine.

Thanks in Advance

Hi

When deploying Windows 7 with MDT I have encountered this strange issue

PXE boot - loads up into MDT wizard – “processing bootstrap.ini settings” progress bar - freezes at this point. But if I hit enter (there are no buttons to interactive with - just a progress bar) the wizard continues correctly with the next stage of deployment. Without hitting enter, it stays at this bootstrap.ini initializing stage all day. It doesn't get to the phase of choosing the task sequence. 

The strange this is, this problem has only started to appear recently (previous deployments were fine).

Things I have done to trouble shoot: I have "completely regenerated" new boot.wim images and loaded these into WDS. Stripped out all but essential code from bootstrap.ini. Created a new task sequence leaving most settings as default. I have cleaned the disk using diskpart to remove any old files lingering from a bad deployment. Tested on another computer.  I have checked logs for obvious errors but because it doesn't error out at any point (it just sits there) there are no obvious errors that i can see.

Bootstrap.ini:

[Settings] Priority=Default

[Default] SKIPBDDWELCOME=YES

DeployRoot=\\servername\DeploymentShare$

USERDOMAIN=mydomain

USERID=adminuser

SkipBDDWelcome=YES

Its not the end of the world because I can just hit enter but its really annoying me and would rather it to be automated

If anyone has any suggestions that would be fantastic

Thanks