- Notes, cautions, and warnings
- Preface
- PowerProtect Data Manager File System Agent Overview
- Enabling the File System Agent
- About the File System agent
- Application agent and File System agent coexistence
- File System agent prerequisites
- File System agent limitations
- Block-based backups
- Best practices for file system backups
- Configure the file system parallel backup setting
- Configure asset multi-streaming for file-based backups
- Protect an asset with the File System agent
- Protect an asset in a Microsoft Windows Server clustered environment with the File System agent
- Installing and uninstalling the File System agent on AIX
- Installing and updating the File System agent on Linux
- Installing and updating the File System agent on Windows
- Manage the File System agent
- Configure the centralized file-level restore service port number
- Update the application agent in the PowerProtect Data Manager UI
- Moving a File System agent from one PowerProtect Data Manager system to another
- Enable the File System agent after migrating File System assets to a refreshed server
- Managing Storage, Assets, and Protection
- Enable an asset source
- Discover a file system host
- Protection policies for File System agent
- Supported protection policy purposes
- Supported protection policy objectives
- File System replication triggers
- Roadmap for planning a protection policy
- Before you add a protection policy for file system protection
- Add a protection policy for file system protection
- Protection rules
- Cancel a File System agent backup or restore job
- Add a service-level agreement
- Extended retention for protection policies created in PowerProtect Data Manager 19.11 or earlier
- Edit the retention period for backup copies
- Delete backup copies
- Host CPU throttling
- Exclusion filters for File Systems
- Centralized restore of a file-system asset
- Updating the File System agent hostname or IP address
- Manage the PowerProtect agent service
- Performing Self-Service Backups and Restores with the File System Agent
- Performing Self-Service Backups and Restores for Disaster Recovery
- Performing Disaster Recovery with the File System Agent in Windows
- Disaster recovery limitations
- Preparing for disaster recovery
- Performing system-state recovery
- Recovering the Active Directory
- Performing bare-metal recovery
- Perform bare-metal recovery of Windows clusters
- Disaster recovery solution for Microsoft SQL application data
- Protecting Microsoft Distributed File System using BMR and SSR
- Performing application restores after bare-metal recovery
- File System Best Practices and Troubleshooting
- Glossary
PowerProtect Data Manager 19.14 File System User Guide
Add the custom WinPE image to a Windows Deployment Services server
You can choose to add the custom WinPE image to a Windows Deployment Services (WDS) server to enable the target host to boot over the network. The Microsoft TechNet website provides detailed steps to configure and use WDS.
About this task
NOTE:
Booting through WDS method from a WinPE image over the network and booting from an ISO image that is connected to the host are supported. The other network boot methods are unsupported.
Steps
- Configure the WDS server.
- Add the WinPE image to the boot menu.
- Ensure that PXE booting is enabled on the WDS target host.
- Boot the target host from the WinPE image over the network.
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please select whether the article was helpful or not.
Comments cannot contain these special characters: <>()\