Quantcast
Channel: VMware Communities : All Content - All Communities
Viewing all 180329 articles
Browse latest View live

ESXI 6.5 root account

$
0
0

I have a bad feeling you all will tell me I am out of Luck but I have run into an issue.

 

I have an ESXi Hypervisor running at home.  It is the free version running on an older Dell PC I have.  I only really have 2 active VM's.  Several Months ago I installed 6.5 on this newer older Dell and moved my disks to the new system.  I got most things set up just like under 6.0 and left it alone.  I was going to show my son something in the ESXi interface when I tried to log in as root I could not.  I am 99.999% sure I have not been hacked and I have not changed the password.  When I looked online I see the issue of expiring password.  I assume that is what happened to the root account.  I am hoping there is a way to get into the box.  When I am at the console and hit the F2 key it prompts for a login.  My root password does not work there.  Any ideas?  I really do not want to lose my VM's and I know that one of the VM's is on the same drive as the boot drive.  Any recommendations or help would be greatly appreciated.   


Does VMware Workstation Pro 15 support Intel Processor Tracing (Intel PT)?

$
0
0

Does VMware Workstation Pro 15 support Intel Processor Tracing?

 

If yes then is this feature usable with a nested hypervisor?

RDS Farm Sizing

$
0
0

What is preferable for say 80 users, 1 rdsh server for 150 users using say 8 vcpus and 32gbm of ram, 2 rdsh users for 75 users per server say 4 vCPUs and 16gb of memory, or 4 rdsh server for 38 users a piece using say 2 vCPUs and 8gb of memory. In general should we create more rdsh servers for smaller numbers, or try to keep with higher numbers. My enviornment is growing, but in what I'm finding out is not normal. I am up to currently 15 different desktop pools or rdsh farms, all with less then 100 users assigned to them., some as small as just 5 desktops max being available.

 

The virutal desktops aspect is running  much better than in the past, but I'm seeing issues with too many people logging in at once, and trying to decide against a bigger rdsh server or more smaller ones.

Win10 LTSB build 1607 users can't change default apps

$
0
0

Can't seem to get anything to stick with changes to default applications within Windows 10. Is there a registry setting or config file that anyone has used to work past this?

I couldn't find anything on this build of the OS (1607 LTSB) there were some issues with the newest update build but nothing listed for this one.

 

Thanks in advance for any help.

SDDC MP - vCenter OS Credentials Missing

$
0
0

Hello there.

I'm totally new to vrops, so my question is probably stupid, but I can't solve it on my own.

I have 2 node HA vrops 6.6.1 cluster and VCSA 6.5u1e.

I installed SDDC MP 4.0 to test the vcenter appliance monitoring and it says in the SDDC documentation that vSphere adapter must be configured. And it is so in my case, the configuration of vSphere adapter was the first thing I made after the vrops deployment. Now according to the SDDC doc I should provide credentials for the VCSA guest OS:

Configure vCenter Server Health

Before you monitor the health for avCenter Server instance, you have to configure the vCenter Server in

your SDDC health solution.

Prerequisites

Verify that you have configured vCenter Server adapter and is running.

Procedure

1 From the Administration tab, click Solutions.

2 Click the edit gear icon, and click Add.

3 Enter the Instance settings text boxes, vCenter Server IP address, Credentials, and click Close.

4 To edit an object, under the Inventory Explorer, under the adapter instances, select an SDDC Health

adapter instance.

5 Search for a vCenter object and click the edit icon.

6 Edit the required text boxes or click the plus icon to add new credentials.

7 In the Manage Credential, enter the OS credentials.

For a Windows vCenter, enter the OS user name. For example, administrator. For a VCSA, enter the

local OS user name. For example, root, any user with a shell access.

8 Click OK.

Well, there are 2 SDDC adapters in the Inventory Explorer, however I can't see any vCenter objects:

1 (1).png

If I try to edit "vCenter Health" there is no option to provide any credentials:

2 (1).png

However I can see some info about VCSA services in the SDDS dashboard:

3 (1).png

Still I get the "SDDC Config Notification - vCenter OS Credentials Missing, Services may not be discovered for this vCenter. Please Configure the VC HOST OS Credential in Inventory Explorer" notification:

4.PNG

I don't know how SDDS gathered some info about vcenter appliance without credentials provided and I don't know how to specify that credentials

Well, for the test purposes, I had specified 'administrator@sso.domain' credentials for the vSphere adapter and it also has admin privileges for the guest photon OS of VCSA, so may be it is the reason why I can see info about vcenter appliance services, but, I guess I need to provide credentials for SDDC adapter.

 

P.S. vrops is breaking my mind.

Changing Windows 10 Registry setting in Base Image

$
0
0

Looking to improve Windows 10 login times.  It has been suggested that this Key might help.

 

HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\

Value name: FSIASleepTimeInMs

Value type: REG_DWORD

 

My question is which is the best way to apply it, as I'm not sure in what order a registry key would be applied.

 

We Apply Appstacks to a Base Image.

 

Should I apply the change in the Appstack, Base Image or both?

 

The Template for the Appstack was created from the Base Image but quite some time ago.

Experience with 6.7U1 ?

$
0
0

Hi,

 

Just after some peoples feed back. Has anyone done the 6.7U1 update? Any issues yet or bugs?

localaccounts.user.add command is missing, can't create local account on vcsa


vSphere 6.0.0 not seeing 82571EB Gigabit Ethernet Controller

$
0
0

host = ESXi  v6.0  build: 3380124

vSphere = 6.0.0  build: 3016447

 

 

0000:00:19.0 Network controller: Intel Corporation 82579V Gigabit Network Connection [vmnic0]

0000:03:00.0 Network controller: Intel Corporation 82571EB Gigabit Ethernet Controller [vmnic1]

0000:03:00.1 Network controller: Intel Corporation 82571EB Gigabit Ethernet Controller [vmnic2]

 

i added the 82571EB dual nic card to the host mobo. lspci command on ESXi shows it recognizes the card but under vSphere it only displays the management nic, vmnic0.

 

since ESXi recognizes the 82571EB card then i assume it has the correct drivers?

 

how do i get vSphere to see the 82571EB dual nic card so i can use it for my VM's

 

[!02.10.2016:update]

due to many host reboots while attempting to get a guest to use the passthru'd GPU geforce 770 all of a sudden i see the 82571EB showing up in Hardware->Network Adapters. i created "vSwitch1/VM Network 2" and added the dual ports to it. looks like i can now add them to my VMs.

 

ESXi software components show the nic driver as "e1000e driver 3.2.2.1-NAPI with firmware 0.13-4 5.11-2" which should work for the 82571EB. for whatever reason seems to be working now.

A/V scanning in Fusion 11.0

$
0
0

When using malware/Antivirus scanning in Fusion of external USB drives, or any network drive, is there an disadvantage of hooking the drive to the host first, and just share the folder, vs if the format is correct (eg NTFS formatted), connecting directly via Bridged mode?

 

or are there downsides? ie... perhaps Fusions shuts down unexpectedly, processes stop etc.. performance reduced, or possible data loss increasing if Read/Write is given?

Fusion is freezing after I upgraded Mac to Mojave

$
0
0

Hi, I need help. I upgraded my Mac to Mojave and now Windows 7 is freezing. I am using an older version of Fusion ( vers. 7.1.3). Is this my problem? My version won't work with Mojave? I tried to upgrade to Fusion 11, but I apparently can't upgrade to Fusion 11 from vers 7.1.3.

Any suggestions are appreciated. Thanks.

Can't use http when doing connect-viserver

$
0
0

Hi experts,

I am trying to use Connect-VIServer with http. Whatever server and username/password are specified, I always get the error below.

 

PowerCLI C:\> Connect-VIServer -Server 101.207.40.46 -Protocol http -User foo -Password ****

Connect-VIServer : 10/19/2018 1:18:47 AM        Connect-VIServer                The provided URI scheme 'http' is invalid; expected 'https'.

Parameter name: via

At line:1 char:1

+ Connect-VIServer -Server 101.207.40.46 -Protocol http -User foo -Pass ...

+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

    + CategoryInfo          : NotSpecified: (:) [Connect-VIServer], ViError

    + FullyQualifiedErrorId : Client20_ConnectivityServiceImpl_Reconnect_Exception,VMware.VimAutomation.ViCore.Cmdlets.Commands.ConnectVIServer

 

My PowerCLI configuration is below,

PowerCLI C:\> Get-PowerCLIConfiguration

 

 

Scope    ProxyPolicy     DefaultVIServerMode InvalidCertificateAction  DisplayDeprecationWarnings WebOperationTimeout

                                                                                                  Seconds

-----    -----------     ------------------- ------------------------  -------------------------- -------------------

Session  UseSystemProxy  Multiple            Unset                     True                       300

User                     Multiple

AllUsers                 Single              Unset

 

I believe it's something wrong with my local settings.

Could anybody point out what the root cause is?

 

Thanks.

Martin

Error about backend database

$
0
0

Successfully installed the appliance and linked two vCenter accounts.  Everything is green on the appliance website.  When I go to vmware.com support and click Skyline I get this error and not sure what it means:

 

There was an issue with validating your login credentials against our backend database.

k8s integration with NSX-T 2.3

$
0
0

Hi.

 

I have install k8s, I have three nodes, one is master,the others are work-node.

I install k8s step as below:

1. install docker

2. apt-get install -y kubelet=1.11.2-00 kubeadm=1.11.2-00 kubectl=1.11.2-00

3. install ovs

4. kubeadm init --kubernetes-version=v1.11.2

5. install nsx-t CNI

then all of nodes are reday.

root@k8s-master:/etc# kubectl get node

NAME         STATUS    ROLES     AGE       VERSION

k8s-master   Ready     master    5d        v1.11.2

k8s-node1    Ready     <none>    5d        v1.11.2

k8s-node2    Ready     <none>    5d        v1.11.2

 

6. then install NCP,  Change ncp-rc. kubectl apply -f ncp-rc, I have a question.

detail in attach.

 

I don't know how to resolve.

root@k8s-master:/etc# kubectl get pod

NAME                   READY     STATUS             RESTARTS   AGE

nsx-ncp-wt5g9          0/1       CrashLoopBackOff   11         29m

nsx-node-agent-c5dls   1/2       CrashLoopBackOff   703        1d

nsx-node-agent-fctch   1/2       CrashLoopBackOff   705        1d

Unable to re-add host into VDS.

$
0
0

Hello,

 

One of ESXi host in a cluster got disconnected, I am trying to re-add my host into VDS but its shows error as below.

 

"vDS operation failed on host local, Received SOAP response fault from [<cs p:00007efd7418e0b0, TCP:localhost:443>]: invokeHostTransactionCall Received SOAP response fault from [<cs p:0243f658, TCP:localhost:8307>]: invokeHostTransactionCall An error occurred during host configuration. got (vim.fault.PlatformConfigFault) exception".

 

 

Can any one please me to fix this issue.

 

 

Thanks in advance.


Delete host from "host" section

$
0
0

Hi ,

using ver 4.7 iv noticed that in administration tab --hosts

i have all of my esx server with some ips that i dont want to log .

id there a way to delete thoes host for the th LI?

 

Iv deselect the admin-administration-vsphere-my/vc-unchacked "Configure ESXI hosts logs to log Insight"

and i still can see the ESXI host at the hosr count.

 

please advice.

 

Regard,

Elad

Used space is much bigger than real used space

$
0
0

Hi All,

I have a VM, which is used about 400GB but in the datastore, it shows the VM used 1.98 TB of datastore. Now I want to run consolidation for this VM but there is not enough space to run. I have tried to delete all snapshots but there is no luck because, there's nothing in Snapshot Manager, just only "You are here". Via console of ESXi, it is shown as below:

esxi-1-ss.JPG

How can I solve this issue?

VDR Looping

$
0
0

I have a vdr backup that I need to recover a VM from.  My problem is that each maintenance cycle takes 3 days, and some of the index is corrupt.  So, In order to correct the index, I need to prevent maintenance from happening, so I can see the corrupt items and delete them.  But I can't do that because the indexing starts again immediately upon completing so there is never a window where I can see the items that need to be deleted.  Clicking stop does stop it (once), but it will immediately restart.

 

So, is there a way to prevent automatic indexing from happening?

 

Or can I set a maintenance schedule in a file on the command line?  It doesn't appear that I can change it while the task is running.

 

Any other suggestions on how I can get at this data?

 

