How To Import duplicate drivers under different packages In SCCM 2007

I am currently working on building seperate Win 7 driver packages for all of our hardware and one of my colleagues came across an issue where he couldnt import a driver for a Toshiba Tecra A11 because it existed in another package.
I did some reading about how SCCM handles drivers and differentiates between them and wondered if adding an extra file into the folder would be enough to convince SCCM that it was different.

So, I added a file without an extension called "Toshiba Tecra A11 Windows 7 x64 N6200 Driver" and ran the import again and it worked!

Its not ideal and please tell me if there is a better way to do this , but it works beautifully :)

EDIT: I have just been informed by the fantastic Steve Beaumont that there IS a better way to do this, there is a hotfix available from Microsoft that allows you to import duplicate drivers:
Get the hotfix here

SCCM Attempting to load a 64bit application, however this CPU is not compatible with 64Bit mode

I got this error when PXE booting a machine and solved it by re-advertising a task sequence that uses the x86 boot image to our unknown computers collection.
The last one I advertised to this collection was a few weeks ago and as far as I remember was an x64 windows 7 TS.
This is strange behaviour but I guess it stems from the fact I have both x86 and x64 boot media advertised to the same collection, I really should look at creating 2 seperate collections for this......

Cheers

Task Sequence has failed with the error code (0x80070070).

If you get this error during a task sequence simply hit F8 to bring up a command window (if you have command support enabled on your boot media) and use diskpart to clean the disk. The following commands should do it:

Diskpart
List disk
Sel disk X
clean
exit

Cheers

SCCM Computer GUID to Hostname report

Here is an SCCM report that can conver machine GUIDs to their hostname:

select * from v_R_System where v_R_System.SMS_Unique_Identifier0='GUID:45299371-2B3C-470B-8D5C-7C42BA1CD864'

Replace the GUID with your own and it should return your computer details.

EDIT: I just discovered something REALLY interesting! you can just enter into the all systems collection

GUID:45299371-2B3C-470B-8D5C-7C42BA1CD864

And it will return the computer in question, how cool is that? :)

SCCM Windows updates stuck in downloading state

This one is for my reference more than anything but im sure it will be of use to someone else. Here is how to fix the issue mentioned above (assuming boundaries etc are all ok)

1) Under the deployment package find the KB that is failing and delete it

2) Delete the KB from deployment management

3) Delete the KB from the update list

4) Update distribution points

5) Monitor the status messages until you see the MileStone "SMS distribution manager sucessfully Processed package"

6) Find the update in the update repository and drag to the update list (dont tick box to download)

7) Copy the update to deployment management and download the update again and add it to the correct deployment package.

8) Update the DPs and again wait for the same MileStone to appear

9) run a report and watch the number of sucessful installs begin to rise

I LOVE CAKE!!

Cakephp that is :)
check out http://cakephp.org/

It is basically a MVC oriented framework for buildiing PHP applications, I have been working with it the last few days and have to say it takes so much of the heavy lifting out of building a web based php app.

but what does it do I hear you ask?

well, how does creating your database, a few tables and then running a few commands sound to get yourself a skeleton app built automatically sound? too good to be true?

Thats what I though but get CakePHP and spend the time to learn it because once you do it is going to save you so much time!
Mad props to Larry Masters the creator of CakePHP for this wonderful framework, seriously why are you still reading? go get it!, now! ^_^

SCCM Clients failing to install windows updates

Just a quick one..
I recently pushed a software update via SCCM to around 3000 clients and had around 15 come back as failing. I found that they had a value for a proxy set in the registry at this location:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Internet Settings\Connections\WinHttpSettings

Internally the clients shouldnt go via a proxy to grab these updates so I backed up the key and deleted the value WinHttpSettings
and lo and behold the updates now work!.

So now I need to find out where those clients are getting this value from and I also need to do some more testing and implement this fix
Cheers