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

MDT: Updating Deployment Share

$
0
0

We have the following computers in our environment where we are deploying Windows 10:


We purchased some new HP 800 G2 SFF desktops to deploy. The 800 G1 series had no issue with deployment at all, but the 800 G2 appeared to drop the network driver right after connecting to the Deployment Share. 

I could go through and connect to the deployment share \\cxx\e$\deploymentshare fine - but when I attempted to log in with my admin login, it would say "invalid credentials the network location cannot be reached". After pressing F8 and typing net use \\cxx\e$\deploymentshare /user:admin1 <password> - same as what is specified in the .ini file:

UserID=admin
UserDomain=<domain>
UserPassword=<password>

But it doesn't connect. ipconfig bring's up nothing, and pinging didn't do anything either. Latest drivers were grabbed from http://h20564.www2.hp.com/hpsc/swd/public/readIndex?sp4ts.oid=7633279 and uploaded to MDT but I hadn't updated the deployment share. 

I ran the update for the deployment share yesterday, and it went through overnight. I've come in this morning and it's on this screen and has been for the past two hours:

Is it just taking a very long time, or is it actually frozen/stuck? What can I do to nudge it along? And will updating the deployment share actually fix the issue? 

Thanks. 


Error creating an image of drive D:, rc = 161

$
0
0

Hello,

When I want to capture an image with MDT 2013 it will get te following error:

Error creating an image of drive D:, rc = 161
ZTI ERROR - Non-zero return code by ZTIBackup, rc = 161
Litetouch deployment failed, Return Code = -2147467259 0x80004005

After I click on ''Finish'' the PC tries to reboot, but it only gets the error that it can't complete the configuration.

Can anyone help me? 

MDT 2013 Update 2 - Will not join to the domain

$
0
0

We are using MDT 2013 Update 2, running a  Windows 10 Bitlocker Task Sequence.(We have the Feb 2016 Windows 10 iso)

Recently my deployment has stopped joining machines to the domain with no changes to it. I want to check all avenues and understand what possible changes I could look at in our environment that could cause this, policy for example.

The domain join is the 1st to last of the task sequence. The last is an MBAM Encryption script that also has stopped working since the domain join has stopped as well. I am not aware of any logs to check besides Event Viewer since the machine is no longer in WinPE but is actually logged into the desktop. There is no MINNIT folder. 


MDT Questions

$
0
0

hi I have been using MDT for several months now and have a few general questions. 

Whats the best practice for deploying 3 different images example we have 3 business units that all have different apps so we have created 3 different reference images.  My questions are because I have fully automated the deployment i dont have the choice to choose which image I want to install.   

Whats the best way to deploy 3 different images.


Thanks 

Nick 


MDT 2013 Update 2 - Bugs

$
0
0

I wanted to see if anyone else has experienced any similar bugs as myself when deploying a Windows 10 image. I would also like some information on Best Practices for manages Deployment Shares on MDT. I found a few articles myself but the more the merrier. 

Issues we have been having with deploying Windows 10 with MDT 2013. These issues occur on every device we are using, SSD & HHD.

1. Image appears to pause and you either have double click the taskbar or go into the MININT folder and start Litetouch to continue deployment.

2. This may not be an MDT issue, but once we image the machine we get an error stating when trying to login with our domain credentials on our SmartCards "Provider could not perform the action since the context was acquired as silent". To resolve this at the present moment, we are using our elevated rights on our card to login and repairing the software ActivClient.

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

$
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!

Cannot import wim into Operating Systems node

$
0
0

I'm using MDT 2013 U2 and ADK v10.1.10586.  Yesterday I was able to import captured images fine, today when I try to import a newly captured wim it gets copied to the .\Operating Systems\ directory, but .\Control\operatingsystems.xml is not updated. 

I have tried renaming operatingsystems.xml to operatingsystems.xml_bak, reopening the Workbench, a new operatingsystems.xml is created but when I re-attempt the import same issue, the wim is copied fine but the xml is not updated. 

Any ideas?

Powershell commands to change operating system image in task sequence

$
0
0

Hello,

I am looking for a way to script changing a task sequence to use a different OS image file. So far the only thing I can find using the powershell MDT module is the "import-mdttasksequence" command, but it looks like that can only create a whole new task sequence.

