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

vbscripts not running

June 20, 2016, 12:37 am
$
0
0

Hi guys,

We've been running a hybrid 2012 / 2013 MDT setup due to legacy requirements and have recently installed update 2 to MDT2013.

It looks as though none of our vbscripts in task sequences are running in MDT2013. MDT2012 is fine.

Removing the 'continue on error' switch has no effect as it looks as though the builds think everything is running successfully.

Our syntax etc is identical to what we are using in 2012.

Has anybody come across this that could shed some light on the issue or is there something simple that's been missed.

Thanks in advance for any help.

Cheers

↧
Search

Issue updating deployment share - won't generate LitetouchPE_(x64).iso

June 21, 2016, 6:48 pm
$
0
0

Hi there. I'm having an issue when trying to update our deployment share where it won't generate a LitetouchPE
_x64.iso.  The 32bit one generates fine.  This is what I see from the output.  Any help will be greatly appreciated.

=== Making sure the deployment share has the latest x86 tools ===

　

=== Processing LiteTouchPE (x86) boot image ===

　

Building requested boot image profile.

Determining if any changes have been made in the boot image configuration.

No existing boot image profile found for platform x86 so a new image will be created.

Calculating hashes for requested content.

Changes have been made, boot image will be updated.

Windows PE WIM C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Windows Preinstallation Environment\x86\en-us\winpe.wim will be used.

WIM file mounted.

Set Windows PE system root.

Set Windows PE scratch space.

Added component winpe-hta

Added component winpe-scripting

Added component winpe-wmi

Added component winpe-securestartup

Added component winpe-fmapi

Added component winpe-mdac

Copy: \\imageserver\mdt\deploymentimage\Control\Bootstrap.ini to C:\Users\bradm\AppData\Local\Temp\MDTUpdate.7256\Mount\Deploy\Scripts\Bootstrap.ini

Copy: C:\Program Files\Microsoft Deployment Toolkit\Templates\Unattend_PE_x86.xml to C:\Users\bradm\AppData\Local\Temp\MDTUpdate.7256\Mount\Unattend.xml

Copy: C:\Program Files\Microsoft Deployment Toolkit\Templates\winpeshl.ini to C:\Users\bradm\AppData\Local\Temp\MDTUpdate.7256\Mount\Windows\system32\winpeshl.ini

Copy: \\imageserver\mdt\deploymentimage\Scripts\LiteTouch.wsf to C:\Users\bradm\AppData\Local\Temp\MDTUpdate.7256\Mount\Deploy\Scripts\LiteTouch.wsf

Copy: \\imageserver\mdt\deploymentimage\Scripts\ZTIUtility.vbs to C:\Users\bradm\AppData\Local\Temp\MDTUpdate.7256\Mount\Deploy\Scripts\ZTIUtility.vbs

Copy: \\imageserver\mdt\deploymentimage\Scripts\ZTIBCDUtility.vbs to C:\Users\bradm\AppData\Local\Temp\MDTUpdate.7256\Mount\Deploy\Scripts\ZTIBCDUtility.vbs

Copy: \\imageserver\mdt\deploymentimage\Scripts\ZTIDiskUtility.vbs to C:\Users\bradm\AppData\Local\Temp\MDTUpdate.7256\Mount\Deploy\Scripts\ZTIDiskUtility.vbs

Copy: \\imageserver\mdt\deploymentimage\Scripts\ZTIDataAccess.vbs to C:\Users\bradm\AppData\Local\Temp\MDTUpdate.7256\Mount\Deploy\Scripts\ZTIDataAccess.vbs

Copy: \\imageserver\mdt\deploymentimage\Scripts\ZTIConfigFile.vbs to C:\Users\bradm\AppData\Local\Temp\MDTUpdate.7256\Mount\Deploy\Scripts\ZTIConfigFile.vbs

