IT deployment workflow for Tallyfy

Deploy system images without failed installations

Deploying from images should be straightforward, but skipped steps or incompatible hardware causes failed installations and wasted time. This workflow ensures every deployment is verified, executed properly, and documented in your asset management system.

14 steps

Import into Tallyfy Preview steps

Information Technology Marketing editing

Run this workflow in Tallyfy with people, AI, and conditions

Installing From Image Run #2,481 Running now

Status	Step	Assignee
Status: Completed	1. Mount the ISO file in Windows 10 or 8.1	TM Team member
Status: Active	2. Access the virtual drive	Claude AI agent
Status: Waiting	3. Eject the virtual drive when done	TM Team member
Status: Conditional	4. Burn the ISO file to disc	Claude AI agent
+ 10 more steps below

Import this template into Tallyfy

Tallyfy is the accountability layer that lets this template mix people, AI agents, and conditions in one auditable flow

Process steps

Mount the ISO file in Windows 10 or 8.1

5 days from previous step

task

Right-click the ISO file and select "Mount" - Windows 10 and 8.1 have this built in, so you don't need extra software. You'll see a new virtual drive letter pop up in File Explorer. If mounting doesn't appear in your right-click menu, check that no third-party archive tool (like 7-Zip) has taken over ISO file associations. You can fix this in Default Apps settings.

Access the virtual drive

5 days from previous step

task

Open File Explorer and find the new virtual drive that appeared after mounting. It'll show up as a DVD drive with the ISO's contents. Browse into it - you should see the installer files (like setup.exe for Windows images). If the drive isn't showing, try mounting again or check Disk Management to see if it's there but just hasn't been assigned a letter.

Eject the virtual drive when done

5 days from previous step

task

Once you're finished with the ISO contents, right-click the virtual drive in File Explorer and select "Eject." This unmounts the ISO and frees up the drive letter. It's not required, but it keeps your File Explorer clean and avoids confusion if you're working with multiple ISOs. The original ISO file stays exactly where it was - ejecting only removes the virtual mount.

Burn the ISO file to disc

5 days from previous step

task

If you need a physical disc, right-click the ISO and select "Burn disc image" (built into Windows). Pick your disc burner drive, insert a blank DVD, and hit Burn. Check the "Verify disc after burning" box - it adds a few minutes but catches bad burns before you waste time trying to boot from a corrupted disc. For larger images, you'll need a DVD-DL or Blu-ray.

Install from the burned disc

5 days from previous step

task

Insert the burned disc into the target machine and boot from it. You'll usually need to press F12, F2, or Del during startup to get to the boot menu - it varies by manufacturer. Select the DVD/CD drive as your boot device. If the machine doesn't recognize the disc, check that the BIOS boot order includes optical drives and that Secure Boot isn't blocking it.

Use the Windows USB/DVD Download Tool

5 days from previous step

task

Download and run Microsoft's USB/DVD Download Tool if you're creating bootable media from a Windows ISO. It's straightforward - point it at your ISO file, choose whether you want USB or DVD output, and let it do its thing. Note: this tool's older and only works for Windows ISOs. For other images or more control, you'll want Rufus or Ventoy instead.

Choose your media type

5 days from previous step

task

Pick USB or DVD based on what makes sense for your situation. USB is faster to create and faster to boot from - it's the better choice in most cases. DVDs are useful when you need read-only media (so nobody accidentally overwrites it) or when the target machine doesn't support USB boot. If you're imaging multiple machines, USB is usually the way to go since you can reuse it.

Insert and prepare your USB drive

5 days from previous step

task

Plug in a USB drive with enough space (8GB minimum for most Windows images, 16GB to be safe). Back up anything on it first - the tool will wipe it completely. Make sure you're selecting the right USB drive, especially if you've got multiple ones plugged in. Formatting the wrong drive is a mistake you only make once. The tool will format it and copy the bootable image files.

Insert a blank DVD for burning

5 days from previous step

task

If you chose DVD, insert a blank disc now. Make sure it's the right capacity for your image - a standard DVD holds about 4.7GB, and a dual-layer DVD-DL holds about 8.5GB. If your image is larger than what fits on one disc, you'll need to switch to USB or use a Blu-ray burner. The tool will start writing once it detects the blank disc.

Verify the target system's requirements

1 day from previous step

task

Before you start imaging, confirm the target hardware can actually run what you're deploying. Check the CPU architecture (x86 vs x64), available disk space, RAM, and whether you've got compatible drivers. Deploying an image to hardware that doesn't match wastes everyone's time and can leave the machine in a broken state. Pull up the spec sheet if you're not sure.

Prepare your deployment media or network share

1 day from previous step

task

Get your image source ready - whether that's a USB drive, network share, or deployment server like WDS/SCCM/MDT. If you're using a file-based image, verify its integrity with checksums (MD5 or SHA256) before you start. A corrupted image means a failed deployment and wasted time. Double-check that your deployment tools are configured and the network path is accessible from the target machine.

Boot the target machine and deploy the image

1 day from previous step

task

Boot the target system from your deployment media - PXE boot, USB boot, or a recovery partition depending on your setup. Start the imaging process and monitor its progress. Large images can take 20-45 minutes depending on the method and disk speed. Don't interrupt it mid-way or you'll have to start over from scratch. If it fails, check the deployment logs before retrying - there's usually a specific reason.

Run post-image configuration

1 day from previous step

task

After the image lands, handle the post-deployment tasks. This typically means setting the computer name, joining your domain, installing hardware-specific drivers, and pulling down the latest patches. If you've got deployment scripts or answer files, run them now. Even with automation, spot-check that things actually worked - domain join failures and missing drivers are the most common issues you'll hit at this stage.

Verify everything works and update your records

1 day from previous step

task

Test the system end-to-end before handing it off. Apps should launch, the network should connect, peripherals should work, and users should be able to log in. Don't skip this - it's much easier to fix problems now than after someone's already using the machine. Update your asset management system with the serial number, image version, and deployment date. Future you will thank present you for keeping records clean.