{"id":4361,"date":"2016-03-08T13:19:53","date_gmt":"2016-03-08T21:19:53","guid":{"rendered":"http:\/\/www.atumvirt.com\/?p=4361"},"modified":"2016-03-08T13:19:53","modified_gmt":"2016-03-08T21:19:53","slug":"provisioning-services-bdm-creation-limitations","status":"publish","type":"post","link":"https:\/\/avtempwp.azurewebsites.net\/2016\/03\/provisioning-services-bdm-creation-limitations\/","title":{"rendered":"Provisioning Services BDM Creation Limitations"},"content":{"rendered":"
There are definitely pros and cons to using the various PVS boot options.\u00a0 If you aren\u2019t familiar or need a refresher, here they are:<\/p>\n
For the purposes of this post, I will be talking about BDM.\u00a0 I\u2019m going to differentiate option #2 with option #3 by referring to #2 as \u201cBDM-TSB\u201d and #3 as \u201cBDM monolithic\u201d.<\/p>\n
The PVS Boot Process diagram<\/a> outlines the process I great detail, and I highly suggest you read it.\u00a0 All options are limited to 4 potential \u201cLogin servers\u201d.\u00a0 When using DNS, DNS based subnet affinity\u00a0 Here are some pro\u2019s and cons of each option<\/p>\n In selecting the BDM-Monolithic option, I was hoping to be able to design a highly fault tolerant environment that does not rely on the network stack (TFTP load balancing) or rely on the two stage boot service on each PVS server.\u00a0 However at scale, we ran into some issues.\u00a0 The design calls for 2 servers per subnet, in a single farm.\u00a0 Since it is currently not possible<\/a> to use DNS currently for the monolithic BDM and if there is a desire to not<\/em><\/strong> rely on DNS anyway\u00a0(say, if another group in the organization owns it), my next thought was to configure bootstrap differently per-server then connect the PVS console to each server, hoping it would use it\u2019s own BOOTSTRAP settings.\u00a0 Unfortunately, this seems to not be the case and it seems to select from the \u201ctop\u201d PVS server in the farm (in my case, this was the second one added to the farm), as shown below.<\/p>\n <\/a>\u00a0<\/a><\/p>\n <\/p>\n Based on this, I started digging.\u00a0 What else could we do to make this a bit easier, without having to reconfigure BOOTSTRAP for the whole farm every time we spin up a subnet?\u00a0 I turned to DotPeek and saw something interesting.<\/p>\n <\/a><\/p>\n If Login servers count = 0, we should hit that \u201celse\u201d statement and use DNS \u2013 which, we can\u2019t modify the hostname, but I\u2019ve confirmed is \u201cImageServer1\u201d (the default) if you look in the BDM that gets \u201cburned\u201d.<\/p>\n <\/a><\/p>\n However, once configured, you\u2019ll be hard pressed to remove servers!<\/p>\nTFTP (w\/ PXE or DHCP)<\/h2>\n
\n
BDM-TSB<\/h2>\n
\n
BDM-Monolithic<\/h2>\n
\n