Hi,

I'm using that from first release till now, it's working fine for me and vCenter integration is most important thing about that.

You can install that on your vCenter machine or on a separated Windows Server.

Syslog Collector configuration is very easy, just you should add your server address to your ESXi settings.

Davoud

Welcome to the Community,

I assume it's "...not a virtual disk" rather than "...file". Anyway, to start with, please post a complete list of files in the VM's folder which shows all files with their sizes and time stamps (e.g. the output of dir *.* /one from the command line).

André

Hi,

1. The VR appliance comes into two flavours.

On just one vCenter server you can use only one combined VR appliance (VRMS+embedded DB+VR server).

Inside the same vCenter server you can (but not necessarily need to) deploy additional appliances that contain only VR server and not VRMS. The additional appliance has a different .ovf name, but same .vmdk files.

If you attempt to power on second VRMS inside the same vCenter Server inventory, it will break the extension data in vCenter server for the first VRMS and won't work.

2. If not using SRM on top of VR, failback operation is manual - you simply stop the replication after failover (A->B), configure it in the reverse direction (B->A) and perform the recovery (B->A).

Regards,

Martin

What OS is your VM running ?    

Hi all,

I'm just trying to get my first workflow to run, but already stuck....

I would like to call a powershell script that uses the NetApp cmdlet "Connect-NAServer" wich needs a PSCredential as input.

I'm using the following code to generate the PS script:

script = " \n"

+ "Import-Module 'DataOntap' \n"

+ "$NAUser = '" + NAUser + "' \n"

+ "$NAPass = '" + NAPassword + "' | ConvertTo-SecureString -AsPlainText -Force \n"

+ "$NAControllers = @(" + NAControllers + ") \n"

+ "$NAcred = New-Object -typename System.Management.Automation.PSCredential -argumentlist $NAuser,$NApass \n"

+ "ForEach ($NAController in $NAControllers) { \n "

+ "Connect-NaController $NAController -HTTP -Credential $NAcred \n"

+ "} \n";

After that I call the script as follows:

try {

session = PSHost.openSession();

output = System.getModule("com.vmware.library.powershell").invokeScript(PSHost,script,session.getSessionId()) ;

} finally {

if (session){

  PSHost.closeSession(session.getSessionId());

}

}

NAPassword is an attribute of the workflow, linked to a configuration element (of type SecureString).

This always results in this error: "System.Security.Cryptography.CryptographicException: The requested operation cannot be completed. The computer must be trusted for delegation and the current user account must be configured to allow delegation."

I already tried to enable delegation in AD for the powershell host. ("Trust this computer for delegation to any service (Kerberos only)"), but still no luck.

Any ideas, what is happening here?

Regards, Stefan

P.S.: The connection the the powershell host is configured to use kerberos authentification - shared authenticaiton.

Works great.  Thanks guys!

Hi,

Some virtual appliances are created by VMware partner companies such as Symantec, Teradici and others for some special management reasons.

Most of the virtual appliances are Linux based and they are customized.

Just don't try to change base configuration on them, for example don't change type of NIC.

Davoud

What you described is certainly possible if the old storage system is supported by the new ESXi version. Anyway, to find out which other options are available, it would be helpful to know which licenses you have and whether you want to create new VMFS5 datastores on the new storage system rather than to upgrading VMFS3 to VMFS5.

André

Is your means that i have to deploy 2 ovf file ?

1-deploy vsphere replication

2- deploy vrms ?

excuse me I am so confused. i want use manualy failover and failback now with deploy  one vsphere replication appliance i can do failover manualy . now my problem is in failback  how can i do failback ?

i have workstation running on cpu intel i7-4770k with two virtual esx 5.5

if enable on vm "fault tollerance" appear new message:

Virtual machines in the same Fault Tolerance pair cannot be on the same host.

help me

