For the purposes of this article we will use the Azure AD Portal, not the Entra ID portal

Requirements

In order to make this work there are a few requirements/prerequisites needed so you can successfully use Azure AD as the Identity Provider. Let’s touch on those requirements now.

• VMware Administrator Role
• VMware vCenter 8.0 U2 or later
• VMware Identity Services from Azure Enterprise App Gallery
• Azure Application Administrator or Global Administrator Role
• Azure App Registration with OpenID Connect (OIDC) scope
• Publicly accessible vCenter endpoint (We will use an Azure App Proxy for this)
• A group or users to sync to vCenter

Create the Azure AD OIDC App Registration

As mentioned in the prerequisites, you will need to create an app registration in Azure AD so you can use this as the authentication endpoint. This app will need to have the openid API permission so let’s walk through setting that up now.
 

Within Azure AD:

• Navigate to App Registration → New Registration
• Direct Link: https://portal.azure.com/#view/Microsoft_AAD_RegisteredApps/CreateApplicationBlade/quickStartType~/null/isMSAApp~/false
• Name the app: vCenter 8 OIDC
• Leave the Organizational directory to Single Tenant
• Leave the Redirect URI blank for now
• Click Register to create the app

Next we’ll want to add the API permissions so we can tie this Azure app to vCenter.
Within the vCenter 8 OIDC App:

• Navigate to API Permissions
• Select Add a permission
• Choose Microsoft Graph → Delegated → enable the 4 listed below
• Grant Consent for good measure

Leave this tab open for now, we will come back to it later.

vCenter Identity Source Configuration

We’re one step closer now that we have have the OIDC app created. Next we need to configure vCenter itself so we can change the Identity Provider from the local embedded provider to Azure AD.
 

Within the vCenter Server:

• Login to vCenter 8 using administrator@vsphere.local since we won’t have any other providers available
• Navigate to Administration → single sign on → configuration → Identity Provider → Identity Sources
• Click Change Provider → Azure AD

• Next, click run prechecks
• Check the box to confirm
• Click Next

• Under Directory Name enter Azure AD
• Enter the domain(s) and click the “+” to add it
• If you have multiple UPN suffixes, add them domain names here.

• Set the token lifetime

Earlier I mentioned to keep the tabs open because we’re going to need them later. Now is that time where we are going to use need them.

• Copy the redirect URI from the vCenter wizard
• Navigate back to the vCenter 8 OIDC app → Authentication tab
• Add a platform → Select Web
• Paste the Redirect URI into the redirect URI in the Azure app
• Click configure

• Copy the AppId (ClientId) from the Azure OIDC app and paste it to the client identifier in vCenter

• Create a secret and paste it in vCenter

• In the overview page of the OIDC App
• Click on EndPoints
• Copy the OpenID Connect metadata document URL and paste it in vCenter

• Review the configuration and proceed

Setting up an Azure App Proxy

One of the requirements to use Azure AD as the Identity source is to make sure we are able to publicly access vCenter from Azure. I am NOT a fan of exposing your network and poking a hole in your firewall so we’ll use the next best thing. In order to satisfy this requirement, we will use an Azure app proxy which will publish an endpoint that sits behind Azure.
 

The idea is that we will use the app proxy’s public endpoint to route to the internal endpoint so Azure is able to talk to vCenter on-premises. An app proxy requires you to install the connector service on an on-premises server that has line of sight to your vCenter server. I would suggest you have the app proxy agent installed on 2 machines so you can have some sort of redundancy when you need to do maintenance on the servers.
 

Let’s walk through the setup now.
Within Azure AD, open a NEW tab:

• Navigate to Azure AD → Application Proxy
• Direct Link: https://portal.azure.com/#view/Microsoft_AAD_IAM/ActiveDirectoryMenuBlade/~/AppProxy
• Download and install the connector service

The install is pretty straight forward so get it installed on 2 machines and go back into the Azure portal.
 

Once the connector is installed, you should see the hostname and public IP show up in the Azure proxy section. From here, click on configure an app.

 