Copy: \\imageserver\mdt\deploymentimage\Scripts\ZTIGather.wsf to C:\Users\bradm\AppData\Local\Temp\MDTUpdate.7256\Mount\Deploy\Scripts\ZTIGather.wsf

Copy: \\imageserver\mdt\deploymentimage\Scripts\ZTIGather.xml to C:\Users\bradm\AppData\Local\Temp\MDTUpdate.7256\Mount\Deploy\Scripts\ZTIGather.xml

Copy: \\imageserver\mdt\deploymentimage\Scripts\Wizard.hta to C:\Users\bradm\AppData\Local\Temp\MDTUpdate.7256\Mount\Deploy\Scripts\Wizard.hta

Copy: \\imageserver\mdt\deploymentimage\Scripts\Credentials_ENU.xml to C:\Users\bradm\AppData\Local\Temp\MDTUpdate.7256\Mount\Deploy\Scripts\Credentials_ENU.xml

Copy: \\imageserver\mdt\deploymentimage\Scripts\Credentials_scripts.vbs to C:\Users\bradm\AppData\Local\Temp\MDTUpdate.7256\Mount\Deploy\Scripts\Credentials_scripts.vbs

Copy: \\imageserver\mdt\deploymentimage\Scripts\WizUtility.vbs to C:\Users\bradm\AppData\Local\Temp\MDTUpdate.7256\Mount\Deploy\Scripts\WizUtility.vbs

Copy: \\imageserver\mdt\deploymentimage\Scripts\Wizard.css to C:\Users\bradm\AppData\Local\Temp\MDTUpdate.7256\Mount\Deploy\Scripts\Wizard.css

Copy: \\imageserver\mdt\deploymentimage\Scripts\Wizard.ico to C:\Users\bradm\AppData\Local\Temp\MDTUpdate.7256\Mount\Deploy\Scripts\Wizard.ico

Copy: \\imageserver\mdt\deploymentimage\Scripts\BackButton.jpg to C:\Users\bradm\AppData\Local\Temp\MDTUpdate.7256\Mount\Deploy\Scripts\BackButton.jpg

Copy: \\imageserver\mdt\deploymentimage\Scripts\plusicon.gif to C:\Users\bradm\AppData\Local\Temp\MDTUpdate.7256\Mount\Deploy\Scripts\plusicon.gif

Copy: \\imageserver\mdt\deploymentimage\Scripts\minusico.gif to C:\Users\bradm\AppData\Local\Temp\MDTUpdate.7256\Mount\Deploy\Scripts\minusico.gif

Copy: \\imageserver\mdt\deploymentimage\Scripts\Summary_Definition_ENU.xml to C:\Users\bradm\AppData\Local\Temp\MDTUpdate.7256\Mount\Deploy\Scripts\Summary_Definition_ENU.xml

Copy: \\imageserver\mdt\deploymentimage\Scripts\Summary_scripts.vbs to C:\Users\bradm\AppData\Local\Temp\MDTUpdate.7256\Mount\Deploy\Scripts\Summary_scripts.vbs

Copy: \\imageserver\mdt\deploymentimage\Scripts\LTICleanup.wsf to C:\Users\bradm\AppData\Local\Temp\MDTUpdate.7256\Mount\Deploy\Scripts\LTICleanup.wsf

Copy: \\imageserver\mdt\deploymentimage\Scripts\BDD_Welcome_ENU.xml to C:\Users\bradm\AppData\Local\Temp\MDTUpdate.7256\Mount\Deploy\Scripts\BDD_Welcome_ENU.xml

Copy: \\imageserver\mdt\deploymentimage\Scripts\WelcomeWiz_Choice.xml to C:\Users\bradm\AppData\Local\Temp\MDTUpdate.7256\Mount\Deploy\Scripts\WelcomeWiz_Choice.xml

