Quantcast
Channel: Microsoft Deployment Toolkit forum
Viewing all 11297 articles
Browse latest View live

MDT 2013 U2 Database question with sccm 2012 1602 integration.

$
0
0

MDT 2013 U2 Database question with sccm 2012 1602 integration.

Hi,

  I am trying to simulate my production with lab. So I have created

Separate Primary sccm server (MDT 2013 U2 integrate)

Separate Sql server

Separate Distribution server

I created mdt share on Primary sccm server.

Created MDT Database with Sql server with SCCM NAA Account and with DBMSSOCN.

My customsettings.ini

[Settings]

Priority=HardwareInfo,Locations, LSettings, Default

Properties=ModelAlias,MyCustomProperty

[HardwareInfo]

UserExit=AliasUserExit.vbs

ModelAlias=#SetModelAlias()#

[Default]

OSInstall=Y

SkipCapture=YES

SkipAdminPassword=YES

SkipProductKey=YES

SkipComputerBackup=YES

SkipBitLocker=YES

SkipAppsOnUpgrade=YES

[Locations]

SQLServer=sqlserver.adminsys.mrll.com

Database=MDT

;Netlib=DBNMPNTW

Netlib=DBMSSOCN

SQLShare=mdtproduction$

Table=Locations

Parameters=DefaultGateway

[LSettings]

SQLServer= sqlserver.adminsys.mrll.com

Database=MDT

;Netlib=DBNMPNTW

Netlib=DBMSSOCN

SQLShare=mdtproduction$

Table=LocationSettings

Parameters=DefaultGateway

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

First question:

It tries to map sqlserver\mdtproduction$ instead from where I created share sccm primary server.

Do I need to copy my share to sqlserver? How can I run with sccm share where I created share?

2<sup>nd</sup> Q.

  I am getting error

FAILURE (Err): 429: CreateObject(Microsoft.BDD.Utility) - ActiveX component can't create object

Log file https://1drv.ms/u/s!AvrwFkn-ASCWkinvKnrrvhReyMOv

3<sup>rd</sup> Q.

  What type of permission required in sql to run MDTDatabase?

I have added my Netaccess from sccm, but I am getting error

ZTI error opening SQL Connection: Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. (-2147217843)    ZTIGather            10/27/2016 4:55:10 PM 0 (0x0000)

Unable to establish database connection using [LOCATIONS] properties.  ZTIGather               10/27/2016 4:55:10 PM 0 (0x0000)



orion


Issues with MDT deployment

$
0
0

Hi, I hope someone can help me. We use MDT to deploy Windows 7 to desktops and laptops. This was working great until recently. The deployment deploys the image but it fails to logon to the computer once the deployment is done so that it can do the Post Install steps in the Task sequence.

I have Auto Logon enabled in 7 oobe System section of the unattend.xml but when it gets to this part it says username/password incorrect. If I manually enter the password set in this step it logs on and carries on with the rest of the task sequence. I have tried creating a totally new task sequence and unattend.xml but i still get the same issue. I have tried changing the account it users from the defualt built in admin account to a domain account but still get the message username/password are incorrect. Is anyone able to help?

"The task sequence has been suspended. LiteTouch is trying to install applications. This cannot be performed in Windows PE."

$
0
0

MDT 2012 Server is up and running. I mistakenly deleted a Task Sequence step called "Install Application" that I thought was not needed (I know I should have disabled it and tested).

I have a problem now, when I went to image a computer I did not get application list (This used to work before I deleted the above TS step) with items to check and uncheck for installation.  "Install Application" TS was readded but now when I try to image I get this error:

"The task sequence has been suspended. LiteTouch is trying to install applications. This cannot be performed in Windows PE."

I've tried moving it to different positions on the list (Higher and lower) to no avail, I always get the same error. Please advise.

-Thanks in advance!






MDT ImageX command line Description issue

$
0
0

We boot into MDT and the drop out to the command line map a drive to the deployment share and run the imagex command from \deploymentshare\tools\x64\ and then run the following imagex command:

Imagex /capture d: s:\captures\filename.wim “description” /compress fast /verify

