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

Help troubleshooting deployment please...

$
0
0

I recently updated our MDT server from 2013 U2 6.3.8330.1000 to 6.3.8443.1000 and I also updated the ADK to v1607, I updated the boot images and imported them in WDS for PXE booting.   I did this so we could get started with Windows 10.  I've created a new build and capture sequence and also a deploy sequence, both for Windows 10, which are working well.  

However, when I tried to image a hyper-v vm using our old Windwos 7 ts it would throw a pink screen and error 6524 while still in WinPE every time, if I imaged a desktop using this ts it would intermittently fail, I can't say for sure whether it was also error 6524 or not.

Anyway, I recreated this Windows 7 ts thinking that was the problem.  When I image the vm I still get the same 6524 error. When I image a desktop I get error 5627 but it's intermittent like before.  The failure screen is:

Something is making me think this is related to our previous habit of fiddling with the partition structure in the image to make a C:, D: and NOT the 500MB utility partition but I don't understand it enough to fix it.  We will not be doing this with Windows 10. If someone can please, please help I would greatly appreciate it, just tell me what you need.

I have shared the logs from the failed desktop imaging here https://1drv.ms/f/s!Apnj5ye_VbzEqA5SA75T6oWRL7gb


MDT... unable to set working directory (-214702483)

$
0
0

Afternoon everyone--

the OS deployed fine but then LIfe Touch starts to install the applications.

most dont install as seen in the pix(ADDED SHORTLY), only a couple not listed install. 

Please any advice where to start ?

i'm new and taking over this imaging process.

many thanks.

Peter

Application Install problems (simple)

$
0
0

Hi,

So I'm having some issues doing very, very basic application installs. Basically I'm loading Flash, Java, and Adobe Reader in an image. I'll try to keep this simply and I'll cut it into a few parts. Screenshots of errors below. This should be very straightforward, what am I doing wrong?

FLASH PLAYER INSTALL

I have downloaded the IE-ActiveX.msi installer from Adobe distribution center. I subsequently added it as an application in MDT with quiet install command: msiexec.exe /i install_flash_player_23_active_x.msi /qn /norestart

I then added a task sequence for this and put that install after the Visual C++ packages.Issue: after deployment I receive a return code: 1603. I've Google'd this code and none of the problems apply to me. It's a new install, no duplicates, system permission is all give. See error screencaps below.

ACROBAT READER DC INSTALL

I downloaded this from the Adobe distrubution center as well. As before, I've added it as an application with a quiet install command: msiexec.exe /i Adobe_Reader_DC_MSI.msi /qn

I then added a task sequence for this install. Issue: after deployment it causes a problem because it tried to install it twice at the same time(?). See screenshot below for reference. It should be a quiet install with no user input, why is it prompting?

Java Install

I downloaded this from the manual download at Java. Specifically the 'Windows Offline' version calledjre-8u111-windows-i586.exe. I added this as an application with command line: jre-8u111-windows-i586.exe /s IEXPLORER=1

I then added a task sequence for this install. Issue: after deploy I get an error code -80. No luck Googl'ing this return code.

Error screen 1

Error screen 2

OS Tweaks not "sticking" when making changes to image during "Suspend" command

$
0
0

Hello,

I have been testing a  number of scenarios with MDT using this video from Michael Beaver as a reference:

Deploy MDT 2013 and Windows 10 from scratch

https://www.youtube.com/watch?v=QOgvECpIsAI

In it - Mike sets up an MDT build lab from the ground up. One thing that is interesting to me in the vid - is where he inserts a Suspend command into the Deploy and Capture segment when first deploying Windows 10 to a new VM. This places a "Resume task sequence" icon on the desktop - but also allows the user to make mods to the Win 10 deployment as well.

