Problem Running Windows/Microsoft Update After LTI Deployment

[Johnny Patton]

I am using MDT 2010 to assist us in deploying R&D images (testing,
development, etc) in our company. We are behing a proxy. We use a proxy.pac
script in IE to get to both intranet and internet sites. I can specify a
proxy server, but it will only allows us to access external sites.

I have Windows XP, Vista, and 7 images that we deploy. All were created
from the original installation media, then customized to our enviroment
(proxy.pac, local accounts, etc) and then I used a Sysprep & Capture TS to
create a custom image. I then imported that image into MDT as an Operating
System. Next I setup a TS to deploy that OS (custom image). Whenever I
deploy any of the custom images using MDT, Windows Update will not work (set
to use proxy.pac). If I change IE from using an automatic config script to
use a proxy server and specify our proxy server info Windows Update will
work. All other sites work just fine, and nothing else appears to be wrong
with the image. The application installation portion completes without
errors as well.

The weird thing is that if I apply the custom image (WIM) using BartPE or
VistaPE and imagex Windows Update works fine using the proxy.pac. Windows
update also worked fine before capturing the image using proxy.pac b/c I
updated each OS before capturing.

Why would Windows Update not work using a proxy.pac when the image is
deployed using MDT 2010? I've looked through the TS settings but didn't see
anyting that stood out as a possible culprit. I also went through the local
security policy on the deployed image, but again nothing stood out.

Any suggestions/help would be appreciated.

[Erik Chapple]

It sounds like you're applying the proxy setting in the reference PC so the
first thing that comes to mind is that the setting is not being applied
globally in deployment. In your Unattend.xml file do you have CopyProfile set
to "True" during sysprep and the deployment itself?
--
Erik Chapple
Denver, CO

Post by Johnny Patton
I am using MDT 2010 to assist us in deploying R&D images (testing,
development, etc) in our company. We are behing a proxy. We use a proxy.pac
script in IE to get to both intranet and internet sites. I can specify a
proxy server, but it will only allows us to access external sites.
I have Windows XP, Vista, and 7 images that we deploy. All were created
from the original installation media, then customized to our enviroment
(proxy.pac, local accounts, etc) and then I used a Sysprep & Capture TS to
create a custom image. I then imported that image into MDT as an Operating
System. Next I setup a TS to deploy that OS (custom image). Whenever I
deploy any of the custom images using MDT, Windows Update will not work (set
to use proxy.pac). If I change IE from using an automatic config script to
use a proxy server and specify our proxy server info Windows Update will
work. All other sites work just fine, and nothing else appears to be wrong
with the image. The application installation portion completes without
errors as well.
The weird thing is that if I apply the custom image (WIM) using BartPE or
VistaPE and imagex Windows Update works fine using the proxy.pac. Windows
update also worked fine before capturing the image using proxy.pac b/c I
updated each OS before capturing.
Why would Windows Update not work using a proxy.pac when the image is
deployed using MDT 2010? I've looked through the TS settings but didn't see
anyting that stood out as a possible culprit. I also went through the local
security policy on the deployed image, but again nothing stood out.
Any suggestions/help would be appreciated.