My end goal is to automate our master image builds  and the last step is to take the captured master wim file, import it into the Operating Systems folder, and then update the associated custom image task sequence to use that new OS image. With"import-mdttasksequence" I have to create a new task sequence with a new ID, when I already have one present that would be easier to just update to point to a different OS image. I do not see anyway to edit task sequence steps using the powershell module.

Is this possible? Maybe using Get-Item to get the OS GUID and then editing the task sequence XML file directly?

MDT 2013
Server 2008 R2

Regards,
Darren


Black Screen w/Mouse Pointer or Immensely Long Login Times

$
0
0

Hi,

I'm trying to deploy Windows 10 Enterprise LTSB and my deployment task fails in several areas. The built-in administrator account shows nothing when logged in but a black screen and a mouse pointer. Logging in as another local user sees the log in process hang on "Preparing Windows" or just take a ridiculously long time >10 minutes to arrive at that same black screen. 10 minutes for a default user profile that is 29MB in size. What is making it take so long. LTSB doesn't have any of the useless Windows Store crap (that's why we chose it), so it cannot be setting that up. No Cortana, so what is it doing? The domain-join part of the task sequence failed, the computer didn't even get the name I specified in the wizard. 


Jason

MDT 2013 U1 Windows 10 Refresh

$
0
0

I am trying to create MDT Task sequence to refresh windows 7 to Windows 10

-But I need to customize the USMT XML Files to Migrate

1. Users Profiles

2. Hosts Files

And create the Usmt Backup store locally to D Drive

ZTI Error - Unhandled error retuned by LTI Apply; Invalid procedure call or argument (5)

$
0
0

Hi

When am trying to deploy any image from MDT 2012, am geting below error.

can some help me on this please...

Unhandled error retuned by LTI Apply; Invalid procedure call or argument (5)

Thank's in advance..

DeploymentScripts\Wizard.hta (Win10) Not Running

$
0
0

Hello,

I am using MDT to deploy a Windows 10 image to a test device. After the imaging process the machine logs into the Administrator account where usually the Deployment Wizard should launch and complete the MDT deployment, following a successful message or errors. However, after the device auto logs into the Administrator account to complete MDT, I am presented with a blank Wizard.hta screen. I followed the path to where the Wizard.hta is launching from and the folder is empty.

Folder = C:\Users\ADMINI~1\AppData\Local\Temp\DeploymentScripts\Wizard.hta

I also located the log file and found this: (Wizard.log)

<![LOG[Property LogPath is now = C:\MININT\SMSOSD\OSDLOGS]LOG]!><time="15:39:25.000+000" date="03-14-2016" component="Wizard" context="" type="1" thread="" file="Wizard"><![LOG[Microsoft Deployment Toolkit version: 6.3.8330.1000]LOG]!><time="15:39:25.000+000" date="03-14-2016" component="Wizard" context="" type="1" thread="" file="Wizard"><![LOG[Property Debug is now = FALSE]LOG]!><time="15:39:25.000+000" date="03-14-2016" component="Wizard" context="" type="1" thread="" file="Wizard"><![LOG[Not Wizard = False]LOG]!><time="15:39:25.000+000" date="03-14-2016" component="Wizard" context="" type="1" thread="" file="Wizard"><![LOG[FAILURE ( 20001 ): Definition file not defined. Please call with /Defintion:<file>   CommandLine:"\\myimages\mymdt\Scripts\Wizard.hta"]LOG]!><time="15:39:25.000+000" date="03-14-2016" component="Wizard" context="" type="3" thread="" file="Wizard"><![LOG[Microsoft Deployment Toolkit version: 6.3.8330.1000]LOG]!><time="15:40:01.000+000" date="03-14-2016" component="Wizard" context="" type="1" thread="" file="Wizard"><![LOG[Not Wizard = False]LOG]!><time="15:40:01.000+000" date="03-14-2016" component="Wizard" context="" type="1" thread="" file="Wizard"><![LOG[FAILURE ( 20001 ): Definition file not defined. Please call with /Defintion:<file>   CommandLine:"\\myimages\mymdt\Scripts\Wizard.hta"]LOG]!><time="15:40:01.000+000" date="03-14-2016" component="Wizard" context="" type="3" thread="" file="Wizard">

Would anyone know why the Wizard.hta is not properly launching and why MDT is not completing on Windows 10? 

Thank-you,

AP


MDT runonce

$
0
0

In need of help!

I have a windows 10 image prepared and tested via MDT. Next I would like to create\execute the runonce for all new users that log on to set IE11 setting and to run Onedrivesetup (NOTE: OneDriveSetup.exe installs OneDrive only within the current user account. OneDriveSetup.exe will need to be run once per each user account on the machine).

I have used these step within windows 10 and tested with a few new users; this process worked!

01)  Open regedit

