nathanbowes

For reference if anyone else gets a similar issue this was resolved by a reply to a post made on the Microsoft MDT forums (Internet Explorer NTLM to Squid Proxy Fails after MDT 2012 Deployment) by Stephan Schwarz. It was a simple case of adding ApplyGPOPack=NO in the customsettings.ini with MDT. Everything now works as it should :-)

The county council use Netsweeper which I believe uses squid proxy. It does appear to be ntlm negotiation between the proxy and IE but I'm at a loss as to why there is an issue when we are deploying using the same Windows 7 wim file through MDT that works fine when we install a workstation from the DVD. It suggests that the MDT deployment process is somehow affecting ntlm.

Thank you but we always create our own images from scratch anyway to help avoid the bloatware installed on newely purchased machines.

We have deployed with numerous scenarios, one being to workgroup rather than domain to rule out rogue GPO settings. There are no settings on the client as we are deploying the wim file from a Windows 7 DVD iso to the clients. An intial part of the MDT deployment is to partition and format the client before it then copies the wim, expands the files and installs Windows 7.

We have started to deploy Windows 7 using Microsoft Deployment Toolkit (MDT) and Deployment Services (we have always used Ghost in the past). Unfortunately we have found (after deploying 60 machines!) that the Internet does not work on a MDT deployed workstation on Internet Explorer 8 or 9 (DVD installed and Ghosted workstations work fine?!). We are however able to connect to the Internet using Firefox and Chrome, download Windows updates and device drives from the Internet, ping the county councils proxy and connect to the Netsweeper admin console from the affected machines using IE. Internet proxy settings are set by Group Policy and work fine for XP and Windows 7 workstations that we have installed from DVD or imaged using Ghost. We have tried deploying a workstation to a workgroup rather the domain (thus no GPOs applied) and after manually entering the proxy information IE still doesn’t work (but Firefox etc. do..) Microsoft are now involved and although we still have no resolution we have discovered using Microsoft Network Monitor 3.4 that it appears to be an issue related to NTLM authentication as when the proxy asks the second time for NTLM authentication the workstation fails to send another request and simply displays the ‘Internet Explorer cannot display the webpage’ page. It appears that IE only sends the domain and workstation name to the proxy and then fails to respond when requested for the username. On a working workstation IE will send an additional request with domain, workstation name and username and from there the proxy will authenticate and send the page requested. The question is, has anyone else experienced this issue, either related to MDT or separately? If the answer is yes have you managed to resolve it and what was the resolution? Any help with this is much appreciated as our Windows 7 deployment is now very much at risk. Many thanks Nath

Hi Will, I have recently taken receipt of 10 of these Samsung 930XT's. I had hoped they would work in the way you mention and am currently struggling to get them working. Did you ever find an answer to your question? We have 30 HP T5530's which work perfectly and have a simple way to clone them. I would be interested to know how you scripted the reconnection and how you got rid of that pesky pre-authentication screen. Nath