Create Client Id and Client Secret for Azure Active Directory

Developers and software-as-a-service (SaaS) providers can develop cloud services, that can be integrated with Azure Active Directory to provide secure sign-in and authorization for their services. To integrate an application or service with Azure AD, a developer must first register the application with Azure Active Directory with Client ID and Client Secret. Creating a service principal, try using Azure Active Directory Managed Service Identity for your application identity.

Any application that wants to use the capabilities of Azure Active Directory must be registered in an Azure. The app registration will give the Client ID which is App ID and Client Secret, Sign-On URL.

How to Create Client Id and Client Secret for Azure

1) Log in to the Azure portal.

You must have sufficient permissions to register an application with your Azure Active Directory tenant and assign the application to a role in your Azure subscription.

2) On the top search bar, type “Azure Active Directory” and click the Active directory or Click on More Services on the left-hand side, and choose the Azure Active Directory.

3) Click on App registrations and Click “New application registration

  • Make sure App registration is allowed for the user account through the Azure Active Directory -> select User settings and “App registrations” selected as “Yes
azure-client-id-secret-key-generate

azure-client-id-secret-key-generate

 

4) Provide a name and URL for the application.

  • Select Web app / API for the type of application and Click Create.
azure-app-registration

azure-app-registration

 

You have created your application.

 

How to Get application ID and authentication key

To get the application Client Id and Key details.

1) From the App registrations in Azure Active Directory, select your application.

azure-app-registration-step2

azure-app-registration-step2

 

 

 

 

 

 

 

2) Copy the Application ID

3) Click Settings on the same window.

azure-app-registration-step3

azure-app-registration-step3

4) To generate an authentication key, Click Keys.

azure-app-registration-step4

azure-app-registration-step4

5) Update a description of the key, and a duration and value which is your password, select Save.

azure-app-registration-step5

azure-app-registration-step5

Now the Client ID and Client Secret will be used for your configurations or any other rest clients.

How to Get Azure tenant ID

It is required to pass the tenant ID with your authentication request.

1) Select the Azure Active Directory.

2) To get the Azure tenant ID, select Properties for your Azure AD tenant.

 

azure-get-tenent-id

azure-get-tenent-id

 

How to Assign Role to application

To access the subscription, you must assign the application to a role. Decide which role represents the right permissions for the application.

1) Select your Subscriptions (On the top search bar, type “Subscriptions“).

2) Click Access Control (IAM)

3) Select Add

4) Select the role you wish to assign to the application.

azure-update-role

azure-update-role

5) Select Save to finish assigning the role. You see your application in the list of users assigned to a role for that scope.

 

How to create an Azure Client ID and Client Secret using AZ command line

1) Login with Azure account.

  • It will ask you the confirmation and update an auth configuration to local. Make sure you are having a valid subscription.
# az login

1) Create Service Principle

  • You will get the tenant id, appid and auth password.
# az ad sp create-for-rbac --name <app_name> --password <passwd>
{
"appId": "8334373-0dd9-438c-b563-2a6dbd8248c9",
"displayName": "my-test",
"name": "http://my-test",
"password": "password",
"tenant": "9a562b46-a92e-2113-4r33-7ca4c3598479"
}

2) Assign Role

# az role assignment list --assignee <app_id>
[
{
"id": "/subscriptions/<su_id>/providers/Microsoft.Authorization/roleAssignments/efccd2ae-236o-41de-ba22-58d2e6146164",
"name": "efccd2ae-4e20-41de-b022-58d2e6046164",
"properties": {
"principalId": "367a4295-5oo5-4162-ae71-248534k463a2",
"principalName": "http://my-test",
"roleDefinitionId": "/subscriptions/<su_id>/providers/Microsoft.Authorization/roleDefinitions/b24988ac-6180-42a0-ab88-20f7382dd24c",
"roleDefinitionName": "Contributor",
"scope": "/subscriptions/<su_id>"
},
"type": "Microsoft.Authorization/roleAssignments"
}
]
 

Azure Virtual Machines Common Error Messages

There are many options to get a failure on your Azure cloud when you create a VM, restart stopped (de-allocated) VMs, resize a VM, or when you add new web or worker role instances, Microsoft Azure allocates compute resources to your subscription. You may occasionally receive errors when performing these operations even before you reach the Azure subscription limits. An error response always includes a status code and an error object. Each error object always contains an error code and a message. If the VM is created with a template, the error object also contains a details section that contains an inner level of error codes and message. Normally, the most inner level of an error message is the root failure.

Azure Common Errors

Azure Common Errors

Azure Virtual Machine Common Errors

The common azure cloud virtual machines error messages you may encounter when managing VMs. Use this errors code to Troubleshoot common Azure deployment errors.

 

Error Code Error Message
AcquireDiskLeaseFailed Failed to acquire lease while creating disk ‘{0}’ using blob with URI {1}. Blob is already in use.
AllocationFailed Allocation failed. Please try reducing the VM size or number of VMs, retry later, or try deploying to a different Availability Set or different Azure location.
AllocationFailed The VM allocation failed due to an internal error. Please retry later or try deploying to a different location.
ArtifactNotFound The VM extension with publisher ‘{0}’ and type ‘{1}’ could not be found in location ‘{2}’.
ArtifactNotFound Extension with publisher ‘{0}’, type ‘{1}’, and type handler version ‘{2}’ could not be found in the extension repository.
ArtifactVersionNotFound No version found in the artifact repository that satisfies the requested version ‘{0}’.
ArtifactVersionNotFound No version found in the artifact repository that satisfies the requested version ‘{0}’ for VM extension with publisher ‘{1}’ and type ‘{2}’.
AttachDiskWhileBeingDetached Cannot attach data disk ‘{0}’ to VM ‘{1}’ because the disk is currently being detached. Please wait until the disk is completely detached and then try again.
BadRequest Aligned’ Availability Sets are not yet supported in this region.
BadRequest Addition of a VM with managed disks to non-managed Availability Set or addition of a VM with blob based disks to managed Availability Set is not supported. Please create an Availability Set with ‘managed’ property set in order to add a VM with managed disks to it.
BadRequest Managed Disks are not supported in this region.
BadRequest Multiple VMExtensions per handler not supported for OS type ‘{0}’. VMExtension ‘{1}’ with handler ‘{2}’ already added or specified in input.
BadRequest Operation ‘{0}’ is not supported on Resource ‘{1}’ with managed disks.
CertificateImproperlyFormatted The secret’s JSON representation retrieved from {0} has a data field which is not a properly formatted PFX file, or the password provided does not decode the PFX file correctly.
CertificateImproperlyFormatted The data retrieved from {0} is not deserializable into JSON.
Conflict Disk resizing is allowed only when creating a VM or when the VM is deallocated.
ConflictingUserInput Disk ‘{0}’ cannot be attached as the disk is already owned by VM ‘{1}’.
ConflictingUserInput Source and destination resource groups are the same.
ConflictingUserInput Source and destination storage accounts for disk {0} are different.
ContainerAlreadyOnLease There is already a lease on the storage container holding the blob with URI {0}.
CrossSubscriptionMoveWithKeyVaultResources The Move resources request contains KeyVault resources which are referenced by one or more {0}s in the request. This is not supported currently in Cross subscription Move. Please check the error details for the KeyVault resource Ids.
DiagnosticsOperationInternalError An internal error occurred while processing diagnostics profile of VM {0}.
DiskBlobAlreadyInUseByAnotherDisk Blob {0} is already in use by another disk belonging to VM ‘{1}’. You can examine the blob metadata for the disk reference information.
DiskBlobNotFound Unable to find VHD blob with URI {0} for disk ‘{1}’.
DiskBlobNotFound Unable to find VHD blob with URI {0}.
DiskEncryptionKeySecretMissingTags {0} secret doesn’t have the {1} tags. Please update the secret version, add the required tags and retry.
DiskEncryptionKeySecretUnwrapFailed Unwrap of secret {0} value using key {1} failed.
DiskImageNotReady Disk image {0} is in {1} state. Please retry when image is ready.
DiskPreparationError One or more errors occurred while preparing VM disks. See disk instance view for details.
DiskProcessingError Disk processing halted as the VM has other disks in failed disks.
ImageBlobNotFound Unable to find VHD blob with URI {0} for disk ‘{1}’.
ImageBlobNotFound Unable to find VHD blob with URI {0}.
IncorrectDiskBlobType Disk blobs can only be of type page blob. Blob {0} for disk ‘{1}’ is of type block blob.
IncorrectDiskBlobType Disk blobs can only be of type page blob. Blob {0} is of type ‘{1}’.
IncorrectImageBlobType Disk blobs can only be of type page blob. Blob {0} for disk ‘{1}’ is of type block blob.
IncorrectImageBlobType Disk blobs can only be of type page blob. Blob {0} is of type ‘{1}’.
InternalOperationError Could not resolve storage account {0}. Please ensure it was created through the Storage Resource Provider in the same location as the compute resource.
InternalOperationError {0} goal seeking tasks failed.
InternalOperationError Error occurred in validating the network profile of VM ‘{0}’.
InvalidAccountType The AccountType {0} is invalid.
InvalidParameter The value of parameter {0} is invalid.
InvalidParameter The Admin password specified is not allowed.
InvalidParameter “The supplied password must be between {0}-{1} characters long and must satisfy at least {2} of password complexity requirements from the following:

  1. Contains an uppercase character
  2. Contains a lowercase character
  3. Contains a numeric digit
  4. Contains a special character.
