Monthly NSX Customer Advisory – May 2017

 Allgemein, Cloud, Knowledge Base, Updates, VMware, VMware Partner, VMware Virtual Infrastructure, vSphere  Kommentare deaktiviert für Monthly NSX Customer Advisory – May 2017
Mai 312017
 

In this communication, we detail the top trending issues with VMware NSX for vSphere and provide you with helpful information on how to address the issues while we build a permanent fix. Please review the left column of the chart below to search for issues specific to your environment, and click on the hyperlinks to access more detailed information on each.

For additional up-to-date, top trending NSX issues, previous and current, please see KB Article Trending support issues in VMware NSX for vSphere 6.x (2131154).

 

NSX for vSphere Version

ComponentIssue SummaryResolution/Work-Around

KB Number

6.2.x , 6.3.xESXiESXi 5.5 and 6.0 hosts fail with a purple diagnostic screen (PSOD): VMCIEventDelayedDispatchCB@com which occurs due to race condition in dvfilter vmci socket deregistration.This issue is resolved in ESXi 5.5 Patch 8 and ESXi 6.0 Patch 3.

To work around this issue, uninstall the dvfilter-dsa driver.

KB : 2149242
6.3.xESXiHosts fails with a purple diagnostic screen when retrieving flows for ALG enabled protocols.To work around this issue, disable flow monitoring related features: IPFix, LiveFlow, Application Rule Manager, Flow monitoring-global flow collection.KB : 2149908

 

Top Issues + Resolution / Workaround

NSX for vSphere 6.3.x, 6.2.x

Issue #1:Process to change VXLAN port from 8472 to 4789 may fail or never complete.

Affected Version: 6.2.x, 6.3.x

Symptom:

  1. The process may fail or never complete while changing the VXLAN port from 8472 to 4789 (standard port assigned by IANA).

Resolution: To resolve the issue, run the REST API calls to check the status of the job and resume the change. For more details, please refer to KB2149996.

 

Issue #2: Guest Introspection USVM reports disk is full.

Affected Version: 6.3.x

Symptom:

  1. You receive an alert that the /var/log disk space is full or almost full on one or more of the Guest Introspection USVMs.
  2. This issue occurs as there is a problem with the internal log maintenance task that causes log files to grow indefinitely, eventually leading to a full disk situation.

Resolution: To work around this issuedelete the Guest Introspection USVM. Click on resolve to redeploy. For more details, please refer to KB2149856.

 

Issue #3: Distributed Firewall (DFW) packets hitting Default Rule instead of previous Rule allowing/blocking designated traffic.

Affected Version: 6.2.x, 6.3.x

Symptom:

  1. In examining Distributed Firewall (DFW) behavior, you may see some packets having a source, destination, and protocol (service) defined in a configured rule hitting the Default rule at the very end of the firewall rule list.
  2. In the dfwpktlogs or in LogInsight, you may see that the SYN packets and the ACK packets are being processed by the configured rule allowing/blocking the defined traffic.
  3. For the same traffic, you see RST and FIN ACK packets hitting the default block/allow rule, meaning that it is not hitting the previously-configured rule.

Resolution: To verify the rules ascribed to the filter or vNIC, type the vsipioctl getrules -f <filtername> command. From this output, you can verify that the configured rule(s) are being applied to the virtual NIC as expected. For more details, please refer to KB2149818

 

Issue #4: VMs are removed from Exclusion List while adding new VM.

Affected Version: 6.2.x, 6.3.x

Symptom:

  1. When attempting to add a virtual machine to the NSX Manager’s Exclusion List to remove the DFW filter from the virtual machine, all other existing excluded virtual machines disappear from the Exclusion List.
  2. In the Web UI, after making the second or duplicate attempt, you may see an error similar to:
    Member: VM is already present in exclude list.

Resolution: To avoid this issue, refresh the UI page before adding the VM to the exclusion list. Refreshing the UI will clear any stale sessions and ensure that if another user has already added the VM, it is now reflected in the UI. For more details, please refer to KB2149997.

 

Issue #5: Backing up the NSX Manager to OpenSSH 7.x or later fails.

Affected Version: 6.2.x, 6.3.x

Symptom:

  1. This issue occurs because the SFTP jar files in the NSX Manager is out of date.

Resolution: To work around this issue, use OpenSSH version 6.x or earlier as your SFTP backup endpoint. For more details, please refer to KB2150053.

 

Trending KB

Issue #1: Re-installing NSX to upgrade vCNS Endpoint to NSX Guest Introspection.

Affected Version: 6.2.x, 6.3.x

Symptom: How to KB.

Resolution: The KB/Solution explains the procedure to upgrade from vCNS to NSX in the environments where vCNS is configured and used for Endpoint only. For more details, please refer to KB2150140.

 

VMware Recommended release

VMware recommends NSX 6.2.6 for new deployments. The minimum version a customer should be running is NSX 6.2.2 based on critical bug fixes identified as having a general impact in an NSX environment. For more information, see Minimum recommended version for NSX for vSphere with GID, ESXi, and vCenter Server (2144295).

 

Have feedback on this NSX Customer Advisory?

We would like to hear from you. Send us your feedback by providing comments on the Feedback Box (available at the bottom of KB Article)Trending support issues in VMware NSX for vSphere 6.x (2131154).


Thank you for helping us continually improve this communication.

 

DO NOT FORGET

Subscribe to my.vmware.com to get timely notifications on NSX Product Releases, Fixes and upcoming patches.

The post Monthly NSX Customer Advisory – May 2017 appeared first on VMware Tech Alliances (TAP) Blog.

Monthly NSX Customer Advisory – May 2017

 Allgemein, Cloud, Knowledge Base, Updates, VMware, VMware Partner, VMware Virtual Infrastructure, vSphere  Kommentare deaktiviert für Monthly NSX Customer Advisory – May 2017
Mai 312017
 

In this communication, we detail the top trending issues with VMware NSX for vSphere and provide you with helpful information on how to address the issues while we build a permanent fix. Please review the left column of the chart below to search for issues specific to your environment, and click on the hyperlinks to access more detailed information on each.

For additional up-to-date, top trending NSX issues, previous and current, please see KB Article Trending support issues in VMware NSX for vSphere 6.x (2131154).

 

NSX for vSphere Version

ComponentIssue SummaryResolution/Work-Around

KB Number

6.2.x , 6.3.xESXiESXi 5.5 and 6.0 hosts fail with a purple diagnostic screen (PSOD): VMCIEventDelayedDispatchCB@com which occurs due to race condition in dvfilter vmci socket deregistration.This issue is resolved in ESXi 5.5 Patch 8 and ESXi 6.0 Patch 3.

To work around this issue, uninstall the dvfilter-dsa driver.

KB : 2149242
6.3.xESXiHosts fails with a purple diagnostic screen when retrieving flows for ALG enabled protocols.To work around this issue, disable flow monitoring related features: IPFix, LiveFlow, Application Rule Manager, Flow monitoring-global flow collection.KB : 2149908

 

Top Issues + Resolution / Workaround

NSX for vSphere 6.3.x, 6.2.x

Issue #1:Process to change VXLAN port from 8472 to 4789 may fail or never complete.

Affected Version: 6.2.x, 6.3.x

Symptom:

  1. The process may fail or never complete while changing the VXLAN port from 8472 to 4789 (standard port assigned by IANA).

Resolution: To resolve the issue, run the REST API calls to check the status of the job and resume the change. For more details, please refer to KB2149996.

 

Issue #2: Guest Introspection USVM reports disk is full.

Affected Version: 6.3.x

Symptom:

  1. You receive an alert that the /var/log disk space is full or almost full on one or more of the Guest Introspection USVMs.
  2. This issue occurs as there is a problem with the internal log maintenance task that causes log files to grow indefinitely, eventually leading to a full disk situation.

Resolution: To work around this issuedelete the Guest Introspection USVM. Click on resolve to redeploy. For more details, please refer to KB2149856.

 

Issue #3: Distributed Firewall (DFW) packets hitting Default Rule instead of previous Rule allowing/blocking designated traffic.

Affected Version: 6.2.x, 6.3.x

Symptom:

  1. In examining Distributed Firewall (DFW) behavior, you may see some packets having a source, destination, and protocol (service) defined in a configured rule hitting the Default rule at the very end of the firewall rule list.
  2. In the dfwpktlogs or in LogInsight, you may see that the SYN packets and the ACK packets are being processed by the configured rule allowing/blocking the defined traffic.
  3. For the same traffic, you see RST and FIN ACK packets hitting the default block/allow rule, meaning that it is not hitting the previously-configured rule.

Resolution: To verify the rules ascribed to the filter or vNIC, type the vsipioctl getrules -f <filtername> command. From this output, you can verify that the configured rule(s) are being applied to the virtual NIC as expected. For more details, please refer to KB2149818

 

Issue #4: VMs are removed from Exclusion List while adding new VM.

Affected Version: 6.2.x, 6.3.x

Symptom:

  1. When attempting to add a virtual machine to the NSX Manager’s Exclusion List to remove the DFW filter from the virtual machine, all other existing excluded virtual machines disappear from the Exclusion List.
  2. In the Web UI, after making the second or duplicate attempt, you may see an error similar to:
    Member: VM is already present in exclude list.

Resolution: To avoid this issue, refresh the UI page before adding the VM to the exclusion list. Refreshing the UI will clear any stale sessions and ensure that if another user has already added the VM, it is now reflected in the UI. For more details, please refer to KB2149997.

 

Issue #5: Backing up the NSX Manager to OpenSSH 7.x or later fails.

Affected Version: 6.2.x, 6.3.x

Symptom:

  1. This issue occurs because the SFTP jar files in the NSX Manager is out of date.

Resolution: To work around this issue, use OpenSSH version 6.x or earlier as your SFTP backup endpoint. For more details, please refer to KB2150053.

 

Trending KB

Issue #1: Re-installing NSX to upgrade vCNS Endpoint to NSX Guest Introspection.

Affected Version: 6.2.x, 6.3.x

Symptom: How to KB.

Resolution: The KB/Solution explains the procedure to upgrade from vCNS to NSX in the environments where vCNS is configured and used for Endpoint only. For more details, please refer to KB2150140.

 

VMware Recommended release

VMware recommends NSX 6.2.6 for new deployments. The minimum version a customer should be running is NSX 6.2.2 based on critical bug fixes identified as having a general impact in an NSX environment. For more information, see Minimum recommended version for NSX for vSphere with GID, ESXi, and vCenter Server (2144295).

 

Have feedback on this NSX Customer Advisory?

We would like to hear from you. Send us your feedback by providing comments on the Feedback Box (available at the bottom of KB Article)Trending support issues in VMware NSX for vSphere 6.x (2131154).


Thank you for helping us continually improve this communication.

 

DO NOT FORGET

Subscribe to my.vmware.com to get timely notifications on NSX Product Releases, Fixes and upcoming patches.

The post Monthly NSX Customer Advisory – May 2017 appeared first on VMware Tech Alliances (TAP) Blog.

VMware vCloud Director: 451 Research Impact Report Explores Expanded Capabilities for Service Providers

 Allgemein, Knowledge Base, Updates, VMware, VMware Partner, VMware Virtual Infrastructure, vSphere  Kommentare deaktiviert für VMware vCloud Director: 451 Research Impact Report Explores Expanded Capabilities for Service Providers
