One of my fellow Microsoft Services consultants from the UK Adam Shepherd, has just had an article published in TechNet Magazine.
The article provides advice on how to scale BDD. This includes how to to support multiple databases, use DFS-R and how to leverage WDS.
The advice is based on learning's from real world so you should find it practical. If nothing else it should help you further understand just how flexible BDD really is.
So go out there and read this article and remember to keep an eye out for future articles from Adam, they will be good!
PS. It is worth having a good look around TechNet Magazine as there are a number of good deployment articles in previous issues.
I've read it and it's a good Practice, however, as WinPE can't discover DFS Root, it uses the %WDSServer% Var instead, as mentiond in the article, but what happens when you're using REFRESH (No WDS) ?
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.
So how can we use the %WDSServer% variable and support new OS installs and Refreshs?
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.
Here is a post by Johan Ardwidmark, although I beleive that bdd 2007 patch 1 removed the need to create a GetWDSServerName function.
We are currently using DFS-R to replicate the deployment point to a share at each site, however we need to kick off the upgrade/refresh remotely and we are using LTI. Which means it will have to happen in Windows as we do not have the remote access cards. If we kick off the Deployment wizard in Windows the %WDSSERVER% is not populated because there is no PXE/WDS. If there another way to populate this variable?
You could assign the deployroot value based on the deployment type.
You do not need to specify a value for refresh as will have already established a connection to the server to start the script.
Yes, but Refresh's WinPE will not understand it as it will be a DFS share during Pre\Post install phases
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.
Is %WDSSERVER% set in OSD's Winpe2005, and if so, where ?
Yes it is set in Windows PE 2005.
This is done by the ztigather script.
Looking at the ztigather.log revieles that the Deployroot is set to \\%WDSSErver%\Share$ instead of \\ServerName\Share$
Is this normal ?
The problem is that the OSDPACKAGEPATH is set to the main BDD site and not the Remote
This should not be the case. Does the Ztigather.log file should a value for WDSServer?
OSDPackagePath should be populated by OSD and should be the nearest DP.
whats the difference between BDD 2007 and 'Microsoft Deployment' ?