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

Strange behavour of physical machine during MDT deployment

April 15, 2016, 6:46 am
$
0
0

Hi Guys

Hope someone can shed some light on this as it has me baffled.

Scenario is this

Replacing windows 32 bit with 64bit on our client machines, have USMT backing up the profiles to a network share (hardlink is to dangerous incase build fails)

our Task Sequence loads the USMT variables from our custome settings.ini everything works as expected until the following

This is our process

1) Log on to client pc (at this stage 32bit) as using a domain account that is part of the local admin group

2) browse to litetouch.vbs on our deployment share and run it

3) select to backup our profiles to the share created (i know i can automate this location in the cs.ini but for the moment during testing i am entering manually)

4) click next, choose not to backup pc and the task kicks off.

at this point as you would expect it gathers etc then moves onto the user state capture, i can see the usmt.mig file in my network share no worries all is good.

computer then boots into win pe and applies the 64 bit OS (all good)

finishes the os imaging and boots into pc as administrator (local) as expected and continues with the other task sequences that i have setup (install McAfee, sms agent then join domain)

mdt build completes and reports success.

Now the problem is that it hasn't brought back down the profiles from the network share so i did abit of testing.  I put a 10 minute pause into the task sequence just before the user state restore runs so i could check connectivity to network share.

at this point it prompts me for creds for the network share (even though it has Z: mapped to the same server.

The very odd thing is i did the exact same sequence as i have laid out above with a Virtual machine and during the 10 minute pause i created it does not ask me for creds for the network share that its USMT.mig is located (even though i am logged on as local admin) but when i run the sequence stated above on a physical PC it promts me for creds for the share.

Anyone seen this behavior before, i am absolutely stumped, i have made sure EVERYTHING is identical in the way i run the sequence (same domain account used, computer names never change, both use the same deployment share, both use the same share for the USMT files.

the only differences between the 2 are

1) one is virtual client and the other is a physical machine

2) one is on ip range .66 and the other is on .80

Any insights would be appreciated

↧
Search

Use MDT 2013 in Azure

April 28, 2016, 8:41 am
$
0
0

Hi.

I want to know if there is a possibility to use MDT 2013 to deploy Windows 10 from Azure.

I think it doesn´t have to be problems if I create a VM in Azure with WDS and MDT 2013, although I have to consider many factors:

  • Network connection site to site
  • Adjust DHCP and IP Helpers
  • Ports in the VM and endopoints in Azure
  • ...

Does anyone can help me with this?

Thanks in advance to everyone

Enrique

↧
↧

Unable to find the SMS Task Sequence. The deployment will not proceed.

March 13, 2014, 9:25 am
$
0
0

Hi,

After one week to work about my problem, I ask help !

I use MDT 2013 on Win 2012 R2 with WDS on Win 2012 R2.

I work, in this case, with Win 7 x64 as OS client OS.

I use VMWare to create my reference wim images.

I use my wim images to deploy new VMs and new PCs

Today I get an error when the PC reboot after installing devices :

Unable to find the SMS Task Sequence. The deployment will not proceed.

I'm not sure about what change between before and after : many things ! (OS (with WSUS Updates), Drivers, LiteTouch.wim, ...)

But I found something strange.

1) My deployments work fine if there is no formatted partition.

2) My deployments work fine if I deploy a VM (with no diag partition) if the VM is new or already with an OS

When I look my log files, in the litetouch.log, I found that the the DeployRoot is empty when the deployment fails and is \\PBCMDT.Cabinet-Besse.net\MDTProd$ when it succeeds.

I always use install operating system task sequence with : Use the next available formatted partition. In my build task sequence and in my prod task sequence.

I use a task sequence format and partition disk standard : disk 0, MBR, Create extra active partition and OSDisk (primary) 100% remaining space on disk in the build task sequence

I use the same parameters with the prod task sequence when the WMI Query report that I work with VMWare

I use a personal script in the format and partition disk with the prod task sequence when the WMI Query report that I work with Dell. This script use diskpart to delete partition 3 and 2 and create two new partitions (with the right size) leaving the hidden diags partition.

Could you help me ?
One week it is a very long duration to repair MDT !

Ludovic.

↧

MDT 2012 - Surface Pro 2 - Task Sequence Suddenly Failing at Format and Partition Disk

April 20, 2016, 6:54 am
$
0
0

Please help!!

We've had Surface Pro's within our environment for the past 2 years. We have a mixture of Surface Pro 2 and 3 and have a standard task sequence in MDT 2012 that deploys a standard Windows 8.1 OS. We have made no modifications to the Task Sequence, OS OR Drivers.

