Hi all,

1. I have extracted an OVA file simply using the 7-zip tool, I assume this is a correct way to do that?
2. Afterwards I edited the OVF file to get compatibility with VSphere.
3. Now I need to merge/import the three files together in 1 ova file, for this I assume I cannot use 7-zip, so I downloaded the ovf tool for Window

I can only find use cases / guides explaining how to use the ovf tool to convert a vmdk to a ova, but I doubt that this includes the mf and ovf file in that same folder.

How do I merge/import all three files to 1 ova?

Thank you very much!

Is anyone using T-shirt drop downs to set CPU, RAM, etc. in Blueprints/Catalog Items in ServiceNow?

If so, how are you doing it... manually configuring the Catalog Items in ServiceNow OR levering the plugin sync using some technique?

I am currently using vRA 7.5, London & vRA/SNOW Plugin V5.

Thanks in advance.

After about 49 days of uptime, the system process of my ESXi 6.7 U1 host (free version) is consuming a lot of CPU time:

By expanding GID 1 in esxtop, I find that a process called "OCFlush" is responsible for the high load.

Searching the web for OCFlush yields a post on reddit where people suppose this might be some kind of overflow, since 2^32 ms ≈ 49 days and 17 hours.

Is that a known bug? What is the purpose of OCFlush?

I have created a work-around and will share here, because this is an important (essential) capability to have.

Background

Question:  How do I set up VMWare Workstation 12.5 (running on a Windows host) to automatically suspend all guest VM's when the host OS shuts down or restarts?

I have read several posts on this over the years:  I know they exist, but none are helpful.

Fact:  Windows 10 will automatically apply updates and restart the machine whenever it feels like it, with little ability for the user to control or disable this behavior.

I am a developer and business user, and use VMWare Workstation (NOT Server) so that I can have multiple VM's open for various interactive purposes:  different development environments, different applications, etc.

If Windows 10 chooses to apply an update in my absence (which it regularly does, without my ability to prevent this from happening), this essentially halts all the running VM's, causing loss of work and potential data corruption.  This is entirely unacceptable.

To be clear, this is not a matter of convenience (i.e. that I am lazy and don't want to suspend the gust VM's before I explicitly shutdown), but is rather that the host OS may spontaneously shutdown or restart without my control.  Thus random loss of work and data is an inherent and regularly-encountered aspect of running VMWare Workstation 12.5 on a Windows 10 host.  There must be a way to correct this problem.

Should be Automatic

According to:  VMware Workstation 12 Pro Release Notes a new feature of VMWare Workstation Pro 12 was:  "Automatically suspend virtual machines upon host shutdown".  But this does not seem to actually work / to be present, and I can find no menu options or documentation pertaining to this feature.

PItfalls

A Windows "shutdown" script won't always work for Windows 10 because of the way fastboot works and because of other changes to the shutdown sequence in Windows 10 (not well-understood).  This means that old answers that say "Create a shutdown script...configure in GPO", etc. are not satisfactory.

Even disabling fastboot does not allow shutdown scripts to run reliably.  There are a number of potential factors, including whether or not you are booting the host from a VHD or from a physical disk, edition of Windows, etc.

Furthermore, even if you could get the shutdown script to run reliably, it may run too late in the shutdown sequence--after the applications, including VMWare Workstation have been terminated...which means that the Windows shutdown script approach is not a useful option.

Solution:  Create a Scheduled Task in Windows Task Scheduler

The heart of this work-around is to create a scheduled task using the Windows Task Scheduler.  The scheduled task should be triggered by certain system events (not by a specific time-of-day schedule).

There are several different events that must trigger this task, as some events apply to only certain shutdown sequences (i.e. command line-initiated, Windows UI initiated, power button, system updates, etc.)

The actual script to execute is below.

The scheduled task should have the following:

Launch "Task Scheduler"

Click on "Task Scheduler Library" treeview (left side of screen)

Click on "Create Task" in the Actions window (right side of screen)

Under "General" tab, provide an appropriate name

Under "General" tab, check:  "Run only when the user is logged on"

Under "General" tab, check:  "Run with highest privileges"

Under "Triggers", you will click "New" to add a new trigger, and will repeat this and the following settings 6 times (6 individual triggering events should be set).  For each:

"Begin the task:" should be set to "On an event"

Select the Log, and the Source, and type in the Event ID for each of the 6 events.  The rest of the settings on the screen can be left at their defaults.

Log:System

Source:User32

Event ID:1074

Log:  Microsoft-Windows-Winlogon/Operational

Source:Winlogon

Event ID:7002

Log:  Microsoft-Windows-Eventlog-ForwardingPlugin/Operational

Source:Eventlog-ForwardingPlugin

Event ID:6005

Log:  Microsoft-Windows-Eventlog-ForwardingPlugin/Operational

Source:Eventlog-ForwardingPlugin

Event ID:6006

Log:Security

Source:Microsoft Windows security auditing.

Event ID:4634

Log:Security

Source:Microsoft Windows security auditing.

Event ID:4647

Under "Actions" tab click "New", the default Action of "Start a program", and click Browse or type in the path to the batch file (see below for the batch file itself).

By using a scheduled task that is triggered by these events, it seems like Windows 10 does reliably launch the batch file at shutdown (or more technically correct, at user logoff).

Batch File

Create a batch file and save it somewhere on you local hard drive.  You can use Notepad to do this.  Name it something that ends in .bat (not .txt)...so when in Notepad you click Save, make sure "Save as file type" is set to "All Files (*.*)" so that Notepad does not append a .txt to the filename.

The contents of the file should be something like this:

@echo off

echo SuspendRunningVMs Command (x64)...

SETLOCAL

REM Specify where vmrun.exe can be located

SET WSPath="C:\Program Files (x86)\VMware\VMware Workstation"

REM Get the list of currently running VMs

%WSPath%\vmrun.exe list | FIND /V "Total running VMs:" > %temp%\vmlist.txt

REM Suspend all running VMs

FOR /F "delims=*" %%v IN (%temp%\vmlist.txt) DO CALL :SuspendVM "%%v"

:WaitLoop

echo Waiting for the VMs to suspend...

REM Pause until no more VMs are running

%WSPath%\vmrun.exe list | FIND "Total running VMs: 0"

IF NOT ERRORLEVEL 1 GOTO End

timeout /t 10 /nobreak

GOTO WaitLoop

:End

echo End of script; all VMs suspended.

ENDLOCAL

GOTO :EOF

REM Suspend a VM

:SuspendVM

REM Suspend any running VM.  Workaround a "vmrun list" quirk that outputs

REM a blank line, by not trying to suspend a blank VM

IF %1x==x GOTO :EOF

echo Suspending VM %1

%WSPath%\vmrun.exe suspend %1

REM Allow some time after suspend call (allow disk to write vmem).

echo Wait a little bit for the VM to commit...

timeout /t 15 /nobreak

GOTO :EOF

REM Resume a VM (not used now, but may have use in future)

:ResumeVM

REM Resume any suspended VM.  Workaround a "vmrun list" quirk that outputs

REM a blank line, by not trying to start a blank VM

IF %1x==x GOTO :EOF

echo Starting VM %1

%WSPath%\vmrun.exe start %1

GOTO :EOF

:EOF

Summary

I cannot understand how auto-suspend of all VM's upon shutdown of the Windows host has not been and is still not a built-in feature of VMWare Workstation running on Windows.  This seems to be critical to anyone who does not want to loose work and risk corrupting data in their VM's.  This need has intensified with Windows 10 as the host, because Windows will spontaneously reboot the computer when it applies updates, and Microsoft does not provide a way to prevent this spontaneous reboot from occurring.

Please, VMWare, make this capability a feature of future VMWare Workstation releases.  This is not a "server-only" feature:  even interactive users of VM's don't want to loose unsaved data and state of their virtual machines.

References

I did a lot of research on this, and was aided by a number of different posts from different people.  I will provide the URL's here:

Question about Task Scheduler during logoff event

https://social.technet.microsoft.com/Forums/en-US/a9eaa5ac-b772-4647-a0b1-72257cdc091a/windows-10-shutdown-scripts-not-always-running?forum=win10itprosetupWindows CMD Script to Aid Backups (esp. post #3)

Windows 10 Shutdown Scripts not always running

https://www.reddit.com/r/Windows10/comments/3yk73v/shutdown_script_called_via_local_machine_group

VMware Workstation 12 Pro Release Notes (see "Automatically suspend virtual machines upon host shutdown")

Improvement Suggestion: Suspend VMs Automatically On Host Log-off/Shut-down

We'd like to be able to post workflow status updates to the RITM. Assuming that the RITM ticket number is in the payload sent to vRO, does anyone know if and how to capture the RITM ticket number?

I just got a new job working overnight at a cloud provider, and while I've had plenty of experience with vCenter, I haven't had any exposure to vCloud before.  I've heard of some of the many ways to break vCloud when doing things in vCenter, so I'm rather nervous about doing anything now.  I don't want to lose this new job, obviously.  Most of my coworkers are more networking gurus, and have less experience than me in virtualization, so I've been asked to take on some of the more complicated virtualization tasks during off hours.  The lack of being able to ask coworkers who have experience with vCloud makes it a bit difficult to do some. 

So, onto the actual problem here.  I need to put a host in maintenance mode by Friday evening, so I have a little time to figure this one out.  It is one host out of 5 identical hosts in the cluster, and there is enough overall resources that two hosts can go down and still maintain all the VMs.  (Host 3 is the only one different, and that is exactly why I need to put it in maintenance mode.  A DIMM died, and we need to shut it down to replace the DIMM.)  When I put this one host in maintenance mode, it moved 6 of 7 the VMs to host #2, instead of spreading to the other hosts, and it seems to be refusing to move anything to host 1, even though it is completely empty.  There is still one last VM on there that vCloud refuses to move.  The DRS also seems to be ignoring hosts 4 and 5.  If I try to move it manually using vCenter, it gives me a warning that I shouldn't because it is managed in vCloud.  I don't see any way in vCloud to manage the hosts or cluster balancing, though. 

One big restriction: (might be obvious, but I think it bear mentioning) I can't power down any VMs without permission because they belong to the customer. 

So, should I just go ahead and move the VMs manually in vCenter?  Will this break vCloud, or does it seem like vCloud is already broken at this point?  What about host #2?  It has many more VMs that the other hosts, and probably needs to have some moved off of it, seeing as it is now at 96% memory usage. 

Thanks in advance.

Hi,

After I enabled the FlexEngine logoff command, it will sign me out immediately after entering my username and password. Did I miss anything? Thank you.

User Configuration > Windows Settings > Scripts> logoff

C:\Program Files\Immidio\Flex Profiles\FlexEngine.exe –s

Yazid-

Hey guys,

I hope someone can help me. We are running a VMware DaaS Environment. and Im trying to install the horizon agent silently with the following parameter: VMware-viewagent-x86_64-7.3.2-7161471.exe /s /v" /qn REBOOT=Reallysuppress VDM_VC_MANAGED_AGENT=1 ADDLOCAL=Core,ClientDriveRedirection,PCoIP,ThinPrint,USB,NGVC,RTAV,VmwVaudio,TSMMR"

If i remove the "ClientDriveRedirection" than the installation is running fine. If I add this, the setup failed with 1603. I tried to get a more detailed installation error on the logfile, but couldnt find out the reason. Is there some requirements to install the clientdriveredirection?

2019-03-12 21:47:42| BootStrapper-build-6133938| Begin Logging

2019-03-12 21:47:42| BootStrapper-build-6133938| Operating system info:

2019-03-12 21:47:42| BootStrapper-build-6133938|    Admin install = TRUE

2019-03-12 21:47:42| BootStrapper-build-6133938|    Major version = 10

2019-03-12 21:47:42| BootStrapper-build-6133938|    Minor version = 0

2019-03-12 21:47:42| BootStrapper-build-6133938|    Service pack  = 0

2019-03-12 21:47:42| BootStrapper-build-6133938|    Build number  = 17134

2019-03-12 21:47:42| BootStrapper-build-6133938|    Bitness       = 64-bit

2019-03-12 21:47:42| BootStrapper-build-6133938|    Platform      = NT

2019-03-12 21:47:42| BootStrapper-build-6133938| Running from: "C:\Program Files (x86)\Common Files\enteo\RepositoryCache\70011\rev\3\Extern$\VMware-viewagent-x86_64-7.3.2-7161471.exe"

2019-03-12 21:47:42| BootStrapper-build-6133938| [Resource] MINORUPGRADE = <not defined>

2019-03-12 21:47:42| BootStrapper-build-6133938| [Resource] PRODUCT_REG_NAME = <not defined>

