Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Could not add DVD drive to machine DC1

Open
#14 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
20/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
powershell

Research direction

Start by reproducing the deployment on the reported Windows Server 2012 R2 Hyper-V host and review the attached s4bDeployment.txt. Then inspect Send-ALToastNotification.ps1 and AutomatedLabWorkerVirtualMachines.psm1 at the reported locations, focusing on the three logged failures. Done means identifying the cause of the deployment errors and confirming that DC1 receives its DVD drive successfully.

Written by the indexing model from the issue text.

Description

I'm getting three errors during the deployment. Maybe one error has to do with the other.

This is the first error I get.

12:15:48|00:00:07|00:00:00.000| Lab 's4bhomeLab' hosted on 'HyperV' imported with 10 machines
Get-ItemPropertyValue : Property ServerNano does not exist at path HKEY_LOCAL_MACHINE\software\Microsoft\Windows NT\CurrentVersion\Server\ServerLevels.
At C:\Program Files\WindowsPowerShell\Modules\AutomatedLabNotifications\Private\Send-ALToastNotification.ps1:16 char:25

  • ... oreOrNano = Get-ItemPropertyValue 'HKLM:\software\Microsoft\Windows N ...
  •             ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    
    • CategoryInfo : InvalidArgument: (:) [Get-ItemPropertyValue], PSArgumentException
    • FullyQualifiedErrorId : Argument,Microsoft.PowerShell.Commands.GetItemPropertyValueCommand

This is the second error: I get this error 10 times, one for each host.

12:15:54|00:00:06|00:00:01.659| - The hosts file has been added 10 records. Clean them up using 'Remove-Lab' or manually if needed
12:15:54|00:00:06|00:00:00.000| - Creating HyperV machine 's4bfe01'..Set-VMFirmware : A parameter cannot be found that matches parameter name 'SecureBootTemplate'.
At C:\Program Files\WindowsPowerShell\Modules\AutomatedLabWorker\AutomatedLabWorkerVirtualMachines.psm1:296 char:52

  • ... vm | Set-VMFirmware -EnableSecureBoot Off -SecureBootTemplate Microso ...

This is the third error: It just sits there retrying to mount the iso file for the domain controler

12:24:50|00:09:02|00:00:00.000| Installing Certificate Servers
12:24:50|00:09:02|00:00:00.000| - Machines with Root CA role to be installed: 'DC1'
12:24:50|00:09:02|00:00:00.000| - Waiting for machines to start upCould not add DVD drive 'D:\LabSources\ISOs\en_windows_server_2012_r2_x64_dvd_2707946.iso' to machine 'DC1'. Retry
ing.
12:25:03|00:09:14|00:00:12.543| - Could not add DVD drive 'D:\LabSources\ISOs\en_windows_server_2012_r2_x64_dvd_2707946.iso' to machine 'DC1'. Retrying.
12:25:08|00:09:19|00:00:17.546| - Could not add DVD drive 'D:\LabSources\ISOs\en_windows_server_2012_r2_x64_dvd_2707946.iso' to machine 'DC1'. Retrying.
12:25:13|00:09:24|00:00:22.556| - Could not add DVD drive 'D:\LabSources\ISOs\en_windows_server_2012_r2_x64_dvd_2707946.iso' to machine 'DC1'. Retrying.
12:25:18|00:09:29|00:00:27.564| - Could not add DVD drive 'D:\LabSources\ISOs\en_windows_server_2012_r2_x64_dvd_2707946.iso' to machine 'DC1'. Retrying.
12:25:23|00:09:35|00:00:32.579| - Could not add DVD drive 'D:\LabSources\ISOs\en_windows_server_2012_r2_x64_dvd_2707946.iso' to machine 'DC1'. Retrying.

My host machine is windows 2012r2 with hyper-v
This is the output of the deployment process
s4bDeployment.txt

I have the feeling that I'm missing something very small, but I can't really figure it out yet after days now. I hope somebody knows what is going on.
Thank you in advance.

Dominant language
PowerShell
Stars
14
Forks
4
PR merge metrics
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from AutomatedLab/SfBAutomatedLab

All issues in AutomatedLab/SfBAutomatedLab

Similar issues

More DevOps issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.