Stage a Verified RHEL ISO in vSphere

Verify and stage a RHEL installation ISO on a vSphere datastore.

Introduction

30 Second Summary

Large setup files often move through several computers before they reach the right place. Even one changed piece can make the file unsafe to use.

In this project, you will move a Red Hat Enterprise Linux setup file through a Windows SMB file share and into VMware vSphere 8.0. You will use a SHA-256 check, which works like a file fingerprint, to make sure every copy matches before you start a test virtual machine.

What You'll Build

You will start a test VM from the uploaded ISO and see the RHEL setup screen, proving the file completed the trip safely.

By the end of this project, you'll have:

  • A media record that shows the approved RHEL version, computer type, exact filename, and official file fingerprint.
  • A checked transfer path where the downloaded file and both copied files have the same SHA-256 fingerprint.
  • Clear boot proof showing the ISO in vSphere and the RHEL setup screen inside the test VM.
  • Secret Mission: Put the fingerprints, file locations, transfer time, and boot proof into one record that another administrator can check.

Are there any prerequisites?

You need the approved RHEL file details and access to Red Hat, the Windows share, and vSphere. You also need enough storage space and a powered-off test VM that is safe to use.

Before We Start

Before you move any files, decide exactly what you are moving and where it needs to go. Write down the approved RHEL version, computer type, full ISO, SMB share, VMFS or NFS datastore, test VM, and reason for the work.

Validate the Transfer Path

Your approved RHEL plan tells you which full ISO to use. It also lists every place the file must travel.

The transfer can fail if a drive is full, you cannot write to a folder, or vSphere cannot use the storage. You will test the whole route before downloading the large ISO.

In this step, get ready to:
  • Check that the Windows tools are ready.
  • Test the shared folder and make the two local folders.
  • Check the datastore space and the test VM settings.
Confirm the Windows tools

You will use Microsoft Edge to open the protected download pages. You will use File Explorer in Windows to work with folders and the shared location.

Windows PowerShell 5.1 has the command that checks each ISO. You will test that command with a small file before using it on the large download.

  • Press the Windows key to open Windows search.
  • Type Microsoft Edge into the search field.
  • Press Enter to open Microsoft Edge.
  • Choose the tab that matches what you see.

✔️ Microsoft Edge opens

Microsoft Edge is ready. You will use it to open the protected Red Hat and vSphere pages later.

ⓧ Microsoft Edge is unavailable

Your organization may control which apps you can install. Follow its rules before installing Microsoft Edge.

  • Use another organization-approved browser to visit the Microsoft Edge download page.
  • Select Download Edge for Windows.
  • Complete the installation under your organization's software policy.
  • Repeat the Windows search after the installation completes.

Installation blocked?

Ask your device administrator to install Microsoft Edge if software installation is centrally managed.

You can also ask for help with an organization-managed Edge installation.

  • Press the Windows key to open Windows search.
  • Type File Explorer into the search field.
  • Press Enter to open File Explorer.

You should see a File Explorer window with access to local drives and network locations.

  • Press the Windows key to open Windows search again.
  • Type Windows PowerShell into the search field.
  • Press Enter to open Windows PowerShell.
  • Check the Windows PowerShell version by running:
$PSVersionTable.PSVersion

What does this command show?

This command shows which PowerShell version is open. This project uses Windows PowerShell 5.1.

  • Choose the tab that matches the version result.

✔️ I see version 5.1

The hard part of the local tool check is complete. Windows PowerShell 5.1 is ready to calculate hashes.

ⓧ I see an older version

Windows PowerShell versions below 5.1 are outside this project's supported path.

  • Stop before running the hash workflow.
  • Ask your device administrator to update the device to a supported Windows version that includes Windows PowerShell 5.1.
  • Share Microsoft's Windows Management Framework guidance with the administrator.
  • Repeat the version check after the device is updated.

ⓧ Windows PowerShell is unavailable

