Hello everyone,

I've been involved on a VMware Mirage project for several weeks and one of the use cases has been migrating user data from an old Win XP desktop to a new Windows 7 desktop:

- Old Desktop with Windows XP Pro 32 bit installed on it and centralized with Mirage.

- New Desktop with Windows 7 Pro 32 bit installed on it (as well as Mirage agent) located on pending devices (so, there is no base layer or nothing installed on that device).

As long as the destination device has no Base layer or app layers on it, we have had to perform a two-step procedure after centralizing the original device:

1. Migrate user data from XP to 7 using Hardware Migration Wizard.

2. Apply base layer and app layers.

Does anyone know if it could be possible to migrate user data and assign base layer to destination device on just one step?

By the way, user data restore has finished properly most of the times using the "Hardware Migration Wizard" (It failed once, Mirage said that restore was succesful but only the folders for every user where migrated to C:\Users on the Win 7 box, no files or folders inside of those folders were migrated). Has anyone else experienced this issue?

Thanks in advance.

Regards.

Hi,

I have successfully installed Solaris-11.2 (64bit) on VMWare workstation-11, but unable to install vmware-solaris-tools as this option is disabled. I tried in workstation-8, but no luck.

I am trying to share directory/drive between host os: Win-7 and guest os: Solaris-11 and I found hgfs is not active on Solaris. Any information and help would be appreciated.

Thanks,

Tusar

SUMMARY OF PROBLEM

My Windows Vista guest VM has started blue-screening every time I enter Unity Mode. (The host system continues running normally.)

I'm running Vista Business (32-bit) inside WMware Player v7.1.0 build-2496824 with 2 GB of RAM.

The host system is Windows 7 Professional (64-bit 6.1.7601) SP1 with 12 GB of RAM.

The guest system has just a handful of small applications installed.

The blue screens occur even with no applications running on the guest.

NOTES

(1) I've been using the VM frequently for several weeks now without any major issues, and I've tried Unity Mode a few times before with success.

However I've mostly just been running my VM in a normal window (whatever you call 'non unity mode'!)

(2) I vaguely recall that one of the times I entered Unity Mode, many weeks ago, my host system made a bit of a drama... I think the Desktop Window Manager crashed and possibly Aero stopped working on the host OS. At the time, I guessed it was an issue with the host's graphics driver. (I've subsequently updated the host's graphics driver, and the problem has not reoccurred, which of course may or may not be pure coincidence.) But Unity Mode definitely worked, and has worked for a good length of time between my last host driver update and today, when the first BSOD occurred.

