I was out this morning looking for an update to the device ID file for Craig Hart's PCI32 bus sniffer and was disappointed to find that the domain where it was formerly hosted is no longer in existence. (Or perhaps there is a DNS issue somewhere.)
The website listed in the README file is: http://members.datafast.net.au/dft0802 and it is yielding a 404 error, while the base address is connecting to http://w3.eftel.com.au/home.cms
In any case, it seems that either the web crawlers are not updated with the new location, (whereever that may be) or this tool and it's creator have disappeared. I would hate to see this tool fall off the face of the earth, so I'm going to post a zip file of the last version I downloaded for those who may have an interest in using it, or posting its new location here.
The last PCIDEVS update I have is from June of 2009.
Cheers!
Our network team wanted IPV6 turned off on Windows 7 machines so I put together this reg hack and package to deploy it via SCCM.
.reg file:
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\TCPIP6\Parameters]
"DisabledComponents"=dword:ffffffff
Program command line:
regedit /S "Disable_IPV6.reg"
I've been finalizing an XP image for the Lenovo X-201 laptop and had a warning on the TPM device, ACPI\SMO1200. I found the driver here:
http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-74404
Silent installation: STM_TPM_Setup.msi /q
One thing I found a bit amusing was that the driver package was created with a piece of freeware - which I thought was a bit odd. But, I suppose this may be typical with some third-party devices.
We had a neeed for this for our developers so I thought I'd make a how-to video in case someone else had a need.
Format: wmv
Duration: 1:30
I've written a few items concerning adding WMI queries to driver packages within the OSD task sequences within SCCM2007. Recently I hit a snag which was somewhat perplexing until I decided to browse the WMI with several different tools.
Generally, I've taken to browsing the WMI on various computers models with SCCM Client Center as it is very good, all-purpose tool. As I was building a model injection task sequence for Windows 7 (x64) I discovered that none of my WMI queries for Win32_ComputerSystem.Model were functioning. Where they had performed flawlessly in Windows XP they were failing in Windows 7.
For example:
Running the following query on an OptiPlex 755 returned a 0 value. (I'm using a 755 so testing the query locally via the SCCM console was a good method of verification.)
SELECT * FROM Win32_ComputerSystem WHERE Model = "OptiPlex 755"
For testing purposes, I changed the = to a LIKE and just left the remainder as "OptiPlex%" which returned a positive result. Additionally, changing the remainder to "OptiPlex 755%" also yielded a positive result. At this point I knew that something was different in the way this particular class was either registered within Windows 7 or something was different in the way it was read.
Using SCCM Client Center yielded a value of "OptiPlex 755". I decided to go download the old WMI Administrative Tools app from Microsoft (located - http://www.microsoft.com/downloads/details.aspx?FamilyID=6430f853-1120-48db-8cc5-f2abdc3ed314&displaylang=en) to see what it would yield. Lo and behold, the value was "OptiPlex 755 " - the spaces being 17 in total. I tested this by inserting 17 spaces into my query and the result came back positive.
My recommendation at this time, in order to save people the trouble of checking each model in their environment for the number of spaces, is to change the query to the following: (insert your computer model where OptiPlex 755 is in the query below)
SELECT * FROM Win32_ComputerSystem WHERE Model LIKE "OptiPlex 755%"
If this fails on any particular machine, I will post here, and would appreciate readers doing the same.
Cheers!
Information concerning the hardware device with details = "USB\VID_0AC5&PID_5801 ..."
Details:
ControlPoint Security Device Driver - specific system in this case was a Dell Latitude E4310 64-bit.
(This is an installation setup - no driver-only files were supplied.)
Link:
http://support.dell.com/support/downloads/format.aspx?c=us&cs=555&l=en&s=biz&deviceid=21539&libid=60&releaseid=R269916&vercnt=2&formatcnt=0&SystemID=lat_e4310&servicetag=DDJH2M1&os=W764&osl=en&catid=-1&dateid=-1&typeid=-1&formatid=-1&impid=-1&checkFormat=true
Silent installation command line: (an .iss file is supplied for silent installations)
setup.exe /s /f1"__path to the .iss file__"\setup.iss
Just a short note for those of you (like me) who are continually ensuring that you have the latest drivers working in your OSD environment - whether or not you adopt them. I have multiple task sequences devoted to model injection - primarily because drivers are being constantly updated as problems are resolved by vendors. Personally, I like to make sure that these drivers can be added to the system without causing problems elsewhere.
One issue I run into every so often occurs when I am repeatedly reimaging a specific model to test new drivers. I haven't quite nailed down the cause of the issue, but I have figured out how to get past it so I can continue working.
Issue: When imaging a specific machine multiple times and then leaving the machine information in SCCM overnight, regardless of whether you have cleared the last pXE advertisement, the machine will act as those this flag is not cleared. The machine can be deleted from SCCM, recreated, let the deletion sit overnight, etc - and the advertisement will not clear.
Reason: It seems as though the cache on the WDS server is retaining the data from the machine in question and it is actually preventing the boot and subsequent imaging process from taking place. A message will be received in SMS_PXE_SERVICE_POINT status messages stating "The SMS PXE Service Point intructed device to boot normally since it has no PXE advertisement assigned." (NOT my spelling... the message actually says "intructed")
Resolution: Restart the WDS service on the pXE server. This clears the cache and allows the box to pXE boot and image.
I'm including a screeny of the error so people will believe that I didn't fat-finger the error. Cheers!
Just a short note to align some field names. Within status message reports, you may occasionally receive messages which reflect an item referred to as a "GUID."
For the purposes of reporting:
Status messages referring to client "GUID's" are referring to the field name, "v_R_System.SMS_Unique_Identifier0."
Personally, I think they should rename the message so that it states something other than GUID, since there are variables wiithin the SCCM database which are referred to as GUID - which can be somewhat confusing to those initially diving into the views.
Cheers!
So everything is working fine and all of the sudden I receive the following error during the preliminary injection of a laptop model into my task sequence:
Task Sequence: TS: Windows XP w/SP3 - Model Injection has failed with the error code (0x80091007). For more information, please contact your system administrator or help desk operator.
So, I pick up the phone and dial myself.
As per just about every post I could find, I verified that all drivers necessary for pre-boot were injected into the boot image, that all necessary post-image drivers had been imported into SCCM and that they had properly replicated to all DP's. No red flags there. I checked my task sequence (which for this particular purpose, only images and installs good and bad drivers... post image software layering is disabled... otherwise, it's identical to my production TS.) No red flags there either.
Four days of repeated troubleshooting. I deleted the image package and re-created it - again waiting for replication to finish before changing the TS to reflect the new package name. No change.
Then, as I was explaining to someone why the OSI model is so important to troubleshooting network problems, a lightbulb appeared over my head.....
I replaced the hard drive and it works perfectly.......
The purpose of this post? Before you bang your head against a table long enough to form a permanent dent, pay your respects to the Physical Layer of the OSI model.
Nuff said....
Information concerning the hardware device with details = "PCI\VEN_8086&DEV_2A04&SUBSYS_20D117AA&REV_0C ..."
Details:
Management Engine Interface (Intel AMT 2.6) driver for Windows Vista, XP - ThinkPad T61, T61p, X61, X61s, X61 Tablet, X300, Reserve Edition
(Specificially, the driver file is - HECI.inf)
Link:
http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-67880
Information concerning the hardware device with details = "PCI\VEN_8086&DEV_2A07&SUBSYS_20D417AA&REV_0C ..."
Details:
Local Manageability Service and Serial Over LAN (Intel AMT 2.6) driver for Windows Vista, XP - ThinkPad T61, T61p, X61, X61s, X61 Tablet, X300, Reserve Edition
(Specificially, the driver file is - mesrl.inf)
Link:
http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-67881
After deploying software updates to a collection the following State ID appears on the report titled: "States 1 - Enforcement States for a deployment"
State ID - 3010006 - "Failed to install update(s)"
When reading the WUAHandler.log file of a machine contained within this report, the following entries are found:
Async searching of updates using WUAgent started.
Async searching completed.
OnSearchComplete - Failed to end search job. Error = 0xc8000438.
Scan failed with error = 0xc8000438.
When noting the time stamps on the first two lines from the above entries, the times are generally seconds apart.
I have found that this is usually an indication of a corrupt or outdated Windows Update Agent. Installing the new agent, followed by an update scan or application will usually solve the issue.
The latest Windows Update Agent can be found here: (scroll to the bottom of the pages for the manual downloads)
http://support.microsoft.com/kb/949104
During the imaging process, it becomes necessary to provide WMI queries within task sequences in order to differentiate between computer models. Typically, this is accomplished by utilizing the following query within a conditional statement inside a task sequence task item:
SELECT * FROM Win32_ComputerSystem WHERE Model = "[model name from WMI]"
Unfortunately, if you are using Levono products, this can have multiple values for the same computer familiy. (i.e. the ThinkPad X61 has several different model "numbers," none of which have the label "ThinkPad X61".) In order to provide a query which will yield the commonly used model "name" for Lenovo Thinkpads, use the following query:
SELECT * FROM Win32_ComputerSystemProduct WHERE Version = "ThinkPad [model number]"
(i.e. SELECT * FROM Win32_ComputerSystemProduct WHERE Version "ThinkPad X200")
It is also very handy to keep a spreadsheet of all the model numbers and corresponding model names for use in reporting CASE statements to make your reports easier for management to decipher.
Information concerning the hardware device with details = "PCI\VEN_8086&DEV_4237&SUBSYS_12118086&REV_00 ..."
Details:
Intel Wireless LAN (abgn, abg, bg) for Windows XP - ThinkPad
(Specificially, the driver file is - NETw5x32.INF)
Link:
http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-70504
Information concerning the hardware device with details = "ACPI\INTC0102\1"
Details:
Intel Integrated TPM (Trusted Platform Module) for Windows XP (SP2) - ThinkPad R400, R500, T400, T400s, T500, W500, W700, W700ds, X200, X200s, X200 Tablet, X301
(Specifically, the driver file is - tpm.inf)
Link:
http://www-307.ibm.com/pc/support/site.wss/MIGR-70123.html
More Posts
Next page »