Windows PowerShell 5.1 is included with supported Windows versions. Its absence requires an administrator to repair or replace the managed Windows environment.

  • Stop before transferring any files.
  • Ask your device administrator for a supported Windows device with Windows PowerShell 5.1 available.
  • Repeat the Windows search after the administrator resolves the issue.

The next command makes a SHA-256 fingerprint for the PowerShell program. Before you run it, do you think the result will show the file and the fingerprint type?

  • Test the hash tool by running:
Get-FileHash $PSHOME\powershell.exe | Format-List

What does this check prove?

This command makes a file fingerprint for PowerShell. Its result shows the fingerprint type, fingerprint value, and file location.

This test uses a small file already on your computer. It lets you check the command before you download the large RHEL ISO.

You should see Algorithm, Hash, and Path in the output. The algorithm should be SHA256.

Missing hash details?

Check that the window title says Windows PowerShell. Another kind of PowerShell window may give a different result.

Run the command again as one complete line. Keep the pipe character between the hash command and the formatting command.

You can ask for help diagnosing the PowerShell hash check.

Validate the share and create the workspaces

An SMB file share is a shared Windows folder that both workstations can reach. A small test file proves that you can add files before you try the much larger ISO.

The Red Hat Customer Portal and VMware vSphere Client 8.0 use your work accounts. Only enter your sign-in details on your organization's approved pages.

  • In Microsoft Edge from earlier, navigate to the Red Hat Customer Portal.
  • Sign in with your organization's Red Hat credentials.
  • Switch back to File Explorer from earlier.
  • Select the File Explorer address bar.
  • Enter approved SMB share path.
  • Press Enter to display the approved share folder.

You should see the files inside the approved shared folder. This proves your Windows computer can reach it.

  • Create a small empty test file inside the approved share folder.

You should see the test file inside the shared folder. This proves your account can add a file there.

  • Remove the small test file from the approved share folder.

Good progress. You proved that you can add files to the shared folder, and you removed the test file.

  • On the download workstation, create C:\RHEL-Transfer with File Explorer.
  • Open C:\RHEL-Transfer in File Explorer.

You should see an empty local folder ready to receive the approved RHEL Installation ISO.

  • On the vCenter-connected workstation, create C:\RHEL-vCenter-Staging with File Explorer.
  • Open C:\RHEL-vCenter-Staging in File Explorer.

You should see an empty folder for the copy that you will upload to vSphere. If one Windows computer does both jobs, create both folders on that computer.

  • Check the available storage on the drive containing C:\RHEL-Transfer.
  • Confirm that the available capacity exceeds the space required for the approved full Installation ISO.

The download folder should have enough free space for one full ISO file.

  • Check the available storage on the drive containing C:\RHEL-vCenter-Staging.
  • Confirm that the available capacity exceeds the space required for the approved full Installation ISO.

The vCenter staging folder should also have enough free space for one full ISO file.

  • Check the available capacity for approved SMB share path.
  • Confirm that the available capacity exceeds the space required for the approved full Installation ISO.

The approved share now has enough capacity for the controlled handoff.

  • In Microsoft Edge, navigate to your organization's VMware vSphere Client 8.0 address.
  • Sign in with your organization-approved vCenter account.

You should see the vSphere Client inventory available to your account.

Can't complete an access check?

If the test file fails, the shared folder may be offline or your account may not be allowed to add files. Ask the folder owner to check the path and your access before you continue.

If you cannot create a local folder, the drive may be locked or full. Ask your device administrator for enough approved space for both named folders.

You can ask for help identifying which transfer-path permission failed.

Confirm the datastore and test VM

The target VMFS or NFS datastore is the storage area that will hold the ISO. The target ESXi host must be able to reach it, and it needs enough free space for the full ISO.

A Virtual Volumes datastore follows a constrained upload path that is outside this project. The approved route uses the datastore named in your media transfer plan.

