[Issue]: Using a custom UNC-Path for P2V image capture is no longer working after HF 173 to remove DHCP information

[iwsbarker]

Describe the bug

HF 173 to remove DHCP information clears the NameServer information for all DHCP network adapters. This prevents access to UNC network paths since the server name cannot be looked up.

Steps to reproduce

Set LIC_BISF_CLI_P2V_PT=1 and LIC_BISF_CLI_P2V_PT_CUS to a network share

Expected behavior

vhdx file should be saved to the network share

Screenshots

No response

Desktop, please complete the following information.

No response

Smartphone, please complete the following information.

No response

Additional context

[captain-threepwood]

Removing these registry entries for DHCP adapters will instantly break DNS resolution. Seen for Server 2019 and 2022. I had the same problem in the past. I just commented these lines in the following file and my problems were solved:
Framework/SubCall/Preparation/97_PrepBISF_PRE_BaseImage.ps1

Lines 573-583
Lines 587-608
Lines 642-651

May not be the final solution but a workaround for me.

[iwsbarker]

I prefer not to modify the BIS-F code directly - we've done that in the past, and it makes for a mess when trying to update to the latest from git. Instead, I created a new script (named to run directly after 97_PrepBISF_PRE_BaseImage.ps1), and in that script it just renews DHCP:

Write-BISFlog -Msg "Renew DHCP config" -showConsole -Color Cyan
Start-BISFProcWithProgBar -ProcPath "$env:SystemRoot\system32\ipconfig.exe" -Args "/renew" -ActText "Renew DHCP config" | Out-Null