What I find is that the description always ends up as part of my file name. When I review the MS article for syntax it appears that my command is correct, but I find other NON Microsoft examples that show up as imagex /capture nameof_file.wim c: "description" /compress fast /verify

I have also tried imagex /capture d:\name.wim s:\captures "description" /compress fast /verify with the same result.

to be clear the issue with not in capturing the image, but getting the description to populate the meta data field "Description" rather than being appended to the file name. If I skip the "description" from the imagex /capture the command will not run.

We are running MDT 2013 Update 2.

I have tried using the MDT capture TS but have not had luck in getting that process to work, so I use what has worked for me in the past.

Deploy SCCM Applications with MDT when Integrated-Is it possible?

$
0
0

I have been hearing all of this talk about Integrating our SCCM and MDT Servers.  So searching around I can see where you can create a MDT task sequence in SCCM, but will that allow you to share Applications and Packages?  I can't seem to find the correct answer on this one.

Thanks

How do you navigate an MDT Deployment Share to a secondary drive?

$
0
0

For a few months now I have been managing and running our MDT Deployment Share off of the C:\ drive on the local MDT server and it's been working flawlessly.

I decided to move it to a secondary drive on the virtual server.

I made the following updates in an attempt to get it to function with the new deployment share:

1.) Copied the entire deployment share to E:\DeploymentShare

2.) Right clicked on Deployment Share, closed it, and then opened up the Deployment Share on the E:\ drive

2.) Shared the folder out, and made sure domain admins had full access to it

3.) Updated the bootstrap.ini file with: DeployRoot=\\server-name\e\DeploymentShare

4.) Edited the properties of the newly imported deployment share so the local path was E:\DeploymentShare and the UNC path was \\server-name\e\DeploymentShare

5.) Completely rebuilt the boot files, uploaded the new boot files to our WDS server, and booted to that

Once trying to connect to the deployment share with domain admin credentials, which I made sure had rights to that drive I shared out, I get the following error:"*Invalid credentials. The network name could not be found."

I'm not sure what I did wrong? I updated the pointers everywhere I could think of, however am unable to connect to the deployment share on the second drive. Does anyone have any insight to this?

MDT 2013 failing Windows 10 install "The computer restarted unexpectedly"

$
0
0

"The computer restarted unexpectedly or encountered an unexpected error. Windows installation cannot proceed. To install Windows, click "OK" to restart the computer, and then restart the installation."

I have been beating my head against this all day and have gotten no where. I cannot find anything in the logs. The issue is intermittent, occurs 100% of imaging attempts on some machines, 0% on others, and completely hit or miss on others. These are dell laptops and desktops, latitude 3570, latitude e7270, and optiplex 3040.

https://drive.google.com/file/d/0ByQV0AantsIYTmxDc09oNXBPY0k/view?usp=sharing

MDT and Multiple Disks

$
0
0

Hi, All

How to make MDT work well when a PC has multiple disks and one of them is SSD,as a target disk running OS.

Now more and more PCs run with at least two disks, so I think this solution is to be needed.

Anyone can help ?



Error 500 : variable is undefined VBScript Code : ValidateTSList

$
0
0

Hello,

I can't load wizard properly while PXE booting on a virtual machine and I'm getting this error :

Error 500 : variable is undefined VBScript Code : ValidateTSList 

This is working without any trouble on a physical machine but it's broken on a virtual machine... (we are using Hyper-V and Windows Server 2012 R2)

Do you have some ideas about this ? Scripts files haven't been modified manually... I already updated deployment share and changed the boot image in our WDS, it didn't resolve the problem.

Thanks a lot,

Valentin

UDI and USMT Restore from USB

$
0
0

This seems like a simple solution but for the life of me I can't figure it out despite hours of trial and error and documentation/internet research.  Any help would be greatly appreciated.

I have created a UDI driven SCCM 1608 task sequence to perform a USMT capture to either a network share or USB drive using the UDI Replace template. The task sequence is run from the Software Center within Windows (no reboot to WinPE). I created a similar UDI driven task sequence using the UDI New Computer template to perform a USMT restore. This task sequence is also run from the Software Center in Windows on the new computer. The problem is that I cannot find a way to have the user select between the USB and Network restore options. 