Before you check the final route, do you expect both the datastore upload controls and the VM hardware settings to be available?

  • In the vSphere Client session from earlier, select target datastore name.
  • Confirm that the displayed datastore type is VMFS or NFS.
  • Confirm that the datastore is accessible to the target ESXi host.
  • Confirm that the datastore has enough free capacity for the approved full Installation ISO.

The target datastore should now meet the type, access, and capacity requirements for the later upload.

  • Right-click target datastore name.
  • Select Browse Files.
  • Confirm that Upload Files is available in the datastore browser.

You should see the datastore file browser with the upload control available. This proves your account can reach the documented local-file upload workflow.

  • Return to the virtual machine inventory.
  • Select test VM name.
  • Confirm that the test VM is powered off.
  • Select Edit Settings.
  • Select Virtual Hardware.
  • Confirm that CD/DVD Drive can be edited when present.
  • Confirm that Add New Device is available when no CD/DVD drive is present.
  • Exit the settings without changing the test VM.

You should see that the disposable test VM is powered off. Its virtual CD/DVD configuration should also be accessible.

Missing a datastore or VM control?

Stop if the selected datastore is Virtual Volumes. Request an approved VMFS or NFS ISO datastore from the storage administrator.

Missing datastore controls can indicate absent Datastore.Browse Datastore or Host.System Management privileges. Missing CD/DVD controls can indicate absent Virtual machine.Change Configuration.Add or remove device permission.

You can ask for help preparing a precise vSphere access request.

The route is cleared. Microsoft Edge, File Explorer, Windows PowerShell, the approved share, both local workspaces, the datastore, and the powered-off test VM are ready without transferring the RHEL ISO.

Your transfer path is ready from end to end. Next, you will download the approved full RHEL Installation ISO and record its official SHA-256 checksum.

Download the Approved RHEL Installation ISO

The path you tested is ready for the approved Red Hat Enterprise Linux file. Now you need to make sure you choose the right file.

The Boot ISO needs other files from the network during setup. You need the full Installation ISO, which the Red Hat Customer Portal calls Binary DVD.

In this step, get ready to:
  • Find the approved full RHEL image.
  • Download the Binary DVD file to the local transfer folder.
  • Save the details that identify the ISO.
Choose the approved download entry

The portal has filters that shorten the list of downloads. Choose the approved version and computer type to find the right image.

  • Switch back to the Red Hat Customer Portal tab in Microsoft Edge.
  • Select Downloads in the portal navigation.
  • Select Red Hat Enterprise Linux.
  • Open All Red Hat Enterprise Linux Downloads.
  • Select the organization-approved option under Product Variant.
  • Select approved RHEL major release under Version.
  • Select approved architecture under Architecture.
  • Confirm the displayed filters match the approved media plan.

You should see download entries filtered to the approved product variant. The displayed version plus architecture should match your transfer plan.

Cannot See the Approved Downloads?

  • Confirm the portal session uses an account connected to your organization's active Red Hat subscription.
  • Ask your subscription administrator to confirm your download entitlement if the approved release remains unavailable.

Get help checking why the approved RHEL download is unavailable.

Download the full installation image

The full image includes the files needed for the later boot test. In the portal, this file is the Binary DVD entry.

The ISO is a multi-gigabyte file. Expect the download to take several minutes or longer on a constrained enterprise connection.

  • Locate the full Installation ISO entry labeled Binary DVD.
  • Confirm the entry shows approved RHEL major release.
  • Confirm the entry shows approved architecture.
  • Start the download from that Binary DVD entry.
  • Use the browser's destination chooser to save the file in C:\RHEL-Transfer.
  • Preserve the filename supplied by the portal.
  • Wait for Microsoft Edge to mark the download as complete.

The completed download status confirms that the browser has finished writing the local file.

  • Switch back to File Explorer from earlier.
  • Navigate to C:\RHEL-Transfer from the File Explorer address bar.

The empty workspace from the previous step should now contain the downloaded .iso file.

