Jump to content


aaronfenwick

Established Members
  • Posts

    33
  • Joined

  • Last visited

Posts posted by aaronfenwick

  1. You need to make sure you have your USMT4 files in your tools folder, or it will error on -2147467259 0x80004005

    (network path not found)

     

    c:\deployment share ools\USMT4

     

    with all the extracted files.

     

    Extract USMT4 msi, from a command prompt..

     

    msiexec /a (and the drag the usmt4_x64.msi or whatever the exact filename is to the command prompt window) then press Enter.

     

    The msiexec install wizard will ask you to enter a path to extract the files too.

     

    Specify c:\deployment share ools\USMT4 (or d:\ if thats where your deployment share is)

     

    Now the USMT files are there it will work.

     

    USMT=4 is not needed, MDT 2010/12 assumes USMT4.

     

    No need to rebuild boot media, as its expecting it there already, hence the -2147467259 0x80004005 error.

     

    The other big tip, is to install configmgr toolkit and run SMSTRACE.EXE and set it as your default text reader.

    This will format your BDD.Log's into a much more readable format.

     

     

    Hope that helps.

    Aaron

  2. You can add this into your task sequence....

     

    I dont specify my product key in the actual built in task sequence, instead I add 2 tasks below the Tattoo section of the State Restore Phase.

     

    Add - command line

    Name - Register Windows Product Key

    Command Line - cscript %windir%\system32\slmgr.vbs /ipk XXXXX-XXXXX-XXXXX-XXXXX-XXXXX (Where XXXX etc is your product key)

     

    Add another below that:

     

    Add - command line

    Name - Activate Windows

    Command Line - cscript %windir%\system32\slmgr.vbs /ato

     

    So not only do I specify a product key, I also activate it as part of the state restore phase.

     

    Hope this helps!

    Aaron.

  3. For drivers like this where you only seem to be able to find a .exe installer, not the raw .inf and .sys files etc,

    I have always used "driver magician".

     

    Install the exe on the machine with the issue, get the device showing as working in device manager,

    and then install driver magician and use this to harvest the drivers for that device to an output folder.

     

    Now use these drivers files in your drivers package - Usually does the trick for me....

     

    Aaron

  4. One thing this link doesn't discuss is the windows 2008 R2 firewall.

     

    Open ports:

    1433, TCP. (Database Engine)

    1434 UDP (Browser Service)

     

    This should solve your connection issue, like brendant says, if your TCPIP and Names pipes are enabled in configuration manager, under network protocols.

     

    Aaron

  5. Make sure that "Virtualization" and Intel VT are enabled in your BIOS, this enables hardware assisted virtualization which Hyper-V requires (and even VMware actually)

    Also check that the Hyper-V services start ok. (for others you get this error)

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.