InvalidParameter The Admin Username specified is not allowed.
InvalidParameter Cannot attach an existing OS disk if the VM is created from a platform or user image.
InvalidParameter Container name {0} is invalid. Container names must be 3-63 characters in length and may contain only lower-case alphanumeric characters and hyphen. The hyphen must be preceded and followed by an alphanumeric character.
InvalidParameter Container name {0} in URL {1} is invalid. Container names must be 3-63 characters in length and may contain only lower-case alphanumeric characters and hyphen. The hyphen must be preceded and followed by an alphanumeric character.
InvalidParameter The blob name in URL {0} contains a slash. This is presently not supported for disks.
InvalidParameter The URI {0} does not look to be correct blob URI.
InvalidParameter A disk named ‘{0}’ already uses the same LUN: {1}.
InvalidParameter A disk named ‘{0}’ already exists.
InvalidParameter Cannot specify user image overrides for a disk already defined in the specified image reference.
InvalidParameter A disk named ‘{0}’ already uses the same VHD URL {1}.
InvalidParameter The specified fault domain count {0} must fall in the range {1} to {2}.
InvalidParameter The license type {0} is invalid. Valid license types are: Windows_Client or Windows_Server, case sensitive.
InvalidParameter Linux host name cannot exceed {0} characters in length or contain the following characters: {1}.
InvalidParameter Destination path for Ssh public keys is currently limited to its default value {0} due to a known issue in Linux provisioning agent.
InvalidParameter A disk at LUN {0} already exists.
InvalidParameter Subscription {0} of the request must match the subscription {1} contained in the managed disk id.
InvalidParameter Custom data in OSProfile must be in Base64 encoding and with a maximum length of {0} characters.
InvalidParameter Blob name in URL {0} must end with ‘{1}’ extension.
InvalidParameter {0}’ is not a valid captured VHD blob name prefix. A valid prefix matches regex ‘{1}’.
InvalidParameter Certificates cannot be added to your VM if the VM agent is not provisioned.
InvalidParameter A disk at LUN {0} already exists.
InvalidParameter Unable to create the VM because the requested size {0} is not available in the cluster where the availability set is currently allocated. The available sizes are {1}. Read more on VM resizing strategy at https://aka.ms/azure-resizevm.
InvalidParameter The requested VM size {0} is not available in the current region. The sizes available in the current region are {1}. Find out more on the available VM sizes in each region at https://aka.ms/azure-regions.
InvalidParameter The requested VM size {0} is not available in the current region. Find out more on the available VM sizes in each region at https://aka.ms/azure-regions.
InvalidParameter Windows admin username cannot be more than {0} characters long, end with a period(.), or contain the following characters: {1}.
InvalidParameter Windows computer name cannot be more than {0} characters long, be entirely numeric, or contain the following characters: {1}.
MissingMoveDependentResources The move resources request does not contain all the dependent resources. Please check error details for missing resource ids.
MoveResourcesHaveInvalidState The Move Resources request contains VMs which are associated with invalid storage accounts. Please check details for these resource ids and referenced storage account names.
MoveResourcesHavePendingOperations The move resources request contains resources for which an operation is pending. Please check details for these resource ids. Retry your operation once the pending operations complete.
MoveResourcesNotFound The move resources request contains resources that cannot be found. Please check details for these resource ids.
NetworkingInternalOperationError Unknown network allocation error.
NetworkingInternalOperationError Unknown network allocation error
NetworkingInternalOperationError An internal error occurred in the processing network profile of the VM.
NotFound The Availability Set {0} cannot be found.
NotFound Source Virtual Machine ‘{0}’ specified in the request does not exist in this Azure location.
NotFound Tenant with id {0} not found.
NotFound The Image {0} cannot be found.
NotSupported The license type is {0}, but the image blob {1} is not from on-premises.
OperationNotAllowed Availability Set {0} cannot be deleted. Before deleting an Availability Set please ensure that it does not contain any VM.
OperationNotAllowed Changing availability set SKU from ‘Aligned’ to ‘Classic’ is not allowed.
OperationNotAllowed Cannot modify extensions in the VM when the VM is not running.
OperationNotAllowed The Capture action is only supported on a Virtual Machine with blob based disks. Please use the ‘Image’ resource APIs to create an Image from a managed Virtual Machine.
OperationNotAllowed The resource {0} cannot be created from Image {1} until Image has been successfully created.
OperationNotAllowed Updates to encryptionSettings is not allowed when VM is allocated, Please retry after VM is deallocated
OperationNotAllowed Addition of a managed disk to a VM with blob based disks is not supported.
OperationNotAllowed The maximum number of data disks allowed to be attached to a VM of this size is {0}.
OperationNotAllowed Addition of a blob based disk to VM with managed disks is not supported.
OperationNotAllowed Operation ‘{0}’ is not allowed on Image ‘{1}’ since the Image is marked for deletion. You can only retry the Delete operation (or wait for an ongoing one to complete).
OperationNotAllowed Operation ‘{0}’ is not allowed on VM ‘{1}’ since the VM is generalized.
OperationNotAllowed Operation ‘{0}’ is not allowed as Restore point collection ‘{1}’ is marked for deletion.
OperationNotAllowed Operation ‘{0}’ is not allowed on VM extension ‘{1}’ since it is marked for deletion. You can only retry the Delete operation (or wait for an ongoing one to complete).
OperationNotAllowed Operation ‘{0}’ is not allowed since the Virtual Machines ‘{1}’ are being provisioned using the Image ‘{2}’.
OperationNotAllowed Operation ‘{0}’ is not allowed since the Virtual Machine ScaleSet ‘{1}’ is currently using the Image ‘{2}’.
OperationNotAllowed Operation ‘{0}’ is not allowed on VM ‘{1}’ since the VM is marked for deletion. You can only retry the Delete operation (or wait for an ongoing one to complete).
OperationNotAllowed Operation ‘{0}’ is not allowed on VM ‘{1}’ since the VM is either deallocated or marked to be deallocated.
OperationNotAllowed Operation ‘{0}’ is not allowed on VM ‘{1}’ since the VM is running. Please power off explicitly in case you shut down the VM from inside the guest operating system.
OperationNotAllowed Operation ‘{0}’ is not allowed on VM ‘{1}’ since the VM is not deallocated.
OperationNotAllowed Operation ‘{0}’ is not allowed on VM ‘{1}’ since VM has extension ‘{2}’ in failed state.
OperationNotAllowed Operation ‘{0}’ is not allowed on VM ‘{1}’ since another operation is in progress.
OperationNotAllowed The operation ‘{0}’ requires the Virtual Machine ‘{1}’ to be Generalized.
OperationNotAllowed The operation requires the VM to be running (or set to run).
OperationNotAllowed Disk with size {0}GB, which is smaller than the size {1}GB of the corresponding disk in Image, is not allowed.
OperationNotAllowed VM Scale Set extensions of handler ‘{0}’ can be added only at the time of VM Scale Set creation.
OperationNotAllowed VM Scale Set extensions of handler ‘{0}’ can be deleted only at the time of VM Scale Set deletion.
OperationNotAllowed VM ‘{0}’ is already using managed disks.
OperationNotAllowed VM ‘{0}’ belongs to ‘Classic’ availability set ‘{1}’. Please update the availability set to use ‘Aligned’ SKU and then retry the Conversion.
OperationNotAllowed VM created from Image cannot have blob based disks. All disks have to be managed disks.
OperationNotAllowed Capture operation cannot be completed because the VM is not generalized.
OperationNotAllowed Management operations on VM ‘{0}’ are disallowed because VM disks are being converted to managed disks.
OperationNotAllowed An ongoing operation is changing power state of Virtual Machine {0} to {1}. Please perform operation {2} after some time.
OperationNotAllowed Unable to add or update the VM. The requested VM size {0} may not be available in the existing allocation unit. Read more on VM resizing strategy at https://aka.ms/azure-resizevm.
OperationNotAllowed Unable to resize the VM because the requested size {0} is not available in the cluster where the availability set is currently allocated. The available sizes are: {1}. Read more on VM resizing strategy at https://aka.ms/azure-resizevm.
OperationNotAllowed Unable to resize the VM because the requested size {0} is not available in the cluster where the VM is currently allocated. To resize your VM to {1} please deallocate (this is Stop operation in the Azure portal) and try the resize operation again. Read more on VM resizing strategy at https://aka.ms/azure-resizevm.
OSProvisioningClientError OS Provisioning failed for VM ‘{0}’ because the guest OS is currently being provisioned.
OSProvisioningClientError OS provisioning for VM ‘{0}’ failed. Error details: {1} Make sure the image has been properly prepared (generalized).