Download Missing or Incomplete?

  • Check the completed download entry in Microsoft Edge to identify the destination folder.
  • Restart the download into C:\RHEL-Transfer if the browser still shows an incomplete transfer.
  • Confirm the workstation still has enough free storage for the ISO.

Help me diagnose an incomplete RHEL ISO download.

Record and verify the media details

The official SHA-256 checksum is the fingerprint Red Hat gives this exact file. Copy it from the same entry as the ISO so you can compare the two later.

  • Return to the matching Binary DVD entry in Microsoft Edge.
  • Record the text before the .iso extension as exact ISO filename.
  • Record the displayed release as approved RHEL major release.
  • Record the displayed architecture as approved architecture.
  • Record the official checksum as official SHA-256.
  • Confirm the checksum comes from the same Binary DVD entry as the downloaded filename.

Before you check, do you expect the downloaded filename to match the portal entry exactly?

  • Switch back to the File Explorer window showing C:\RHEL-Transfer.
  • Confirm the downloaded filename matches exact ISO filename.
  • Return to the matching portal entry.
  • Confirm its release matches approved RHEL major release.
  • Confirm its architecture matches approved architecture.
  • Confirm the recorded checksum came from that same entry.

You should see exact ISO filename.iso in C:\RHEL-Transfer.

The matching portal entry should show release approved RHEL major release. It should show architecture approved architecture.

Your recorded official checksum should be official SHA-256 from that same portal entry.

What Have You Confirmed?

You have confirmed the downloaded image's identity plus its official reference checksum. PowerShell verifies the downloaded bytes in the next step.

That is the media-selection risk handled. Next, you will calculate the download's SHA-256 value before placing the ISO on the approved share.

Copy the ISO to the Windows File Share

Your approved RHEL ISO is now saved in C:\RHEL-Transfer\exact ISO filename.iso. You also saved its official SHA-256 from the matching Red Hat Customer Portal entry.

A large copy can have the right name even when part of the file changed. You will check the local file before moving it to the approved SMB share.

In this step, get ready to:
  • Check the local ISO against the official SHA-256 fingerprint.
  • Copy the checked ISO to the approved shared folder.
  • Compare the names and sizes of both copies.
Verify the local ISO hash

A SHA-256 hash is a digital fingerprint made from every part of a file. Windows PowerShell will calculate that fingerprint for your ISO.

The calculated value must match the official portal value before this file becomes the source for your share copy.

  • Press the Windows key to open the search bar.
  • Type Windows PowerShell into the search bar.
  • Press Enter to open Windows PowerShell.

Before you calculate the hash, do you expect the local value to match the official value you recorded?

  • Replace <Path> in the command below with C:\RHEL-Transfer.
  • Replace <Filename> with your recorded ISO filename including .iso.
  • Calculate the local ISO hash by running the completed command:
Get-FileHash -Path "<Path>\<Filename>" -Algorithm SHA256

What Does This Command Do?

  • Get-FileHash calculates a fingerprint from the file's contents.
  • -Path identifies the ISO that PowerShell reads.
  • -Algorithm SHA256 selects the algorithm used for the official portal checksum.

PowerShell returns an Algorithm, Hash, and Path for the ISO.

  • Compare the returned Hash with official SHA-256.

You should see SHA256 as the algorithm. The returned hash should exactly equal your official value.

That is a strong checkpoint. Your local ISO now matches the official portal record.

Hash Does Not Match?

  • Stop the transfer if the returned hash differs from the official value.
  • Download the ISO again from its matching Red Hat Enterprise Linux portal entry.
  • Check that the completed path points to the file inside C:\RHEL-Transfer if PowerShell cannot find the ISO.

help me diagnose my ISO hash mismatch

Copy the verified ISO to the share

The local source is verified. File Explorer now carries it to the approved handoff folder while preserving its filename.