Copy: \\imageserver\mdt\deploymentimage\Scripts\WelcomeWiz_Choice.vbs to C:\Users\bradm\AppData\Local\Temp\MDTUpdate.7256\Mount\Deploy\Scripts\WelcomeWiz_Choice.vbs

Copy: \\imageserver\mdt\deploymentimage\Scripts\WelcomeWiz_DeployRoot.xml to C:\Users\bradm\AppData\Local\Temp\MDTUpdate.7256\Mount\Deploy\Scripts\WelcomeWiz_DeployRoot.xml

Copy: \\imageserver\mdt\deploymentimage\Scripts\WelcomeWiz_DeployRoot.vbs to C:\Users\bradm\AppData\Local\Temp\MDTUpdate.7256\Mount\Deploy\Scripts\WelcomeWiz_DeployRoot.vbs

Copy: \\imageserver\mdt\deploymentimage\Scripts\WelcomeWiz_Initialize.xml to C:\Users\bradm\AppData\Local\Temp\MDTUpdate.7256\Mount\Deploy\Scripts\WelcomeWiz_Initialize.xml

Copy: \\imageserver\mdt\deploymentimage\Scripts\WelcomeWiz_Initialize.vbs to C:\Users\bradm\AppData\Local\Temp\MDTUpdate.7256\Mount\Deploy\Scripts\WelcomeWiz_Initialize.vbs

Copy: \\imageserver\mdt\deploymentimage\Scripts\SelectItem.jpg to C:\Users\bradm\AppData\Local\Temp\MDTUpdate.7256\Mount\Deploy\Scripts\SelectItem.jpg

Copy: \\imageserver\mdt\deploymentimage\Scripts\WelcomeBanner.jpg to C:\Users\bradm\AppData\Local\Temp\MDTUpdate.7256\Mount\Deploy\Scripts\WelcomeBanner.jpg

Copy: \\imageserver\mdt\deploymentimage\Scripts\btnout.png to C:\Users\bradm\AppData\Local\Temp\MDTUpdate.7256\Mount\Deploy\Scripts\btnout.png

Copy: \\imageserver\mdt\deploymentimage\Scripts\btnover.png to C:\Users\bradm\AppData\Local\Temp\MDTUpdate.7256\Mount\Deploy\Scripts\btnover.png

Copy: \\imageserver\mdt\deploymentimage\Scripts\btnsel.png to C:\Users\bradm\AppData\Local\Temp\MDTUpdate.7256\Mount\Deploy\Scripts\btnsel.png

Copy: \\imageserver\mdt\deploymentimage\Scripts\LTIGetFolder.wsf to C:\Users\bradm\AppData\Local\Temp\MDTUpdate.7256\Mount\Deploy\Scripts\LTIGetFolder.wsf

Copy: \\imageserver\mdt\deploymentimage\Scripts\NICSettings_Definition_ENU.xml to C:\Users\bradm\AppData\Local\Temp\MDTUpdate.7256\Mount\Deploy\Scripts\NICSettings_Definition_ENU.xml

Copy: \\imageserver\mdt\deploymentimage\Scripts\ZTINicUtility.vbs to C:\Users\bradm\AppData\Local\Temp\MDTUpdate.7256\Mount\Deploy\Scripts\ZTINicUtility.vbs

Copy: \\imageserver\mdt\deploymentimage\Scripts\ZTINicConfig.wsf to C:\Users\bradm\AppData\Local\Temp\MDTUpdate.7256\Mount\Deploy\Scripts\ZTINicConfig.wsf

Copy: \\imageserver\mdt\deploymentimage\Scripts\BackButton.png to C:\Users\bradm\AppData\Local\Temp\MDTUpdate.7256\Mount\Deploy\Scripts\BackButton.png

Copy: \\imageserver\mdt\deploymentimage\Scripts\FolderIcon.png to C:\Users\bradm\AppData\Local\Temp\MDTUpdate.7256\Mount\Deploy\Scripts\FolderIcon.png

