Are you the publisher? Claim this channel


Embed this content in your HTML

Search



Account: (login)

More Channels


Channel Catalog


Channel Description:

This is an open forum where we invite you to ask questions, post answers, and share your insights regarding the operations of MDT.

older | 1 | .... | 148 | 149 | 150 | (Page 151) | 152 | 153 | 154 | .... | 213 | newer

    MDT 2012

    Using the tools folder and cab files looks nice. Any chance of getting ADSI support in there?


    Hi

    I installed  WIK for Windows 7 SP1 and MST 2012 on Windows server 2008 R2.

    I configured WDS, AD and DHCP. Added  Windows 7 SP1 Build 6.1.7601.17514 as Operating system and 96 windows 7 updates under package.

    when I update deployment share I get following error

    Deployment Image Servicing and Management tool
    Version: 6.1.7600.16385

    Image Version: 6.1.7600.16385 (6.1.7601.17514)

    Processing 1 of 1 - Adding package Package_for_KB2647753~31bf3856ad364e35~amd64~~6.1.4.0

    Error: 0x800f081e

    The specified package is not applicable to this image.

    The DISM log file can be found at C:\Windows\Logs\DISM\dism.log

    Exit code = -2146498530

    DISM /Add-Package failed, rc = -2146498530.
    Injected package Package_for_KB2647753 neutral amd64 6.1.4.0 KB2647753

    Previously I used RT7 Lite to inject all 96 updates to same windows 7 build. If I use this image to deploy windows 7 in a workstation, I can see only 35 updates are added to the windows 7 installation.

     can some one suggest a solution

    Jijo


    I am trying to use UpdateExit.vbs to run a command against the mounted litetouch WIM when it is being created/updated in MDT 2012.  I had this working in MDT 2010.

    I added the command to the If oEnv("STAGE") = "WIM" section of the UpdateExit.vbs and I added a WScript.Quit 1 to the end so that the output would be listed in the MDT console.  The issue I am having is that it appears that STAGE is never set to WIM so that section is never processed and my command is never run.

    I see stages called POSTWIM, ISO and POSTISO, but not one called WIM.

    Here is the output from my console:

    === 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 D:\Program Files\Windows AIK\Tools\PETools\x86\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-mdac
    Added component dart
    <the part where it injects drivers>
    <the part where it copies files>
    Copying WIM to the deployment share.

    Microsoft (R) Windows Script Host Version 5.6
    Copyright (C) Microsoft Corporation 1996-2001. All rights reserved.

    INSTALLDIR = C:\Program Files\Microsoft Deployment Toolkit
    DEPLOYROOT = D:\DeploymentPoints\Workstation
    PLATFORM = x86
    ARCHITECTURE = x86
    TEMPLATE = LiteTouchPE
    STAGE = POSTWIM
    CONTENT = C:\DOCUME~1\user\LOCALS~1\Temp\1\MDTUpdate.4860\LiteTouchPE_x86.wim

    Exit code = 1

    Creating an ISO.
    Microsoft (R) Windows Script Host Version 5.6
    Copyright (C) Microsoft Corporation 1996-2001. All rights reserved.

    INSTALLDIR = C:\Program Files\Microsoft Deployment Toolkit
    DEPLOYROOT = D:\DeploymentPoints\Workstation
    PLATFORM = x86
    ARCHITECTURE = x86
    TEMPLATE = LiteTouchPE
    STAGE = ISO
    CONTENT = C:\DOCUME~1\user\LOCALS~1\Temp\1\MDTUpdate.4860\ISO

    Exit code = 1

    Copying ISO to the deployment share.
    Microsoft (R) Windows Script Host Version 5.6
    Copyright (C) Microsoft Corporation 1996-2001. All rights reserved.

    INSTALLDIR = C:\Program Files\Microsoft Deployment Toolkit
    DEPLOYROOT = D:\DeploymentPoints\Workstation
    PLATFORM = x86
    ARCHITECTURE = x86
    TEMPLATE = LiteTouchPE
    STAGE = POSTISO
    CONTENT = C:\DOCUME~1\user\LOCALS~1\Temp\1\MDTUpdate.4860\LiteTouchPE_x86.iso

    Exit code = 1

    === Completed processing platform x86 ===

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

    === Processing LiteTouchPE (x64) 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 x64 so a new image will be created.
    Calculating hashes for requested content.
    Changes have been made, boot image will be updated.
    Windows PE WIM D:\Program Files\Windows AIK\Tools\PETools\amd64\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-mdac
    Added component dart
    <the part where it injects drivers>
    <the part where it copies files>
    Copying WIM to the deployment share.
    Microsoft (R) Windows Script Host Version 5.6
    Copyright (C) Microsoft Corporation 1996-2001. All rights reserved.

    INSTALLDIR = C:\Program Files\Microsoft Deployment Toolkit
    DEPLOYROOT = D:\DeploymentPoints\Workstation
    PLATFORM = x64
    ARCHITECTURE = amd64
    TEMPLATE = LiteTouchPE
    STAGE = POSTWIM
    CONTENT = C:\DOCUME~1\user\LOCALS~1\Temp\1\MDTUpdate.4860\LiteTouchPE_x64.wim

    Exit code = 1

    Creating an ISO.
    Microsoft (R) Windows Script Host Version 5.6
    Copyright (C) Microsoft Corporation 1996-2001. All rights reserved.

    INSTALLDIR = C:\Program Files\Microsoft Deployment Toolkit
    DEPLOYROOT = D:\DeploymentPoints\Workstation
    PLATFORM = x64
    ARCHITECTURE = amd64
    TEMPLATE = LiteTouchPE
    STAGE = ISO
    CONTENT = C:\DOCUME~1\user\LOCALS~1\Temp\1\MDTUpdate.4860\ISO

    Exit code = 1

    Copying ISO to the deployment share.
    Microsoft (R) Windows Script Host Version 5.6
    Copyright (C) Microsoft Corporation 1996-2001. All rights reserved.

    INSTALLDIR = C:\Program Files\Microsoft Deployment Toolkit
    DEPLOYROOT = D:\DeploymentPoints\Workstation
    PLATFORM = x64
    ARCHITECTURE = amd64
    TEMPLATE = LiteTouchPE
    STAGE = POSTISO
    CONTENT = C:\DOCUME~1\user\LOCALS~1\Temp\1\MDTUpdate.4860\LiteTouchPE_x64.iso

    Exit code = 1

    === Completed processing platform x64 ===

    === Processing complete ===


    Hi all,

    So today I had a run in with a colleague who started to install fat images on my MDT solution across 5 sites with DFS-R replication and would like to hear from you all if you are using a one or the other or a mixture of the both?

    I prefer thin images myself due to the fact that i use less storage, I think it is easier to quickly update drivers, apps etc using thin images. However we do have some applications like the Oracle 10 client, old Seagate Crystal Report client and a client for our Maginus ERP system. neither of these we can do quiet install on, so i can understand why he would go with fat images for that reason.

    my attempt so far to install all 3 apps and then re-package them have failed, but the oracle client would need some settings in ODBC connections too. so not sure if that would be captured either.

    looking forward to read your feedback.


    Regards
    ronnie.jorgensen systems engineer
    My blog


  • 08/07/13--23:22: Move MDT 2012 Server to New VM (chan 3834436)
  • HI Guys,

      I need to move our MDT to new VM. So what is the steps i required? 

    AS

      


    Litetouch deployment failed, return code=-214746729 0x80004005

    Failed to save environment to 80070057

    Failed to run the action:Install Operating System

    Unknown error(Error:000015FB;Source:Unknown)

    The execution of the group(install) has failed and the execution has been aborted. An action failed

    Operating system aborted(Error:8004004:Source:Windows)

    Failed to run last action:Install Operating system.Execution of task sequence failed

    Unknown error:Error:000015FB:Source:unknown)

    Can some one help me with this? I am trying to run standard client TS for windows 7

    Thanks,

    Rajith.


    Thanks, Rajith P


    Hi Friends and MVPs,

    We want to use existing USB hard drives as Media for MDT image deployment. We are OK to format and copy the MDT media into Hard disk drive. We can't buy USB flash drives :-(

    1. Is it supported?

    2. How to copy the content into USB hard drive (Is it same procedure as USB flash drive? with addition of  “bootsect /nt60 p:”)

    3. Any links?

    4. If not in MDT 2012 U1, Is MDT 2013 is going to support USB Hard drive as Media?

    TIA.


    saravanan rajappa


  • 03/13/12--09:30: VBScript Error MDT 2012 RC1 (chan 3834436)
  • Is anyone else having the below VBScript at the end of a OS Refresh.

    I'm doing this with MDT 2012 RC1 within a new Server and MDT install

    It will continue if I use HideShell in the customsettings.ini

    Error Below

    _________________________________________________________________________

    VBSCRIPT ERROR AT THE END

    C:\DOCUME~1\ADMIN~1\LOCALS~1\Temp\DeploymentScripts\Wizard.hta

    A VBScript Runtime Error has occurred:
    Error: 13 = Type mismatch
    VBScript Code:
    ----------------
    InitializeSummary

    ____________________________________________________________________________


    I've been deploying windows 7 x86 images via MDT 2010 Update 1 which is working great!

    Question..  I need to disable as much as possible for our users in our environment. I need to disable Windows Firewall, Windows Defender, the Action Center, and Windows Updates.. Im pretty confident in separate registry keys to disable all of the above, but wanted some experts opinions in how to disable all via MDT, scripts, registry, etc.... I already have my wim, applications, and task sequences set up and successfully deploying to computers... 

    Any help would be appreciated.


    Greetings,

      I loaded the standard server task sequence in MDT 2012 (Update 1). In the PreInstall phase there is an Inject Drivers step which allows me to select a Selection profile. In the PostInstall phase, there is an Inject Drivers step, but this doesnt allow me to select a profile - it calls ztidrivers.wsf. Why do these two steps with the same name do different things? Can I delete the postinstall ztidrivers and add a proper Inject drivers step with a selection profile?

    Thanks

    David Z


    So I've used MDT2012 to capture my reference images and it works very well. One requirement I have is to create separate images with only slight differences between each other. After I run my task sequence to capture the image, can I simply restart the reference workstation back into windows, make additional changes and run the capture task sequence again? Or will I need to completely rebuild/reinstall my reference workstation?

    Greetings,

      At the beginning of the MDT process, credentials are gathered and stored in the properties - username, userpassword and userdomain.

      When the "recover from domain" step runs post install, I want to use these credentials. So how do I copy username to domainadmin, userdomain to joindomain and domainadmindomain and userpassword to domainadminpassword please?

    Also, I would like to use the userdomain property as part of the target OU e.g.

    MachineObjectOU=OU=Staging,DC=%userdomain%,DC=acme,DC=com ??? Is this possible?

    Thanks

    David Z


    AD:Win Srv 2012:AD+DHCP+DNS;

    MDTServer:MDT2013 Preview+ADK8.1  

    Deployment Type=Replace

    "Standard Client Replace Task Sequence" error:



    Hi,

    I'm fairly new to MDT / WDS and I have created a regular win7pro deployment.  It works fine, except that just after the image has been transferred, during the Configure Windows state (before the installation of applications) Windows pops up the product key / activation form. Right afterwards the wireless network connection form is displayed.  We just have to click the Skip button on both of these forms as we tank student computers and the students themselves are requested later in runonce scripts to enter the product key from the label underneath the computer and they will also connect to the proper wireless network.

    I have not found a key or setting to automatically skip the product key and wireless network forms during the installation. How do I disable these two?

    Thanks for help on this

    regards Tor



  • 08/09/13--00:59: Captured Image not Joining Domain (chan 3834436)
  • Hello Sir,

    My Captured Image not joining domain automatically, Although When I deploy Fresh Image through MDT it joined domain automatically. When I start the Image capturing the computer is not on the domain, as advised in the available threads, Image Captured went successfully, but when I try to deploy the Captured Image through MDT, the target computer not join the domain automatically, we have to do the domain Join manually. Please advise what went wrong.

    regards / Abhishek



  • 08/08/13--12:40: CustomSettings.ini - 009, 010 (chan 3834436)
  • Hello,

    I've looked and looked, but can't find an answer to this.

    I've got a long list of applications I'm making mandatory. Once I get to ManadatoryApplications009, I don't know what the next one should be. Logically, I would think it's 010, 011, etc. When I booted to the wizard, it stops at 009.

    Any ideas on this one?


    Hello,

    I have started using MDT 2012 Deployment in a production environment and all has been working OK. I have been installing from PXE and USB sticks on HP Desktops 6000 SFF and 6305's and also HP Laptops 6570b and various others.

    My problem is with a new deployment I have created for HP Elite 8100 tower PC's. I have all the settings in my CustomSettings.ini and when the computers boot the load up the selection screen OK then I get prompted to enter in my computer name and the domain settings are preconfigured (via CS.ini) and lastly I enter in the admin password. So far so good as it shows it is reading the customsettings.ini all OK. BUT once the deployment has completed the machince has not been added to the domain and also has not applied the admin password specified?

    It PC is OK on the network as I see a DHCP reservation for it and if I use PXE it starts and runs OK but just doesn not apply the domain details, admin password and locale settings defined in the CustomSettings.ini.

    Any pointers?


  • 08/09/13--00:02: Slow TFTP downloads (chan 3834436)
  • Hi everyone,

    This one really has got me baffled.  Our Lite Touch image is ~200MB, and takes about 1 minute and 15 seconds to download from WDS if one client is booting the WIM.

    The moment I do two clients, it goes up to about 2 minutes (and so on and so forth).

    Regardless of this, it seems our WDS server has set a cap of 0.1% of the available bandwidth for TFTP.

    The server itself is an HP DL180G6 with 4 gigabit NICs all teamed in 802.3ad Link Aggregation using the HP teaming software.  The clients are mostly HP dx2450 machines with NVIDIA gigabit bootable NICs.

    I can't seem to find a way to persuade WDS that it can use more than 0.1% of the bandwidth.

    We have adjusted the TFTP block size, and any more than 1422 causes problems (we lack jumbo frame support in places!), and we've tried TFTP window sizes from 1 through 16 - no performance increases (many decreases at higher numbers!).

    We've even been through http://blog.danovich.com.au/2011/07/28/slow-sccm-osd-tftp-pxe/ as well, and upped the buffers on each card to 2048 (although we can't seem to adjust them on the team itself in the HP software!)

    Has anyone got any ideas?  This is driving us up the wall!

    Cheers,

    Chris


    Greetings,

      Im running a light touch deployment and I was wondering if it is possible to skip the screen that asks you to press "Run the deployment wizard to install an operating system". I tried skipbddwelcome=yes but it doesnt affect this screen. I just want it to do the initial gather and go straight on to the credentials screen.

    Thanks

    David Z


    I recently converted to MDT 2012 after running MDT 2010 for awhile (which has been great). Johan had written up an article (http://www.deployvista.com/Home/tabid/36/EntryID/139/language/en-US/Default.aspx) that allows you to do settings per task sequence without the use of a database which was amazing for our environment. After switching to 2012 this no longer works. Is there something I'm missing or what do I need to change to make this work?

    Thanks!
    Joe


older | 1 | .... | 148 | 149 | 150 | (Page 151) | 152 | 153 | 154 | .... | 213 | newer