The file can contain DHCPv4 and DHCPv6 configuration data. This example imports the configuration and lease data in the specified file onto the DHCP server service that runs on the computer named. Example 2: Import configuration and lease data PS C:\> Import-DhcpServer -ComputerName "" -File "C:\exports\dhcpexport.xml" -BackupPath "C:\dhcpbackup\" -Leases This example imports the configuration data in the specified file onto the DHCP server service that runs on the computer named. Examples Example 1: Import configuration data PS C:\> Import-DhcpServer -ComputerName "" -File "C:\exports\dhcpexport.xml" -BackupPath "C:\dhcpbackup\" If the file specified contains any scope information, the same information is not imported on the destination DHCP server service. If you specify the ServerConfigOnly parameter, only the server level configuration is imported on the destination DHCP server service. If this parameter is not specified and the scope being imported exists on the destination DHCP server service, a warning message is displayed and the import proceeds to process the next scope being imported. If you specify the ScopeOverWrite parameter and the scope being imported exists on the destination server, the scope on the target DHCP server service is overwritten. If you specify the Leases parameter, the lease data in the specified file is imported in addition to configuration data. If you specify neither the ScopeId nor the Prefix parameter, all of the configurations that is contained in the file, and optionally any lease data, is imported. If you specify either the ScopeId or the Prefix parameter, or both, only the specified scopes or prefixes are imported. The Import-DhcpServer cmdlet imports the Dynamic Host Configuration Protocol (DHCP) server service configuration, and optionally lease data, from the specified file. In this article Syntax Import-Dhcp Server This option is especially recommended if there are important sync tasks.Imports the Dynamic Host Configuration Protocol (DHCP) server service configuration, and optionally lease data, from a file. The configuration file covers all backup and sync tasks created under the " Home" tab. With this option, you can export the configuration file (ambackup.xml) to another location. Once the configuration file is imported, all backup and sync tasks will be recovered and you can check the backup and sync tasks are listed under the " Home" tab. (To recover both backup and sync tasks.)Īs described above, if there is a backup image, you can simply recover the backup task by the option " Import Image.īesides, if there is a configuration file, you can also click the " Browse" button to import the configuration file (ambackup.xml) you previously exported to another location. (To export and recover both backup/sync tasks.)ġ. To export and import configuration files to recover backup/sync tasks. And then, the backup task will be recovered and you can check the backup task is listed under the " Home" tab. If there is a backup image, you can click the " Browse" button and select backup image files (*.adi, *.afi) on the backup destination location and click " OK". To import Image files(*.adi, *.afi) to recover backup tasks. If the task configuration is not exported, it is unable to recover sync tasks.Ī. But you can only recover sync tasks by the option " Import Task". Tip: To recover backup tasks, you can use both " Import Image" and " Import Task". You can also use the feature to import backup/sync configurations to recover backup/sync tasks.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |