Quantcast
Channel: VMware Communities : Unanswered Discussions - vCenter™ Server
Viewing all 3506 articles
Browse latest View live
↧

vCenter 6.7 u3f Content Library issues

April 28, 2020, 8:18 am
$
0
0

Background:  I have 2 sites, one production, one DR/Dev.  I have setup a Local Content Library in the production site vCenter, and added a Subscribed Automatically Synchronous CL at the DR/Dev site.  Both sites have their respective CL on a volume that is mounted to every host at that site.  In that Content Library, there are both Templates and ISO objects.

 

Problem:  From the Production CL I can see and mount any of the ISO images to the VMs as needed.  From the DR/Dev site, I can see the ISOs in the content Library, but cannot mount them to the VM's in that vCenter.  I have an old application that can only be modified from a local ISO, but cannot mount that ISO, even though it is visible in the Subscribed CL.

 

Does anyone have any guidance that could help resolve my issue of not being able to mount ISO's out of the content library?

↧
Search

Upgrade vCenter Server 6.0 U3i from Windows 2008 R2 to Windows 2012 R2 Best Practice

April 28, 2020, 1:15 pm
$
0
0

Currently we have a Windows 2008 R2 virtual machine running as vCenter Server and are looking for ways to move to Windows 2012 R2. The vCenter Server is running version 6.0.0 U3i

↧
↧

File-Based Backup and Restore of vCenter Server Appliance

April 28, 2020, 7:04 pm
$
0
0

I tried to do do file based backup in vcsa 6.7 but failed.

Will I able to do file baseed backup to vcsa own datastore? Or I need to backup to remote servers?

Does vcsa 6.7 come with ftp , scp ?

Thanks

↧

Problems With vCenter Server Apliance

April 28, 2020, 7:05 pm
$
0
0

Hi Community

 

I have a problem with VCSA

 

I send a ping to the IP adress and this responds

 

 

But when intro the Ip in my web browser show me the following

 

I try to enter the Vm of the VCSA and I observe this detail "No Compatible Network Adapter"

 

 

 

Thanks!!!!!!!!!!

↧

Windows vCenter with multiple nic routing

April 29, 2020, 4:53 am
$
0
0

Hi,

 

Have a Windows vCenter with 2 vNIC's

 

if I come from the VPN (remote address) to one of these interface IP which however does not have a gateway set, does Windows vCenter automatically route back traffic out via the other interface which has the gateway set?

 

 

Thanks

↧
↧

vCenter authentication error

April 29, 2020, 9:48 am
$
0
0

I'm receiving an "invalid credentials" when logging into vCenter with username and password. It is joined to the domain.

 

websso.log shows this error:

"native platform error code 40265 lw_error_errno_econnrefused"

 

Is this a blocked port? We are in linked mode but I don't think that changes the way vCenter authenticates to AD but I could be mistaken. The vdcadmintool ldap test succeeds and I can add groups just nobody can login. -Thanks

↧

vCenter 6.7 Plugin Icon doesn't appear in vCenter server after doing power Cycle operation on vCenter Server, need to do refresh even its already installed

April 30, 2020, 4:20 am
$
0
0

Hi All,

We have developed a local plugin with vCenter 6.7 u2 SDK. The plugin is registered through the extension in which we provide the pluginBundle.zip file path which has jar and war file.  When the plugin is installed for 1st time on vCenter we need to re-login/refresh the browser for the plugin to upload and client plugins show that state its In progress and then deployed. But after successful installation, if we do vCenter power off and power on the plugin Icon doesn't appear in vCenter server. We still have to login and then re-login/refresh the vCenter server.

Step:

1. Trying to do Power cycle vCenter Server.(Power off the vCenter server and then after 10 minutes Power ON).

2. Then login to the vCenter server>> go to shortcut>> here didn't see the plugin icon.  the plugin is there but the icon is missing.

3. Then also checked in Administration>> Client plugin page.

4. And after refresh the web browser it shows properly.

 

Expected result: Icon should come after a power cycle the vCenter server, without refreshing the browser.

↧

VCENTER 6.7 TLS Version 1.1 Protocol Detection on Port 5432

May 1, 2020, 3:05 am
$
0
0

Hello,

 

The Nessus scanner  detect TLS1.1 on Vcenter 6.7 -   - Build number  15976714  any idea how to disable the TLS1.1 and allow only TLS1.2 on specific port 5432?

Currently all other ports use only TLS1.2

 

 

Synopsis

The remote service encrypts traffic using an older version of TLS.

Description

