Update to registry HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WcmSvc\wifinetworkmanager\config
Or via Login Script or during the task sequences in Configuration Manager or MDT (post image install)
reg add HKLM\SOFTWARE\Microsoft\WcmSvc\wifinetworkmanager\config /t REG_DWORD /v AutoConnectAllowedOEM /d 0
Modify Unattend.xml to add Microsoft-Windows-WiFiNetworkManager
Set WiFiSenseAllowed to 0
For Windows 10 build 1511 or later
Configure the Group Policy Object Allow Windows to automatically connect to suggested open hotspots, to networks shared by contacts, and to hotspots offering paid services under
Computer Configuration\Administrative Templates\Network\WLAN Service\WLAN Settings\.
Microsoft has just released an update to MDT 2013 today as Update 2. Update 1 provided Windows 10 support (Windows 10 supported ADK is needed still). Update 2 as stated in the blog does not add major new features but adds some improvements to existing features and functionality.
jparekh at netrixllc dot com
After couple of years of debates to do this or not, we have decided to move forward with this group. There is no similar group like this in Chicagoland area. We have done topics with the Chicago Windows User Group in the past and will continue to support them in joint events. However, the membership for a Windows user group vs. a System Center, EMS, datacenter and client management, is much different.
If you are in the Chicago area, please sign up.
The group is co-founded by Rich Lilly. Check out his blog here and follow him on Twitter
If you get a prompt to Set Network Location (See Figure 1) in Windows 7 on a domain-joined computer, there is a hotfix from MS to resolve this issue.
Package the hotfix and deploy as a Task in the OSD or MDT Task Sequence as part of the Windows 7 deployment.
Extracting the Files without Installing
This self-extracting archive supports the following command line parameters:
Do not automatically start the installation process.
Extract the files silently.
Destination path where the archived files will be extracted to.
I came across this issues where the Litetouch MDT scripts would not run on certain IBM or Lenovo computers (wscript.exe process exists right away, no MININT folder, no logs, etc.). After researching, found that the IBM/Lenevo tool called Rescue and Recovery was blocking the scripts from running and creating the MININT folder in C: root. Removal of his tool from the system, allowed the MDT to launch and work successfully.