Your destination is approved SMB share path. Several minutes or longer can be normal for this large copy on a busy enterprise network.

  • Switch back to File Explorer from earlier.
  • Open a second File Explorer window.
  • Navigate the second window to C:\RHEL-Transfer.
  • Right-click exact ISO filename.iso.
  • Select Copy.
  • Switch back to the approved SMB share window from earlier.
  • Right-click an empty area inside the approved share folder.
  • Select Paste.

File Explorer shows transfer progress while Windows copies the ISO.

  • Wait for the transfer progress to finish.

You should see exact ISO filename.iso inside the approved share folder.

ISO Missing from the Share?

  • Confirm that the transfer progress finished before checking the destination.
  • Confirm that you pasted the ISO into approved SMB share path.
  • Stop if Windows reports that a file with the same name already exists. Confirm the existing file's owner and purpose before replacing anything.

help me find my copied ISO on the SMB share

Compare the two copies

The shared folder now has a copy of the local ISO. Matching names and sizes are the first signs that the correct file arrived.

Before you compare the copies, what evidence do you expect the filename and displayed size to provide?

  • Read the displayed filename for the ISO in C:\RHEL-Transfer.
  • Read the displayed filename for the ISO in the approved share folder.
  • Compare the two displayed filenames.
  • Read the displayed size for the local ISO.
  • Read the displayed size for the shared ISO.
  • Compare the two displayed sizes.

You should see exact ISO filename.iso in both locations. You should also see matching displayed sizes.

The expected file reached the shared folder. You still need to check its SHA-256 fingerprint to prove every part matches.

What Did This Check Prove?

Matching filenames show that the intended ISO name survived the handoff. Matching displayed sizes show that both file listings report the same amount of data.

These checks do not inspect every byte. The shared ISO remains intentionally unverified until its SHA-256 value is calculated.

Your verified source has reached the approved Windows share with its original name and displayed size intact. Next, you will calculate the shared copy's SHA-256 value to close the evidence gap.

Verify the Shared ISO and Staging Copy

The shared ISO has the same name and size as the checked download. Those two details cannot prove that every part of the file matches.

Windows PowerShell 5.1 can make a SHA-256 fingerprint from the file. You will use it to check the last copy before uploading the ISO to vSphere.

In this step, get ready to:
  • Check the ISO in the approved shared folder.
  • Copy the checked ISO into C:\RHEL-vCenter-Staging.
  • Make sure all four SHA-256 fingerprints match.
Verify the shared copy's SHA-256 hash

SHA-256 makes a fingerprint from every part of the file. If it matches the official fingerprint, the shared copy did not change during the move.

  • On the Windows workstation that can reach vCenter, switch back to Windows PowerShell.
  • Replace <Path>\<Filename> in the command below with the full UNC or mapped-drive path to the shared ISO.

Before you run the check, do you expect the shared copy's fingerprint to match the official value?

  • Calculate the shared copy's SHA-256 hash by running the edited command:
Get-FileHash -Path "<Path>\<Filename>" -Algorithm SHA256

What does this command check?

  • Get-FileHash calculates a fingerprint from the contents of the selected file.
  • -Path identifies the shared ISO that PowerShell reads.
  • -Algorithm SHA256 selects the same hashing algorithm used for the official checksum.
  • Hash is the value you compare with the official Red Hat checksum.

PowerShell returns a result with Algorithm, Hash, and Path.

  • Compare the returned Hash with the official SHA-256 value recorded from the matching portal entry.
  • Confirm that the shared-copy value matches the official value character for character.

Shared hash does not match?

  • Confirm that the command points to the ISO in the approved share folder.
  • Confirm that the filename belongs to the approved release and architecture.
  • Stop the transfer if the path is correct but the hash differs.
  • Repeat the approved file handoff from the verified local download before checking the shared copy again.

help me investigate a shared ISO hash mismatch

The matching fingerprint proves that the shared folder has an exact copy of the approved ISO.

Copy the verified ISO into the staging folder

The datastore upload in VMware vSphere Client selects a file from the local computer. The existing C:\RHEL-vCenter-Staging folder provides that controlled upload source.

This multi-GB transfer may stay active for a while on a busy enterprise network.

  • Switch back to File Explorer in Windows on the vCenter-connected workstation.
  • Return to the approved SMB share folder from earlier.
  • Select the verified ISO with its original filename.
  • Copy the selected ISO using Copy in File Explorer.
  • Navigate to C:\RHEL-vCenter-Staging in File Explorer.
  • Paste the ISO using Paste in File Explorer.
  • Wait for the copy progress window to close.

You should see the ISO inside C:\RHEL-vCenter-Staging with the same original filename.

Copy did not complete?

  • Confirm that the approved share is still accessible from the vCenter-connected workstation.
  • Confirm that C:\RHEL-vCenter-Staging still has enough free space for the ISO.
  • Remove any incomplete staging copy before repeating the approved copy operation.

help me troubleshoot the ISO staging copy

Verify the local staging copy

The staging file is a new copy of the verified shared ISO. An independent hash check proves that this final handoff preserved the same contents.

  • Switch back to Windows PowerShell on the vCenter-connected workstation.
  • Replace <Path>\<Filename> in the command below with the full path to the ISO inside C:\RHEL-vCenter-Staging.

Before you run the final check, do you expect the official checksum and all three calculated hashes to match?

  • Calculate the staging copy's SHA-256 hash by running the edited command:
Get-FileHash -Path "<Path>\<Filename>" -Algorithm SHA256

Why hash the staging copy again?

  • The new path makes PowerShell read the local copy intended for the datastore upload.
  • A matching Hash proves that the share-to-staging copy preserved the ISO contents.
  • The result completes an integrity chain from the official checksum to the final local staging file.

PowerShell returns Algorithm, Hash, and Path for the staging copy.

  • Compare the staging copy's Hash with the official SHA-256 value.
  • Confirm that the official checksum and all three calculated hashes match exactly.

You should now have four identical SHA-256 values: the official portal checksum, the local download hash, the shared copy hash, and the staging copy hash.

Staging hash does not match?

  • Confirm that the command points to the ISO inside C:\RHEL-vCenter-Staging.
  • Stop before uploading the ISO if the staging hash differs.
  • Remove the mismatched staging copy.
  • Repeat the approved copy operation from the verified shared ISO.

help me investigate a staging ISO hash mismatch

That completes the integrity chain: the official checksum and every calculated copy now match exactly.

Your verified staging copy is ready. Next, you will upload it to the approved datastore and prove that it boots the disposable test VM into the RHEL installer.

Upload and Boot the ISO in vSphere

Every SHA-256 value now matches the official Red Hat checksum. The verified staging copy is ready on the vCenter-connected workstation.

VMware vSphere uploads files from a local computer into a datastore. A successful RHEL installer boot proves the host can use that uploaded media.

In this step, get ready to:
  • Upload the verified staging ISO to the approved datastore folder.
  • Attach the datastore ISO to the powered-off disposable test VM.
  • Boot the test VM to the RHEL installer screen.
Upload the verified ISO

The datastore browser moves a local file into storage that the target ESXi host can access. Your verified copy in C:\RHEL-vCenter-Staging is the source for this upload.

Why Direct Datastore Upload?

Direct datastore upload is the shortest path for one verified ISO. It places the media where the target ESXi host can use it.

A Content Library adds catalog management that this one-file handoff does not need.

  • Return to the VMware vSphere Client session from earlier.
  • Select target datastore name in the inventory.
  • Right-click the selected datastore.
  • Select Browse Files.
  • Create approved ISO folder with New Folder if it is missing.
  • Select approved ISO folder as the upload destination.

