anyweb

R2 doesn't support Windows XP at all, you'd need to import a WinPE 3.1 boot wim in to R2 just to properly deploy Windows XP, and the version of USMT would be USMT 4

ah good old typos they get us all

I havn't added that post yet, hopefully soon

well the fish has come and gone twice with to 'public betas' of Windows 8, so it's quite likely we'll see another version of it in the future

dont do anything in wsus, your SUP controls what wsus syncs and when

well you need to deploy whatever script you have to a collection and to run hidden test the script on a virtual machine and run the script with system permissions *use psexec to test it*

the fish was jut part of Windows 8.1 preview

are those rare systems in the right collection or not ?

works fine, you can either disable bitlocker in Windows and then reboot and migrate your data via hardlinking or disable bitlocker in WinPE using some logic like you have here CM12 in a Lab -The CM12 BitLocker FrontEnd HTA - video CM12 in a Lab - The CM12 BitLocker FrontEnd HTA

great stuff, hope this helps others

if Microsoft release out of cycle patches then deploy then without an ADR (just create a regular SDR to deal with out of cycle patches).

did you follow my guide exactly ? did you set UDA options on the distribution point ?

if you want to patch systems with updates released before you started your cycle then create baselines for each year containing updates for that platform eg: Windows 7 updates - 2013 Baseline Windows 7 updates - 2012 Baseline and so on....

the clients will get their updates from the sources in the order that you specify so if you specify only UNC shares then that's where they'll get them from, is that enough info ?

when the guide was written (RTM) there was no such option. But I will amend it for everyones benefit.

welcome Nigel

what is the version number listed in control panel for your Windows ADK 8.1 ?

are you using at least 1gb of ram in your deployment test machine ? what errors are your logs telling you ?

the links i provided are the same url's used to automatically update definition updates from Microsoft, see here If you are running a 32-bit Windows operating system, download the latest updates manually at http://go.microsoft.com/fwlink/?LinkID=87342 (http://go.microsoft.com/fwlink/?LinkID=87342). If you are running a 64-bit Windows operating system, download the latest updates manually at http://go.microsoft.com/fwlink/?LinkID=87341 (http://go.microsoft.com/fwlink/?LinkID=87341). if you want to get more details about when they are updated see this link

the restriction is because the Client os (windows 7, windows 8, etc) can not host Windows Deployment Services, that is a server service, therefore you cannot enable PXE on dp's running on a client os. you can however enable PXE on a dp on a server running Server 2012 R2 no problem

you can also deploy EXE files by manually specifying the application deployment type

thanks ! as to your issues 1. are you using the Microsoft Surface nic ? 2. try installing the configmgr console on a windows 7 computer and create the standalone media there cheers niall

have you seen CM12 in a lab - Part 17. Using MDT 2012 RC1 with Configuration Manager 2012 CM12 in a lab - Part 18. Deploying a UDI Client Task Sequence or http://www.windows-noob.com/forums/index.php?/topic/4045-system-center-2012-configuration-manager-guides/

no problem, you did the right thing by posting here and including a screenshot :-)

at first it looks like the network is ok <![LOG[Found network adapter "Intel® PRO/1000 MT Network Connection" with IP Address 192.168.1.146.]LOG]!><time="19:39:10.825+480" date="11 but then theres loads of dns failures like this so either you have DNS issues or its dropping the ip address, can you ping the FQDN of your mp after it fails ?