anyweb

simply remove the values we added in the registry hack and all is good.

you could script it sure, but what is stopping you from using SCCM, have you considered MDT also ?

are you referring to EP as from being installed above or purely talking about FEP 2012 on a different version of SCCM ? please clarify

did you login as Domain Admin and try again

have you tried SCCM 2012 RC yet ? in case you didn't know i'm running a series of guides all about it, so join in and see what is new and exciting with ConfigMgr 2012 Release Candidate

nope unless you want to, but do it to the x86 boot image at least

hi there ! have you looked here yet ?

there is more than one LOGS folder, double check that you are looking in the right place, if in doubt use explorer to SEARCH your disc partitions for the file

this has been covered before in previous posts by others i'm pretty sure, but anyway try the following deselect 'enable pxe' on the dp uninstall the windows deployment service reboot re-enable PXE on the dp monitor the distrimgr.log and see what it says about the wds service does that help ?

well, glad it's working now

if you update membership a few times in a row, and then refresh the collection do you see it ?

are you deploying Windows 7 X64 ? that exml is for X86

ok and after doing the above is the Windows deployment service reinstalled (by enabling the pxe option on the dp role) and is it started ?

you need to use virtual hardware, hyperv or vmware to make the images and use imagex to capture the images. http://technet.micro...28WS.10%29.aspx

ok good, go back to your mdtsvr computer and double check that there is a pxesetup.log file, it may be in a folder that you cannot access (UAC), if it doesnt exist does your SCCM computer account have local admin access on the other computer ?

post the smsts.log file here please

when you reply simply check the more reply options which allows you to post attachments etc..

so just to confirm, you have a Configmgr pxe service point role installed on the MDT server (can you show me a screenshot of it as you see it in your sccm sites sytems, select the mdt server and see what roles are listed)

and that was answered here

ok i missed that you said about ip-helpers earlier, my bad. have you tried the following in this order:- deselecting PXE on the dp, uninstall the DP role, uninstall WDS service, reboot server, re-enable the DP role, re-enable PXE on that DP role, monitor the distrmgr.log to see what it says about the WDS service (which Enabling the PXE option will start in process).

on the mdt server, look for the pxesetup.log, what does it say

ah ok, if i'm understanding you correctly, you have a separate WDS server in this lab, which is powered off, but was in use before, that one may have configured some DHCP options...do you know ? when you start sccm 2012 rc, does the WDS service itself start or not ?

ok well i'm glad it works for you :-)

of course, restrict them to an OS that you are not running in the organisation just like in this post > http://www.windows-n...98100432004.jpg that's a screenshot from sccm 2007 but same principal applies

please clarify, what are 'pxe services' and by 'wds services' do you mean the windows deployment services Role ? are you saying that you did the following:- uninstall the Distribution Point role uninstall Windows Deployment Services Windows Role, reboot do NOT install or Configure WDS install the DP role, monitor the Distrmgr.log