Too often you see questions on roaming and site boundaries. The labels for these are not indicative to the function. Sometime back, Microsoft provided a nice white paper on the subject on Advanced Client Roaming which, on page 7, gives a very nice definition of the functions of each type of boundary. A good read for those still scratching their heads on the subject.
In making a single-platform image, without the assistance of the cool things in SCCM, (which, by the way, I can't wait to upgrade to) I've come across many driver quirks. But... I've never encountered two drivers, for the same series of NIC's, with the same name, not containing information necessary for the earlier NIC to function.
Enter the E1E5132 driver for the Intel(R) Pro/1000 Gigabit Adapters.
Case:
-
Lenovo 61 series laptops (T-61 and X-61) - Device ID PCI\VEN_8086&DEV_1049&SUBSYS_20B917AA
-
Dell Optiplex 755 desktops - Device ID PCI\VEN_8086&DEV_10BD&SUBSYS_02111028
-
Drivers provided by each vendor named E1E5132."ext"
-
Lenovo driver does not function in the Dell and vice-versa
Resolution:
-
I renamed the Dell driver files to E1E5132b."ext"
-
Then, I replaced every reference in the .INF file to E1E5132b."ext"
Well.... it was really a stab in the dark, but it worked. Give it a try... if you have a better solution, please comment.
There have been numerous occasions where I've read of administrators in a panic over an advertisement which needs to be stopped from running on some or all SMS clients. Being in the position where I am introducing the technology of SMS to the Desktop Support team of my new employer, I have been waiting for this to happen.
Well, it did - so I figured I'd write up this simple process so that others who may be in this position can log this and have something to fall back on. Keep in mind that I am an avid user of SMS Client Center (see http://myitforum.com/cs2/blogs/mlucero/archive/2007/05/21/sms-2003-tools-sms-client-spy.aspx ), so my procedures in most cases will involve you viewing items from within this fantastic tool My process for killing an advertisement is pretty straight-forward:
-
Within the SMS console, go to the properties of the collection housing the clients with the offending advertisement and verify the advertisement name. (Select Collection, right-click, select Properties, click on the Advertisements tab)
-
Find the offending advertisement within the Advertisements list and disable it. (Select the advertisement, right-click, select All Tasks, select Disable Program)
-
Ensure that the change to this advertisement has made it to your site servers.
-
-
Remove from this same collection all membership rules. ( I do this as an added precaution. )
-
Update the collection membership and ensure that there are no remaining members.
I typically will perform a spot check using SMS Client Center on a few clients. Within execmgr.log of the affected clients, you should see the following for your advertisement: (this particular advertisement was for Office 2007)
Policy deleted for advertisement CEN200C4 package CEN000B4 program Microsoft Office Profession Edition 2007 - Install execmgr 6/4/2008 7:31:53 AM 2088 (0x0828)
Policy was deleted or expired for program Microsoft Office Profession Edition 2007 - Install. Remove the execution request. execmgr 6/4/2008 7:31:53 AM 2088 (0x0828)
You can further check within SMS Client Center in the Advertisements section, noting that the advertisement will be eliminated from the list.
I have never had this process fail me, but if others have alternate methods, please feel free to post comments.