Mai 312017
 

The introduction of vCloud Director 8.20 received analyst coverage from 451 Research, which took a closer look at the platform and the expanded capabilities enabling service providers to manage and operate virtual data centers (VDCs) for multiple customers.

 

Because vCloud Director is VMware&#rsquo;s strategic cloud management platform for service providers, it is designed to support the multi-tenancy and self-service requirements of public cloud (IaaS) and managed hosting providers. For enterprise customers with dedicated private clouds, VMware offers vRealize Automation to accelerate the deployment and management of applications and compute services.

 

The 451 Research Impact Report explored vCloud Director 8.20 and the new features informed by service provider feedback. These include a redesigned and re-implemented user portal, NSX® integration at the API level, and role management with organization and virtual machine affinity. Improved updating processes and automatic discovery and importation of vCenter virtual machines also contribute to a &#rsquo;stable, mature and capable cloud management platform&#rdquo; for service providers, according to 451 Research.

 

Lauded by 451 Research as &#rsquo;one of the most mature and able cloud management platforms extant&#rdquo; with &#rsquo;features tailored to its intended audience, and a track record of developing to answer demand from that specific audience,&#rdquo; vCloud Director is designed to meet the unique needs of service providers, including the rapid on-boarding of customers, monetization of services, and ability to differentiate in a highly competitive managed infrastructure market.

 

The Impact Report focuses on two areas specifically – the new user portal, and NSX integration, which 451 Research calls &#rsquo;a big deal&#rdquo; because it allows providers to tie NSX into billing and metering systems, which in turn enables rapid monetization of NSX-based services and future-proofs vCloud Director.

 

vCloud Director now integrates more closely with VMware NSX network virtualization, which means that service providers can abstract and define more NSX features for individual tenants while customers are able to customize network settings. This enables new, advanced service offerings that give tenants more power to manage their workloads.

 

Moving away from plugins, the new user portal for vCloud Director 8.20 takes advantage of industry-standard HTML5, enabling improved role-based access and controls, and better updates. With a new automated discovery tool service providers can dramatically improve customer on-boarding, especially in a hybrid environment.

 

Watch this video to learn how PhoenixNAP uses VMware vCloud Director to grow its enterprise cloud services business, or read how US Signal is empowering customers to consume resources on-demand and accelerating business growth.

 

Interested in learning more about how vCloud Director can keep you ahead of the competition? Visit vcloudairnetwork.com today. And don&#rsquo;t forget to join in on the conversation at Twitter and like the vCloud page on Facebook.


 

Source: 451 Research: vCloud Director 8.20 and a fresh commitment to VMware&#rsquo;s partners, March 23, 2017 by Carl Brooks

The post VMware vCloud Director: 451 Research Impact Report Explores Expanded Capabilities for Service Providers appeared first on VMware vCloud.

Welcome to VMworld 2017 Europe

 Allgemein, Knowledge Base, Updates, VMware, VMware Partner, VMware Virtual Infrastructure, vSphere  Kommentare deaktiviert für Welcome to VMworld 2017 Europe
Mai 312017
 

Registrati oggi stesso al VMworld 2017 Europe!

###

Le aziende di tutto il mondo stanno affrontando la trasformazione digitale e si affidano a persone come te per poterlo fare! Portatori di cambiamento in grado di sfidare lo status quo, disruptor e visionari. Sono quelli che, dove altri vedono limiti e ostacoli, sono in grado di individuare nuove possibilità e opportunità.

Ecco perché quest&#rsquo;anno il VMworld 2017 Europe è stato creato appositamente per te e per i tuoi colleghi: per offrirvi le conoscenze e gli spunti di cui avete bisogno per tracciare la strada del successo in base alle vostre personali esigenze, sia che si tratti di modernizzare il data center, integrando tutti gli ambienti cloud, sia di supportare clienti e dipendenti offrendo loro esperienze digitali e mobile uniche.

Il VMworld 2017 Europe rappresenta un luogo d&#rsquo;incontro ideale per i professionisti della tecnologia. Unisciti a noi e ai principali esperti del settore per quattro giorni di innovazione, acquisisci nuove competenze e scopri gli strumenti per abilitare il successo del tuo business.

Si tratta di un&#rsquo;occasione unica per conoscere quali sono le tecnologie, i trend e le persone che stanno plasmando il futuro del digital business.

Iscriviti ora e inizia a personalizzare la tua esperienza al VMworld 2017 Europe grazie a una vasta gamma di attività, sessioni e aree a tua disposizione:

  • Keynote del management di VMware sui principali trend del digital business
  • Centinaia di sessioni con esperti e professionisti
  • Sessioni spotlight dedicate alla vision e roadmap strategiche sui temi tecnologici più attuali e rilevanti
  • Hands-On-Labs per acquisire per primi e in modo rapido le competenze sulle soluzioni VMware
  • Certificazione in real-time sulle soluzioni VMware ottenibili con sconti speciali
  • Solution Exchange dove incontrare le aziende dell&#rsquo;ecosistema dei Partner di VMware – dalle aziende enterprise alle start up
  • Confronto aperto con gli esperti di mercato durante i diversi momenti della giornata e durante gli eventi di networking

Unisciti a noi dall&#rsquo;11 al 14 settembre e scopri un mondo dove il software crea possibilità illimitate.
Benvenuto al VMworld 2017 Europe!

Welcome to VMworld 2017 Europe

 Allgemein, Knowledge Base, Updates, VMware, VMware Partner, VMware Virtual Infrastructure, vSphere  Kommentare deaktiviert für Welcome to VMworld 2017 Europe
Mai 312017
 

Registrati oggi stesso al VMworld 2017 Europe!

###

Le aziende di tutto il mondo stanno affrontando la trasformazione digitale e si affidano a persone come te per poterlo fare! Portatori di cambiamento in grado di sfidare lo status quo, disruptor e visionari. Sono quelli che, dove altri vedono limiti e ostacoli, sono in grado di individuare nuove possibilità e opportunità.

Ecco perché quest&#rsquo;anno il VMworld 2017 Europe è stato creato appositamente per te e per i tuoi colleghi: per offrirvi le conoscenze e gli spunti di cui avete bisogno per tracciare la strada del successo in base alle vostre personali esigenze, sia che si tratti di modernizzare il data center, integrando tutti gli ambienti cloud, sia di supportare clienti e dipendenti offrendo loro esperienze digitali e mobile uniche.

Il VMworld 2017 Europe rappresenta un luogo d&#rsquo;incontro ideale per i professionisti della tecnologia. Unisciti a noi e ai principali esperti del settore per quattro giorni di innovazione, acquisisci nuove competenze e scopri gli strumenti per abilitare il successo del tuo business.

Si tratta di un&#rsquo;occasione unica per conoscere quali sono le tecnologie, i trend e le persone che stanno plasmando il futuro del digital business.

Iscriviti ora e inizia a personalizzare la tua esperienza al VMworld 2017 Europe grazie a una vasta gamma di attività, sessioni e aree a tua disposizione:

  • Keynote del management di VMware sui principali trend del digital business
  • Centinaia di sessioni con esperti e professionisti
  • Sessioni spotlight dedicate alla vision e roadmap strategiche sui temi tecnologici più attuali e rilevanti
  • Hands-On-Labs per acquisire per primi e in modo rapido le competenze sulle soluzioni VMware
  • Certificazione in real-time sulle soluzioni VMware ottenibili con sconti speciali
  • Solution Exchange dove incontrare le aziende dell&#rsquo;ecosistema dei Partner di VMware – dalle aziende enterprise alle start up
  • Confronto aperto con gli esperti di mercato durante i diversi momenti della giornata e durante gli eventi di networking

Unisciti a noi dall&#rsquo;11 al 14 settembre e scopri un mondo dove il software crea possibilità illimitate.
Benvenuto al VMworld 2017 Europe!

[Video] Western Carolina University Extends Digital Workspace Solutions Campus-Wide

 Allgemein, Knowledge Base, Updates, VMware, VMware Partner, VMware Virtual Infrastructure, vSphere  Kommentare deaktiviert für [Video] Western Carolina University Extends Digital Workspace Solutions Campus-Wide
Mai 312017
 

Nestled in the mountain town of Cullowhee, Western Carolina University (WCU) is the westernmost school in the University of North Carolina system. From the residence hall to the science lab, the school is extending digital workspace solutions to all corners of the campus and beyond.

WCU was the first campus in the University of North Carolina system to require its students to bring a computer to school. Now its 10,800 students show up with a variety of devices, from desktop and laptop computers to tablets and smartphones. The University needed a way to provide consistent and easy-to-access resources to each student, no matter what kind of device they have or whether the student is on or off campus.

Single Sign-on, Simple Access

The University tied their existing student portal to VMware Workspace ONE using SAML and VMware Identity Manager. Now only one login is needed to access apps, from Microsoft Office 365 to specialized programs for academics. With Workspace ONE, users log in once, then they can launch any desktop, RDSH or Software-as-a-Service (SaaS) applications they have access to.

&#rsquo;The fact that we can consistently and conveniently offer all this software is a huge benefit to our community.&#rdquo;
— Mark Ellersick, Technology Support Analyst, Western Carolina University

Apps are distributed and customized with VMware App Volumes. App Volumes customizes desktops based on student profiles. When a student finishes a class, their access to apps for that class is withdrawn—saving money for WCU&#rsquo;s IT department.

Any App at Any Time

VMware Horizon provides nonpersistent virtual desktops for students. &#rsquo;The great thing about the technology is that students don&#rsquo;t notice it,&#rdquo; said Mark. &#rsquo;They walk into a lab, log in and do their work. When they walk out of that lab and go to their residence, or even to another town or state, they can access that same resource. Now the lab is open 24 hours a day, seven days a week.&#rdquo;

To access published apps, the WCU IT staff uses Horizon&#rsquo;s RDS Hosted Applications feature. If someone doesn&#rsquo;t need access to a full desktop (McGraw cites the University&#rsquo;s IT ticketing system, as an example) they simply authenticate to Horizon and then launch a published app, save files and use network resources from a remote RDSH server as if it were on their local device.

With VMware User Environment Manager, dynamic personalization management manages specific experiences around locations or user groups. For example, campus printers are made available based on users&#rsquo; locations, and UEM makes it easy to add or take away card-key access to electronic locks on campus.

High-Powered Graphics—Not Just for Engineering Class

WCU uses products from VMware partner NVIDIA for both academic and personal computing. NVIDIA GRID cards bring the power of the NVIDIA graphics processing unit (GPU) to Horizon virtual desktops, speeding graphics performance and rendering for applications such as 3D modeling and computer-aided design. To support all the streaming services and videos that students watch in their free time, the WCU IT team is also expanding NVIDIA cards to each host box they deploy.

Windows 10 Made Easy

WCU is finding that virtualization is a big help in getting their community acclimated to Windows 10 as the University begins to upgrade.

