Finally upgraded to vCenter 6.7. However in working with the customization spec part of the Edit network "Use an application configured on the vCenter Server to generate an IP address" piece is greyed out. See capture. can anyone tell me why?

My apologies, TAM is Technical Account Manager which gets tag to Account (not VMware Account).

It is definitely not in your case.

Then Request feature would be your best chance.

I did try and be mindful of that, however in the end I've been able to parse a log file and make the information I've needed available through a text file.  I mentioned this in a support call about something else and was basically told that I should only mess with those files under their direction.  Oh well...

ok - I may open a case on this.  Thanks for the reply.

Bump

Has this issue been solved?

If not are there accurate instructions to disable Hyper-V and use Workstation?

I tried per previous discussion but no luck.

On the solution path using ms windows scheduler, you could use the ms windows schtasks command to execute a temporary ps script.

Powershell and schtasks as well, both have parameters for "interactive" in the meaning of what do show up in case the loggedon username matches with the run as user option set.

Be aware, a managed solution path with windows scheduler dependency is rather dificult.

$ScriptFile = "Yourfullpathandrandomfilename.ps1"

$lines = ''

$lines += '$CodeBlock=@'+"'`r`n"

$lines += "insert enc64 content here"+"`r`n"

$lines += "'" + '@'+"`r`n"

set-content -path $ScriptFile -value $lines -encoding ASCII

$hzpassword="password"

$hzuser="username"

$begintime="00:00"

$TaskName="Your random task name"

$PowershellFilePath="$PsHome\powershell.exe"

$Argument = "\"""+$PowershellFilePath +"\"" -WindowStyle Normal -NoLogo -NoProfile -Executionpolicy unrestricted -command \"""+$ScriptFile+"\"""

echo ${hzpassword} | schtasks.exe /create /f /tn "$Taskname" /tr $Argument /SC ONCE /SD "12/17/2019" /ST $begintime /RU ${hzuser} /RL HIGHEST

schtasks /Run /TN "$Taskname" /I

Hello Guys

I have vROPS 7.5 and need monitoring transaction Database Oracle. I installed EPO in Linux OS (Red Hat) but need to know if is possible monitoring the transaction of Database trought script in vrops.

Thanks for your help.

Regards

Sebastian

If Windows 7/10 VMs are being hosted by VMWare, is there any way to force all existing applications running on Windows to use VMCI sockets instead of the Windows' socket library?  Want to speed up network communication between VM hosts.

Does anyone have experience applying a QoS Policy for the Skype for Business Optimization Pack? We can apply it to physical Windows devices using Group Policy but also need to apply it to our Windows Thin Client's that are not managed by GPO and do not have Skype installed locally.

I was able to apply the policy locally I confirmed the file vmware-remotemks.exe is the file being used during Skype calls but the file is not being tagged during the calls.

I am having the same issue. The CMID is not changing each pool created has the an unique CMID for the pool.

How do we get Windows 10 to activate using the KMS server? Is there a way?

I've been trying to use the Add-AppxProvisionedPackage to do just that but it hasn't exactly been working properly. The last time I tried it was complaining about a license issue.

Cloud builder installed 100% correctly and has been an ongoing environment for the last 6 months.

- Aware of the licensing issue and it was not in the .json file.

I will have a look at logs.

Hello folks,

I have two installations with vCenter installed on them that are both doing something that seems peculiar.  They send DNS queries from the vCenter IP address to the assigned DNS servers.  Roughly 15% of the time, they will generate a query the same second with the same source port to both the primary and secondary DNS servers.  When this happens, the firewall logs that the vCenter server responds to the secondary DNS server's answer with an ICMP type 3 code 3 (port unreachable).  This clearly shouldn't be happening (the query to the secondary DNS server probably shouldn't even be happening).  Any ideas on why this would occur?

vCenter Server with an embedded Platform Services Controller

v6.7.0.30000

Build 13010631

Example firewall log entries:

access-list vm_interface_access_in permitted udp vm-interface/10.1.1.5(33201) -> dc_interface/10.1.3.1(53)

access-list vm_interface_access_in permitted udp vm-interface/10.1.1.5(33201) -> dc_interface/10.1.3.2(53)

No matching connection for ICMP error message:  icmp src vm_interface:10.1.1.5 dst dc_interface:10.1.3.2 (type 3, code 3) on vm_interface.  Original IP payload:  udp src 10.1.3.2/53 dst 10.1.1.5/33201.

Thank you!

BrettMcAllstar:

Coincidentally, my context is a large financial institution too. Separation of duties, and therefore access, drives a lot of technical issues.

Did you ever get an answer or more information?

continuum did you have time to take a look?

I don't want to bother, sorry.

Hi

I assume you are searching for this flat.vmdk ?

# Disk DescriptorFile

version=1

encoding="UTF-8"

CID=eb9deacf

parentCID=ffffffff

isNativeSnapshot="no"

createType="vmfs"

# Extent description

RW 584843264 VMFS "IMDEAidinet-flat.vmdk"

# The Disk Data Base

#DDB

ddb.adapterType = "lsilogic"

ddb.geometry.cylinders = "36405"

ddb.geometry.heads = "255"

ddb.geometry.sectors = "63"

ddb.longContentID = "5cc4501ef58a0e8097a5299feb9deacf"

ddb.uuid = "0e be 5f e8 5f e8 e6 a9-a9 21 5e 31 0c 8b 9f f0"

Unfortunately the VMFS-metadata for that flat.vmdk has been deleted - there is no way to create a quick script to extract it again.

There is no unreferenced object of the expected size left in the VMFS-metadata.

As you are using esxi 6.5 with VMFS 5 this means that it looks like somebody deleted the file manually.

It may be possible to find the flat.vmdk with a scalpel - scan - according to the descriptorfile the vmdk was thick provisioned.

It probably was created in 2012 as one of the first objects inside that datastore so it may have been written in one piece.

A scalpel scan may take a day or more depending on the datastoresize ....

Maybe useful for further troubleshooting I attach a list with all the descriptorfiles I found.

Ulli

#################################################################

# Disk DescriptorFile

version=1

encoding="UTF-8"

CID=762c3b07

parentCID=ffffffff

isNativeSnapshot="no"

createType="vmfs"

# Extent description

RW 83886080 VMFS "Pruebas_0-flat.vmdk"

# The Disk Data Base

#DDB

ddb.adapterType = "lsilogic"

ddb.geometry.cylinders = "5221"

ddb.geometry.heads = "255"

ddb.geometry.sectors = "63"

ddb.longContentID = "5273f70a23f483689e3e96a6762c3b07"

ddb.thinProvisioned = "1"

#################################################################

# Disk DescriptorFile

version=1

encoding="UTF-8"

CID=40e185a1

parentCID=ffffffff

isNativeSnapshot="no"

createType="vmfs"

# Extent description

RW 584845312 VMFS "IDINET-Server-flat.vmdk"

# The Disk Data Base

#DDB

ddb.adapterType = "lsilogic"

ddb.encoding = "UTF-8"

ddb.geometry.biosCylinders = "36404"

ddb.geometry.biosHeads = "255"

ddb.geometry.biosSectors = "63"

ddb.geometry.cylinders = "36404"

#################################################################

# Disk DescriptorFile

version=1

encoding="UTF-8"

CID=1072a767

parentCID=ffffffff

isNativeSnapshot="no"

createType="vmfs"

# Extent description

RW 41943040 VMFS "RECUPERACION-flat.vmdk"

# The Disk Data Base

#DDB

ddb.adapterType = "lsilogic"

ddb.geometry.cylinders = "2610"

ddb.geometry.heads = "255"

ddb.geometry.sectors = "63"

ddb.longContentID = "4b22ae3ee5ea31d6968e67251072a767"

ddb.toolsInstallType = "0"

#################################################################

# Disk DescriptorFile

version=1

encoding="UTF-8"

CID=10a16e80

parentCID=e3a8e3af

isNativeSnapshot="no"

createType="vmfsSparse"

parentFileNameHint="IDINET-Server-000002.vmdk"

# Extent description

RW 584845312 VMFSSPARSE "IDINET-Server-000003-delta.vmdk"

# The Disk Data Base

#DDB

ddb.longContentID = "008be33ca90e2da6d42de2b510a16e80"

#################################################################

# Disk DescriptorFile

version=1

encoding="UTF-8"

CID=e0ba8572

parentCID=ba7ae9ca

isNativeSnapshot="no"

createType="vmfsSparse"

parentFileNameHint="IMDEAidinet-000002.vmdk"

# Extent description

RW 584843264 VMFSSPARSE "IMDEAidinet-000003-delta.vmdk"

# The Disk Data Base

#DDB

ddb.longContentID = "879206f9e977e60b80e3ad29e0ba8572"

#################################################################

# Disk DescriptorFile

version=1

encoding="UTF-8"

CID=0dc2e5de

parentCID=10a16e80

isNativeSnapshot="no"

createType="vmfsSparse"

parentFileNameHint="IDINET-Server-000003.vmdk"

# Extent description

RW 584845312 VMFSSPARSE "IDINET-Server-000004-delta.vmdk"

# The Disk Data Base

#DDB

ddb.longContentID = "e65104a8be034058eb37c7850dc2e5de"

ddb.toolsInstallType = "0"

ddb.toolsVersion = "0"

#################################################################

# Disk DescriptorFile

version=1

encoding="UTF-8"

CID=3e8991b1

parentCID=e0ba8572

isNativeSnapshot="no"

createType="vmfsSparse"

parentFileNameHint="IMDEAidinet-000003.vmdk"

# Extent description

RW 584843264 VMFSSPARSE "IMDEAidinet-000004-delta.vmdk"

# The Disk Data Base

#DDB

ddb.longContentID = "c7c71e2b2388a96cf5e4c09b3e8991b1"

ddb.toolsInstallType = "0"

ddb.toolsVersion = "0"

#################################################################

# Disk DescriptorFile

version=1

encoding="UTF-8"

CID=762c3b07

parentCID=ffffffff

isNativeSnapshot="no"

createType="vmfs"

# Extent description

RW 83886080 VMFS "Pruebas_0-flat.vmdk"

# The Disk Data Base

#DDB

ddb.adapterType = "lsilogic"

ddb.geometry.cylinders = "5221"

ddb.geometry.heads = "255"

ddb.geometry.sectors = "63"

ddb.longContentID = "5273f70a23f483689e3e96a6762c3b07"

ddb.thinProvisioned = "1"

ddb.uuid = "60 00 C2 9e eb bd 2a 97-30 5e 4f 5a 30 31 67 fa"

ddb.virtualHWVersion = "13"

#################################################################

# Disk DescriptorFile

version=1

encoding="UTF-8"

CID=514aa69f

parentCID=0dc2e5de

isNativeSnapshot="no"

createType="vmfsSparse"

parentFileNameHint="IDINET-Server-000004.vmdk"

# Extent description

RW 584845312 VMFSSPARSE "IDINET-Server-000006-delta.vmdk"

# The Disk Data Base

#DDB

ddb.longContentID = "9df4bfd7dc4118cc4e99037c514aa69f"

ddb.toolsInstallType = "1"

ddb.toolsVersion = "10272"

#################################################################

# Disk DescriptorFile

version=1

encoding="UTF-8"

CID=818bd5cc

parentCID=3e8991b1

isNativeSnapshot="no"

createType="vmfsSparse"

parentFileNameHint="IMDEAidinet-000004.vmdk"

# Extent description

RW 584843264 VMFSSPARSE "IMDEAidinet-000006-delta.vmdk"

# The Disk Data Base

#DDB

ddb.longContentID = "9c08b46915590de549856dc0818bd5cc"

ddb.toolsInstallType = "1"

ddb.toolsVersion = "10272"

#################################################################

# Disk DescriptorFile

version=1

encoding="UTF-8"

CID=12a8a791

parentCID=0dc2e5de

isNativeSnapshot="no"

createType="vmfsSparse"

parentFileNameHint="IDINET-Server-000004.vmdk"

# Extent description

RW 584845312 VMFSSPARSE "IDINET-Server-000005-delta.vmdk"

# The Disk Data Base

#DDB

ddb.longContentID = "04001db8b0ba1afb65ed7b2312a8a791"

#################################################################

# Disk DescriptorFile

version=1

encoding="UTF-8"

CID=d615ef9b

parentCID=3e8991b1

isNativeSnapshot="no"

createType="vmfsSparse"

parentFileNameHint="IMDEAidinet-000006.vmdk"

# Extent description

RW 584843264 VMFSSPARSE "IMDEAidinet-000005-delta.vmdk"

# The Disk Data Base

#DDB

ddb.longContentID = "dbcb63a08ccd4ed87228cac1d615ef9b"

#################################################################

# Disk DescriptorFile

version=1

encoding="UTF-8"

CID=40e185a1

parentCID=ffffffff

isNativeSnapshot="no"

createType="vmfs"

# Extent description

RW 584845312 VMFS "IDINET-Server-flat.vmdk"

# The Disk Data Base

#DDB

ddb.adapterType = "lsilogic"

ddb.encoding = "UTF-8"

ddb.geometry.biosCylinders = "36404"

ddb.geometry.biosHeads = "255"

ddb.geometry.biosSectors = "63"

ddb.geometry.cylinders = "36404"

ddb.geometry.heads = "255"

ddb.geometry.sectors = "63"

ddb.longContentID = "b7fff46c54805973d7cb9b0f40e185a1"

ddb.toolsInstallType = "1"

ddb.toolsVersion = "10272"

ddb.uuid = "60 00 C2 92 01 4a 86 a9-68 45 8b ee 4f 46 25 4d"

ddb.virtualHWVersion = "11"

#################################################################

# Disk DescriptorFile

version=1

encoding="UTF-8"

CID=eb9deacf

parentCID=ffffffff

isNativeSnapshot="no"

createType="vmfs"

# Extent description

RW 584843264 VMFS "IMDEAidinet-flat.vmdk"

# The Disk Data Base

#DDB

ddb.adapterType = "lsilogic"

ddb.geometry.cylinders = "36405"

ddb.geometry.heads = "255"

ddb.geometry.sectors = "63"

ddb.longContentID = "5cc4501ef58a0e8097a5299feb9deacf"

ddb.uuid = "0e be 5f e8 5f e8 e6 a9-a9 21 5e 31 0c 8b 9f f0"

ddb.virtualHWVersion = "4"

#################################################################

# Disk DescriptorFile

version=1

encoding="UTF-8"

CID=1072a767

parentCID=ffffffff

isNativeSnapshot="no"

createType="vmfs"

# Extent description

RW 41943040 VMFS "RECUPERACION-flat.vmdk"

# The Disk Data Base

#DDB

ddb.adapterType = "lsilogic"

ddb.geometry.cylinders = "2610"

ddb.geometry.heads = "255"

ddb.geometry.sectors = "63"

ddb.longContentID = "4b22ae3ee5ea31d6968e67251072a767"

ddb.toolsInstallType = "0"

ddb.toolsVersion = "0"

ddb.uuid = "60 00 C2 99 fe 3c 4c 1f-ef f5 af 55 1c ab eb 0b"

ddb.virtualHWVersion = "13"

#################################################################

# Disk DescriptorFile

version=1

encoding="UTF-8"

CID=c3289935

parentCID=40e185a1

isNativeSnapshot="no"

createType="vmfsSparse"

parentFileNameHint="IDINET-Server.vmdk"

# Extent description

RW 584845312 VMFSSPARSE "IDINET-Server-000001-delta.vmdk"

# The Disk Data Base

#DDB

ddb.longContentID = "cc734ff02fd013e1521fb40fc3289935"

#################################################################

# Disk DescriptorFile

version=1

encoding="UTF-8"

CID=4a6d8188

parentCID=eb9deacf

isNativeSnapshot="no"

createType="vmfsSparse"

parentFileNameHint="IMDEAidinet.vmdk"

# Extent description

RW 584843264 VMFSSPARSE "IMDEAidinet-000001-delta.vmdk"

# The Disk Data Base

#DDB

ddb.longContentID = "31cb2b237397d2b6a4da935e4a6d8188"

#################################################################

# Disk DescriptorFile

version=1

encoding="UTF-8"

CID=e3a8e3af

parentCID=c3289935

isNativeSnapshot="no"

createType="vmfsSparse"

parentFileNameHint="IDINET-Server-000001.vmdk"

# Extent description

RW 584845312 VMFSSPARSE "IDINET-Server-000002-delta.vmdk"

# The Disk Data Base

#DDB

ddb.longContentID = "9f48c5a657aad2842d254699e3a8e3af"

#################################################################

# Disk DescriptorFile

version=1

encoding="UTF-8"

CID=ba7ae9ca

parentCID=4a6d8188

isNativeSnapshot="no"

createType="vmfsSparse"

parentFileNameHint="IMDEAidinet-000001.vmdk"

# Extent description

RW 584843264 VMFSSPARSE "IMDEAidinet-000002-delta.vmdk"

# The Disk Data Base

#DDB

ddb.longContentID = "f1303c15681351fb971d244cba7ae9ca"

#################################################################

# Disk DescriptorFile

version=1

encoding="windows-1252"

CID=fec1c02a

parentCID=fec1c02a

isNativeSnapshot="no"

createType="twoGbMaxExtentSparse"

parentFileNameHint="imdeaenergia.dimdea.local.vmdk"

# Extent description

RW 18284544 SPARSE "imdeaenergia.dimdea.local-000001-s001.vmdk"

RW 18284544 SPARSE "imdeaenergia.dimdea.local-000001-s002.vmdk"

RW 18284544 SPARSE "imdeaenergia.dimdea.local-000001-s003.vmdk"

RW 18284544 SPARSE "imdeaenergia.dimdea.local-000001-s004.vmdk"

RW 18284544 SPARSE "imdeaenergia.dimdea.local-000001-s005.vmdk"

RW 18284544 SPARSE "imdeaenergia.dimdea.local-000001-s006.vmdk"

RW 18284544 SPARSE "imdeaenergia.dimdea.local-000001-s007.vmdk"

RW 18284544 SPARSE "imdeaenergia.dimdea.local-000001-s008.vmdk"

RW 18284544 SPARSE "imdeaenergia.dimdea.local-000001-s009.vmdk"

RW 18284544 SPARSE "imdeaenergia.dimdea.local-000001-s010.vmdk"

RW 18284544 SPARSE "imdeaenergia.dimdea.local-000001-s011.vmdk"

RW 18284544 SPARSE "imdeaenergia.dimdea.local-000001-s012.vmdk"

RW 18284544 SPARSE "imdeaenergia.dimdea.local-000001-s013.vmdk"

RW 18284544 SPARSE "imdeaenergia.dimdea.local-000001-s014.vmdk"

RW 18284544 SPARSE "imdeaenergia.dimdea.local-000001-s015.vmdk"

RW 18284544 SPARSE "imdeaenergia.dimdea.local-000001-s016.vmdk"

RW 18284544 SPARSE "imdeaenergia.dimdea.local-000001-s017.vmdk"

RW 18284544 SPARSE "imdeaenergia.dimdea.local-000001-s018.vmdk"

RW 18284544 SPARSE "imdeaenergia.dimdea.local-000001-s019.vmdk"

RW 18284544 SPARSE "imdeaenergia.dimdea.local-000001-s020.vmdk"

RW 18284544 SPARSE "imdeaenergia.dimdea.local-000001-s021.vmdk"

RW 18284544 SPARSE "imdeaenergia.dimdea.local-000001-s022.vmdk"

Hi Rick,

Sorry for the delay, I was out of the office for a few weeks.

I followed the steps below and attached the log.

1. I shutdown and then started the VM.

2. I launched Altium Designer, opened a project.

3. As it was trying to render the design I got an "Not Enough Memory" error reported by Altium.

Thanks for assitance.  If you need any other info or would like me to run some other tests let me know. 

Travis

Oh dear - thats  5 years ago - sorry I dont remember any details.

All I can say is that your do not have the same issue.

Your case may be trivial - maybe just a missing descriptor-vmdk or a syntax error.

So if you want help provide a list of all files in the VMs directory - to create such a list use ssh and putty and  run

ls -lah > filelist.txt

or create a screenshot of the display in WinSCP.

Make sure the list includes the full filenames, filesize and filedates for all objects.