Hyper-V
Operate against the host and guest estate.
- VM creation
- VM state
- Switches
- Checkpoints
- Imports
Integrations
Connect Hyper-V automation to the Microsoft stack around it.
Integrations let VyperForge use Hyper-V, PowerShell Direct, Active Directory, Configuration Manager, SMB storage, credential profiles and Teams notifications as part of repeatable workflows.
What problem does this solve?
Practical infrastructure work, made repeatable.
A VM is rarely useful just because it exists. It usually needs guest configuration, domain state, applications, deployment collections, credentials, storage and notifications.
VyperForge connects those operational pieces without forcing engineers to stitch every step together manually.
Typical workflow
How the workflow usually runs.
Connect hostSelect credential profileRun PowerShell DirectJoin domainDeploy applicationsAssign ConfigMgr collectionsNotify operators
Capabilities
What Integrations covers.
PowerShell Direct
Configure guests before network dependencies are ready.
- No guest networking required
- Variables
- Credentials
- Timeouts
- Logging
- Output
Active Directory
Prepare Windows systems for domain-backed environments.
- Domain join
- Name validation
- Connectivity checks
Configuration Manager
Connect builds to endpoint-management workflows.
- Discover sites
- SMS Provider
- Browse collections
- Search collections
- Add devices
SMB storage
Use network storage for images, packages and backups.
- UNC paths
- SMB shares
- Backup destinations
- Package sources
Credential management
Use named access accounts without exposing secrets in every workflow.
- Guest accounts
- Domain join accounts
- Backup share access
- ConfigMgr provider access
Microsoft Teams
Send operational status where teams already watch work.
- Success
- Failure
- Warnings
- Completion notifications
Key decisions
What to decide before you run it.
External systems
Connect to the systems already used for device collections, scripts, credentials and notifications.
Credentials
Keep integration secrets deliberate and scoped rather than embedding them in scripts or notes.
Automation boundary
Use integrations where they add context or action, while leaving core Hyper-V operations visible in VyperForge.
Operational notes
How this fits real work.
Integrations should reduce swivel-chair work without making the product feel dependent on a giant external platform.
The current page intentionally uses quiet placeholders where we still need final screenshots.
Product screens
See the workflow in VyperForge.
Product screens from the current beta build show how this capability appears in the desktop app.
ConfigMgr collection browserCollections, IDs, folders and selected targets.
Screen capture coming soon.
Screen capture coming soon.
Credential managementNamed account profiles without visible passwords.
Screen capture coming soon.
Screen capture coming soon.
ConfigMgr settingsProvider, site code and test connection result.
Screen capture coming soon.
Screen capture coming soon.
Notification settingsTeams and tray notification preferences.
Screen capture coming soon.
Screen capture coming soon.
Why VyperForge?
Practical advantages over native tools and loose scripts.
- PowerShell, AD and ConfigMgr tasks can live in the same plan.
- Credential profiles reduce repeated secret handling.
- PowerShell Direct avoids early guest-network dependency.
- ConfigMgr collection assignment becomes part of the build workflow.
- Notifications help operators understand completion and failures.
Example scenario
A practical way to use it.
A lab workflow can use ConfigMgr collections to target machines, trigger deployment tasks, then notify the team when the environment is ready.
Real-world examples
Where this helps.
- Join newly created clients to a lab domain.
- Add devices to ConfigMgr collections after build.
- Run PowerShell Direct scripts before guest networking is configured.
- Notify a team when a long build or protection plan completes.
Related platform areas