Are you the publisher? Claim or contact us about this channel


Embed this content in your HTML

Search

Report adult content:

click to rate:

Account: (login)

More Channels


Showcase


Channel Catalog


Channel Description:

Latest Forum Threads in VMware Communities

older | 1 | .... | 6678 | 6679 | (Page 6680) | 6681 | 6682 | .... | 6759 | newer

    0 0

    Hi There,

     

    Q1.  After some research, I am able to create ConfigurationElements programmatically, now I want to set attribute and its values with an array of composite types how to do it?

    Q2.  if vRO is not allowed to edit attributes and its values by the unauthorized user then is it allowed to edit programmatically?

     

     

    Thanks

    Laxmi


    0 0

    On the findings page https://skyline.vmware.com/advisor/findings , Skyline is not showing any data, even after 48 hours.

     

    Please see attached screenshot

     

    I can see the collector and objects on the account page: https://skyline.vmware.com/advisor/account-details

     

    Collector id is f719634f-f4ac-4a15-ae3e-10a0e6d9f807

     

    Many thanks


    0 0
  • 10/26/18--12:47: Windows 10 1803 and Persona
  • Has anyone solved with issue with Windows 10 1803 not syncing persona data to the assigned share?

     

    - The Windows 10 VDI is fully patched.

    - I have tried agents 7.4, 7.5, and 7.6.

     

    Still no joy...    Anyone conquer this yet?  


    0 0

    Bonjour à tous,

     

    Je créé ce groupe de discussion afin de savoir si l'un de vous à déjà rencontrer l'erreur d'installation " erreur inconnu " pendant la mise à niveau de son vCenter Server Windows 5.5 Update 3d

     

    Environnement VMware

    1 vCenter Server de type Windows 5.5 Update 3d

    Build Number (vSphere Web Client) : 3721164

    Install Build Number (Site VMWare) : 3730491

     

    La base de données du vCenter Server est Windows SQL Server 2014 64 bits12.0.2000.8.

     

    2 ESXi (2 lames HP Dl 380p Gen8)

    ESXi 5.5 Update 3f (build 6480324)

    ESXi 5.5 Express Patch 10 (build 3568722)

     

    Mon objectif est mettre à jour cet environnement de PROD en vCenter 6.5 u2 et ESXi 6.5 u2

    La matrice de compatibilité entre vCenter Server 6.5 u2 Appliance n'admet pas la version de la base données SQL Server 2014 64 bits12.0.2000.8.

    Si j'ai bien compris, on peut en revanche quand même mettre à jour le vCenter Server de type Windows 5.5 Update 3d en conservant le vCenter Server de type Windows.

    (VMware Product Interoperability Matrices)

     

    Installation en échec : " erreur inconnue "

    Une fois l'ISO de vCenter Server 6.5 Windows monter, les paramétres renseignés, le processus de mise à jour presque terminé, une fenêtre d'erreur apparaît à la phase de mise à niveau.

    Le message d'erreur est " erreur inconnue"

    La lecteur du fichier vminst.log montre le même message..

    Je n'ai pas pu garder ce fichier de log donc impossible d'ouvrir un case chez VMware

     

    Je reconnais ne pas savoir comment gérer ; contourner cette anomalie. Vos conseils sont donc plus que bienvenue

     

    Merci à vous,

    Louis


    0 0

    user name and password put in correctly as soon as it tries to connect I get   The session was disconnected. Lost connection to server. Does anybody know a fix to this. When I called support they said I needed  a license to report problems.


    0 0
  • 12/19/18--12:42: Software
  • Where can I download a copy of VMware Workstation V11?


    0 0

    I recently upgraded my 100Mbps switch to a Gigabit switch. However, I noticed that the ESXi NICs are still running at 100 Mbps, not 1000Mbps. So using vSphere Client I changed the speed to 1000Mbps, and oh boy what a disaster that was. That seemed to trash the network connection which meant everything stopped working and I could no longer connect to the ESXi host though vSphere Client. And because I couldn't connect with vSphere Client I couldn't change the speed back to 100Mbps. So I ended up going into the ESXi console and choosing Reset from the menu which essentially means starting again with a blank ESXi config. This was of course very frustrating.

     

    So my questions are:

    1) Why might the NICs be running at only 100Mbps even though they're now connected to a Gigabit switch?

    2) How do I get them running at Gigabit without losing network connectivity?

    3) If I do run into the same problem again, how can I reset the NIC without having to do a complete ESXi reset?


    0 0

    I was using the free version of ESXI for about 60 days and forgot to put in my license info after a rebuild.

     

    Today, my VM's stopped working I assume because my trial expired (specifically I lost my remote connections to VM's in the VLAN200), so I logged into esxi put my registration info and rebooted.

     

    When I first rebooted, I had access to my VLAN200 port group/switch (I also have the default vSwitch0 on my default lan). But minutes later, it stopped working again. Never had a networking issues before.

     

    Here are the events that I see

     

    Here are screenshots of my config

     

    I have the onboard Nic on my workstation a 4 port Intel Gigabit ET adaptor, Dell Part Number: HM9JY that I'm only using one NIC (the one that seems to be going down)

     


    0 0

    scenario:

    2 physical vsan 6.7u1 nodes + 1 witness vm 6.7u1

    each physical host in seperate fire sections

    all connected via 10gb lan switches on the same campus

    witness and vcsa running on other non vsan cluster host in a 3rd fire sections

     

    now we do a lot failure testing, remove disks, remove network, failed hosts, failed power.

    the vsan automatically rebuild everytime without needing hands on.

    perfekt.

     

    BUT:

    when all hosts are shut down, we power on secondary fault domain host and witness the vms didnt restart. all vms are disconnected or inaccessible.

    there ist no way to get the vms back online.

    why?

     

    if we power on the preferred fault domain host and the witness, the vms fix automatically and restart automatically.

     

    the customer, needs the same "automatic repair" equal which data host is alive

     

    is this is bug or a configuration (or an understanding) error?

     

    best regards

    Alexander


    0 0

    Hello:

    We just upgraded from AppVol 2.12 to 2.14.2 (latest).  After the upgrade, users are calling in with an issue where Outlook 2016 Pro Plus tries to run an install or configure every time it is launched. In our case we have Office installed directly on the master image which has not changed, it is not an AppStack.  We use Writable Volumes and I have verified that the issue is not related to any changes in the snapvol.cfg file with the update as I've tried the old version of snapvol.cfg as well and get the same behavior, so it's definitely an issue with the 2.14.2 upgrade somehow.

     

     

    Has anybody else experienced this and know of a workaround?  I've been looking and so far no solution that I can find.

    Thanks in advance!

    Chris


    0 0

    We have a handful of production servers where the vmware snapshot provider service is installed (per the installer), but the service does not exist (in services or in registry).  We use this for our backups, and can't figure out why this stopped working after our last round of MS patching.  We are assuming that the disappearance of the service is what started our backups not working.

     

    We have tried to modify VMtools to remove and re-add that service, but even though the installation completes without error, the service still does not exist.

     

    Is there any way to manually add that service to Windows without rebooting the server?  The only option I can find so far is to remove and reinstall VMware tools, which requires two reboots.  Due to the production nature of these servers, we cannot do that quickly enough to get back to having.


    0 0
  • 11/08/18--23:34: delta exam for VCP6.7 ??
  • Hi

    Any information to VMware plan create delta exam from 6.0 or 6.5 to 6.7 ??

    In september 2019 my certification VCP 6.5 expired and I wonder what's next?

     

    MM


    0 0

     

    I recently made a new VM with 2008 datacenter R2 and it would apear vmware tools is not installing properly.

     

     

    i only have 2 services vmware tools service and vmware upgrade helper.  I am missing the snapshot provider service.  I have made sure com+ is there and not disabled and dtc is also enabled and running.

     

     

    i attached the 2 log files i could find that might relate to the install

     

     


    0 0

    I've searched but not found this problem mentioned anywhere; any ideas?

    • Host is Window 10 Pro x64
    • Guest is Windows 7 Pro x64 (up to date after many executions of Windows Update)
    • Using Workstation Pro 15 (downloaded trial yesterday)

     

    Per event viewer:

    Error is reported by System account

    Source is Service Control Manager

    Event ID is 7009

    Error is repeated multiple times

     

    Other points..

    I did disable AVG antivirus SW before attempting installation

    I did install the guest OS from a DVD using Easy Install.

    I did try to install VMware Tools several times before I figured out how to set the DVD to Auto detect but it is set correctly now.

    Every time I try to do the install, the correct iso file appears to get connected to the virtual DVD and the installation begins and runs for a while before hitting this error.

    (i.e. If I look at the DVD while the install window is open, I see the iso on my host.)

    Searched registry per one kb article and found nothing that looks like a partial install.

    No files at C:\Program Files\VMware on the guest.

     

    I've spent several hours on this and am disappointed.  Will try to create a new VM with a Windows 10 guest tomorrow.

     

    Any ideas will be appreciated.

     

    Thanks,

    James


    0 0

    Hi all

     

    I have created to new Win Server 2016 Servers. Both VMs are attached to a Domain. I have Created a Multi-Write Shared VMDK Drive. This is mounted on each VM via a new Scsi Adaptor.

     

    I can create and modify files happily.

     

    When setting NTFS Permissions these do not seem transfer to the other VM is this normal?

     

    So, if I say set domain\user1 to have full read permissions on VM1 (on the Shared Drive) I would expect the same permission to be available on VM2 (on the Shared Drive)


    0 0

    I am encountering the following when attempting to Start a VMmark Run using VMmark3-StartSTAX from a terminal window from Gnome via VNC or the vSphere Web Client Console:

     

    root@primeclient ~]# /root/VMmark3/tools/VMmark3-STAX.sh

    Exception in thread "AWT-EventQueue-0" java.awt.HeadlessException

    at java.awt.GraphicsEnvironment.checkHeadless(GraphicsEnvironment.java:204)

    at java.awt.Window.<init>(Window.java:536)

    at java.awt.Frame.<init>(Frame.java:420)

    at javax.swing.JFrame.<init>(JFrame.java:233)

    at VMmarkWindow.createAndShowGUI(VMmarkWindow.java:22)

    at VMmarkWindow.access$000(VMmarkWindow.java:9)

    at VMmarkWindow$1.run(VMmarkWindow.java:35)

    at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:311)

    at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:758)

    at java.awt.EventQueue.access$500(EventQueue.java:97)

    at java.awt.EventQueue$3.run(EventQueue.java:709)

    at java.awt.EventQueue$3.run(EventQueue.java:703)

    at java.security.AccessController.doPrivileged(Native Method)

    at java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:74)

    at java.awt.EventQueue.dispatchEvent(EventQueue.java:728)

    at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:205)

    at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:116)

    at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:105)

    at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:101)

    at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:93)

    at java.awt.EventDispatchThread.run(EventDispatchThread.java:82)

    Exception in thread "main" java.awt.HeadlessException

    at java.awt.GraphicsEnvironment.checkHeadless(GraphicsEnvironment.java:204)

    at java.awt.Window.<init>(Window.java:536)

    at java.awt.Frame.<init>(Frame.java:420)

    at java.awt.Frame.<init>(Frame.java:385)

    at javax.swing.JFrame.<init>(JFrame.java:189)

    at com.ibm.staf.service.stax.STAXMonitor.<init>(STAXMonitor.java:519)

    at com.ibm.staf.service.stax.STAXMonitor.main(STAXMonitor.java:5623)

     

    Attempts to start STAX in the GUI by double-clicking on the VMmark3-StartSTAX icon on the desktop doesn't do a thing.

     

    I'm probably missing/doing something simple, but my eyes are about to bleed from staring at this for so long (spent the majority of last week troubleshooting the Provisioning Process which ended up being an NFS Datastore permissions issue).

     

    Hoping someone can help.

     

    Thanks in advance!

     

    -tim


    0 0

    This issue has been unresolved for at least a month - and I do not see any response - even "We're looking at it."

     

    There is a missing path to the files needed to remove the previous .msi file and thus the updated Tools cannot be installed until the previous version is removed.


    0 0

    I'm trying to upgrade my VCSA from 6.5 to 6.7 and it fails the Stage 2 Pre Upgrade Checks with a pretty unhelpful:

     

    "Cannot validate target appliance configuration as not enough information from the source appliance can be collected. For more details check out the server logs"

     

    I've attached the upgrade logs, can anyone assist with this? Thanks


    0 0
  • 12/19/18--16:21: vCenter Single Sign-On error
  • I am running the vCenter Server Appliance version 6.7 and I am using LDAP for authentication. When I first set up vCenter the LDAP authentication was working perfectly fine and continued to do so up until sometime last week. The problem that I am having is that under the users and groups tab when I select my LDAP domain I get the error "A vCenter Single Sign-On service error occurred" and I am unable to see any of the users. However, I am still able to log in to all of the LDAP user accounts without any errors. I am also unable to set permissions on objects by user but I am still able to add the users to groups.

     

    I am using the vCenter Server Appliance version 6.7 running on ESXi version 6.7. I am using Open LDAP for authentication. I have both forward and reverse DNS records set up for both the vCenter server and the LDAP server. I have tried re installing vCenter Server to fix the problem as well as trying a different LDAP server, both of which did not solve the problem.

     

    Any help with this would be greatly appreciated.


    0 0

    Hey guys I recently bought VMware fusion 7 Pro and I completed the configuration but then VM said "File not found". I already have VMware Fusion 6 installed and I want to open my windows 7 account in VMware Fusion 7 and then VM said that the file wasn't found. Do you guys also have this problem and how can I solve this? Thnx a lot!


older | 1 | .... | 6678 | 6679 | (Page 6680) | 6681 | 6682 | .... | 6759 | newer