After installing Hyper-V Integration Services on the next reboot the VM displays BSOD 0x0000007B – P2V Hyper-V Guest BSOD 0x0000007e wdfldr.sys

After a P2V from an old server a BSOD was showing. I see same error related to WDFLDR.SYS.

Solution:

  1. Boot the VM into LastKnownGood. Press F8 during boot.
  2. Open the Registry and drill down to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Wdf01000 There is a Group Value that should have the Value WdfLoadGroup. In my cases it was wrongly set to base… Change this to WdfLoadGroup
  3. Then remove the Integration Components from Control Panel/Software.
  4. Reboot the VM (now without ICs)
  5. Install the ICs once again

Thanks to robertvi2 from https://blogs.msdn.microsoft.com/robertvi/2009/10/07/after-installing-hyper-v-integration-services-on-the-next-reboot-the-vm-displays-bsod-0x0000007b/ to help to resolve this.

Enable/Disable Network interface via command line

Start elevated Command Prompt.

Get NIC list and index number:

wmic nic get name, index

Enable NIC with index number: (eg: 7)

wmic path win32_networkadapter where index=7 call enable

Disable NIC with index number: (eg: 7)

wmic path win32_networkadapter where index=7 call disable

Thanks To EddieZA from https://answers.microsoft.com/en-us/windows/forum/windows_7-hardware/enabledisable-network-interface-via-command-line/17a21634-c5dd-4038-bc0a-d739209f5081

Add Davmail as Service Linux (Systemd)

Create file davmail-systemd on  /etc/systemd/system/davmail-systemd.service

nano /etc/systemd/system/davmail-systemd.service
[Unit]
Description=DavMail gateway service
After=syslog.target
After=network.target

[Service]
Type=simple
User=root
Group=root
ExecStart=/opt/davmail/davmail.sh /opt/davmail/davmail.properties
TimeoutSec=120

[Install]
WantedBy=multi-user.target

 

systemctl enable davmail-systemd

systemctl start davmail-systemd

We can test trafic with:

tail -f /opt/davmail/nohup.out

Thanks to https://github.com/stdevel/davmail-initscript/blob/master/davmail-systemd for systemd Script.