anyweb

yes please include a screenshot of what you are talking about

are you using the Release Candidate of Configuration Manager 2012 ? that was replaced by the RTM release way back in April, and now Service Pack 1 beta is soon to come, I'd suggest you do all your testing on the RTM release. as regards a dp being on a primary, of course it can be there and it's added during the primary setup, have you verified what roles are installed on your server ?

hmm have you done anything different when creating this key ? this is also in SP1 beta ?

all i do is set the network card as Legacy Adaptor (check part 7 theres a setting up a virtual machine in hyperv guide linked to at the end of that post)

Today we reached an important milestone in the development of the new Office. Moments ago, the Office engineering team signed off on the Release to Manufacturing (RTM) build. This milestone means the coding and testing phase of the project is complete and we are now focused on releasing the new Office via multiple distribution channels to our consumer and business customers. This is the most ambitious release of Office we've ever done. It spans the full family of Office applications, servers and cloud services. The new Office has a fresh, touch friendly design that works beautifully on Windows 8 and unlocks modern scenarios in social, reading, note-taking, meetings and communications. We are proud to achieve this milestone and are eager to deliver this exciting release to our customers. General availability is planned for the first quarter of 2013. Starting October 19, customers purchasing Office 2010 from local retailers or resellers will receive the new Office for free upon availability. Customers will also see a preview version of the new Office on Windows RT devices, beginning with the Windows 8 launch on October 26. Additionally, we have a number of programs that provide business customers with early access so they can begin testing, piloting and adopting Office within their organizations: We will begin rolling out new capabilities to Office 365 Enterprise customers in our next service update, starting in November through general availability. Volume Licensing customers with Software Assurance will be able to download the Office 2013 applications as well as other Office products including SharePoint 2013, Lync 2013 and Exchange 2013 through the Volume Licensing Service Center by mid-November. These products will be available on the Volume Licensing price list on December 1. IT professionals and developers will be able to download the final version via their TechNet or MSDN subscriptions by mid-November. Please stay tuned for more specifics on general availability dates and other Office launch news. In the meantime, if you'd like to give the pre-release version a try, you can visit office.com/preview. Thank you to the millions of people who have been testing early releases of the new Office. We are grateful for your support. Your invaluable feedback has helped us make the new Office the best Office ever. via > http://blogs.office.com/b/office-news/archive/2012/10/11/office-reaches-rtm.aspx

you can't it's a one time deal, you can however delete the application deployment and start again

well you are missing network drivers in the apply driver package step for the hardware you are installing on, that's what it looks like your problem is, so can you confirm that ? what version of Configuration Manager are you using ?

you've setup your DP as HTTPS, do you have a PKI infrastructure ?

Jorgen has published a script on his blog to address this, here it is.

oops that's an error, i'll fix the link now.. FIXED !

and today it arrived in the post :-) awesome !

did you enable PXE ability on both boot images, did you enable it on the DP, did you enable it on the task sequence deployment ? what does the SMSPXE.log file tell you

there are SP1 guides already if you look here (look at the Windows 8 posts, UEFI, pre-provision BitLocker and more), but for this series of guides I will stick with the RTM release until SP1 is released to manufacturing.

have you verified they have the required network drivers added via an apply driver package step (you can bring up a command prompt around the time of failure and type ipconfig, any valid ip address ? can you ping the fqdn of the managment point ?)

have you double checked your Network Access Account that's it's set and set correctly ?

it's best practise to use Virtual Hardware for Building and Capturing images, that way the images remain driver free and hardware agnostic, there are plenty of free alternatives out there for virtualising, that said, are you PXE booting a computer that is in the same VLAN (network) as the network that your Configuration Manager PXE enabled distribution point ?

this guide was for configuration manager 2012 BETA 1, in other words a build that was released some years ago and which has been replaced with beta 2, release candidate 1, and RTM.....

i add this feature using a dism command line after copying the SXS files first, if you want i'll post a howto to explain the methodology

just tested it and it works in Windows 7 deployments also see screenshot :-)

there's a post here that explains the right way to do it, here it is

yeah i was going to take them in Amsterdam during Teched Europe but ran out of time, perhaps I'll try and do some of them soon

thanks ! can you attach the windowsupdate.log file from that client ?

actually it's a WinPE4 feature and as such you should be able to pre-provision BitLocker for windows 7 deployments also, I just have not tested it yet, cheers niall

if windows is ending up on D: then you are using install.wim from the Windows media (this probelm is resolved in Configuration Manager 2012 Service Pack 1).

yeah see if your notebook has a usb 2 port, does it ?