2019-03-12 21:47:42| BootStrapper-build-6133938| Silent installation = TRUE

2019-03-12 21:47:42| BootStrapper-build-6133938| Upgrade at shutdown = FALSE

2019-03-12 21:47:42| BootStrapper-build-6133938| [Resource] SKIPADMINCHECK = <not defined>

2019-03-12 21:47:42| BootStrapper-build-6133938| [Resource] OPERATION = INSTALLUPD

2019-03-12 21:47:42| BootStrapper-build-6133938| [Resource] PRODUCTNAME = VMware Horizon Agent

2019-03-12 21:47:42| BootStrapper-build-6133938| [Resource] UPGRADECODE = {F85AD017-4794-4D0A-ADD2-0906AEC9B19D}

2019-03-12 21:47:42| BootStrapper-build-6133938| [Resource] PRODUCTCODE = {D7F189C9-2BCA-4E0B-A4FD-88427BC887EF}

2019-03-12 21:47:42| BootStrapper-build-6133938| [Resource] LANGUAGES = 1028 1031 1034 1036 1041 1042 2052

2019-03-12 21:47:42| BootStrapper-build-6133938| [Resource] VM_DATABASE64 = <not defined>

2019-03-12 21:47:42| BootStrapper-build-6133938| [Resource] VM_DATABASE = VMware Horizon Agent64.msi

2019-03-12 21:47:42| BootStrapper-build-6133938| [Resource] SFXINSERT = 1286144

2019-03-12 21:47:42| BootStrapper-build-6133938| [Resource] VMIOPTION = one

2019-03-12 21:47:42| BootStrapper-build-6133938| [Resource] CACHEMSI = <not defined>

2019-03-12 21:47:42| BootStrapper-build-6133938| [Resource] MINIMUM_9X_MSI = 200

2019-03-12 21:47:42| BootStrapper-build-6133938| [Resource] MINIMUM_NT_MSI = 300

2019-03-12 21:47:42| BootStrapper-build-6133938| [Resource] INSTMSIW = <not defined>

2019-03-12 21:47:42| BootStrapper-build-6133938| [Resource] VCRUNTIME32 = vcredist_x86.exe

2019-03-12 21:47:42| BootStrapper-build-6133938| [Resource] VCRUNTIME64 = vcredist_x64.exe

2019-03-12 21:47:42| BootStrapper-build-6133938| [Resource] VCRUNTIME32_ALT = vc_redist.x86.exe

2019-03-12 21:47:42| BootStrapper-build-6133938| [Resource] VCRUNTIME64_ALT = vc_redist.x64.exe

2019-03-12 21:47:42| BootStrapper-build-6133938| Current OS version = 10.0.

2019-03-12 21:47:42| BootStrapper-build-6133938| No need to install update KB2999226 for the current OS

2019-03-12 21:47:42| BootStrapper-build-6133938| [Resource] PROPERTIES = <not defined>

2019-03-12 21:47:42| BootStrapper-build-6133938| [Resource] OLDCODES =

2019-03-12 21:47:42| BootStrapper-build-6133938| [Resource] HELPER_UI = <not defined>

2019-03-12 21:47:42| BootStrapper-build-6133938| The user's default locale is 1031

2019-03-12 21:47:42| BootStrapper-build-6133938| Found an exact match, returning 1031

2019-03-12 21:47:42| BootStrapper-build-6133938| Total unpacked size will be 214 MB (223937155 bytes)

2019-03-12 21:47:42| BootStrapper-build-6133938| [Resource] REQ_MB_SPACE = <not defined>

2019-03-12 21:47:42| BootStrapper-build-6133938| Total space required to unpack is 351 MB (367290730 bytes)

2019-03-12 21:47:42| BootStrapper-build-6133938| Attempting to find best location for unpacking temporary installation files

2019-03-12 21:47:42| BootStrapper-build-6133938| Examining drive for temp folder "C:\Users\NETINS~1\AppData\Local\Temp\"

2019-03-12 21:47:42| BootStrapper-build-6133938| Local fixed drive C: has 44642 MB (46809829376 bytes) free

2019-03-12 21:47:42| BootStrapper-build-6133938| CurrentLocation "C:\Users\NETINS~1\AppData\Local\Temp\{D7F189C9-2BCA-4E0B-A4FD-88427BC887EF}~setup\"

2019-03-12 21:47:42| BootStrapper-build-6133938| Not a directory: 2 - C:\Users\NETINS~1\AppData\Local\Temp\{D7F189C9-2BCA-4E0B-A4FD-88427BC887EF}~setup\

2019-03-12 21:47:42| BootStrapper-build-6133938| Creating directory 'C:\Users\NETINS~1\AppData\Local\Temp\{D7F189C9-2BCA-4E0B-A4FD-88427BC887EF}~setup\'

2019-03-12 21:47:42| BootStrapper-build-6133938| Selecting "C:\Users\NETINS~1\AppData\Local\Temp\{D7F189C9-2BCA-4E0B-A4FD-88427BC887EF}~setup\" for unpacking temp files

2019-03-12 21:47:42| BootStrapper-build-6133938| Extracting setup files to "C:\Users\NETINS~1\AppData\Local\Temp\{D7F189C9-2BCA-4E0B-A4FD-88427BC887EF}~setup\"

2019-03-12 21:47:42| BootStrapper-build-6133938|   --> VMware Horizon Agent64.msi [39051264]

2019-03-12 21:47:42| BootStrapper-build-6133938|   --> vcredist_x86.exe [4485976]

2019-03-12 21:47:42| BootStrapper-build-6133938|   --> vcredist_x64.exe [5225304]

2019-03-12 21:47:42| BootStrapper-build-6133938|   --> vc_redist.x86.exe [14458272]

2019-03-12 21:47:42| BootStrapper-build-6133938|   --> vc_redist.x64.exe [15302984]

2019-03-12 21:47:42| BootStrapper-build-6133938|   --> Windows6.1-KB2999226-x64.msu [1034556]

2019-03-12 21:47:42| BootStrapper-build-6133938|   --> Windows6.1-KB2999226-x86.msu [629006]

2019-03-12 21:47:42| BootStrapper-build-6133938|   --> Windows8-RT-KB2999226-x64.msu [1359820]

2019-03-12 21:47:42| BootStrapper-build-6133938|   --> Windows8-RT-KB2999226-x86.msu [625544]

