+ Post New Thread
Results 1 to 15 of 15
O/S Deployment Thread, pxe boot and sccm in Technical; I need help, soon be mental help if I donít soon get this working. Iíve been setting up a SCCM ...
  1. #1
    andy_nic's Avatar
    Join Date
    Jun 2008
    Location
    Peterborough
    Posts
    445
    Thank Post
    31
    Thanked 39 Times in 33 Posts
    Rep Power
    19

    pxe boot and sccm

    I need help, soon be mental help if I donít soon get this working.
    Iíve been setting up a SCCM 2012 SP1 server Iíve got a boot image distributed; Iíve set up dhcp 66 to the IP address of the server and 67 to smsboot\x86pxeboot.com
    But when I boot the PC to PXE boot I get a blue screen of death.
    But what I donít get is how PXE boot works let me explain
    1.Boot PC to pxe
    2.goes to dhcp
    3.gets server and bootpath
    loads boot file.
    But what if I have 2 boot files such as windows 8 and windows 7?
    Please help this is week 3 of setting up sccm 2012 sp1 and its starting to my head in. Iíve followed a book and youtube videos and tutorials and still it wonít work.

  2. #2
    Sam_Brown's Avatar
    Join Date
    Sep 2009
    Location
    Northampton
    Posts
    516
    Thank Post
    89
    Thanked 29 Times in 27 Posts
    Rep Power
    15
    You'll download the .com file and this is basically nothing more than a tiny program to enable you to then download the Windows PE Boot Image (this is what handles all the tools to image your computer). Providing you're fully 64-bit compatible you should only need one .com file and one Boot Image.

    Funnily enough my option 67 is set to...

    smsboot\x64\wdsnbp.com

    Once you get that far that Windows PE has been downloaded then you get to chose what Task Sequence you want to run etc. This is when you get to chose what images you want to use such as Windows 7 or Windows 8.

    Blue screen could be you're trying to run the wrong boot image such as trying to run x64 on a x86 system or that it doesn't have the right network drivers in it. Could also be the hard disk. Try setting the bios HDD settings to Legacy. This has fixed some of our issues before.

  3. Thanks to Sam_Brown from:

    VeryPC_Colin_M (7th August 2013)

  4. #3
    andy_nic's Avatar
    Join Date
    Jun 2008
    Location
    Peterborough
    Posts
    445
    Thank Post
    31
    Thanked 39 Times in 33 Posts
    Rep Power
    19
    when i change it, it now come up with
    "The details below show the information relating to the pxe boot request for this computer. please provide these details to your WDS administrator so that this request can be approved

    peading request ID 6
    Message from admin
    Please wait. SMS is looking for policy
    "

  5. #4
    Sam_Brown's Avatar
    Join Date
    Sep 2009
    Location
    Northampton
    Posts
    516
    Thank Post
    89
    Thanked 29 Times in 27 Posts
    Rep Power
    15
    That's good news. Basically means it's talking to the SCCM server but the SCCM server doesn't have anything deployed to the collection the PC \ Laptop you're booting from is in.

    A few steps you may have missed...

    * Create Task Sequence - This is where you'll set what O\S to install, what drivers to use, what Applications to install etc etc.
    * Distribute Content - You'll have to make all the content the TS needs to run available on a Distribution Point. This is things like the O\S image, Boot Image, Drivers etc.

    * Deploy the TS to a Collection - Basically make this Task Sequence available to the computers in a specific collection. If it's a new computer not in a collection already then deploying it to the UNKNOWN COMPUTERS collection is probably the way you want to go although please please bare in mind the below...

    IMPORTANT!!! - Make sure when deploying your TS to set it to "AVAILABLE" and "ONLY MEDIA AND PXE". The last thing you want is to accidentally start to re-image everything on your network with the Config Manager Client on it! Setting it to REQUIRED and pushing it to a large collection is a sure fire way to accidentally re-image everything on your network!
    Last edited by Sam_Brown; 7th August 2013 at 04:16 PM.

  6. #5
    andy_nic's Avatar
    Join Date
    Jun 2008
    Location
    Peterborough
    Posts
    445
    Thank Post
    31
    Thanked 39 Times in 33 Posts
    Rep Power
    19
    i've got a task for a collection with just 1 PC in Hyper V i had the client software, i'm trying to do a build and capture task. if i log in to the PC and look at System center client i can see the task.

  7. #6
    Sam_Brown's Avatar
    Join Date
    Sep 2009
    Location
    Northampton
    Posts
    516
    Thank Post
    89
    Thanked 29 Times in 27 Posts
    Rep Power
    15
    That might mean you've made the TS available to "ONLY CONFIGURATION MANAGER CLIENTS" when you deployed the TS. You could try redeploying it and altering where it's made available to. You've got a few things to try really. But the first thing is making sure it's set to a deployment type where PXE is allowed.

    As for Build and Capture. There was a topic on here a while back about the merits of it. Personally I never saw the benefits of Deploy and Capture over building a machine from scratch using the default INSTALL.WIM although I know there are people who disagree with me on that one! I did try it although it though although found it created a few issues I never had time to fix so resorted to building from scratch which has always worked so far!
    Last edited by Sam_Brown; 7th August 2013 at 04:29 PM.

  8. Thanks to Sam_Brown from:

    andy_nic (8th August 2013)

  9. #7
    free780's Avatar
    Join Date
    Sep 2012
    Posts
    896
    Thank Post
    41
    Thanked 67 Times in 64 Posts
    Rep Power
    17
    You also need to provide additional switches for when the sccm client is installed in the build and capture. This is because the vm will never be on the domain. SCCM has taken several test installs to get right. Its a complex beast.

  10. #8
    Sam_Brown's Avatar
    Join Date
    Sep 2009
    Location
    Northampton
    Posts
    516
    Thank Post
    89
    Thanked 29 Times in 27 Posts
    Rep Power
    15
    I wish I'd have known this at the time! Probably why my client kept on screwing up! Would build a computer based on a BnC image and the client would never install properly! You think this is related to what you're talking about?

  11. #9
    free780's Avatar
    Join Date
    Sep 2012
    Posts
    896
    Thank Post
    41
    Thanked 67 Times in 64 Posts
    Rep Power
    17
    Also you need culmative update 1 think 2 is out as well as the cert on one of the msi's signing/cert is out of date. CCMSetup.exe /mp:SMSMP01 /logon SMSSITECODE=AUTO FSP=SMSFP01
    Make sure you use fqdn for servers. I usually specify the site code.

    http://technet.microsoft.com/en-us/l.../gg712298.aspx
    Last edited by free780; 7th August 2013 at 05:24 PM.

  12. #10
    Sam_Brown's Avatar
    Join Date
    Sep 2009
    Location
    Northampton
    Posts
    516
    Thank Post
    89
    Thanked 29 Times in 27 Posts
    Rep Power
    15
    Quote Originally Posted by free780 View Post
    Also you need culmative update 1 think 2 is out as well as the cert on one of the msi's signing/cert is out of date. CCMSetup.exe /mp:SMSMP01 /logon SMSSITECODE=AUTO FSP=SMSFP01
    Make sure you use fqdn for servers. I usually specify the site code.

    How to Install Clients on Windows-Based Computers in Configuration Manager
    When creating a TS based off a Windows image captured from a B&C do you need to add installing the Config Client in the TS as well? Or is the fact it's captured already in the image from the B&C process enough? This may be where I was going wrong. Deploying it in the original B&C image and then again in the TS based on that captured B&C image...

    I hope that makes sense!

  13. #11
    andy_nic's Avatar
    Join Date
    Jun 2008
    Location
    Peterborough
    Posts
    445
    Thank Post
    31
    Thanked 39 Times in 33 Posts
    Rep Power
    19
    It works, changed the boot to smsboot\x86\wdsnbp.com and the deployed task to only media and PXE, So is it possible to move images from WDS to SCCM, without rebuilding?

  14. #12

    localzuk's Avatar
    Join Date
    Dec 2006
    Location
    Minehead
    Posts
    17,528
    Thank Post
    513
    Thanked 2,406 Times in 1,862 Posts
    Blog Entries
    24
    Rep Power
    822
    Quote Originally Posted by Sam_Brown View Post
    When creating a TS based off a Windows image captured from a B&C do you need to add installing the Config Client in the TS as well? Or is the fact it's captured already in the image from the B&C process enough? This may be where I was going wrong. Deploying it in the original B&C image and then again in the TS based on that captured B&C image...

    I hope that makes sense!
    Indeed, you add the client in both the B&C TS and the deployment TS. The reason being - part of the process uses the client to do things. But when you finish the capture, the client settings are stripped I believe.
    Last edited by localzuk; 8th August 2013 at 09:31 AM.

  15. #13
    free780's Avatar
    Join Date
    Sep 2012
    Posts
    896
    Thank Post
    41
    Thanked 67 Times in 64 Posts
    Rep Power
    17
    bc.png
    This is what I did in the b and c config. We decided on GPO for the client for existing computers you spicy the MP and smssitecode in group policy. I also put the into the program section for the config manager client upgrade package.

  16. #14
    Sam_Brown's Avatar
    Join Date
    Sep 2009
    Location
    Northampton
    Posts
    516
    Thank Post
    89
    Thanked 29 Times in 27 Posts
    Rep Power
    15
    @andy - Not something we've had to do before but certainly worth a test. You could try importing one of the old .wim files into SCCM under the "OPERATING SYSTEM IMAGES" part and using it in a task sequence. Really have no idea if it will work or not though.

  17. #15
    free780's Avatar
    Join Date
    Sep 2012
    Posts
    896
    Thank Post
    41
    Thanked 67 Times in 64 Posts
    Rep Power
    17
    If you use images created using WAIK or from win 7 media they wont be fully supported. SCCM 2012 SP1 is supposed to use the ADK for its boot images. There is limited support in CU2 i believe Description of Cumulative Update 2 for System Center 2012 Configuration Manager Service Pack 1 Waik would have needed the 3.1 supplement. Unless your imaging P4 computers (hope not) go with ADK.

SHARE:
+ Post New Thread

Similar Threads

  1. Windows CC4 PXE Boot and Mac Netboot
    By mdrabble in forum O/S Deployment
    Replies: 3
    Last Post: 22nd November 2012, 11:27 AM
  2. PXE booting and bootfiles
    By Hedghog in forum O/S Deployment
    Replies: 2
    Last Post: 23rd June 2010, 12:32 PM
  3. WDS and PXE booting
    By powdarrmonkey in forum Wireless Networks
    Replies: 3
    Last Post: 19th June 2008, 09:44 PM
  4. Altiris Deployment Solution Server and Pxe Boot howto?
    By roland in forum How do you do....it?
    Replies: 1
    Last Post: 24th January 2008, 09:13 AM
  5. LTSP Problems with TFTP and PXE boot
    By Joedetic in forum Thin Client and Virtual Machines
    Replies: 3
    Last Post: 18th May 2006, 04:40 PM

Thread Information

Users Browsing this Thread

There are currently 2 users browsing this thread. (0 members and 2 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •