What does attaching an ISO through dedicated-server virtual media actually do?
Virtual media presents an image or remote media device to the server as if suitable media were attached locally. Attaching an ISO is not the same as installing its operating system, but booting into an installer can lead to destructive disk changes. Verify image origin, intended boot mode and the exact target machine first.
Before you start
- Authorised access to the dedicated server and the named inspection tools.
Instructions
1. Verify the image and access method
Use the manufacturer/provider’s supported media interface and an image obtained through the operating-system publisher’s trusted process. Check its full digest against an independently trusted published value before attachment.
Get-FileHash -Algorithm SHA256 -LiteralPath "C:\Downloads\server-installer.iso"This local PowerShell command hashes the selected ISO. The digest confirms matching bytes only when compared with a trusted expected value.
2. Attach and boot only within the plan
Confirm controller feature entitlement and network access to the image. Prefer the reviewed one-time boot selection for recovery, observe the console and do not start installation or partitioning without the approved storage plan.
Check the result
- The intended image is visible to the correct server, the authorised task completes, virtual media is detached and normal boot behaviour is restored.
Troubleshooting
- The image disconnects during use
- Check the management network and source availability; remote media may depend on a workstation or URL remaining reachable.
- The server keeps returning to the installer
- Inspect attached media and persistent boot order instead of reinstalling again.
Official references
Use the documentation for your installed version when a flag, service name or platform feature differs.
