Create a status message filter to delete the MACs of the USB adapters from the inventory?
On Tue, Feb 25, 2014 at 4:20 PM, Jason Wallace <[email protected]> wrote: > I have fixed this by: > > Create a collection for newly added devices based on creation date > Create a program to force a discovery cycle and advertised it to always > re-run on a schedule which is more frequent than the build time > Create client settings against this collection to force a hardware > inventory on the same basis > Assigned build engineers 2 sets of USB dongles labelled A and B and told > them to alternate during builds. > > On 25 Feb 2014, at 20:30, "Fusco, Brendan" <[email protected]> wrote: > > Our current foolproof workaround for this issue is to have our > procurement department require a unique USB NIC to be ordered with any such > device (presently, we only support two devices without wired NICs - the MS > Surface and the Dell Venue 11 Pro) and then delivered to the end user > whether they need it or not. > > > > I would be interested in a more "creative" solution as well...thought about > running discovery/hardware inventory after the machine has been deployed to > disassociate the USB NIC's MAC address from the device, but that seems > clunky. > > > > Brendan A. Fusco > > Sr. Systems Engineer > > DePaul University, Information Services > > > > *From:* [email protected] [ > mailto:[email protected] <[email protected]>] *On > Behalf Of *Krueger, Jeff > *Sent:* Tuesday, 25 February, 2014 2:21 PM > *To:* [email protected] > *Subject:* [mssms] need a practical solution for imaging devices with USB > Ethernet adapters > > > > Has anyone come up with a practical solution for imaging devices that > don't have built in Ethernet adapters? The problem with using USB>Ethernet > adapters is that the mac address of that adapter will be tied to the device > that was just imaged. When trying to image another one using that same > adapter it will mark the other computer's record as obsolete and try to > name new device the same as the old record (mileage may vary depending on > how you handle device naming to begin with). > > > > Possible scenarios include: Importing a new computer record based on > UUID, this would not be realistic in a large environment with many devices > to be staged. Have a set known of USB adapters and use a script to remove > the mac address of those adapters from the database with some kind of > scheduled task, this is a bit dirty in my mind and could get sideways if > adapters get lost/replaced. > > > > Any other ideas? With the influx of new thin laptops and tablet devices I > know that other people have to running into this. Since Microsoft has > their own device without an Ethernet port that they would have been a > little more preciencent with this potential problem when developing SCCM > 2012. > > > > Jeff Krueger > > IT - Endpoint Design Services > > Henry Ford Health System > > [email protected] > > 248.853.4466 > > > > > ------------------------------ > > > CONFIDENTIALITY NOTICE: This email contains information from the sender > that may be CONFIDENTIAL, LEGALLY PRIVILEGED, PROPRIETARY or otherwise > protected from disclosure. This email is intended for use only by the > person or entity to whom it is addressed. If you are not the intended > recipient, any use, disclosure, copying, distribution, printing, or any > action taken in reliance on the contents of this email, is strictly > prohibited. If you received this email in error, please contact the sending > party by reply email, delete the email from your computer system and shred > any paper copies. > > Note to Patients: There are a number of risks you should consider before > using e-mail to communicate with us. See our Privacy & Security page on > www.henryford.com for more detailed information as well as information > concerning MyChart, our new patient portal. If you do not believe that our > policy gives you the privacy and security protection you need, do not send > e-mail or Internet communications to us. > > > > >
