terça-feira, 9 de março de 2010 16:55We are currently upgrading from SMS 2003/BDD 1.0 to SCCM 2007 SP2 R2 / MDT 2010 and I have a question:
With SMS/BDD you build a boot CD from SMS / Image Package node and reference zerotouchinstallation.vbs with custom settings.ini.
You then add information to the bddadmincore table which reference the mac address of the system and the package ID and program of the image that you want that particular mac address to run when the CD runs.
I have a contractor helping me and he is indicating that I have to add the system to a collection to get the task sequence advertised to it, and then boot the CD. The CD does not run a task sequence or package/program from the database. If this is true it is no longer zero touch and it seems like it is no longer "zero touch". I am not sure how I would do that?
Todas as Respostas
terça-feira, 9 de março de 2010 22:31You can enable support for unknown computers and advertise your task sequence to all unknown computers. Then you don't have to prestage the computer in the collection.
Another way is to have a webservice adding the machine to the collection in real time, after reading what image it should use from the MDT database... However, this is something you need to create, there is no built-in solution for that.
- Marcado como Resposta Tim MintnerModerator quarta-feira, 10 de março de 2010 00:20
quinta-feira, 11 de março de 2010 17:33
I sort of have the unknown computer thing going but I have to remove the system from the SMS database before the CD will work based on unknown computer.
What if the SMS client dies, or the OS dies and I have to use the CD ..do I have to add the system to a collection every tim this happens?
I was hoping to have gather or some program on the CD read the DB and then boot PE and then apply a task sequence based mac address, and then afterwards run some additional task sequences also based on that mac.
I also am having to delete tha system from the DB and then import it and add it to a collection which in order to do a push. I have a task sequence advertised to that collection.
I am currently doing this in SMS . BDD 1 so I don't see why I can't do that here.
sexta-feira, 12 de março de 2010 09:33
If the client is in the ConfigMgr database it's no longer unknown... To avoid having to delete the machine from ConfigMig before hitting F12 I created a webservice (called from the pre-execution media hook) that deletes the machine from ConfigMgr. I also use a webservice to put the machine in a given collection, either by prompting or by reading a setting from the MDT database. Since I'm executing this before the "normal" client starts, it will happily pick up the sequence.
Maik Koster has a free version of such webservice at http://mdtcustomizations.codeplex.com
The only thing is of course that he writes his webservices in VB .NET and I write mine in C#.... But we are still friends :)
sexta-feira, 12 de março de 2010 20:58Johan,
Thanks for the info:
I think I might be complicating this issue more than it needs to be unless MDT is less functional than BDD.
I do 2 things with BDD and SMS 2003 now that I can not seem to do with SCCM MDT:
1. CD Build - Create a CD that boots PE, reads a macin the MDT DB, and deploys a particular task sequence based on mac (package/program) which installs the OS and runs some stuff particular to that mac, and it does it regargless of whether the system (based on netbios and mac) are in SMS or not.
Is there a way MDT does not have to use "unknown computer" function? Is there an MDT CD or just an SCCM task sequence CD?
2. SMS Push - Add an existing system already in SCCM to a collection and have it run a task sequence against it and not have to remove it from the collection before the build is over. Currently if I do not remove it, it just builds over and over until it gets a message about limit exceeded? Alos I now have to remove the system from the DB and "import it back into the DB by mac using the import function in SCCM for it to work?
quarta-feira, 17 de março de 2010 23:02ConfigMgr 2007 is very different from SMS 2003 OSD FP. It's not MDT's fault, but MDT gives you ways to fix it...
1. ConfigMgr 2007 does have support (in R2) for unknown computers, but as for configuring what task sequence to deploy through the MDT database, sorry nope, not without a web service... I will release one to the public that does this at MMS 2010 in Las Vegas... If you need it sooner, contact me offline ( johan [dot] arwidmark [at] truesec [dot] com ) and we can most likely work it out...
2. It's a known issue with mandatory advertisments set (like always rerun). The best solution is to have the task sequence remove the client from the collection once it's setup.