I say VMware Log Insight all the way.  The standard VMware syslog collector (from the vCenter ISO) is fine and works perfectly.  However, if you want to slice and dice your data and really know what's happening in real time (i.e. are my hosts affected by this NIC driver bug, do I have any APDs, etc.) then Log Insight is amazing.  Of course it retains all the historical information as well but what really stands out for me is that I can look at the default view (last 5 minutes) and see what's happening now.  Without that, I am ssh'ing into a random sampling of VMHosts to make my decisions/observations.  Log insight ensures that you don't miss anything.

What I noticed when using the standard syslog collector is I typically only looked at that info after experiencing an issue.  Log Insight on the other hand makes it easy to be proactive.  The interface is very intuitive and makes it fun to dig in and find out what's really happening under the hood in your environment.

If budget is a concern, then the standard VMware syslog collector is fine.  If money is no object, then go vCOPS Enterprise (includes Log Insight) which is absolute BEAST MODE and includes everything you can imagine to slice and dice your data.  End to end event correlation (GOS events, VMHost events, Custom Vendor Cards/Packs, etc.).  If you can't go vCOPS Enterprise then the Advanced is still pretty damn good but doesn't include VMware Configuration Manager and some others.  Like all things VMware, this is subject to change and over time and many things will eventually be included in the lower licensing levels (speculation).

Of course, Log Insight can be purchased on it's own as well.  Either way, this is one of the best investments you can make for your infrastructure IMO.  The most important thing is to start logging asap no matter what you choose.  You can start by configuring the the VMware Syslog Collector, and then add VMware Log Insight as a secondary syslog server while you evaluate the product on free trial for example.  That's what I did.  See below for links to do this with PowerCLI (can also be done via vSphere GUI instead):

PowerCLI Script - Pointing to One Syslog Server:

Log Insight bulk ESXi host configuration with PowerCLI | VMware vSphere Blog - VMware Blogs

PowerCLI Function - Pointing to Multiple Syslog Servers:

Using PowerCLI for Advanced Syslog Configuration Tasks | Jonathan Medd's Blog

VMWare Workstation 10: No internet on guest on NAT Settings

Symptoms

• The virtual machine does not have network connectivity.
• You cannot connect to the Internet from the guest operating system.
• Your virtual machine does not have an IP address.
• Bridged, Host-only, or NAT networking fails.
• After upgrading from a previous version of VMware Workstation, there is no Internet connection.
• You see a red X over the network connection icon in the system tray.
• Your Ethernet controller drivers are not installed.
• When you open Internet Explorer, you see the message:
  
  Internet Explorer cannot display the webpage
  
  
• When you hover your mouse over the network icon in the system tray, you see one of these messages:
  • Not connected
  • No connections are available

Resolution

There can be a number of reasons why the networking might stop working in VMware Workstation. Validate each of these troubleshooting steps to verify if it is true for your environment. Each step provides instructions or a link to a document to eliminate possible causes and take corrective action as necessary. The steps are ordered in the most appropriate sequence to isolate the issue and identify the proper resolution. Do not skip a step.

After each numbered step, check whether your virtual machine has an Internet connection. There is no need to proceed with further steps once the issue is resolved.

To troubleshoot your network and Internet connection:

1. Make sure that your Host machine has a working network connection.
   
2. Confirm that your virtual machine's firewall is not blocking the Internet access. For information on turning off your firewall, see:

• Windows XP: Microsoft Knowledge Base article 283673
• Windows Vista: Microsoft article Turn Windows Firewall on or off
• Windows 7: Microsoft article Turn Windows Firewall on or off

Warning: Turning off your firewall can leave your computer open to attack. This is a troubleshooting step only. If turning off the firewall resolves the issue, consult the operating system's documentation for instructions to configure it properly so that it does not completely block this connection.

1. Confirm that your virtual machine's anti-virus program is not blocking the Internet access. Consult the Help menu of the anti-virus program or see the manufacturer's documentation for instructions on configuring it correctly.
   
   

2. Run an anti-virus scan on your virtual machine to make sure there are no viruses or other malware interfering with your Internet connection.
   
   