Copy: \\imageserver\mdt\deploymentimage\Scripts\ItemIcon1.png to C:\Users\bradm\AppData\Local\Temp\MDTUpdate.7256\Mount\Deploy\Scripts\ItemIcon1.png

Copy: \\imageserver\mdt\deploymentimage\Scripts\MinusIcon1.png to C:\Users\bradm\AppData\Local\Temp\MDTUpdate.7256\Mount\Deploy\Scripts\MinusIcon1.png

Copy: \\imageserver\mdt\deploymentimage\Scripts\PlusIcon1.png to C:\Users\bradm\AppData\Local\Temp\MDTUpdate.7256\Mount\Deploy\Scripts\PlusIcon1.png

Copy: \\imageserver\mdt\deploymentimage\Scripts\SelectItem.png to C:\Users\bradm\AppData\Local\Temp\MDTUpdate.7256\Mount\Deploy\Scripts\SelectItem.png

Copy: \\imageserver\mdt\deploymentimage\Scripts\header-image.png to C:\Users\bradm\AppData\Local\Temp\MDTUpdate.7256\Mount\Deploy\Scripts\header-image.png

Copy: \\imageserver\mdt\deploymentimage\Scripts\NavBar.png to C:\Users\bradm\AppData\Local\Temp\MDTUpdate.7256\Mount\Deploy\Scripts\NavBar.png

Copy: \\imageserver\mdt\deploymentimage\Scripts\Computer.png to C:\Users\bradm\AppData\Local\Temp\MDTUpdate.7256\Mount\Deploy\Scripts\Computer.png

Copy: \\imageserver\mdt\deploymentimage\Scripts\WelcomeWiz_Background.jpg to C:\Users\bradm\AppData\Local\Temp\MDTUpdate.7256\Mount\Deploy\Scripts\WelcomeWiz_Background.jpg

Copy: \\imageserver\mdt\deploymentimage\Scripts\DeployWiz_Administrator.png to C:\Users\bradm\AppData\Local\Temp\MDTUpdate.7256\Mount\Deploy\Scripts\DeployWiz_Administrator.png

Copy: \\imageserver\mdt\deploymentimage\Tools\x86\BDDRUN.exe to C:\Users\bradm\AppData\Local\Temp\MDTUpdate.7256\Mount\Windows\system32\BDDRUN.exe

Copy: \\imageserver\mdt\deploymentimage\Tools\x86\WinRERUN.exe to C:\Users\bradm\AppData\Local\Temp\MDTUpdate.7256\Mount\Deploy\Tools\x86\WinRERUN.exe

Copy: \\imageserver\mdt\deploymentimage\Tools\x86\CcmCore.dll to C:\Users\bradm\AppData\Local\Temp\MDTUpdate.7256\Mount\Deploy\Tools\x86\CcmCore.dll

Copy: \\imageserver\mdt\deploymentimage\Tools\x86\CcmUtilLib.dll to C:\Users\bradm\AppData\Local\Temp\MDTUpdate.7256\Mount\Deploy\Tools\x86\CcmUtilLib.dll

Copy: \\imageserver\mdt\deploymentimage\Tools\x86\Smsboot.exe to C:\Users\bradm\AppData\Local\Temp\MDTUpdate.7256\Mount\Deploy\Tools\x86\Smsboot.exe

Copy: \\imageserver\mdt\deploymentimage\Tools\x86\SmsCore.dll to C:\Users\bradm\AppData\Local\Temp\MDTUpdate.7256\Mount\Deploy\Tools\x86\SmsCore.dll

Copy: \\imageserver\mdt\deploymentimage\Tools\x86\TsCore.dll to C:\Users\bradm\AppData\Local\Temp\MDTUpdate.7256\Mount\Deploy\Tools\x86\TsCore.dll

Copy: \\imageserver\mdt\deploymentimage\Tools\x86\TSEnv.exe to C:\Users\bradm\AppData\Local\Temp\MDTUpdate.7256\Mount\Deploy\Tools\x86\TSEnv.exe

