I recently had an issue with only the default printer being mapped over from the local Windows 7 PC to the View Client session. It did not make any sense to me. I had 10 printers mapped yet only 1 was showing up. It turns out its a limitation of Windows 7. If all the printers are using the same Driver and Port then you will only see the default printer under the Devices and Printers page. If you right click that printer it will list all the printers you have mapped. When you try to print something it will also list all your printers.
Nutanix recently released the 5.0 code, and it has a lot of new really nice features. In a future post I plan on going over some of the features, and detail why they are so important.
Before you start upgrading all of your Nutanix host you should first upgrade Prism Central to 5.0 This server gives you an overview of all your Nutanix clusters and some management capabilities. I am still fairly new to Nutanix so I was not sure how to upgrade Prism Central. Usually you can upgrade from within the Nutanix console, but with this being a brand new release you had to download it directly from the website. Sometime soon in the future it will be a part of the automatic upgrade within the Console.
At first I was a little confused about how to upgrade. You would think there would be a separate upgrade for Prism Central since it was originally a separate install. Instead the update is included in the AOS 5 download. Download the complete AOS 5.0 and also download the Upgrade Metadate File.
Once you have that downloaded everything login to Prism Central. Next click the gear icon and then click upload the Prism Central Binary. Now point it to the AOS 5.0 download and the metadate file. Click upgrade and soon you will be running Prism Central 5.0.
I have an application that writes to its Device then inside the array that Device is mirrored to an BCV. When it is time for a backup a script will kick off that will break the mirror.
Then the backup application reads the data from that mirrored BCV. Sometimes things will go wrong and that script will never resync the mirror. That then results in broken backups. To fix this I had to go into the VMAX3 SYMCLI and run these few commands.
- symdev -lock list
- symdev release “Then confirm yes for each lock”
Looks really simple doesn’t it? It took me a while to figure out. It is not often I have to touch the VMAX and when I do it is usually with the GUI. I also have a thick book of all the long complicated SYMCLI commands. Thankfully through trial and error it ended up just being two simple commands.