Next you should be taken to the app proxy configuration settings.

• Copy the vCenter Tenant URL and paste it into the app proxy Internal URL field
• Ensure the dropdown is set to https://
• Enter in a name for your app proxy (vcenter8appproxy or something similar is fine)
• Set the domain drop to which ever makes sense for you. Leaving the default is fine
• Set the pre authentication method to passthrough
• Set the connector group accordingly. If you have multiple connector groups, make sure it is set on the App proxy blade AND the Enterprise app settings

Trusting vCenter Root Certificate on the Connector Service Machine

If you’re using a publicly trusted certificate for vCenter than you can skip this part. However, if you’re using the default certificate that comes pre-loaded with vCenter you will need to do this. An easy way to find out, is go to your vCenter URL and if you’re getting Your connection is not private then you’re not using a trusted cert.
 

Let’s go back to the machine(s) that you installed the service connector on because that’s where we will need to have the cert be trusted. These steps need to be done on EACH server that has the connector agent.

On a NEW tab:

• Navigate to https://<your vcenter url>/certs/download.zip
• Right click and save as a zip file
• Open the zip file → certs → win
• Double click on the crt file to install it on the local machine
• Install it under the local machine context
• Place it under the Trusted Root Certification Authorities

• You can verify this by opening mmc.exe on the service connector machine
• Certificates → Local machine → Trusted root certification authorities
• Seeing the CA cert there

Create the VMware Identity Service App from the Gallery

Next on the list, we’ll need to create the VMware Identity Service app from the Azure App gallery to allow us to use SCIM provisioning.

Within Azure AD on a NEW tab:

• Navigate to Enterprise Application → New Application
• Direct Link: https://portal.azure.com/#view/Microsoft_AAD_IAM/AppGalleryBladeV2
• Search for “VMware Identity” to install the VMware Identity Service
• Name it vCenter 8 SCIM Provisioning

Setup Provisioning to Sync Users to vCenter

Here is where the rubber meets the road and we can finally start syncing users from Azure AD to vCenter.

• Navigate to the Enterprise Application → vCenter 8 SCIM Provisioning → Provisioning

• Click on Provisioning and set the mode to automatic
• Copy the External URL from the Azure app proxy and paste it here under Tenant URL

• Create a secret from vCenter 8 configuration and paste it here under Secret Token
• Click Test Connection. If everything is configured correctly, it should work.
• Save the configuration

Once the setting is saved, refresh the tab so the other settings can kick in. Another option is to close out of the blade and go back into the provisioning section.

• From here within the provisioning blade → Users and groups
• Set the users and/or groups you want to sync to vCenter

Once we’re happy with the users and/or groups we want to add, we’ll need to start the provisioning cycle so the objects can sync to vCenter 8.

• Go to the overview page
• Click on start provisioning to start the sync engine

Integrating Permissions for VMware vCenter

At this point you should now have your users and/or groups syncing to VMware vCenter 8. The last step here is to actually add these users to the permissions that you want to grant. VMware has these steps pretty well documented so it’s a quick search away. However, we’ll do a quick overview to ensure we add our users to the admin role so we can manage vCenter and all its resources.
 

Within vCenter 8 UI:

• Navigate to Administration → single sign on → Users and Groups → Groups → Administrators

• Click Edit to modify the members
• Next to Add a member, click the drop down to add your domain
• Search for the group that is synced from Azure AD provisioning
• Click Save to save the keep the settings

Conclusion

So there you have it, a full step by step guide on how to setup VMware vCenter SSO Integration with Azure AD. This method is especially helpful because this allows you to have vCenter in scope of conditional access policies and phishing resistance MFA methods such as Windows Hello for Business and Fido 2 security keys.

The post VMware vCenter SSO Integration with Azure AD appeared first on the Sysadmin Channel.

What if you wanted to check 1000? 10,000? Doing this manually is not going to scale very well so today we’re going to share how to get ESXi Server uptime using Powershell and PowerCLI.

Requirements

In order to make this work, there are a couple of requirements needed so let’s list them out here.
 

• PowerCLI module
• Connection to vCenter or ESXi host

Get ESXi Server Uptime Using Powershell and PowerCLI

Ideally, if you want to get the ESXi uptime status for more than 1 host, you’ll want to connect to a vCenter server. However, if you’re only checking 1 host, this script will work just fine.

With that said, let’s get to the script.

Function Get-EsxiUptime {
<#
.SYNOPSIS
    This script will get the current uptime for VMware ESXi Hosts

.NOTES
    Name: Get-EsxiUptime
    Author: theSysadminChannel
    Version: 1.0
    DateCreated: 2021-Aug-21

.LINK
    https://thesysadminchannel.com/get-esxi-server-uptime-using-powershell-and-powercli/ -
#>

    [CmdletBinding()]
    param(
        [Parameter(
            Mandatory = $false,
            ValueFromPipeline = $true,
            ValueFromPipelineByPropertyName = $true,
            Position = 0
        )]
        [Alias('Server', 'EsxiHost')]
        [string[]]    $VMHost
    )

    BEGIN {
        if (-not ($Global:DefaultVIServer)) {
            Write-Error "Unable to continue.  Please connect to a vCenter Server." -ErrorAction Stop
        }
    }

    PROCESS {
        foreach ($EsxiServer in $VMHost) {
            try {
                $Server = Get-VMHost $EsxiServer -ErrorAction Stop
                if ($Server.PowerState -eq 'PoweredOn') {
                    $LastBoot = $Server.ExtensionData.Summary.Runtime.BootTime.ToLocalTime()
                    $Uptime = (Get-Date) - $LastBoot

                    [PSCustomObject]@{
                        VMHost   = $Server.Name
                        LastBoot = $LastBoot
                        UpTime   = ([String]$Uptime.Days + " Days " + $Uptime.Hours + " Hours " + $Uptime.Minutes + " Minutes")
                        ConnectionState = $Server.ConnectionState
                    }
                } else {
                    [PSCustomObject]@{
                        VMHost   = $Server.Name
                        LastBoot = 'Unknown'
                        UpTime   = 'Unknown'
                        ConnectionState = $Server.ConnectionState
                    }
                }

            } catch {
                Write-Error $_.Exception.Message

            }
        }
    }

    END {}

}

Script Parameters

    -VMHost

DataType: string/array
Alias: Server, EsxiHost
Description: Specify the ESXi server you would like to query.
 

Example 1 – Specify a list of servers separated by a comma

PS C:\> Get-EsxiUptime -VMHost esxi1.ad.thesysadminchannel.com, esxi2.ad.thesysadminchannel.com

Example 2 – Using the pipeline

PS C:\> Get-VMHost esxi* | Get-EsxiUptime

Conclusion

I suppose it would have helped if I had ESXi1 host powered on, but I thought it would be good to show what the expected output is for a machine that’s offline. Hopefully this script to get Esxi Uptime using Powershell and PowerCLI was helpful for you to see how quickly and easily you can scale this across multiple servers. I personally like how it receives pipeline input so you can use the native Get-VMHost command that you’re probably already familiar with.
 

If you liked this script, be sure to check out a similar script to Get Reboot History Using Powershell. It can definitely come in handy for Windows environments.

The post Get ESXi Server Uptime Using Powershell and PowerCLI appeared first on the Sysadmin Channel.

Screenshot for GUI method

As you can see from my screenshot above, I’m up to date on my windows 10 machine. However, as I mentioned already this method is not scalable at all so this is why I prefer the Powershell PowerCLI method.

Understanding The VM Properties in PowerCLI

I should probably start off by explaining the properties that are available with the Get-VM cmdlet as this will lay down the foundation for what we’re trying to do. Anytime you run the command Get-VM -Name MyComputer it will output that VM along with the default properties of Name, PowerState, NumCPUs and MemoryGB.

