Ben Hunter

That is correct. The article assumes that the deployment share is on the server as the WDS server. It is done this way because you cannot discover the DFS root. DFS-R is simply used for replication purposes.

Thanks,

Ben

You need to use DFS-R to replicate the deployment point to a share at each site. When you boot to the server using WDS BDD will automatically populate the WDSSERVER value.

Then you will set the deployment point in the BS.ini file.

DeployRoot=\\%WDSSERVER%\sharename

Here is a post by Johan Ardwidmark, although I beleive that bdd 2007 patch 1 removed the need to create a GetWDSServerName function.

http://www.deployvista.com/Blog/tabid/70/EntryID/35/Default.aspx

Thanks,

Ben

Hi Greg,

You could assign the deployroot value based on the deployment type.

For example:

[Settings]

Priority=DeploymentType,Default

[NewComputer]

Deployroot=\\%WDSSERVER%\share$

You do not need to specify a value for refresh as will have already established a connection to the server to start the script.

Thanks,

Ben

Hi Or,

YOu are correct about the DFS share thing. That is why DFS should only be used as a replication tool. You must create shares on each server yourself.

Thanks,

Ben

Yes it is set in Windows PE 2005.

This is done by the ztigather script.

Thanks,

Ben

This should not be the case. Does the Ztigather.log file should a value for WDSServer?

Thanks,

Ben

OSDPackagePath should be populated by OSD and should be the nearest DP.

Thanks,

Ben

Hi Steve,

MDT offers a bunch of incremental improvements over BDD 2007. It also provides support for ConfigMgr and Server deployment.

If you are choosing between BDD 2007 and MDT then I would strongly recommend using MDT.

Thanks,

Ben