Jump to content


ersatyle

Established Members
  • Posts

    26
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by ersatyle

  1. hi guys, first of all thanks for all those wonderful material, the guides and all the screenshots are really really useful! I'm starting a project of deployment for windows 7 through sccm, I read all the guides here and a lot of other, but surely I did miss something: I was able to build, capture and deploy an installation on an existing computer (meaning it did already appears in sccm), however if I try any of those operations and a bare metal computer I get the message "failed to run task sequence" - "there are no task sequences for this computer" At this time I don't have pxe enabled, so I'm creating a bootable media, ticking "enable unknown computer support" Doing this my understanding is that any computer running this bootable media should be able to "see" the task sequence, and run it, but it keep saying (in smsts.log) Client does not have an ID. Please ensure you have created a record for this client in the SMS database. Invalid advise flags (Error: 80040001; Source: Windows) Even if I try to add the computer manually (comport Association > import computer information) with the correct MAC it won't work, and the computer is not added to the specified collection (maybe it's linked with that The computer associations are not created by the import computer information wizard in SCCM 2007 Service pack 2 , I can't install the fix for now) and anyway I don't want to add manually those info in sccm, I want to install the new computers on the fly. Is there a way to achieve that, or did I misunderstood something in the concept? As I said with an existing computer everything is fine, I can deploy the OS, the media works well Is the fact that we don't have pxe could be the cause? If some of you have any ideas I'd be glad to hear them, thanks!
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.