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 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.



Reply via email to