Creating Windows 8.1 master image with MDT 2013,cannot capture .WIM

I am having an issue with creating a master image with Windows 8.1 and MDT 2013.  
I have followed extensive tutorials on how to create a master image using Microsoft Deployment Toolkit. my goal is to have a fully configured windows 8.1 image which I can deploy through Windows Deployment Services. I have been relatively successful thus far,
except for one issue I have run into, which is successfully capturing this image as a .WIM.
I have successfully created a task sequence and the task sequence is able to run all the way through until the final step. Essentially the task sequence is supposed to install Windows and Office, then suspend the task sequence to allow me to make customisations
to the start screen and desktop background, and I simply click resume task sequence, and the task sequence should sysprep reboot and capture the machine image as a .WIM file.
the task sequence is able to sysprep the machine, but upon rebooting it boots into out of box experience, and does not create a wim file. I receive an error saying: "cannot find script file C:\ltibootstrap.Vbs" after the machine completes OOBE 
I am using Windows Server 2012 r2, creating my Master machine image using hyper-v, and my master image is running Windows 8.1.
Any help would be greatly appreciated.

I'm not sure about the sequence of steps here. Try taking your captured.wim file and deploying it using MDT again, or at least to another machine. MDT sometimes leaves extra files around on the captured machine, so simply rebooting it may not get a accurate
test results.
IF you are getting the ltibootstrap.vbs it is most likely because there is a stray unattend.xml file somewhere in your image that is looking for this file. Crack open your Wim file and search for any unattend.xml files.
Keith Garner - Principal Consultant [owner] -
http://DeploymentLive.com

