XistEnCe

Yeah! That option came when I configured the WDS Role. 060 is set to "PXEClient" now. 066 is set to the IP of the server and 067 is set to blank for now.

Thanks for the reply! I've done the above - except the #67, as my shared folders do not contain any linkable files. If I have to put the files there myself, where would I get them from? The microsoft link you put up, doesn't go anywhere (even without the trailing . ). Still no luck in getting the clients to PXE boot..

Ran the above command, and now the previous one worked! I booted up a client and tried to PXE boot it, but its taking forever to fetch DHCP (and it fails at the end). With: PXE-E55 Proxy DHCP Service did not reply to request on port 4011. I haven't defined the #67 rule, in DHCP - could this be the problem? (As no files exists on the shares..)

When trying to run the commands on the page you linked me - I get the error: >WDSUTIL /Set-Server /UseDHCPPorts:No /DHCPOption 60:Yes Windows Deployment Services Management Utility [Version 6.1.7600.16385] Copyright (C) Microsoft Corporation. All rights reserved. An error occurred while trying to execute the command. Error Code: 0xC1030104 Error Description: The Deployment Server role service for Windows Deployment Ser vices has not been configured on the server. This is after a fresh install of WDS and PXE Role in SCCM.

Amazing webcasts! And yes, it was a good idea with a bit more volume

Now the client reports that No boot file name received and PXE-E53. This is probably linked with the file that's set in the DHCP settings? My folders are empty as stated earlier.. Why, I don't know - but it can't be a good thing? Is it possible to get a hold of those files from somewhere?

I ran through the configuration part of WDS Role, and it added the 060 value to the DHCP server. The value is set to: PXEClient and that's all good?

Yeah, I find it wierd that it's not even in the list of options to add. It should be in the list with the rest, under the scope settings - right? Seems like it could be hard to get PXE working then.. What info should I input there, in case it magically appears? I've even tried reinstalling the PXE service point, with no luck..

But should it update the WDS settings or do I have to do that? It's listed under roles with a yellow "!" and it tells me it's not configured. I read the info on the link, and entered: 060 = client Identifier (PXEClient) Could not find this in the options at all 066 = boot server host name (Tried both FQDN and hostname of the computer with SCCM and PXE) 067 = boot file name (I have no idea what info to input here, and the REMINST\SMSBoot\x86\ and REMINST\SMSBoot\x64\ folders are both empty. The only file around is boot.sdi in the SMSBoot folder (Parent dir to x*\).

When using a media (CD/DVD/USB) to run the TS, I have no problem what so ever. But still no luck on getting the PXE to reply.. I imagine it could be the WDS Role reporting to be "not configured"? Is it safe to configure it normally? Or does the "hands off the WDS Role" rule still apply?

Still having issues with no reply from the PXE servers.. If I check the WDS Role on the server, it's still listed as not configured for some reason. Is that correct? The server I'm running sccm on is also the DHCP - so I shouldn't have any problems there?

Ok, solved. The last log entry gave me the solution straight up. Extended the schema in AD, and clients are now locating the correct site!

Hi I'm having an issue with the sccm client not installing on any computers at all. I followed the tutorial, enabling client push, but when I right click a computer in a collection, and select install client - nothing happens. If I run ccmsetup.exe directly from the server, it gets installed - but it can't discover which site it belongs to. I have disabled the firewall on both the client and the server (for testing purposes). The only two Actions avalible are Use and computer policy retrieval. Even if I set the site code manually, it can not connect. Does anyone have a solution to this? Edit: The log from one of the clients show: "Failed to open to WMI namespace '\\.\root\ccm\Policy\Machine' (8007045b)" And it's got a: Attempt to auto discover site has failed. Error: 0X40002 aaaand: Unable to verify the sitecode 'BBB', AD schema is not extended or SLP is not present. Cannot continue site assignment. I'm so confused..

Thank you for the reply! I just installed the WDS service, and installed the PXE feature in SCCM afterwards. The I enabled it, and told it to reply. Clients still don't get any IP and times out to the PXE request. How do i define which dhcp server the clients should use for PXE booting?

Hi! I've just installed SCCM2007R3 with FEP2010. I'm trying to configure everything and get this show on the road - but..... When booting, the clients just wait for DHCP from the PXE server, and times out. Does the PXE boot, require the WDS service? Or is this optional? The server running SCCM is also a DHCP server, and I have defined a boundary which contains the net in the DHCP scope. Do I have to advertise anything for it to PXE boot?

Checked all the services, and which account they ran as. Set everything correctly but it still wouldn't work. I had to reinstall the SQL features, and then - for some strange reason it decided to work!

Hi there! I was wondering if anyone could give me a pointer in the right direction when it comes to installing FEP2010 with SCCM R3 and SQL 2k8 STD? When going through the checklist before install, it fails like this: Error: Setup cannot determine the SQL Integration Service version. Microsoft Forefront Endpoint Protection 2010 requires Microsoft SQL Server Integration Services 2005 Enterprise or Standard edition with Service Pack 2 or higher or Microsoft SQL Server Integration Services 2008 Enterprise or Standard edition or higher. Make sure that the component is installed, running and auto-started on server server.domain.ok. The services are started, and set to auto-start with the local system account. Any pointers on how to solve?