(3) Prior to today, the only issue I have noticed with the VM is sometimes there is mouse pointer corruption after doing 'stuff' in the VM window (perhaps after performing actions that cause the guest's mouse pointer to change?) then moving the pointer outside the VM window: now, instead of just a regular white arrow, there's a varying pattern of pixels in two horizontal lines, a good few pixels below the bottom of the arrow. This corruption typically vanishes when I move the pointer back inside the VM window area, but often reappears (sometimes changing to a different pattern of corruption) when I move it outside again, and so on. After a varying number of repetitions (outside VMware window / inside / outside...) the corruption vanishes for the time being. (By the way, the corruption survives pointer changes on the host. So for example, I can move the corrupted pointer to a window edge on the host, causing the pointer to change to a double-arrow like usual, but the corruption is still there below the pointer.)

I've always felt the dodgy mouse pointer was a mild cause for concern! Nothing like this occurs until I start running my VM.

(4) It's only in the last ~24 hours that I've been getting the BSODs when entering Unity Mode.

This roughly correlates with Vista demanding activation (which I have now finally got round to doing!) - this may or may not be pure coincidence.

The Vista guest definitely seemed to be on the brink of refusing to work - today it kept changing my desktop wallpaper to a plain black background and saying this was my last day to activate. This behaviour stopped as soon as I successfully activated it.

The Unity Mode BSODs have occurred both before AND after activation.

(5) I have looked through recent Windows updates on both the host and the guest.

On the guest, there's nothing there other than Definitions Updates for Microsoft Security Essentials in the last month.

On the host, it's been six days since an OS update (since then, just MSE definition updates).

(6) [Update] I've tried disabling Aero on the guest. The VM still BSODs on entering Unity Mode.

The blue screen itself:

A problem has been detected and Windows has been shut down to prevent damage to your computer.

PFN_SHARE_COUNT

...

Technical information:

*** STOP: 0x0000001B (0x00000000, 0x00000000, 0x00000000, 0x00000000)

Log files:

WERAC16.tmp.version.txt

Windows NT  Version 6.0 Build: 6002 Service Pack 2

Product (0x6): Windows Vista (TM) Business

Edition: Business

BuildString: 6002.19327.x86fre.vistasp2_gdr.150225-1506

Flavor: Multiprocessor Free

Architecture: X86

LCID: 1033

Mini041115-01.dmp

I've run dumpchk on the minidump file. It says:

Probably caused by : vm3dmp.sys ( vm3dmp+17c6f )

I have attached a photo showing the intermittent mouse pointer corruption issue.

I've also attached a screen shot of the BSOD.

Please let me know if there's any other info I should include. Thanks in advance for any suggestions!

Hi,

I am new to ESXi development. In ESXi, it possible to communicate the vmkernel from user space using api such as ioctl,netlink,genetlink,etc,.

These API were used in Linux to communicate the kernel from user space (Application level).

My question is how to use IOCTL in ESXi  and How to communicate the vmkernel from user space.

Thanks in advance!!!!

Thanks,

Mari

I'm using vmkfstools for backuping virtual disks on a  esxi 5.5 from internal datastore to NFS datastore conncted by 1Gbps ethernet.

Time needed for cloning 100GB thin file with about 2GB of data is about 90 seconds, which is fine. I use -d thin, so on the NFS server, the file is only about 2GB. BUT the reverse process (NFS->datastore) takes about 15 minutes.  Whole 1Gbps line is saturated. So it seems, that vmkfstools takes the file as it was thick and read and sends whole file. Is there a better

Hi All,

Getting error for VM Datastore Name, below is the script

$report = @()

$vms = Get-VM rpt01 | Get-View

foreach ($vm in $vms)

{

    foreach($dev in $vm.Config.Hardware.Device){

        if(($dev.gettype()).Name -eq "VirtualDisk"){

            if(($dev.Backing.CompatibilityMode -eq "physicalMode") -or ($dev.Backing.CompatibilityMode -eq "virtualMode")){

                $row = "" | select Cluster, Folder, VMHost, VMName, IP, Powerstate, HDMode, HDName, HDsize, LUN, HDDisplayName, VMDataS

                #$row = "" | select VMHost, VMName, HDName, LUN, HDsize, HDMode, HDDisplayName, IP, Cluster,Folder

                $row.VMName = $vm.Name

                $esx = Get-View $vm.Runtime.Host

                $row.VMHost = ($esx).Name

                $row.Powerstate = $vm.Runtime.PowerState

                $row.VMDataS = (Get-Datastore -VM $vm | Select -Last 1).Name

                $row.HDName = $dev.DeviceInfo.Label           

                $row.HDMode = $dev.Backing.CompatibilityMode

                $row.HDSize = [system.math]::Round($dev.CapacityInKB / 1048576)

                $row.HDDisplayName = ($esx.Config.StorageDevice.ScsiLun | where {$_.Uuid -eq $dev.Backing.LunUuid}).CanonicalName

                $lun = Get-ScsiLun -VmHost $row.VMHost -CanonicalName $row.HDDisplayName

                $row.LUN = $lun.RuntimeName.SubString($lun.RuntimeName.LastIndexof("L")+1)

                $row.IP = $vm.guest.IpAddress

                $row.Cluster = (get-view -ViewType clustercomputeresource | ?{$_.moref -match $esx.parent.value}).name

                $row.Folder = (get-view -ViewType Folder | ?{$_.moref -match $vm.parent.value}).name

                $report += $row

            }

         }

    }

}

getting below error

Get-Datastore : Cannot bind parameter 'RelatedObject'. Cannot convert the "VMware.Vim.VirtualMachine" value of type "VMware.Vim.VirtualMachine" to type

"VMware.VimAutomation.ViCore.Types.V1.RelatedObject.DatastoreRelatedObjectBase".

At C:\VM_RDM_Info.ps1:16 char:39

+                 $row.VMDataS = (Get-Datastore -VM $vm | Select -Last 1).Name

+                                                   ~~~

    + CategoryInfo          : InvalidArgument: (:) [Get-Datastore], ParameterBindingException

    + FullyQualifiedErrorId : CannotConvertArgumentNoMessage,VMware.VimAutomation.ViCore.Cmdlets.Commands.GetDatastore

Get-Datastore : Cannot bind parameter 'RelatedObject'. Cannot convert the "VMware.Vim.VirtualMachine" value of type "VMware.Vim.VirtualMachine" to type

"VMware.VimAutomation.ViCore.Types.V1.RelatedObject.DatastoreRelatedObjectBase".

At C:\VM_RDM_Info.ps1:16 char:39

+                 $row.VMDataS = (Get-Datastore -VM $vm | Select -Last 1).Name

+                                                   ~~~

    + CategoryInfo          : InvalidArgument: (:) [Get-Datastore], ParameterBindingException

    + FullyQualifiedErrorId : CannotConvertArgumentNoMessage,VMware.VimAutomation.ViCore.Cmdlets.Commands.GetDatastore

I have just finished installing Vcenter 6 appliance, everything went well and I joined the appliance to the domain via the web client, administration, system configuration, nodes - manage.  That worked and I rebooted the appliance, then I added the AD as an identity source which also completed without errors.  But when I goto users and groups and select my domain to list users it wont list i just receive this error "Error while extracting local SSO users".

Any ideas how to resolve this, I have gone through the documentation several times to find what i missed but i've followed all the instruction as to join to the domain and add as identity source but it just wont list the users from the domain.

What is the SSO user?  Also I am using a domain account with Domain admin priviliges when joining the domain and adding the identity source.

Thanks

John Kenny

how to connect 2 VMware Workstation on diffrent pcs at the sam network??????

I am seeing a blue screen every time entering unity mode with error code PFN_SHARE_COUNT:

VMware workstation 11.1.2-2780323

Host Windows 2008r2 -or- 2012r12

Guest Windows 2008r2 with latest guest additions

Accelerate 3D graphics -> Disabled

Intel Z97 board using onboard graphics

Intel Video drivers 15.36.20.64.4206 (latest)

3 monitors attached and active

... result: lots of PFN_SHARE_COUNT blue screens when entering unity.

No unity and no blue screens.

------

relevant excerpt from vmware.log:

2015-07-22T06:37:37.691-04:00| vmx| I120: GuestRpc: Got error for connection 11:Remote connection failure

2015-07-22T06:37:37.705-04:00| mks| I120: MKS-SWB: Number of MKSWindows changed: 0 rendering MKSWindow(s) of total 2.

2015-07-22T06:37:37.708-04:00| mks| I120: ToolsSetDisplayTopology: Sending rpcMsg = DisplayTopology_Set 3 , 0 1200 1600 1200 , 1600 800 1200 1600 , 0 0 1600 1200

2015-07-22T06:37:39.009-04:00| vmx| I120: GuestRpc: Got error for connection 12:Remote connection failure

2015-07-22T06:37:39.842-04:00| vmx| A115: ConfigDB: Setting ide1:0.fileName = "auto detect"

2015-07-22T06:37:39.842-04:00| vmx| A115: ConfigDB: Setting gui.lastPoweredViewMode = "unity"

2015-07-22T06:37:39.842-04:00| vmx| I120: TOOLS received request in VMX to set option 'synctime' -> '1'

2015-07-22T06:37:39.842-04:00| vmx| A115: ConfigDB: Setting tools.syncTime = "TRUE"

2015-07-22T06:37:39.869-04:00| vmx| I120: VMXVmdb_SetCfgState: cfgReqPath=/vm/#_VMX/vmx/cfgState/req/#6a/, remDevPath=/vm/#_VMX/vmx/vigor/setCfgStateReq/#74/in/

2015-07-22T06:37:39.870-04:00| vmx| A115: ConfigDB: Setting ide1:0.fileName = "auto detect"

2015-07-22T06:37:39.872-04:00| vmx| A115: ConfigDB: Setting ide1:0.fileName = "auto detect"

2015-07-22T06:37:39.877-04:00| vmx| W110: [Vmdb_Set] Stale data for path: /vm/#_VMX/mks/grabState/new/ (current value '_UNSET_' -> new value '../req/#78/') [2->1]

2015-07-22T06:37:39.899-04:00| mks| I120: MKS-SWB: Number of MKSWindows changed: 1 rendering MKSWindow(s) of total 3.

2015-07-22T06:37:42.407-04:00| vmx| W110: [Vmdb_Set] Stale data for path: /vm/#_VMX/mks/grabState/new/ (current value '_UNSET_' -> new value '../req/#ee/') [6->5]

2015-07-22T06:37:48.120-04:00| mks| I120: MKS-SWB: Number of MKSWindows changed: 2 rendering MKSWindow(s) of total 4.

2015-07-22T06:37:48.631-04:00| mks| I120: MKS-SWB: Number of MKSWindows changed: 1 rendering MKSWindow(s) of total 4.

2015-07-22T06:37:48.634-04:00| svga| I120: MKS-SWB: Number of MKSWindows changed: 1 rendering MKSWindow(s) of total 3.

2015-07-22T06:37:55.616-04:00| svga| I120: MKS-SWB: Number of MKSWindows changed: 0 rendering MKSWindow(s) of total 2.

2015-07-22T06:37:55.620-04:00| mks| I120: ToolsSetDisplayTopology: Sending rpcMsg = DisplayTopology_Set 1 , 0 0 1596 1058

2015-07-22T06:37:55.654-04:00| mks| I120: MKS-SWB: Number of MKSWindows changed: 1 rendering MKSWindow(s) of total 2.

2015-07-22T06:37:56.172-04:00| vmx| I120: GuestRpc: Got error for connection 13:Remote connection failure

2015-07-22T06:38:03.250-04:00| vmx| I120: Tools_SetGuestResolution: Sending rpcMsg = Resolution_Set 1188 934

2015-07-22T06:38:03.250-04:00| vmx| I120: Tools_SetGuestResolution: Sending rpcMsg = Resolution_Set 1188 934

2015-07-22T06:38:03.315-04:00| vcpu-0| I120: TOOLS call to Resolution_Set failed.

2015-07-22T06:38:03.396-04:00| vmx| I120: Tools_SetGuestResolution: Sending rpcMsg = Resolution_Set 2792 1600

2015-07-22T06:38:03.444-04:00| vcpu-0| I120: Guest: vm3d: WDDM Fatal: vm3ddevadapter.c:846 Command buffer error, 3D command: 1126

2015-07-22T06:38:03.444-04:00| vcpu-0| I120+

2015-07-22T06:38:03.444-04:00| vcpu-0| I120: Guest: vm3d: WDDM Fatal: vm3ddevadapter.c:935 Fatal command buffer error id=1126.

2015-07-22T06:38:03.494-04:00| vcpu-0| I120: SCSI0: RESET BUS

2015-07-22T06:38:03.545-04:00| svga| I120: SVGA disabling SVGA

2015-07-22T06:38:04.095-04:00| vcpu-0| I120: SCSI0: RESET BUS

2015-07-22T06:38:11.603-04:00| vmx| I120: GuestRpcSendTimedOut: message to toolbox-dnd timed out.

2015-07-22T06:38:16.155-04:00| vcpu-0| I120: SCSI scsi0:1: Unsupported command START STOP UNIT issued. --ok

2015-07-22T06:38:16.156-04:00| vcpu-0| I120: SCSI scsi0:1: Unsupported command START STOP UNIT issued. --ok

2015-07-22T06:38:16.156-04:00| vcpu-0| I120: SCSI scsi0:1: Unsupported command START STOP UNIT issued. --ok

2015-07-22T06:38:16.156-04:00| vcpu-0| I120: SCSI scsi0:1: Unsupported command START STOP UNIT issued. --ok

2015-07-22T06:38:16.157-04:00| vcpu-0| I120: SCSI scsi0:1: Unsupported command START STOP UNIT issued. --ok

2015-07-22T06:38:16.176-04:00| vmx| I120: Tools_SetGuestResolution: Sending rpcMsg = Resolution_Set 1596 1058

2015-07-22T06:38:16.177-04:00| vmx| I120: Tools_SetGuestResolution: Sending rpcMsg = Resolution_Set 1596 1058

2015-07-22T06:38:16.465-04:00| svga| W110: WinBSOD: (29) 'Physical memory dump complete.                                                  '

2015-07-22T06:38:16.465-04:00| svga| W110:

2015-07-22T06:38:16.465-04:00| svga| W110: WinBSOD: (30) 'Contact your system admin or technical support group for further assistance.    '

2015-07-22T06:38:16.465-04:00| svga| W110:

I have esxi server and I am able to create VM through ovftool and power it on. so far it is good but I want to manage (linux-vm) from esxi cli. Like this I want to login to the esxi through ssh from there I want to access linux-vm console. Is there any way to do it?

Noon everyone,

I´m facing an issue with a vCAC 6.1 implementation.

Here´s what´s happening (i´ll use makeshift addresses):

The vCAC appliance is configured to point to an Identity Appliance. The ID App address is id.domain.net.

The vCAC appliance is correctly configured to point to id.domain.net:7444.

The vCAC appliance FQDN is vcac.domain.com.

Now, the vCAC services won´t start. I see the following entries within catalina.out:

==================================================================================================================

Exception thrown is unexpected during retry operation with message: I/O error on GET request for "https://id.domain.com:7444//websso/SAML2/Metadata/vsphere.local":java.security.cert.CertificateException: Untrusted certificate chain

==================================================================================================================

Now here´s the big mistery: Why is it point to id.domain.com instead of what is configured: id.domain.net?

If I try a simple resolv test: ping id.domain.net, it pings correctly

Anyone knows where exactly vCAC stores that information?

I already tried adding search domain.net within /etc/resolv.conf.

I already tried addingthe correct entries within /etc/hosts.

Anyone, help?

Thank you once again.

hi fastscp not able to connect to vm 5.5.

what port should i use

please advise

thanks

B

hi

I am using vsphere client to host a vm,which is currently showing storage full, it says"remove some data"and it is not letting the VM to turn on only.The datastore is filled with vmdk files,should i erase the vmdk files or should i consolidate the vm,or should i remove the orphaned vmdk file,or can i make the vmdk files to store in different datastore(if yes how can i change disk file path).I am new with the vmdk file managemnt ,plz guide me through the process.

This vCO package aims to include workflows to Create/Read/Update/Delete vCAC custom properties on more than just VirtualMachine objects.

It is dependent on the vCAC IaaS Plugin for vCO.

So far it has workflows for manipulating properties on Blueprint, Build Profiles, Management Endpoints, Property Sets, Property Dictionary Definitions/Attributes and Business Group (vCAC 6.x) / Provisioning Group (vCAC 5.x):

USAGE Examples:

Dynamically updated request forms example with vRA, vRO and Chef | VMtoCloud.com

UPDATES:

• 7/2/2015:
  • Added Apply to Existing VMs functionality option for workflows:
    • Blueprints
      • Create / Update property on Blueprint
      • Delete property from Blueprint
      • Import Blueprint Properties From Property Set XML
      • Toggle Build Profile on Blueprint.  (Can be rerun to apply a modified build profile to VMs.)
  • Fixed presentation defect in Blueprints/Import Blueprint Properties From Property Set XML
  • Added action addUpdateManyPropertyFromVirtualMachineEntity which will add/update many properties in a more efficient manner.
    • Fixed return of action to be an array of vCAC:Entity in com.vmware.pso.vcac.proptoolkit.20150702_1.package
• 12/7/2014:
  • Added workflows:
    • Find Blueprint by Property
    • Find Business Groups by Property
    • Find Virtual Machines by Property
• 8/26/2014:
  • Added workflows:
    • For Blueprint properties
    • Apply Build Profile to Existing Virtual Machine
    • Get Properties of Disposed Virtual Machines
    • Add/Remove item for ValueList attributes of DropDown Property Definitions.
    • Get All Property Definition Attribute Entities
    • Preliminary Property Dictionary Layout workflows.
    • Parse Property Set XML
  • Fixed workflows:
    • Create Build Profile From Property Set XML - Fixed handling of strings that contain a "#" character.
    • Fixed error handling for Get Property Definition Attribute Entity when multiple attributes have the same name.
• 7/2/2014:
  • Added Workflows:
    • Build Profiles\Delete Many Build Profiles
    • Business Groups\Copy Business Group Properties
    • Property Dictionary\Copy Property Definition
    • Endpoints\Copy Endpoint Properties
    • Endpoints\Create / Update Property on Endpoint
    • Endpoints\Delete Property from Endpoint
    • Endpoints\Export Endpoint Properties as Property Set XML
    • Endpoints\Import Endpoint Properties From Property Set XML
  • Added description output to workflows:
    • Build Profiles\Get Build Profile Entity
    • Build Profiles\Export Build Profile as Property Set XML
  • Added attributeNames and controlTypeName outputs to workflow:
    • Property Dictionary\Get Property Definition Entity
  • Added sameAsSource boolean input to Copy Build Profile and Copy Property Definition workflows. This will make authoring workflows easier for managing many Build Profiles or Property Definitions when you just need to copy the object exactly between different vCAC hosts.
• 5/23/2014:
  • Added workflows to create / update / delete Property Definitions in the Property Dictionary
  • Added workflows to create / update / delete Property Attributes in Property Definitions

How can I disable this alert?

VMware vSphere Update Manager notification alert: (critical): 1(1)

The number of notifications downloaded:

Critical/Total notifications: 1/1

ID: ESXi550-201505101-BN

Impact: Critical

Release date: 2015-05-05

Summary: VMware advises not to upgrade to ESX 5.5 Patch Release ESXi550-201504002 released on 4/30/2015.   Refer to KB#2116370 for details.

Description: VMware advises not to upgrade to ESX 5.5 Patch Release ESXi550-201504002 released on 4/30/2015.   Refer to KB#2116370 for details.

When I clear this alarm in vcenter, it will appear again after restarting update manager service.

Добавляю диск - выбираю SATA

диск добавился вроде всё збс

на окне настроеш жму ОК

выдаёт какуето типо "внутреннею ошибку"

какие у неё проблемы?

The VMware Fusion team is very excited to announce the VMware Fusion Technology Preview 2015 release! This release includes many great new features that we’ve been working on and we would love to hear your feedback.

What’s New

Windows 10 Insider Preview Support - With Microsoft Windows 10 general availability just around the corner, we’ve been working hard on providing top level support for this brand new operating system. You can run the latest Windows 10 Insider Preview build in VMware Fusion Tech Preview 2015, when you create a Windows 10 Insider Preview virtual machine, Fusion is now able to recognize the operating system based on the ISO file, and complete the Easy Install for you.

OS X El Capitan Beta Support - Now you can easily create and run El Capitan Beta virtual machine, or run virtual machines on your El Capitan Beta host, with this Tech Preview release.

Other New OS Support - Fusion Tech Preview 2015 supports a variety of new operating systems including Ubuntu 15.04 and Fedora 22. If you are running these latest operating systems, we would like to hear your feedback on how they perform within this release.

DirectX 10 Support - DirectX 10.0 is a high sought-after feature that we are excited to deliver it in this Tech Preview release. With DX10, you can run more 3D applications, notice better performance, and use advanced features like Power Map in Microsoft Excel 2013. DirectX 10 is enabled for virtual machines that run hardware version 12, which is the default hardware version when you create a new virtual machine with VMware Fusion Tech Preview 2015.

DirectX 10 is supported on OS X 10.10 and newer for the following GPUs:

- Intel: HD4000 or newer

- NVidia: GeForce 650M or newer

- AMD: Radeon HD 5770 or newer

OpenGL 3.3 Support - For Windows virtual machine with the latest hardware version, OpenGL 3.3 is now supported. This support for Windows guests extends from Windows Vista to Windows 10 Insider Preview.

Performance Improvement for Encrypted VM Suspend, Resume, and Snapshot - In this Tech Preview release, we significantly improved the suspend and resume performance of encrypted virtual machines. Our testing continuously shows these operations to be 4-5 times faster than before, and now we would like to hear your feedback.

IPv6 NAT Support - We are very excited about our improvements around IP networking, with added support for IPv6 Network Address Translation (IPv6 NAT). You can set up an IPv6 network between multiple virtual machines regardless of whether the external network is IPv4 or IPv6. To use IPv6 NAT, create a new custom network and select using NAT, then check “Enable IPv6”. You can also set the prefix of the IPv6 address for each IPv6 NAT network in the Virtual Network Editor.

Performance Improvement for Voice Call within the Guest - More and more customers are making voice and video calls with conference call software such as Lync and Skype within a virtual machine, we have made many improvements to make sure that calls perform well so you don’t have to hang up and call in from your Mac.

Advanced Resolution Setting - This Tech Preview release provides a global setting and a per-virtual machine setting, where you can set the rules between window resizing and virtual machine resolution change. You can find the global settings in VMware Fusion > Preferences > Display, and the per-virtual machine setting is located in Virtual Machine > Settings... -> Display, if you would like to override the global setting for a specific virtual machine.

Create a Remote Virtual Machine - We introduced vSphere Integration in VMware Fusion 7 last year, users can connect to a vCenter Server instance to view inventory, upload/download virtual machines, and remote console access to a virtual machine. In this Tech Preview release, you can also create a new virtual machine directly on the server, instead of creating a local virtual machine and then uploading it to the server.

User Experience Improvement - We revisited a few places to add some fresh paint and polish, including the New VM Creator and the Start Menu in the menu bar. Our aim has been to optimize the user experience so you can easily find the most important actions with the least amount of steps.

New PC Migration Agent with Windows 10 Insider Preview Support

General Stability and Application Compatibility

Installation Notice

This Tech Preview release runs on OS X 10.9 and newer, while other requirements remain the same as Fusion 7. See this VMware Fusion Document for more detailed system requirements.

Please note that the drivers included in this preview have NOT been signed and Windows will prompt you accordingly during installation.

In rare circumstances, it might be necessary to recreate a virtual machine that was created in this Technology Preview in a subsequent version of the product. This Technology Preview includes changes to the underlying virtualization platform, which is under active development. There are no guarantees that changes in this preview will be forward-compatible with other VMware software, nor that these changes will be present in future supported releases of VMware Fusion.

Uninstallation Notice

To uninstall the VMware Fusion Technology Preview:

1. Uninstall VMware Tools from each virtual machine used with the Technology Preview

2. Ensure that all virtual machines are downgraded to be compatible with an earlier version of VMware Fusion (Virtual Machine > Settings... > Compatibility > Advanced options)

3. Exit the VMware Fusion Technology Preview

4. Remove VMware Fusion Technology Preview by moving the application to the Trash

Known Issues

- The Tech Preview release uses a beta build with debugging mode on, the performance will be slower than the normal release build.

- Occasionally switching to Unity mode may cause virtual machine crash when running an old Windows 10 Insider Preview build as a guest.

- Upgrading a virtual machine from hardware version 10 to hardware version 12 without upgrading the VMware Tools may cause black screen in fullscreen mode. Make sure you install the latest VMware Tools.

- Running 3DMark 2013 may cause system crash on MacBook Pro 15 inch Mid 2015 with AMD Radeon R9 M370X GPU.

- Connecting a USB device through a multi-ports USB-C adaptor to a virtual machine may cause a VMX crash.

- When an application trying to change the resolution of a Windows 7 virtual machine in full screen mode, this virtual machine might fail.

- On OS X 10.11 Developer Preview host, occasionally virtual machine can not boot up, you may need to reboot the host after this Tech Preview build is installed to solve this issue.

- On OS X 10.11 Beta host, unplugging an external monitor while running a virtual machine in full screen mode might cause VMware Fusion crash.

- On OS X 10.11 Beta host, user will run into a certificate error while connect to the update server.

We really appreciate your help testing this software. Please post all of your feedback in the VMware Fusion Technology Preview 2015 communities forum.  We will try to answer any questions that you have and will investigate any issues that you find. Please also post any other comments you may have on how we can improve these currently implemented features or enhancements that you would like to see in future releases.

Thank you!

The VMware Fusion Team

I am trying to setup amazon ec2 templates but when I go to my appd url

https://appd/agent/jre-7u45-linux-amd64.rpm

I dont get anything

I am following this

vRealize Automation 6.2 Documentation Center

I am developing a plugin for vRealize Orchestrator, and I am trying to understand how files can/should be stored on the vRealize Orchestrator server. I am aware that a temporary directory is available for writing files, but is there a recommended way to store files long-term (e.g. backups and patch files for the orchestrated technology) on the Orchestrator server?

Additionally, there is an EndpointConfigurationService interface available within the Spring Maven archetype for a vRO plugin, but there does not appear to be any implementation of this interface within the archetype's dependencies. Is there a default implementation of this interface, or is it the developer's responsibility to implement it themselves?

People,

I'm having some serious issue here after upgrading the HP Blade BL 465c G7 with Emulex NC551i Dual Port FlexFabric 10 Gb adapter.

The problem: After successful inline update from ESXi 5.1 Update 2 Patch 5 (2000251) into ESXi 5.1 Update 3 (2323236) the ESXi server cannot be pinged nor it can ping to outside network, therefore it failed to reconnect back to VCenter server.

Software/Firmware version:

Before the upgrade of the server the version are as follows:

~ # ethtool -i vmnic0

driver: be2net

version: 10.2.293.0

firmware-version: 4.9.416.2

bus-info: 0000:04:00.0

~ #

Since the version above doesn't work, I've managed to download VMW-ESX-5.1.0-be2net-10.2.477.20-offline_bundle-2541837.zip to upgrade the VMNic driver it into: 10.2.477.20 but still after the update and reboot the network is not ping-able.

Rollback:

I have also tried to perform rollback to the previous working ESXi server version 2000251 using Shift+R but the ESXi server still rebooting as 2323236 with no working network still.

Any other suggestion would be greatly appreciated without having to reconfigure the ESXi settings and Distributed Switch configuration from scratch.