While attempting to migrate a Citrix PVS base image to a new hypervisor, I uninstalled the PVS bits from the VDA and quickly found that DHCP had been broken. I have slamming my head against the wall a bit, I remembered something I had done years ago to this image to avoid an issue where PVS was failing in an older split-scope environment we had - set the PVS service "BNDevice" as a dependency of the DHCP service so that it would request the correct IP address during the hand-off to the OS (Thanks to Syxin https://www.syxin.com/tag/bndevice/).
This obviously was preventing DHCP from starting since the BNDevice service no longer existed after removing PVS tools. Simply needed to reverse that change:
HKLM\System\CurrentControlSet\Services\dhcp\DependsOnService
Remove BNDevice from the list of dependencies.
December 01, 2017
Subscribe to:
Posts (Atom)
Red Flags and the Value of Experience
One of the things I hear often said, and something I subscribe to as well, is the idea that a lot of technical knowledge in the world of IT ...
-
UPDATE: Turns out this is a known issue during the 1.5 > 5.1 VSM upgrade and a fix should be released in an upcoming patch. That's ... -
After completing an Exchange 2007 > 2013 migration recently, I was left with one issue that was preventing us from stamping the project...
-
While testing an SMTP connection to AOL's mail servers, I got this awesome syntax error response when I forgot to put a space between &q...