locked
OSDComputername variable in a boot ISO RRS feed

  • Question

  • I have a non-pxe boot image, created for servers only. As I couldn't get the
    osdcomputername variable to work in my Task Sequence, my next step was to add
    the osdcomputername variable in a boot iso created of of the non-pxe boot
    image.

    This also didn't work. However, what did happened is quite alarming. All the Windows 7
    image attempts (using Pxe services) started to look for the non-pxe boot image
    and of course failed.

    I would like to know why this variable created this impact.

    Thank you!



    • Edited by STHLM Wednesday, November 12, 2014 6:07 PM
    Wednesday, November 12, 2014 6:07 PM

Answers

  • I just did a quick test with a deployment of a task sequence with a boot image that is available for PXE and after that a deployment of another task sequence with a boot image that's not available for PXE. The behavior was, as I expected, the machine doing a PXE boot was looking for the boot image that's not available for PXE.

    The easiest work around would be to remove the current deployment of the Windows 7 task sequence and recreate that. That way that's the latest deployed task sequence.


    My Blog: http://www.petervanderwoude.nl/
    Follow me on twitter: pvanderwoude

    Thursday, November 13, 2014 7:32 PM

All replies

  • The OSDComputerName variable does not cause behavior like that. Did you by any change add the boot image to a task sequence that is targeted to those devices?

    My Blog: http://www.petervanderwoude.nl/
    Follow me on twitter: pvanderwoude

    Wednesday, November 12, 2014 7:18 PM
  • The non-pxe boot image was only added to server TSs and not to the Win 7 TSs. I conformed that also when they reported the issue to me.


    • Edited by STHLM Wednesday, November 12, 2014 8:40 PM
    Wednesday, November 12, 2014 8:29 PM
  • But is it targeted to the same devices? For example, by targetting the Unknown computers.

    My Blog: http://www.petervanderwoude.nl/
    Follow me on twitter: pvanderwoude

    Wednesday, November 12, 2014 8:47 PM
  • Hi Peter,

    The server Task Task Sequences using the non-pxe boot image are deployed to unknown computers.

    Thursday, November 13, 2014 2:23 PM
  • If you're also deploying your Windows 7 machines by targeting the unkown computers, then that's were you're problem started. During the initial boot the machine will use the boot image of the task sequence that was deployed the latest to the machine. In this case that would be the boot image of the server deployment.

    My Blog: http://www.petervanderwoude.nl/
    Follow me on twitter: pvanderwoude

    Thursday, November 13, 2014 2:31 PM
  • That has changed from SCCM 2007 then as we had the same design when it comes to boot images, one for servers (non-pxe) and at least couple for workstations. We never had the issue of the non-pxe boot image 'taking over'.

    Here is the interesting part; the server boot image was out there for 2-3 days and didn't seem to couse an issue. It is only when the computer propt varaible was added to an iso, that I got notified.

    Thanks!

    Thursday, November 13, 2014 3:08 PM
  • I just did a quick test with a deployment of a task sequence with a boot image that is available for PXE and after that a deployment of another task sequence with a boot image that's not available for PXE. The behavior was, as I expected, the machine doing a PXE boot was looking for the boot image that's not available for PXE.

    The easiest work around would be to remove the current deployment of the Windows 7 task sequence and recreate that. That way that's the latest deployed task sequence.


    My Blog: http://www.petervanderwoude.nl/
    Follow me on twitter: pvanderwoude

    Thursday, November 13, 2014 7:32 PM