Similar Messages

  • I want to create an image gallery with forward back nav, master image with a click to pop out zoom

    Hi Musers,
    I'm currently building a photography website and need some help building a specific type of gallery.
    xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
    Below is a description of the gallery I want to build:
    On the gallery page the gallery appears as a single 'Master Image' with forward and back 'Navs.' and a 'Counter' underneath this single 'Master Image'. Lets say that there are 10 images in this gallery. When the viewer clicks on the forward 'Nav.' the 'Master Image' changes to the next image in the sequence of 10 and the 'Counter' below confirms this progression, in this example the 'Counter' changes from 1 of 10 to read 2 of 10, the 'Master Image' displayed is the second image in the sequence.
    Simple so far.. This above I can do as this is just a basic gallery. What follows is what I cannot find a solution for.
    I want the gallery viewer to be able to click on the 'Master Image' and launch an enlargement of that image overlaying the gallery page, very much like the way the 'Lightbox' widget displays an enlarged image. When the viewer clicks off the 'Ligtbox' or enlarged image it dissapears, reverting the page view back to the standard gallery view with 'Master Image', 'Navs.' and 'Counter'. I do not want the expanded / Enlarged 'Lightbox' image accompanied by a thumbnail gallery, 'Navs.' / Navigation arrows or a 'Counter'. What I want is to be able to launch an enlarged version of the 'Master Image' as an overlay on the gallery page, something like a pop out.
    xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
    Can anyone explain how I can do this? Is it possible?
    The solution I want seems to be a highbrid between the standard gallery with navigation arrows kept but minus thumbnails and captions with some of the functionality of the lightbox gallery widget.
    I very much appreciate any help anyone can give.
    Thank you

    Hi Harriet,
    Thanks for the message. I'm sure as time goes on new features will be introduced but it's a bit of a shame that the widget library is a little basic, oh, and at times it's just that little bit buggy. So far I'm really impressed by Muse despite being ever so slightly disappointed by some of it's limitations. I'd like to see more image gallery options, the ability to set up a client login area or a client ftp within a site, I also tried embedding video but as I'm no programmer the result looked clumsy so some focus on this would be a help. Considering that a good number of people benefiting from a Muse site will be online retailers a zoom function should have been there from the start.
    Best regards
    Jacques

  • Create Image using MDT 2013

    Hi ,
    I am quite new for MDT 2013. I have recently installed MDT 2013 in my Windows Server 2012.
    Now , I do have about 10 physical machine with different hardware specification inside. I have installed Windows 8.1 with all required software in it and now I want to distribute the same image in all 10 another physical machine.
    Can anyone provide me the steps to implement this...
    Do I need to create the image using image x software and then use it as a standard image to be deploy it in rest of the systems..
    Thank you...

    I was getting exact same error.
    here is what I did to fix it.
    You need to do all this in a virtual envinronment.
    1- import Windows 8.1 x64 from the DVD and add it to your listed os in MDT
    2- create standard task sequence and select the OS you imported in step one. you need to add suspend to your TS ( look it up on how to )
    3- For some reason WinPe x64 bit kept giving error during deployment so I used WinPe x86.
    4- import Winpe x86 boot.wim into your WDS if you use Pxe boot or create a boot disk from the ISO and boot your VM from it.
    5- deploy windows 8.1 x64 to your VM ,make sure to select " capture image ".
    make all the necessary changes when windows is installed  and MDT  suspends the deployment, take snapshot of your VM , and then cintinue the deployment to finish the capture.
    6- import the new captured image into MDT
    7- creates new standard TS or modify your existing one to deploy the newly captured image.
    8- update your deployment share and start the deployment of your new image.

  • Capture system image with MDT

    Hello everyone,
    I want to create a Windows 7 installation disc that will allow me to have, immediately after installation, a system updated with the latest hotfixes, installed programs and all the settings I want already selected in the system.
    Now, I used MDT 2013 on x64 Windows 8.1 Pro to create a DeploymentShare Windows 7 Pro x86, including drivers, applications and various hotfixes, once I create the image of Windows PE, through which I install the above system from DeploymentShare, all row smoothly,
    but I have any dubious:
    1) Once the system is installed, they log me in as Administrator, why?
    2) If I log in as Administrator, then I have to run the sysprep.exe / generalize / oobe before delivering the computer to an imaginary customer?
    3) If I want to make changes to the settings of the user (for example to make sure that hidden folders see by default after installation or arrange the icons on the desktop as I will ensure that the end user see it exactly so) I have to use the CopyProfile?
    4) If yes, at what stage should I use the CopyProfile? Specifying an unattend.xml during sysprep.exe on point 2? Or maybe I recapture system image after install it and use the file *.wim with a different unattend.xml, that is, in practice doing two laps of
    installation?
    5) Once I captured the system image, when I try to install it, the system logs me in again with Administrator account instead of OOBE, why?
    I want to do this final procedure on the end user PC:
    1) Put the DVD (or USB) of this modified Windows
    2) Install Windows automatically with all applications, hotfixes and settings
    3) Once Windows is installed, I install in audit mode all drivers for that PC and sysprep /oobe it
    4) Give the PC to the client
    Thank you in advance!
    P.S: sorry for my bad english

    1. By design, a hold out from the days when MDT also supported XP.
    2. By design, images need to be syspreped if they are to be applied to other machines.
    3. Typically I do *NOT* recommend making changes to HKCU during imaging, instead settings should be applied using GPO or other method. CopyProfile can work as a last resort.
    4. CopyProfile is applied during "Specialize" as per documentation, not during sysprep.
    5. MDT enables the local administrator account for use in MDT deployments later. Check out the unattend64.xml template in the MDT install directory:
    <RunSynchronous>
    <RunSynchronousCommand wcm:action="add">
    <Description>EnableAdmin</Description>
    <Order>1</Order>
    <Path>cmd /c net user Administrator /active:yes</Path>
    </RunSynchronousCommand>
    <RunSynchronousCommand wcm:action="add">
    <Description>UnfilterAdministratorToken</Description>
    <Order>2</Order>
    <Path>cmd /c reg add HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System /v FilterAdministratorToken /t REG_DWORD /d 0 /f</Path>
    </RunSynchronousCommand>
    <RunSynchronousCommand wcm:action="add">
    <Description>disable user account page</Description>
    <Order>3</Order>
    <Path>reg add HKLM\Software\Microsoft\Windows\CurrentVersion\Setup\OOBE /v UnattendCreatedUser /t REG_DWORD /d 1 /f</Path>
    </RunSynchronousCommand>
    </RunSynchronous>
    This works for MDT deployment later, but if you have a custom process, you may need to adjust the system.
    Keith Garner - Principal Consultant [owner] -
    http://DeploymentLive.com

  • Deployed a new computer with MDT 2013, but Windows licensing did not give me an initial grace period

    Hi all,
    Strange issue. I have created a Windows 7 x64 gold image to be deployed. When creating the image, I allowed Sysprep to rearm Windows. I've deployed about 10 computers in the past week and everything has worked fine.
    Yesterday, I deployed another two computers. One works fine, but when I logged into the second one, I was greeted with the you need to activate Windows now screen. I was confused so I ran slmgr /dlv and sure enough my license status was not "Initial
    Grace Period" but instead "Notification." (by the way, it did show remaining rearms as 2, which is expected since it was rearmed with sysprep when capturing the image, so we know it was in fact rearmed).
    So my question is how and why did this happen? I was in a hurry so I just ran slmgr /rearm to burn off another rearm. I plan on putting in a KMS server at the end of the week, but I'm worried if I should redeploy the image to this machine since something
    appears to be wacky.
    Anyone seen this before or have any thoughts on the matter?

    Either way, it was correct when I checked it today so maybe it corrected itself after Windows was installed? Not sure how else to explain this one.
    Me either.
    After Windows is installed, if you are domain-joining, the clock will sync to your Domain Controller.
    If not domain-joined, Windows will try to sync to time.windows.com (or similar).
    Don
    (Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
    This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!)

  • Deploy win7 and linux image with MDT

    We have been using mdt 2010 for our deployment in the last few months. It works perfectly. Now i am facing a bit problem, our organization decide to include a linux image  into the standard one. Is there anyway we can deploy this linux image in mdt?

    Sure you can, but it's not supported (at all) by Microsoft... :)
    It's been a while, but I have tested two ways of doing this
    1. Have a custom task sequence create a 50 MB fat partition, make it bootable using syslinux, copy the linux boot image to c:\, copy the kickstart script, create the syslinux.cfg, reboot, allow the kickstart setup to do the rest...
    2. Have a custom task sequence use a disk image utility like dd for windows to just dump a cloned image...
    I like option 1 the most...
    Please don't consider dualbooting, its a beating, it just adds additional complexity... If they really need Linux and Windows on the same box, run Linux in a VM (or the other way around).
    / Johan

  • Exporting master images WITH adjustments

    Hello,
    I have a simple question about exporting images.
    Let's say I have imported a bunch of raw images into my Aperture Library (but they are referenced files, located in the folder specified by me). Then I have worked on them. And now I want to backup my work - all my adjustements. But I don't want to export them as new versions (jpgs), but just export the raw files together with adjustments I have just made.
    How do I do that?
    Any help would be really appreciated.
    Best greetings,
    Tomasz
    iMac G5 17'' Flat Panel   Mac OS X (10.4.8)  

    This is where the Adobe DNG could shine.
    http://www.adobe.com/products/dng/index.html
    Worth the read ... this can save the changes that one
    makes.
    DNG does NOT help in this case.
    There is a huge misunderstanding that this is part of what DNG can or should do.
    But if you think about it, what good are the adjustments being stored in DNG if you have to use a particular program to open it anyway?
    Think about Aperture's Edge Sharpen for a second. Lets say you store that value in a DNG. Fine, what other program is going to able to reproduce that result EXACTLY to how you were previewing it at 100% on your monitor?
    Lighroom is trying to do something along these lines by passing editing commands off to Bridge through DNG. But here you run into another problem - it constrains what editing any one program can do. If Lightroom is limited to only ever having editing commands that are the same as what Bridge offers, and no other program on earth supports them, then what have you really accomplished? Will unknown editing commands simply be dropped without warning?
    That's why I think simply exporting projects, which hold master images alongside sidecar files (very like XMP) that describe edits are about as good as you are going to get. If you want to truly preserve editing work and you care about quality, nothing beats a TIFF file where 100% of the pixels are exactly as you reviewed them during editing. I personally trust Aperture enough to back up master images along with edits, and am fine with that.

  • HOWTO and script: create and burn an UDF image with 4+GB files

    Most people think, creating UDF images with files bigger than 4GB or even 1GB is impossible, however it's not true! You just need udftools. Also you need to load loop and udf modules. There's a good howto by grigio, I also created an (admitably pretty poor) script to do it automatically, since grigio's howto doesn't include real dvd sizes:
    UDFPATH=$HOME
    echo -e "By default the udf image will be placed into your home directory. \n Do you want to enter an alternative one? (Enter y or n)"
    read yesorno
    if [ $yesorno == y ]; then
    echo "Please enter the directory you want to use: "
    read UDFPATH
    if [ -d $UDFPATH ]; then
    echo "Using $UDFPATH"
    else
    echo "Creating $UDFPATH" && mkdir -v $UDFPATH
    fi
    fi
    if [ $yesorno == n ]; then
    echo "Using default directory"
    fi
    if [ $yesorno != y -a $yesorno != n ]; then
    echo "Incorrect entry, aborting..." && exit 0
    fi
    if [ -e $UDFPATH/udf.iso ]; then
    mv $UDFPATH/udf.iso $UDFPATH/udf.iso.bak-`date +%y.%m.%d-%H.%M` && echo "udf.iso already exists! Backing up..."
    fi
    echo -e "Please enter your type of disk: dvd5p, dvd5m, dvd9p or dvd9m:\n(5/9 stand for normal/double layer disk and p/m for +/-)"
    read type
    if [ $type == dvd5p ]; then
    echo "Creating a 4,7 GB DVD+R image..."
    dd if=/dev/zero of=$UDFPATH/udf.iso bs=1024 count=4590208
    fi
    if [ $type == dvd5m ]; then
    echo "Creating a 4,7 GB DVD-R image..."
    dd if=/dev/zero of=$UDFPATH/udf.iso bs=1024 count=4596992
    fi
    if [ $type == dvd9p ]; then
    echo "Creating a 8,5 GB DVD+R image..."
    dd if=/dev/zero of=$UDFPATH/udf.iso bs=1024 count=8347648
    fi
    if [ $type == dvd9m ]; then
    echo "Creating a 8,5 GB DVD-R image..."
    dd if=/dev/zero of=$UDFPATH/udf.iso bs=1024 count=8343424
    fi
    if [ $type != dvd5p -a $type != dvd5m -a $type != dvd9p -a $type != dvd9m -a $type != cheat ]; then
    echo "Wrong type entered, aborting..." && exit 0
    fi
    mkudffs $UDFPATH/udf.iso
    echo -e "UDF image created in $UDFPATH/udf.iso. Want to mount it right now? (Make sure udf and loop modules are loaded)"
    read yesorno
    if [ $yesorno == y ]; then
    echo "Please enter the directory you want to use for mounting: "
    read MOUNTPATH
    if [ $UDFPATH = $MOUNTPATH ]; then
    echo "You can't mount the image to the directory it exists in!" && exit 0
    echo -e " Mount it yourself with 'sudo mount -o loop,user,uid=`id -u` -t udf $UDFPATH/udf.iso targetdir\'"
    echo " Afterwards copy your files, unmount the image and burn the dvd."
    echo -e " For burning you may just use 'cdrecord -eject -dao -dev=/dev/sr0 $UDFPATH/udf.iso'\n (the path to your DVD burner may vary!)"
    fi
    if [ -d $MOUNTPATH ]; then
    echo "Using $MOUNTPATH"
    USERID=`id -u`
    sudo mount -o loop,user,uid=$USERID -t udf $UDFPATH/udf.iso $MOUNTPATH
    echo "Copy your files, umount the image and burn the dvd."
    echo -e "For burning you may just use 'cdrecord -eject -dao -dev=/dev/sr0 $UDFPATH/udf.iso'\n(the path to your DVD burner may also vary)";
    else
    echo "Creating $MOUNTPATH..." && mkdir -v $MOUNTPATH
    USERID=`id -u`
    sudo mount -o loop,user,uid=$USERID -t udf $UDFPATH/udf.iso $MOUNTPATH
    echo "Copy your files, umount the image and burn the dvd."
    echo -e "For burning you may just use 'cdrecord -eject -dao -dev=/dev/sr0 $UDFPATH/udf.iso'\n(the path to your DVD burner may also vary)";
    fi
    fi
    if [ $yesorno == n ]; then
    echo -e "All right, then mount it yourself with 'sudo mount -o loop,user,uid=`id -u` -t udf $UDFPATH/udf.iso targetdir'\nAfterwards copy your files, unmount the image and burn the dvd."
    echo -e "For burning you may just use 'cdrecord -eject -dao -dev=/dev/sr0 $UDFPATH/udf.iso'\n(the path to your DVD burner may also vary)"
    fi
    if [ $yesorno != y -a $yesorno != n ]; then
    echo "Incorrect entry, aborting..."
    echo -e " Mount it yourself with 'sudo mount -o loop,user,uid=`id -u` -t udf $UDFPATH/udf.iso targetdir\'"
    echo " Afterwards copy your files, unmount the image and burn the dvd."
    echo -e " For burning you may just use 'cdrecord -eject -dao -dev=/dev/sr0 $UDFPATH/udf.iso'\n (the path to your DVD burner may vary!)"
    exit 0
    fi
    EDIT: Some major mistakes solved.
    Last edited by ku (2009-04-23 19:02:41)

    See the second article for how to look through a list of files in a folder.
    http://stackoverflow.com/questions/7854727/loop-over-video-files-in-folder-to-ge t-video-length

  • Capture window shows the same image with Viewer

    Hi there,
    I'm trying to capture a movie from HDCAM-SR via Sony SR-5500 deck.
    Deck's settings look fine, It plays the tape very well, I can see it from it's original display screen.
    I think somethings wrong with my FCP setting.
    I use FCP 5.1. When I say CAPTURE, I see the same image in viewer and in capture windos. if the viewer is black, capture win. is black too. I tried to change my display settings, but it didn't work.
    I'm capturing it via KONA 3 card and 10 Bit Uncompressed.
    This happened before, but I don't remember how I get rid of that...
    thanks in advance

    scs...
    Can you take another shot at explaining this? I'm confused.
    CaptM

  • WINPE User & Keyboard Locale with MDT 2013 & Windows 8.1

    Hi
    I'm using MDT 2013 to deploy win8.1 (ADK 8.1 installed and so on) but I'm having trouble to set the keyboard layout when the Wizard (hta) is loaded.
    We are serving multiple countries so different keyboard settings need to be pushed for our operators when they go through the Wizard in boot.wim/PE phase.
    I opened up the boot.wim file that is generated when you update the deloyment share and generate the litetouch boot iso.
    In there I see that a basic unnattend.xml is being used which specifies the 0409:0000409 (en-US) locale.
    I was under the impression that if we made different Task sequences with their own unnattend.xml we could set the WINPE locale in the WINPE phase via the amd64_xxxx_WINPE_Neutral_xxxx component but it doesn't seem to work that way.
    I know you can provide  a locale in bootstrap.ini but that's a general setting for
    all deployments ...
    Anyone any ideas?
    My next step would be to add skipbdewelcome screen in bootstrap.ini and then have some sections in the customsettings.ini (bound to gateway or site or whatever) to set LOCALEs  in there ....
    jgs

    Hi,
    Sorry for my dilatory reply. According to your description, I doubt whether your Unattened.xml file was set correctly.
    To set default InputLocale during deployment, the correct format should like this:
    <InputLocale>0409:00010409</InputLocale>
    <SystemLocale>en-us</SystemLocale>
    <UILanguage>en-us</UILanguage>
    <UserLocale>en-us</UserLocale>
    From:
    http://technet.microsoft.com/en-us/library/cc749191(v=ws.10).aspx
    In addition, here is another thread which is similar with your problem, may be helpful with your question:
    http://social.technet.microsoft.com/Forums/systemcenter/en-US/9af61b5c-6407-44b9-87c4-a4044a94729c/change-regional-settings-keyboard-layout-and-locale-in-task-sequence?forum=configmgrosd
    Roger Lu
    TechNet Community Support

  • Error when deploying LiteTouch image using MDT 2013 Media Flashdrive

    Please help! I have created a media flash drive (drive capacity: 64Gb) to deploy LiteTouch x86 and x64 images (Win7 and Win8, 8.1) to PCs but getting error for the 3rd time. I am using the following tools in my environment: i am using MDT 2013 on a Windows
    2k8 WDS server. PXE boot works fine deploying images but i keep getting this error after creating the Media flash drive). I first got the same failure with 14 errors but recreated the media on the WorkBench using a different selection profile but now i am
    getting this error: (by the way where is the BDD.LOG?)
    "Deployment Summary
    During the deployment process, 8 errors and 0 warnings were reported.
    Details...
    Failure ( 5456): Unable to determine destination disk, partition, and/or drive. See BDD.LOG for more information.
    Litetouch deployment failed, return code = -2147467259 0x80004005
    Failed to run the action: inject drivers.
    Unknown error (error: 00001550; source: unknown)
    The execution of the group (preinstall) has failed and the execution has been aborted. An acton failed. 
    Operation aborted (error: 80004004; xource: windows)
    Task sequence engine failed! code:enExecutionFail
    Task sequence execution failed with error code 80004005
    Error Task Sequence Manager failed to execute task sequence. code 0x80004005

    I am planning to build a WDS with Win2k12 and MDT2013 and perhaps will be lucky to create a successful media. I created one with my WDS Win2k8 it works on a HP laptop but failed on other machines like Dell...
    Did you get driver injection in configuration WDS and MDT?
    Considering if the incompatible drivers cause your issue.
    If you can post back the MDT log during the deployment on DELL computers, it would be helpful for us to determine your issue.
    Kate Li
    TechNet Community Support

  • Surface Pro 3: unable to reimage with MDT 2013

    MDT 2013, Windows 8.1 with all udpates in wim file.
    Download all drivers and firmware
    http://www.microsoft.com/en-us/download/details.aspx?id=38826 to out of box. Update the Surface Ethernet Adapter in winpe. when i am booting i am getting following error, seems like its looking for "VEN_11AB&DEV_2B38&SUBSYS_045E0001&REV_00"
    i search for hwdid, but didn't find anythings. Any help?
    orion

    Hi there,
    I am using MDT 2013 on a WDS 2008 R2 and everytime i tried to image the tablet via PXE boot through the Surface Pro 3 ethernet adapter, i get this error:
    Wizard Error:
    A connection to the deployment (my deployment share) could not be made.
    The following network device did not have a driver installed.
    PCI\VEN_11AB&DEV_2B38&SUBSYS_045E0001&REV_00
    Retry: Try again to connect to the deployment share.
    Cancel: Give up, cancelling any in-progress task sequence.
    PLEASE HELP!
    YOu most likely need to add the microsoft networking adapter to the MDT console, and explicitly add it to the WinPE group. Don't forget to rebuild the deployment share so it regenerates the WinPE iamge.
    Keith Garner - Principal Consultant [owner] -
    http://DeploymentLive.com

  • Applying GPO Packs on Server 2012 R2 with MDT 2013

    Hi All,
    I'm having a problem applying a GPO Pack to Server 2012 R2 via MDT 2013 LTI offline media.
    I'm using a standard server task sequence. I've copied my GPO Pack files (created with local GPO export) to the following directory:
    DeploymentShare\Templates\GPOPacks\WS2012R2-MDTGPOPack
    GPOPack.wsf has been modified with the following
    If(Left(strOpVer,3) = "6.3") and (strProductType <> "1") then
             strOS = "WS12R2"
            ElseIf(Left(strOpVer,3) = "6.3") and (strProductType = "1") then
             strOS = "Win81"
            ElseIf(Left(strOpVer,3) = "6.2") and (strProductType <> "1") then
           strOS = "WS12"
    ZTIApplyGPOPack.wsf has been modified with the following:
    If (Left(sOSVersion,3) = "6.3") and oEnvironment.Item("IsServerOS") then
                        sOS = "WS2012R2"
                     oLogging.CreateEntry "Using Windows Server 2012 R2 GPO Pack", LogTypeInfo
                ElseIf (Left(sOSVersion,3) = "6.3") and Not(oEnvironment.Item("IsServerOS")) then
                        sOS = "Win81"
                        oLogging.CreateEntry "Using Windows 8.1 GPO Pack", LogTypeInfo
                ElseIf (Left(sOSVersion,3) = "6.2") and oEnvironment.Item("IsServerOS") then
                    sOS = "WS2012RTM"
    After creating new media I've copied my GPO Pack to the media directory:
    MDTMedia\Content\Deploy\Templates\GPOPacks\WS2012R2-MDTGPOPack
    After I create the ISO and mount in a VM the LTI works fine and I can see in temp\ZTIApplyGPOPack logs that the GPO pack is copied to C:\minint and executed but none of my GP settings are applied.
    Any ideas?
    Thanks in advance

    if you are using offline media (and not over the network deployment) maybe you are having this problem: 
    http://social.technet.microsoft.com/Forums/en-US/be2c05a0-620c-4b64-a82f-18ccc9f6cec5/apply-gpo-pack-offline-media-does-not-apply?forum=mdt

  • Cannot install PIA on Windows 8.1 64-bit with Office 2013 64-bit

    I am building a clean machine after a hard drive failure.  Everything is finally reinstalled WITH THE EXCEPTION of the Office Interop for Office 2010.  I have a clean install of Windows 8.1 which also has Office 2013 installed.
    The documentation for the 2010 library is that it only requires the framework 2.0 present (which is) so it should install.  However when I run the installation program is throws up the window "determining requirements" runs for a few seconds
    then disappears.  
    All I need is to get these things showing up in the GAC so I can get a clean build.  But try as I might I don't have them showing up at all.  Any help would be greatly appreciated!!!
    ADDITIONAL INFO:
      When I run the MSI file it brings up the window that says it is gathering information.
       This run for about 1 second (if that) moves the progress bar about halfway across, then stops and closes down the installation.
      We also installed Office 2010 and reran the PIA with the same results.  *sigh*

    Why do you need to install Office 2010 PIAs? 
    Consider embedding interop types into the assembly without using PIAs on the end user PCs.
    Beginning with the .NET Framework 4, the common language runtime supports embedding type information for COM types directly into managed assemblies, instead of requiring the managed assemblies to obtain type information for COM types from interop assemblies.
    Because the embedded type information includes only the types and members that are actually used by a managed assembly, two managed assemblies might have very different views of the same COM type. Each managed assembly has a different Type object
    to represent its view of the COM type. The common language runtime supports type equivalence between these different views for interfaces, structures, enumerations, and delegates. See Type
    Equivalence and Embedded Interop Types for more information. 
    You just need  to set the Embed
    Interop Types property to True.

  • Keep extra partition on deployment with MDT 2013

    hello all,
    I am using MDT 2013 to make the
    deployment of some workstations in the company,
    however they all have an extra
    partition (D: \),
    doing some testing I noticed that the
    MDT does clean the entire
    disk, not just on the C:\ drive.
    Is it possible to get the MDT format
    just drive the system keeping
    the extra drive (D:\)?
    Thank you.
    Eduardo Sena | Microsoft Certified Professional | Embaixador Windows 8 | MVP Windows-Expert IT Pro | [email protected] Blog - www.eduardosena.com.br

    if you are just replacing the OS, then I recommend the "Refresh" scenario. Refresh will take an existing Machine and refresh it to a new OS version, persisting the existing partition configuration.
    Keith Garner - Principal Consultant [owner] -
    http://DeploymentLive.com

Maybe you are looking for