Cisco E4200 Router & 1080p Video streaming

Just a quick post to say that the Cisco E4200 CAN stream 1080p video with no problems using the 5GHZ Band.

I couldnt find this info out anywhere on the net and had to take the plunge and just buy this router and thank god it works beautifully :)

Currently I am streaming a 10GB+ 1080p MKV video across my network via this router straight to my Samsung Galaxy S2 and outputting to my HDTV.

So just to summarise incase anyone is wondering:

Samsung Galaxy S2 + Cisco E4200 = WIN! :)

Pre installing drivers during imaging

Recently I was faced with a challenge of how to pre install drivers for our universal USB docking stations so that a freshly imaged machine can just be handed out to a user without having to go through a manual install of the drivers beforehand.

The way I accomplished this was to use a utility found in the WDK (Microsoft Windows Driver Kit) called DpInst.exe

Here is the documentation for it:

WDK Documentation

At a high level all you basically have to do is get the drivers together in a folder with the correct version of DpInst (x86 / x64), build an XML file (called DPInst.xml) and then run it with a few switches to have it install the drivers for you. Then when a standard domain user comes along and plugs in the hardware it will automatically install it without asking for admin rights!

All you then have to do is build a package and include it in your SCCM task sequence to fully automate this tedious process :)

Thanks

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