The USB and Network restore options are grayed out when I run the UDI/USMT restore task sequence.  I have locked the ‘No Data’ and ‘Local’ restore options in the UDI New Computer template (so I expect those to be grayed out) but the USB and Network restore options are unlocked.  See attached screen shots for details.

Can anyone point me in the right direction on how to make both the USB and Network restore options available during the UDI/USMT restore task sequence?

MDT 2012 Update 2 – UDI/USMT Capture (Replace) Configuration

Note: Successfully able to select “USB” during UDI/USMT capture task sequence as seen above

MDT 2012 Update 2 – UDI/USMT Restore (New Computer) Configuration

Problem: Cannot select “USB” device during UDI/USMT restore task sequence as seen above

Again, any help or guidance would be greatly appreciated.

Regards,

JJ

Non-zero return code by ZTIApplyGPOPack

$
0
0

I'm running MDT 2013 Update 2 and sporadically receiving the error:

Litetouch deployment failed, Return Code = -2147467259  0x80004005

This error appears to be caused by: 

Event 41002 sent: ZTI ERROR - Non-zero return code by ZTIApplyGPOPack, rc = 1

Logs:

<![LOG[USing GPO Pack Path Specified in variable GPOPackPath: GPO]LOG]!><time="08:48:50.000+000" date="10-31-2016" component="ZTIApplyGPOPack" context="" type="1" thread="" file="ZTIApplyGPOPack"><![LOG[Copying GPO Pack files to: C:\MININT\GPO]LOG]!><time="08:48:50.000+000" date="10-31-2016" component="ZTIApplyGPOPack" context="" type="1" thread="" file="ZTIApplyGPOPack"><![LOG[About to run command: cmd /c cscript.exe "C:\MININT\GPO\GPOPack.wsf" /Path:"C:\MININT\GPO" /silent]LOG]!><time="08:48:51.000+000" date="10-31-2016" component="ZTIApplyGPOPack" context="" type="1" thread="" file="ZTIApplyGPOPack"><![LOG[Command has been started (process ID 904)]LOG]!><time="08:48:51.000+000" date="10-31-2016" component="ZTIApplyGPOPack" context="" type="1" thread="" file="ZTIApplyGPOPack"><![LOG[ZTI Heartbeat: command has been running for 0 minutes (process ID 904)]LOG]!><time="08:48:51.000+000" date="10-31-2016" component="ZTIApplyGPOPack" context="" type="1" thread="" file="ZTIApplyGPOPack"><![LOG[Event 41003 sent: ZTI Heartbeat: command has been running for 0 minutes (process ID 904)]LOG]!><time="08:48:52.000+000" date="10-31-2016" component="ZTIApplyGPOPack" context="" type="1" thread="" file="ZTIApplyGPOPack"><![LOG[Return code from command = 1]LOG]!><time="08:48:52.000+000" date="10-31-2016" component="ZTIApplyGPOPack" context="" type="1" thread="" file="ZTIApplyGPOPack"><![LOG[ZTI ERROR - Non-zero return code by ZTIApplyGPOPack, rc = 1]LOG]!><time="08:48:52.000+000" date="10-31-2016" component="ZTIApplyGPOPack" context="" type="3" thread="" file="ZTIApplyGPOPack"><![LOG[Event 41002 sent: ZTI ERROR - Non-zero return code by ZTIApplyGPOPack, rc = 1]LOG]!><time="08:48:52.000+000" date="10-31-2016" component="ZTIApplyGPOPack" context="" type="1" thread="" file="ZTIApplyGPOPack"><![LOG[Command completed, return code = -2147467259]LOG]!><time="08:48:53.000+000" date="10-31-2016" component="LiteTouch" context="" type="1" thread="" file="LiteTouch"><![LOG[Litetouch deployment failed, Return Code = -2147467259  0x80004005]LOG]!><time="08:48:53.000+000" date="10-31-2016" component="LiteTouch" context="" type="3" thread="" file="LiteTouch"><![LOG[Event 41014 sent: Litetouch deployment failed, Return Code = -2147467259  0x80004005]LOG]!><time="08:48:54.000+000" date="10-31-2016" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">

