Search For:
- Home
- Search For:
Uninstall Azure ad PowerShell Module - Steps to do it
This article covers how to uninstall the #Azure #PowerShell module and AzureRM module from MSI and PowerShellGet.
To uninstall all official PowerCLI modules except VMware.PowerCLI, run the following command:
(Get-Module VMware.PowerCLI -ListAvailable).RequiredModules | Uninstall-Module -Force
When you want to uninstall the program, you can go to the Programs and Features to uninstall it.
So when you want to uninstall Windows Azure SDK and Windows Azure Tools for Microsoft Visual Studio (the first solution is to uninstall it via Programs and Features.
How do I uninstall Windows PowerShell?
Uninstall PowerShell from Start Menu.
1. You can click Start menu at the bottom-left, type PowerShell in the search box, and you will see Windows PowerShell app.
2. Right-click Windows PowerShell app, and select Uninstall, or expand the menu in the right to select Uninstall to remove Windows PowerShell exe from Windows 10.
To Install VMware PowerCLI Module From PC With Internet Connection:
1. From a computer with an internet connection open powershell (preferrably as an administrator)
2. Find-Module -Name VMware.PowerCLI.
3. Install-Module -Name VMware.PowerCLI -Scope CurrentUser.
4. Get-Command -Module *VMWare*
To use Azure PowerShell in PowerShell 5.1 on Windows:
1. Update to Windows PowerShell 5.1. If you're on Windows 10 version 1607 or higher, you already have PowerShell 5.1 installed.
2. Install . NET Framework 4.7.
3. Make sure you have the latest version of PowerShellGet. Run Install-Module -Name PowerShellGet -Force .
500 oops vsftpd refusing to run with writable root inside chroot - Fix it now
This article covers fixes to '500 oops vsftpd refusing to run with writable root inside chroot()' error which occurs while connecting to vsftpd if it is a newly installed vsftpd or if it is upgraded.
To fix this error, you need to upgrade your Server by adding the jessie repository to my Debian installation and upgrade it so:
echo "deb http://ftp.us.debian.org/debian jessie main contrib non-free" >> /etc/apt/sources.list
aptitude update
aptitude upgrade vsftpd
echo "allow_writeable_chroot=YES" >> /etc/vsftpd.conf
service vsftpd restart
Also, add the value:
seccomp_sandbox=NO
to the configuration and restart the service with service vsftpd restart:
Then "allow_writeable_chroot=YES"
The URI Failed to Connect to the Hypervisor - Fix it now
This article covers methods to resolve hypervisor error. The error message is misleading about the actual cause. This error can be caused by a variety of factors, such as an incorrectly specified URI, or a connection that is not configured.
To fix THE URI FAILED TO CONNECT TO THE HYPERVISOR:
1. Incorrectly specified URI
When specifying qemu://system or qemu://session as a connection URI, virsh attempts to connect to host names system or session respectively. This is because virsh recognizes the text after the second forward slash as the host.
Use three forward slashes to connect to the local host. For example, specifying qemu:///system instructs virsh connect to the system instance of libvirtd on the local host.
When a host name is specified, the QEMU transport defaults to TLS. This results in certificates.
2. Connection is not configured
The URI is correct (for example, qemu[+tls]://server/system) but the certificates are not set up properly on your machine. For information on configuring TLS, see Setting up libvirt for TLS available from the libvirt website.
mdadm failed to run_array - Fix this Linux Software RAID error now
This article covers how to resolve the RAID #error.
This error indicate that the RAID metadata is lost or is no longer consistent.
However, sometime following command can fix the issue if other two driver are known to be good.
/proc/mdstat file will provide RAID status and make sure RAID is active.
Type the following command at a shell prompt to fix this issue:
mdadm -A /dev/md0 -f --update=summaries /dev/sda1 /dev/sdb1
FreeBSD Apache Jail Connection refused connect to listener failed
This article covers how to fix 'FreeBSD Apache Jail: Connection refused' issue for our customers.
While running Apache 2 server under FreeBSD jail, you may see a warning error messages in /var/log/httpd-error.log as follows:
[warn] (61)Connection refused: connect to listener on 0.0.0.0:80
To resolve this FreeBSD Apache Jail error:
1. You need to always set your actual, real IP. Open httpd.conf
# vi /usr/local/etc/apache22/httpd.conf
2. Find out Listen directive:
#Listen 12.34.56.78:80
Listen directive allows you to bind Apache to specific IP addresses and/or ports, instead of the default.
Change this to Listen on specific IP addresses as shown below to prevent Apache from glomming onto all bound IP addresses i.e. 0.0.0.0 which is not available in jail
3. Save and close the file. Restart apache:
# /usr/local/etc/rc.d/apache22 restart
No guest machines present libvirtd - Fix it now
This article covers how to troubleshoot and fix No guest machines present libvirtd for our customers.
The virsh program is the main interface for managing virsh guest domains. The program can be used to create, pause, and shutdown domains.
It can also be used to list current domains. Libvirt is a C toolkit to interact with the virtualization capabilities of recent versions of Linux (and other OSes).
The libvirt daemon is successfully started, but no guest virtual machines appear to be present.
There are various possible causes of this problem.
Performing these tests will help to determine the cause of this situation:
1. Verify KVM kernel modules
Verify that KVM kernel modules are inserted in the kernel:
$ lsmod | grep kvm
If you are using an AMD machine, verify the kvm_amd kernel modules are inserted in the kernel instead, using the similar command lsmod | grep kvm_amd in the root shell.
If the modules are not present, insert them using the modprobe <modulename> command.
Note: Although it is uncommon, KVM virtualization support may be compiled into the kernel. In this case, modules are not needed.
2. Verify virtualization extensions
Verify that virtualization extensions are supported and enabled on the host:
# egrep "(vmx|svm)" /proc/cpuinfo
Enable virtualization extensions in your hardware's firmware configuration within the BIOS setup.
3. Verify client URI configuration
Verify that the URI of the client is configured as desired:
# virsh uri
How to fix No guest machines present #libvirtd #error:
After performing these tests, use the following command to view a list of guest virtual machines:
# virsh list --all
