Fixes for 21 remote code execution (RCE) vulnerabilities included for products like Excel, Outlook, the Windows Graphics component, and the Windows TCP/IP stack.
Tag: vmware-workstation
Provisioned Server VDAs Are Unable to Boot After Restart
Customer was using VMware 6.5 Update 1, and targets were being affected by a known VMware issue:
PR 2323959: PXE booting of a virtual machine with a VMXNET3 virtual network device from a Citrix Provisioning Services (PVS) server might fail.
The issue has been fixed in 6.5 Update 3.
Related:
Operating System Fixup in XenCenter 5.6 or later OVF Appliance Plug-in
This article describes the Open Virtualization Format (OVF) Appliance Plug-in feature of XenCenter 5.6 and later. The OVF includes advanced hypervisor interoperability option Run Operating System Fixups.
Background
The OVF standard is composed of metadata and file elements that describe Virtual Machines (VMs), and additional information that is important to the deployment and operation of the applications in the OVF package.
Using OVF as a method of packaging does not guarantee cross hypervisor compatibility of the virtual machines. An OVF package created on one hypervisor might not automatically work on a different hypervisor. This happens for a variety of reasons including; different interpretations of the OVF specification, guest operating system devices, drivers, and implementations inherent to a hypervisor.
The Operating System Fixup feature in XenCenter 5.6 creates a basic level of interoperability for OVF packages that are imported to XenServer 5.6. The Fixup process addresses the operating system device and driver issue inherent when moving from one hypervisor to another. This is not designed to perform conversions from one platform to another.
Operating System Fixup Option
The Operating System Fixup is included with the XenCenter 5.6 installer as an automatically booting ISO image.
It can be enabled from the Advanced Options screen of the Appliance Import and Disk Image Import wizards in XenCenter.
The Operating System Fixup attempts to repair boot device related problems with the imported virtual system that might prevent the operating system within the virtual machine from booting.
It is important to understand how an appliance or disk image was created when deciding to use if the operating system fixup, or when diagnosing problems with booting a VM after import has completed.
Requirements for Operating System Fixup
An ISO Storage Repository (SR) for the OVF Appliance wizard to copy the Fixup ISO from the XenCenter administrative client machine to a location where XenServer can use it.
The ISO Storage Repository can be CIFS or NFS share with read/write permissions.
What does Operating System Fixup do to the Virtual Machine?
The Operating System Fixup option is designed to make the minimal changes possible to enable a virtual system to boot. Depending on the guest operating system and original hypervisor host, additional configuration changes, driver installation, or other actions might be required following using the fixup option.
During the Fixup process, an ISO is copied to an ISO SR. This ISO is attached to a virtual machine; the boot order is set to boot from the virtual DVD drive, and that virtual machine boots into the ISO. The environment within the ISO then checks each disk of the virtual machine to determine if it is a Linux or a Windows system.
If a Linux system is detected, then the location of the GRUB configuration file is determined and any pointers to SCSI disk boot devices are modified to point to IDE disks. For example, if GRUB contains an entry of /dev/sda1 representing the first disk on the first SCSI controller, this entry is changed to /dev/hda1 representing the first disk on the first IDE controller.
If a Windows system is detected, a generic critical boot device driver is extracted from the driver database of the installed operating system and registered with the operating system. This is especially important for older Windows operating systems when the boot device is changed between a SCSI and IDE interface. Also, if certain virtualization tool sets are discovered in the virtual machine, they are disabled to prevent performance problems and unnecessary event messages.
What Hypervisors has the OVF Appliance Wizard Imported Content From?
The hypervisors that the OVF Appliance Wizard has imported VMs from and applied the Operating System Fixup option to:
|
Tested Hypervisor VMs and Utilities |
Version |
Comments |
|
VMware Workstation |
6.5.x |
Delete VMware Tools from the VM to import if possible. |
|
VMware ESX |
3.5, 4.0 |
Delete VMware Tools from the VM to import if possible. |
|
VMware OVF Tool |
1.0 |
Delete VMware Tools from the VM to import if possible. |
|
VMware Studio |
1.0 |
Delete VMware Tools from the VM to import if possible. |
|
Sun Virtual Box |
3.x |
Delete Virtual Box Tools from the VM to import if possible. |
|
MS Virtual Server |
2005 SP1 |
Delete MS Tools from the VM to import if possible. |
|
MS Hyper-V |
2008, 2008 R2 |
Operating Systems that has the Operating System Fixup been Tested With
The Operating System Fixup option has been tested with the following operating systems:
| Windows | Linux |
|
Windows 2000 Advanced Server |
Debian 4, 5 |
*WIM disk image imports have only been tested with Windows operating systems.
Does the Operating System Fixup Repair all Problems?
There are differences among operating systems that cannot be repaired by the Fixup. It is also important to note that this is not a conversion process.
One example is: CentOS 5.3. The primary distribution media for CentOS 5.3 contains kernel revision 18. This kernel contains a bug that prevents it from migrating between SCSI and IDE boot devices; the bug is not fixed until kernel revision 28. The appliance cannot be repaired by the fixup because a new kernel could break numerous applications within the virtual machine because of kernel dependencies.
Operating System Fixup Expected Behavior with Different Operating Systems
The following tables identify the expected behavior when choosing to use or not to use the Operating System Fixup option. Success indicates that the VM booted and could be logged in to.
| Tested VM Imports with Fixups | Version | Comments |
| CentOS 4, 32 bit | 4 | |
| CentOS 5, 32 bit | 5 | Known kernel incompatibility 1 |
| CentOS 5, 64 bit | 5 | Known kernel incompatibility 1 |
| Debian 3 and 4, 32 bit | 4.0 (Etch) | Hangs at USB device detection, requires user hitting <Enter> 2 |
| Debian 5, 32 bit | 5.0 (Lenny) | |
| Red Hat Enterprise Linux, 32 bit | 4.8 | Fixups do not repair 3 |
| Red Hat Enterprise Linux, 32 bit | 5.3 | Fixups are optional 4 |
| Red Hat Enterprise Linux, 64 bit | 5.3 | Fixups are optional 4 |
| SuSE Linux Enterprise Server, 32 bit | 10 SP2 | |
| SuSE Linux Enterprise Server, 32 bit | 11 | |
| SuSE Linux Enterprise Server, 64 bit | 11 | |
| Oracle Enterprise Linux , 32 bit | 5 | |
| Oracle Enterprise Linux 64 bit | 5 | |
| Windows 2000 | Advanced Server SP4 | |
| Windows XP Professional | SP3 | |
| Windows Server 2003 | Enterprise Edition SP2 | |
| Windows Server 2003 x64 | Enterprise Edition SP2 | |
| Windows Vista | Enterprise Edition SP2 | Fixups are not necessary 5 |
| Windows Vista x64 | Enterprise Edition SP2 | Fixups are not necessary 5 |
| Windows Server 2008 | Enterprise Edition SP2 | Fixups are not necessary 5 |
| Windows Server 2008 x64 | Enterprise Edition SP2 | Fixups are not necessary 5 |
| Windows Server 2008 R2 (64 bit only) | Enterprise Edition | Fixups are not necessary 5 |
| Windows 7 32 bit | Ultimate | Fixups are not necessary 5 |
| Windows 7 64 bit | Ultimate | Fixups are not necessary 5 |
Notes
-
After importing a 64-bit CentOS 5.2 appliance to XenServer the appliance fails to boot with a repeating error that contains: “unable to read inode block”. There is a known problem with the CentOS kernel 2.6.18 that CentOS 5.x is based on causing this problem. Builds including and beyond 2.6.22 do not exhibit this problem. To upgrade the kernel, the appliance must be booted on the same type of hypervisor it was built on and the kernel must be updated to at least 2.6.22. Instructions can be found here.
-
A Debian based virtual machine guest imported from VMware will hang during the boot sequence loading the HID USB device. XenServer represents the keyboard and mouse as USB tablet devices. To resolve, install the XenServer Tools.
-
This contains a kernel that does not migrate to XenServer, nor handle hardware change. The recommendation is to not attempt import of this distribution but to build it on the hypervisor.
-
If the Red Hat distribution includes the Anaconda module; hardware change should be detected and device driver issues should be handled by the operating system.
-
Windows systems versions after Vista do not require fixups. Hardware detection within the operating system addresses device driver issues.
| Tested WIM Imports | Disk Controller | Selecting Fixups | Not selecting Fixups |
| Windows 7 Enterprise, x86 and x64 | SCSI | Success | Success |
| Windows 7 Enterprise, x86 and x64 | IDE | Success | Success |
| Windows Server 2008 R2 | SCSI | Success | Success |
| Windows Server 2008 R2 | IDE | Success | Success |
| Windows Vista SP2, x86 | SCSI | Success | Success |
| Windows Vista SP2, x86 | IDE | Success | Success |
| Windows Server 2008 SP2, x86 and x64 | SCSI | Success | Success |
| Windows Server 2008 SP2, x86 and x64 | IDE | Success | Success |
| Windows XP SP3, x86 | SCSI | Success | “Stop 0x0000007B” error |
| Windows 2003 R2, x86 | SCSI | Success | “Stop 0x0000007B” error |
| Windows 2008 R2, x64 *See the workaround noted in the following section. |
SCSI | “Stop 0x0000007B” error | “Stop 0x0000007B” error |
| Windows Server 2008 R2, x86 and x64 – Physical System | SATA | “Stop 0x0000007B” error | Success |
| Windows XP SP2, x86 and x64 – Physical System | SATA | “Stop 0x0000007B” error | Success |
Known Issues with Operating System Fixup
Windows Server 2003 R2 64-bit might not boot following import. A WIM import of the 64-bit version of Server 2003 might result in a STOP 7B error when the VM is booted.
The following workaround is required to repair a virtual machine that meets this scenario:
-
After importing the virtual appliance attach a WinPE x64 boot disk ISO to the VM (or use the Server 2003 installation media and drop to a command prompt).
-
Boot the VM.
-
At the WinPE console type the following command: chkdsk c: /f
-
When chkdsk is finished shut down the VM.
-
Eject the WinPE ISO.
-
Attach the xenserver-linuxfixup-disk.iso to the VM.
-
Start the VM.
The VM shuts down when the fixup process is complete and the ISO can be ejected.
CTX121908 – How to Enable Physical Volumes on HVM Linux Virtual Machines from VMware (SLES Debian)
CTX121737 – How to Use Kenso Open Virtualization Format Technology to Import VMware Appliances
CTX121616 – Error: Failed to start the X server (your graphical interface)
CTX121624 – How to Import Citrix Merchandising Server using XenConvert
CTX121621 – Repairing Debian after importing to XenServer from VMware
CTX121620 – Repairing X Windows on RedHat after importing to XenServer from VMware
CTX121619 – Repairing X Windows on CentOS after importing to XenServer from VMware
CTX124924 – How to Build a Reference Virtual Machine for Deployment from WIM
CTX124925 – Appliance Imported Virtual Machine Fails to Boot with STOP 7B or ‘Device Does Not Exist
Related:
7022955: DSfW: Unable to join Windows 10 version 1709 workstation to domain.
This document (7022955) is provided subject to the disclaimer at the end of this document.
Environment
Open Enterprise Server 2015 (OES 2015) Linux
Open Enterprise Server 2015 (OES 2015) Linux Support Pack 1
Open Enterprise Server 2018 (OES 2018) Linux
Open Enterprise Server 2015 (OES 2015) Linux Support Pack 1
Open Enterprise Server 2018 (OES 2018) Linux
Domain Services for Windows
DSfW
Situation
Attempting to join a Windows 10 workstation to a DSfW domain will fail in the following conditions:
- The Windows 10 workstation has the Fall Creators Update version 1709 installed.
- The Windows 10 workstation is a new installation of version 1709 or higher.
- The DSfW domain has not been updated to the 2008/2012 functional level. NOTE: In case the domain functional level has been raised, the join operation will succeed but it is not possible to access GPO’s, SYSVOL, or any other domain resources.
Resolution
In order to join the workstation to the domain, the SMBv1 feature on the Windows 10 workstation needs to be enabled using the add or remove programs method.
Details on how to do this can be found here
Cause
SMBv1 is not installed by default in Windows 10 Fall Creators Update and Windows Server, version 1709 and later versions. DSfW only supports SMBv1 at this time.
Additional Information
See the following links for more information from:
https://support.microsoft.com/en-us/help/4034314/smbv1-is-not-installed-by-default-in-windows
Disclaimer
This Support Knowledgebase provides a valuable tool for NetIQ/Novell/SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented “AS IS” WITHOUT WARRANTY OF ANY KIND.
Related:
Network applications holding connections to network share
I need a solution
Running SEP 14.2.770.0000 on Windows 10 workstation. During software development programs are copied from local workstation to network share. Application is executed from network share. After program stops execution for about 5 min time frame new versions of the application cannot be copied to the network share. Something has the files (exe’s and dll’s) still locked up an in use.
Tried various exclusions. Tried Disabling SEP. Only un-installing the Endpoint Protection fixes the problem. What is holding a lock on the program, it seems that it SEP 14.2 but even with the program disabled we still have issue. SEP is only loaded on workstation and not on network server. We did not have issue with version 14.0.3.
0
Related:
How to check SEP14 client package installer settings on a client
I need a solution
Hi All, does anyone know if there is a way to check on a host windows workstation if the Dark Network option was used in the installer for the SEP client?
Cheers
PaulC
0
Related:
7022687: Open Enterprise Server 2018 upgrade fails with blank screen when virtual machine hardware is set to old level
This document (7022687) is provided subject to the disclaimer at the end of this document.
Environment
VMware
Open Enterprise Server 2018 (OES 2018) Linux
Open Enterprise Server 2018 (OES 2018) Linux
Situation
When booting from the VMware-connected OES 2018 ISO file in the virtual drive, the system boots properly, the “Upgrade” option is selected, various items continue to load on the console, and then there is nothing but a black screen shown. In some cases, the virtual machine (VM) will not boot at all.
When checked, the VMware hardware compatibility level was set to four (4).
Resolution
Change the virtual machine (VM) hardware compatibility level to 5.1 (or later), and possible ensure that the display resolution is at least 1024×768 to resolve the issue.
Screenshot before the VMware configuration change:
Screenshot after the VMware configuration change:
Additional Information
VMware Compatibility List: https://docs.vmware.com/en/VMware-vSphere/6.5/com.vmware.vsphere.vm_admin.doc/GUID-789C3913-1053-4850-A0F0-E29C3D32B6DA.html
VMware’s hardware level setting list: https://kb.vmware.com/s/article/1003746
Disclaimer
This Support Knowledgebase provides a valuable tool for NetIQ/Novell/SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented “AS IS” WITHOUT WARRANTY OF ANY KIND.
Related:
A way to use NAT network by using Oracle virtualBox
That is true.
Vmware is easy and confortable tools to make vitrual machines than Oracle virtual box. But Oracle vitrual box is free to use and vmware needs to buy license.
Now, here is a way to use NAT network by using Oracle virtualBox.
I am sorry that my interface is chinese words. I can do to make them to be understand easily.
Yes, When you first time finish install Oracle virtual box , you just see one vitrual network card .
See the the rounded rectangle, it is exist after fininshing install on your host machine network setting area.
You also can see just only one host only network setting for each guests machine.
The red line is the original one.
If we were let it go, for example , we had created two guest machines “linux3” and “linux4”. The “linux3” guest ip is 10..0.2.15 and the “linux4” ip is 10.0.2.25.
Then we just add extra one more vbox host-only network card on vitrual box console, like yellow line marked.. The we can see the yellow rounded rectangle marked network adapter show on host machine.
After that., we just need to find this two guest machines network adapters setting and set NAT port mapping rule. Just as follows.
, 
After all that finished, we are suprised that we can ssh from host machine to Oracle vitrual machine box.guest machine.
so we can see:
Then problem solved.
Thanks
Related:
Re: Avamar VM backup fails
I am having a very odd problem in my vSphere 6.5 update 1 environment. When i try to run a on-demand backup, i see the snapshot being taken by the avamar user i setup in vSphere. However after 5 seconds the snapshot is removed and the backup fails. I am using Avamar version 7.1.2-21 and the proxy is version 7.1.102-21. I have verified the following:
1) nslookup of the host from the proxy is successful
2) port 443 is open to the vCenter, and port 902 is open for the host. I verified this by using the curl -kv command from the proxy to the host
3) I can log into vSphere as the avamar user, Storage vMotion, take multiple snapshots, and remove snapshots.
4) as the avamar user i am able to navigate to the VM files in the datastore
5) The avamar user has full admin rights at the highest level and is propagated down
This is the errors I am seeing:
2017-12-26 11:08:03 avvcbimage Error <0000>: [IMG0008] Failed to connect to virtual disk [DataStore2] VM_TEST_WORKSTATION/VM_TEST_WORKSTATION.vmdk (13) (13) You do not have access rights to this file (Log #1)
2017-12-26 11:08:03 avvcbimage Error <0000>: [IMG0008] VixDiskLib_Open([DataStore2]] VM_TEST_WORKSTATION/VM_TEST_WORKSTATION.vmdk) returned (13) You do not have access rights to this file (Log #1)
2017-12-26 11:08:04 avtar Info <7202>: Backup CANCELED, wrapping-up session with Server (Log #2)
2017-12-26 11:08:05 avvcbimage Error <0000>: [IMG0011] Avtar exited with ‘code 163: externally cancelled’ (Log #1)
2017-12-26 11:08:05 avtar FATAL <0000>: Backup ‘MOD-1514304411263’ to DDR not sealed due to previous errors2017-12-26 11:08:05 avtar Info 0000>: Entering the ‘final’ phase of termination, Fatal error enountered) (Log #2)
2017-12-26 11:08:05 avtar FATAL <5155>: Backup aborted due to earlier errors. No backup created on the server. (Log #2)
2017/12/26-16:08:04.57942 avtar DEBUG-ERROR <0001> backstreamdir::childdone error merging history stream data during phase_do_hidden while processing directory ‘VMFiles/ForceError-0’ (Log #2)
2017/12/26-16:08:04.69779 avtar DEBUG-ERROR <0001> backstreamdir::childdone error merging history stream data during phase_do_hidden while processing directory ‘VMFiles’ (Log #2)
2017/12/26-16:08:05.78554 avtar DEBUG-ERROR <0001> backstreamdir::childdone error merging history stream data during phase_do_hidden while processing directory ” (Log #2)
I also see this which I thought was weird:
2017-12-26 11:07:18 avvcbimage Info <0000>: [IMG0009] Pre-snapshot script: completed successfully
2017-12-26 11:07:18 avvcbimage Info <9692>: a VM snapshot has been requested
2017-12-26 11:07:18 avvcbimage Info <14627>: Creating snapshot ‘Avamar-1514304438dd479ddf05179a0e24945b8011b1dfc61a1eb87e’, quieceFS=1
2017-12-26 11:07:18 avvcbimage Info <14631>: Snapshot ‘Avamar-1514304438dd479ddf05179a0e24945b8011b1dfc61a1eb87e’ creation for VM ‘[DataStore2] VM_TEST_WORKSTATION/VM_TEST_WORKSTATION.vmx’ task still in progress, sleep for 2 sec
2017-12-26 11:07:20 avvcbimage Info <14631>: Snapshot ‘Avamar-1514304438dd479ddf05179a0e24945b8011b1dfc61a1eb87e’ creation for VM ‘[DataStore2] VM_TEST_WORKSTATION/VM_TEST_WORKSTATION.vmx’ task still in progress, sleep for 2 sec
2017-12-26 11:07:22 avvcbimage Info <14631>: Snapshot ‘Avamar-1514304438dd479ddf05179a0e24945b8011b1dfc61a1eb87e’ creation for VM ‘[DataStore2] VM_TEST_WORKSTATION/VM_TEST_WORKSTATION.vmx’ task still in progress, sleep for 2 sec
2017-12-26 11:07:24 avvcbimage Info <14631>: Snapshot ‘Avamar-1514304438dd479ddf05179a0e24945b8011b1dfc61a1eb87e’ creation for VM ‘[DataStore2] VM_TEST_WORKSTATION/VM_TEST_WORKSTATION.vmx’ task still in progress, sleep for 2 sec
2017-12-26 11:07:26 avvcbimage Info <14632>: Snapshot ‘Avamar-1514304438dd479ddf05179a0e24945b8011b1dfc61a1eb87e’ creation for VM ‘[DataStore2] VM_TEST_WORKSTATION/VM_TEST_WORKSTATION.vmx’ task completed, moref=snapshot-138
2017-12-26 11:07:26 avvcbimage Info <19680>: vmAction runBackupScript: ()
2017-12-26 11:07:26 avvcbimage Info <19681>: vmAction runBackupScript: script is skipped because it is null
2017-12-26 11:07:26 avvcbimage Info <0000>: [IMG0009] Post-snapshot script: completed successfully
Anyone have any suggestions?
Related:
Avamar VM backup fails
I am having a very odd problem in my vSphere 6.5 update 1 environment. When i try to run a on-demand backup, i see the snapshot being taken by the avamar user i setup in vSphere. However after 5 seconds the snapshot is removed and the backup fails. I am using Avamar version 7.1.2-21 and the proxy is version 7.1.102-21. I have verified the following:
1) nslookup of the host from the proxy is successful
2) port 443 is open to the vCenter, and port 902 is open for the host. I verified this by using the curl -kv command from the proxy to the host
3) I can log into vSphere as the avamar user, Storage vMotion, take multiple snapshots, and remove snapshots.
4) as the avamar user i am able to navigate to the VM files in the datastore
5) The avamar user has full admin rights at the highest level and is propagated down
This is the errors I am seeing:
2017-12-26 11:08:03 avvcbimage Error <0000>: [IMG0008] Failed to connect to virtual disk [DataStore2] VM_TEST_WORKSTATION/VM_TEST_WORKSTATION.vmdk (13) (13) You do not have access rights to this file (Log #1)
2017-12-26 11:08:03 avvcbimage Error <0000>: [IMG0008] VixDiskLib_Open([DataStore2]] VM_TEST_WORKSTATION/VM_TEST_WORKSTATION.vmdk) returned (13) You do not have access rights to this file (Log #1)
2017-12-26 11:08:04 avtar Info <7202>: Backup CANCELED, wrapping-up session with Server (Log #2)
2017-12-26 11:08:05 avvcbimage Error <0000>: [IMG0011] Avtar exited with ‘code 163: externally cancelled’ (Log #1)
2017-12-26 11:08:05 avtar FATAL <0000>: Backup ‘MOD-1514304411263’ to DDR not sealed due to previous errors2017-12-26 11:08:05 avtar Info 0000>: Entering the ‘final’ phase of termination, Fatal error enountered) (Log #2)
2017-12-26 11:08:05 avtar FATAL <5155>: Backup aborted due to earlier errors. No backup created on the server. (Log #2)
2017/12/26-16:08:04.57942 avtar DEBUG-ERROR <0001> backstreamdir::childdone error merging history stream data during phase_do_hidden while processing directory ‘VMFiles/ForceError-0’ (Log #2)
2017/12/26-16:08:04.69779 avtar DEBUG-ERROR <0001> backstreamdir::childdone error merging history stream data during phase_do_hidden while processing directory ‘VMFiles’ (Log #2)
2017/12/26-16:08:05.78554 avtar DEBUG-ERROR <0001> backstreamdir::childdone error merging history stream data during phase_do_hidden while processing directory ” (Log #2)
I also see this which I thought was weird:
2017-12-26 11:07:18 avvcbimage Info <0000>: [IMG0009] Pre-snapshot script: completed successfully
2017-12-26 11:07:18 avvcbimage Info <9692>: a VM snapshot has been requested
2017-12-26 11:07:18 avvcbimage Info <14627>: Creating snapshot ‘Avamar-1514304438dd479ddf05179a0e24945b8011b1dfc61a1eb87e’, quieceFS=1
2017-12-26 11:07:18 avvcbimage Info <14631>: Snapshot ‘Avamar-1514304438dd479ddf05179a0e24945b8011b1dfc61a1eb87e’ creation for VM ‘[DataStore2] VM_TEST_WORKSTATION/VM_TEST_WORKSTATION.vmx’ task still in progress, sleep for 2 sec
2017-12-26 11:07:20 avvcbimage Info <14631>: Snapshot ‘Avamar-1514304438dd479ddf05179a0e24945b8011b1dfc61a1eb87e’ creation for VM ‘[DataStore2] VM_TEST_WORKSTATION/VM_TEST_WORKSTATION.vmx’ task still in progress, sleep for 2 sec
2017-12-26 11:07:22 avvcbimage Info <14631>: Snapshot ‘Avamar-1514304438dd479ddf05179a0e24945b8011b1dfc61a1eb87e’ creation for VM ‘[DataStore2] VM_TEST_WORKSTATION/VM_TEST_WORKSTATION.vmx’ task still in progress, sleep for 2 sec
2017-12-26 11:07:24 avvcbimage Info <14631>: Snapshot ‘Avamar-1514304438dd479ddf05179a0e24945b8011b1dfc61a1eb87e’ creation for VM ‘[DataStore2] VM_TEST_WORKSTATION/VM_TEST_WORKSTATION.vmx’ task still in progress, sleep for 2 sec
2017-12-26 11:07:26 avvcbimage Info <14632>: Snapshot ‘Avamar-1514304438dd479ddf05179a0e24945b8011b1dfc61a1eb87e’ creation for VM ‘[DataStore2] VM_TEST_WORKSTATION/VM_TEST_WORKSTATION.vmx’ task completed, moref=snapshot-138
2017-12-26 11:07:26 avvcbimage Info <19680>: vmAction runBackupScript: ()
2017-12-26 11:07:26 avvcbimage Info <19681>: vmAction runBackupScript: script is skipped because it is null
2017-12-26 11:07:26 avvcbimage Info <0000>: [IMG0009] Post-snapshot script: completed successfully
Anyone have any suggestions?