The remote service accepts connections encrypted using TLS 1.1. TLS 1.1 lacks support for current and recommended cipher suites. Ciphers that support encryption before MAC computation, and authenticated encryption modes such as GCM cannot be used with TLS 1.1  As of March 31, 2020, Endpoints that are not enabled for TLS 1.2 and higher will no longer function properly with major web browsers and major vendors.  PCI DSS v3.2 still allows TLS 1.1 as of June 30, 2018, but strongly recommends the use of TLS 1.2. A proposal is currently before the IETF to fully deprecate TLS 1.1 and many vendors have already proactively done this.

Output from most recent scan

TLSv1.1 is enabled and the server supports at least one cipher.

Solution

Enable support for TLS 1.2 and/or 1.3, and disable support for TLS 1.1.

↧
Search

Making Updated ISO from Dell OEM ISO

May 3, 2020, 1:36 am
$
0
0

Hi

 

I'm trying to update the latest Dell ESXi 6.7 ISO (build 15160138) to include the updates and patches included in the latest ESXi 6.7 release build 202004002.

 

I've downloaded the offline bundles for both builds in zip format and tried using Auto Deploy in VCSA but keep getting the error:

 

Invalid Fault

ThrowableProxy.cause

'name'

 

I'm using VCSA 7.0, don'y know if that's got anything to do with it?

 

Thanks in advance for any help.

↧
↧

Unable to logon VCSA 6.7 Child Domain

May 3, 2020, 7:06 am
$
0
0

Strange issue: We are unable to log into the VCSA using domain accts from one child domain, but can from another child domain. Here is what we have component/information wise:

- VCSA 6.7 U3F (embedded PSC)

- ESXi 6.7 (latest patches)

- Multi Domain Forest. VCSA nodes will are part of Domain "A"

- DNS forward/reverse records created

- NTP servers are the same device (no time skew) between site DCs and VCSA nodes

- Identity source configured to Integrated Windows Auth - set with Domain "A" but of course resolves to the Forest Domain/Alias - Trusts are all in place and working

- Smart Card access configured / Username and PW still enabled until complete

- Accounts/permissions are correctly added to vCenter

- Have a Production VCSA 6.5 environment (External PSC) in Domain "A" that is having no issues with logon

- Domain "A" functional level is 2012r2, Domain "B" functional level is 2012r2

 

Issue:

When attempting to login the vCenter, using accounts from Domain "A", we receiving the following error/s:

- When using username/password we receive "Invalid Credentials"

- When attempting to log in using Smart Card, we receive " [400] An error occurred while processing the authentication response from the vCenter Single Sign-On server. Details: Status: urn:oasis:names:tc:SAML:2.0:status:Responder, sub status: urn:oasis:names:tc:SAML:2.0:status:Null"

 

When attempting to log in, using above parameters, with domain accounts from Domain "B" we have no issues at all. Domain "B" accounts log in correctly.

 

As mentioned above, the Domain Trusts are all in place and working as this is a production environment. We currently have a VCSA 6.5 U3 environment running in the same configuration (except for the External PSC piece), and can log on with accounts from Domain "A", Domain "B", or any of the other domains in the forest. Looking in the websso.log file, I can see errors about Native Platform No EPIPE, and some other errors related to dead DNS records for off site DCs that have been Decom'd. Running packet traces I can confirm that it is talking to the closest DCs (our site), I see SMB2 traffic, but I noticed that for the Domain "A" NBNS queries, those packets are showing Workstation/Redirector. When logging in with Domain "B" accounts, those same NBNS queries are resolving the names of all the site DCs and show as Domain Controller in the packet. I have confirmed that DNS (forward/reverse) is working from the VCSA and can ping/resolve site DCs in Domain "A". We have confirmed NTP, we have removed the nodes from the domain and rejoined (both GUI and CLI). Once logged into the VCSA (using local OS or Domain "B" accounts), we see all the trusted domains and can add accounts from all the trusted domains, to include Domain "A", to SSO groups.

 

We have a ticket open with VMware, but I can not supply logs from this network. Has anyone run into an issues like this? We have tried/verified all the VMware KB "can't log in with Active directory accounts" articles, but still unable to log in with accounts from the one child domain - Domain "A"

 

Thoughts, help, crazy ideas?

↧

VCenter 7.0 - cannot add host

April 26, 2020, 4:34 am
$
0
0

Running VCenter 7.0 and I am trying to add an ESXi-7.0.0-15843807-standard host. I enter all the correct credentials and addition process starts but then abruptly ends with:

 

A specified parameter was not correct: info.productVersion

 

Anybody seen this and know why this is occurring and a possible fix?

↧

SSO password

May 4, 2020, 10:00 am
$
0
0

Hi Folks,

 

We have 4 vCenters in different locations and out of one we are getting administrator SSO password expiring soon, since I have given in the command line password never expire parameter still I'm observing same issue. Can someone help here please.

 

Thanks.

