In the screenshot above you’ll see setup.cmd batch file. This is the secret to deploying the drivers using SCCM. The Intel documentation states that you can run setup.exe -s to silently install the drivers. However, when I created a software distribution package and set it to run setup.exe -s the drivers never installed and the installer routine exited due to an invalid command option. What you need to do is create a batch file which calls setup.exe -s and point the software package as the batch file, e.g.

As part of an Intel AMT deployment I needed to update the BIOS on our Dell OptiPlex desktops and Latitude laptops. I created a package to run the BIOS update and added this to the operating system task sequence.

Next, in System Center Configuration Manager (SCCM) create a standard software package. Set the command line to the BIOS file followed by -NOREBOOT –NOPAUSE . This enables the BIOS update to run silently and without rebooting the system. I additionally set the package to run “whether or not a user is logged on” using the setting on the Environment tab.

Go to your operating system deployment task sequence and choose Add -> General -> Install Software. Select the BIOS update package. Next, click into the Options tab and click “Add Condition” and select “Query WMI” and enter SELECT SMBIOSBIOSVersion From Win32_BIOS WHERE SMBIOSBIOSVersion < “A21” Replace A21 with the BIOS version you’re using for the update. This WMI Query ensures the BIOS is flashed only if it’s older than a given version. I then have a restart task to reboot the machine and flash the BIOS.

I’ve been developing a sandboxed web part for SharePoint 2010. The web part retrieves images from a SharePoint image library and uses Silverlight to display them in a slideshow. I deployed the web part solution to the live environment and added it to a simple test page. The web part displayed the images without error. In preparation for the release of the web part I added it to the home page and configured an audience to hide the web part from all but a test group of users. As soon as I added an audience to the web part it failed to load and just displayed an error. Looking in the SharePoint log file showed the error below

Searching Google indicated that the error could be due to the size of the HTTP request. In order to resolve the error I opened the sandbox solution web.config file in C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\UserCode\web.config. I added <httpRuntime requestLengthDiskThreshold = “4096” /> to the system.web section of the file according to the information here http://msdn.microsoft.com/en-us/library/e1f13641.aspx .