Copy: \\imageserver\mdt\deploymentimage\Tools\x86\TsManager.exe to C:\Users\bradm\AppData\Local\Temp\MDTUpdate.7256\Mount\Deploy\Tools\x86\TsManager.exe

Copy: \\imageserver\mdt\deploymentimage\Tools\x86\TsmBootstrap.exe to C:\Users\bradm\AppData\Local\Temp\MDTUpdate.7256\Mount\Deploy\Tools\x86\TsmBootstrap.exe

Copy: \\imageserver\mdt\deploymentimage\Tools\x86\TsMessaging.dll to C:\Users\bradm\AppData\Local\Temp\MDTUpdate.7256\Mount\Deploy\Tools\x86\TsMessaging.dll

Copy: \\imageserver\mdt\deploymentimage\Tools\x86\TsmBootstrap.exe to C:\Users\bradm\AppData\Local\Temp\MDTUpdate.7256\Mount\Deploy\Tools\x86\TsmBootstrap.exe

Copy: \\imageserver\mdt\deploymentimage\Tools\x86\TsProgressUI.exe to C:\Users\bradm\AppData\Local\Temp\MDTUpdate.7256\Mount\Deploy\Tools\x86\TsProgressUI.exe

Copy: \\imageserver\mdt\deploymentimage\Tools\x86\TSResNlc.dll to C:\Users\bradm\AppData\Local\Temp\MDTUpdate.7256\Mount\Deploy\Tools\x86\TSResNlc.dll

Copy: \\imageserver\mdt\deploymentimage\Tools\x86\CommonUtils.dll to C:\Users\bradm\AppData\Local\Temp\MDTUpdate.7256\Mount\Deploy\Tools\x86\CommonUtils.dll

Copy: \\imageserver\mdt\deploymentimage\Tools\x86\ccmgencert.dll to C:\Users\bradm\AppData\Local\Temp\MDTUpdate.7256\Mount\Deploy\Tools\x86\ccmgencert.dll

Copy: \\imageserver\mdt\deploymentimage\Tools\x86\msvcp120.dll to C:\Users\bradm\AppData\Local\Temp\MDTUpdate.7256\Mount\Deploy\Tools\x86\msvcp120.dll

Copy: \\imageserver\mdt\deploymentimage\Tools\x86\msvcr120.dll to C:\Users\bradm\AppData\Local\Temp\MDTUpdate.7256\Mount\Deploy\Tools\x86\msvcr120.dll

Copy: \\imageserver\mdt\deploymentimage\Tools\x86\00000409\tsres.dll to C:\Users\bradm\AppData\Local\Temp\MDTUpdate.7256\Mount\Deploy\Tools\x86\00000409\tsres.dll

Copy: \\imageserver\mdt\deploymentimage\Tools\x86\Microsoft.BDD.Utility.dll to C:\Users\bradm\AppData\Local\Temp\MDTUpdate.7256\Mount\Deploy\Tools\x86\Microsoft.BDD.Utility.dll

Copy: C:\dml\batman.bmp to C:\Users\bradm\AppData\Local\Temp\MDTUpdate.7256\Mount\Windows\system32\winpe.bmp

Copying WIM to the deployment share.

Creating an ISO.

Copying ISO to the deployment share.

　

=== Completed processing platform x86 ===

　

=== Making sure the deployment share has the latest x64 tools ===

　

=== Processing complete ===

　

　

↧
↧

"Please Fix All Error Before Continuing "

June 20, 2016, 3:19 am
$
0
0

Hi All,

I am trying to Install Windows-10 using MDT. While I was importing the OS (Windows-10) I just get the following error "Please Fix All Error Before Continuing ".

Can anyone assist me on this.

↧

MDT 2013 Update2 :Unable to split image and generate ISO