Thanks in advance,

Kev.

Lots of "Deassert" messages about drives

$
0
0

I've got a whole lot of "Deassert" messages on my new install of ESXi:

 

SAS A 0: Config Error - DeassertGreen0Cable/InterconnectUnknown
Disk Drive Bay 1 Cable SAS B 0: Config Error - DeassertGreen0Cable/InterconnectUnknown
Disk Drive Bay 1 Drive 0: Drive Fault - DeassertGreen0StorageUnknown
Disk Drive Bay 1 Drive 0: In Critical Array - DeassertGreen0StorageUnknown
Disk Drive Bay 1 Drive 0: In Failed Array - DeassertGreen0StorageUnknown
Disk Drive Bay 1 Drive 0: Parity Check In Progress - DeassertGreen0StorageUnknown
Disk Drive Bay 1 Drive 0: Predictive Failure - DeassertGreen0StorageUnknown
Disk Drive Bay 1 Drive 0: Rebuild Aborted - DeassertGreen0StorageUnknown
Disk Drive Bay 1 Drive 0: Rebuild In Progress - DeassertGreen0StorageUnknown
Disk Drive Bay 1 Drive 1: Drive Fault - DeassertGreen0StorageUnknown
Disk Drive Bay 1 Drive 1: In Critical Array - DeassertGreen0StorageUnknown
Disk Drive Bay 1 Drive 1: In Failed Array - DeassertGreen0StorageUnknown
Disk Drive Bay 1 Drive 1: Parity Check In Progress - DeassertGreen0StorageUnknown
Disk Drive Bay 1 Drive 1: Predictive Failure - DeassertGreen0StorageUnknown
Disk Drive Bay 1 Drive 1: Rebuild Aborted - DeassertGreen0StorageUnknown
Disk Drive Bay 1 Drive 1: Rebuild In Progress - DeassertGreen0StorageUnknown
Disk Drive Bay 1 Drive 2: Drive Fault - DeassertGreen0StorageUnknown
Disk Drive Bay 1 Drive 2: In Critical Array - DeassertGreen0StorageUnknown
Disk Drive Bay 1 Drive 2: In Failed Array - DeassertGreen0StorageUnknown
Disk Drive Bay 1 Drive 2: Parity Check In Progress - DeassertGreen0StorageUnknown
Disk Drive Bay 1 Drive 2: Predictive Failure - DeassertGreen0StorageUnknown
Disk Drive Bay 1 Drive 2: Rebuild Aborted - DeassertGreen0StorageUnknown
Disk Drive Bay 1 Drive 2: Rebuild In Progress - DeassertGreen0StorageUnknown
Disk Drive Bay 1 Drive 3: Drive Fault - DeassertGreen0StorageUnknown
Disk Drive Bay 1 Drive 3: In Critical Array - DeassertGreen0StorageUnknown
Disk Drive Bay 1 Drive 3: In Failed Array - DeassertGreen0StorageUnknown
Disk Drive Bay 1 Drive 3: Parity Check In Progress - DeassertGreen0StorageUnknown
Disk Drive Bay 1 Drive 3: Predictive Failure - DeassertGreen0StorageUnknown
Disk Drive Bay 1 Drive 3: Rebuild Aborted - DeassertGreen0StorageUnknown
Disk Drive Bay 1 Drive 3: Rebuild In Progress - DeassertGreen0StorageUnknown
Disk Drive Bay 1 Drive 4: Drive Fault - DeassertGreen0StorageUnknown
Disk Drive Bay 1 Drive 4: In Critical Array - DeassertGreen0StorageUnknown
Disk Drive Bay 1 Drive 4: In Failed Array - DeassertGreen0StorageUnknown
Disk Drive Bay 1 Drive 4: Parity Check In Progress - DeassertGreen0StorageUnknown
Disk Drive Bay 1 Drive 4: Predictive Failure - DeassertGreen0StorageUnknown
Disk Drive Bay 1 Drive 4: Rebuild Aborted - DeassertGreen0StorageUnknown
Disk Drive Bay 1 Drive 4: Rebuild In Progress - DeassertGreen0StorageUnknown
Disk Drive Bay 1 Drive 5: Drive Fault - DeassertGreen0StorageUnknown
Disk Drive Bay 1 Drive 5: In Critical Array - DeassertGreen0StorageUnknown
Disk Drive Bay 1 Drive 5: In Failed Array - DeassertGreen0StorageUnknown
Disk Drive Bay 1 Drive 5: Parity Check In Progress - DeassertGreen0StorageUnknown
Disk Drive Bay 1 Drive 5: Predictive Failure - DeassertGreen0StorageUnknown
Disk Drive Bay 1 Drive 5: Rebuild Aborted - DeassertGreen0StorageUnknown
Disk Drive Bay 1 Drive 5: Rebuild In Progress - DeassertGreen0StorageUnknown
Disk Drive Bay 1 Drive 6: Drive Fault - DeassertGreen0StorageUnknown
Disk Drive Bay 1 Drive 6: In Critical Array - DeassertGreen0StorageUnknown
Disk Drive Bay 1 Drive 6: In Failed Array - DeassertGreen0StorageUnknown
Disk Drive Bay 1 Drive 6: Parity Check In Progress - DeassertGreen0StorageUnknown
Disk Drive Bay 1 Drive 6: Predictive Failure - DeassertGreen0StorageUnknown
Disk Drive Bay 1 Drive 6: Rebuild Aborted - DeassertGreen0StorageUnknown
Disk Drive Bay 1 Drive 6: Rebuild In Progress - DeassertGreen0StorageUnknown
Disk Drive Bay 1 Drive 7: Drive Fault - DeassertGreen0StorageUnknown
Disk Drive Bay 1 Drive 7: In Critical Array - DeassertGreen0StorageUnknown
Disk Drive Bay 1 Drive 7: In Failed Array - DeassertGreen0StorageUnknown
Disk Drive Bay 1 Drive 7: Parity Check In Progress - DeassertGreen0StorageUnknown
Disk Drive Bay 1 Drive 7: Predictive Failure - DeassertGreen0StorageUnknown
Disk Drive Bay 1 Drive 7: Rebuild Aborted - DeassertGreen0StorageUnknown
Disk Drive Bay 1 Drive 7: Rebuild In Progress - DeassertGreen0StorageUnknown
Disk Drive Bay 3 ROMB Battery 0: Failed - DeassertGreen0BatteryUnknown
Disk Drive Bay 3 ROMB Battery 0: Low - Deassert

 

 

