locked
Image Deployment Question RRS feed

  • Question

  • I have to roll out a large number of images with SCCM 2007 (latest configuration). Windows 7 Ent edition.

    These are computers that are not domain members yet (but will be after imaging) and not presently assigned to the SCCM site code. Basically they come out of the box with an image I need to replace.

    So I was going to try this: manually add the computer name to SCCM in a separate collection. Create a task sequence for imaging then advertise it to the collection containing the new computer names. Then boot the computers to be reimaged with boot CD created by SCCM to run the task sequence. These have to be static addresses (we can't use DHCP) so I was going to address the NIC after getting booted with the task sequence wizard.

    Prior to doing this I will also have gone to DNS on the DC and assign them all an address.

    Does this sound like something that would work? Thanks for any tips or advice.

    Sunday, June 9, 2013 2:01 PM

Answers

  • Sorry, I have no idea what "task scheduled" is? Are you referring to a task sequence advertisement? If so, then yes, absolutely. Boot media is just one way to deliver WinPE to the target system and kick off a TS advert in addition to PXE and within the OS itself. All three are identical as far as OSD is concerned and all three simply deliver WinPE to get the ball rolling.

    Please refer to the link I posted above on using Unknown Computer Support.


    Jason | http://blog.configmgrftw.com

    • Marked as answer by Highspeedlane Tuesday, June 18, 2013 9:25 PM
    Monday, June 10, 2013 1:13 AM

All replies

  • Why not use unknown computer support: http://technet.microsoft.com/en-us/library/cc431374.aspx ? This was added with R2 so you need either R2 or R3.

    Why can't you use DHCP? Not having DHCP in an enterprise environment is absurd (probably not your fault, but still, it makes *everyone's* life more difficult and there honestly are no real reasons not to use it except misconceptions and false requirements to track things by static IP that can be satisfied other ways).


    Jason | http://blog.configmgrftw.com

    Sunday, June 9, 2013 5:56 PM
  • Why not use unknown computer support: http://technet.microsoft.com/en-us/library/cc431374.aspx ? This was added with R2 so you need either R2 or R3.

    Why can't you use DHCP? Not having DHCP in an enterprise environment is absurd (probably not your fault, but still, it makes *everyone's* life more difficult and there honestly are no real reasons not to use it except misconceptions and false requirements to track things by static IP that can be satisfied other ways).


    Jason | http://blog.configmgrftw.com

    Hi Jason,

    We are prohibited from using DHCP. Our PC's use a protected (static) IP address scheme and port address translation at the firewall to two public IP addresses. It is just what we have to put up with.

    I have to use a proprietary Windows 7 image with one remaining rearm. I have had no luck getting the task scheduler for image distribution to run if the command is sent from SCCM (we have R3) using this image. If I create a boot disk and use that, address the NIC and point it to the SCCM, it picks up the scheduled task and runs it. That was from a PC that was already joined to the site code.

    The task scheduler seems to be working fine, the service is running, but I can't remember the errors (my notes are at work). But if disk booting it works I can use that.

    I'm hoping my plan will work, but have yet to test it out.

    If you need more details let me know, but I appreciate your assistance.

    Sunday, June 9, 2013 7:01 PM
  • One additional question since a lot of this hinges on DHCP, but may be outside the scope of this topic. I wonder if I could temporarily enable DHCP for this group of computers, only for the purpose of using SCCM unknown device support?

    I have Windows Server 2003 R2 Ent for DC's. I recall from memory the DHCP service runs on them. I know I could look into that, so long as it's only temporary and for the purpose of imaging, then revert them back to static afterward.

    Just thinking out loud (I know, a dangerous thing:)

    Sunday, June 9, 2013 7:43 PM
  • Unknown Computer Support does not require DHCP. Only PXE requires DHCP. Those are two completely different things.

    Wow, one rearm left? My condolences, I won't belabor that except to say that's ridiculous. It really has nothing to do with deploying it though.


    Jason | http://blog.configmgrftw.com

    Sunday, June 9, 2013 11:12 PM
  • Thanks Jason. I am extremely newb at this so that's why I'm asking such basic questions.

    I'm hoping to be able to boot the PC's using the boot utility for task scheduled OS deployment and get this to work, thus my questions.

    I'll report back if I can get it to work. Thanks for your help.

    Sunday, June 9, 2013 11:45 PM
  • Sorry, I have no idea what "task scheduled" is? Are you referring to a task sequence advertisement? If so, then yes, absolutely. Boot media is just one way to deliver WinPE to the target system and kick off a TS advert in addition to PXE and within the OS itself. All three are identical as far as OSD is concerned and all three simply deliver WinPE to get the ball rolling.

    Please refer to the link I posted above on using Unknown Computer Support.


    Jason | http://blog.configmgrftw.com

    • Marked as answer by Highspeedlane Tuesday, June 18, 2013 9:25 PM
    Monday, June 10, 2013 1:13 AM
  • Okay, got the process working and tested out with boot media and a TS for image deployment. Success. Very grateful for your assistance.
    Tuesday, June 18, 2013 9:25 PM