Patrick McGraw, virtualization and tier one engineer, said, &#rsquo;Some people are hesitant about adopting Windows 10 because it&#rsquo;s a big change. We created a pool of Windows 10 desktops so people can play with the software and get to know it. Then when we upgrade their machine, they&#rsquo;re already used to the technology, and that makes them happy. We&#rsquo;ve gotten a lot of positive responses.&#rdquo;

&#rsquo;We&#rsquo;re excited, as a university and as an IT department, to give students a consistent experience and really level the playing field. We&#rsquo;re breaking down barriers and making resources more accessible. We&#rsquo;re excited that we can bring everything together in a very intuitive and easy-to-use package.&#rdquo;
—Mark Ellersick

Learn more about the technologies powering WCU&#rsquo;s digital workspace:

  • VMware Identity Manager—A BYOD Solution Everyone Can Agree On
  • The Best Keeps Getting Better: Introducing App Volumes 2.12
  • VMware Horizon 7.1 Technical Deep Dive
  • Understanding the Benefits of User Environment Manager
  • Experience High-Performance Graphics with Free NVIDIA GRID & VMware Blast Extreme Test Drive

The post [Video] Western Carolina University Extends Digital Workspace Solutions Campus-Wide appeared first on VMware End-User Computing Blog.

Why Customizing vROPs Is Important for Your Container Strategy

 Allgemein, Knowledge Base, Updates, VMware, VMware Partner, VMware Virtual Infrastructure, vSphere  Kommentare deaktiviert für Why Customizing vROPs Is Important for Your Container Strategy
Mai 312017
 

Two key takeaways from last month&#rsquo;s DockerCon: containers have gone mainstream and system administrators are paying close attention. Long a haven for developers, this year&#rsquo;s DockerCon in Austin hosted more system administrators than I&#rsquo;d ever seen, and they all seemed to be asking one question:We get it that containers are here to stay; how do we operationalize them?

 

