ZeroHour

I would probably add a setup to this guide informing people to update the task "capture the reference machine" as they need to update both the path to save the image and the account used to save the wim file.

Np, I just wondered, not used ipb that much so I did not realise.

Is it just me or is this identical to: http://www.sadikhov.com/forum/index.php Are they another partner or just someone using the same theme?

OMG I am a muppet, I found the problem. I did not realise what the setting in: Site Settings->Component configuration->Software Update Point Components->Sync settings->WSUS reporting events I had that set to "Do not create WSUS reporting events" which appears to disable status updates being posted to the wsus box from clients. I have changed it to "Create all WSUS reporting events" and things seem to be working now so far. Cheers for the help though

Hi I am eval'ing sccm right now and I was going to have a play with how it manages updates by linking it to our wsus server. The link went fine and updates are shown in the sccm console but now clients that update from the wsus server (using GP point to wsus directly) dont seem to update the database wsus uses so it states that X computer has not updated in X days even though I have manually forced the client to scan wsus. It appears approved updates are still sent from wsus but client updates are not. Is there anyway to allow clients to continue to update from wsus as normal? Right now since its just a eval I dont want to roll the sccm client out on mass. Cheers

Cheers for that, dont have current log files as I had to rebuild the SCCM server (NEVER EVER INSTALL ISA FIREWALL CLIENT!) but now I know it can be done I will take another go at it and post an update. I do love SCCM but damn microsoft need to simply it a little. Roll on 2010 as they say

Hi I have followed most of your guides here for SCCM which have helped a lot but I seem to be having problems with drivers and sysprep.inf files and I thought you may be able to clarify how it works. We mostly have no HAL problems here since its all the same hal type mostly so I figured I may be able to use one image of xp for those machines thinking I can just add the drivers to sccm in the task sequence but this does not appear to work as expected. I had not added a display driver for a client which I did a build and capture of XP on so the screen was at the incorrect res. I added the driver to the sccm driver store and thought I would kick a rebuild off using the captured image of xp I just made but now I figured the driver would be found in PE mode and windows would install it. This did not work though and the screen remained the same stating it was missing the driver. Does this injecting of drivers work for XP? I am correct in thinking I can just add device drivers into the sccm for new hardware and continue to use one image or is this a vista feature? I use a custom sysprep.inf file which is deployed but its a sysprep from a image used with WDS previously. Do I need to ensure certain lines are in/out of it? I am guessing sccm customises the sysprep as it goes along but is there a way to see what its final config sysprep is in case their is a problem with it? I hope all this makes sense. Cheers