If I received the error, I can restart the exact same deployment on the same machine and it will go through without an error.

Does anyone know of a fix for this issue?


MDT 2013 Creates Extra Active Partition

$
0
0
How to stop MDT 2013 creating an extra active partition.This is no option for canceling now,but in the earlier verion,it has. 



Invalid Credentials Error

$
0
0

Hi Experts,

I am getting below "DEPLOYMENT FAILURE ERROR" while deploying Windows 8.1 however i removed my user name which as domain permission from boot.ini and RULES in workbench properties.

kindly help me out.

Below is RULES in Workbench.

[Settings]
Priority=Default
Properties=MyCustomProperty

[Default]
OSInstall=Y
SkipBDDWelcome=YES
SkipDeploymentType=YES
SkipDomainMembership=YES
SkipApplications=NO
SkipSummary=YES
SkipUserData=YES
SkipComputerName=NO
SkipTaskSequence=NO
SkipLocaleSelection=YES
;SkipTimeZone=YES
SkipAppsOnUpgrade=YES
SkipAdminPassword=YES
SkipProductKey=YES
SkipComputerBackup=YES
SkipBitLocker=YES
SkipCapture=YES
SkipFinalSummary=YES

Below is the Boot.ini Configuration.

[Settings]
Priority=Default

[Default]
DeployRoot=\\CSJRN-ADC\DeploymentShare$
SkipBDDWelcome=YES
KeyboardLocale=en-US

MDT Capturing Wim Image - FAILURE (5456) Error

$
0
0

Hi All,

Please could you assist, i have the latest version of MDT and i'm having an issue when capturing a WIM file.

It seems to be an issue only with one of our devices which is UEFI. I can boot to the MDT stick OK and when i select the capture wim task sequence and select where to store the wim it attempts to capture the wim and fails with the following errors. Below are the error logs, any help would be much appreciated.

AILURE ( 5456 ): Unable to determine Destination Disk, Partition, and/or Drive. See BDD.LOG for more information.

Litetouch deployment failed, Return Code = -2147467259  0x80004005LiteTouch26-Oct-16 5:31:44 PM0 (0x0000)

When using the same Task Sequence to capture an MBR formatted image it works OK!!

Any assistance would be much appreciated.

MDT for SCCM

$
0
0
If my company already have existing SCCM Task Sequence setup and used as production for sometime. when I setup MDT and configure to integrate with SCCM, will it affect the running of existing Task Sequence.

Anyone else working with HP SoftPaq-based driver files?

$
0
0
If anyone else here is dealing with HP computers you know what I mean. They offer their drivers in the form of these little .EXE-based files called SoftPaqs. They tend to be named something like ""SPxxxxx.exe". I have been setting these up in the MDT as APPLICATIONS and I'm running a set of silent install commands on each one to get them installed. If anyone wants to know here's the supported command syntax:

  •  "SPxxxxx.exe is the SoftPaq to unpack
  • "-pdf" is a runtime switch that overrides the build parameters
  • "-f" is a runtime switch that overrides the default path set at build time
  • "-s" instructs the package to unpack in silent mode, skipping the Welcome, License, and Directory screens
  • "-e" instructs the package to extract only, that is, do not run the component installation program.
  • -s -a -silent -reboot (Good for silent installs.)

My question is this:

Is anyone else doing this differently (specifically for HP SoftPaqs)?


I've read a few other posts and I've noticed that many people tend to go for a process that involves extracting drivers from vendors and getting them integrated into Out-Of-Box drivers. I'm just wondering if my method is the best. mainly because I need to associate a specific set of these drivers with specific task sequences and that is probing difficult when they are set up as Applications. Any thoughts/advice?

Windows 10 MDT doesn't start deployment wizard

$
0
0

Hello,

I am new to MDT 2013, and my scenario is this:  I am trying to create a Windows 10 reference image.  I have created a deployment share, task sequence, etc and am trying to run the TS on the virtual machine I have created.  It processes the Bootstrap and Custom settings but then just sits at a grey screen that says "Microsoft Deployment Toolkit" and goes no further.  I thought it may have been a problem with the WSUS server line in the customsettings.ini, so I took the entry for that out, but it's still not doing anything that I can see.  No logs have been created either, so I'm not sure where to begin looking.  Any help would be greatly appreciated.

