sk84's Posts

sk84 · ‎09-19-2020

Leave it as 20 cores x 1 socket as long as your VM has less than half of the physical memory and less vCPUs than physical cores. This might clarify some things (there is no vNUMA behavior chan...

Leave it as 20 cores x 1 socket as long as your VM has less than half of the physical memory and less vCPUs than physical cores. This might clarify some things (there is no vNUMA behavior change between 6.7 and 7.0): Virtual Machine vCPU and vNUMA Rightsizing - Rules of Thumb - VMware VROOM! Performance Blog

sk84 · ‎07-21-2019

There is no official evaluation mode for vCloud Director 9.x because vCD 9.x is only available for Service and Cloud Providers with an active VCPP contract. And within VCPP, vCD is free. Therefor...

There is no official evaluation mode for vCloud Director 9.x because vCD 9.x is only available for Service and Cloud Providers with an active VCPP contract. And within VCPP, vCD is free. Therefore a trial period makes no sense for this product.

sk84 · ‎07-18-2019

As far as I know, that's not possible. Roles and rights are assigned to organization and users and applied to general object types (all vApps, all VMs, all oVDCs, etc.). That means, you can only ...

As far as I know, that's not possible. Roles and rights are assigned to organization and users and applied to general object types (all vApps, all VMs, all oVDCs, etc.). That means, you can only assign roles or permissions to tenants (organizations) or users, but not to oVDCs. And if you set the right to view the object type "oVDCs" in a role, all users with this role can see all oVDCs that belong to the corresponding organization. There is no mechanism for selecting "Allow view for oVDC X, Y and Z". See: Managing Rights and Roles

sk84 · ‎07-18-2019

You can try the following: ovftool.exe --sourceType="ISO" --noSSLVerify C:\TEST.iso "vcloud://user:password@MY-VCD-URL?org=Dev&vdc=Dev-VDC&catalog=CD&media=TEST.iso"

sk84 · ‎07-18-2019

Oh, I didn't see that you mentioned the version. Sorry for that. And I'm pretty sure SSLv1 is not used anymore in vSphere 6.5. You should therefore contact your security team and ask them whic...

Oh, I didn't see that you mentioned the version. Sorry for that. And I'm pretty sure SSLv1 is not used anymore in vSphere 6.5. You should therefore contact your security team and ask them which service or port uses SSLv1 and ask if this could be a false positive. And maybe this resource will also help you or your security team: VMware Knowledge Base Do you know what a Tame server is and what is to be configured? No. Here you should also ask your security team what they mean and what you should do.

sk84 · ‎07-17-2019

It's great that you found and revived a post from 2012... The news is in the post above yours. VMware uses CIM to monitor the health of an ESXi host and monitoring tools can also retrieve this...

It's great that you found and revived a post from 2012... The news is in the post above yours. VMware uses CIM to monitor the health of an ESXi host and monitoring tools can also retrieve this information.

sk84 · ‎07-17-2019

Since vSphere 6.7 only TLSv1.2 is enabled by default. In addition there is a tool for managing the TLS protocols: Managing TLS Protocol Configuration with the TLS Configurator Utility But sin...

Since vSphere 6.7 only TLSv1.2 is enabled by default. In addition there is a tool for managing the TLS protocols: Managing TLS Protocol Configuration with the TLS Configurator Utility But since you didn't specify your version, other vSphere versions may look different. And whether changing the SSL/TLS settings will have an impact depends mainly on third-party software. vSphere itself (vCenter and ESXi Hosts) will work fine with higher TLS versions from 6.5 onwards. However, if you are using other software (backup software, monitoring tools or other VMware products in older versions), they may no longer work. Or if you use the vSphere (Web) client with an older browser that does not support TLS v1.2, you won't be able to connect to the vCenter server. --------------------------------------------------------------------------------------------------------- Was it helpful? Let us know by completing this short survey here.

sk84 · ‎07-13-2019

At first, if you have specific VxRail questions, contact Dell EMC Hyper-Converged Support. Because only general VMware questions are answered here and HCI systems can be special in some ways. Sec...

At first, if you have specific VxRail questions, contact Dell EMC Hyper-Converged Support. Because only general VMware questions are answered here and HCI systems can be special in some ways. Second, it's always good to tell the people here what versions you're using, as there may be differences in how to do something depending on the version. To give you a general answer: The vCenter of VxRails is not really different from a normal vCenter. So you can make normal file based backups using the VAMI backend: File-Based Backup and Restore of vCenter Server Appliance

sk84 · ‎07-13-2019

At first, if you have specific VxRail questions, contact Dell EMC Hyper-Converged Support. Because only general VMware questions are answered here and HCI systems can be special in some ways. Sec...

At first, if you have specific VxRail questions, contact Dell EMC Hyper-Converged Support. Because only general VMware questions are answered here and HCI systems can be special in some ways. Second, it's always good to tell the people here what versions you're using, as there may be differences in how to do something depending on the version. To give you a general answer: The vCenter of VxRails is not really different from a normal vCenter. So you can make normal file based backups using the VAMI backend: File-Based Backup and Restore of vCenter Server Appliance

sk84 · ‎07-13-2019

Since vSphere version 6.5 there are only 2 clients available: vSphere Web Client (Flash based) and the vSphere Client (HTML5 based). Both are only running in a browser. The HTML5 vSphere Client w...

Since vSphere version 6.5 there are only 2 clients available: vSphere Web Client (Flash based) and the vSphere Client (HTML5 based). Both are only running in a browser. The HTML5 vSphere Client will be the future and it's usually faster and (in my opinion) has less bugs and a cleaner look & feel. The name of the HTML vSphere client is a bit confusing. Because there was an older standalone client application (for vSphere versions 4.x, 5.x, and 6.0) that you could install on Windows. And it was also called vSphere Client (or Fat Client). But it has nothing to do with the new HTML5 vSphere client.

sk84 · ‎07-09-2019

The security team called this a security vulnerability. Seriously? The security team has no idea. It's only a security problem if the accesses are not regulated and unauthorized people have ...

The security team called this a security vulnerability. Seriously? The security team has no idea. It's only a security problem if the accesses are not regulated and unauthorized people have access to this host... --------------------------------------------------------------------------------------------------------- Was it helpful? Let us know by completing this short survey here.

sk84 · ‎07-09-2019

As far as I know this is not officially supported and there is no proper way to do that what you want. There are some guides on the internet on how to change this URL behavior in the endpoints.co...

As far as I know this is not officially supported and there is no proper way to do that what you want. There are some guides on the internet on how to change this URL behavior in the endpoints.conf configuration file of the rhttpproxy. However, none of this works for rewriting the complete URL. And I wouldn't recommend you experimenting with it on a productive system either. But what exactly do you want to achieve? What bothers you about this URL and why do you want to change it at all?

sk84 · ‎07-02-2019

I can see the General section in the vSphere Client (HTML5) and in the old vSphere Web Client (Flash): (vSphere 6.7 U2)

sk84 · ‎07-02-2019

All these questions are easy to find on the Internet with a search engine... If you don't know any or don't know how to use them, here are some examples and instructions: Google Bing LMG...

All these questions are easy to find on the Internet with a search engine... If you don't know any or don't know how to use them, here are some examples and instructions: Google Bing LMGTFY And yes, you need at least the root password of the Appliance Backend for the upgrade to U2. If you don't know how to reset the root password or admin@vsphere.local account: LMGTFY

sk84 · ‎06-28-2019

To test vSphere HA, I would recommend performing 2 tests covering the two most common errors: loss of network connection and power failure. So I would pull the power cables as the first test. ...

To test vSphere HA, I would recommend performing 2 tests covering the two most common errors: loss of network connection and power failure. So I would pull the power cables as the first test. And the second test would be to pull the network cables.

sk84 · ‎06-27-2019

Yeah sorry. I was wrong about the express patches. They are also cumulative and you only need the last one (EP10). What I don't understand is why you write U1? If you are on a pre 6.7 U1 vers...

Yeah sorry. I was wrong about the express patches. They are also cumulative and you only need the last one (EP10). What I don't understand is why you write U1? If you are on a pre 6.7 U1 version, you can directly upgrade to U2 and just apply the EP10. And if you already have upgraded/installed 6.7 U1 then you only need to upgrade to U2 and install EP10 as well.

sk84 · ‎06-27-2019

Basically you can directly upgrade to 6.7 U2 and only apply EP08, 09 and 10. But to make things more complicated: Not all upgrade paths are supported because some versions are newer than other...

Basically you can directly upgrade to 6.7 U2 and only apply EP08, 09 and 10. But to make things more complicated: Not all upgrade paths are supported because some versions are newer than others. You can check your upgrade path here: VMware Product Interoperability Matrices

sk84 · ‎06-27-2019

What daphnissov wrote is not entirely wrong. There are major versions (6.0, 6.5, 6.7), update bundles (U1, U2, U3), patches (P01, P02, etc.) and express patches (EP01, EP02, etc.). Major v...

What daphnissov wrote is not entirely wrong. There are major versions (6.0, 6.5, 6.7), update bundles (U1, U2, U3), patches (P01, P02, etc.) and express patches (EP01, EP02, etc.). Major versions, update bundles and patches are cumulative. But express patches are not. So, you need to look at the latest GA release, update or patch and take this as base to apply all higher express patches. There is a KB article about all ESXi versions and build numbers where you can look at: VMware Knowledge Base For example: If you want to go from ESXi 6.0 U2 to ESXi 6.5 EP14, you just need to install or upgrade to 6.5 U2c and apply the express patches 09, 10, 11, 12, 13 and 14. Or alternatively, you can install or upgrade to 6.5 U2c, apply patch 03 (P03) and just install express patch 12, 13 and 14.

sk84 · ‎06-27-2019

What Deso1ator wrote is correct. The host don't go in maintenance mode because of the missing DRS feature in your license. Insufficient resources to satisfy vSphere HA failover level on clust...

What Deso1ator wrote is correct. The host don't go in maintenance mode because of the missing DRS feature in your license. Insufficient resources to satisfy vSphere HA failover level on cluster XXXXXXX This may be a different issue. How many hosts do you have in this cluster and what are the admission control settings? For example: If you only have 2 hosts in a cluster and set admission control to tolerate 1 host failure, this message would appear during the maintenance mode of one host because the cluster can no longer tolerate 1 host failure (because just one active host is left).

sk84 · ‎06-23-2019

You must also put the request in quotation marks. The "&" character is otherwise interpreted by the shell (execute task in the background) and is no longer part of the request for curl. Therefore...

You must also put the request in quotation marks. The "&" character is otherwise interpreted by the shell (execute task in the background) and is no longer part of the request for curl. Therefore your request is always truncated at the "&" character and you always see the same page. So the right thing would be: curl -i -k -H "Accept:application/*+xml;version=31.0" -H "x-vcloud-authorization:f9c49bfdghkjkfgd4ebf4d7e2d89c17b" -X GET "https://my-vcd/api/query?type=adminUser&page=2"

All

sk84's Posts

Re: SQL CPU Configuration

Re: Evaluate vCloud Director 9.x

Re: Different permissions of each orgVDC

Re: ovftool - How to upload ISO file into vcd catalog media folder?

Re: Disable old SSL and TLS versions on VCSA?

Re: Nagios vSphere monitoring via NRPE

Re: Disable old SSL and TLS versions on VCSA?

Re: VXRail Vcenter backup

Re: Dell Vxrail Vcenter appliance backup issue

Re: Why should I use the VSphere Client to connect to ESXi hosts and vCenter?

Re: vSphere Web client Redirect

Re: vSphere Web client Redirect

Re: There is no "General" under settings.

Re: vcenter update

Re: Problem with HA configuration

Re: Improving upgrade/update process

Re: Improving upgrade/update process

Re: Improving upgrade/update process

Re: Problem with HA configuration

Re: REST API pagination problem