So where I work we have a large number of laptops coming in without network ports, and we don't want the external dongles adding to the cost, so in addition to standalone USBs, I've been setting up, configuring, and testing various multicast deployments over wifi (using SCCM).
Most of the APs and core switch are fairly new, the Wlan controllers are not as new. Sorry I'm not the network guy so I actually don't know hardware specs for these things. I've been working with a guy though, but I don't want to waste his time quizzing him on everything so I keep it to "how do we get this to work etc".
I have a motley crew of various laptop models that are in bad enough shape to not be in the wild, but good enough shape to get the tests done. Two HP models and one Dell that's quite a bit newer.
So at first I couldn't get it to work at all. Then the guy removed some rendezvous point and setup a video stream where he had to put a specific IP range to look for, and I configured that part in SCCM.
Then it worked, but for some reason, when I did deployments at more than one location (but still same WLC) of the same task sequence, many of the computers started failing with a hash not correct error. When I separated it into task sequences calling their own image files per building, the failures went away, except for one random one in a building where I split the computers between 3 APs.
The guy then makes it so all the WLCs use the same IP range, and so I decide to test deploying at two buildings, each on a different WLC. I use the same task and image file because I didn't have time to get multiple copies distributed before this test. As I sort of expected, I got failures again of the same type.
But here's the weird thing, only one model had failures, an aging (but not oldest) HP probook. It's wifi adapter is an intel dual-band wireless n 7260, model 7260HMW AN.
I can think of a few possibilities, but was hoping someone else might have some insight into the likely reason this particular adapter has difficulty, but apparently only when deploying the same package to multiple locations at once.
No comments:
Post a Comment