Improve company productivity with a Business Account.Sign Up

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1725
  • Last Modified:

PXE boot and Computer association

I am having a few problems with PXE boot, Computer association and Collections in general.

Question 1:-   Why does it take so long for a collection to update its membership?

Question 2:-  I have created a task sequence to build & capture a windows 7 image.  I then imported computer information in Computer Association,  I imported a single machine using a name and MAC address. This all seemed to work fine built the machine and then captured the image.

I then deleted the machine from the collection and then tried to add it again from the computer association into the deploy 7 collection.  However this time with a different name but same MAC address.  This completes with no errors but does not add it.

I am sure I am being very stupid but why is this not adding?  Before I deleted I clicked on "Clear last PXE advertisement".  I seem to have a similar issue with any machine I have previously tried to PXE boot or add from computer association (import information) before and then delete.
0
WNottsC
Asked:
WNottsC
  • 10
  • 8
1 Solution
 
WNottsCAuthor Commented:
An update to this is that it seems to add it sometimes if I wait a very long time for the collection membership to update, but not always.  As asked in Question 1 can someone explain why this takes so long to run?  Is it just a case that it does take that long or can it be an indicator that something is not working correctly?
0
 
woolnoirCommented:
>>Question 1:-   Why does it take so long for a collection to update its membership?

Because collections can have dynamic assignments based on other things that just static membership, it has to do a fair amount of calculations.

>Question 2:-  I have created a task sequence to build & capture a windows 7 image.  I then imported >computer information in Computer Association,  I imported a single machine using a name and MAC >address. This all seemed to work fine built the machine and then captured the image.

>I then deleted the machine from the collection and then tried to add it again from the computer association >into the deploy 7 collection.  However this time with a different name but same MAC address.  This >completes with no errors but does not add it.

Just add the machine manually to the collection , right click collection, properties and click to manually assign a machine to a domain.

I wrote an article on this process, perhaps it will help

http://www.experts-exchange.com/OS/Microsoft_Operating_Systems/Server/Systems_Management_Server/A_4516-Windows-7-Deployment-using-SCCM2007-A-simple-guide.html
0
 
woolnoirCommented:
And just to double check, after a 'update collection membership' operation, always right click and 'refresh' too. The interface tends to be a tad slow to update at times. But i'd always control collection membership through the collections themselves, as per my guide.
0
Upgrade your Question Security!

Your question, your audience. Choose who sees your identity—and your question—with question security.

 
WNottsCAuthor Commented:
thank you very much for this and I am just about to accept your solution.  Would you be able to answer one other quick question about drivers and driver packages?
0
 
woolnoirCommented:
I can try :) go ahead.
0
 
WNottsCAuthor Commented:
For the build and capture image I used an OPTIPLEX GX520 and I am currently pushing out the image back to the same machine and it seems to work fine.

However I want to use the same image for all the other types of machines I have.  In particular one from a company called Stone Computers.  The problem when I tried to capture from this machine or when I try and push the image out is that it needs a "network card driver" and "possibly a "drivers Driver"( although I thnk it will do with out this).

Question 1

I have tried downloading the latest drivers and adding them to a package. What is the relations ship between a driver and a driver package why do we need a package?

Question 2

 If the task sequence uses a X86 boot image as we have previously discussed does it need the X86 drivers or X64 drivers (sounds a stupid question as I am typing it, but I will ask anyway).

Think that is it at the moment :)  the Network card in question is the Intel(R) 82578DM Gigabit Network Connection  there are no drivers for this directly  but the 82567LM-3 has the DM as a supported model on the Applicability tab of the driver.

Hope this all makes sense sorry a bit of a noob with the drivers
0
 
woolnoirCommented:
The way i think about it are the drivers are the actual drivers , packages are groups of drivers which we apply for certain hardware builds.

You need to think about drivers in terms of the Boot image (PE) and the image you are applying. Drivers need to be appropriate for each. If you are using a x86 boot image then specifically for things like network cards you need a x86 driver. The drivers for the install image need to be appropriate too.
0
 
woolnoirCommented:
did i make any sense there ? it makes sense in my head, but maybe not yours :)

0
 
WNottsCAuthor Commented:
I undestand the part about the boot image so if we have 6 different types of machines and we were using the X86 boot image we may create 6 different driver packages for each type of machine with the 32bit drivers included.

Hope I got that correct??

The bit I am not sure on is how are drivers added to the install image.   I am sure I am being thinck but stay with me.
0
 
woolnoirCommented:
To add a driver package to a image you edit the task sequence  .
i.e
drivers
0
 
WNottsCAuthor Commented:
whats the difference or why from the screen shot have you got an "Auto Apply Drivers" task and an "Apply Driver Package" task  or is this just to show the example
0
 
woolnoirCommented:
The apply driver package in red is where you 'inject' the drivers into the work-flow, the one above (actually in the wrong order as it should be below) controls how they are applied ( you can customise it a little) - you can apply all, or only certain ones, etc. I'm still playing with driver packages at this stage - most of my SCCM work up until this point has been the deployment process and control, i'm currently working on a EE article about drivers but thats not due for another week or so :)
0
 
WNottsCAuthor Commented:
we manage to deploy the image and I now understand the driver tasks the last problem we have I promise is that when I look through the logs we have two software packages that were meant to install after the Setup windows and ConfigMgr task.

However the error message in the log for these is:-

HRESULT=80040215 (e:\nts_sms_fre\sms\client\osdeployment\installsoftware\main.cpp,374) The sms client service is not running. Install Software failed, hr=0x80040215

Any ideas?
0
 
woolnoirCommented:
edit the task sequence and check where the software install stage happens, is it after the setup windows and configmgr install stages ?
0
 
WNottsCAuthor Commented:
I think I have found the problem and a possible solution but I am not sure of the code.

The issue seems to be that as part of my task sequence I am adding software packages.  One of which is the client hotfix - KB977384 for R3.  Looking at the following microsoft article http://support.microsoft.com/kb/977384  they are saying that this is not the way that it should be done.

They aresaying that if you add this as a software package it will cause the SCCM client to stop:-

"For operating system deployments, the KB977384 hotfix must be installed during a ConfigMgr 2007 OSD task sequence in the "Setup Windows and ConfigMgr" task. Otherwise, the problem will continue to occur while the task sequence is executed. Additionally, the "Install Software" task cannot be used to install the hotfix. Trying to do this will cause the ConfigMgr 2007 client service to stop, which will cause the task sequence to fail."

I have the code they suggest in the article but I am not sure if I have done it correctly.  Do you or anyone currently do this and if so how?  I have include the code I use in the installation properties of the Setup Windows and ConfigMgr task section

SMSCACHESIZE=8000
PATCH="%_SMSTSMDataPath%\OSD\DR400004\i386\hotfix\KB977384\ sccm2007ac-sp2-kb977384-x86-enu.msp"



0
 
woolnoirCommented:
Based on the article it look right to me, the best thing to do is to create a test collection and test doing it. Based on the article, your string looks correct. What you are being told about the installation method as part of a OSD is correct, its configured during the setup configmgr stage.
0
 
woolnoirCommented:
Did you have any luck on this one ? :)
0
 
WNottsCAuthor Commented:
I may just be a little slow at the moment but from the String:-

PATCH="%_SMSTSMDataPath%\OSD\DR400004\i386\hotfix\KB977384\ sccm2007ac-sp2-kb977384-x86-enu.msp"

what does the %_SMSTSDataPath% mean  ?
what does the OSD part mean?

On the server the only physical path I can find is this one:-

\\{server name}\smspkge$\00100005\i386\hotfix\kb977384\sccm2007ac-sp2-kb977384-x86-enu.msp
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: SSL Checker

Scans your site and returns information about your SSL implementation and certificate. Helpful for debugging and validating your SSL configuration.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 10
  • 8
Tackle projects and never again get stuck behind a technical roadblock.
Join Now