This happens because (by default) the Proxmox VE install comes with the enterprise update repositories enabled, and you probably don’t have an Enterprise subscription. It’s a pretty easy fix, you just need to disable the Enterprise repositories, and enable the free (No subscription) repository.
Select the host you wish to change, Updates > Repositories > Locate the enterprise Repository and select it > Disable.
Here I have a second Enterprise repository so I’ve also disabled that > Add > Change the repository to ‘No Subscription‘ > Add.
This is what it should look like, Note: Green tick and ‘You get updates for Proxmox VE‘.
Now go to the updated tab > Refresh > Task should complete without error.
Repeat the process on your other Proxmox VE hosts.
Related Articles, References, Credits, or External Links
There was a time you had to go to VMware and download PowerCLI then install it, that’s no longer the case, any machine with a, (reasonably new) version of PowerShell can simply pull the commandlets down from a repository and you are ready to go.
Solution
Firstly if you have the ‘old version’ of PowerCLI you can uninstall it from Add/Remove programs (appwiz.exe).
Before installing, you need to be running Powershell version 5 or above, so issue the following command;
[box]
$psversiontable
[/box]
Below, you will see this is version 4, if yours is the same, you need to upgrade to version 5.
You can upgrade the PowerShell version by installing Windows Management Framework 5.1, like so;
Why AllowClobber? Well if you have any old commandlets hanging around, they will be updated and if you are installing on a Hyper-V server you can see some errors.
Related Articles, References, Credits, or External Links
When adding a ‘Backup Repository’ to Veeam you may see one of the following;
The file system on the specified volume does not support fast cloning. We recommend using ReFS volume formatted with 64 KB cluster size. Proceed anyway?
The specified ReFS volume is formatted with 4 KB cluster size. We recommend formatting the volume with 64 KB cluster size. Proceed anyway?
Solution
Without going into what ReFS is, think of it as the new NTFS. So that’s the format which you use when formatting the volume you want to use as a repository, the second error above will be seen if you did format the volume as ReFS but used the default 4 KB block size. This is what you need to do when creating the volume;
But there’s already data on the drive! Well tough, either accept and proceed, or move the data elsewhere and reformat. (At present there is no way to convert an NTFS volume to ReFS).
Related Articles, References, Credits, or External Links
I’ve just replaced my XBMCbuntu media PC (an Acer Revo 3700) with a newer machine, and I was rebuilding the old one for my neighbour. I’m not sure if he has a wired connection where his TV is so I wanted to use Network Manager to setup the wireless connection. But when I tried to add it, this happened;
XBMC 13.0 (Compiled May 4 2014)
Solution
1. To get round this you need to install the add-on from a .zip file, so download the following file and put it on a USB drive.
Having a button that you could upload patches from, that would crazy eh? Cheers Cisco! I deployed a CDA appliance recently, and it needs (eventually) to be able to talk to Cisco ISE so I knew it had to be up to patch 2. At time of writing we are at patch 4, so I thought I’d put them all on.
I don’t know if the patches are cumulative, and patch 3 looks a little smaller than patch 2 so I thought I would apply them all, in order to be on the safe side.
Solution
Before you start make sure your patches are downloaded and in the root of your FTP server (I use 3cDaemon).
In the process below I will install patch 4, the procedure is the same for all of the patches, the only difference is patch 1 does not automatically reboot the CDA when it is finished, all the others do.
1. Connect to the CDA either directly to the console or via SSH. Go to config mode and create a repository.
[box]
Petes-CDA/admin# conf t
Enter configuration commands, one per line. End with CNTL/Z.
Petes-CDA/admin(config)# repository CDAPatch4
Petes-CDA/admin(config-Repository)# url disk://CDAPatch4
Petes-CDA/admin(config-Repository)# end
Petes-CDA/admin#
[/box]
2. Make a directory that the repository will use.
[box]
Petes-CDA/admin# mkdir disk://CDAPatch4
Petes-CDA/admin# dir
Directory of disk:/
4096 Jan 19 2015 13:00:07 CDAPatch4/
16384 Dec 08 2014 14:15:07 lost+found/
Usage for disk: filesystem
172765184 bytes total used
14275043328 bytes free
15234142208 bytes available
[/box]
3. Copy your patch over from your FTP server. (You wont get any response to say it worked!)
Petes-CDA/admin# dir recursive
Directory of disk:/
4096 Jan 19 2015 13:02:11 CDAPatch4/
16384 Dec 08 2014 14:15:07 lost+found/
Directory of disk:/CDAPatch4
3974740 Jan 19 2015 13:02:11 cda-patchbundle_1.0.0.011-4.i386.gz
Directory of disk:/lost+found
No files in directory
Usage for disk: filesystem
176746496 bytes total used
14271062016 bytes free
15234142208 bytes available
[/box]
5. Install the patch.
[box]
Petes-CDA/admin# patch install cda-patchbundle_1.0.0.011-4.i386.gz CDAPatch4
Save the current ADE-OS running configuration? (yes/no) [yes] ? yes
Generating configuration...
Saved the ADE-OS running configuration to startup successfully
Initiating Application Patch installation...
% This application Install or Upgrade requires reboot, rebooting now...
Broadcast message from root (pts/0) (Mon Jan 19 13:52:39 2015):
The system is going down for reboot NOW!
Patch successfully installed
Petes-CDA/admin#
[/box]
6. After the CDA has rebooted, check the patch version(s) installed.
[box]
Petes-CDA/admin# show ver
Cisco Application Deployment Engine OS Release:
ADE-OS Build Version:
ADE-OS System Architecture: i386
Copyright (c) 2005-2011 by Cisco Systems, Inc.
All rights reserved.
Hostname: Petes-CDA
Version information of installed applications
---------------------------------------------
Cisco Context Directory Agent
---------------------------------------------
Version : 1.0.0.011
Build Date : Tue May 8 15:34:26 2012
Install Date : Mon Dec 8 14:24:18 2014
Cisco Context Directory Agent Patch
---------------------------------------------
Version : 1
Build number : NA
Install Date : Mon Jan 19 13:22:19 2015
Cisco Context Directory Agent Patch
---------------------------------------------
Version : 2
Build number : NA
Install Date : Mon Jan 19 13:34:54 2015
Cisco Context Directory Agent Patch
---------------------------------------------
Version : 3
Build number : NA
Install Date : Mon Jan 19 13:44:30 2015
Cisco Context Directory Agent Patch
---------------------------------------------
Version : 4
Build number : NA
Install Date : Mon Jan 19 13:52:36 2015
Petes-CDA/admin#
[/box]
Related Articles, References, Credits, or External Links
Just as I was hunting around for an NFR version of Cisco ISE 1.3, they released 1.4. I wasn’t sure if I could upgrade my NFR version without breaking it so I thought I would ‘have a go’.
Solution
If you read the documentation for the upgrade of 1.2 to 1.4, I suggest you skip straight to the tasks to do AFTER upgrade, as it has a habit of resetting things back to default, best to make sure you know how everything is setup that might break before you start.
This upgrade took me a long time! The best part of an afternoon!
1. Before we do anything let’s take a snapshot, just in case it all goes to hell in a hand cart.
2. Gotcha! The upgrade fails if you have any expired certificates, even disabling them wont help, you need to delete all expired root certs before you start.
3. Copy the upgrade file from an FTP server to the ISE device, it wont show you any progress bar, go and get a coffee, if it does not error it’s probably copying over OK :).
4. When you get the prompt back you can check it’s there with a ‘dir’ command.
5. Before you can upgrade you need to create a repository for the upgrade;
[box]
ISE-01/admin# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
ISE-01(config)# repository upgrade
ISE-01(config-Repository)# url disk:
% Warning: Repositories configured from CLI cannot be used from the ISE web UI and are not replicated to other ISE nodes.
If this repository is not created in the ISE web UI, it will be deleted when ISE services restart.
ISE-01(config-Repository)# exit
ISE-01(config)# exit
[/box]
6. Then you need to ‘prepare’ for the upgrade.
[box]
ISE-01/admin# application upgrade prepare ise-upgradebundle-1.2.x-to-1.4.0.253.x86_64.tar.gz upgrade
Getting bundle to local machine...
md5: 35a159416afd0900c9da7b3dc6c72043
sha256: e3358ca424d977af67f8bb2bb3574b3e559ce9578d2f36c44cd8ba9e6dddfefd
% Please confirm above crypto hash matches what is posted on Cisco download site.
% Continue? Y/N [Y] ? Y
[/box]
7. Start the upgrade, this takes ages, go and have at least three coffees.