At first we believed it may be HardDrive related, but now we have 3x Surface Pro 2's that all fails at the same stage. These Surface Pro 2's where initially imaged using the same task sequence and was successful, however this was several months ago.

We are re-imaging these devices for re-deployment and fails at Format and Partition Disk portion of the task sequence.

It stays at the stage:

Running Action: Format and Partition Disk / Preparing Disk 0 Partitions ... for approx. 2 mins

Then returns error:

ZTI ERROR - Unhandled error returned by ZTIDiskpart: Object required (424)

Litetouch deployment failed, Return Code = -2147467259 0x80004005

I've also attached the image of our Task Sequence for reference

We have Microsoft Deployment Toolkit 2012 Update 1

and Microsoft Deployment Workbench Version 6.2.5019.0

Any Help would be greatly appreciated!

↧

MDT Stops with Blank Wizard.hta No logs

April 28, 2016, 10:56 am
$
0
0

I am having trouble with a task sequences that installs windows 10 with bitlocker. The sequence has worked many times before but on a Dell Precision 7510 is stops just before the Bitlocker enable step with a blank Wizard.hta showing. The administrator\appdate\local\temp\ folder only has a smsts.log file which is duplicated in a smstslog folder. The smsts.log file shows the task sequence running and going into the STATERESTORE mode. It then shows that ZTIGather.wsf comes back with an error code of 1 and then the sequence fails with error code 80004005. There are no other logs and if I close the blank Wizard.hta the TS removes the minint folder and ends. No logs are written back to the logging folder in the usual place. The Deployment Workbench Monitoring show the Task Sequence for the new computer as Running until I delete it.

Any clues?

Things are the way they are because that is the way they are.

↧
↧

Unable to launch MDT 2013 task sequence

April 28, 2016, 11:10 am
$
0
0

Hello,

I am having trouble creating a Windows 7x64 WIM in MDT 2013.  I created a LiteTouchPE_x64.ISO from MDT share then used VM to boot up from this ISO.  All I see is boot up to X:\Windows\System32 command prompt with the Solution Accelerators blue background .  I didn't find any solution from Internet which could help me to go pass this situation.  Some stated disable Antivirus, some stated delete the boot folder then run Update MDT Development shared to recreate the ISO, some even stated to recreate MDT shared from scratch.  It seems like I am missing something from MDT configuration.  Anyone has any suggestion? 

↧

A connection to the deployment share could not be made. Network routing error or network configuration error

December 11, 2013, 5:08 am
$
0
0

I have been using MDT for some time without much trouble. Yesterday I was able to PXE boot a machine without a hitch. It brought me to the MDT wizard and I wanted to start a new deployment. After approximately 3 minutes I received an error stating that the connection to the deployment share could not be made."Can not reach deploy root. Possible cause:Network routing error or Network Configuration error"

Anyone who can provide any assistance it would be appreciated. Nothing was done to the network to bring about this error. I checked the bootstrap.ini and it's correct. Thanks in advance for any assistance.

Bob

↧

No GPO Templates folders?

April 28, 2016, 10:41 am
$
0
0
I've got my first deployment share all ready to go and the last step I need is to be able to create and apply a GPO Package. I've already created a baseline in SCM but when I look to my Deployment share my Templates folder is empty. Everything I'm reading online says I should have a few folders in there of default GPO Packages from which I will need to copy some specific files in order to create my custom GPO Package. Any ideas why I have nothing in this folder?
↧
Search

Disable Legal Notice in MDT Windows 10 Deploy?

April 27, 2016, 3:32 am
$
0
0

Is there a way to disable/bypass then re-enable the domain GPO security screen during MDT deployment of Windows 10 so that
the task can continue uninterrupted? I have it working for Windows 7 and it's a great feature.
Thanks!


What I eventually hope to do is have the Administrator boot right to the desktop without stopping
at the security banner or having to enter the password. I've got the p/w in the unattend as usual but
it stops at the notice and makes me click OK then choose Local Account and sign in as Admin.
Not completely efficient.
↧
↧

Unable to invoke application 'wscript.exe X:\deploy\Scripts\LiteTouch.wsf

April 28, 2016, 6:19 pm
$
0
0

Hi,

I created a new LiteTouchPE_x64.iso from MDT 2013.  After I boot up from VM, it stopped at X:\windows\system32 within command prompt.  It does not launch MDT Task Sequence for me to capture the WIM.  On X:\windows\system32 folder, I notice below error in winpeinit.log.  Any suggestion?

Brian

↧

WinPE-MDAC-Package Error: 0x80070005