3. Ensure that the network adapter is enabled. Follow the steps in the Microsoft article relevant to your version of Windows:
   
   Windows Vista: Enable or disable a network adapter
   Windows 7: Enable or disable a network adapter

   Windows 8: How do I fix network adapter problems?
   
   For Windows XP, follow these steps:
   
   • Click Start> Control Panel> Networking Connection.
   • Right-click Local Area Network Connection and select Enable.

4. Change your adapter from NAT to Bridged, or vice-versa. If one selection works and the other does not, then the problem is with your network and not with Workstation or your virtual machine. For more information, see Understanding networking types in hosted products (1006480).
   
   

5. Shut down the virtual machine, then restart your Host Machine.
   
   

6. After your Host machine reboots, reopen Workstation.
   
   

7. Download and reinstall VMware Workstation. This ensures that you have the most recent version, and that any missing or corrupted virtual network settings are replaced/repaired.
   
   

8. Confirm that Workstation services are working properly.
   
   

9. Uninstall and reinstall VMware Tools. For more information, see General VMware Tools installation instructions (1014294).
   
   

10. Make sure that your network adapter is connected to the virtual machine by removing and re-adding it:

    • Shut down your virtual machine.
    • In Workstation, go to VM > Settings> Network Adapter.
    • Ensure that the network adapter is connected (that is, the Connected and Connect at power on options are selected).
    • Ensure that the network adapter is configured for NAT or Bridged, and not Host Only. Make a note of your setting.
    • Click on Remove.
    • From the Settings pane, select Add > Network Adapter to re-add your network adapter.
    • Verify that your new network adapter settings match your old settings.
    • Restart your Host machine.
    • Power on your virtual machine.
      
      
11. Update the Windows network adapter in Device Manager:
    • Start the virtual machine.
    • Click Start, right-click My Computer, and click Manage.
    • Select Device Manager from the left pane.
    • Click the arrow to expand the Network Adapters section.
    • Right-click your Ethernet Controller in that list (name may vary) and click Update Driver Software.
      • Select Search automatically for updated driver software. If the driver is not automatically detected:
        • Repeat the above step and select Browse my computer for driver software.
        • Select Let me pick from a list of device drivers on my computer.
          • For Windows XP, select VMware Accelerated AMD PCNet Adapter.
          • For Windows Vista and 7, select Intel Pro/1000 MT Network Connection.
      • Click Close.
      • Restart Windows.
        
        
12. Uninstall and reinstall all network adapters in the Device Manager:
    • Start the virtual machine.
    • Click Start, right-click My Computer, then click Manage.
    • Select Device Manager from the left pane.
    • Click the arrow to expand the Network Adapters section.
    • Right-click the Intel(R) PRO/1000 MT Network Connection (in Windows Vista and 7) or VMware Accelerated AMD PCNet Adapter (in Windows XP) device and select Uninstall.
    • In the menu bar, click Action> Scan for hardware changes.
    • Restart Windows.
      
      
13. Reset TCP/IP and Winsock settings to default:
    • To reset TCP/IP, follow the resolution steps in the Microsoft Knowledge Base article 299357.
    • To reset Winsock settings, follow the resolution steps in the Microsoft Knowledge Base article 811259.

If your problem continues to exist after performing the steps in this article, please file a support request:

Thanks,

That looks exactly like the issue I am having. Hopefully this is fixed soon or I will have to try NFS as a workaround.

I have the same issue with editing in Netbeans in a Ubuntu - Ubuntu environment.  With a web server running on the guest machine, the pages are not being updated after edit within Netbeans.

Hi Grasshopper,

Thank you for the detailed info, much appreciated!

Awesome, thanks! I'll try that

Resolution

Each step below provides instructions and a link to a document, for performing the step and taking corrective action as necessary. The steps are ordered in the most appropriate sequence to isolate the issue and to identify the proper resolution. They are also ordered in the most appropriate sequence to minimize data loss. After completing each step, check network connectivity again. Work through each troubleshooting step in order, and do not skip a step.

To troubleshoot a lack of network connectivity in a virtual machine:

1. Verify that your virtual machine is using the right type of virtual networking (either Bridged, Host-only, or Network Address Translation (NAT)). For more information, see Understanding networking types in hosted products (1006480).
   
   Note: If a host machine is connected to a network using managed switches or routers, these devices may be configured to block unregistered MAC addresses. In this circumstance, any virtual machine using bridged networking is not able to communicate on the physical network. To resolve the issue, reconfigure the host machine, router, or use NAT networking instead.
   
   
2. If automatic bridging is enabled in a bridged network, virtual network adapters may be binding to the wrong physical adapter or an adapter that is not connected to a valid network. To resolve the issue, manually assign an active physical network adapter to virtual network adapters. For more information see, Bridged networking does not work when loopback adapter is installed on host (1007250).
   
   
3. Ensure that these processes are running. If not then start them manually
   • /usr/bin/vmnet-bridge on Linux hosts using Bridged networking.
   • /usr/bin/vmnet-natd and /usr/bin/dhcpd on Linux hosts using NAT networking.
   • vmnat.exe and vmnetdhcp.exe on Windows hosts using NAT or Bridged networking.
     
     
4. Verify that the host and guest operating systems do not have any services or programs enabled or installed on them that may interfere with network connectivity. These services and programs include, but are not limited to:
   • Firewalls – Some firewalls may see network traffic from virtual machines as foreign to the host and block the traffic from reaching the physical network. To troubleshoot the connection issue, create exceptions for the virtual machine traffic in the firewall or disable or uninstall it.
   • Virtual Private Network (VPN) software – To troubleshoot the connection issue, disable or uninstall it.
   • Internet Protocol Security (IPsec) – To troubleshoot the connection issue, disable or uninstall it.
     
     
5. On Windows host machines, reinstall the VMware Bridge Protocol:

   1. In Windows XP – Click Start> Settings> Network and Dial-up Connections.
      In Windows Vista/7 – Click Start > Control Panel > Network and Internet > View Network status and tasks > Change adapter settings.

   2. Right-click any network adapter icon and click Properties.

   3. Select VMware Bridge Protocol and click Uninstall.

   4. Click Install.

   5. Select Service and click Add.

   6. Select VMware Bridge Protocol and click OK.
      
      

6. On Linux host machines using VMware Workstation version 6.5.0 or lower, reconfigure the network adapters by executing this command in a terminal window:

   
   /usr/bin/vmware-config.pl
   
   

7. If your network does not provide Dynamic Host Configuration Protocol (DHCP), confirm that the static IP settings on the virtual machines are consistent with the addressing scheme on the physical LAN.
8. For Workstation, restore the networking defaults.
   
   To restore the networking defaults, click Edit > Virtual Network Editor and then click Restore defaults.
   
   
9. Rebuild your virtual networking stack by reinstalling the VMware product.

To stay vendor agnostic

Does anyone have experience with Kiwi Syslog Server?

Install Workstation on a Windows Host

You run the Windows setup program and installation wizard to install Workstation on a Windows host system.

Remote connections and virtual machine sharing are enabled by default when you install Workstation. With remote connections, you can connect to remote hosts and run remote virtual machines. With virtual machine sharing, you can create virtual machines that other instances of Workstation can access remotely.

Shared virtual machines are stored in the shared virtual machines directory, where VMware Workstation Server (the VMware Workstation Server service) manages them. Remote users connect to VMware Workstation Server through HTTPS port 443 on the host system.

To change the shared virtual machines directory or select a different port during the installation process, you must select the Custom option. You can also change the shared virtual machines directory, select a different port, and disable remote connections and virtual machine sharing after Workstation is installed by modifying the Shared VMs Workstation preference setting. See Using VMware Workstation for more information.

Procedure

After Workstation is installed, the VMware Workstation Server service starts on the host system. The VMware Workstation Server service starts whenever you restart the host system.

Hello and welcome to the communities.

Note: Discussion successfully moved from VMware Workstation to Nested Virtualization