- This topic has 4 replies, 3 voices, and was last updated 14 years, 7 months ago by
nobrainer.
-
AuthorPosts
-
September 8, 2010 at 6:25 pm #379427nobrainerParticipant
I got a weird problem… and I mean WEIRD…
a while ago when we were doing the monolithic image (maybe… May 2010ish) I built an image off a user’s machine that had a bluetooth keyboard and mouse setup. I had forgotten to remove it from the bluetooth device list (so under devices it shows username’s keyboard and username’s mouse) on every machine that was done with that image. Fast forward to the August build I did w/ instadmg… done off a completely different system, using instaup2date, etc and the OEM dvd’s… we just deployed to a brand new out of the box 17″ MBP i7 … and I got a note from the deployment team that the bluetooth devices is populated with that same user’s keyboard and mouse..
Sure enough, I just checked my system, which I deployed this same image on a week or so ago, that same devices are populated.
That user sits in a physically different building – so it’s not like I can pick up the Bluetooth signal from it…
Any idea’s how or why it would pick up the information from a system 3+ months ago?
September 8, 2010 at 7:19 pm #379428Allister BanksParticipantHey nobrainer,
Nope! no clue. Okay, maybe a clue. Step one could be to run fseventer(or opensnoop) while removing the device, and find out where that configuration is stored. Step two is to verify no custom package could possibly have that file… grasping at straws here. I was wondering earlier how a machine could be reimaged, but the keyboard is still paired and refuses to pair with anything else until the bond to that one piece of hardware is broken. I guess Bluetooth is like the iPad: magical!
Allister
September 10, 2010 at 1:59 am #379448larkostParticipantThis is purely a guess, but I am pulling on a little bit of information that came up in a question on the MacEnterprise mailing list: it seems that the Bluetooth pairings are both in preference settings, and also stored on some bit of hardware in the system (the sucessor to PRAM maybe). This came up because Apple has started shipping some units pre-paired with the bluetooth mouse and keyboard that comes with them, and imaging the computer does not get rid of this.
So my guess about what has happened:
1) Your old image had the settings in it as a plist.
2) When the computes booted they took this preference and put it down in flash memory, duplicating the information in the plist.
3) The new image got applied to the computers, but the information was still in the flash memory, so got picked back up (maybe into the plist again).
My guess is that imaging systems (meaning things like DeployStudio) are going to have to start addressing this issue. But like I said, this is mostly guesswork. Can anyone out there take a whack at confirming this? I don’t think I have any time in the lab this week to do so.
September 10, 2010 at 12:10 pm #379449nobrainerParticipantstrangely enough, I built just the base image and it wasn’t there.
However, when layered the rest of the apps on the machine for deployment to a user, the keyboard / mouse showed back up. So it DOES sound like a preference file somewhere has it in there..
however, now I have to figure out which of the other 15 or so apps is causing it.September 10, 2010 at 8:03 pm #379455nobrainerParticipantThe culprit appears to be /Library/Preferences/com.apple.Bluetooth.plist
Since I already ruled out the base image as the culprit, I did manage to find out it’s my AV of all things.
Thank you for the help!
-
AuthorPosts
- You must be logged in to reply to this topic.
Comments are closed