There are more properties available but just not available from the default output. Thus we will need to pipe it to FL (or Format-List). That would look like this. Get-VM -Name PAC-WIN1001| fl

 
What I prefer to use when checking what’s available is setting the output into a variable and quickly finding those properties. This way we can use the $VM.Property1.property2 etc..

In our case we’re going to be drilling down to the ExtensionData -> Guest properties and there we will find our vmtools information.

Use PowerCLI To Check VMware Tools Status – Powershell Script

Script Requirements

• Must have the PowerCLI module installed
• Must be connected to vCenter server (or individual host) via PowerCLI

Parameters

    -Name

Description: Enter the virtual machine name that’s listed in vcenter

    -InputObject

Description: Allows pipeline input through the Get-VM cmdlet.

Examples

Example 1:
Get-VMToolsStatus -Name VM1, VM2, VM3
 
Example 2:
Get-VM -Name VM1, VM2, VM3 | Get-VMToolsStatus

This script also supports pipeline input

Powershell PowerCLI Script

Function Get-VMToolsStatus {
<#
.SYNOPSIS
    This will check the status of the VMware vmtools status.
    Properties include Name, Status, UpgradeStatus and Version

.NOTES
    Name: Get-VMToolsStatus
    Author: theSysadminChannel
    Version: 1.0
    DateCreated: 2020-Sep-1

.LINK
    https://thesysadminchannel.com/powercli-check-vmware-tools-status/ -

.EXAMPLE
    Please refer to the -Online version
    help Get-VMToolsStatus -Online

#>

    [CmdletBinding()]
    param(
        [Parameter(
            Position=0,
            ParameterSetName="NonPipeline"
        )]
        [Alias("VM", "ComputerName", "VMName")]
        [string[]]  $Name,


        [Parameter(
            Position=1,
            ValueFromPipeline=$true,
            ValueFromPipelineByPropertyName=$true,
            ParameterSetName="Pipeline"
            )]
        [PSObject[]]  $InputObject
    )

    BEGIN {
        if (-not $Global:DefaultVIServer) {
            Write-Error "Unable to continue.  Please connect to a vCenter Server." -ErrorAction Stop
        }

        #Verifying the object is a VM
        if ($PSBoundParameters.ContainsKey("Name")) {
            $InputObject = Get-VM $Name
        }

        $i = 1
        $Count = $InputObject.Count
    }

    PROCESS {
        if (($null -eq $InputObject.VMHost) -and ($null -eq $InputObject.MemoryGB)) {
            Write-Error "Invalid data type. A virtual machine object was not found" -ErrorAction Stop
        }

        foreach ($Object in $InputObject) {
            try {
                [PSCustomObject]@{
                    Name = $Object.name
                    Status = $Object.ExtensionData.Guest.ToolsStatus
                    UpgradeStatus = $Object.ExtensionData.Guest.ToolsVersionStatus2
                    Version = $Object.ExtensionData.Guest.ToolsVersion
                }
            } catch {
                Write-Error $_.Exception.Message

            } finally {
                if ($PSBoundParameters.ContainsKey("Name")) {
                    $PercentComplete = ($i/$Count).ToString("P")
                    Write-Progress -Activity "Processing VM: $($Object.Name)" -Status "$i/$count : $PercentComplete Complete" -PercentComplete $PercentComplete.Replace("%","")
                    $i++
                } else {
                    Write-Progress -Activity "Processing VM: $($Object.Name)" -Status "Completed: $i"
                    $i++
                }
            }
        }
    }

    END {}
}

 
Hopefully you found some value from this post and can now use this script in your environment. It’s always a good idea to do a basic audit to see what’s not up to standard. Speaking of audit, I would also suggest you take a look at the VMware VM Information Script which will give you specific details on host, cluster, datacenter, datastore, network, IP address etc.. It’s actually pretty neat and yours for the taking.

If you’re more into video learning, be sure to check out our Youtube Channel for sysadmin video content.

The post Use PowerCLI To Check VMware Tools Status appeared first on the Sysadmin Channel.

Get VMInformation Using Powershell and PowerCLI

Function Get-VMInformation {
<#
.SYNOPSIS
    Get information from a VM object. Properties inlcude Name, PowerState, vCenterServer, Datacenter, Cluster, VMHost, Datastore, Folder, GuestOS, NetworkName, IPAddress, MacAddress, VMTools


.NOTES   
    Name: Get-VMInformation
    Author: theSysadminChannel
    Version: 1.0
    DateCreated: 2019-Apr-29


.EXAMPLE
    For updated help and examples refer to -Online version.


.LINK
    https://thesysadminchannel.com/get-vminformation-using-powershell-and-powercli -
    
#>

    [CmdletBinding()]

    param(
        [Parameter(
            Position=0,
            ParameterSetName="NonPipeline"
        )]
        [Alias("VM")]
        [string[]]  $Name,


        [Parameter(
            Position=1,
            ValueFromPipeline=$true,
            ValueFromPipelineByPropertyName=$true,
            ParameterSetName="Pipeline"
            )]
        [PSObject[]]  $InputObject

    )


    BEGIN {
        if (-not $Global:DefaultVIServer) {
            Write-Error "Unable to continue.  Please connect to a vCenter Server." -ErrorAction Stop
        }

        #Verifying the object is a VM
        if ($PSBoundParameters.ContainsKey("Name")) {
            $InputObject = Get-VM $Name
        }

        $i = 1
        $Count = $InputObject.Count
    }

    PROCESS {
        if (($null -eq $InputObject.VMHost) -and ($null -eq $InputObject.MemoryGB)) {
            Write-Error "Invalid data type. A virtual machine object was not found" -ErrorAction Stop
        }

        foreach ($Object in $InputObject) {
            try {
                $vCenter = $Object.Uid -replace ".+@"; $vCenter = $vCenter -replace ":.+"
                [PSCustomObject]@{
                    Name        = $Object.Name
                    PowerState  = $Object.PowerState
                    vCenter     = $vCenter
                    Datacenter  = $Object.VMHost | Get-Datacenter | select -ExpandProperty Name
                    Cluster     = $Object.VMhost | Get-Cluster | select -ExpandProperty Name
                    VMHost      = $Object.VMhost
                    Datastore   = ($Object | Get-Datastore | select -ExpandProperty Name) -join ', '
                    FolderName  = $Object.Folder
                    GuestOS     = $Object.ExtensionData.Config.GuestFullName
                    NetworkName = ($Object | Get-NetworkAdapter | select -ExpandProperty NetworkName) -join ', '
                    IPAddress   = ($Object.ExtensionData.Summary.Guest.IPAddress) -join ', '
                    MacAddress  = ($Object | Get-NetworkAdapter | select -ExpandProperty MacAddress) -join ', '
                    VMTools     = $Object.ExtensionData.Guest.ToolsVersionStatus2
                }

            } catch {
                Write-Error $_.Exception.Message

            } finally {
                if ($PSBoundParameters.ContainsKey("Name")) {
                    $PercentComplete = ($i/$Count).ToString("P")
                    Write-Progress -Activity "Processing VM: $($Object.Name)" -Status "$i/$count : $PercentComplete Complete" -PercentComplete $PercentComplete.Replace("%","")
                    $i++
                } else {
                    Write-Progress -Activity "Processing VM: $($Object.Name)" -Status "Completed: $i"
                    $i++
                }
            }
        }
    }

    END {}
}

Copy the script to a folder and let’s go over some of the usage and examples. Since Get-VM already displays the basic info such as CPU, memory etc.. in the default output, I didn’t think it was necessary to add those properties in the script.

Get-VMInformation Examples and Usage

First things first, we’ll need to load the function into memory and connect to a vcenter server in order to query the information that we’re looking for. If you’re not connected, the script will output an error saying its unable to continue.

#import the PowerCLI module
Import-Module VMware.PowerCLI

#Connect to a vcenter server
Connect-VIServer -Server vcenter.thesysadminchannel.com

#Load the function into memory.  This is assuming your file is located in C:\Scripts
. 'C:\Scripts\Get-VMInformation.ps1'

