Jump to content


Established Members
  • Content Count

  • Joined

  • Last visited

  • Days Won


PolishPaul last won the day on March 3 2012

PolishPaul had the most liked content!

Community Reputation

1 Neutral

About PolishPaul

  • Rank

Profile Information

  • Gender
  • Location
    New York
  • Interests
  1. 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.
  2. 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 \smsb
  3. (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
  4. 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 goi
  5. 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 hav
  6. 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?
  7. 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?
  8. <![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"
  9. New problem. The Task Sequence: build and capture Win 7 x64 has failed with the error code (0x00000002).
  10. 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?
  11. 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%"
  • Create New...