we have a contract customer that cant communicate with the domain over the office wireless, over the ethernet theyre fine, one win 10, one win 7. we are suspecting that the microsft monkery caused it, we pushed all the wsus updates from last tuesday out on thursday and are hoping it resolves it. may be unrelated, but given theyre jacking around in that stack and it started at the same time im not generating alot of billable time for a customer for microsofts f up
On Tue, Dec 27, 2016 at 1:46 PM, Ken Hohhof <[email protected]> wrote: > Is anyone still running into customers with Windows 10 computers that boot > up with an autoconfiguration address but will get a valid address if you > Restart them? I got yet another call today about this. Of course, > customers think it’s our problem because the symptom is “no Internet” on > the affected computer. > > > > I would have thought all computers would have the patch by now. But I > guess if the symptom is “no Internet”, the computer might not get the > update. > > > > Annoying that this has not been better publicized. Somewhere customers > actually read, not this: > > > > http://arstechnica.com/business/2016/12/microsoft- > windows-10-dhcp-broken-update/ > > > -- If you only see yourself as part of the team but you don't see your team as part of yourself you have already failed as part of the team.