What's really odd about these messages is I only have FOUR drives. I'm seeing messages about EIGHT drives here and they seem to just repeat through these various messages.

 

Are these real or could I be mising an update?

 

I installed a customized ESXi for the Dell R710 from the Dell website.

 

Thanks in advance

Virtualization Based Security (VBS) in vSphere 6.7

$
0
0

I've just upgraded to vSphere 6.7 Update 1 and one of the first things I wanted to start experimenting with is Virtualization Based Security (VBS) in my VMs. I have a Win2016 and Win2019 VM I have installed with hardware version 14 and VMware Tools 10338. Windows is patched with October 2018's updates.

 

I've read a few articles on enabling VBS but there are some discrepencies so I wanted to list the steps I followed to see if I am installing/configuring VBS correctly:

 

  1. Shut down VM and tick the "Enable" box next to Virtualization Based Security under VM options
  2. Power VM on
  3. In VM open gpedit.msc and browse to:

 

Computer Configuration > Administrative Templates > System > Device Guard > Turn On Virtualization Based Security - Set to Enable and configure options as follows:

 

Select Platform Security level                    :   Secure Boot and DMA Protection
Virtualization Based Protection of Code Integrity :   Enabled with UEFI lock
Credential Guard Configuration                    :   Enabled with UEFI lock

 

  4. Reboot server

  5. This is where I am confused. Some articles say you have to enable/install the Hyper-V feature and reboot (others don't mention enabling Hyper-V). On my one test VM I haven't installed Hyper-V yet but after completing up to step 4. above VBS appears to be working/running:

 

 

So my questions are, do I need to install/enable Hyper-V for VBS to work? On my second test VM I did install the Hyper-V feature and VBS looked identical to the screenshot above that shows VBS running.

 

So I'm confused, do I need to install/enable Hyper-V or can I just follow the first 4 steps above to get VBS installed and working correctly?

Viewing all 180329 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>