April 28, 2016, 3:59 pm
$
0
0

Hi,

I received below error when I update Deployment Shared in MDT 2013.  It looks like the update completed and created new LiteTouchPE_x64.ISO and LiteTouchPE_x64.wim.  However, when I used VM to boot from this ISO, it stopped at X:\windows\system32 in command prompt.  Any idea?

[===========================67.3%=======                   ]
[===========================69.5%========                  ]
[===========================71.7%=========                 ]
[===========================74.0%==========                ]
[===========================74.0%==========                ]
[==========================100.0%==========================]
An error occurred - WinPE-MDAC-Package Error: 0x80070005
Error: 5
Access is denied.
The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log
Exit code = 5
DISM /Add-Package failed for component C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Windows Preinstallation Environment\amd64\WinPE_OCs\winpe-mdac.cab, rc = 5.
Added component winpe-mdac
Deployment Image Servicing and Management tool
Version: 10.0.10586.0
Image Version: 10.0.10586.0
Found 1 driver package(s) to install.
Installing 1 of 1 - E:\MDT\Out-of-box Drivers\Net\Ax88772_3.10.3.13_3B1780F670228607377C2CE99F7C5B227CE5C2E3C34F59637D3289A906CFDCE6\Ax88772.inf:
INFO: DISM has skipped driver signature check because the version of running OS and that of target OS do not match.
Error - An error occurred. The driver package could not be installed.
For more information, check for log files in the <windir>\inf folder of the target image.
Error: 5
Access is denied.
The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log
Exit code = 5
DISM /Add-Driver failed, rc = 5.
Injected driver ASIX Net Ax88772.inf 3.10.3.13

An error occurred - WinPE-MDAC-Package Error: 0x80070005
Error: 5

↧

One USB for two Deployment Shares

April 28, 2016, 9:46 pm
$
0
0

I have two deployment shares (one has a UEFI Win8 image deploy) and one has an NTFS deploy share for Win7. I'm using this template below but its on one server, not two. I see both shares in the drop-down, but both drop-downs take me to the Win7 deploy share. I have to copy a Litetouch wim to the USB, but which wim do I copy? I copied the Win7 wim and I see those deploy TS's but under the other drop-down, I still only see the same Win7 TS's. My goal is to use one USB for two separate Deploy Shares on the same server.

<?xmlversion="1.0"encoding="utf-8"?>
<servers>
    <QueryDefault></QueryDefault>
    <server>
        <serverid>1</serverid>
        <friendlyname>
          ViaMonstra HQ, New York, USA
        </friendlyname>
        <UNCPath>\\MDT01\MDTProduction$</UNCPath>
    </server>
    <server>
        <serverid>2</serverid>
        <friendlyname>
          ViaMonstra BO, Stockholm, Sweden
        </friendlyname>
        <UNCPath>\\MDT02\MDTProduction$</UNCPath>
    </server>
</servers>

↧

How to enable Windows 10 Enterprise Bitlocker using MDT 2013 Update 1

April 29, 2016, 5:38 am
$
0
0

Deploying Windows 10 Enterprise using MDT 2013 Update 1.

Can anyone point me to step by step on what needs to be done on the customsettings.ini and task sequences?

Thank you all!

↧
↧

MDT 2012 database Upgrade to MDT 2013 U2

April 29, 2016, 1:58 pm
$
0
0

Hello,

Our production MDT share is version 2012. If I install the new version of MDT 2013U2 will my MDT 2012 Database up graded also? Or do I need to just recreate the DB?

Thanks

↧

Surface Pro background problem

April 22, 2016, 11:36 am
$
0
0

With MDT & Windows 10 we have been replacing the img0.jpg file in C:\windows\web\wallpaper\windows with our custom image during the WinPE phase so we don’t have to mess with permissions. This has been working fine until we started working with the Surface Pro 3. The higher resolution screens for some reason are using the default Windows background instead of our custom one, not sure where it’s even coming from. The weird thing is if we change the resolution to 1920x1200 then it shows our image but if I change the resolution to the default 2160X1440 then it shows the default windows image. Any ideas?

↧
Search

Setting Up Windows 10 with MDT

April 29, 2016, 12:48 pm
$
0
0

Hi Everyone,

We have been using MDT 2013 Update 1 for a few months now with no issues using Windows 7. We now have plans to move all the systems to Windows 10 which will also require us to set up the imaging process which we are having trouble with.

