We have the ThinkPad Yoga and just wait for HINV to update the record. We are not rolling many of these though, so it's a workable solution for us.
We deploy to unknown machines, so if we need to build them more rapidly, we just delete the record from the console. Daniel Ratliff From: [email protected] [mailto:[email protected]] On Behalf Of Timothy Ransom Sent: Tuesday, February 25, 2014 4:12 PM To: [email protected] Subject: [mssms] RE: need a practical solution for imaging devices with USB Ethernet adapters We are using Latitude 10, Venue11 and XPS12 but nothing creative here - we just order a usb nic for each tablet at purchase and then the usb nic stays with the device it imaged. From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Fusco, Brendan Sent: Tuesday, February 25, 2014 3:28 PM To: [email protected]<mailto:[email protected]> Subject: [mssms] RE: need a practical solution for imaging devices with USB Ethernet adapters 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]> [mailto:[email protected]] On Behalf Of Krueger, Jeff Sent: Tuesday, 25 February, 2014 2:21 PM To: [email protected]<mailto:[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]<mailto:[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<http://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. ********************************************************************************************** GDOL CONFIDENTIALITY NOTICE: This transmission may contain confidential information protected by state or federal law. The information is intended only for use consistent with the state business discussed in this transmission. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or the taking of any action based on the contents is strictly prohibited. If you have received this transmission in error, please delete this email and notify the sender immediately. Your cooperation is appreciated. ********************************************************************************************** The information transmitted is intended only for the person or entity to which it is addressed and may contain CONFIDENTIAL material. If you receive this material/information in error, please contact the sender and delete or destroy the material/information.