OSProvisioningClientError SSH host key generation failed. Error details: {0}. To resolve this issue verify if Linux agent is set up properly.

OSProvisioningClientError Username specified for the VM is invalid for this Linux distribution. Error details: {0}.
OSProvisioningInternalError OS Provisioning failed for VM ‘{0}’ due to an internal error.
OSProvisioningTimedOut OS Provisioning for VM ‘{0}’ did not finish in the allotted time. The VM may still finish provisioning successfully. Please check provisioning state later.
OSProvisioningTimedOut OS Provisioning for VM ‘{0}’ did not finish in the allotted time. The VM may still finish provisioning successfully. Please check provisioning state later. Also, make sure the image has been properly prepared (generalized).

OSProvisioningTimedOut OS Provisioning for VM ‘{0}’ did not finish in the allotted time. However, the VM guest agent was detected running. This suggests the guest OS has not been properly prepared to be used as a VM image (with CreateOption=FromImage). To resolve this issue, either use the VHD as is with CreateOption=Attach or prepare it properly for use as an image:

OverConstrainedAllocationRequest The required VM size is not currently available in the selected location.
ResourceUpdateBlockedOnPlatformUpdate Resource cannot be updated at this time due to ongoing platform update. Please try again later.
StorageAccountLimitation Storage account ‘{0}’ does not support page blobs which are required to create disks.
StorageAccountLimitation Storage account ‘{0}’ has exceeded its allocated quota.
StorageAccountLocationMismatch Could not resolve storage account {0}. Please ensure it was created through the Storage Resource Provider in the same location as the compute resource.
StorageAccountNotFound Storage account {0} not found. Ensure storage account is not deleted and belongs to the same Azure location as the VM.
StorageAccountNotRecognized Please use a storage account managed by Storage Resource Provider. Use of {0} is not supported.
StorageAccountOperationInternalError Internal error occurred while accessing storage account {0}.
StorageAccountSubscriptionMismatch Storage account {0} doesn’t belong to subscription {1}.
StorageAccountTooBusy Storage account ‘{0}’ is too busy currently. Consider using another account.
StorageAccountTypeNotSupported Disk {0} uses {1} which is a Blob storage account. Please retry with General purpose storage account.
StorageAccountTypeNotSupported Storage account {0} is of {1} type. Boot Diagnostics supports {2} storage account types.

  • This error occurs if you use the premium storage account for Boot diagnostics. For more information, see How to use boot diagnostics.