June 20, 2016, 9:08 pm
$
0
0

Hi,

Im trying to split the wim file in order to support UEFI deployment i tried below option still dint work.

1.Tried manually to split wim file and apply but no luck

2.In MDT 2013 Update 2, we can split wim file by changing setting.xml under deployment share control folder and as well as in media. This option also did not work.

links:

https://social.technet.microsoft.com/Forums/en-US/7c5837d7-2906-4fa7-8182-d1760c7f8228/mdt-2013-update-2-is-not-splitting-wim?forum=mdt

https://social.technet.microsoft.com/Forums/en-US/d170bb4b-3588-45e1-997e-b4a4282b01c9/4gb-wim-not-being-split-when-creating-media-deployment-point-in-mdt-2013-update-2?forum=mdt

Request all to help me in on this.

Regards,

Suresh.MM

↧

Windows Script Host Error

June 20, 2016, 2:43 pm
$
0
0

I'm receiving this error when I PXE boot a Dell 5040 into LiteTouchx64.wim.  I'm using MDT 2012 Update 1 to deploy images using Task Sequences.  Any ideas what the issue could be?  I haven't made any changes to the LiteTouch.wsf file...


↧
↧

MDT 2013 Update 2 Monitoring errors

February 9, 2016, 11:48 am
$
0
0

We just upgraded our MDT server to Update 2.  After the update, monitoring is not longer working.  The service is running and the settings in cs.ini are correct.  The bdd.log on the client shows an error from the web service - "Unexpected response from web service: 400 Bad Request"

The monitoring service was working perfectly before upgrading to Update 2.  Has anyone seen this issue?

↧

Failure (5627): 50: Run DISM.exe when deploying Windows 10

June 22, 2016, 3:57 am
$
0
0

I got a issue with deploying Windows 10 in MDT. During the network boot of windows 10 it stops when its at 100% of the windows 10 operating system process. The error messege that comes up is:

FAILURE (5627): 50: Run DISM.exe

Litetouch deployment failed, return code = -2147467259 0x80004005

Failed to run the action: install Operating System

Unknownerror (Error: 000015FB; Source: Unknown)

The execution of the group (Install) has failed and the execution has been aborted. an action failed.

Unknown error (Error: 80004004; Source: Unknown)

Failed to run the last action: install operating system. Execution of task sequence failed.

Unknown error (000015FB; Source: Unknown)

Task seequence engine failed! Code: enExecutionFail

Task sequence execution failed with error code 8004005

Error task Sequence Manager failed to execute task sequence. Code 0x8004005

I'm not sure how i should go about fixing this so would be grateful for some help.

↧

Using a server deployment Task Sequence to add (and correctly letter) Drives.

June 22, 2016, 8:15 am
$
0
0

Hi

I'm having an issue with an MDT deployment task sequence in which I need to create and name a couple of extra partitions as part of the deployment.My machines all have two physical disks.

Disk zero should be partitioned with a 100GB OS partition as C: (this is happening) and a second partition which should be given E: as drive letter (via a task sequence variable).

Disk one has a single partition which should be given f: as the drive letter.

I've set up format and partition tasks for both drives (the first does the OSDisk and the E: partition the second the F: drive).

I can see both tasks run watching the the lite touch dialog box.

However once it is all complete there are two issues.

1. On disk zero although the drive volume is there and labelled correctly it hasn't picked up the drive letter variable and

2. Disk one is offline. when I bring it online however the volume is there and labelled correctly

This tells me that the volume creation is working fine but something happens that takes the second drive off line (and loses the drive letters).

Anyone have any suggestions how to fix this ?

Many thanks

John

↧
Search

Proper MDT Setup

June 15, 2016, 4:50 pm
$
0
0

I have MDT installed and have images built. My ip for mdt is 152.146.74.135

when i boot a system for a pxe boot it does not pull an ip address even though this is configured in dhcp