↧

vCenter 7.0 HTML5 login page stuck after Active Directory integrated with vCenter

May 5, 2020, 5:05 am
$
0
0

Just after integrating Active Directory to vCenter 7.0 and rebooting the appliance i tried login (with administrator@vsphere.local) to vCenter but the HTML5 client is stuck.

 

- i tried different browsers

- cleared cache

- tried incognito

- tried restarting vCenter service

 

but no luck, eventually rebooted the vCenter appliance and it worked but yet again once i logged off from vCenter and tried to login the loading page stuck again and reboot was the only answer ...

 

Also when i logged off from vCenter, received error: [401] This request requires HTTP authentication. After which it does not goes back to login screen unless i restart the browser.

↧
↧

VCSA Update from 6.5 U3 to 6.5 U3h - Unable to login via the flash web-client

May 6, 2020, 3:50 am
$
0
0

I recently patched the VCSA from 6.5 U3 to 6.5 U3h and now unable to login via the flash web client.

 

Web Client access is just showing a blue screen with the timer spinning.

 

I have tried an install of the latest Authentication Plugin and cleared IE cookies.

VCSA services are all running fine.

IE settings/config has not changed.

 

HTML5 access is still possible.

 

Has anyone else experienced the issue?

 

Thanks.

↧

vSphere Web client 6.7.0.1150 build 8495056 to VCenter Appliance upgrade

May 6, 2020, 5:49 am
$
0
0

is it possible to install VC appliance version 7 machine with my existing Vcenter 6.7.

not comfortable of upgrade but rather install a new VM instead of upgrade is it possible? if not, can you provide me upgrade path and documents.

 

Thanks

↧
Search

user account

May 6, 2020, 5:50 am
↧

VCSA restore from file native file level backup

May 6, 2020, 6:57 am
$
0
0

Hi All,

In my lab I have been running VCSA 6.7 which has been updated to version 6.7.0.42300 which is update 3e.

I now need to restore my VCSA and it appears that I need the ISO for the same version as the file level backup was created with.

 

In my case that is version 6.7.0u3e, however update 3e is a patch version and I am unable to find an iso for version 6.7.0u3e. The documentation stats that you need to use the ISO of the particular patch for the version you are restoring. How do I deploy a VCSA from the patch iso in order to restore my backup?

 

Has anyone a working procedure for this?

 

Any help or suggestions is greatly appreciated.

 

DJ

↧
↧

v6.7 Rollback

May 6, 2020, 9:07 pm
$
0
0

Hi guys,

 

We're planning to upgrade a vCenter instance from v6.0 to v6.7 (update 3). All the hosts we manage from this vCenter are all v6.0 hosts - various builds, vast majority of which are 3620759. We're not actively looking at upgrading the hosts to 6.7 just yet.

In the event of a failure, our rollback plan is to restore a backup of the vCenter host VM - that is, this vCenter installed on a Windows Server VM. Is there any reason to assume the hosts won't function as expected, in the event that we roll back vCenter in this way?

 

Any advise would be appreciated, thanks in advance

↧

vCenter 7 GA, cannot edit VM "Notes"

May 7, 2020, 5:39 am
$
0
0

Heads up. In vCenter 7 GA, the "edit notes" function of a VM seems broken. You can click the "edit" link and the Edit windows will popup. But you cannot enter text. Deleting characters is possible but inserting/entering new characters is not. This bug existed in an early version of VCSA 6.7 and was long fixed. But now it's back it seems.

Tried this with two vCenter 7 instances in the lab and with various current browsers.

↧

VCSA 6.7 - Cannot Replace Certificate

May 7, 2020, 6:36 am
$
0
0

I successfully created a Let's Encrypt cert for my homelab vcenter server (6.7.0.43000). I installed VCSA  less than a week ago and all else is working correctly.  I uploaded the new cert to the VCSA appliance and ran the built in scripts in certificate manager to install it. However, I hit this error during that process and it rolled back to the original:

 

Previous MACHINE_SSL_CERT Subject Alternative Name does not match new MACHINE_SSL_CERTIFICATE Subject Alternative Name
Performing rollback of Machine SSL cert

 

The hostname of the server (vcenter.mydomain.mycountry) is exactly the same as the cert and the SAN is also identical. I checked the original cert and it also has the same format domain name as the SAN. Everything is correct, old and new, but this keep failing. Rebooted the server a few times, same error.

 

Also, tried a wildcard cert but got the exact same error. I read VMWare does not like wildcards, fair enough, but I'm not seeing how this is failing.

 

Posted first on the Let's Encrypt forums and they say the cert and SAN are correct. So where is the obstacle?

 

Thanks.

 

↧
Viewing all 3506 articles
Browse latest View live
Search
<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>