While Mike does at least one thing in his video (Sets Remote Desktop to be on) - in my tests - I tried to do a few more things like add two group policy changes (Lose Consumer Experiences and Turn Off Cortana and I cleaned up the start menu etc - and then continue on with the Task Sequence by double clicking the icon.

But when I finally get around to capturing that image and then redeploying it to test it on a new VM - all of my tweaks are gone. No GP edits came across and the start menu is back to it's shoddy state.

Clearly something else is happening when I hit "Resume Task Sequence". Anyone have any ideas on why something like turning on Remote Desktop will stick in the captured images but my stuff will not?

Cheers,

B

Best Practice: Updating My WIMs

$
0
0
Hi all. I'd like to know what the best practice method(s) is(are) for updating the captured windows images that I deploy via MDT. So for instance, let's say I have an image from the start of 2016. That image includes Windows OS and core applications (e.g. Office).

Everything else (adobe, web browsers, drivers, etc.) are deployed with the wim at deployment time. However, what about Windows updates? I've considered using WSUS with MDT but that considerably slowed deployment time so we'll be using WSUS outside of MDT later on. Also what about if I'd like to make changes to the wim? Changes like registry values or local/security policy?

Complete Guide to "customsettings.ini"

$
0
0

I've been Google'ing, searching TechNet and perusing the MDT Documentation Library for a complete guide to "customsettings.ini". While I've managed to find bits and pieces here and there, I've yet to find something that lists all the possible commands and variables. Does anyone know where I can find this?  Or even a giant example customsettings file with all the commands they know of with a line by line explanation of what each does. (It's OK to leave out the database parts.)

Thanks!!!

Drivers not being installed

$
0
0

My school system is looking into moving to Windows Deployment, I have been testing the waters. I can not for the life of me get past this one recurring issue.

No device drivers are being installed. I have the total control method setup currently, as we have many different hardware. I have my folders organized and setup. I have the correct DriverGroup setup in the task sequence, and the correct drivers are being moved to the client machine. I can install them all by hand after the deployment and system setup completes. I was assuming this was a problem with sysprep, so I attempted to sysprep the reference system then boot into PE and capture and deploy that image. Again correct drivers were moved over, but not installed. They are all moved over to C:\Drivers. I assumed from everything I researched that the default sysprep and capture task would work fine, but that gives me the same problem. I have attempted to look through some log files for the deployment process but I am unable to find what might be causing this issue, granted I might not have looked in the correct place. I have tried to run the deployment on other pieces of hardware, all not installing.

Any advice? Thank you in advance.

PXE Booting from Fiber

$
0
0

Hi All,

I have a machine which boots fine over ethernet and I an deploy my image using MDT. I also have a 2port fibre PCI-e card installed (Intel X520), how do I boot from via fibre port. Do I need to provide fiber port MAC address to MDT?

Many Thanks

Zeshan


MDT 2012 failing to capture (Win PE problem)

$
0
0

Hello, I've been using an existing MDT 2013 deployment setup that I've used for Windows 7 and 8. I installed the new ADK for windows 10, and updated my server to U2. When I'm running the task sequence to capture my image, everything seems to run well up until the PE and capture steps in my task sequence. Sysprep runs, then the computer reboots back into the OS (running OOBE like a fresh system). It should be booting into PE and running the capture. I'm not exactly sure where this is failing, but I'm left with a small 3.75KB .wim file. Since I'm getting a .wim, it doesn't seem to be PE drivers. I'm also not even booting into PE, so I'm missing something. I'm using a Hyper-V host as my deployment machine to create the image. 

Anyone run into this before? Any tips? It was 2 years ago I set this up for Win 7, and I don't remember having this issue previously. Thanks in advance. 

Unable to mount the WIM, so the update process cannot continue.

$
0
0

Hi , I am getting this error message when I try to update deployment share for AMD x64. I have MDT in a separate server and WDS in separate server. once the WIM is updated , I map the other server and update the boot image to the WDS to deployment.

This  is the error message.

=== 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.
Loading the existing boot image profile for platform x86.
Calculating hashes for requested content.
Changes have been made, boot image will be updated.
Windows PE WIM D:\Deployment Shares\AMD\Boot\LiteTouchPE_x86.wim will be used.
Unable to mount the WIM, so the update process cannot continue.

=== Completed processing platform x86 ===

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

=== Processing Generic (x64) boot image ===

Building requested boot image profile.
Determining if any changes have been made in the boot image configuration.
Loading the existing boot image profile for platform x64.
Calculating hashes for requested content.
Changes have been made, boot image will be updated.
Windows PE WIM D:\Deployment Shares\AMD\Boot\Generic_x64.wim will be used.
Unable to mount the WIM, so the update process cannot continue.

=== Processing LiteTouchPE (x64) boot image ===

Building requested boot image profile.
Determining if any changes have been made in the boot image configuration.
Loading the existing boot image profile for platform x64.
Calculating hashes for requested content.
Changes have been made, boot image will be updated.
Windows PE WIM D:\Deployment Shares\AMD\Boot\LiteTouchPE_x64.wim will be used.
Unable to mount the WIM, so the update process cannot continue.

=== Completed processing platform x64 ===


=== Processing complete ===

Please help,

Thanks

Dirty environment found on some models but not others

$
0
0

Hello.

We use MDT 8443 to deploy clients (Windows 10) and servers (Windows Server 2016) and have issues with "Dirty environment found".

Both clients and servers use UEFI booting. We initiate installations by PXE booting from a WDS server.

On clients, some models install without a hitch and some consistently present a "Dirty Environment found" dialog, if you answer "No" and let the task sequence continue it finishes successfully.

On servers, one model (HP ProLiant ML110 Gen9) applies the OS image and reboots, after reboot it boots to PXE. If we boot from WDS again, we get a "Dirty Environment found" dialog", answer "No", the server reboots and boots off internal disks. The installation seems to finish properly, but we get an error from ZTITatoo, "FAILURE ( 9601 ): ERROR - ZTITatoo state restore task should be running in the full OS, aborting" in the summary.

If we run the same server task sequence on a VMWare virtual server, it finishes successfully without booting from PXE or displaying errors from ZTITatoo.

Does anyone have an idea what goes wrong when we end up with a dirty environment?

Building Reference for Terminal servers

$
0
0

Have some Questions related to building reference image for Windows Terminal servers (Citrix) using MDT 2013 U1

OS is server 2008 R2 SP1

I am not sure how i can accomplish this easily . the Task is to install OS , Install RDS role , Install upto date windows components , RDS hotfixes , then change install mode and begin all application installations  once all apps are installed , install Citrix software , fully patch the system and apps and capture the image.

I want to do this efficiently using MDT 2013 

Any suggestions

Packages Node in MDT 2013

$
0
0
At what point in the build process are the Update s(msu / hotfixes)  which we import in Packages node installed during the Task Sequence.

Upgraded to latest MDT package

$
0
0

Already have the latest ADK installed.  Have the latest version of SCCM (1610).  Installed the latest version of MDT, updated deployment share and reintegrated MDT with SCCM.  Deployed a OS task sequence and everything went as expected.  My question is why in MDT monitoring are my deployments not showing up anymore?

Did I forget a step?

Disk(0) was not found.Unable to continue error in windows 7 sp1 imaging-Thinkpad P50

$
0
0

I am getting below when trying to pxe boot in thinkpad P50 model.latest storage drivers from vendor site has been imported and updated in the deployment share.pls guide me to fix this error.

make:Lenovo Thinkpad P50

<label class="ng-isolate-scope" l-translate="MTMLabel" style="box-sizing:content-box;border:0px none;font-family:museo_sans300;font-feature-settings:inherit;font-kerning:inherit;font-size:13px;font-variant-numeric:inherit;line-height:inherit;margin:0px;padding:0px;vertical-align:baseline;">Machine Type</label>20EN001RUS

winpe version:4.0

secure boot option in bios diabled.

uefi/legacy option both option enabled in BIOS.




Nisajudeen


Sysprep and Capture using the latest version of MDT

$
0
0

Hello,

I recently upgraded our MDT 2013 U2 to the latest version - 6.3.8443.1000.  After performing the update, I can no longer run the sysprep task sequence.  It just runs like I'm dropping a new image on a PC.  I tried to test out a fresh install on my laptop and got the same result.  

After I uninstalled the latest MDT and installed build 6.3.8298.1000, created a new deployment share and tried, the task sequence worked fine.  

Is there a new way to create sysprep tasks or a different way to go about it with the new build?

Thanks

USMT: Migrate to same profile but different domain

$
0
0

Hi All,

We are working on a migration. Our requirement is as follows:

 -Migrate user profile of User1 of DomainA.com to User2 in DomainB.Com domain.

 -Make sure only settings (User profile settings are migrated). Basically, we don't want to copy user profiles.

Can this be done using USMT tool?

Thank you for your help.

Nick R.

cant get an IP address on WIN10 after latest updates

$
0
0

Here's the problem...

cant get an IP address on WIN10 after latest updates.   After the 12/9 update (KB3201845)  I LOST my WiFi connection.

I keep getting "invalid IP address" and when I check IPCONFIG, I have a 169.x.x.x address.   I have changed my router & Comcast cable modem AND tried many of the fixes on several forums (Winsock, Resets, etc...) - NO GOOD

When I go back to a 'Restore Point' from Nov 28 - EVERYTHING is OK.   BUT - i then am FORCED to downloadEVERY WIN10 Update - and BANG - I back where I started.  PLEASE HELP FIX THIS MICROSOFT PROBLEM!!!!


CustomSettings.ini Not Applied

$
0
0

I customized this customsettings.ini with to join mydomain. but after the installation it join workgroup and computername is different. It seems that it keep apply different CS.ini but I can't figure out which one and where. Is anyone know a way to force the customsettings.ini inside the rules tap to  override any other CS.ini. 

Settings]
Priority=Default
[Default]
OSDComputername=xxx-#Left("%SerialNumber%",6)#
OSInstall=YES
UserDataLocation=AUTO
TimeZoneName=Central Standard Time
AdminPassword=*******
JoinDomain=mydomain.com
DomainAdmin=mydomain\administrator
DomainAdminPassword=*******
SLShare=\\mdt\Logs$
HideShell=YES
ApplyGPOPack=NO
SkipAppsOnUpgrade=NO
SkipAdminPassword=YES
SkipProductKey=YES
SkipComputerName=NO
SkipDomainMembership=YES
SkipUserData=YES
SkipLocaleSelection=YES
SkipTaskSequence=NO
SkipBitLocker=YES
SkipSummary=YES
SkipCapture=YES
SkipFinalSummary=NO
EventService=http://MDT:9800

Found a typo in ServerManager.xml

$
0
0

I found a typo in ServerManager.xml which resulted features not installing. In both Server 2016 sections, the last letter for each is missing.


Incorrect Values:

 <RoleService DisplayName='HTTP Errors' Id='Web-Http-Error' />

 <RoleService DisplayName='WebDAV Publishing' Id='Web-DAV-Publishin' />

Corrected Values:

  <RoleService DisplayName='HTTP Errors' Id='Web-Http-Errors' />

  <RoleService DisplayName='WebDAV Publishing' Id='Web-DAV-Publishing' />

Viewing all 11297 articles
Browse latest View live


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