PolishPaul

I believe you have to schedule it. I think i remember reading this somewhere, but when i browsed through the docs i read, i could not confirm this.

I'm trying to troubleshoot one of my labs which is having all sorts of PXE issues. I'm comparing it to my other lab that i have functioning. In some of the articles i'm reading, they suggest that i TFTP from command line to test if its working. Well, it isn't in either case and i'm beginning to wonder if it is supposed to and if this troubleshooting step is applicable/viable. Could someone confirm if this is working in their SCCM 2012 setup? Basically what i'm doing is running this command from my DC for example to my SCCM server (distribution point). tfpt -i 192.168.x.x GET \smsboot\x64\pxeboot.com You will need to add TFTP client from the windows features in server manager.

(PXE Without DHCP worked, NOW* it doesn't) I have a lab with an SCCM server with SQL and another as the Active directory server (2 servers total). These are on a private network and have a Linux DHCP/PXE setup. When i setup SCCM i never setup DHCP but i did setup PXE on the distribution point. I was able to boot up right into the SCCM server's PXE or to the Linux one if i put in a delay on the SCCM server. Last week i was trying to get PXE to chain load from another server (without success so far, but that's another post). On Monday, i look at the setup and I was no longer able to PXE into my SCCM server. Granted, i was mucking around with the settings but... How was it possible that the SCCM server received and handled PXE requests without DHCP? I was under the impression that DHCP was needed. The reason i didn't install DHCP on SCCM is because i was trying to integrate it with the exitsting Linux setup. Kinda stumped on this one...

I noticed that WDS and SCCM have their boot / PXE files in a different location (\remoteinstall\boot vs \remoteinstall\SMSboot) as Desek described. The guide mentiones setting the WDS with this command: wdsutil /set-server /bootprogram:boot\x64\pxelinux.0 /architecture:x64 Which i believe refers to \remoteinstall\boot. I tried using a different path such as \smsboot\ etc.. but i have not been able to get this to work. Somehow i feel that SCCM is doing its own thing with the PXE settings and the wdsutil is not affecting its PXE boot settings. Am i correct in that assumption? I'm going to double check my work again.... EDIT: Also, I noticed that when i do: wdsutil /get-server /show:all I get this output: SETUP INFORMATION FOR SERVER [--------------------------------------------- Server State: OS version: 6.1 WDS operational mode: Native Installation State: RemoteInstall location: C:\RemoteInstall RemoteInstall share up-to-date: Yes Boot files installed: x86 - Yes x64 - Yes ia64 - No [--------------------------------------------- CONFIGURATION INFORMATION FOR SERVER [--------------------------------------------- An error occurred while trying to execute the Error Code: 0x4E66 Error Description: <No description available> Desek, in the system that you have it working, can you get more output with that command than i did?

I'm attempting to pxe chain from either my SCCM 2012 server or from the linux server. Still not able to get it to work and i'm working out the kinks. For booting from windows, i found this article: http://www.vcritical.com/2011/06/peaceful-coexistence-wds-and-linux-pxe-servers/ however, this doesn't seem to work for me. My guess, from what i can see, is that SCCM handles the PXE configuration and not WDS. I tried to set the wdsutil settings but the PXE boot doesn't seem to respond to them. So my question is: How can i tell SCCM PXE to boot using a specific file? (goal here is to have a cusom menu like in the linked example)

I'm setting up an SCCM 2012 lab and i need to be able to integrate an existing Linux based PXE environment. Does anyone have any experience in setting up such an environment or perhaps can point me in the right direction while i try to read up on the whole topic?

regarding step "Step 4. Delegate Permission to the System Management Container" Is there any MS/Technet documentation about this delegation? I coudn't find any (looking in the SCCM2012 docs) Any reference you can point me to?

<![LOG[Failed to set log directory. Some execution history may be lost. The system cannot find the file specified. (Error: 80070002; Source: Windows)]LOG]!><time="14:18:09.390+300" date="03-02-2012" component="OSDSetupHook" context="" type="3" thread="832" file="osdsetuphook.cpp:192"> <![LOG[Executing task sequence]LOG]!><time="14:18:09.531+300" date="03-02-2012" component="OSDSetupHook" context="" type="1" thread="832" file="osdsetuphook.cpp:277"> <![LOG[Task Sequence environment not found. Task sequence completed in Windows PE.]LOG]!><time="14:18:09.531+300" date="03-02-2012" component="OSDSetupHook" context="" type="1" thread="832" file="basesetuphook.cpp:1291"> <![LOG[uninstalling Setup Hook]LOG]!><time="14:18:09.531+300" date="03-02-2012" component="OSDSetupHook" context="" type="1" thread="832" file="basesetuphook.cpp:1427"> <![LOG[Removing setup hook from registry.]LOG]!><time="14:18:09.531+300" date="03-02-2012" component="OSDSetupHook" context="" type="0" thread="832" file="vistasetuphook.cpp:143"> <![LOG[successfully removed C:\Windows\system32\OSDGINA.DLL]LOG]!><time="14:18:09.531+300" date="03-02-2012" component="OSDSetupHook" context="" type="1" thread="832" file="basesetuphook.cpp:1183"> <![LOG[successfully removed C:\Windows\system32\OSDSETUPHOOK.EXE]LOG]!><time="14:18:09.546+300" date="03-02-2012" component="OSDSetupHook" context="" type="1" thread="832" file="basesetuphook.cpp:1183"> <![LOG[successfully removed C:\Windows\system32\_SMSOSDSetup]LOG]!><time="14:18:09.562+300" date="03-02-2012" component="OSDSetupHook" context="" type="1" thread="832" file="basesetuphook.cpp:1220"> <![LOG[successfully finalized logs to SMS client log directory from C:\Windows\CCM\Logs]LOG]!><time="14:18:09.578+300" date="03-02-2012" component="OSDSetupHook" context="" type="1" thread="832" file="tslogging.cpp:1542"> This is the smsts.log on the win7 machine. EDIT: So i went through all the settings once more and (as usual) i made a mistake. In Step 6. Create the Build and Capture Task Sequence, i pasted in the line SMSMP=sccm.server2008r2.lab.local without updating it to my domain! <facepalm> Looks like the capture is working this time around.

New problem. The Task Sequence: build and capture Win 7 x64 has failed with the error code (0x00000002).

Hello and thank you for your tutorials. I'm getting stuck on the Task Sequence after PXE booting. I enter my password and get the 80004005 error. Here's what I'm doing: I'm using Hyper-V 2008R2, created a virtual machine and i'm able to network boot. I'm unable to interrupt the bootup with F8. Once the PE is initialized, it asks for my password. After typing it in, it fails. I can't see anything in the SMSPXE.log logs about that issue. Kinda stumped here. I've been reading this forum post's replies and trying what i can, but no luck so far. This looks like a permissions issue? EDIT: I enabled Command support on the x64 package and was able to get to the smsts.log. Turns out I'm having the same issue as lishi. The virtual machine is getting DHCP from my router and not the DC. I'm going to have to figure out how to have it poll the DHCP from my DC. EDIT 2: So yes, my VM is getting my router's DHCP settings. I edited the hosts file in the PE environment (notepad x:\windows\system32\drivers\etc\hosts) and punched in the hostname of my SCCM server. Does anyone have any suggestions on how to run this in a lab so that I'm picking up the right DHCP/DNS server? The Hyper-V server is on a standard home internet connection.

Thanks for these tutorials! For creating a Windows x64 collection, does the query that you provided in Part 5 need to be altered to filter for x64? select * from SMS_R_System where SMS_R_System.OperatingSystemNameandVersion like "%Workstation 6.1%"