#Get vm information for PAC-DC01.  
PS C:\> Get-VMInformation -Name PAC-DC01

Name        : PAC-DC01
PowerState  : PoweredOn
vCenter     : vcenter.thesysadminchannel.com
Datacenter  : US
Cluster     : Cluster-01
VMHost      : esx.thesysadminchannel.com
Datastore   : ESX_Local
Folder      : VMs
GuestOS     : Microsoft Windows Server 2012 (64-bit)
NetworkName : DPortGroup
IPAddress   : 10.0.0.100
MacAddress  : xx:xx:xx:xx:xx:xx
VMTools     : guestToolsCurrent

Since the function allows for pipeline input, we can get an array in VMs from a cluster or datacenter and just pipe it to the function. We will just have to make sure the Get-VM cmdlet is used before the Get-VMInformation to get the objects.

#EXAMPLE 1 - Gets the VM information for all VMs that are in the specified cluster within the US Datacenter and VCSA01 vcenter server.
    Get-Cluster Cluster-01 -Server vCSA01 -Location US | Get-VM | Get-VMInformation

#EXAMPLE 2 - Gets VM information for VMs 1 and 2
    Get-VM VM1, VM2 | Get-VMInformation

#EXAMPLE 3 - Gets VM information for VMs 1 and 2
    Get-VMInformation -Name VM1, VM2

I hope you found as much value in the Get-VMInformation script as I did. Let me know in the comments if you would like me to develop a script that has some usefulness to the general population.

For more VMware related articles take a look at VMware Gallery or stop by our Youtube Channel with VMware Videos

The post Get VMInformation Using Powershell and PowerCLI appeared first on the Sysadmin Channel.

Fix VMWare Call “HostDatastoreSystem.QueryVmfsDatastoreCreateOptions” for object “ha-datastoresystem” on ESXi failed

• Login to vSphere and navigate to configuration
• Click Security -> Properties -> SSH
• Click Options -> Start
• SSH into your host
• Navigate to /dev/disks directory
• List file (ls)
• Match the identifier with the datastore that you cant create in vSphere (Example: naa.6d4ae7608f873700762a910c5402c983)
• Type: partedUtil mklabel /dev/disks/naa.6d4ae7608f873700762a910c5402c983 msdos
• Exit SSH session
• Go back into vSphere and create the datastore
• Disable SSH service
• Subscribe to theSysadminChannel on Youtube for awesome video demos

I hope this helped someone with their error: Call “HostDatastoreSystem.QueryVmfsDatastoreCreateOptions” for object “ha-datastoresystem” on ESXi failed. If you have any questions be sure to leave a comment below and I’ll do my best to respond.

The post [Solved] Call “HostDatastoreSystem.QueryVmfsDatastoreCreateOptions” for object “ha-datastoresystem” on ESXi failed appeared first on the Sysadmin Channel.

Fix for Error Connecting to VMware vSphere Update Manager

I’ve seen from from different systems that this occurs mostly when you have MS Sql installed for your vcenter database. In this example I’m going to enable my user ad\vcenteradmin as the user account to use VUM.

• Login to your VMware vCenter Server
• Open SQL Server Management Studio and login to the instance
• Under Security -> Logins -> Right Click New Login
• Then to go General -> Type the domain\username
• Next click on User Mapping -> check VIM_UPD and VIM_VCDB
• Close out SQL Server Management Studio

• Next Add your vCenter admin account as a local administrator to the machine
• Go to Services.msc
• Right Click VMware vSphere Update Manager Service -> Properties
• Under Logon -> enter the domain\username that you set
• Restart the Service

Close out of the vSphere client and relaunch. You should now see that your Update Manager Plugin is now enabled.

 

Hopefully that solved your error for connecting to VMware vSphere Update Manager. Don’t forget to check us out on Youtube for more Sysadmin videos. https://www.youtube.com/c/TheSysadminChannel

The post [Solved] There Was An Error Connecting To VMware vSphere Update Manager appeared first on the Sysadmin Channel.

