The perfect choice of one-stop service for diversification of architecture.
You can also add .
net 4.
5 support to the wims and try using the wirelessconnect program mentioned on this page: to scroll down a bit to see where he employs it. I myself got wireless going, but it was with a static network. Hope you take this up again.
So, we have a Win10 task sequence that I'm trying to update to 1803. However, the task sequence was designed specifically for offline use (including Offline Domain Join). The thing is, prior to 1703, it worked fine. However, after 1703, it stopped asking for a WiFi connection. So when it's plugged into ethernet, it works fine, but if not, then it fails to download the ODJ file, so it can't complete the ODJ, so the Enable BitLocker step fails because it can't communicate with AD to upload the recovery key.
To try to force it to prompt for a WiFi connection I'm applying an unattend.xml during the task sequence. I know that the HideWirelessSetupInOOBE is supposed to have been deprecated several versions back, but other people have said it worked for them. It hasn't for me though. But, just in case, here's the contents of my unattend.xml:
I'm at kind of a loss here, because without this functionality, this TS is severely ham-stringed. We have a large consultant fleet who are rarely in the office, and periodically need to re-image their laptops at a client site, or a hotel, or their house, or whatever. So manually adding a WiFi connection via the task sequence is also out of the question.
Does anyone have any ideas on what I can try?
·OTHER ANSWER:
So, we have a Win10 task sequence that I'm trying to update to 1803. However, the task sequence was designed specifically for offline use (including Offline Domain Join). The thing is, prior to 1703, it worked fine. However, after 1703, it stopped asking for a WiFi connection. So when it's plugged into ethernet, it works fine, but if not, then it fails to download the ODJ file, so it can't complete the ODJ, so the Enable BitLocker step fails because it can't communicate with AD to upload the recovery key.
To try to force it to prompt for a WiFi connection I'm applying an unattend.xml during the task sequence. I know that the HideWirelessSetupInOOBE is supposed to have been deprecated several versions back, but other people have said it worked for them. It hasn't for me though. But, just in case, here's the contents of my unattend.xml:
I'm at kind of a loss here, because without this functionality, this TS is severely ham-stringed. We have a large consultant fleet who are rarely in the office, and periodically need to re-image their laptops at a client site, or a hotel, or their house, or whatever. So manually adding a WiFi connection via the task sequence is also out of the question.
Does anyone have any ideas on what I can try?