if i place the system onto a different dhcp server i do get a dhcp address.

what needs to be configured to allow me to see across subnets if i cant pull an ip address on the .74 range? i get an ip on a .54 address range.

↧
↧

Help with error 0x80070570. Images getting corrupt on target computers after image transfers

July 15, 2011, 8:56 am
$
0
0

So, changing the WDS Multicast settings to have all clients on the same transfer rate didn't help, as three out of 14 still failed. Sure this is better odds this time, but it could six that fail next time. I just don't understand how some computers would fail unpacking the image and others would unpack fine and not get any errors. I do want to think it is a network issue, but I've had this issue in other buildings that have thier own MDT server and have yet to find a resolution anywhere. I'm inclined to think it is an image issue, but then I point back to computers image successfully using the same image that other fail with. Could it be an image issue?

I did check the Permormance Monitor and I am seeing alot of Repair packet requests along with many Slow Down requests. Could it be that a packet didn't get repaired? I'm using WDS on Server 2008 R2, so I can't manually set the transfer rate like you can in Server 2008. I am also imaging using Windows 7 x64 Enterprise with SP1 and MDT 2010 Update 1.

I decided to start a new post so I didn't hijack an old one that had already been answered. For the back story, check this post. http://social.technet.microsoft.com/Forums/en-US/mdt/thread/25cc44ec-ca22-44a6-b093-86b6c8ffda5f/#a5206123-98ad-4f94-a536-9f7e8ab357f5

I need to get this figured out since I have very little time to waste. We have 1000 tablets to be completed imaging in two weeks. I've never had this problem before and it just showed up about a week or so ago. I've successfully imaged several hundred other computers using the same servers and networks without issue, granted they are the exact same models as these I'm having problems with. The image has changed slightly, but it shouldn't have changed that much. I only added one file using the imagex mountrw and unmount/commit, which from what I understand is exactly the reason it exists.

The image I used before that has Adobe CS5 in it, I created on a VM and captured by running the LiteTouch.vbs manually. I've done it that way many times in the past and had never had an issue, so I don't expect there to be an issue now.

I guess it is time for more testing and reporting. Any help anyone can offer would be greatly appriciated.

↧

How can i run a yes/no command which requires user input as part of my task sequence?

June 22, 2016, 5:30 pm
$
0
0

Hi All!

I created this batch file and placed in %scriptroot% to call the .bat but it does nothing when run in task sequence, i need it to open a window to ask the user to input Y or N as part of the final task.

Any ideas much appreciated, thanks :

Here is the question file:

@ECHO OFF

:choice
set /P c=Is this machine for THS UNIT? [Y/N]
if /I "%c%" EQU "N" goto :somewhere
if /I "%c%" EQU "Y" goto :somewhere_else
goto :choice


:somewhere

echo "blah blah"
pause 
exit

:somewhere_else


↧

Rebooting Issues with Deploying to a Optiplex 7040-Setup never completes.

January 25, 2016, 11:28 am
$
0
0

We are trying to use both MDT and SCCM to reimage this unit (Optiplex 7040). The imaging process completes normally. When the unit restarts, it goes into a constant Repair boot loop. I have rebooted it in safemode and then notice that on AMDKMPFD.sys, the unit will restart. Both deployments have been configured to use ONLY drivers for the 7040. Anyone had this issue?

I have created a MDT task sequence isolating the drivers for the 7040 and it still has the issue.

↧

Powershell Command IMPORT-TOPIC does not work.

April 28, 2016, 7:32 am
$
0
0

I'm using a guide that is telling to import a snap-in on a Windows 2012 R2 Server using the following command, but it does not work.

Import-Topic"C:\Program Files\Microsoft Deployment Toolkit\bin\MicrosoftDeploymentToolkit.psd1"

New-PSDrive -Name "DS001" -PSProvider MDTProvider -Root "E:\MDTBuildLab"