Get All VMware Snapshots using PowerCLI

You’re going to have to download and install the PowerCLI module as a prerequisite so I’ve linked an article we’ve previously wrote on how to do just that.

Now for the command.

Get-VM | Get-Snapshot | select VM, Name, Created

This method definitely beats having to right click each virtual machine and navigating one by one to see if the snapshot manager has something in memory.

Bonus Tip

If you find that you want to remove all snapshots at once you can append the Remove-Snapshot to the end of the Get-Snapshot. It would look something like this.

Note: We also want to append the Confirm parameter so it doesn’t prompt us to delete after running the command.

Get-VM | Get-Snapshot | Remove-Snapshot -Confirm:$false

Don’t forget to follow us on Youtube for more Sysadmin content

#PowershellBooks :
Learn PS month of Lunches

The post Get All VMware Snapshots using PowerCLI Module appeared first on the Sysadmin Channel.

vCenter version using VMware.PowerCLI

#Importing Module and Connecting to vCenter.
Import-Module VMware.PowerCLI
Connect-VIServer PAC-vCSA01

$Global:DefaultVIServers | select Name, Version, Build

And that’s it. Now you know how to find the vCenter version using VMware.PowerCLI. Don’t forget to check out our Sysadmin Channel on Youtube for awesome system administration related videos.

The post Find vCenter version using VMware.PowerCLI appeared first on the Sysadmin Channel.

Install VMware PowerCLI Module From PC With Internet Connection

• From a computer with an internet connection open powershell (preferrably as an administrator)
• Find-Module -Name VMware.PowerCLI
• Install-Module -Name VMware.PowerCLI -Scope CurrentUser
• Get-Command -Module *VMWare*

Using the -Scope CurrentUser parameter allows Powershell to install the module without administrator access.

Offline Installation of VMware PowerCLI Module

• Hop on a computer with internet access and open powershell (preferrably as an administrator)
• Find-Module -Name VMware.PowerCLI
• Save-Module -Name VMware.PowerCLI -Path Path
• Copy the files you downloaded to the offline computer
• Move the copied files to C:\Windows\System32\WindowsPowerShell\v1.0\Modules (requires admin rights)

Set-PowerCLIConfiguration Options

Once we have the module successfully imported we’re going to run a basic configuration command so we’re not prompted to join the VMware’s Customer Experience Improvement Program (“CEIP”) and so it ignores the certificate warning.

#Set the participation to false and ignore invalid certificates for all users
Set-PowerCLIConfiguration -Scope AllUsers -ParticipateInCeip $false -InvalidCertificateAction Ignore

#Connect to our vCenter Server using the logged in credentials
Connect-VIServer PAC-vCSA01

#Get a list of Virtual Machines
Get-VM

Once you’re able to get the list of VMs that means that you’re good to go. Hopefully this article was an excellent tutorial to get you to install vmware powercli. If you have any questions or run into any issues let me know in the comments so I can update it on my end.

On another note, don’t forget to take a look at our Sysadmin channel on Youtube. Be sure to subscribe to get up to date videos on sysadmin related content.

The post How To Install VMware PowerCLI Module using Powershell appeared first on the Sysadmin Channel.

Fix for WMware Workstation Not Showing Bridged Network Adapters

• On your Host computer, go to Network and Sharing Center -> Change Adapter Settings.
• Right Click your Ethernet Adapter and select Properties.
• Click Install.
• Select Service -> Add.
• On the left panel, select VMWare for the Manufacturer and Click OK.
• Select WMware Bridge Protocol and Click OK.
• Restart your computer

Now if you go back into VMware Workstation Machine Settings, you should be able to click on the bridged radio button and configure adapters. Select which adapter you want bridged to your network and you’re all set. The issue of WMware Workstation not showing bridged network adapters is now resolved.

Also, don’t forget to check out our Youtube Channel for more awesome Sysadmin content. Thanks again for joining us.

The post [Solved] WMware Workstation Not Showing Bridged Network Adapters appeared first on the Sysadmin Channel.