anyweb

you need to read it again, i say in production to select IP Address Range Boundaries, the linked article refers to why IP Subnet boundaries are evil see the difference ? and I quote Jason below

did you post this on technet as well? , the reason for your bitlocker failure is because it cannot communicate with your domain controller, fix that issue first and you'll be good to go

some things to check.. did you add back both architecture boot images ? did you distribute both to the dp's ? did you change your task sequences so that they are using the new boot images ?

well i install the dp role on a server 2012, no issues whatsoever, did you forget a step ?

you don't need a MDT task sequence but you do need those scripts yes, I havnt tested it in Configuration Manager 2012 yet but I think it'll work

yes you could say that they are a preference of the user, as MDT is optional and provides additional functionality, you could also note that these guides (part 17) are based on the Release Candidate version of Configuration Manager whereas the other guides are based on the RTM version (current) I will update the RTM guides with MDT relevant content when time permits

so you are just trying to install a dp on a remote server 2012 server, correct ?

and in case that article ever moves i've copied the solution below, thanks for updating your post, it's great when people do that.

full support for Windows 8 and Server 2012 will not be provided via Configuration Manager 2007 or Configuration Manager 2012 until early 2013. please review the following Microsoft statement for details of that

once you've added the driver to your boot.wim images you need to Update Your Distribution Points (not add dp's) see the screenshot below..

press f8 before it reboots, does the client get an ip address ? if not you might need to add network drivers for the network card on that client pc to your boot images and re-distribute them to the distribution points

cool it's easy when you know how isn't it

told ya ;-) to resolve you'll probably have to point out which one contains the WIM file, probably index 2.

try diskparting the hard disc before imaging it something like diskpart sel disk 0 clean cre par pri format fs=ntfs quick assign exit then reboot, and try pxe boot again, the remediation errrors you highlighted are not important at all and are only related to Network Access Protection (NAP) which you are not using.

1. only you will know if its enough or not, performance issues will show themselves very quickly though with 4gb ram, 2. yes you can have up to 250 dp's under one standalone primary 3. best to take that licensing question with your local Microsoft technical account manager 4. as long as you don't enable the Endpoint Protection role or configure it, then nothing will happen as regards Endpoint Protection

check the image index, was it different between the two ?

dont delete the computer object from the collection, delete the direct membership instead

have you deployed the task sequence to the Unknown computers collection ? were there any records in All Systems called Unknown ?

you never answer my question, is the client on the same virtual network as your configuration manager computer ? is dhcp server on the same box or on your domain controller, is that on a different lan ? abortpxe just means that it's pxe booted before but not finished properly (usually) so search for the computername in the All Systems collection, if you can't find it it's likely to be listed as unknown, delete it and restart the Windows Deployment Service, then PXE boot again....

i mean logon to your active directory domain controller using a user account that has Administrative permissions on the server, that can be any user that is a member of the builtin Administrators group on that domain controller, so you can login as Administrator or a domain admin or any user as long as they are in the local administrator group (on the DC)

sorry i meant the smspxe.log of course, can you attach it here, is the Configuration Manager server on the same network as your client ?

what does your SMSTS.log file tell you ? what error are you getting, we need more details to figure out what you are missing

it's covered very well by fellow ConfigMgr MVP and good buddy Rob right here

you are on the right track, create the new application and then create a supersedence relationship.

you can combine the settings from one XML into another the only reason i call this specific XML file "HideWirelessSetupInOOBE.xml" is that it is all it does, obviously you can create XML files in Windows SIM that do much much more than this and name them accordingly