SubscriptionNotAuthorizedForImage The subscription is not authorized.
TargetDiskBlobAlreadyExists Blob {0} already exists. Please provide a different blob URI to create a new blank data disk ‘{1}’.
TargetDiskBlobAlreadyExists Capture operation cannot continue because target image blob {0} already exists and the flag to overwrite VHD blobs is not set. Either delete the blob or set the flag to overwrite VHD blobs and retry.
TargetDiskBlobAlreadyExists Capture operation cannot continue because target image blob {0} has an active lease on it.
TargetDiskBlobAlreadyExists Blob {0} already exists. Please provide a different blob URI as target for disk ‘{1}’.
TooManyVMRedeploymentRequests Too many redeployment requests have been received for VM ‘{0}’ or the VMs in the same availability set with this VM. Please retry later.
VHDSizeInvalid The specified disk size value of {0} for disk ‘{1}’ with blob {2} is invalid. Disk size must be between {3} and {4}.
VMAgentStatusCommunicationError VM ‘{0}’ has not reported status for VM agent or extensions. Please verify the VM has a running VM agent and can establish outbound connections to Azure storage.
VMArtifactRepositoryInternalError An error occurred while communicating with the artifact repository to retrieve VM artifact details.
VMArtifactRepositoryInternalError An internal error occurred while retrieving the VM artifact data from the artifact repository.
VMExtensionHandlerNonTransientError Handler ‘{0}’ has reported failure for VM Extension ‘{1}’ with terminal error code ‘{2}’ and error message: ‘{3}’
VMExtensionManagementInternalError Internal error occurred while processing VM extension ‘{0}’.
VMExtensionManagementInternalError Multiple errors occurred while preparing the VM extensions. See VM extension instance view for details.
VMExtensionProvisioningError VM has reported a failure when processing extension ‘{0}’. Error message: “{1}”.
VMExtensionProvisioningError Multiple VM extensions failed to be provisioned on the VM. Please see the VM extension instance view for details.
VMExtensionProvisioningTimeout Provisioning of VM extension ‘{0}’ has timed out. Extension installation may be taking too long, or extension status could not be obtained.
VMMarketplaceInvalidInput Creating a virtual machine from a non Marketplace image does not need Plan information, please remove the Plan information in the request. OS disk name is {0}.
VMMarketplaceInvalidInput The purchase information does not match. Unable to deploy from the Marketplace image. OS disk name is {0}.
VMMarketplaceInvalidInput Creating a virtual machine from Marketplace image requires Plan information in the request. OS disk name is {0}.
VMNotFound The VM ‘{0}’ cannot be found.
VMRedeploymentFailed VM ‘{0}’ redeployment failed due to an internal error. Please retry later.
VMRedeploymentTimedOut Redeployment of VM ‘{0}’ didn’t finish in the allotted time. It might finish successfully in some time. Else, you can retry the request.
VMStartTimedOut VM ‘{0}’ did not start in the allotted time. The VM may still start successfully. Please check the power state later.

 

 

