Unregister-NCache - PowerShell Cmdlet
This PowerShell Cmdlet is used to deactivate licenses for activated machines. By deactivating a license, you can free up existing licenses, which can then be used to activate other machines. This PowerShell Cmdlet supports both online and offline modes of deactivating a license.
Important
NCache OSS has different parameters in some Cmdlet instances. Please refer to the seperate Open Source PowerShell Reference to ensure intended working in this case.
Unregister-NCache [-Key] [-OfflineDeactivate] [-Server] [-Port] [-Credentials] [-NoLogo]
Examples of Unregister-NCache - PowerShell Cmdlet
- This PowerShell Cmdlet deactivates NCache on a local server.
Unregister-NCache -Key xxxxxxxx-xxxxxx-xxxxxxxx
- This command deactivates NCache on server 20.200.20.11.
Unregister-NCache -Key xxxxxxxx-xxxxxx-xxxxxxxx -Server 20.200.20.11
- This command deactivates NCache in the offline mode using the
OfflineDeactivate
parameter.
Unregister-NCache -Key xxxxxxxx-xxxxxx-xxxxxxxx -OfflineDeactivate
Properties
Note
The parameters with asterisk (*) on their names are the required parameters and the rest are optional.
Parameters | Data Types | Description | Default Value |
---|---|---|---|
-Key* |
<String> |
License key (obtained from Alachisoft on purchase of NCache) that will be used to deactivate your licenses. | - |
-OfflineDeactivate |
<SwitchParameter> |
This allows you to deactivate a server that has no internet connection. When this switch is used, the command generates a "Deactivation Request URL". Copy this URL to another computer with Internet access. Open that URL from that computer to complete the deactivation of licenses. | True |
-Server |
<String> |
Specifies the server name or IP where the NCache Service is running. | Local Machine |
-NoLogo |
<SwitchParameters> |
Suppresses display of the logo banner. | True |
-Port |
<Long> |
Specifies the port of the server. | 8250 |
-Credentials |
<pscredential> |
Specifies the user credentials required to authorize access for the specified operation. These credentials should belong to a user who has appropriate permissions at the node. | - |