Forum Discussion
Errors OOBEAADV10 and 80192ee7
I am working from home today, so I plugged it in to a second ethernet connection that has always worked fine before. I know it has internet connection because Azure AD shows successful sign ins from my home ip address. I have nothing on my network that would block access to those sites.
I will try from the office tomorrow but my home setup isn't much different from an average user.
If the objective is to have non-technical users just take a computer out of the box, connect to the internet, sign in, and have their computer set up per the policies and profiles it really shouldn't be this fussy.
- Just like Harm was also pointing out... this issue could be caused by a couple of things that were also pointed out in that oobeaadv10 blog I wrote.
In an autopilot world with all strings attached, sometimes things can break... sometimes its your own network, sometimes its an issue at Microsoft their side...I plugged it in at the office this morning, signed in, and everything updated and all my apps installed as they should.
That suggests that the issue was on my home network. I wanted to try it from there before rolling it out to more users. If that is the issue, then I wonder if others would have the same thing.
When it works it is a great timesaver. For the next few users, I will have to choose people who can come in to an office if need be.
Thanks for your suggestions
- You're not running a pihole in your home network, that was my weird issue at home. One address was blocked by an ad list which was very important 😅
- The issue that you have is not wide-spread and an every day thing, once setup by the admin users should have the easy autopilot experience.