Increase VMware vSphere Web Client Session Timeout

You have noticed that while working on both vSphere Web Client and HTML5 vSphere Client, You will be logged out from the vsphere Web Client due to inactivity. This may be annoying you to log in multiple times to your Web Client environment. We can increase session timeout value for VMware vSphere Web client for both vCenter Server Appliance and Windows vCenter setup.

Use below steps to increase the vSphere web client session timeout value but note that the vSphere Web Client session inactivity timeout is really needed in the Production environment to secure your vSphere environment by avoiding someone else access your windows session and access the vSphere environment via your Web client session.

Increase Web Client Session Timeout

Increase Web Client Session Timeout

Increase VMware vSphere Web Client Session Timeout

From vSphere 5.5, the vSphere Web Client session timeout period was increased to 120 minutes by default.

Open the webclient.properties file and modify session.timeout values in vSphere Web Client to fix this issue.

vCenter Server 5.x

Windows 2003 – %ALLUSERSPROFILE%\Application Data\VMware\vSphere Web Client
Windows 2008/2012 – %ALLUSERSPROFILE%\VMware\vSphere Web Client
VMware vCenter Server Appliance – /var/lib/vmware/vsphere-client

vCenter Server 6.x

Windows:

For Flash-based Web Client - %ALLUSERSPROFILE%\VMware\vCenterServer\cfg\vsphere-client
For HTML5 vSphere Client in vSphere 6.5 - %ALLUSERSPROFILE%\VMware\vCenterServer\cfg\vsphere-ui

vCenter Server Appliance:

For Flash-based Web Client - /etc/vmware/vsphere-client/
For HTML5 vSphere Client in vSphere 6.5 - /etc/vmware/vsphere-ui/

Add this line to the webclient.properties file:

Note: If the line already exists, verify that the line does not contain a hash (#).

session.timeout = value

where the value is the timeout value in minutes.

For example, to set the timeout value to 180 minutes (3 hours), add the line:

session.timeout = 180

If you want to disable and never get a timeout (It is not recommended for security reason)

Change the value to “0” (zero).

 

Restart the vSphere Web Client service

In Windows vCenter Server 5.x, use services.msc to restart the VMware web client service.

In vCenter Server Appliance 5.x, run this command:

/etc/init.d/vsphere-client restart

In Windows vCenter Server 6.x:

To restart Flash-based Web Client service, run these commands using Command-Prompt:

C:\Program Files\VMware\vCenter Server\bin\service-control --stop vspherewebclientsvc
C:\Program Files\VMware\vCenter Server\bin\service-control --start vspherewebclientsvc

To restart HTML5 vSphere Client service in vSphere 6.5, run these commands using Command-Prompt:

C:\Program Files\VMware\vCenter Server\bin\service-control --stop vsphere-ui
C:\Program Files\VMware\vCenter Server\bin\service-control --start vsphere-ui

In vCenter Server Appliance 6.x:

To restart Flash-based Web Client service, run these commands:

service-control --stop vsphere-client
service-control --start vsphere-client

To restart HTML5 vSphere Client service in vSphere 6.5, run these commands:

service-control --stop vsphere-ui
service-control --start vsphere-ui