The upload can remain in progress for several minutes because the ISO is a large file. That delay is the verified media moving into the datastore.

  • Click Upload Files.
  • Select C:\RHEL-vCenter-Staging\exact ISO filename.iso in the local file picker.
  • Click Open.
  • Wait for the upload to finish.
  • Refresh the datastore browser.

You will see exact ISO filename.iso inside approved ISO folder on target datastore name.

That is the slowest handoff complete. The verified ISO is now available to the target host.

Can't Upload the ISO?

  • Confirm you selected target datastore name from earlier.
  • Check that the datastore still has sufficient free capacity.
  • Retry the upload after refreshing the datastore browser.

help me troubleshoot a vSphere datastore ISO upload

Attach the datastore ISO to the test VM

A virtual CD/DVD drive presents the datastore ISO to the VM as installation media. The Datastore ISO File source keeps the VM connected to the uploaded copy.

  • Select test VM name in the vSphere inventory.
  • Click Edit Settings.
  • Select Virtual Hardware in the settings dialog.
  • Locate CD/DVD Drive in the hardware list.
  • Click Add New Device if the drive is missing.
  • Select CD/DVD Drive from the device menu if you opened it.
  • Set the drive's media source to Datastore ISO File.
  • Click Select File.
  • Select target datastore name.
  • Open approved ISO folder.
  • Select exact ISO filename.iso.
  • Enable Connect At Power On.
  • Save the settings.

What Do These Settings Do?

Datastore ISO File tells the VM to read installation media from the selected datastore path.

Connect At Power On mounts that media when the VM starts. This gives the VM a bootable virtual disc from its first power-on moment.

The saved CD/DVD configuration now points to target datastore name/approved ISO folder/exact ISO filename.iso.

Can't Select the Datastore ISO?

  • Confirm the VM is powered off before reopening its CD/DVD settings.
  • Confirm target datastore name is selected in the file browser.
  • Confirm exact ISO filename.iso remains visible inside the approved folder.

help me fix the VM's datastore ISO attachment

Boot to the RHEL installer

The installer screen is the final proof that the host can read the uploaded ISO. The project stops at that screen because installing the operating system is outside this transfer test.

The console may stay quiet briefly while the VM starts from the ISO. That pause is normal during boot.

Before you power on the VM, do you expect it to start from the datastore ISO? Keep that prediction in mind.

  • Power on test VM name from the vSphere Client.
  • Open the VM console.

You will see the RHEL installation menu or welcome screen. This proves the uploaded ISO is readable boot media.

  • Leave the installer at the menu or welcome screen without starting the operating-system installation.

VM Didn't Boot From the ISO?

  • Power off the disposable test VM before editing its CD/DVD settings.
  • Confirm the drive uses Datastore ISO File.
  • Confirm Connect At Power On is enabled.

help me diagnose why the test VM did not boot from the RHEL ISO

You have completed the verified media chain from the Red Hat download to a bootable vSphere datastore ISO. The installer screen confirms the handoff works from end to end.

Secret mission

Build an Audit-Ready Transfer Record

Turn your verified RHEL media handoff into an audit-ready record. Link every calculated hash to the exact ISO filename across both transfer locations. Add the transfer timestamp plus policy-approved boot evidence.

Clean Up Your Resources

Clean Up Your Resources

Choose whether to keep the verified media available, pause for a later installation window, or remove approved copies entirely. Your existing enterprise access adds no expected incremental charge.

Resources you used:

  • The verified RHEL Installation ISO in C:\RHEL-Transfer, named exact ISO filename.iso.
  • The verified vCenter upload copy in C:\RHEL-vCenter-Staging, named exact ISO filename.iso.
  • The verified ISO in the approved Windows SMB share at approved SMB share path.
  • The audit-ready transfer-record.txt in approved SMB share path.
  • The policy-approved evidence package in approved change ticket or transfer-evidence location.
  • The uploaded ISO in the VMware vSphere 8.0 datastore at target datastore name/approved ISO folder/exact ISO filename.iso.
  • The ISO attachment on disposable test VM test VM name.

