| description | external help file | Module Name | ms.date | online version | schema | title |
|---|---|---|---|---|---|---|
Use this topic to help manage Windows and Windows Server technologies with Windows PowerShell. |
Microsoft.Licensing.VolumeActivation.Powershell.dll-Help.xml |
VAMT |
12/20/2016 |
2.0.0 |
Import-VamtData |
Imports the data from a specified .cilx or .cil file into a VAMT database.
Import-VamtData -Products <Product[]> [-DbConnectionString <String>] [-DbCommandTimeout <Int32>]
[<CommonParameters>]
Import-VamtData -InputFile <String> [-DbConnectionString <String>] [-DbCommandTimeout <Int32>]
[<CommonParameters>]
The Import-VamtData cmdlet imports data from a specified .cilx or .cil file into a dep_nextref_vamt database. You can merge data from a previous version of dep_nextref_vamt into your database by exporting the data in the previous version to a .cil file and then importing the .cil file into the dep_nextref_vamt database. You can import data from a .cilx file to recover data from a backup file.
PS C:\> Import-VamtData -InputFile ".\vamtdata.cilx"
This command imports data from the specified file.
PS C:\> $ProductInfo = Get-VamtProduct
PS C:\> $UpdatedProductInfo = Get-VamtConfirmationId -Products $productinfo
PS C:\> Import-VamtData -Products $UpdatedProductInfo
This command gets a product object, acquires the confirmation IDs for the products, and then imports the data to the database. Just acquiring the CIDs does not mean that the data is in the database. The data must be imported as shown in this example.
Indicates how long dep_nextref_vamt waits for a response from the database before timing out. The default value is 30 seconds.
Type: Int32
Parameter Sets: (All)
Aliases:
Required: False
Position: Named
Default value: None
Accept pipeline input: True (ByPropertyName)
Accept wildcard characters: FalseSpecifies the database that the data from the .cilx file or .cil file is imported into. If no database connection string is provided, dep_nextref_vamt attempts to use the database that the dep_nextref_vamt user console used on the local computer. If dep_nextref_vamt does not find a database, it returns an error. You can find the connection string in the dep_nextref_vamt UI in the Preferences dialog box. On the menu bar, click View, and then click Preferences to open the Volume Activation Management Tool Preferences dialog box. The connection string is in the Database Settings section under Current connection string.
Type: String
Parameter Sets: (All)
Aliases:
Required: False
Position: Named
Default value: None
Accept pipeline input: True (ByPropertyName)
Accept wildcard characters: FalseSpecifies the name of the file that contains the data to import into the dep_nextref_vamt database. You cannot use the InputFile parameter together with the Products parameter.
Type: String
Parameter Sets: File
Aliases:
Required: True
Position: Named
Default value: None
Accept pipeline input: True (ByPropertyName, ByValue)
Accept wildcard characters: FalseSpecifies the product information to import. If the Products parameter is not included, all product information in the .cilx or .cil file is imported into the dep_nextref_vamt database. You cannot use the Products parameter together with the InputFile parameter.
Type: Product[]
Parameter Sets: Products
Aliases:
Required: True
Position: Named
Default value: None
Accept pipeline input: True (ByPropertyName, ByValue)
Accept wildcard characters: FalseThis cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable, -InformationAction, -InformationVariable, -OutVariable, -OutBuffer, -PipelineVariable, -Verbose, -WarningAction, and -WarningVariable. For more information, see about_CommonParameters.