Quantcast
Viewing all articles
Browse latest Browse all 2818

Clients connecting to wrong Deployment Share when booting from LAN

Good Morning,

I hope someone can offer some advice as im a little stumped by the situation I am currently trying to troubleshoot on a WDS server (Windows Server 2003 R2, sp2) with MDT 2010 installed we have at one of my companies branch offices.

During boot from LAN I can confirm the client is connecting to the correct WDS server IP but at the image selection screen I am getting a list of images from another WDS server located in our head office and I can confirm it is using this Deployment Share instead of the one specified localy on our branch WDS Server.

I have gone through and checked the MDT configuration and compared it to a working WDS server at one of our other branch offices and everything appears to be set correctly;

•The General tab on the MDT Deployment Share has the correct UNC and local path specified
•The Bootstrap.ini file to be displaying the correct ip and server address info plus UNC path to the local share;

[Settings]
Priority=Default, DefaultGateway
Keyboard-Locale=en-GB

[Default]
DeployRoot=\\server.domain.com\DeploymentShare$
SkipBDDWelcome=Yes

[DefaultGateway]
10.6.0.100=SiteName

[Bristol]
DeployRoot=\\server.domain.com\DeploymentShare$
SkipBDDWelcome=Yes

•Share Permissions and security settings on the local DeploymentShare are correct and match other WDS server that are functioning correctly at other branch offices
•I've even configured a WaitFiorIP.bat file under PE Customizations which includes the following which is apparently not strictly required in MDT 2010;

:LOOP1

ipconfig

ipconfig

ipconfig

ipconfig

ping server.domain.com

if errorlevel 1 GOTO LOOP1

 

If anyone can offer me some advice or other areas to check id appreciate it greatly as I can't see what's causing the issue...

Kind regards


Trevor


Viewing all articles
Browse latest Browse all 2818

Trending Articles