I couple of things I need help understanding.
1. What is the difference between drivers and driver packages? 2. I have set up pxe service point for sccm, and it is working properly, for bare metal osd deployments you advertise the TS to unknown computers is this correct?
May 28th, 2012 8:19am

Hi, Drivers are imported in the SCCM DB and the actual files are placed in Driver Packages, in SCCM 2007 you can create a Driver Package and deploy it with importing the drivers. Check out this blog post series from Ben Hunter: http://blogs.technet.com/b/deploymentguys/archive/2008/02/15/driver-management-part-1-configuration-manager.aspx 2. You can advertise a TS to unknonw clients, you can also choose to import the computers in the SCCM DB before installing them, that is the two options available. Regards, Jrgen-- My System Center blog ccmexec.com -- Twitter @ccmexec
Free Windows Admin Tool Kit Click here and download it now
May 28th, 2012 8:37am

Drivers in ConfigMgr are the actual imported drivers into ConfigMgr and Driver Packages are used for distributing the content of the drivers. So when you want to 'inject' drivers during a task sequence they Always have to be part of a package.That's one way, the other one is advertising to a 'custom' collection and importing the computer-objects into that collection by using the Import Computer Information Wizard (or a custom script/hta). My Blog: http://www.petervanderwoude.nl/ Follow me on twitter: pvanderwoude
May 28th, 2012 8:38am

So if I want to create a driver package which will be installed with an OSD deployment, I should import them into the sccm db using drivers first BEFORE creating the driver package? also should I be adding them to the boot images?. How do I import an unknown computer in the sccm db, I have never done that before. Thanks as always for your help and advise it is always appreciated.
Free Windows Admin Tool Kit Click here and download it now
May 28th, 2012 9:49am

It doesn't matter if you import the drivers first or create the driver package first, as long as you add them to a driver package before you use them. Importing a computer into ConfigMgr can be done by using the Import Computer Information Wizard (http://technet.microsoft.com/en-us/library/bb632330.aspx ). Keep in mind that doing this will make the computer known in ConfigMgr.My Blog: http://www.petervanderwoude.nl/ Follow me on twitter: pvanderwoude
May 28th, 2012 10:32am

is it even necessary to import them into the the sccm db? or can I just create the driver package db without even importing them? I just set up pxe for sccm, I was watching this video can you tell me how this was done with a list of options etc?, I'd like to set up something like this in our environment. http://www.youtube.com/watch?v=eBPJg23-bWI&feature=results_video&playnext=1&list=PL8B2125757A368643
Free Windows Admin Tool Kit Click here and download it now
May 28th, 2012 10:40am

One quick point on the drivers vs driver packages: drivers are files and ConfigMgr uses packages to deliver files to clients. Thus, drivers must be in a driver package to be available to the client. Technically, yes you must import the driver into ConfigMgr via the console to add it to a driver package. There is an unsupported workaround where you do not have to import drivers, called the Johan method, but that method no longer works in 2012.Jason | http://blog.configmgrftw.com | Twitter @JasonSandys
May 28th, 2012 10:47am

is it wise to integrate MDT 2010 into sccm 2007? I been doing a lot of reading have anyone of you done this?. what are the benefits?
Free Windows Admin Tool Kit Click here and download it now
May 29th, 2012 10:18am

There is no down-side to doing so. Just because you integrate it does not mean you have to use it and it is easily uninstalled. Integration with ConfigMgr simply means adding a few items to a couple of context menus and makes the MDT tasks available in the TS editor. This is no way affects, obscures, or overwirites the core OSD functionality which will still be completly available. Now, if you are asking "should" you use MDT in conjunction with OSD, well, that's a much bigger question. Obviosuly, if you want to use the extended capabilities of MDT, then yes you should. There is no requirment to do so though and many use OSD very effectively without MDT.Jason | http://blog.configmgrftw.com | Twitter @JasonSandys
May 29th, 2012 12:42pm

Assuming it was done with BGInfo: http://blogs.technet.com/b/cameronk/archive/2010/04/28/snazzy-osd-status-with-bginfo.aspxJason | http://blog.configmgrftw.com | Twitter @JasonSandys
Free Windows Admin Tool Kit Click here and download it now
May 29th, 2012 7:52pm

thanks Jason. Since others here have more experience with sccm then I thus far can you take a look at the following video http://www.youtube.com/watch?v=eBPJg23-bWI&feature=results_video&playnext=1&list=PL8B2125757A368643 Do you have any idea how the system info was put on the background of winpe? As well as the status menu with the arrows also in the background? I am asking out of curiosity as I am trying to figure it out.
May 29th, 2012 7:53pm

Assuming it was done with BGInfo: http://blogs.technet.com/b/cameronk/archive/2010/04/28/snazzy-osd-status-with-bginfo.aspxJason | http://blog.configmgrftw.com | Twitter @JasonSandys
Free Windows Admin Tool Kit Click here and download it now
May 29th, 2012 7:58pm

wow Jason, even the progress menu would have never thought it was all bginfo. I am trying to water down pxe/sccm to something easy like this for our techs in our environment. A lot of people seem intimidated by sccm since we are migrating from symantec ghost.
May 29th, 2012 8:33pm

Stone Age to Modern Era. Jason | http://blog.configmgrftw.com | Twitter @JasonSandys
Free Windows Admin Tool Kit Click here and download it now
May 29th, 2012 8:36pm

yeah exactly. So If I understand it correctly the progress menu is basically 5 different bitmaps?, that refresh every time I step is done? I was looking at the link you gave me I have noticed the link to the source code is gone. do you know exactly what source code they are talking about in this blog.
May 29th, 2012 8:42pm

Just about everything talked about in that blog was incorporated into UDI which is part of MDT now but does not actually require MDT. You should be able to find everything in the MDT 2010 Update 1 download. It should be part of MDT 2012 also but not 100% sure.Jason | http://blog.configmgrftw.com | Twitter @JasonSandys
Free Windows Admin Tool Kit Click here and download it now
May 29th, 2012 8:53pm

Thanks Jason, If you have a moment I am having trouble understanding a section of the blog.I am having trouble understanding this. Setup the task sequence. Setting up the Task Sequence Assuming all the required files exist in one directory, a method for calling the appropriate Step is necessary. This can be accomplished through a batch file containing the following: "%~dp0bginfo.exe" "%~dp0step_0%1.bgi" /nolicprompt /silent /timer:0 In this manner, your Task Sequence would simply reference the package and call the batch file with a Step number:
May 30th, 2012 9:24am

It's about creating a batchfile and calling it in a Run Command Line -step during a Task Seqeunce.My Blog: http://www.petervanderwoude.nl/ Follow me on twitter: pvanderwoude
Free Windows Admin Tool Kit Click here and download it now
May 30th, 2012 3:46pm

It's about creating a batchfile and calling it in a Run Command Line -step during a Task Seqeunce.My Blog: http://www.petervanderwoude.nl/ Follow me on twitter: pvanderwoude
May 30th, 2012 3:47pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics