Every customer.
Its own workspace.
Keep tenants separate and switch between the workspaces you can access.
Use your main Microsoft account. Only workspaces assigned to you are available.
Forge / by Asterio
A clear path from
device to deployment.
Manage customer workspaces, approve devices and follow Windows installation from one portal.
Sign in with your authorized work account.
ONE WORKSPACE. CLEAR DECISIONS.
01
Prepare your workspace
One place for each customer.
02
Approve the device
Review before deployment starts.
03
Follow every stage
From WinPE to Windows startup.
Every customer.
A decision before
the next step.
Approve or deny device requests, with a record of each decision.
Private images.
Visible progress.
Signed image manifests, private downloads and progress reported by the device.
Test before rollout.
Deployment validation is ongoing. Verify firmware, drivers and installation on test devices before wider use.
Forge access
Waiting for access.
Ask your workspace administrator to grant access, then select Refresh access.
Administration
Your customers.
Manage tenant workspaces and access their deployment records.
Customer directory
Loading customers…
| Customer | Microsoft tenant | Status | Plan | Manage |
|---|
Administration
All devices.
Find known devices across customer workspaces.
| Customer | Device | Serial / model | Source | Status | Last seen | Manage |
|---|
Forge administration
Driver library.
Prepare model drivers for future deployments.
| Manufacturer / model | Windows / architecture | Version | Forge copy | Size | Manage |
|---|
Build host
Requested for build-host preparation
Packs that deployments or administrators asked for, and packs whose build or prepared copy needs attention. The build-host worker prepares each one automatically with the Driver Automation Tool as a compressed WIM and publishes it to Forge; deployments waiting at the driver step continue once it is ready.
| Manufacturer / model | Windows / architecture | Version | Manufacturer file | Status | Requested |
|---|
Automatic lookup
Model requests
Models that approved deployments asked for but the library could not match. Forge looks up the HP, Dell and Lenovo catalogs automatically; Surface models need a manual import.
| Manufacturer / model | System ID | Windows / architecture | Seen | Status | Manage |
|---|
Manufacturer catalogs
Find a model
Search the cached HP, Dell and Lenovo catalogs and add a pack to the library by its catalog identity. Forge never accepts download addresses.
| Manufacturer / model | Windows / architecture | Version | Size | Manage |
|---|
Customer connections
Customer status.
Workspace settings
Administration.
Setup and permissions
Microsoft app assignment allows sign-in. Forge workspace roles control access. These settings do not check current Microsoft assignments.
Connected tenants
Tenant workspaces.
One main account. The right access to each tenant.
Managing customer
Associated tenant workspaces
Each tenant keeps its own devices, deployments, logs and connections. Assign user access separately.
| Tenant workspace | Association | Manage |
|---|
Workspace user access
Assign users who have signed in through the main tenant. Each role applies only to this workspace.
| Main tenant user | Workspace access | Status |
|---|
Customer access
User access.
Manage the people who can use this customer workspace.
Current workspace
Only Forge administrators can switch customers. Archived customers are read-only.
| User | Portal access | Last seen |
|---|
View only reads progress. Deployment access manages deployments. Customer administrator also manages workspace users.
Prepare access
Add users before first sign-in
Choose a role for new users. Manage existing users in the list above.
These IDs apply only to this tenant and are not looked up in Microsoft. Assign users to the Forge portal Enterprise Application too.
Deployment troubleshooting
Deployment logs.
Current and older runs keep their own decisions and events.
Events through every stage
Forge records decisions and accepted changes. Device reports show the client's reported progress. Download logs saves this timeline with the device's uploaded log bundles (kept for 30 days) as one zip file.
| Recorded at | Stage | Source | Level | Event |
|---|
No recorded events yet.
Site delivery
Share downloads locally.
Customer defaults
Devices on the same network share verified Windows images automatically and use any Forge cache they can reach. Office uses Delivery Optimization in Full OS; existing organization policies take priority.
Caches
Cache servers enrolled for this customer. A cache fetches the Windows images for the customer's architectures and the driver packs for the models the customer uses, and reports every five minutes; a cache not seen for 24 hours is shown offline. Caches are optional and used by every device that can reach them; devices keep sharing on their own network and the HTTPS cloud fallback.
Download installer
The person configuring the cache signs in with their Forge account; an administrator role for this customer is required.
Install the MSI, open Forge Cache Setup, Configure, sign in. The cache enrols itself and renews its 90-day credential automatically; no credential is copied by hand.
PXE responders
Forge PXE Responder serves Forge's signed UEFI network-boot first stage over TFTP on this customer's network, for devices that boot as classic PXE clients (many HP models). It answers only the client networks listed here, only the selected architectures, and only while it is on; from iPXE on, the device continues over HTTPS exactly as with HTTP boot. A responder registers itself through Forge PXE Setup with an administrator's sign-in and reports every five minutes.
DHCP for network boot
Forge answers no DHCP. On the customer's DHCP server, set option 66 (boot server) to the responder's listen address and option 67 (boot file) to x64/snponly-shim.efi for x64 devices or arm64/snponly-shim.efi for ARM64 devices (a vendor class or policy tells them apart). Legacy BIOS PXE is not answered.
Only one TFTP server can use UDP port 69 on an address: do not run the responder on an address where Windows Deployment Services or another TFTP server listens. The responder then reports that the port is in use.
Driver models
The models whose driver packs site caches fetch in advance: derived from this customer's known devices, plus models added by hand. A pack the build host has not prepared yet is listed as not prepared and is fetched once it is ready.
| Manufacturer | Model | System ID | Source | Last seen | Pack | Manage |
|---|
Deployment control
Approve devices. Follow their progress.
Review requests in this workspace. Installation also requires approved media and target-disk confirmation in WinPE.
Current workspaceDefault environment
Connect a device
Start with the code on its screen.
Enter the device's code to connect it and approve this deployment.
- 01 Check the intended device
- 02 Choose its workspace
- 03 Claim and approve
Awaiting approval
—Ready for an operator’s decisionIn progress
—Approved or runningFinished
—Completed, denied, failed or expiredNeeds attention
—Failed, or stalled with no recent device activityDeployment progress
Device deployments
Not connected
Each device shows its latest deployment. Select View logs for current and older runs. Updates appear every 15 seconds. Stalled means a running device has not reported or advanced for a while. Ready means Windows preparation finished; user setup, licensing and enrollment are checked separately.
Your environment is getting ready
We’ll show attempts after connecting and checking access.
| Device / latest deployment | Architecture | Progress | Stage updated | Actions |
|---|
Customer inventory
Known devices
Claimed and Autopilot devices appear here. View logs opens a device's last three deployments, including ones removed from the list above. Known devices skip the code but need approval each time unless the workspace's zero-touch policy is on. A denial does not block their next attempt; remove a device to require a new claim.
Device-reported identity is not hardware attestation. Check the intended device before approving its deployment.
Loading devices…
| Device | Serial / model | Source | Status | Last seen | Manage |
|---|
Customer workspace administrators can remove Forge-only devices here. Autopilot devices stay protected. Removal keeps history; moving a device to another customer requires a Forge administrator to release its reservation.
Full OS preparation · Restricted preview
Microsoft 365 Apps
Install Office during Full OS preparation. Preview: Asterio Tech Test only. Set up Autopilot separately under Connect Microsoft Intune.
Deployment results
Deployment dashboard
How deployments are going.
Deployments started
—Success rate
—Median deployment time
—Active right now
—Per day
Deployments per day
UTC calendar days. Started counts new deployment requests; completed and failed count the day the deployment finished.
No deployments in this window yet.
Failure reasons
Fixed reasons the device reported with its failure, most frequent first.
| Reason | Failures | Share | Last |
|---|
No failed deployments in this window.
Active deployments
Devices waiting for approval, approved or installing right now.
| Device | Stage | Started | Updated |
|---|
No deployment is running right now.
Fleet dashboard
Every customer at a glance.
Fleet-wide deployment outcomes and each customer's numbers, sorted by failures.
Deployments started
—Success rate
—Median deployment time
—Active right now
—Per day, all customers
Deployments per day
No deployments in this window yet.
Customers
Trend bars show completed deployments above the line and failed below, per day.
| Customer | Started | Completed | Failed | Success | Median | Active | Trend | Top reason |
|---|
No customers are registered yet.
Failure reasons
| Reason | Failures | Share | Last |
|---|
No failed deployments in this window.
Infrastructure
Status.
What Forge itself knows about its platform, media, driver pipeline and customer sites. Checked on every visit and refreshed every minute.
Open infrastructure alerts
Raised by the five-minute evaluator for the whole fleet. Customer alerts appear in each customer's notifications and in the bell.
No open infrastructure alerts.