- Notes, cautions, and warnings
- Preface
- Introduction
- Architecture
- Backup
- File system restore
- Disaster recovery
- Installation
- Preparing to install the Avamar client software
- System requirements
- Windows Server cluster requirements
- Windows Server 2019, 2016, or 2012 for SOFS or SMB cluster requirements
- Multi-homed cluster requirements
- VSS requirements
- Supported Windows features
- Hardware requirements
- Networking requirements
- Additional software requirements
- Unsupported configurations and features
- Preparing a Windows Server 2019, 2016, or 2012 for SOFS or SMB cluster
- Downloading the software
- Verifying the environment
- Installing the Avamar client software
- Installation road maps
- Stand-alone installation road map
- Installation road map for Windows Server clusters
- Installation road map for Windows Server active/active clusters
- Installation road map for Windows Server 2019, 2016, or 2012 clusters with SOFS or SMB
- Installation road map for Windows Server 2019, 2016, or 2012 active/active clusters with SOFS or SMB
- Installing the Avamar Client for Windows
- Registering the client
- Configuring the federated cluster client on Windows Server
- Configuring the proxy cluster client on Windows Server 2019, 2016, or 2012 for SOFS or SMB clusters
- Adding permissions for hidden file access in a cluster
- Adding permissions for non-administrator user access in a cluster
- Viewing the cluster client configuration
- Installation road maps
- Upgrading the Avamar client software
- Uninstalling the Avamar client software
- Preparing to install the Avamar client software
- Backup
- Performing on-demand backups
- Schedule backups using the AUI Policy wizard
- Monitor backups
- Cancel backups
- Enforcement of backups to Data Domain
- File System Restore
- Bare Metal Recovery
- Plug-in Options
- Command Line Interface
- Troubleshoot
- activation
- Active Directory
- administrator
- avagent
- Avamar Administrator
- Avamar Bare Metal Recovery Wizard
- Avamar client
- avtar
- backup
- backup policy
- bare metal recovery (BMR)
- browse
- client activation
- client agent
- client registration
- cluster
- Cluster Configuration Tool
- cluster shared volumes (CSV)
- clustered file server for general use
- critical disk
- Data Domain system
- database
- dataset
- Directory Services Restore Mode (DSRM)
- disaster recovery
- DNS
- domain
- federated cluster client
- file system
- group
- group policy
- LAN
- MCS
- metadata
- nonauthoritative restore
- noncritical disk
- plug-in
- plug-in options
- policy
- proxy cluster client
- proxy node
- redirected restore
- registration
- restore
- retention
- Scale-Out File Server (SOFS)
- schedule
- Server Core
- Server Message Block (SMB) 3.0 file shares
- shadow copy volume
- System State
- virtual hard disk (VHD) files
- virtual machine (VM)
- Volume Shadow Copy Service (VSS)
- VSS provider
- VSS requestor
- VSS writer
- Windows Deployment Services (WDS)
- WinPE ISO image
Dell EMC Avamar for Windows Servers 19.7 User Guide
(Optional) Adding the WinPE ISO boot image to a Windows Deployment Services server
About this task
You can add the WinPE ISO boot image to a Windows Deployment Services (WDS) server to enable a network boot of the target computer. The Microsoft TechNet website provides detailed steps to configure and use WDS.
NOTE WDS is described here as a known example of how to boot from an ISO boot image over a network. Other network boot technologies may also work.
Steps
- Configure the WDS server.
- Add the WinPE ISO boot image to the boot menu.
- Ensure that PXE booting is enabled on the WDS client.
- To use the image, perform a network boot of the WinPE ISO boot image, Windows System Recovery, on the WDS client.
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: <>()\