[mdt] MDT Built machines, network shares and litetouch do not play ball! :(

[churchy112]

Greetings,

 

I've almost got MDT perfect! At all of my schools I've standardised MDT and at all schools I have this problem so it must be something I'm doing.

 

On an OEM or CD built machine I am able to access our NASBOX on a 172.x.x.x address from a 10.x.x.x school and I am also able to RUN the litetouch.vbs wizard.

 

On an MDT built machine I cannot access the 172.x.x.x nasbox (The specific network is no longer available). I am able to access the Deploymentshare$ with full rights but I cannot RUN the litetouch.vbs. It gives me a connection permission error (Sorry for the vague error message)

 

This happens whether I build the machine from a bog standard Windows 7 wim or from a captured WIM. Also happens with a wired or wireless connection.

 

 

I'm using MDT 2012 / WAIK

Servers will vary but mainly 2008R2

 

Any suggestions would be appreciated

 

Thanks

Scott

[churchy112]

Bump: Any suggestions at all would be fantastic!

[computer_expert]

Could issues with the NAS be something to do with this? http://www.edugeek.net/forums/o-s-deployment/103042-warning-mdt-2012-issues-ntlm-if-you-allow-apply-local-gpo-package.html

[Jamo]

Could issues with the NAS be something to do with this? http://www.edugeek.net/forums/o-s-deployment/103042-warning-mdt-2012-issues-ntlm-if-you-allow-apply-local-gpo-package.html

 

That will only apply after the machine has been imaged as the Local GPO script is run during the deployment.

 

It could be DNS resolution issues, make sure your deployment share is correctly referenced in the properties windows (right click/Properties on the share name)

 

Try FQDN and the IP if that doesn't work

 

 

 

 

 

 

Edit - ignore My post above I misread your post! As someone has already mentioned its highly likely to be the local GPO option.

Edited December 13, 2014 by Jamo

[snagrat]

Try setting the following in GPO and see if it works after a reboot

 

Local Policies -> Security Options -> Microsoft network client: Digitally sign communication (always) = Disabled

[churchy112]

Try setting the following in GPO and see if it works after a reboot

 

Local Policies -> Security Options -> Microsoft network client: Digitally sign communication (always) = Disabled

 

No luck with that one thanks though

 

If it's the Local GPO package, I'll have to find some time and do a test build without that step and try to figure out what's causing it! Does anyone else have this problem with their builds?