Fortunately, VMware has an easy answer: pretty much the same way you have put any other application into production when you are using our cloud management platform. VMware vCenter and vSphere Integrated Containers (&#rsquo;VIC&#rdquo;) enable system administrators to manage an increasingly diverse application ecosystem, including microservices, cloud-native applications and traditional, monolithic ones, across public and private clouds, all from a common platform. This greatly eases the administrative burden because it means you can manage containers using the same, familiar tools you use to manage your VMs.

 

The challenge of how to monitor containers is a bit more complex. As you might suspect, I&#rsquo;m optimistic that VMware can make that also as simple as possible, but the truth is monitoring microservices is somewhat different and the ability to customize your monitoring solution will be part of the answer for some time to come.

 

vRealize Operations allows for customization of the dashboarding, alerting and reporting functions to easily and effectively monitor containerized services in your enterprise. My approach here is less of a &#rsquo;how to&#rdquo; than a &#rsquo;why&#rdquo;—why is monitoring microservices different than other application types, and how does this affect system administrators?

 

Containers are changing the role of the system administrator, and that role is changing because how we define user communities is changing. It&#rsquo;s no longer as simple as being the SysAdmin for SQL Server or Microsoft Exchange. Microservices are among the cloud-era trends that redefine the composition of users along the lines of who uses a particular service—and it&#rsquo;s not just one app in relative perpetuity, it&#rsquo;s a service that crosses organizational borders and often for a short time (most microservices live for just days). Many of these services are exposed to customers, now bringing the system admin into the customer experience.

 

Microservices, with their short life spans and distributed nature, require more than just standard alerting; they require asking different questions. By creating custom dashboards, alerts and reports that consider the behavior of your microservices, you can derive a meaningful picture of application health; it&#rsquo;s a more holistic approach, one that challenges us all to think beyond individual components and even performance metrics. What is the health of the underlying application?

 

vRealize Operations offers an operationally efficient way to effectively monitor microservices and can easily be customized to derive meaningful data from containerized instances.

 

vROps lets you manage applications, infrastructure, hypervisors and yes, containers, all from one platform. vSphere Integrated Containers lets you easily manage VMs and containers leveraging vCenter, so you don&#rsquo;t have to learn new tools. Clearly as the enterprise becomes more complex, we need to ensure that management domains don&#rsquo;t also grow in number or complexity. VMware keeps it simple by viewing containers as another activity abstracted from physical infrastructure, yet allowing you the tools to gain the insight you or your business users may need.

 

VIC integrates natively with Docker to manage the monitoring and alerting of Docker containers. With microservices you can be less concerned with the container itself and more with the health of what it depends on; the application is broken into many different pieces so you are less concerned with infrastructure and more with app-level metrics (which are offered in vCOPs).

 

vCenter organizes all your containers in a folder; vROps can then monitor the affected resources as a pool or you can customize a dashboard that just dials in on what you need to know. With a custom dashboard a particular system administrator can say: &#rsquo;I only want information on cloud-native-apps#4 and #5.&#rdquo;

 

Custom Alerting:

Best practice: make sure your alerts identify issues before they impact the business, not after. Microservices behave differently than traditional, monolithic applications; vROps uses machine learning to quickly understand the application&#rsquo;s behavior, but it may know more than it can tell you if you haven&#rsquo;t set up your alerting system with that context in mind. The key takeaway here is that before you configure alerts, define what triggers an alert. The mindset of monitoring symptoms calls for re-examination in a container environment; microservices will likely present different symptoms because they use and impact resources differently.

vROps alerts can be built and customized without programming or scripting languages, making it easy for even the newest on the team and driving opex savings in the bargain. Linking alerts with recommended actions and workflows drives further efficiency through automation.

Custom Dashboard:

vROps employs widgets for easy custom dashboarding. An intuitive GUI allows you to draw what you want to see, then paint in the details, such as &#rsquo;Cloud-Native App #4.&#rdquo; This can be helpful for the granularity needed when monitoring a service that may only live for days. The &#rsquo;mashup&#rdquo; chart is an important option for those managing containers: it uses a special widget that brings together disparate pieces of information for a resource, showing a health chart, an anomaly count graph and metric graphs for key performance indicators. Widgets can also help with the sharing of information from one dashboard to another, which helps with troubleshooting.

Custom Reporting:

This rather mundane reality—the need to easily see the activity in your domain—may enjoy a more important role in the containers era. As mentioned, because user communities are changing the role of the system administrator, we may see the need to report to business owners and executives shift as well. Custom reports can be generated quickly, shared (yes, even printed out) and consumed easily well beyond the borders of IT. Again, the &#rsquo;why&#rdquo; of custom reporting when it comes to containers may be as simple as; new business owners are asking new questions for different reasons (for more on &#rsquo;how&#rdquo; see the customization guide link at the bottom of this post).

As cloud matures and microservices become just how we do business, the role of the system administrator may once again settle down to a job description that holds for the eternity of maybe a year. And today&#rsquo;s custom dashboard may be a regular feature in a future release. But I&#rsquo;m not holding my breath. We are in a transition that will last a while, and customizing the monitoring environment for this dynamic ecosystem is imperative to effective operations for containers. Using a single management console robust enough to handle it this complexity makes your job a little simpler.

 

For a deep-dive on customization in vROps, here&#rsquo;s VMware&#rsquo;s definitive guide. For more on containers going mainstream, check out Kit Colbert&#rsquo;s recent post. And for user reviews on vROps, go here.

 

 

The post Why Customizing vROPs Is Important for Your Container Strategy appeared first on VMware Cloud Management.

Using VMware Identity Manager to transform users between Active Directory domains..

 Allgemein, Knowledge Base, Updates, VMware, VMware Partner, VMware Virtual Infrastructure, vSphere  Kommentare deaktiviert für Using VMware Identity Manager to transform users between Active Directory domains..
Mai 312017
 

I get a lot of questions about how to solve Single Sign-On (SSO) of users between two Active Directories without trust. Using the federation protocol SAML and VMware Identity Manager this is easy to achieve.

In my example we have two Domains, A and B. Users in Domain A wants to access resources in Domain B without being prompted for username or password.

Prerequisites

  • You need two VMware Identity Managers. One in each domain.
  • Federate the resource (a web server in my example) in Domain B to VMware Identity Manager in Domain B
  • A user object representing the user must exist in both Domains. One user attribute must be shared across the two domains. In my example I use the Email attribute. The attribute you choose must uniquely identify the user.

If your resource is a Windows application, VMware Horizon and the feature TrueSSO can be used to achieve SSO access for Domain A users into a Windows application running in Domain B.

Establish SAML based trust

First thing first, once the prerequisites are in place next step is to establish a trust between the two VMware Identity Managers. This trust is based on SAML and is much easier to establish than traditional Active Directory trust.

You establish trust by exchanging metadata.xml files between the two Identity Managers. In my example users from Domain A need to access resources in Domain B. So, VMware Identity Manager B must trust Identity Manager A as a third-party Identity Provider (idP).

On the VMware Identity Manager in Domain A navigate to Catalog – Settings – SAML Metadata. Right click on Identity Provider (idP) metadata and choose Copy link address.

Now navigate to the VMware Identity Manager in Domain B and add a third-party idP.

Give the new Identity Provider a name and paste the link to the idp.xml into the metadata field. Scroll down and click Save.

Once saved you&#rsquo;ll see all the settings being populated.

In my example, I&#rsquo;m relying on the Email attribute. Therefore, delete all the other Name ID Formats.

Next configure the user store where your users are in Domain B&#rsquo;s VMware Identity Manager and which network ranges this idP will serve.

You need to create an Authentication Method. I will use Password to login users in Domain A&#rsquo;s VMware Identity Manager. So I named the Authentication Method: domainA_PWD and password typically use SAML Context: urn:oasis:names:tc:SAML:2.0:ac:classes:PasswordProtectedTransport. But obviously here your settings must match your implementation.

Scroll down..

Right click on the SAML Metadata, Service Provider (SP) metadata link and choose Save link as…

Now you have downloaded a file called sp.xml.

Click Save

Still on the VMware Identity Manager in Domain B you need to add the new Authentication Method in your access policy. In my example I simply add it as the last one. In my case I will only support idP initiated flow. If you are planning on supporting SP-init flow you must think about the order of authentication (authN) methods.

In above picture, you can see I added domainA_PWD as the third authN method. (This name was given the authentication method in previous step.)

With these steps, we have now established a SAML based trust. Domain B&#rsquo;s VMware Identity Manager trusts SAML assertions from Domain A&#rsquo;s Identity Manager.

Configure Users

Next step is to make sure you have user objects in both domains sharing the same attribute.

I&#rsquo;m using the Email attribute as the unique User Identifier.

Above is a screenshot of my test user synced into VMware Identity Manager in Domain B.

And below is the user object in my Domain A&#rsquo;s VMware Identity Manager.

As you can see in my example most attributes are the same. But the only important attribute is the Email one. That must be identical in both Domain A and B.

Run a test

Let&#rsquo;s now run a test to verify the SAML trust works from A to B.

We need to create an application in Domain A&#rsquo;s VMware Identity Manager that represents the Identity Manager in Domain B.

In Domain A create a new SAML 2.0 based Web Application.

Paste the content of the sp.xml file you saved previously into the Meta-data XML field and click on Save.

Modify the Configuration to use Email instead of Username:

Name ID Format: Email address

Name ID Value: ${user.email}

Click Save.

Entitle your test user to the newly created application.

Login to VMware Identity Manager in Domain A as your test user.

Click on the application icon representing the VMware Identity Manager in Domain B.

SAML Assertion is generated..

..if all is correctly configured you should now have been Single Sign-On into the VMware Identity Manager in Domain B. Now all resources entitled to the test user in Domain B are possible to consume.

Below is a picture showing what we have configured and tested so far.

While the test was successful. This method is not ideal from an end-user experience perspective. Users have to login to one portal and then get SSO:d into another portal. Next users must launch the application. We can solve this by adding resources from Domain B straight into the portal in Domain A.

Adding remote resources in VMware Identity Manager portal

VMware Identity Manager have one very nice feature and that is that each resource has its own unique launch URL. This can be used in many ways. Customers are placing links that launches applications on their intranet pages and such.. But in this case, we will use it to provide a greater user experience.

First, we need to identify the unique application ID used in the VMware Identity Manager in Domain B.

In above picture, you can easily find the UUID. This is the key to the unique launch URL. For Web Applications, you can also find the unique launch URL under Configuration tab.

But for Horizon resources it is different.. Here you will have to build your own launch URL using the UUID.

The launch URL format is:https://<hostname>/SAAS/API/1.0/GET/apps/launch/app/<resourceUUID>

So now when we know the unique launch URL let&#rsquo;s login to VMware Identity Manager in Domain A and manually create the representation of the resource.

Create a new SAML 2.0 SAML Web Application in Domain A&#rsquo;s VMware Identity Manager.

Configure the new Web Application:

  1. Copy the content of the sp.xml (same one as we used to create the icon for the full Domain B&#rsquo;s VMware Identity Manager) into the metadata field
  2. Name ID Format and Name ID Value should be Email (just the same as we did before)
  3. RelayState, enter the unique Launch URL of the application

Once saved, entitle the new application to your test user..

Now let&#rsquo;s test this new method..

Login to Domain A&#rsquo;s VMware Identity Manager as your test user.

Now launch the application pointing to the unique Launch URL. In my case Office 365 Portal.

SAML Assertion is generated..

..if the configuration is correct you should get straight into your federated application.

That concludes this blog post.. I hope you found it useful.

The post Using VMware Identity Manager to transform users between Active Directory domains.. appeared first on Horizon Tech Blog.

Mai 312017
 

If you’re listening to this podcast you’ve probably heard it said that Nonvolatile memory express (NVMe) is the future of storage. The goal is to give flash drives in a storage network the same I/O speed as one connected directly to a computer via PCIe. This week John and I bring on Flash expert Dave

The post vSpeaking Podcast Episode 46: NVMe appeared first on Virtual Blocks.

Mai 312017
 

みなさん、こんにちは。VMwareでパートナー様を担当させて頂いてますSEの北村です。

今回は、Site Recovery Manager (SRM) のコンパチビリティに関連した次の2点について、Cloud Infrastructure Blog に投稿したいと思います。

1. SRM がサポート対象としている vCenter Server と ESXi のバージョンについて
2. SRM の Guest Operating System Customization Support について

では、それぞれについて記載していきます。

 

1. SRM がサポート対象としている vCenter Server と ESXi のバージョンについて

例えば、SRM 6.5 がサポートしている vCenter Server のバージョンは 6.5 ですが、SRM 6.5 がサポートしている ESXi のバージョンは、vCenter Server 6.5 がサポートしている ESXi と同じバージョンになります。 この事は、Compatibility Matrixes for VMware Site Recovery Manager 6.5 の vCenter Server Requirements と ESXi Server Requirements で確認できます。

ただし、SRM 環境で異なるバージョンの ESXi が混在している場合、仮想マシン・ハードウェア・バージョンなど、vSphere としての互換性が求められる場合があります。 つまり、SRM の保護サイトが vSphere 6.5 ( vCenter Server も ESXi もバージョンは 6.5) で、災害対策サイトが vCenter Server 6.5 と ESXi 6.0 の場合、仮想マシン・ハードウェア・バージョン 13 は、ESXi 6.0 ではサポートされませんので、この様なサイト間では、使用される仮想マシン・ハードウェア・バージョンは 11 より以前のバージョンである必要があります。 この様に、SRM 環境においては、保護サイトと災害対策サイトの 2つのサイトを 1つのシステムとして考える必要があります。

参考情報:Virtual machine hardware versions (1003746)

図1:SRM 6.5 ドキュメント ページ

図2:Compatibility Matrixes for VMware Site Recovery Manager 6.5 ページ

SRM の Compatibility Matrixes は、それぞれの SRM のバージョン毎に存在しています。 上記、図1は最新バージョンの SRM 6.5 のドキュメント ページです。 オレンジ色で囲われている “Site Recovery Manager 6.5 の互換性マトリックス” をクリックすると、図2の SRM 6.5 の Compatibility Matrixes のページが表示されます (他の SRM のバージョンでも同様です)。 Compatibility Matrixes のページは英語表記のみでの提供となっています。

 

2. SRM の Guest Operating System Customization Support について

SRMでは、仮想マシンの IP 設定をカスタマイズする機能を提供しています。この機能を使う事で、仮想マシンが災害対策サイトで起動されるときに、今まで使用していた保護サイトの IP 設定を災害対策サイトの IP 設定に上書きする事ができます。この事を “SRM のゲスト OS の IP カスタマイズ” と、言ったりするのですが、このカスタマイズのサポート対象となるゲストOSのマトリックスを公開しています。

図3:Compatibility Matrixes for VMware Site Recovery Manager 6.5 ページの プルダウンメニュー

図3の SRM 6.5 の Compatibility Matrixes のページで、プルダウンメニューから Guest Operating System Support を選択すると、次の図4のページが表示されます。

図4:SRM 6.5 Compatibility Matrixes ページ

このページ (図4) で、SRM 6.5 でサポート対象となる Guest Operating System SupportGuest Operating System Customization Support について説明していますが、Guest Operating System Customization Support の中で、SRM のゲスト OS の IP カスタマイズのサポート対象を PDF:VMware Guest OS Customization Support Matrix で公開しています。

また、仮想マシンによっては、複数の IP アドレスが割り当てられている場合がありますが、&#rdquo;SRM のゲスト OS の IP カスタマイズ&#rsquo; としてサポートされる構成について、KB (Knowledge Base) を公開しています (英語のみ)。

以下は SRM 6.5 の KB になりますが、SRM 5.8 以降、Operational Limits for Site Recovery Manager X.X (X.X は、5.8、6.0、6.1、または、6.5) という KB を公開しています (KB のサイトで “Operational Limits for Site Recovery Manager” というキーワードで検索すると、他の SRM のバージョンの KB も検索結果から参照できます)。

Operational Limits for Site Recovery Manager 6.5 (2147110)

上記 KB 内で、IP Customization Maximums for Site Recovery Manager 6.5というセクションに記載されている内容 (以下はその抜粋) がサポートされる構成となります。

=== KB2147110 より抜粋 ===
IP Customization Maximums for Site Recovery Manager 6.5
If you implement IP customization for recovered virtual machines, you can configure a maximum of one IP address for each NIC, using DHCP, static IPv4, or static IPv6. For static IPv4 or IPv6 addresses, you provide the following information per NIC:
・1 IP address
・Subnet information
・1 gateway server address
・2 DNS servers (primary and secondary)
====================

上記、KBのポイントは、「仮想マシンの個々 (複数) の vNIC に、それぞれ 1つの IP アドレスが割り当てられている構成がサポートされる構成」 という点です。

似ている構成として、「仮想マシンの 1つ vNIC に複数の IP アドレスが割り当てられている構成」 も考えられますが、以下の KBで公開されている通り、この構成は、SRM の IP カスタマイズではサポートされませんので、ご注意ください。

Can I use multiple IP addresses mapping to a single NIC with vCenter VMware Site Recovery Manager’s IP customization? (2129186)

今回触れた SRM の Compatibility Matrixesですが、日々の活動の中で、意外と存在を知られていない、と感じる事が続いた為、今回はこの件をピックアップしてブログにさせて頂きました。

 

最後まで読んで頂きありがとうございます。今回は以上となります。またの機会をお楽しみに。

The post ちょっとした技術的な TIPs のご紹介 (2017.05) appeared first on Japan Cloud Infrastructure Blog.

Using FlexPod? How to Monitor Oracle Database Performance

 Allgemein, Knowledge Base, Updates, VMware, VMware Partner, VMware Virtual Infrastructure, vSphere  Kommentare deaktiviert für Using FlexPod? How to Monitor Oracle Database Performance
Mai 312017
 

By: Brian Williams

 

In the third part of our three-post series about Blue Medora&#rsquo;s FlexPod Bundle, I&#rsquo;ll be providing insight into how you can drive better performance across your Oracle Database environment.

In case you missed it, check out our other blog posts in this series:

  • Using FlexPod? How to Drive Better Cisco UCS
  • How to Drive Better NetApp Performance with FlexPod

 

What is FlexPod?

FlexPod, which includes Cisco UCS, Cisco Networking and NetApp Storage, was developed by Cisco and NetApp to create an integrated solution for your IT infrastructure — specifically for your computing, networking and storage. The FlexPod Bundle extends to other layers of the IT stack, including your databases.

Check out the third video in our series to learn how you can drive better Oracle Database performance with the FlexPod bundle:

 

With the FlexPod Bundle for vRealize Operations from Blue Medora, garner essential insight into your FlexPod resources and infrastructure with a series of dashboards and reports. In addition to product-specific reporting and analytics as shown in the video above, the FlexPod Bundle from Blue Medora offers dashboards, reports and metrics for the integrated infrastructure as well.

Beyond metrics and reporting, the FlexPod Bundle gives you essential insight into relationship mapping and capacity definitions. Detailed alerts and notifications provide real-time insight into performance problems, enabling you to set thresholds and customize so they fit your unique business requirements. Combined with relationship mapping, you can pinpoint issues as they arise — simplifying troubleshooting so you can repair the issue before it impacts your end users.

 

To learn more about the FlexPod Bundle from Blue Medora or to download a free trial, please visit the True Visibility Suite for VMware vRealize Operations page on Blue Medora&#rsquo;s website.

The post Using FlexPod? How to Monitor Oracle Database Performance appeared first on VMware Cloud Management.

New Subscription Period for VSPs & VTSPs

 Allgemein, Knowledge Base, Updates, VMware, VMware Partner, VMware Virtual Infrastructure, vSphere  Kommentare deaktiviert für New Subscription Period for VSPs & VTSPs
Mai 302017
 

The window of time to complete VSP and VTSP accreditations has changed. Effective May 1, 2017, you will have 90 days from your registration date to fully consume recently introduced VSP and VTSP courses. Please note this will not affect existing training plans or already completed enrollments.

The post New Subscription Period for VSPs & VTSPs appeared first on Partner News.

Enabling Organization Rights in vCloud Director

 Allgemein, Knowledge Base, Updates, VMware, VMware Partner, VMware Virtual Infrastructure, vSphere  Kommentare deaktiviert für Enabling Organization Rights in vCloud Director
Mai 302017
 

vCloud Director 8.20 introduced new services that Tenants can consume from the self-service tenant portal, for e.g., Distributed Firewall configurations, Dynamic Routing, L2 and SSL VPN, etc. By default, these new services are restricted by tenants/organizations. This allows service providers to control the services tenants receive. Service Providers can enable/disable these services to individual tenants based on their service agreements.

 

If, as a service provider, you want to enable services to tenant, you will have to enable them using the Organization Rights. It&#rsquo;s done using an API and involves the below process:

 

  1. Retrieve a list of all rights that can be made available to an organization
  2. Retrieve the list of rights that an organization has currently
  3. Make a list of rights you want to add to the organization comparing 2 to 1
  4. Finally, append the organization rights to the one you want

 

Let’s take a look at an example:

 

1. Retrieve the total rights that can be assigned to any organization, after logging in to vCD API

  • GET https://{{vcloud.example.com}}/api/admin
  • Accept:application/*;version=27.0
  • x-vcloud-authorization:{{authorization}}

 

This call will give you a response which will have an element <RightReferences>, this element will have an extensive list of rights that an organization can have.

 

 

2. Retrieve the right to the organization you want to edit, the reference to the organization can be retrieved from the response in the previous call on /api/admin. In my case I want to edit rights for the Organization &#rsquo;Client1&#rdquo;

 

GET https://{{vcloud.example.com}}/api/admin/org/04ff7b85-6b06-4745-b049-c9a54d12fbd1/rights

Accept:application/*;version=27.0

x-vcloud-authorization:{{authorization}}

 

This call will retrieve the Rights that are currently available to the Organization:

 

 

3. Compare the list of rights that the org has (step 2) compared to what&#rsquo;s generally available from step1, add/append the Rights you want the Org to have.

 

For example, for the Org &#lsquo;Client1&#rsquo; below are the rights in terms of Org-vDC-Gateway:

<RightReference href=”https://10.134.3.58/api/admin/right/f79b15c9-388a-3e1e-8e35-457039998396″ name=”Hybrid Cloud Operations: Create from-the-cloud tunnel” type=”application/vnd.vmware.admin.right+xml”/>

<RightReference href=”https://10.134.3.58/api/admin/right/84ddb40f-a49a-35e1-918e-3f11507825d7″ name=”Organization vDC Gateway: Configure Syslog” type=”application/vnd.vmware.admin.right+xml”/>

<RightReference href=”https://10.134.3.58/api/admin/right/9dc33fcb-346d-30e1-8ffa-cf25e05ba801″ name=”Organization vDC Gateway: Convert to Advanced Networking” type=”application/vnd.vmware.admin.right+xml”/>

<RightReference href=”https://10.134.3.58/api/admin/right/b080bb50-cff1-3258-9683-842d34255a95″ name=”Organization vDC Gateway: Configure Services” type=”application/vnd.vmware.admin.right+xml”/>

<RightReference href=”https://10.134.3.58/api/admin/right/d1c77fc0-a4b9-3d99-bd4b-d7fab35e4fae” name=”Organization vDC Gateway: View” type=”application/vnd.vmware.admin.right+xml”/>

 

And I want to add below new rights:

<RightReference href=”https://10.134.3.58/api/admin/right/b080bb50-cff1-3258-9683-842d34255a95″ name=”Organization vDC Gateway: Configure Services” type=”application/vnd.vmware.admin.right+xml”/>

<RightReference href=”https://10.134.3.58/api/admin/right/84ddb40f-a49a-35e1-918e-3f11507825d7″ name=”Organization vDC Gateway: Configure Syslog” type=”application/vnd.vmware.admin.right+xml”/>

<RightReference href=”https://10.134.3.58/api/admin/right/ff3fc70f-fd25-3c0a-9d90-e7ff82456be5″ name=”Organization vDC Gateway: Configure System Logging” type=”application/vnd.vmware.admin.right+xml”/>

<RightReference href=”https://10.134.3.58/api/admin/right/9dc33fcb-346d-30e1-8ffa-cf25e05ba801″ name=”Organization vDC Gateway: Convert to Advanced Networking” type=”application/vnd.vmware.admin.right+xml”/>

<RightReference href=”https://10.134.3.58/api/admin/right/e90fa73c-3347-3ec7-b407-e25eae2cfe8d” name=”Organization vDC Gateway: Create” type=”application/vnd.vmware.admin.right+xml”/>

<RightReference href=”https://10.134.3.58/api/admin/right/e22e674f-17c3-32cc-ba8a-aecc6733b977″ name=”Organization vDC Gateway: Delete” type=”application/vnd.vmware.admin.right+xml”/>

<RightReference href=”https://10.134.3.58/api/admin/right/bc655eb3-964c-335a-b588-167a9a69cd13″ name=”Organization vDC Gateway: Modify Form Factor” type=”application/vnd.vmware.admin.right+xml”/>

<RightReference href=”https://10.134.3.58/api/admin/right/6122ae98-30b3-3450-b4d1-e1b935e36fbd” name=”Organization vDC Gateway: Update” type=”application/vnd.vmware.admin.right+xml”/>

<RightReference href=”https://10.134.3.58/api/admin/right/93268d9c-3f30-3924-bc2e-9e42bfe6418c” name=”Organization vDC Gateway: Update Properties” type=”application/vnd.vmware.admin.right+xml”/>

<RightReference href=”https://10.134.3.58/api/admin/right/7e1af410-d811-3056-8593-85e2b1808ad9″ name=”Organization vDC Gateway: Upgrade” type=”application/vnd.vmware.admin.right+xml”/>

<RightReference href=”https://10.134.3.58/api/admin/right/d1c77fc0-a4b9-3d99-bd4b-d7fab35e4fae” name=”Organization vDC Gateway: View” type=”application/vnd.vmware.admin.right+xml”/>

<RightReference href=”https://10.134.3.58/api/admin/right/2c4eb5ac-15f5-33f0-8b4a-680b3a1d3707″ name=”Organization vDC Gateway: Configure BGP Routing” type=”application/vnd.vmware.admin.right+xml”/>

<RightReference href=”https://10.134.3.58/api/admin/right/be1abe9a-7ddc-38f6-bdf3-94affb01e46b” name=”Organization vDC Gateway: Configure DHCP” type=”application/vnd.vmware.admin.right+xml”/>

<RightReference href=”https://10.134.3.58/api/admin/right/b755b050-772e-3c9c-9197-111c286f563d” name=”Organization vDC Gateway: Configure Firewall” type=”application/vnd.vmware.admin.right+xml”/>

<RightReference href=”https://10.134.3.58/api/admin/right/209cde55-55db-33f1-8357-b27bba6898ed” name=”Organization vDC Gateway: Configure IPSec VPN” type=”application/vnd.vmware.admin.right+xml”/>

<RightReference href=”https://10.134.3.58/api/admin/right/eeb2b2a0-33a1-36d4-a121-6547ad992d59″ name=”Organization vDC Gateway: Configure L2 VPN” type=”application/vnd.vmware.admin.right+xml”/>

<RightReference href=”https://10.134.3.58/api/admin/right/27be9828-4ce4-353e-8f68-5cd69260d94c” name=”Organization vDC Gateway: Configure Load Balancer” type=”application/vnd.vmware.admin.right+xml”/>

<RightReference href=”https://10.134.3.58/api/admin/right/c9e19573-3d54-3d4a-98f2-f56e446a8ef9″ name=”Organization vDC Gateway: Configure NAT” type=”application/vnd.vmware.admin.right+xml”/>

<RightReference href=”https://10.134.3.58/api/admin/right/3b337aef-42a8-3ed1-8616-341152bc5790″ name=”Organization vDC Gateway: Configure OSPF Routing” type=”application/vnd.vmware.admin.right+xml”/>

<RightReference href=”https://10.134.3.58/api/admin/right/72c5e652-c8d7-3f19-ab83-283d30cb679f” name=”Organization vDC Gateway: Configure Remote Access” type=”application/vnd.vmware.admin.right+xml”/>

<RightReference href=”https://10.134.3.58/api/admin/right/92b7d500-6bb6-3176-b9eb-d1fda4ce444d” name=”Organization vDC Gateway: Configure SSL VPN” type=”application/vnd.vmware.admin.right+xml”/>

<RightReference href=”https://10.134.3.58/api/admin/right/f72af304-97b0-379e-9d6d-68eb89bdc6cf” name=”Organization vDC Gateway: Configure Static Routing” type=”application/vnd.vmware.admin.right+xml”/>

<RightReference href=”https://10.134.3.58/api/admin/right/d9dabcab-579e-33c5-807b-dc9232bf7eff” name=”Organization vDC Gateway: View BGP Routing” type=”application/vnd.vmware.admin.right+xml”/>

<RightReference href=”https://10.134.3.58/api/admin/right/8e16d30d-1ae3-3fff-8d4b-64c342b186a9″ name=”Organization vDC Gateway: View DHCP” type=”application/vnd.vmware.admin.right+xml”/>

<RightReference href=”https://10.134.3.58/api/admin/right/7fee6646-ec0c-34c9-9585-aff6f4d92473″ name=”Organization vDC Gateway: View Firewall” type=”application/vnd.vmware.admin.right+xml”/>

<RightReference href=”https://10.134.3.58/api/admin/right/82beb471-ab7f-3e2b-a615-136ba6645525″ name=”Organization vDC Gateway: View IPSec VPN” type=”application/vnd.vmware.admin.right+xml”/>

<RightReference href=”https://10.134.3.58/api/admin/right/105191de-9e29-3495-a917-05fcb5ec1ad0″ name=”Organization vDC Gateway: View L2 VPN” type=”application/vnd.vmware.admin.right+xml”/>

<RightReference href=”https://10.134.3.58/api/admin/right/2a097e48-f4c4-3714-8b24-552b2d573754″ name=”Organization vDC Gateway: View Load Balancer” type=”application/vnd.vmware.admin.right+xml”/>

<RightReference href=”https://10.134.3.58/api/admin/right/fb860afe-2e15-3ca9-96d8-4435d1447732″ name=”Organization vDC Gateway: View NAT” type=”application/vnd.vmware.admin.right+xml”/>

<RightReference href=”https://10.134.3.58/api/admin/right/eb525145-08e5-3934-91ef-ec80837c9177″ name=”Organization vDC Gateway: View OSPF Routing” type=”application/vnd.vmware.admin.right+xml”/>

<RightReference href=”https://10.134.3.58/api/admin/right/65439584-6aad-3c2c-916f-794099ee85bf” name=”Organization vDC Gateway: View Remote Access” type=”application/vnd.vmware.admin.right+xml”/>

<RightReference href=”https://10.134.3.58/api/admin/right/cdb0edb0-9623-30a8-89de-b133db7cfeab” name=”Organization vDC Gateway: View SSL VPN” type=”application/vnd.vmware.admin.right+xml”/>

<RightReference href=”https://10.134.3.58/api/admin/right/9740be24-4dd7-373c-9237-91896338c11e” name=”Organization vDC Gateway: View Static Routing” type=”application/vnd.vmware.admin.right+xml”/>

<RightReference href=”https://10.134.3.58/api/admin/right/2cd03d47-38e1-337a-907c-8d5b6a5258f2″ name=”Organization vDC Distributed Firewall: Configure Rules” type=”application/vnd.vmware.admin.right+xml”/>

<RightReference href=”https://10.134.3.58/api/admin/right/a100f6a0-2c81-3b61-90c3-c4dbd721b3a8″ name=”Organization vDC Distributed Firewall: Enable/Disable” type=”application/vnd.vmware.admin.right+xml”/>

<RightReference href=”https://10.134.3.58/api/admin/right/4e61b5b8-0964-36b6-b021-da39aea724fc” name=”Organization vDC Distributed Firewall: View Rules” type=”application/vnd.vmware.admin.right+xml”/>

 

Below is a snippet of the final call to append Organization Rights

 

PUT https://{{vcloud.example.com}}/api/admin/org/04ff7b85-6b06-4745-b049-c9a54d12fbd1/rights

Accept:application/*;version=27.0

x-vcloud-authorization:{{authorization}}

Content-Type:application/vnd.vmware.admin.org.rights+xml

 

<?xml version=”1.0″ encoding=”UTF-8″?><Link rel=”edit” href=”https://10.134.3.58/api/admin/org/04ff7b85-6b06-4745-b049-c9a54d12fbd1/rights” type=”application/vnd.vmware.admin.org.rights+xml”/>

<RightReference href=”https://10.134.3.58/api/admin/right/39ec03d4-440d-32cf-8507-f01acd822540″ name=”Catalog: Change Owner” type=”application/vnd.vmware.admin.right+xml”/>

<RightReference href=”https://10.134.3.58/api/admin/right/4886663f-ae31-37fc-9a70-3dbe2f24a8c5″ name=”Catalog: Add vApp from My Cloud” type=”application/vnd.vmware.admin.right+xml”/>

<RightReference href=”https://10.134.3.58/api/admin/right/79b736fb-1cb8-3e25-8ce4-b2c33b66909c” name=”Catalog: Sharing” type=”application/vnd.vmware.admin.right+xml”/>

<RightReference href=”https://10.134.3.58/api/admin/right/893b4d54-5677-3c89-a335-e10f96516e0c” name=”Catalog: Create / Delete a Catalog” type=”application/vnd.vmware.admin.right+xml”/>

<RightReference href=”https://10.134.3.58/api/admin/right/9c449c77-f7d0-3944-bf13-e58abe1ca68c” name=”Catalog: Edit Properties” type=”application/vnd.vmware.admin.right+xml”/>

<RightReference href=”https://10.134.3.58/api/admin/right/e2b61554-7dbf-3f9d-919f-bc59f7564100″ name=”Catalog: CLSP Publish Subscribe” type=”application/vnd.vmware.admin.right+xml”/>

<RightReference href=”https://10.134.3.58/api/admin/right/e2b61554-7dbf-3f9d-919f-bc59f7564153″ name=”Catalog: Publish” type=”application/vnd.vmware.admin.right+xml”/>

<RightReference href=”https://10.134.3.58/api/admin/right/f01671e6-dfad-379d-b8e2-0d18e37ce993″ name=”Catalog: View Published Catalogs” type=”application/vnd.vmware.admin.right+xml”/>

<RightReference href=”https://10.134.3.58/api/admin/right/fa4ce8f8-c640-3b65-8fa5-a863b56c3d51″ name=”Catalog: View Private and Shared Catalogs” type=”application/vnd.vmware.admin.right+xml”/>

<RightReference href=”https://10.134.3.58/api/admin/right/1aa46727-6192-365d-b571-5ce51beb3b48″ name=”vApp Template / Media: View” type=”application/vnd.vmware.admin.right+xml”/>

<RightReference href=”https://10.134.3.58/api/admin/right/3eedbfb4-c4a3-373d-b4b5-d76ca363ab50″ name=”vApp Template / Media: Edit” type=”application/vnd.vmware.admin.right+xml”/>

<RightReference href=”https://10.134.3.58/api/admin/right/444def42-24a8-33b5-a780-13af93b52fac” name=”vApp Template / Media: Copy” type=”application/vnd.vmware.admin.right+xml”/>

<RightReference href=”https://10.134.3.58/api/admin/right/82f79ccf-3039-3436-aa99-06f1911f04eb” name=”vApp Template: Download” type=”application/vnd.vmware.admin.right+xml”/>

<RightReference href=”https://10.134.3.58/api/admin/right/86006d64-9326-3b60-9cbb-d4e511233cc8″ name=”vApp Template / Media: Create / Upload” type=”application/vnd.vmware.admin.right+xml”/>

<RightReference href=”https://10.134.3.58/api/admin/right/ab08b301-7f06-33a6-8f0c-eb8bdaa782d6″ name=”vApp Template: Checkout” type=”application/vnd.vmware.admin.right+xml”/>

<RightReference href=”https://10.134.3.58/api/admin/right/1e5ad20d-1023-34d1-b073-1ea30bce3854″ name=”Disk: Delete” type=”application/vnd.vmware.admin.right+xml”/>

<RightReference href=”https://10.134.3.58/api/admin/right/438e45e9-9389-3e29-9073-638b36921a2a” name=”Disk: Create” type=”application/vnd.vmware.admin.right+xml”/>

<RightReference href=”https://10.134.3.58/api/admin/right/5ddb661d-caf0-3680-9a74-59d4b06137f3″ name=”Disk: Change Owner” type=”application/vnd.vmware.admin.right+xml”/>

<RightReference href=”https://10.134.3.58/api/admin/right/7bbee458-b3c5-3252-ba5a-b1781b1c7b92″ name=”Disk: Edit Properties” type=”application/vnd.vmware.admin.right+xml”/>

<RightReference href=”https://10.134.3.58/api/admin/right/fd036ae5-b78b-3c9f-8f28-a7f6b33d0d92″ name=”Disk: View Properties” type=”application/vnd.vmware.admin.right+xml”/>

<RightReference href=”https://10.134.3.58/api/admin/right/2cd03d47-38e1-337a-907c-8d5b6a5258f2″ name=”Organization vDC Distributed Firewall: Configure Rules” type=”application/vnd.vmware.admin.right+xml”/>

<RightReference href=”https://10.134.3.58/api/admin/right/4e61b5b8-0964-36b6-b021-da39aea724fc” name=”Organization vDC Distributed Firewall: View Rules” type=”application/vnd.vmware.admin.right+xml”/>

<RightReference href=”https://10.134.3.58/api/admin/right/36e20503-17a8-3d25-b0da-9c34beadad0d” name=”Hybrid Cloud Operations: Acquire control ticket” type=”application/vnd.vmware.admin.right+xml”/>

<RightReference href=”https://10.134.3.58/api/admin/right/629c90fd-78a4-3929-98bd-57e4747d067b” name=”Hybrid Cloud Operations: View from-the-cloud tunnel” type=”application/vnd.vmware.admin.right+xml”/>

<RightReference href=”https://10.134.3.58/api/admin/right/62fa6340-394a-3724-afdc-08b67ce7739d” name=”Hybrid Cloud Operations: Update from-the-cloud tunnel endpoint tag” type=”application/vnd.vmware.admin.right+xml”/>

<RightReference href=”https://10.134.3.58/api/admin/right/b0afa930-bafd-358e-a59c-c06057d5f588″ name=”Hybrid Cloud Operations: Acquire from-the-cloud tunnel ticket” type=”application/vnd.vmware.admin.right+xml”/>

<RightReference href=”https://10.134.3.58/api/admin/right/b35346e7-aee3-38e2-a37b-663964dde46e” name=”Hybrid Cloud Operations: Delete from-the-cloud tunnel” type=”application/vnd.vmware.admin.right+xml”/>

<RightReference href=”https://10.134.3.58/api/admin/right/f79b15c9-388a-3e1e-8e35-457039998396″ name=”Hybrid Cloud Operations: Create from-the-cloud tunnel” type=”application/vnd.vmware.admin.right+xml”/>

<RightReference href=”https://10.134.3.58/api/admin/right/84ddb40f-a49a-35e1-918e-3f11507825d7″ name=”Organization vDC Gateway: Configure Syslog” type=”application/vnd.vmware.admin.right+xml”/>

<RightReference href=”https://10.134.3.58/api/admin/right/9dc33fcb-346d-30e1-8ffa-cf25e05ba801″ name=”Organization vDC Gateway: Convert to Advanced Networking” type=”application/vnd.vmware.admin.right+xml”/>

<RightReference href=”https://10.134.3.58/api/admin/right/b080bb50-cff1-3258-9683-842d34255a95″ name=”Organization vDC Gateway: Configure Services” type=”application/vnd.vmware.admin.right+xml”/>

<RightReference href=”https://10.134.3.58/api/admin/right/d1c77fc0-a4b9-3d99-bd4b-d7fab35e4fae” name=”Organization vDC Gateway: View” type=”application/vnd.vmware.admin.right+xml”/>

<RightReference href=”https://10.134.3.58/api/admin/right/e90fa73c-3347-3ec7-b407-e25eae2cfe8d” name=”Organization vDC Gateway: Create” type=”application/vnd.vmware.admin.right+xml”/>

<RightReference href=”https://10.134.3.58/api/admin/right/e22e674f-17c3-32cc-ba8a-aecc6733b977″ name=”Organization vDC Gateway: Delete” type=”application/vnd.vmware.admin.right+xml”/>

<RightReference href=”https://10.134.3.58/api/admin/right/bc655eb3-964c-335a-b588-167a9a69cd13″ name=”Organization vDC Gateway: Modify Form Factor” type=”application/vnd.vmware.admin.right+xml”/>

<RightReference href=”https://10.134.3.58/api/admin/right/6122ae98-30b3-3450-b4d1-e1b935e36fbd” name=”Organization vDC Gateway: Update” type=”application/vnd.vmware.admin.right+xml”/>

<RightReference href=”https://10.134.3.58/api/admin/right/93268d9c-3f30-3924-bc2e-9e42bfe6418c” name=”Organization vDC Gateway: Update Properties” type=”application/vnd.vmware.admin.right+xml”/>

<RightReference href=”https://10.134.3.58/api/admin/right/7e1af410-d811-3056-8593-85e2b1808ad9″ name=”Organization vDC Gateway: Upgrade” type=”application/vnd.vmware.admin.right+xml”/>

<RightReference href=”https://10.134.3.58/api/admin/right/d1c77fc0-a4b9-3d99-bd4b-d7fab35e4fae” name=”Organization vDC Gateway: View” type=”application/vnd.vmware.admin.right+xml”/>

<RightReference href=”https://10.134.3.58/api/admin/right/2c4eb5ac-15f5-33f0-8b4a-680b3a1d3707″ name=”Organization vDC Gateway: Configure BGP Routing” type=”application/vnd.vmware.admin.right+xml”/>

<RightReference href=”https://10.134.3.58/api/admin/right/be1abe9a-7ddc-38f6-bdf3-94affb01e46b” name=”Organization vDC Gateway: Configure DHCP” type=”application/vnd.vmware.admin.right+xml”/>

<RightReference href=”https://10.134.3.58/api/admin/right/b755b050-772e-3c9c-9197-111c286f563d” name=”Organization vDC Gateway: Configure Firewall” type=”application/vnd.vmware.admin.right+xml”/>

<RightReference href=”https://10.134.3.58/api/admin/right/209cde55-55db-33f1-8357-b27bba6898ed” name=”Organization vDC Gateway: Configure IPSec VPN” type=”application/vnd.vmware.admin.right+xml”/>

<RightReference href=”https://10.134.3.58/api/admin/right/eeb2b2a0-33a1-36d4-a121-6547ad992d59″ name=”Organization vDC Gateway: Configure L2 VPN” type=”application/vnd.vmware.admin.right+xml”/>

<RightReference href=”https://10.134.3.58/api/admin/right/27be9828-4ce4-353e-8f68-5cd69260d94c” name=”Organization vDC Gateway: Configure Load Balancer” type=”application/vnd.vmware.admin.right+xml”/>

<RightReference href=”https://10.134.3.58/api/admin/right/c9e19573-3d54-3d4a-98f2-f56e446a8ef9″ name=”Organization vDC Gateway: Configure NAT” type=”application/vnd.vmware.admin.right+xml”/>

<RightReference href=”https://10.134.3.58/api/admin/right/3b337aef-42a8-3ed1-8616-341152bc5790″ name=”Organization vDC Gateway: Configure OSPF Routing” type=”application/vnd.vmware.admin.right+xml”/>

<RightReference href=”https://10.134.3.58/api/admin/right/72c5e652-c8d7-3f19-ab83-283d30cb679f” name=”Organization vDC Gateway: Configure Remote Access” type=”application/vnd.vmware.admin.right+xml”/>

<RightReference href=”https://10.134.3.58/api/admin/right/92b7d500-6bb6-3176-b9eb-d1fda4ce444d” name=”Organization vDC Gateway: Configure SSL VPN” type=”application/vnd.vmware.admin.right+xml”/>

<RightReference href=”https://10.134.3.58/api/admin/right/f72af304-97b0-379e-9d6d-68eb89bdc6cf” name=”Organization vDC Gateway: Configure Static Routing” type=”application/vnd.vmware.admin.right+xml”/>

<RightReference href=”https://10.134.3.58/api/admin/right/d9dabcab-579e-33c5-807b-dc9232bf7eff” name=”Organization vDC Gateway: View BGP Routing” type=”application/vnd.vmware.admin.right+xml”/>

<RightReference href=”https://10.134.3.58/api/admin/right/8e16d30d-1ae3-3fff-8d4b-64c342b186a9″ name=”Organization vDC Gateway: View DHCP” type=”application/vnd.vmware.admin.right+xml”/>

<RightReference href=”https://10.134.3.58/api/admin/right/7fee6646-ec0c-34c9-9585-aff6f4d92473″ name=”Organization vDC Gateway: View Firewall” type=”application/vnd.vmware.admin.right+xml”/>

<RightReference href=”https://10.134.3.58/api/admin/right/82beb471-ab7f-3e2b-a615-136ba6645525″ name=”Organization vDC Gateway: View IPSec VPN” type=”application/vnd.vmware.admin.right+xml”/>

<RightReference href=”https://10.134.3.58/api/admin/right/105191de-9e29-3495-a917-05fcb5ec1ad0″ name=”Organization vDC Gateway: View L2 VPN” type=”application/vnd.vmware.admin.right+xml”/>

<RightReference href=”https://10.134.3.58/api/admin/right/2a097e48-f4c4-3714-8b24-552b2d573754″ name=”Organization vDC Gateway: View Load Balancer” type=”application/vnd.vmware.admin.right+xml”/>

<RightReference href=”https://10.134.3.58/api/admin/right/fb860afe-2e15-3ca9-96d8-4435d1447732″ name=”Organization vDC Gateway: View NAT” type=”application/vnd.vmware.admin.right+xml”/>

<RightReference href=”https://10.134.3.58/api/admin/right/eb525145-08e5-3934-91ef-ec80837c9177″ name=”Organization vDC Gateway: View OSPF Routing” type=”application/vnd.vmware.admin.right+xml”/>

<RightReference href=”https://10.134.3.58/api/admin/right/65439584-6aad-3c2c-916f-794099ee85bf” name=”Organization vDC Gateway: View Remote Access” type=”application/vnd.vmware.admin.right+xml”/>

<RightReference href=”https://10.134.3.58/api/admin/right/cdb0edb0-9623-30a8-89de-b133db7cfeab” name=”Organization vDC Gateway: View SSL VPN” type=”application/vnd.vmware.admin.right+xml”/>

<RightReference href=”https://10.134.3.58/api/admin/right/9740be24-4dd7-373c-9237-91896338c11e” name=”Organization vDC Gateway: View Static Routing” type=”application/vnd.vmware.admin.right+xml”/>

<RightReference href=”https://10.134.3.58/api/admin/right/0b8c8cd2-5af9-32ad-a0bd-dc356503a552″ name=”General: Administrator View” type=”application/vnd.vmware.admin.right+xml”/>

<RightReference href=”https://10.134.3.58/api/admin/right/2cd2d9d7-262c-34f8-8bee-fd92f422cc2c” name=”General: Administrator Control” type=”application/vnd.vmware.admin.right+xml”/>

<RightReference href=”https://10.134.3.58/api/admin/right/68e7ea03-e095-323c-aafd-6f29be6d3997″ name=”General: Send Notification” type=”application/vnd.vmware.admin.right+xml”/>

<RightReference href=”https://10.134.3.58/api/admin/right/2c8d98ef-4acc-3be4-9214-fcb9682b7a19″ name=”Organization vDC Network: View Properties” type=”application/vnd.vmware.admin.right+xml”/>

<RightReference href=”https://10.134.3.58/api/admin/right/b0cfe989-521b-3d7f-9bc2-f23c74a99633″ name=”Organization vDC Network: Edit Properties” type=”application/vnd.vmware.admin.right+xml”/>

<RightReference href=”https://10.134.3.58/api/admin/right/194c71a1-3d68-3156-b789-6a6384028b78″ name=”Organization Network: View” type=”application/vnd.vmware.admin.right+xml”/>

<RightReference href=”https://10.134.3.58/api/admin/right/2637b30e-0394-3b5e-813f-0377700e78d4″ name=”Organization: Import User/Group from IdP while Editing VDC ACL” type=”application/vnd.vmware.admin.right+xml”/>

<RightReference href=”https://10.134.3.58/api/admin/right/30a64c60-c5cc-3b4f-a321-5e6f2bca02c2″ name=”Organization: View” type=”application/vnd.vmware.admin.right+xml”/>

<RightReference href=”https://10.134.3.58/api/admin/right/39946bab-445e-3dfd-8fbe-e9afd2e52971″ name=”Organization: Edit Leases Policy” type=”application/vnd.vmware.admin.right+xml”/>

<RightReference href=”https://10.134.3.58/api/admin/right/4c3f3357-b64d-300c-88d7-780533d6f5a2″ name=”Catalog: View ACL” type=”application/vnd.vmware.admin.right+xml”/>

<RightReference href=”https://10.134.3.58/api/admin/right/60d60d89-6839-3fa7-a24e-cf5bb67cd3ff” name=”Organization: Edit Federation Settings” type=”application/vnd.vmware.admin.right+xml”/>

<RightReference href=”https://10.134.3.58/api/admin/right/6bdadad3-1e25-3a4a-9d39-4927676e09dc” name=”vApp: View ACL” type=”application/vnd.vmware.admin.right+xml”/>

<RightReference href=”https://10.134.3.58/api/admin/right/6cb3596a-15eb-3c2f-a657-5f14f2039719″ name=”Organization Network: Edit Properties” type=”application/vnd.vmware.admin.right+xml”/>

<RightReference href=”https://10.134.3.58/api/admin/right/6f3d4643-da13-3b5d-8f20-6cac72330d8b” name=”Organization: Edit OAuth Settings” type=”application/vnd.vmware.admin.right+xml”/>

<RightReference href=”https://10.134.3.58/api/admin/right/87a1fa5c-86fb-3a1e-9a6a-412f6f6ce419″ name=”Access All Organization VDCs” type=”application/vnd.vmware.admin.right+xml”/>

<RightReference href=”https://10.134.3.58/api/admin/right/a9bb4826-fd63-3df8-b604-119748cc4878″ name=”Organization: Edit Properties” type=”application/vnd.vmware.admin.right+xml”/>

<RightReference href=”https://10.134.3.58/api/admin/right/b065a1c4-4ba4-36b3-8a2b-2e5f2b05abd6″ name=”Organization: Edit Quotas Policy” type=”application/vnd.vmware.admin.right+xml”/>

<RightReference href=”https://10.134.3.58/api/admin/right/bc677a69-c2fe-36f9-a257-a74b21ffe296″ name=”Organization: Edit Association Settings” type=”application/vnd.vmware.admin.right+xml”/>

<RightReference href=”https://10.134.3.58/api/admin/right/c666dbd5-559f-3567-8a3a-ba5938a24c12″ name=”Organization: Edit Password Policy” type=”application/vnd.vmware.admin.right+xml”/>

<RightReference href=”https://10.134.3.58/api/admin/right/e348c652-5b83-32e3-a029-a42df17af02d” name=”Organization vDC: View ACL” type=”application/vnd.vmware.admin.right+xml”/>

<RightReference href=”https://10.134.3.58/api/admin/right/f0c442a1-920a-3259-9577-d9cb414af747″ name=”Organization vDC: Edit ACL” type=”application/vnd.vmware.admin.right+xml”/>

<RightReference href=”https://10.134.3.58/api/admin/right/ffa60ee8-2dd0-37dc-bc3e-17fbc5bdd1ce” name=”Organization: Edit SMTP Settings” type=”application/vnd.vmware.admin.right+xml”/>

<RightReference href=”https://10.134.3.58/api/admin/right/3379f74c-9961-3007-8547-981fcd080d52″ name=”Organization vDC Storage Profile: Set Default” type=”application/vnd.vmware.admin.right+xml”/>

<RightReference href=”https://10.134.3.58/api/admin/right/8cce262a-3ae5-376d-9e06-edc36634b8c8″ name=”Organization vDC: Edit” type=”application/vnd.vmware.admin.right+xml”/>

<RightReference href=”https://10.134.3.58/api/admin/right/f199d4aa-9067-39e0-a504-f625c8404e40″ name=”Organization vDC: Manage Firewall” type=”application/vnd.vmware.admin.right+xml”/>

<RightReference href=”https://10.134.3.58/api/admin/right/f66d8e79-b584-3d79-a501-d71aaa2ebbf9″ name=”Organization vDC: View” type=”application/vnd.vmware.admin.right+xml”/>

<RightReference href=”https://10.134.3.58/api/admin/right/e2201b23-8c93-39d9-8523-715a12895749″ name=”Role: Create, Edit, Delete, or Copy” type=”application/vnd.vmware.admin.right+xml”/>

<RightReference href=”https://10.134.3.58/api/admin/right/268c6111-f8c6-3753-acd1-1e5468f09af6″ name=”Hybrid Cloud Operations: Create to-the-cloud tunnel” type=”application/vnd.vmware.admin.right+xml”/>

<RightReference href=”https://10.134.3.58/api/admin/right/6eae6dec-51b5-3764-a544-a268c842dea0″ name=”Hybrid Cloud Operations: Acquire to-the-cloud tunnel ticket” type=”application/vnd.vmware.admin.right+xml”/>

<RightReference href=”https://10.134.3.58/api/admin/right/c9dafe91-824b-3d41-903a-da5b52114fa3″ name=”Hybrid Cloud Operations: Delete to-the-cloud tunnel” type=”application/vnd.vmware.admin.right+xml”/>

<RightReference href=”https://10.134.3.58/api/admin/right/e1772a14-9246-3af1-9396-8ab5af41d1a9″ name=”Hybrid Cloud Operations: View to-the-cloud tunnel” type=”application/vnd.vmware.admin.right+xml”/>

<RightReference href=”https://10.134.3.58/api/admin/right/5e579955-fe9d-3f0b-bc6b-a3da4db328f1″ name=”Group / User: View” type=”application/vnd.vmware.admin.right+xml”/>

<RightReference href=”https://10.134.3.58/api/admin/right/94b041c2-04cd-3a9b-a3ff-0ba57814cff4″ name=”VDC Template: View” type=”application/vnd.vmware.admin.right+xml”/>

<RightReference href=”https://10.134.3.58/api/admin/right/974452d6-f3a4-3c22-bf8f-e33057d029c7″ name=”VDC Template: Instantiate” type=”application/vnd.vmware.admin.right+xml”/>

<RightReference href=”https://10.134.3.58/api/admin/right/0efcfea8-d79f-3556-8275-0ba6e18ce05b” name=”vApp: Use Console” type=”application/vnd.vmware.admin.right+xml”/>

<RightReference href=”https://10.134.3.58/api/admin/right/1222edb5-adb4-32c4-be70-0e88aef1f03b” name=”vApp: Sharing” type=”application/vnd.vmware.admin.right+xml”/>

<RightReference href=”https://10.134.3.58/api/admin/right/2dc8abec-2e0d-3789-a5f9-ce0453160b53″ name=”vApp: Create / Reconfigure” type=”application/vnd.vmware.admin.right+xml”/>

<RightReference href=”https://10.134.3.58/api/admin/right/4965b0e7-9ed8-371d-8b08-fc716d20bf4b” name=”vApp: Copy” type=”application/vnd.vmware.admin.right+xml”/>

<RightReference href=”https://10.134.3.58/api/admin/right/5250ab79-8f50-33f9-8af5-015cb39c380b” name=”vApp: Edit VM Properties” type=”application/vnd.vmware.admin.right+xml”/>

<RightReference href=”https://10.134.3.58/api/admin/right/580860cd-55bc-322d-ac39-4f9d8e3e1cd2″ name=”vApp: Power Operations” type=”application/vnd.vmware.admin.right+xml”/>

<RightReference href=”https://10.134.3.58/api/admin/right/5ce247aa-6155-3478-97e0-2480ff8747d1″ name=”vApp: Download” type=”application/vnd.vmware.admin.right+xml”/>

<RightReference href=”https://10.134.3.58/api/admin/right/69bc6569-6b5b-3fdf-abaf-e0d16ae0e2d7″ name=”vApp: VM Boot Options” type=”application/vnd.vmware.admin.right+xml”/>

<RightReference href=”https://10.134.3.58/api/admin/right/729a3828-8b63-31b2-88db-f56612a06722″ name=”vApp: Edit VM CPU” type=”application/vnd.vmware.admin.right+xml”/>

<RightReference href=”https://10.134.3.58/api/admin/right/8832800f-575f-3501-ad84-8e15f3898f11″ name=”vApp: Change Owner” type=”application/vnd.vmware.admin.right+xml”/>

<RightReference href=”https://10.134.3.58/api/admin/right/a6984ef7-de84-3d15-8bfd-0c3de0b6bd9d” name=”VAPP_VM_METADATA_TO_VCENTER” type=”application/vnd.vmware.admin.right+xml”/>

<RightReference href=”https://10.134.3.58/api/admin/right/aaea131b-fac0-335a-8734-99c7547d0d13″ name=”vApp: View VM metrics” type=”application/vnd.vmware.admin.right+xml”/>

<RightReference href=”https://10.134.3.58/api/admin/right/ad2ca91e-9541-3869-a960-433e3f502a15″ name=”vApp: Upload” type=”application/vnd.vmware.admin.right+xml”/>

<RightReference href=”https://10.134.3.58/api/admin/right/af90833f-5014-3fa5-b7f7-f2e653ec200b” name=”vApp: Snapshot Operations” type=”application/vnd.vmware.admin.right+xml”/>

<RightReference href=”https://10.134.3.58/api/admin/right/b2bb3262-8724-3775-ab39-f8713782c856″ name=”vApp: Manage VM Password Settings” type=”application/vnd.vmware.admin.right+xml”/>

<RightReference href=”https://10.134.3.58/api/admin/right/c2a29357-1b2a-3f9d-9cd6-de3d525d49f3″ name=”vApp: Edit Properties” type=”application/vnd.vmware.admin.right+xml”/>

<RightReference href=”https://10.134.3.58/api/admin/right/c6c827dc-fc42-33a8-844f-8ab5a91f8a6c” name=”vApp: Edit VM Memory” type=”application/vnd.vmware.admin.right+xml”/>

<RightReference href=”https://10.134.3.58/api/admin/right/cd02b5f8-c54a-334a-b782-5d31a1d77d85″ name=”vApp: Edit VM Hard Disk” type=”application/vnd.vmware.admin.right+xml”/>

<RightReference href=”https://10.134.3.58/api/admin/right/df05c07f-c537-3777-8d9b-a9cfe8d49014″ name=”vApp: Delete” type=”application/vnd.vmware.admin.right+xml”/>

<RightReference href=”https://10.134.3.58/api/admin/right/f24fffde-f953-3976-9f2b-8b355b25881d” name=”vApp: Edit VM Network” type=”application/vnd.vmware.admin.right+xml”/>

<RightReference href=”https://10.134.3.58/api/admin/right/2cd03d47-38e1-337a-907c-8d5b6a5258f2″ name=”Organization vDC Distributed Firewall: Configure Rules” type=”application/vnd.vmware.admin.right+xml”/>

<RightReference href=”https://10.134.3.58/api/admin/right/a100f6a0-2c81-3b61-90c3-c4dbd721b3a8″ name=”Organization vDC Distributed Firewall: Enable/Disable” type=”application/vnd.vmware.admin.right+xml”/>

<RightReference href=”https://10.134.3.58/api/admin/right/4e61b5b8-0964-36b6-b021-da39aea724fc” name=”Organization vDC Distributed Firewall: View Rules” type=”application/vnd.vmware.admin.right+xml”/>

</OrgRights>

 

On successful response, the rights are given to the Org. An authorized user with appropriate rights will be able to configure these services. Check here for how to configure.

Interested in learning more about how vCloud Director can keep you ahead of the competition? Visitvcloudairnetwork.comtoday. And don&#rsquo;t forget to join in on the conversation atTwitterand like the vCloud page onFacebook.

The post Enabling Organization Rights in vCloud Director appeared first on VMware vCloud.

New KB articles published for week ending 27th May 2017

 Allgemein, Knowledge Base, Updates, VMware, VMware Partner, VMware Virtual Infrastructure, vSphere  Kommentare deaktiviert für New KB articles published for week ending 27th May 2017
Mai 302017
 

VMware Workstation

“serial0: Unable to launch virtual printer proxy” error after upgrading Workstation Pro 12.5.5 to 12.5.6
Date of Published:2017/05/24
Cannot launch VMware Workstation on SUSE Linux Enterprise Server 11 and SUSE Linux Enterprise Desktop 11
Date of Published:2017/05/22

VMware vRealize Automation

A Destroy operation on a cluster member prevents Scale Out/Scale In from working as expected in vRA
Date of Published:2017/05/23
Deployments with multiple load balancers incorrectly display load balancer virtual servers in vRA
Date of Published:2017/05/23
Unable to receive a bound property by the Windows CMD script at run time in vRA
Date of Published:2017/05/23

VMware vSphere Data Protection

Backup jobs fail to use HotAdd and fall back to NBD transport method
Date of Published:2017/05/25

VMware vCenter Server

Error: “Service-control failed. Error Failed to start vmon services.vmon-cli RC=1, stderr=Failed to start updatemgr services. Error: Operation timed out”
Date of Published:2017/05/24

VMware ESXi

ESXi host fails with PSOD “NOT_IMPLEMENTED bora/vmkernel/filesystems/devfs/devfs.c:2655”
Date of Published:2017/05/23
Registration/unregistration of third-party IO filter storage provider fails on a host
Date of Published:2017/05/26

VMware User Environment Manager

Folder redirection configured by UEM does not show the redirected location
Date of Published:2017/05/22

VMware Horizon View

Horizon Client cannot logon to Connection Server fails an error http error 505
Date of Published:2017/05/22
Supported Windows Versions for Remote Desktop Systems for Horizon Agent
Date of Published:2017/05/24
Virtual machines are not connected to Network Adapter when deploying from Horizon View
Date of Published:2017/05/23

VMware NSX for vSphere

Publishing Identity Firewall rule fails
Date of Published:2017/05/24

VMware vSAN

Understanding Congestion in vSAN
Date of Published:2017/05/22
vSAN node fails to enter the maintenance mode in current state
Date of Published:2017/05/23

The post New KB articles published for week ending 27th May 2017 appeared first on Support Insider.

Welcome to VMworld 2017 Europe

 Allgemein, Knowledge Base, Updates, VMware, VMware Partner, VMware Virtual Infrastructure, vSphere  Kommentare deaktiviert für Welcome to VMworld 2017 Europe
Mai 302017
 
Register today for VMworld 2017 Europe.

Companies everywhere are transforming into digital businesses. And they&#rsquo;re relying on people like you to make it happen. Change agents and challengers of the status quo. Disruptors and visionaries. Where others see boundaries and obstacles, you find new possibilities and opportunities.

That&#rsquo;s why this year&#rsquo;s VMworld 2017 Europe has been designed for you and your peers. We want you to discover the knowledge and insights you need to chart success on your own terms – whether that be modernising your data center, integrating the power of all clouds, or empowering employees and customers alike with marvellous mobile and digital experiences.

VMworld 2017 Europe is our premier thought leadership and education destination for technology professionals. Join us and the industry&#rsquo;s top thought leaders for four days of innovation and learn new skills, hear expert insights, and gain the tools to enable business success.

This is the one indispensable event to discover the technology, trends and people who are shaping the future of digital business.

Customize your own VMworld 2017 Europe experience

Register now and start customising your own VMworld 2017 Europe experience from a vast array of activities, sessions and areas:

  • Keynotes from top VMware leaders on the biggest digital business trends
  • Hundreds of breakout sessions for VMworld veterans and newcomers alike
  • Spotlight sessions for strategy insights and roadmaps on the most pertinent technology topics of today
  • Be the first to gain new, free and rapid VMware product learning in our Hands-On-Labs
  • Get certified with deep discounts on VMware solutions in real time
  • Visit the Solutions Exchange and meet the companies in VMware&#rsquo;s partner ecosystem – from enterprise organisations to rising stars
  • Socialise with industry experts over lunch, drinks and networking events

Join us at VMworld 2017 Europe on 11-14 September and let us welcome you to a world where software creates unlimited possibilities.

Welcome to VMworld 2017 Europe.