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


Channel Catalog


Channel Description:

Most recent forum messages

older | 1 | .... | 5517 | 5518 | (Page 5519) | 5520 | 5521 | 5522 | newer

    0 0

    I am using new feature in vRA 7.2 to create a Active Directory policy to add a computer to OU

     

    I have successfully created vRO Active Directory EndPoint and also created policy with OU information.

     

    I am using ext.policy.ActiveDirectory.id in blueprint  customer property and I do see workflow is kicking off in vRO.  However it is failing to add the computer and I see following error in the server.log

     

    Any idea why this workflow is failing

     

    Script execution error on workflow : Add machine to active directory (Event Broker) / 'Create Computer'(item13) : 0000202B: RefErr: DSID-031534A4, data 0, 1 ac

    cess points

            ref 1: 'usnewsdcglob06.ad.global'

    ^@ (Workflow:Add machine to active directory (Event Broker) / Create Computer (item13)#21)

    2017-04-26 17:30:11.373+0000 vco: [component="SqlExceptionHelper" priority="WARN" thread="Workflow Execution Notification Thread" user="cafe-u_O5_jLqGQ@vsphere.local" context="DKS46OPs" token="8aa9

    0d495b9c441c015b9d5aece9000b" wfid="24ad4ae5-723b-4e10-b344-9bea7a742217" wfname="EventBroker Purge PE Agent Node" anctoken="" wfstack="24ad4ae5-723b-4e10-b344-9bea7a742217" instanceid="f9dd8838-d5

    6b-407b-8458-08f360b36ab8"] SQL Error: 0, SQLState: 22021

    2017-04-26 17:30:11.373+0000 vco: [component="SqlExceptionHelper" priority="ERROR" thread="Workflow Execution Notification Thread" user="cafe-u_O5_jLqGQ@vsphere.local" context="DKS46OPs" token="8aa

    90d495b9c441c015b9d5aece9000b" wfid="24ad4ae5-723b-4e10-b344-9bea7a742217" wfname="EventBroker Purge PE Agent Node" anctoken="" wfstack="24ad4ae5-723b-4e10-b344-9bea7a742217" instanceid="f9dd8838-d

    56b-407b-8458-08f360b36ab8"] Batch entry 0 insert into vmo_logevent (logtimestamp, longdescription, originatorid, originatortype, originatoruri, originatorusername, severity, shortdescription, id)

    values ('2017-04-26 17:30:11.372000 +00:00:00', '0000202B: RefErr: DSID-031534A4, data 0, 1 access points

            ref 1: ''usnewsdcglob06.ad.global''

    0000202B: RefErr: DSID-031534A4, data 0, 1 access points

            ref 1: 'usnewsdcglob06.ad.global'

    ^@ (Workflow:Add machine to active directory (Event Broker) / Create Computer (item13)#21)', 'ca555b29-359c-4fc7-987d-43d6fce720a9', NULL, 'dunes://service.dunes.ch/WorkflowToken?id=''8aa90d495b9c4

    41c015bab5030ad01a5''&dunesName=''WorkflowToken''', 'cafe-u_O5_jLqGQ@vsphere.local', '2', 'Workflow ''Add machine to active directory (Event Broker)'' has failed', '8aa90d495b9c441c015bab50322c01a9

    ') was aborted.  Call getNextException to see the cause.

    2017-04-26 17:30:11.373+0000 vco: [component="SqlExceptionHelper" priority="WARN" thread="Workflow Execution Notification Thread" user="cafe-u_O5_jLqGQ@vsphere.local" context="DKS46OPs" token="8aa9

    0d495b9c441c015b9d5aece9000b" wfid="24ad4ae5-723b-4e10-b344-9bea7a742217" wfname="EventBroker Purge PE Agent Node" anctoken="" wfstack="24ad4ae5-723b-4e10-b344-9bea7a742217" instanceid="f9dd8838-d5

    6b-407b-8458-08f360b36ab8"] SQL Error: 0, SQLState: 22021

    2017-04-26 17:30:11.374+0000 vco: [component="SqlExceptionHelper" priority="ERROR" thread="Workflow Execution Notification Thread" user="cafe-u_O5_jLqGQ@vsphere.local" context="DKS46OPs" token="8aa

    90d495b9c441c015b9d5aece9000b" wfid="24ad4ae5-723b-4e10-b344-9bea7a742217" wfname="EventBroker Purge PE Agent Node" anctoken="" wfstack="24ad4ae5-723b-4e10-b344-9bea7a742217" instanceid="f9dd8838-d

    56b-407b-8458-08f360b36ab8"] ERROR: invalid byte sequence for encoding "UTF8": 0x00

    2017-04-26 17:30:11.374+0000 vco: [component="BatchingBatch" priority="ERROR" thread="Workflow Execution Notification Thread" user="cafe-u_O5_jLqGQ@vsphere.local" context="DKS46OPs" token="8aa90d49

    5b9c441c015b9d5aece9000b" wfid="24ad4ae5-723b-4e10-b344-9bea7a742217" wfname="EventBroker Purge PE Agent Node" anctoken="" wfstack="24ad4ae5-723b-4e10-b344-9bea7a742217" instanceid="f9dd8838-d56b-4

    07b-8458-08f360b36ab8"] HHH000315: Exception executing batch [could not execute batch]

    2017-04-26 17:30:11.388+0000 vco: [component="SCRIPTING_LOG" priority="ERROR" thread="WorkflowExecutorPool-Thread-1" user="cafe-u_O5_jLqGQ@vsphere.local" context="s7DBCXSM" token="8aa90d495b9c441c0

    15bab5030ad01a5" wfid="ca555b29-359c-4fc7-987d-43d6fce720a9" wfname="Add machine to active directory (Event Broker)" anctoken="" wfstack="ca555b29-359c-4fc7-987d-43d6fce720a9" instanceid="f9dd8838-

    d56b-407b-8458-08f360b36ab8"] Workflow execution stack:


    0 0

    No... the developers of this software stack have thought things through a bit more carefully than that. 

     

    mokutil is not by itself able to simply add the certificate directly to the database...  It can only queue the cert for later addition to the database.  After running mokutil, the system must be rebooted.  At boot, the EFI shim bootloader will discover that a MOK request was queued, so it will launch the MOK Manager which will prompt the console operator to confirm the addition of the new certificate.  This process cannot be automated, and requires the manual confirmation of a physically-present user – or, more generally, requires access to the system console in the pre-boot environment, either by physical presence or via Service Processor based console redirection.  Malware cannot complete this step.  If a mokutil request is queued and no-one confirms the request at the console, the system will simply ignore the queued request and continue booting as it did before.

     

    Here's a webpage (unrelated to VMware) which shows pictures of the enrollment process: ELRepo : SecureBootKey

     

    I hope this helps to ease your concerns!

     

    Cheers,

    --

    Darius


    0 0

    Hi guys,

     

    Recently we installed a new vCenter Appliance 6.5 and move all our Horizon View 7 to the new vCenter. So far everything is working fine except the recompose. We are able to create / recompose new Pools but the Pools that were created on the old vCenter are having issues when we tried to recomposed. I found some articles about changes the view composer credential but is not working.

     

    Can you guys give some hands here?

     

     

    View Composer operations fail after vCenter Server has been fully reinstalled using a different machine name (2011962)

     

     

    2017-04-26 13:11:16,055 | 64            | FATAL | Sim.ServiceCore.SimServiceApiImpl - Error: fail to execute web service call: AddDeploymentGroup

    VMware.Sim.CommonLib.Exception.SimCryptoException: Error occurred while decoding OAEP padding.


    0 0

    Hello,
    I have a kit of VMWare essentials. I am interested in adding a 4th host.

     

    I seem to remember that, with vmware essentials, I can't add a 4th host, even for an additional cost. Is that true? If so, is that true for essentials plus as well? Maybe that restriction has been lifted or maybe I mis-remembering.

     

    Thanks


    0 0

    Quick update:

     

    I reinstalled the 2.12.1 agent update without the windows updates that I pushed last time in the same snapshot and it worked.  Installing the windows updates and pushing the new snapshot has broke it again, I will try and narrow it down to the KB that is causing the issue in case anyone comes across something similar.


    0 0

    Having a hard time to get View Planner services up and running on the Desktop.

     

    The Desktop is a Windows7 box.

     

    I downloaded the ViewPlanner Agent for Desktop from controller VM and ran the "Viewplanner_agent_for_Desktop" file.

    Made sure prerequisites were met before running the executable.

    The setup goes through installing a bunch of utilities, however in the end "View planner services start" shows up as failed an highlighted in red.

    Most frustrating part is there is no log file generated under C:\viewplanner-agent-installer.log. I have no clue whats going wrong.


    0 0

    Both Essentials Kits are limited to 3 hosts.

    The only exception that I'm aware of is/was "VMware vSphere Essentials for Retail and Branch Offices", see http://www.vmware.com/content/dam/digitalmarketing/vmware/en/pdf/products/vsphere/vmware-vsphere-essentials-for-retail-a…

     

    André


    0 0

    Running as administrator from PowerShell on Windows 10 64-bit worked for me as well. Thanks for the recommendation!


    0 0
  • 04/26/17--12:23: Re: Migration to VSAN
  • Hello Bala

     

    From what I have seen of Physical to Virtual (P2V) conversions, I have yet to find any tool that is Object-based storage aware and allows direct conversion from non-VMFS disks to vSAN Objects (.vmdk), if anyone knows of such a tool/process do let us know here.

    (vCenter standalone converter lists vSAN-related mention in 6.0 version patch notes but from looking in the Admin guides for 6.0 and 5.5 versions there is zero mention of vSAN!)

     

    Going to go out on a limb and guess possible scenarios here and based on shivam_chawla comment:

     

    P2VSAN(FC Storage) - Migrate OS/Apps running on physical servers backed by FC storage:

    You can do a P2V conversion 'in-place' on the same FC-SAN, just make a VMFS datastore on the same SAN and use vCenter Converter or something similar to P2V from the current storage to the VMFS datastore. Then you can attach these FC VMFS datastores to the vSAN nodes and Storage vMotion to vSAN-datastore and convert them into vSAN-Objects.

     

    P2VSAN(Directly-attached Storage) - Migrate OS/Apps running on physical servers backed by local storage:

    Similar to above, you could attach FC-SAN to the physical box and use converter or some other tool to P2V from the local-storage to the FC VMFS datastores and then SvMotion/migrate to vSAN-datastore.

     

    V2VSAN(FC Storage) - VMs backed by VMFS on FC storage.

    This would just involve attaching these FC VMFS datastores to the vSAN nodes and then Storage vMotioning to vSAN-datastore.

     

    When migrating these from VMFS to vSAN datastore you should be able to choose which vSAN Storage Policy to apply to each VM/Object so that their components are created to adhere to these policies, so create any specific policies you may require prior to this (or just apply vSAN Datastore Default Policy and change them later).

     

    If none of the above is what you are trying to achieve here then please clarify your question further

     

    Bob

     

    -o- If you found this comment useful please click the 'Helpful' button and/or select as 'Answer' if you consider it so, please ask follow-up questions if you have any -o-


    0 0

    Im Still having issues with this , i cant run Hyper V under vmware workstation even when applied the VMX filde mods. Any advice?


    0 0

    I can attest to the fact that PowerShell 4, 5, and 5.1 are all functional in PowerGUI 3.8.0.129.  Unfortunately that will probably be the final version and as much as I love using it I am looking into alternatives.


    0 0
    0 0

    I'm looking to change the domain of my vCSA device. Is this possible or would I be better off creating a new one in the new domain. If so what steps would I need to take to migrate it.

     

    Thanks


    0 0

    Hi Wil,

     

    Thanks for chiming in!

     

    "install the VMware Tools that come with Player."

     

    I tried that first and that's what fails with "vmware-tools.service failed because the control process exited with error code"

     

    "sudo apt-get install build-essential"

     

    gives me -

    build-essential is already the newest version (12.1ubuntu2).

    0 to upgrade, 0 to newly install, 0 to remove and 0 not to upgrade.

     

    "sudo apt-get install kernel-headers"

     

    gives me - E: Unable to locate package kernel-headers

     

    Starting to look like a can of worms..


    0 0

    The only other way I know of for a VM to get created by vRA without annotation is via XAAS.  In which case, on your items tab, make sure they are not in the 'vCenter" tab on the left.  Also, what blueprint created those VMs?  That will also help you track them down.

    The reason for the rule of "not deleting them in vCenter" is that, if vRA has them in its database and you delete them in vCenter, then the only way I know of to clean the vRA database is to do it manually via SQL.  Not a very good thing :-)

     

    Carl L.


    0 0

    Thanks so much for the details!

     

    You have the option key causing the boot menu to be displayed instead of showing the available netboot images.  Is there any way to view or choose between netboot images, or are we restricted to booting to the default image?


    0 0

    Thanks raul for your reply,

    so what would happen to my desktops? Can i use them again or those go to the heaven? ;-)

    It is extremely important to me to manage this problem without any user sense


    0 0

    I'd like to perform a migration where all VMs on 3 datastores are migrated. 

     

    To reduce the performance impact on the source datastores, only two VMs can be svmotioned at a time off of a single datastore. 

     

    However, to decrease the overall time required to complete the storage vmotions, I'd like the script to execute on all 3 datastores at the same time, while limiting concurrent vmotions on any single datastore to two.

     

    Is this possible to accomplish within powercli without adjusting settings in vCenter (like max cost per datastore)?

     

    Thanks!


    0 0

    vmotion, I think not technically possible to give it a VNI

    I imagine vnis means indepdent logical switches only for workload vms

    vmotion kernal interface (dvs backed) will be utilized by all the vms connected with various logical switches/vnis for vmotion

    With respect to vmotion with top of the rack being l2-l3 boundary and esxi clusters/hosts are scattered across dc.

    Therefor, for vmotion to work, vmotion vlan should extend to other esxi hosts over layer 3.

    now question is how pocket moves for vmotion

     

    We need to use vmkernel stack for VMotion/FT/Mgmt etc . However whether we need L3/L2 for VMotion is totally a design choice . For eg : If your existing setup is stretched via OTV for all workloads . Except for VMkernel traffic for all other workloads you can leverage VXLAN via NSX . Technically you can break extended l2 and run it purely like a L3 network and that way you don't need to stretch vlan . Remember VMotion is supported over l3 . Only challenging part would subnet change on one of the the complete DC stack . Not all components would support IP change. So watch out for that and plan it accordingly.

     

     

    outbound traffic

    east west traffic .. what is the path

    is it DLR that decides if it is east west or south north or within the same host

     

    Yes,as long as you are using DLR that would be the deciding factor because for VM that would be the first hop. If we use Edge as first hop,traffic will flow in N-S if Edge and respective Src/Dest VM are on different blades.

     

    since every esxi host has vtep, arp, mac address information for a transport zone,  does it mean traffic will not go to esg but will

    get encasulated by vtep and send towards l3 gateway on the physical network device.

     

    ESG would be paired with external L3 g/w via one of the supported protocol.  ARP/MAC,VTEP learning is a different process(Whether you are learning for the first time or it is already populated) and actual traffic flow is different

    VMware Documentation Library

     

    . To make the explanation simple.VM's on two blades if there is a communication demand. L2/L3 data traffic will always leave the respective blade.

     

    another question which vlan svi this traffic will hit and how..vxlan kernal interface is assigned vlan, but the

    question is .would it mean I would need to extend this transport vlan across all the esxi hosts under a single transport zone

     

    VLAN is optional for vtep  You should certainly read this thread VTEP VLAN limitation


    0 0

    The [WARN ] ADMX-based settings were not (fully) processed successfully message is logged when a setting that is configured through ADMX-based settings already exists in the registry. This usually means that it's been set through Group Policy already, and UEM does not want to overwrite those Group Policy settings.

     

    There's an advanced setting that enables more verbose logging for ADMX-based settings, which will exactly indicate which particularly values were skipped in such a scenario. You can download the advanced settings ADMX template from the VMware Knowledge Base.


older | 1 | .... | 5517 | 5518 | (Page 5519) | 5520 | 5521 | 5522 | newer