Need help troubleshooting "Name already exists:" errors when replicating to linked shares...

$
0
0

Hey guys,

Recently I accidentally deleted and then had to re-import a driver into my Out-Of-Box drivers node in the Deployment Workbench. When I did that I just gave it the same name as the old driver so no harm no foul right? The problem is that now when I try to replicate out to my linked deployment shares I constantly get errors like this: 

"Name already exists: '\\<MyServerName>\<MyMDTShareName$\Out-of-Box Drivers\<MyFolderName>\<MyDriverName>' specified."

I've actually gone as far as deleting everything under Out-Of-Box drivers and re-replicating everything. The error continues to persist. I searched here and found this similar post:

http://social.technet.microsoft.com/Forums/en-US/mdt/thread/627bc398-1f95-4092-a385-ce5e2e132be0

It seems they just caulked it up to a bug and left it at that. I'm wondering if there is some erroneous entry in a XML file that I can delete or if anyone else has come up with any sort of solution to this issue. I've had it happen more than once now, so surely someone else has encountered it and knows how to fix it.

Anyone?

MDT 2012 - Error while importing driver CABs

$
0
0

Hello community,

I have a huge problem with MDT2012 since yesterday: I cleaned my driver repository a little and now I cannot import driver CAB´s anymore, every time it ends with this error:

System.Management.Automation.CmdletInvocationException: Index was out of range. Must be non-negative and less than the size of the collection.
Parameter name: index ---> System.ArgumentOutOfRangeException: Index was out of range. Must be non-negative and less than the size of the collection.
Parameter name: index
   at System.ThrowHelper.ThrowArgumentOutOfRangeException()
   at System.Collections.Generic.List`1.get_Item(Int32 index)
   at Microsoft.BDD.PSSnapIn.Verifier.AddDriver(String theInfFile)
   at Microsoft.BDD.PSSnapIn.ImportDriver.ImportDrivers(String thePath)
   at Microsoft.BDD.PSSnapIn.ImportDriver.ImportDrivers(String thePath)
   at Microsoft.BDD.PSSnapIn.ImportDriver.ImportDrivers(String thePath)
   at Microsoft.BDD.PSSnapIn.ImportDriver.ImportDrivers(String thePath)
   at Microsoft.BDD.PSSnapIn.ImportDriver.ImportDrivers(String thePath)
   at Microsoft.BDD.PSSnapIn.ImportDriver.ImportDrivers(String thePath)
   at Microsoft.BDD.PSSnapIn.ImportDriver.ImportDrivers(String thePath)
   at Microsoft.BDD.PSSnapIn.ImportDriver.ImportDrivers(String thePath)
   at Microsoft.BDD.PSSnapIn.ImportDriver.ImportDrivers(String thePath)
   at Microsoft.BDD.PSSnapIn.ImportDriver.ProcessRecord()
   at System.Management.Automation.CommandProcessor.ProcessRecord()
   --- End of inner exception stack trace ---
   at System.Management.Automation.Internal.PipelineProcessor.SynchronousExecuteEnumerate(Object input, Hashtable errorResults, Boolean enumerate)
   at System.Management.Automation.Runspaces.LocalPipeline.InvokeHelper()
   at System.Management.Automation.Runspaces.LocalPipeline.InvokeThreadProc()

Funny: For testing I have created a second (new) "deployment share" and the same CABs gets imported without problems there. So the problem must be somewhere in my old share, but I have no clue how to fix this.

I crawled tho hole web and can not find anything! I don´t wont to move my whole share to the new one :(

Any advise?



Error: 0x800f081e The specified package is not applicable to this image

$
0
0

I have verified the version numbers of the VM(1607 OS 14393.350) and the private package I am trying to install (10.0.14393.460). which is greater than the one I am replacing with.

The packages itself is fine, does this have anything to do with my dev box!

DISM Logs are here. appreciate any feedback on how I could fix this.

2016-11-02 00:52:53, Info                  DISM   DISM Provider Store: PID=6392 TID=6408 Getting Provider DISM Package Manager - CDISMProviderStore::GetProvider
2016-11-02 00:52:53, Info                  DISM   DISM Provider Store: PID=6392 TID=6408 Provider has previously been initialized.  Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
2016-11-02 00:52:53, Info                  DISM   DISM Package Manager: PID=6392 TID=6408 Processing the top level command token(add-package). - CPackageManagerCLIHandler::Private_ValidateCmdLine
2016-11-02 00:52:53, Info                  DISM   DISM Package Manager: PID=6392 TID=6408 Attempting to route to appropriate command handler. - CPackageManagerCLIHandler::ExecuteCmdLine
2016-11-02 00:52:53, Info                  DISM   DISM Package Manager: PID=6392 TID=6408 Routing the command... - CPackageManagerCLIHandler::ExecuteCmdLine
2016-11-02 00:52:53, Info                  DISM   DISM Package Manager: PID=6392 TID=6408 Encountered the option "packagepath" with value "KB123456.CAB" - CPackageManagerCLIHandler::Private_GetPackagesFromCommandLine
2016-11-02 00:52:54, Info                  DISM   DISM Package Manager: PID=6392 TID=6408 Package Package_for_KB123456_private_0b35f981e41558d2893166f6e0530deba8851816~31bf3856ad364e35~amd64~~10.0.1.0 with CBS state 0(CbsInstallStateAbsent) being mapped to dism state 1(DISM_INSTALL_STATE_NOTPRESENT) - CDISMPackage::LogInstallStateMapping
2016-11-02 00:52:54, Error                 DISM   DISM Package Manager: PID=6392 TID=6408 The package Package_for_KB123456_private_0b35f981e41558d2893166f6e0530deba8851816 is not applicable to the image. - CPackageManagerCLIHandler::Private_ProcessPackageChange
2016-11-02 00:52:54, Info                  DISM   DISM Package Manager: PID=6392 TID=6408 Initiating Changes on Package with values: 4, 7 - CDISMPackage::Internal_ChangePackageState
2016-11-02 00:52:54, Info                  DISM   DISM Package Manager: PID=6392 TID=6408 CBS session options=0x100! - CDISMPackageManager::Internal_Finalize
2016-11-02 00:52:55, Info                  DISM   DISM Package Manager: PID=6392 TID=6424  Error in operation: the package is not applicable. (CBS HRESULT=0x800f081e) - CCbsConUIHandler::Error
2016-11-02 00:52:55, Info                  DISM   DISM Package Manager: PID=6392 TID=6408 DISM has detected a DISM component change. Requesting a shutdown. - CDISMPackageManager::Internal_Finalize
2016-11-02 00:52:55, Info                  DISM   DISM Image Session: PID=6392 TID=6408 The image session needs to be closed and re-opened before any servicing operations can be performed. - CDISMImageSession::put_ImageState
2016-11-02 00:52:55, Error                 DISM   DISM Package Manager: PID=6392 TID=6408 Failed while processing command add-package. - CPackageManagerCLIHandler::ExecuteCmdLine(hr:0x800f081e)
2016-11-02 00:52:55, Info                  DISM   DISM Package Manager: PID=6392 TID=6408 Further logs for online package and feature related operations can be found at %WINDIR%\logs\CBS\cbs.log - CPackageManagerCLIHandler::ExecuteCmdLine
2016-11-02 00:52:55, Info                  DISM   DISM Provider Store: PID=6392 TID=6424 Found the OSServices.  Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
2016-11-02 00:52:55, Info                  DISM   DISM Provider Store: PID=6392 TID=6424 Found the OSServices.  Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
2016-11-02 00:52:55, Info                  DISM   DISM Provider Store: PID=6392 TID=6424 Found the PE Provider.  Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
2016-11-02 00:52:55, Info                  DISM   DISM Provider Store: PID=6392 TID=6424 Finalizing the servicing provider(DISM Package Manager) - CDISMProviderStore::Internal_DisconnectProvider
2016-11-02 00:52:55, Info                  DISM   DISM Package Manager: PID=6392 TID=6424 Finalizing CBS core. - CDISMPackageManager::Finalize

Viewing all 11297 articles
Browse latest View live




Latest Images