I got two versions of Windows 10 from Dell, one is the "OEM" CD and the other is the USB. When I upload them to MDT they are identified as "Microsoft Windows Recovery .... for Windows 10 Pro". What I did is I took an existing task sequence that gives the system drivers/installs OS/adds local admin account/installs applications (in this case I selected no applications to be installed)/joins the system to domain as the very last step. However, we are keep getting stuck right after installing the OS. After MDT finishes installing OS it reboots and takes us to the screen that asks to select the language and the keyboard layout. After we select Englush/US layout and click continue it takes us back to the same screen and so on. This happens regardless of if we shut down the system.

My question is if anyone has seen this issue and if you know how we should go about getting around this and preferably skip that setup all together so MDT can continue to image. Ideally I would want it to act same as Windows 7 where no interaction is needed with the system. I should also mention that we are pretty much using the standard template and we simply added few cmd line procedures for the service account and etc.


↧

A quick hint on how I'm supposed to use MDT 2013 for Windows 8.1 deployment.

April 29, 2016, 10:23 pm
$
0
0

Hello,

I asked a question earlier on technet but I believe I was in the wrong sub-forum.   I have a need to deploy fully updated Windows 8.1 images to customer's PCs.   In Windows 7, I'd just startup a virtual machine, start installing 7, boot into Audit Mode, update the machine through Windows Update, sysprep the machine, capture the image, replacing install.wim on the 7 installation medium with my captured image and when I'd install 7 on a machine, it'd be fully updated.   I'd create an answer file to do various things, like partition the drives, etc.


It seems with 8 and 8.1 though, things have changed a good bit.   I tried what I used to do with 7, but when I replaced the Windows 8.1 install.esd file with my custom captured install.swm and install2.swm file, Windows setup wouldn't accept the product key.

Someone suggested I use the MDT 2013.   Could someone please give me a rough idea of how I'm supposed to create a master and reference image to deploy Windows 8.1?   I will probably be deploying 8.1 via a thumb drive, although I'm okay with a network deployment.   Any help would be greatly appreciated.   Thank you.

Spork Schivago


↧
↧

Can not find script file "c:\LTIBootstrap.vbs". Cant make a REF image.

April 29, 2016, 7:59 pm
$
0
0

I must have done something. I had a nice working MDT-Build share with a Task Sequence with a Suspend action where I installed applications like Chrome and so on (I knooow its a better way to do it!)..

When I try to make a new Image, it wont Capture it. I deploys the OS itself it seems with following error: 
Can not find script file "c:\LTIBootstrap.vbs" The file do exist in the Deploymentshare. It DID work before to make Ref images.Im sure I have done something.. Its a lab env. Gen2 machine.

Using latest MDT and Server 2012r2 with latest updates.

↧

Windows could not parse or process unattend answer file.. Ref image error.

April 30, 2016, 1:28 pm
$
0
0

I did a ref image in my mdt-build share, and imported the finished images with "hardinstalled" applications and fully updated, into my mdt-production share. And it applied just fine, but after I am getting:

My Rules looks like this, I guess it have nothing to do with the rules, but who knows..

[Settings]
Priority=Default
Properties=MyCustomProperty

[Default]
OSInstall=Yes
SkipCapture=YES
SkipAdminPassword=YES
SkipProductKey=YES
SkipComputerBackup=YES
SkipBitLocker=YES


SkipComputerName=YES
OSDComputerName=PC-#Left(“%SerialNumber%”,12)#

SkipDomainMembership=YES
JoinDomain=xxx.us
DomainAdmin=xxx
DomainAdminDomain=xxx
DomainAdminPassword=xxx!

SkipUserData=YES


SkipLocaleSelection=YES
SkipTimeZone=YES
KeyboardLocalePE="041d:0000041d"
KeyboardLocale= "sv-SE,041d:0000041d"
UserLocale= sv-SE
UILanguage= en-US
TimeZoneName=W. Europe Standard Time



↧

SFB issues in IOS Device after March 2016 CU Update

April 28, 2016, 4:28 am
$
0
0

Hello Team,

This is to update you that recently i have upgraded the March 2016 CU for my SFB Server and found that still i am facing issues while doing an audio and video calls from Iphone Mobile device. Whereas from any Android device i am not facing such issues.

* From Iphone mobile using Skype for Business APP cannot make audio and video calls to the external federated contacts. Sometimes the chat also didn't responds and sometimes chat works.

* In Android device i am able to do IM , AUDIO , VIDEO calls without any issue with external federated contacts.

I am afraid how to solve this issue from IOS side. Can anyone help me in this to troubleshoot the issue.

Any help on the same will be appreciated.

↧
Viewing all 11297 articles
Browse latest View live
Search
<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>