02)  Go to HKEY_USERS

03)  Load Hive

04)  Browse to C:\Users\Default User\ntuser.dat

05)  Give it a temporary key name, for example Test

06)  Go to HKEY_USERS\Test\Software\Microsoft\Windows\CurrentVersion

07)  Create a key RunOnce

08)  Create a string value there eg: First Run, then change the value to where your script sits, eg: "C:\temp\IE_trustedsites.reg"

09)  Create a string value there eg: Second Run, then change the value to where your script sits, eg: "C:\temp\One_Drive.bat"

10)  Go back to HKEY_USERS\Test

11)  Unload the hive

12)  Log on with new user

 

Can this be done during MDT deployment or as registry push during MDT post application? Are there other recommended suggestions?

Thanks in advance for the assistance.

Strange behavour of physical machine during MDT deployment

$
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

MDT Driver are not getting installed Automatically after Windows 7 Enterprise Operating System Installs

$
0
0

I am using MDT 2012 to deploy Windows 7 on HP Z440 Workstation.  I have injected SCSI & Network Drivers for WinPE 6.0 (x86) and (x64) and created separate selection profiles for both.  The Selection Profiles are assigned to appropriate WINPE images. The winpe works fine but I have another selection profile that has all the HP Z440 Workstation and have both 64 and 86 drivers. I am creating separate task sequence with Drivergroup=001 with Windows 7/x86/%make%/%Model% and in injecting driver is selected as nothing. using method as all control of drivers.  I do know all the drivers are correct and its Pnp injection of drivers and it should automatically install after the operating system has been installed.  I did read it should create C:\Drivers folder on the C drive but i don't see the C:\driver folder when i go into deploy windows 7 machine. I tried everything i can please let me know if i am missing something or something else i can try. 

Thank You

Nilay


UDI Wizard Designer Preview not working

$
0
0

Hi there,

I built a test environment to get OSD working at my organization and the UDI Wizard Designer's Preview function worked well. It was running on a Hyper-V Server 2012 R2 Standard. Now that I've migrated things over to production I'm finding that the Preview function isn't working. The server it's running on is also Server 2012 R2 Standard. I've gone through the pages contained in the UDI Wizard to ensure I've moved every reference from the test enviro to the production enviro. I saw someone elsewhere claim that this function doesn't work in a server OS, but I don't think that's correct. Any ideas?

MDT 2013 U2 UDI Wizard preview not working

$
0
0

Hello. Has anyone else noticed that clicking the UDI Wizard preview does not do anything ?

I have tried on several systems with the same result, nothing happens.

I monitored the activity with process monitor, but the processes it fires seems to exit normally.


eshe

Surface Pro background problem

$
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?

Is it possible to PXE boot from USB-to-Ethernet adapter to MDT?

$
0
0

Hi guys,

We have some laptops that don't come with ethernet ports that we would like image over the network with MDT. Is there any way to make USB-to-Ethernet adapter boot into PXE? There is no option to boot into it from the F12 menu.

Thank you,

Steve

MDT connection with SQL database

$
0
0

Hi,

i have problem with my MDT server. In one location everything works fine, but in another:

ZTI error opening SQL Connection: [DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied. (-2147467259)
Unable to establish database connection using [MMAPPS] properties.

MDT 2013 update 2

SQL Server Express 2014

TCP/IP enabled, Named Pipes enabled

Add a "Run command line" to task sequences in the steps that boots into Winpe the command line: wpeutil disablefirewall

[MMApps]
SQLServer=name
Instance=MSSQL
Database=name
Netlib=DBNMPNTW
SQLShare=DeploymentShare$
Table=MakeModelSettings
Parameters=Make, Model
DBID=user
DBPwd=Password

Thanks for any suggestion to resolve problem.

Viewing all 11297 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>