Jump to content


aaronfenwick

Established Members
  • Content Count

    33
  • Joined

  • Last visited

Community Reputation

1 Neutral

About aaronfenwick

  • Rank
    Advanced Member
  • Birthday 02/06/1976

Profile Information

  • Gender
    Male
  • Location
    Oxfordshire, United Kingdom
  • Interests
    Cars
  1. sounds like corrupted import media to me... I assume youve run the office tool setup.exe /admin to output an msp file..? if you did you should kick off the command line setup.exe /adminfile mymsp.msp
  2. In vista and W7 sysprep is found under c:\windows\system32\sysprep In xp, you have to manually create a c:\sysprep folder with the sysprep cab on the XP CD expanded,
  3. Looks like all that data is in your comments box when you created the task sequence. The MDT TS selection menu displays all that. I'd re-create your TS without the comments.... i dont know of a way of suppressing those lines.. (yet)
  4. i'd remove all your apps and re-import them, then it will generate new guids. Rebuild your boot media, and you should be set, Aaron
  5. its buggy. i often find if you close the deployment toolkit (as its usually open, right?) and re-open it re-connects to the database due to time-out.
  6. Install a client, and use Driver Magician to extract all the currently used drivers off your "donor" build. Then import them into the MDT out-of-box drivers, using the WMI Manufacturer, model arcitecture. \Dell Inc.\Latitude E6400 as an example.
  7. 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
  8. Yeah easy - add this line to your rules tab in the default section... _SMSTSORGNAME=companyname where companyname is the name of the company i.e. _SMSTSORGNAME=The Big Company Inc. Then update your deployment share and re-create your boot menu from the ISO's.
  9. 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.
  10. If anyone is interested, I have just produced (today) a solution to use WDS as a PXE boot point, to Boot PE and then automatically run a batch to image a PC using imagex to a nominated (in batch) file share, we've had a lot of leavers lately and I needed a quick way of backing up a lot of machines. If anyone is interested in this, i'll document it up. Aaron
  11. 20 minutes to image, then 20-30 mins with apps (but we have a lot of self packaged apps!)
  12. Again, i point you to my doc, which I have written for noobs.. http://www.windows-noob.com/forums/index.php?/topic/5081-windows-7-deployment-guide-using-mdt-2010/
  13. Also, here is my MDT 2010 guide. http://www.windows-noob.com/forums/index.php?/topic/5081-windows-7-deployment-guide-using-mdt-2010/ Aaron
  14. sounds to me like your WAIK download is dodgy, I'd download it again, as rebuilding the deployment share is based on good winpe.
  15. Credit to Johan on this... its all him this time! https://docs.google....ZHMyTEhwQQ/edit
×
×
  • Create New...