Should the command be Import Module ??? or perhaps a "add-pssnapin ????

Import-Module"C:\Program Files\Microsoft Deployment Toolkit\bin\MicrosoftDeploymentToolkit.psd1"

New-PSDrive -Name "DS001" -PSProvider MDTProvider -Root "E:\MDTBuildLab"

Michael Agee

↧
↧

Visual Studio Community 2015

June 23, 2016, 3:05 am
$
0
0

I have one error, code:X3000 "Illegal character in shader file". This problem is for all files .fx . How to fix this ? I learn DirectX11. I have a book "Introduction to 3D Game Programming with DirectX 11"(I'm from Poland,I have Polish book). For this book are examples to download and they didn't work by this error. 

↧

Multipe Deployment shares for each OS?

June 23, 2016, 4:07 am
$
0
0

Ok, i have inherited an already setup system from a previous employee.

They have created a separate deployment share for each OS, Win7 8 and 10.

Previously i have always put all OS deployments in the same share and setup different driver folders etc for the specific OS.

I have looked around Google etc and can't find any reason for having a separate deployment share for each OS, is this a correct conclusion or am i missing something?

↧
Search

Deploying Office 2016

June 23, 2016, 12:50 am
$
0
0

Hi.

I am trying to deploy Office 2016, but the installation stops at roughly 70%. Has anyone else experienced this problem? I can't find anyone reporting on this issue.

I am using this recipe for my Office 2016 deployment: http://renshollanders.nl/2015/10/office-365-get-office-365-wave-2016-now/

and it worked fine for the 2013 version.

↧

MDT 2013 Update 2 and Windows 10 custom image

June 21, 2016, 3:07 am
$
0
0
Is there a supported fix for the Dism return code 50 error when deploying Windows 10 images.
↧
↧

Failure (Err): 429: CreateObject(Microsoft.BDD.Utility) - ActiveX component Can't Create Object Windows 7 deployment

June 24, 2016, 10:59 am
$
0
0

Using WDS and MDT to deploy custom Windows 7 images.  I had a working image that needed a tweak (minor error messages on boot) or two before deploying to 500 machines, set up sysprep and capture after making the changes.  I can still deploy the previous image without any problems, new image fails each time. 

Currently, MDT deploys the image about 90% then fails with the relatively generic "Failure (Err): 429: CreateObject(Microsoft.BDD.Utility) - ActiveX component Can't Create Object" error message.  The machine never boots into windows, it's still deploying when it errors out.  Any help is greatly appreciated, i've tried to capture the image a second time, build a new task sequence from scratch and still having the issue.  Apparently I can't add links yet, so i've put the BDD log file on pastebin, with the following identifier: CzM1GKFb

Running Windows Server 2012, MDT version 6.3.8330.1000

I'm still able to use the previous image without any error, looking at task sequences I can't see anything different between them

↧

MDT OSD stalls at Applying Image

June 24, 2016, 11:46 am
$
0
0
Recently all of my OSD task sequences have been stalling at Applying Image. This is a recent occurrence and does not happen every time. Sometimes it will take 5-6 hours and it will finally install the OS, sometimes restarting the Deployment Server fixes the issue, other times I have to restart the deployment entirely. I have looked at the server side smsts.log and bdd.log but was unable to find any errors related to the issue.
↧

Problem importing multiple images to deployment share

June 24, 2016, 2:58 pm
$
0
0
Hi, I'm running into a problem while trying to import multiple OS images. The import is successful, however when I try to deploy to a VM the lite touch dialog closes while applying the OS. Looking at bdd.log I see a 5630 failure. I found the error is caused because the OS images are all imported using index 1. After I remove all the other images using the same image index deployment works as expected. I can't find any reason why all my images are being imported with the same index and haven't been able to find a fix. Has anyone come across this issue or can point me in the right direction?
↧
Viewing all 11297 articles
Browse latest View live
Search
<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>