2019-03-12 21:47:42| BootStrapper-build-6133938|   --> Windows8.1-KB2999226-x64.msu [1005170]

2019-03-12 21:47:42| BootStrapper-build-6133938|   --> Windows8.1-KB2999226-x86.msu [603348]

2019-03-12 21:47:42| BootStrapper-build-6133938|   --> Core.cab [140155911]

2019-03-12 21:47:42| BootStrapper-build-6133938| IsMsiUpgradeNecessary: No upgrade is necessary. Windows Installer version 500 meets minimum requirements

2019-03-12 21:47:42| BootStrapper-build-6133938| [Resource] VCRUNTIME_VER = 9

2019-03-12 21:47:42| BootStrapper-build-6133938| [Resource] VCRUNTIME_VER_ALT = 14

2019-03-12 21:47:42| BootStrapper-build-6133938| Look for VC 9 x32 runtime libraries.

2019-03-12 21:47:42| BootStrapper-build-6133938| install state for product code {1F1C2DFC-2D24-3E06-BCB8-725134ADF989} = -1

2019-03-12 21:47:42| BootStrapper-build-6133938| install state for product code {9BE518E6-ECC6-35A9-88E4-87755C07200F} = 5

2019-03-12 21:47:42| BootStrapper-build-6133938| VC 9 x32 runtimes are already installed

2019-03-12 21:47:42| BootStrapper-build-6133938| Look for VC 9 x64 runtime libraries.

2019-03-12 21:47:42| BootStrapper-build-6133938| install state for product code {4B6C7001-C7D6-3710-913E-5BC23FCE91E6} = -1

2019-03-12 21:47:42| BootStrapper-build-6133938| install state for product code {5FCE6D76-F5DC-37AB-B2B8-22AB8CEDB1D4} = 5

2019-03-12 21:47:42| BootStrapper-build-6133938| VC 9 x64 runtimes are already installed

2019-03-12 21:47:42| BootStrapper-build-6133938| Look for VC 14 x32 runtime libraries.

2019-03-12 21:47:42| BootStrapper-build-6133938| install state for product code {37B55901-995A-3650-80B1-BBFD047E2911} = -1

2019-03-12 21:47:42| BootStrapper-build-6133938| install state for product code {844ECB74-9B63-3D5C-958C-30BD23F19EE4} = -1

2019-03-12 21:47:42| BootStrapper-build-6133938| VC 14 x32 runtime libraries need to be installed

2019-03-12 21:47:42| BootStrapper-build-6133938| VC 14 is being installed - we need to install KB2999226

2019-03-12 21:47:42| BootStrapper-build-6133938| ** InstallVCRedist [vc_redist.x86.exe][ /Q]

2019-03-12 21:47:42| BootStrapper-build-6133938| Found "C:\Users\NETINS~1\AppData\Local\Temp\{D7F189C9-2BCA-4E0B-A4FD-88427BC887EF}~setup\vc_redist.x86.exe"

2019-03-12 21:47:42| BootStrapper-build-6133938| Attempting to launch ""C:\Users\NETINS~1\AppData\Local\Temp\{D7F189C9-2BCA-4E0B-A4FD-88427BC887EF}~setup\vc_redist.x86.exe"  /Q"

2019-03-12 21:47:43| BootStrapper-build-6133938| Child exited with code 1638

2019-03-12 21:47:43| BootStrapper-build-6133938| Process returned 1638

2019-03-12 21:47:43| BootStrapper-build-6133938| vc redist returned ERROR_PRODUCT_VERSION (1638) - Another version of vc_redist 14 is already installed so we will skip the installation of vc_redist

2019-03-12 21:47:45| BootStrapper-build-6133938| Look for VC 14 x64 runtime libraries.

2019-03-12 21:47:45| BootStrapper-build-6133938| install state for product code {FAAD7243-0141-3987-AA2F-E56B20F80E41} = -1

2019-03-12 21:47:45| BootStrapper-build-6133938| install state for product code {F20396E5-D84E-3505-A7A8-7358F0155F6C} = -1

2019-03-12 21:47:45| BootStrapper-build-6133938| VC 14 x64 runtime libraries need to be installed

2019-03-12 21:47:45| BootStrapper-build-6133938| VC 14 is being installed - we need to install KB2999226

2019-03-12 21:47:45| BootStrapper-build-6133938| ** InstallVCRedist [vc_redist.x64.exe][ /Q]

2019-03-12 21:47:45| BootStrapper-build-6133938| Found "C:\Users\NETINS~1\AppData\Local\Temp\{D7F189C9-2BCA-4E0B-A4FD-88427BC887EF}~setup\vc_redist.x64.exe"

2019-03-12 21:47:45| BootStrapper-build-6133938| Attempting to launch ""C:\Users\NETINS~1\AppData\Local\Temp\{D7F189C9-2BCA-4E0B-A4FD-88427BC887EF}~setup\vc_redist.x64.exe"  /Q"

2019-03-12 21:47:45| BootStrapper-build-6133938| Child exited with code 1638

2019-03-12 21:47:45| BootStrapper-build-6133938| Process returned 1638

2019-03-12 21:47:45| BootStrapper-build-6133938| vc redist returned ERROR_PRODUCT_VERSION (1638) - Another version of vc_redist 14 is already installed so we will skip the installation of vc_redist

2019-03-12 21:47:48| BootStrapper-build-6133938| VerifyPackageSignature: Examining "C:\Program Files (x86)\Common Files\enteo\RepositoryCache\70011\rev\3\Extern$\VMware-viewagent-x86_64-7.3.2-7161471.exe": 4

2019-03-12 21:47:48| BootStrapper-build-6133938| VerifyPackageSignature: Verifying C:\Users\NETINS~1\AppData\Local\Temp\{D7F189C9-2BCA-4E0B-A4FD-88427BC887EF}~setup\\VMware Horizon Agent64.msi

2019-03-12 21:47:48| BootStrapper-build-6133938| IsVendorAppFromVersionInfo: Retrieving C:\Users\NETINS~1\AppData\Local\Temp\{D7F189C9-2BCA-4E0B-A4FD-88427BC887EF}~setup\\VMware Horizon Agent64.msi's vendor information using Version Info

2019-03-12 21:47:48| BootStrapper-build-6133938| IsVendorAppFromVersionInfo: Cannot get vendor name - no file ver info size (1812:Die angegebene Image-Datei enthält keinen Ressourcenabschnitt.)

2019-03-12 21:47:48| BootStrapper-build-6133938| IsVendorAppFromSummaryInfo: Get vendor name found from Summary Info

2019-03-12 21:47:48| BootStrapper-build-6133938| VerifyPackageSignature: C:\Users\NETINS~1\AppData\Local\Temp\{D7F189C9-2BCA-4E0B-A4FD-88427BC887EF}~setup\\VMware Horizon Agent64.msi is VMware's App - continue verification

2019-03-12 21:47:48| BootStrapper-build-6133938| VerifyPackageSignature: Examining "C:\Users\NETINS~1\AppData\Local\Temp\{D7F189C9-2BCA-4E0B-A4FD-88427BC887EF}~setup\\VMware Horizon Agent64.msi": 4

2019-03-12 21:47:48| BootStrapper-build-6133938| VerifyPackageSignature: C:\Program Files (x86)\Common Files\enteo\RepositoryCache\70011\rev\3\Extern$\VMware-viewagent-x86_64-7.3.2-7161471.exe-C:\Users\NETINS~1\AppData\Local\Temp\{D7F189C9-2BCA-4E0B-A4FD-88427BC887EF}~setup\\VMware Horizon Agent64.msi certificates are different

2019-03-12 21:47:48| BootStrapper-build-6133938| VerifyPackageSignature: Verifying C:\Users\NETINS~1\AppData\Local\Temp\{D7F189C9-2BCA-4E0B-A4FD-88427BC887EF}~setup\VMware Horizon Agent64.msi

2019-03-12 21:47:48| BootStrapper-build-6133938| IsVendorAppFromVersionInfo: Retrieving C:\Users\NETINS~1\AppData\Local\Temp\{D7F189C9-2BCA-4E0B-A4FD-88427BC887EF}~setup\VMware Horizon Agent64.msi's vendor information using Version Info

2019-03-12 21:47:48| BootStrapper-build-6133938| IsVendorAppFromVersionInfo: Cannot get vendor name - no file ver info size (1812:Die angegebene Image-Datei enthält keinen Ressourcenabschnitt.)

2019-03-12 21:47:48| BootStrapper-build-6133938| IsVendorAppFromSummaryInfo: Get vendor name found from Summary Info

2019-03-12 21:47:48| BootStrapper-build-6133938| VerifyPackageSignature: C:\Users\NETINS~1\AppData\Local\Temp\{D7F189C9-2BCA-4E0B-A4FD-88427BC887EF}~setup\VMware Horizon Agent64.msi is VMware's App - continue verification

2019-03-12 21:47:48| BootStrapper-build-6133938| VerifyPackageSignature: Examining "C:\Users\NETINS~1\AppData\Local\Temp\{D7F189C9-2BCA-4E0B-A4FD-88427BC887EF}~setup\VMware Horizon Agent64.msi": 4

2019-03-12 21:47:48| BootStrapper-build-6133938| VerifyPackageSignature: C:\Program Files (x86)\Common Files\enteo\RepositoryCache\70011\rev\3\Extern$\VMware-viewagent-x86_64-7.3.2-7161471.exe-C:\Users\NETINS~1\AppData\Local\Temp\{D7F189C9-2BCA-4E0B-A4FD-88427BC887EF}~setup\VMware Horizon Agent64.msi certificates are different

2019-03-12 21:47:48| BootStrapper-build-6133938| VerifyPackageSignature() returned: 0

2019-03-12 21:47:48| BootStrapper-build-6133938| Setting Internal UI level to 2

2019-03-12 21:47:48| BootStrapper-build-6133938| CommandLine Properties = ""

2019-03-12 21:47:48| BootStrapper-build-6133938| Checking for existing product {D7F189C9-2BCA-4E0B-A4FD-88427BC887EF}

2019-03-12 21:47:48| BootStrapper-build-6133938| No existing products found

2019-03-12 21:47:48| BootStrapper-build-6133938| The product code {D7F189C9-2BCA-4E0B-A4FD-88427BC887EF} is unknown. Use first time install logic.

2019-03-12 21:47:48| BootStrapper-build-6133938| MSI logging to "C:\Users\NETINS~1\AppData\Local\Temp\vmmsi.log"

2019-03-12 21:47:48| BootStrapper-build-6133938| CWD is now "C:\Users\NETINS~1\AppData\Local\Temp\{D7F189C9-2BCA-4E0B-A4FD-88427BC887EF}~setup\"

2019-03-12 21:47:48| BootStrapper-build-6133938| Calling InstallProduct():

2019-03-12 21:47:48| BootStrapper-build-6133938|   MSI file  : "C:\Users\NETINS~1\AppData\Local\Temp\{D7F189C9-2BCA-4E0B-A4FD-88427BC887EF}~setup\VMware Horizon Agent64.msi"

vdmInstUtil: 03/12/19 21:47:49 Begin Logging

vdmInstUtil: 03/12/19 21:47:49 --- VMResetRegSecurity()

vdmInstUtil: 03/12/19 21:47:49 Getting property Version9X =

vdmInstUtil: 03/12/19 21:47:49 --- CA: VMResetRegSecurity

vdmInstUtil: 03/12/19 21:47:49 Reseting security for HKLM\SOFTWARE\VMware, Inc.

vdmInstUtil: 03/12/19 21:47:49 Getting property PRODUCT_REG_NAME = VMware VDM

vdmInstUtil: 03/12/19 21:47:49 Reseting security for HKLM\SOFTWARE\VMware, Inc.\VMware VDM

vdmInstUtil: 03/12/19 21:47:49 Begin Logging

vdmInstUtil: 03/12/19 21:47:49 --- CA exec: VMCheckWindowsFIPSMode

vdmInstUtil: 03/12/19 21:47:49 End Logging

vdmInstUtil: 03/12/19 21:47:49 Begin Logging

vdmInstUtil: 03/12/19 21:47:49 --- VMSetFQHN()

vdmInstUtil: 03/12/19 21:47:49 FQHN = '***-VM-TMPL3.***-systeme.intra'

vdmInstUtil: 03/12/19 21:47:49 Setting property: VM_FQHN = ***-VM-TMPL3.***-systeme.intra

vdmInstUtil: 03/12/19 21:47:49 Begin Logging

vdmInstUtil: 03/12/19 21:47:49 --- VMAppSearch()