Keep everything running

No media cleanup is needed. Choose this if the ISO remains approved for the planned installation window.

  • Power off test VM test VM name.
  • Leave the CD/DVD Drive attached for the planned installation window.
  • Keep the verified download in C:\RHEL-Transfer.
  • Keep the verified upload copy in C:\RHEL-vCenter-Staging.
  • Retain the verified share copy according to organizational policy.
  • Retain transfer-record.txt according to organizational policy.
  • Retain the evidence package according to organizational policy.
  • Retain the datastore copy within the approved storage quota.

Pause - I'll come back to this later

This option powers off the disposable test VM while preserving the verified transfer chain for later work.

  • Power off test VM test VM name.
  • Preserve every verified ISO copy listed above.
  • Keep transfer-record.txt in the approved SMB share.
  • Keep the policy-approved evidence package in approved change ticket or transfer-evidence location.
  • Record the pending installation or approval status in the change ticket.
  • Leave the datastore ISO attached to the powered-off test VM.

Delete - I don't want to use this again

Removing verified media is permanent. Each policy-managed copy stays in place unless your organization approves its deletion.

Detach the ISO from the test VM
  • Return to test VM test VM name in the signed-in VMware vSphere Client.
  • Power off the test VM.
  • Select Edit Settings.
  • Expand CD/DVD Drive under Virtual Hardware.
  • Clear Connect At Power On.
  • Remove the CD/DVD Drive from Virtual Hardware.
  • Save the settings.
  • Select Edit Settings again.

You should no longer see CD/DVD Drive under Virtual Hardware.

Remove the local ISO copies
  • Return to File Explorer from earlier.
  • Go to C:\RHEL-Transfer.
  • Select exact ISO filename.iso.
  • Choose Delete.
  • Go to C:\RHEL-vCenter-Staging.
  • Select exact ISO filename.iso.
  • Choose Delete.

You should no longer see exact ISO filename.iso in either local folder.

Remove the share artifacts
  • Check the retention policy for the verified share copy.
  • Check the retention policy for transfer-record.txt.
  • Return to approved SMB share path in File Explorer.
  • Select exact ISO filename.iso only when removal is approved.
  • Choose Delete.
  • Select transfer-record.txt only when removal is approved.
  • Choose Delete.
  • Confirm that every approved deletion is absent from the share folder.
Remove the evidence package
  • Check the retention policy for the transfer evidence.
  • Return to approved change ticket or transfer-evidence location.
  • Remove the evidence package for exact ISO filename.iso through the organization's approved records procedure.
  • Confirm that the approved location no longer contains that evidence package.
Remove the datastore ISO
  • Confirm that retention policy permits removal of the datastore copy.
  • Confirm that no other VM or administrator depends on the datastore copy.
  • Return to datastore target datastore name in the signed-in VMware vSphere Client.
  • Select Browse Files.
  • Select folder approved ISO folder.
  • Select exact ISO filename.iso.
  • Choose Delete.
  • Confirm that the ISO is no longer visible in Browse Files.

Nice Work!

Nice Work!

You did it! You completed a controlled Red Hat Enterprise Linux media handoff through the approved Windows SMB share into VMware vSphere 8.0. The disposable test VM now boots the verified ISO to the RHEL installer.

You've learned how to:

  • Select the organization-approved full Installation ISO using the required release and architecture. You identified the correct media through its Binary DVD label.
  • Protect the media transfer chain by comparing every calculated SHA-256 hash with the official value. Matching hashes prove the download and each staged copy remained unchanged.
  • Upload the verified ISO to a compatible datastore. You mounted it as virtual CD/DVD media on a disposable VM. You confirmed the RHEL installer starts without beginning the operating-system installation.
  • Secret Mission: Produced an audit-ready transfer record that links the matching hashes to every file location. You saved policy-approved datastore and boot evidence for independent review.

Ready to quiz yourself?