vdmInstUtil: 03/12/19 21:47:49 Getting property Version9X =

vdmInstUtil: 03/12/19 21:47:49 Service start type: 3

vdmInstUtil: 03/12/19 21:47:49 Setting property SVC_STARTTYPE_INITIAL_PERFHOST = 3

vdmInstUtil: 03/12/19 21:47:49 Getting property Version9X =

vdmInstUtil: 03/12/19 21:47:49 Service uxsms could not be opened! Error: 00000424

vdmInstUtil: 03/12/19 21:47:49 Setting property SVC_STARTTYPE_INITIAL_UXSMS.9BC9DCAA_DD96_44B1_BC29_6E3802296C2D =

vdmInstUtil: 03/12/19 21:47:49 Getting property Version9X =

vdmInstUtil: 03/12/19 21:47:49 Service stisvc was found by name.

vdmInstUtil: 03/12/19 21:47:49 Service stisvc found with exe path "C:\Windows\system32\svchost.exe -k imgsvc".

vdmInstUtil: 03/12/19 21:47:49 Setting property SVC_WINDOWS_IMAGE_ACQUISITION = C:\Windows\system32\svchost.exe -k imgsvc

vdmInstUtil: 03/12/19 21:47:49 C:\Windows\system32\svchost.exe -k imgsvc service exists and SVC_WINDOWS_IMAGE_ACQUISITION set

vdmInstUtil: 03/12/19 21:47:49 End Logging

vdmInstUtil: 03/12/19 21:47:49 Begin Logging

vdmInstUtil: 03/12/19 21:47:49 --- CA exec: VMSetVDM_LOOPBACK_IP

vdmInstUtil: 03/12/19 21:47:49 Getting Property VDM_IP_PROTOCOL_USAGE = IPv4

vdmInstUtil: 03/12/19 21:47:49 Setting property: VDM_LOOPBACK_IP =

vdmInstUtil: 03/12/19 21:47:49 localhost IPv4 address is 127.0.0.1

vdmInstUtil: 03/12/19 21:47:49 localhost IPv6 address is ::1

vdmInstUtil: 03/12/19 21:47:49 Setting property: VDM_LOOPBACK_IP = 127.0.0.1

vdmInstUtil: 03/12/19 21:47:49 End Logging

vdmInstUtil: 03/12/19 21:47:49 Begin Logging

vdmInstUtil: 03/12/19 21:47:49 --- VMCheckRunningInVm()

vdmInstUtil: 03/12/19 21:47:49 The installation is done in a VMware VM.

vdmInstUtil: 03/12/19 21:47:49 Setting property VM = VMware

vdmInstUtil: 03/12/19 21:47:49 End Logging

vdmInstUtil: 03/12/19 21:47:49 Begin Logging

vdmInstUtil: 03/12/19 21:47:49 --- CA exec: VMCheckWindowsUpdateProgress

vdmInstUtil: 03/12/19 21:47:49 Setting property: VDM_WINDOWS_UPDATE_IN_PROGRESS =

vdmInstUtil: 03/12/19 21:47:49 ERROR: IUpdateInstaller::get_IsBusy() failed. Return value: 0x80070422. Der angegebene Dienst kann nicht gestartet werden. Er ist deaktiviert oder nicht mit aktivierten Geräten verbunden.

vdmInstUtil: 03/12/19 21:47:49 Setting property: VDM_WINDOWS_UPDATE_IN_PROGRESS = -1

vdmInstUtil: 03/12/19 21:47:49 Begin Logging

vdmInstUtil: 03/12/19 21:47:49 --- VMCheckForClientSession()

vdmInstUtil: 03/12/19 21:47:49 End Logging

vdmInstUtil: 03/12/19 21:47:49 Begin Logging

vdmInstUtil: 03/12/19 21:47:49 --- CA exec: VMSetVCManaged

vdmInstUtil: 03/12/19 21:47:49 Getting Property VDM_VC_MANAGED_AGENT = 1

vdmInstUtil: 03/12/19 21:47:49 Running in a VMware VM

vdmInstUtil: 03/12/19 21:47:49 VMX_TYPE_SCALABLE_SERVER

vdmInstUtil: 03/12/19 21:47:49 Setting property VDM_VC_MANAGED_AGENT = 1

vdmInstUtil: 03/12/19 21:47:49 End Logging

2019-03-12 21:47:49| instUtils-build-5597633| Begin Logging

2019-03-12 21:47:49| instUtils-build-5597633| VMSetRealVersionNT running

2019-03-12 21:47:49| instUtils-build-5597633| Setting property VersionNT = 1000

2019-03-12 21:47:49| instUtils-build-5597633| Getting Property VersionNT64 = 1000

2019-03-12 21:47:49| instUtils-build-5597633| Setting property VersionNT64 = 1000

2019-03-12 21:47:49| instUtils-build-5597633| VMSetRealVersionNT Done

2019-03-12 21:47:49| instUtils-build-5597633| End Logging

vdmInstUtil: 03/12/19 21:47:49 Begin Logging

vdmInstUtil: 03/12/19 21:47:49 --- VMCheckSanPolicy()

vdmInstUtil: 03/12/19 21:47:50 Setting property: VDS_SAN_POLICY = 1

vdmInstUtil: 03/12/19 21:47:50 Begin Logging

vdmInstUtil: 03/12/19 21:47:50 --- VMCheckReboot()

vdmInstUtil: 03/12/19 21:47:50 Getting property SUPPRESS_RUNONCE_CHECK =

vdmInstUtil: 03/12/19 21:47:50 File/directory does not exist: "C:\Users\NETINS~1\AppData\Local\Temp\vmreboot.tmp"

vdmInstUtil: 03/12/19 21:47:50 INFO: Installation doesn't require a reboot

2019-03-12 21:47:51| BootStrapper-build-6133938| InstallProduct() returned: 1603

2019-03-12 21:47:51| BootStrapper-build-6133938| Util_NeedReboot: Checking if we need to reboot

2019-03-12 21:47:51| BootStrapper-build-6133938| Did not find file/directory: "C:\Users\NETINS~1\AppData\Local\Temp\\vmreboot.tmp"

2019-03-12 21:47:51| BootStrapper-build-6133938| The reboot file does not exist

2019-03-12 21:47:51| BootStrapper-build-6133938| Did not find file/directory: "C:\Users\NETINS~1\AppData\Local\Temp\\vmwareboot.tmp"

2019-03-12 21:47:51| BootStrapper-build-6133938| The reboot file does not exist

2019-03-12 21:47:51| BootStrapper-build-6133938| Util_NeedReboot: Reboot not needed.

2019-03-12 21:47:51| BootStrapper-build-6133938| Returned to [C:\Program Files (x86)\Common Files\enteo\RepositoryCache\70011\rev\3\Extern$]

2019-03-12 21:47:51| BootStrapper-build-6133938| Cleaning up temp dir "C:\Users\NETINS~1\AppData\Local\Temp\{D7F189C9-2BCA-4E0B-A4FD-88427BC887EF}~setup\"

2019-03-12 21:47:51| BootStrapper-build-6133938| Deleting [C:\Users\NETINS~1\AppData\Local\Temp\{D7F189C9-2BCA-4E0B-A4FD-88427BC887EF}~setup\]

2019-03-12 21:47:51| BootStrapper-build-6133938| Setup exit code is: 1603

2019-03-12 21:47:51| BootStrapper-build-6133938| End Logging

 

hi gurus

as you can tell by my previous post, I am still new to this, I have never upgrade horizon but this will be my first, has anyone here have like a step by step process that I can follow ,so I don't screw up and it goes smoothly.

Thanks a bunch

upgraded to mojave on mac vmfusion is no longer working same problem as everyone else.

would greatly appreciate the help.

Hello!

I am playing around with the Data Grid in the New Custom forms Designer - more precisely with the "disks" Grid. What I found so far:

• Adding the Grid to the Forms I got this Error:

Schema fields [[is_clone, initial_location, volumeId, id, label, custom_properties, userCreated, storage_reservation_policy, capacity]] should match the default value fields [[is_clone, initial_location, volumeId, id, label, userCreated, storage_reservation_policy, capacity]].

Cause: there is no "custom_properties" Field in the Grid Layout

Solution: Look at the "Default" Value and remove the "custom_properties," from the Header and the "," bevor the capacity - in my case before the "80":

is_clone,initial_location,volumeId,id,label,custom_properties,userCreated,storage_reservation_policy,capacity

true,,0,1525072814859,Hard disk 1,,false,,80

is_clone,initial_location,volumeId,id,label,custom_properties,userCreated,storage_reservation_policy,capacity

true,,0,1525072814859,Hard disk 1,,false,80

• Using the "disks" Grid "breaks" any approval Policies based on Storage Size

Cause: If you add more disks to the Grid the Value of "Storage (GB)" will not be incremented

Solution: Well... its more a workaround since I have not found a way to pass the Values of a Data Grid to an vRO Action. I created a vRO Action which fills the "disks" Grid based on Values in the Custom Form (the size of the template base disks are Hardcoded):

• If you use an external vRO Action for the Grid Values the Return type of the Action must be "Array/Properties". In my Case the Action was not found if I use this return Type.

Cause: Bug?

Workaround: I changed the Return Type to "Array/String" and the Action was found in vRA. After I changed the Values Binding in the Custom Form, Saved the Blueprint and corrected the Return Type of the Action to Array/Properties.

I am working with a customer and they posed the below question:

1. Is there is a way to automate the pool deletion process with Powershell or PowerCli and to send out a report once the pool deletion completes?

Hi, guys,

I have a question:

Vcenter----->home---->inventory--->host and Clusters, I select an ESX host and ------->configuration----->storage adapter, we can see many LUNs from storage.

We usually right click the "Name" to change the name to match with what we see in stroage side.

file:///E:/1.jpg

now we present 90 LUNs to this ESX cluster.

I am wondering if there is any command we can change the device name?

I tried get-ScsiLun.....and I can get the HLU, but there is no "Name" in the outpur.........

would you help please point the right command?

many thanks in advance!

Hello,

Since a coupe of weeks we experience intermitted connectivity on a daily basis. Though not always on the same time, not always every day, though in the ESXi logs we see the following:

2019-03-13T20:06:20.426Z cpu2:2097220)igbn: indrv_UplinkReset:1447: indrv_UplinkReset : vmnic0 device reset started

2019-03-13T20:06:20.426Z cpu2:2097220)igbn: indrv_UplinkQuiesceIo:1411: Stopping I/O on vmnic0

2019-03-13T20:06:20.462Z cpu2:2097220)igbn: indrv_DeviceReset:2306: Device Resetting vmnic0

2019-03-13T20:06:20.462Z cpu2:2097220)igbn: indrv_ChangeState:326: vmnic0: change PF state from 2 to 8

2019-03-13T20:06:20.462Z cpu2:2097220)igbn: indrv_Stop:1890: stopping vmnic0

2019-03-13T20:06:20.462Z cpu2:2097220)igbn: indrv_ChangeState:326: vmnic0: change PF state from 8 to 4

2019-03-13T20:06:20.492Z cpu2:2097220)igbn: indrv_ChangeState:326: vmnic0: change PF state from 4 to 1

2019-03-13T20:06:20.492Z cpu2:2097220)igbn: indrv_ChangeState:326: vmnic0: change PF state from 1 to 20

2019-03-13T20:06:20.493Z cpu2:2097220)igbn: indrv_ChangeState:326: vmnic0: change PF state from 20 to 2

2019-03-13T20:06:20.493Z cpu2:2097220)igbn: indrv_UplinkStartIo:1393: Starting I/O on vmnic0

2019-03-13T20:06:20.507Z cpu2:2097220)igbn: indrv_UplinkReset:1464: indrv_UplinkReset : vmnic0 device reset completed

2019-03-13T20:06:27.426Z cpu2:2097220)NetqueueBal: 5032: vmnic0: device Up notification, reset logical space needed

2019-03-13T20:06:27.427Z cpu3:2212666)NetSched: 654: vmnic0-0-tx: worldID = 2212666 exits

2019-03-13T20:06:27.428Z cpu3:2224632)NetSched: 654: vmnic0-0-tx: worldID = 2224632 exits

2019-03-13T20:06:27.428Z cpu2:2097220)igbn: indrv_UplinkDisableCap:1114: Disable vmnic0 cap function 1

2019-03-13T20:06:27.428Z cpu2:2097220)igbn: indrv_UplinkDisableCap:1114: Disable vmnic0 cap function 4

...

In Syslog we see some more events related as the access switch in the datacenter reports an up/down event:

Hardware profile:

Cisco 3750 switch stack

Server hardware:

• Hypervisor:VMware ESXi, 6.7.0, 11675023
• Model:PowerEdge R720
• Processor Type:Intel(R) Xeon(R) CPU E5-2609 v2 @ 2.50GHz
• Logical Processors:8
• NICs:4
• Virtual Machines:22
• State:Connected
• Uptime:11 days

At this moment it is also unknown why VMNIC1 is not taking over the data stream as it is configured to become active when the primary link fails VMNIC0.

Any suggestions are welcome and if more information is required then let me know.

Regards,

Martin Meuwese

I'm using Workstation Player.

I have host as Windows 10 x64 and guest as Fedora 29 x64 and I have problems when I click on Maximize. When the guest operating system was not fully loaded (I'm using Mate) then it freezes and no reaction from the guest. If I wait enough time and the guest's desktop is fully loaded and then if I click on Maximize, then the background image will be in cascading style.

If I go to

System -> Preferences -> Look and Feel -> Appeareance -> Background and if I change the background it freezes sometimes and I can only Power Off the guest.

I don't know it it is related to Fedora or Maximizing the window or background, but it's quite annoying.

Any ideas

Installed ESXi 6.5U1, moved to Distributed Switch, configured it as a reference host by adding couple vMotion vmkernels and couple iSCSI vmkernels, updated DNS and NTP setting.  So the vmkernels were laid out like this:

vmk0 = management

vmk1 = vmotion1

vmk2 = vmotion2

vkm3 = iSCSI1

vmk4 = iSCSI2

Then created a Host Profile. Updated that Host Profile with a MOTDm attached back to the original host and remediate.  Within a minute the host went disconnected and would not ping. Checked console and it was NOT rebooting.  So I performed a reboot on the host and it boot back up with vmotion1 IP address as the management IP.  WTH!!!

Manually changed the IP back to the management IP, re-connected to vCenter and now vmk0 is deleted and the management IP is on vmk1.   So it looks like this now:

vmk1 = management

vmk2 = vmotion2

vkm3 = iSCSI1

vmk4 = iSCSI2

Found these articles but were all dated for 5.x environments.

VMware Knowledge Base

Host profile removing vmk0 management port | vKARPS

Took a look at the vmk order in the Host Profile and the management vmk is listed first, see attached pic.  So clueless at this point.

Anyone experienced the same?

Hi,

one of our VM stopped after this happened:

2019-03-12T13:54:49.042Z| vcpu-2| I125: Msg_Question:

2019-03-12T13:54:49.042Z| vcpu-2| I125: [msg.hbacommon.corruptredo] The redo log of 'name-000001.vmdk' is corrupted. If the problem persists, discard the redo log.

2019-03-12T13:54:49.042Z| vcpu-2| I125: ----------------------------------------

2019-03-12T13:58:49.399Z| vcpu-2| I125: Timing out dialog 50213563

2019-03-12T13:58:49.399Z| vcpu-2| I125: MsgQuestion: msg.hbacommon.corruptredo reply=0

2019-03-12T13:58:49.399Z| vcpu-2| E105: PANIC: Exiting because of failed disk operation.

2019-03-12T13:58:51.381Z| vcpu-2| W115: A core file is available in "/vmfs/volumes/58bfd14a-c3018463-6615-b4e10f0a7ae8/name/vmx-zdump.000"

2019-03-12T13:58:51.381Z| mks| W115: Panic in progress... ungrabbing

2019-03-12T13:58:51.381Z| mks| I125: MKS: Release starting (Panic)

2019-03-12T13:58:51.381Z| mks| I125: MKS: Release finished (Panic)

The snapshot was taken roughly 1 year ago. The vsphere was migrated from 5.5 to 6.5 few months after the snapshot was taken.

VM has a single 300 GB virtual disk assigned. The snapshot file size is 291.2 GB.

After the VM was stopped I tried to delete snapshot. It removed the snapshot from the snapshot manager, but the file is still on the datastore and vmx is pointing to it.

I tried to run consolidation of disks multiple times. It failed every time.

I tried to create a new snapshot and then delete all snapshots. It, similarly like before, removed the snapshot from the list in the snapshot manager, but kept the virtual drive.

Creating a clone of the VM failed as well.

There are now these files in the VM folder:

name-000001-delta.vmdk 

name-000001.vmdk

name-000002-delta.vmdk

name-000002.vmdk

name-000003-delta.vmdk

name-000003.vmdk

name-Snapshot3.vmsn

name-aux.xml

name-flat.vmdk

name.nvram

name.vmdk

name.vmsd

name.vmx

name.vmxf

vmmcores.gz

vmware-1.log

vmware-2.log                               

vmware-3.log

vmware-4.log

vmware-5.log                               

vmware.log

vmx-zdump.000

What should I do to fix the VM?

Добрый день!

Есть хранилище DELL SC3020. Был создан на нем LUN  для хранения виртуальных машин. Хранилище делала снэпшоты, после чего был переполнен LUN и виртуальная машина остановилась с ошибкой "The operation cannot be allowed at the current time because the virtual machine has a question pending: 'msg.hbacommon.outofspace:There is no more space for virtual disk '/vmfs/volumes/5c4b18ea-39e14e84-39e7-f4e9d4cf4810/AD/AD -000002.vmdk'. You might be able to continue this session by freeing disk space on the relevant volume, and clicking Retry. Click Cancel to terminate this sessio".  VCENTER не позволил увеличить LUN, пришлось через ESXI. Есть ли вообще смылс использовать снэпшоты на устройстве  DELL SC3020

Hi - Looking to do a query against all my datastores to find out what is at 90% used space but exclude a list of datastores from the output. I can't seem to get the content read in to exclude  my list and not sure what I am doing wrong. It seems like it should be a fairly easy script - any help is appreciated.

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

#powershell script to output the datastores that over over 90%used

#add datastores to be excluded

$exceptiondatastores = Get-Content C:\exceptiondatastores.txt <<this file contains a list of datastores as well as * at the end for wildcard

Get-Datastore |

Select Name, @{N='UsedPerc';E={($_.CapacityGB - $_.FreeSpaceGB)/$_.CapacityGB}} |

where{$_.'UsedPerc' -ge 0.90  -and $_.Name -notmatch $exceptiondatastores} |

Select Name -expandproperty Name |Sort-Object -Property Name |

out-file  C:\diskusage90.txt

Disconnect-VIServer -Server xxxx -Confirm:$false

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