VMware Integrated OpenStack Video Series: Software Update

 Allgemein, Knowledge Base, Updates, VMware, VMware Partner, VMware Virtual Infrastructure, vSphere  Kommentare deaktiviert für VMware Integrated OpenStack Video Series: Software Update
Mrz 112016
 

Cloud administrators need a simple way to update the OpenStack control plane as features are patched. The VMware Integrated OpenStack team included a simplified update utility in the platform to accomplish just that. Patches are applied using either the command line interface on the VIO management server or the VIO plugin in the VMware vSphere web client.

Figure 1 shows the Software Update interface after uploading a patch with the green plus button.

Figure 1: Patch is loaded and ready to apply

During your change control window, you can then click the Apply link. The dialog window shown in Figure 2 will be displayed.

Figure 2: Confirm the patch deployment

Once the patch deployment is complete, the status changes to a green checkmark, and the administrator even has the option to revert the system to the state it was at before the patch was applied! (See Figure 3)

Figure 3: Patch deployment is complete

The following videos steps through the process of applying a patch to a VIO installation in greater detail:

 

Stay tuned for the next installment covering instance resource allocation withVMware vSpherereservations and limits! In the meantime, you can learn more on the VMware Product Walkthrough site and on the VMware Integrated OpenStack product page.

The post VMware Integrated OpenStack Video Series: Software Update appeared first on OpenStack Blog for VMware.

[Video] Q&A with Inna Fabrikant: The Future of Socialcast & Enterprise Collaboration

 Allgemein, Knowledge Base, Updates, VMware, VMware Partner, VMware Virtual Infrastructure, vSphere  Kommentare deaktiviert für [Video] Q&A with Inna Fabrikant: The Future of Socialcast & Enterprise Collaboration
Nov 102015
 

AirWatch’s Maddie Cook had the opportunity to sit down with Inna Fabrikant, Socialcast Sr. Client Development Manager, at AirWatch Connect Atlanta earlier this year. In this Q&A, she shares her unique insights on Socialcast’s capabilities, new feature enhancements and what she sees as the future of Socialcast and the enterprise collaboration market.


So, Inna, what is Socialcast?

Socialcast is an enterprise collaboration platform that enables daily work activities, so things like knowledge sharing, expertise finding, issue resolution, exception handling, things that we all do in our jobs every single day. Also, project management, ideation and secure mobile chat.

The other really special thing about Socialcast is that our customer base ranges from start-ups to the Fortune 500, which I think really speaks to the breadth of the product.

What’s new with Socialcast?

We’ve got a lot of really exciting things going on. The first is our partnership with AirWatch. There’s a real synergy between AirWatch and Socialcast in that both product prioritize mobility and security and collaboration. It’s very natural for us to take Socialcast and combine it with Content Locker, as well as with AirWatch Video, and create what we’ve called the VMware Collaboration Bundle.

The second thing we’re really excited about is our recent Integration Store release. With that release, allowing external applications to post events and updates and notifications directly into the Socialcast stream, and then administrations can actually collaborate around those events.

Lastly, we’re really excited about chat. We took our private messaging capability and turned it into a real-time collaboration experience. We did that because we noticed that a lot of people are much more comfortable sharing in smaller groups rather than with the entire organization. Now, teams can get together and share privately in a very synchronous way. … When they’re ready, they can expose that content to the broader audience. … You can start a conversation with your iPad at home, continue that conversation at your computer at work. … It’s a very persistent, seamless experience.

How would you describe the future of Socialcast and enterprise communication and collaboration?

We’re always innovating and trying to push the envelope. … We’ve looked at unpacking a typical day for a typical employee, and we’ve noticed that there are three themes. Those are triaging, team collaboration and knowledge sharing/crowd sourcing. … Our mission is to really be a secure and seamless cross-platform enterprise collaboration experience that enables daily workflows for individuals, for teams, for executives.

Other blogs you might like:

  • What’s New with Socialcast? We’re Glad You Asked! [Webinar]
  • Socialcast Positioned as a Leader in Aragon Research Globe for Social Software
  • #TipTuesday Pick a Good Platform, But Don’t Focus on the Technology

Inna is a Sr. Client Development Manager with the Socialcast Client Services team. For the past four years, Inna has been managing relationships with some of Socialcast’s largest customers and helping educate the market on the importance of social technology. Prior to joining Socialcast, she helped launch new industry verticals for legal consulting firm Axiom Law. She received her B.A. in Sociology from Columbia University. Follow her on Twitter @innafabrikant.

What’s New with Socialcast? We’re Glad You Asked! [WEBINAR]

 Allgemein, Knowledge Base, Updates, VMware, VMware Partner, VMware Virtual Infrastructure, vSphere  Kommentare deaktiviert für What’s New with Socialcast? We’re Glad You Asked! [WEBINAR]
Okt 272015
 

We’ve been stealthily busy here at Socialcast, helping businesses like yours align their vision and literally get on the same digital page. But it’s been awhile since we shared with you the types of things we’re doing behind the scenes, including some great new product updates, feature enhancements and use case stories. We’d love for you to join us as we answer the question: what’s new with Socialcast?

FREE WEBINAR
What’s New with Socialcast?
Wednesday, October 28
1 p.m. EST

In this 60-minute webinar, learn about the latest features of Socialcast, our enterprise social networking solution and discover how it continues to add value to the VMware Collaboration Bundle. Socialcast experts will walk you through our in-depth product capabilities, including the secure Chat function and Integration Store. We’ll also leave plenty of time for a real-time demo before answering any of your questions.

Can’t attend? We’d still love to get you up-to-speed. Contact one of our experts here for a one-on-one chat: http://socialcast.com/contact-form.

A few more blogs you might like:

  • Fearlessly Innovating with Socialcast: Part 1
  • 90 Days of Preparation, 48 Hours of Execution: All Managed with Socialcast Projects
  • Socialcast Unveils Chat for Secure Instant Messaging & Collaboration

What’s New with Socialcast? We’re Glad You Asked! [WEBINAR]

 Allgemein, Knowledge Base, Updates, VMware, VMware Partner, VMware Virtual Infrastructure, vSphere  Kommentare deaktiviert für What’s New with Socialcast? We’re Glad You Asked! [WEBINAR]
Okt 272015
 

We’ve been stealthily busy here at Socialcast, helping businesses like yours align their vision and literally get on the same digital page. But it’s been awhile since we shared with you the types of things we’re doing behind the scenes, including some great new product updates, feature enhancements and use case stories. We’d love for you to join us as we answer the question: what’s new with Socialcast?

FREE WEBINAR
What’s New with Socialcast?
Wednesday, October 28
1 p.m. EST

In this 60-minute webinar, learn about the latest features of Socialcast, our enterprise social networking solution and discover how it continues to add value to the VMware Collaboration Bundle. Socialcast experts will walk you through our in-depth product capabilities, including the secure Chat function and Integration Store. We’ll also leave plenty of time for a real-time demo before answering any of your questions.

Can’t attend? We’d still love to get you up-to-speed. Contact one of our experts here for a one-on-one chat: http://socialcast.com/contact-form.

A few more blogs you might like:

  • Fearlessly Innovating with Socialcast: Part 1
  • 90 Days of Preparation, 48 Hours of Execution: All Managed with Socialcast Projects
  • Socialcast Unveils Chat for Secure Instant Messaging & Collaboration

Horizon FLEX 1.5 now shipping

 Allgemein, Knowledge Base, Updates, VMware, VMware Partner, VMware Virtual Infrastructure, vSphere  Kommentare deaktiviert für Horizon FLEX 1.5 now shipping
Jun 232015
 
Andy here again. I'm delighted to announce that Horizon FLEX 1.5 is now shipping. This update is huge. We've got server side improvements, client side improvements, probably even improvements in the bit that connects the two! Sorry, I'll try and be serious, this is after all a very big deal. It's been just 6 months […]]>

Horizon FLEX 1.5

Andy here again. I'm delighted to announce that Horizon FLEX 1.5 is now shipping. This update is huge. We've got server side improvements, client side improvements, probably even improvements in the bit that connects the two!

Sorry, I'll try and be serious, this is after all a very big deal. It's been just 6 months since we shipped Horizon FLEX 1.0, and less than 3 months since we shipped 1.1. This release adds many of the features you requested.

  • The ability to remotely wipe a VM from a host machine
  • Granular control over USB devices
  • Policy control over a common file system between the host and client
  • More lenient user controls over RAM and CPU allocation
  • Greater integration with Active Directory for encryption / decryption
  • Limit to single instance of virtual image

We've even improved the way you distribute the Horizon FLEX Clients, and added the ability to make a desktop shortcut for your virtual image. Your users are going to love this.

Watch the introductory video below to learn more.

To access the software, just sign in to your account and download it from either support or from the store.

Thank you.

Apr 302015
 
Recently I was asked by the vBrownbag community to present on vSphere 6 security. vBrownbag is a community-lead podcast series that features online webinars covering various Virtualization and VMware Certification topics, all led by members of the community. It’s an outstanding resource if you are looking to achieve certification or are just in the mood […]]> Recently I was asked by the vBrownbag community to present on vSphere 6 security. vBrownbag is a community-lead podcast series that features online webinars covering various Virtualization and VMware Certification topics, all led by members of the community. It’s an outstanding resource if you are looking to achieve certification or are just in the mood to learn. Read on to see how this webinar went and view for yourself.

What’s really great is that these types of discussions are becoming more and more frequent. I attribute that to VMware’s virtual infrastructure underpinning SO many businesses that the security teams are putting pressure on the IT teams to “make sure it’s secure”. Now, for some of you, you may ask…

Is vSphere security even a popular topic?

The answer is most definitely “YES!” This was made abundantly clear to me last year at VMworld when I asked the ~500 people in my security session some questions. Now, the first clue here is that there were ~500 people in a vSphere security session at VMworld! Holy cow! If I had done that session in 2009 I would have been lucky to pull in 30 attendees!

The first question I asked was “How many here are security professionals who’s main job is IT security?” I’ll guess about 15-30 hands went up. I then asked “How many here are IT/Virtualization professionals who are here because the security guy is on them about securing the virtual infrastructure?”

Every…other…hand went up. Now, I had a pretty good guess that was going to be the answer. But what I think it showed to everyone in the audience is that they are not alone and that security of the virtual infrastructure has finally reached critical mass.

For those of you with access to past VMworld content, the session was INF2336

The vBrownbag Webinar

So, with that in mind, I did the vBrownbag and I had a blast! We discussed the changes in the vSphere Hardening Guide for 6.0 (and showed a sneak peek of some seriously cool PowerCLI stuff!) and then went into some of the updates that have been made in the release. It covers the gamut from easier certificate management to automation of some settings that used to require hand-editing.

You can see in the video below that also we got LOTS of questions. And I got a bunch of questions afterwards via email and Twitter.

Participate!

If you are one of those IT folks who owns the virtual infrastructure and you’re looking to upgrade to vSphere 6 and your IT Security colleagues are challenging you to secure it, this presentation will help. I also encourage you to check out all the other vBrownbag content and even better, contribute your own! Be a part of the community. We’re all in this together and there’s NO shortage of community members that are here to help.

You can find the vBrownbag home page here and the webinar I did here.

Let me know if you have feedback. You can reach me on Twitter as @vspheresecurity or @mikefoley or you can send me email to mfoley at vmware dot com. If there’s a topic you want covered on vSphere security, send it in!

thanks,

mike

Apr 302015
 
Recently I was asked by the vBrownbag community to present on vSphere 6 security. vBrownbag is a community-lead podcast series that features online webinars covering various Virtualization and VMware Certification topics, all led by members of the community. It’s an outstanding resource if you are looking to achieve certification or are just in the mood […]]> Recently I was asked by the vBrownbag community to present on vSphere 6 security. vBrownbag is a community-lead podcast series that features online webinars covering various Virtualization and VMware Certification topics, all led by members of the community. It’s an outstanding resource if you are looking to achieve certification or are just in the mood to learn. Read on to see how this webinar went and view for yourself.

What’s really great is that these types of discussions are becoming more and more frequent. I attribute that to VMware’s virtual infrastructure underpinning SO many businesses that the security teams are putting pressure on the IT teams to “make sure it’s secure”. Now, for some of you, you may ask…

Is vSphere security even a popular topic?

The answer is most definitely “YES!” This was made abundantly clear to me last year at VMworld when I asked the ~500 people in my security session some questions. Now, the first clue here is that there were ~500 people in a vSphere security session at VMworld! Holy cow! If I had done that session in 2009 I would have been lucky to pull in 30 attendees!

The first question I asked was “How many here are security professionals who’s main job is IT security?” I’ll guess about 15-30 hands went up. I then asked “How many here are IT/Virtualization professionals who are here because the security guy is on them about securing the virtual infrastructure?”

Every…other…hand went up. Now, I had a pretty good guess that was going to be the answer. But what I think it showed to everyone in the audience is that they are not alone and that security of the virtual infrastructure has finally reached critical mass.

For those of you with access to past VMworld content, the session was INF2336

The vBrownbag Webinar

So, with that in mind, I did the vBrownbag and I had a blast! We discussed the changes in the vSphere Hardening Guide for 6.0 (and showed a sneak peek of some seriously cool PowerCLI stuff!) and then went into some of the updates that have been made in the release. It covers the gamut from easier certificate management to automation of some settings that used to require hand-editing.

You can see in the video below that also we got LOTS of questions. And I got a bunch of questions afterwards via email and Twitter.

Participate!

If you are one of those IT folks who owns the virtual infrastructure and you’re looking to upgrade to vSphere 6 and your IT Security colleagues are challenging you to secure it, this presentation will help. I also encourage you to check out all the other vBrownbag content and even better, contribute your own! Be a part of the community. We’re all in this together and there’s NO shortage of community members that are here to help.

You can find the vBrownbag home page here and the webinar I did here.

Let me know if you have feedback. You can reach me on Twitter as @vspheresecurity or @mikefoley or you can send me email to mfoley at vmware dot com. If there’s a topic you want covered on vSphere security, send it in!

thanks,

mike

Announcing the availability of the new and improved Workspace Portal Hands-On Lab.

 Allgemein, Knowledge Base, Updates, VMware, VMware Partner, VMware Virtual Infrastructure, vSphere  Kommentare deaktiviert für Announcing the availability of the new and improved Workspace Portal Hands-On Lab.
Okt 272014
 

By Dean Flaming and Jim Yanik – VMware End User Computing Technical Enablement Team

One of the new functionalities of VMware Horizon 6 with View is the ability to handle Global Name Space support with the new Horizon 6 feature known as Cloud Pod Architecture. This ability allows for users of your View environment to easily handle connection to their virtual desktop using a single name no matter where they reside geographically.

History:

For some of you, this may sound familiar under a different name. VMware previously termed this as both Linked Mode View and Multi-Datacenter View at one point or another. We decided upon the name Cloud Pod Architecture simply because using the best practice Pod and Block for design and configuration, Cloud Pod Architecture allowed for the global expansion of VDI pods into a cloud configuration for end users to access via one single name space no matter where they may be.

 

Additional Information:

For an additional technical summary, please see Narasimha Krishnakumar’s blog article, “Horizon 6.0 – Cloud Pod Architecture Details“.

For an introduction on Cloud Pod Architecture, see Narasimha Krishnakumar’s blog article, “VMware Horizon 6 – Introducing Cloud Pod Architecture“.

 

Basic Steps to Setting Up Cloud Pod Architecture:

  1. Setup the 1st Connection Server and View Desktop Pools – This is just the standard setup of Horizon 6 with View.
  2. Setup the 2nd Connection Server and View Desktop Pools – This is duplicating step 1, potentially in a different location or datacenter. It should be noted, there are no requirements to make this identical in configuration to the first View Connection Server.
  3. Setup the Sites (1st and 2nd Site).
      • Initializethe first site ONLY.
      • All other sites will bejoinedto the first site.
    • Setup the Pods (1st and 2nd Pod).
    • Add Pods to Sites.
    • Setup your Global Pools.
    • Add Connection Servers to Global Pools.
    • Entitle Users to Global Pools.

     

    Tips:

      • All configurations are done via command line from the View Connection Servers.
      • All Command Lines use the LMVUTIL.CMD file located in the “C:\Program Files\VMware\VMware View\Server\tools\bin\” folder.
      • All Command Lines Switches are case sensitive (yes, really).

       

      Step-by-Step Setup of Cloud Pod Architecture:

      After setting up at least two View Connection Servers with desktop pools and testing them to ensure they work properly, including assigning users (or test users) to the environments, it is now time to setup the Cloud Pod Architecture feature for supporting a global name space.

       

      Step 1. Initializing the First Pod and Connection Server

      This first step is to initialize the View Connection Server in the primary pod. This makes the primary pod a master.

      Run the following command on Horizon View Connection Server – 1:

      Command:

      lmvutil.cmd –initialize –authDomain [domainname] –authAs [username] –authPassword [password]

      Example:

      lmvutil.cmd –initialize –authDomain corp.local –authAs administrator –authPassword VMware1!

      NOTES:

        • This command turns on the ability to run federated pods.
        • This command must be run once on the primary pod.
        • It can be run on any connection server in the primary pod.
        • It will automatically do LDAP configurations across the Connection Server.
        • DO NOT execute this INITIALIZE command on any other connection server in the primary or secondary pods.
        • This must only be done on one pod in the Global Pool (if this is done on other pods, then they will not be able to join the Global Pool).
        • VIPA is basically a WAN friendly inter-pod replication service – unlike others such as JMS.
        • The Global LDAP listener runs on #TCP 22389 and is a different ADAM instance.

         

        Step 2. Joining the Second Pod to the First Pod from the Second Connection Server

        You are now going to join subsequent pods to the first pod and allow them to synchronize. This must be done from a secondary site connection server.

        Run the following command on the second View Connection Server.

        Command:

        lmvutil.cmd –join –joinServer [primary_connection_server] –userName [domain\username] –password [password] –authDomain [AD.domain] –authAs [username] –authPassword [password]

        Example:

        lmvutil.cmd –join –joinServer hvcs-w8-01.corp.local –userName corp\administrator –password VMware1! –authDomain corp.local –authAs administrator –authPassword VMware1!

        NOTE: The first set of credentials authenticate to the primary connection server for synchronization and the second set of credentials authenticate to the local (secondary) connection server to execute the command.

        NOTICE: This is one of the only commands which must be executed from a secondary connection server.

         

         

        Step 3. Validate Initial Pod and Connection Server Settings

        Go back to the command prompt on the first View Connection Server. You must now validate the initial pod and connection server settings on the initial View Connection Server to ensure the JOIN command done in the previous step on the secondary connection server properly took affect.

        Run the following command on the first View Connection Server.

        Command:

        lmvutil.cmd –listPods –authDomain [AD.domain] –authAs [user] –authPassword [password]

        Example:

        lmvutil.cmd –listPods –authDomain corp.local –authAs administrator –authPassword VMware1!
        NOTES:

          • This will list the pods which the default first site is aware of.
          • Everything is in the default first site at this point.

           

          Step 4. Create the First Site

          You must now organize the environment into multiple sites. To start this process, you must create the first site. This is done on the first View Connection Server.

          Run the following command on the View Connection Server.

          Command:

          lmvutil.cmd –createSite –siteName [site name] –authDomain [AD.domain] –authAs [user] –authPassword [password]

          Example:

          lmvutil.cmd –createSite –siteName Site1 –authDomain corp.local –authAs administrator –authPassword VMware1!

          NOTES:

            • A site is a logical grouping of pods.
            • No response is shown to the command.

             

            Step 5. Create the Second Site

            You must now create the second site. This is done on the first View Connection Server.

            Run the following command on the first View Connection Server.

            Command:

            lmvutil.cmd –createSite –siteName [site name] –authDomain [AD.domain] –authAs [user] –authPassword [password]

            Example:

            lmvutil.cmd –createSite –siteName Site2 –authDomain corp.local –authAs administrator –authPassword VMware1!

            NOTES:

              • No response is shown to the command.

               

              Step 6. Validate Both Sites are Created

              It is important to validate both sites have been properly created to ensure a command was not mistyped.

              Run the following command on the first View Connection Server to validate both sites have been created.

              Command:

              lmvutil.cmd –listSites –authDomain [AD.domain] –authAs [user] –authPassword [password]

              Example:

              lmvutil.cmd –listSites –authDomain corp.local –authAs administrator –authPassword VMware1!

              NOTES:

                • Connection Servers will show in the “Default First Site”.
                • No Connection Servers will show in either of the defined sites (i.e. Site1 or Site2 if using the example commands).

                 

                 

                Step 7. Add the First Pod to the First Site

                Now you need to move the first pod into the first site you created.

                Run the following command on the first View Connection Server.

                Command:

                lmvutil.cmd –assignPodToSite –podName [POD Name] –siteName [Site Name] –authDomain [AD.domain] –authAs [username] –authPassword [password]

                Example:

                lmvutil.cmd –assignPodToSite –podName Cluster-HVCS-W8-01 –siteName Site1 –authDomain corp.local –authAs administrator –authPassword VMware1!

                NOTES:

                  • Naming for the pod defaults to Cluster-[first sever you created it from].
                  • No response is shown to the command.

                   

                  Step 8. Add the Second Pod to the Second Site

                  Now you need to move the second pod into the second site you created previously.

                  Run the following command on the first View Connection Server.

                  Command:

                  lmvutil.cmd –assignPodToSite –podName [POD Name] –siteName [Site Name] –authDomain [AD.domain] –authAs [username] –authPassword [password]

                  Example:

                  lmvutil.cmd –assignPodToSite –podName Cluster-HVCS-W8-02 –siteName Site2 –authDomain corp.local –authAs administrator –authPassword VMware1!

                  NOTES:

                    • Naming for the pod defaults to Cluster-[first sever you created it from].
                    • No response is shown to the command.

                     

                    Step 9. Validate Pods are Joined to Sites

                    You should now validate pods have been successfully moved to their respective sites.

                    Run the following command on the first View Connection Server.

                    Command:

                    lmvutil.cmd –listSites –authDomain [AD.domain] –authAs [user] –authPassword [password]

                    Example:

                    lmvutil.cmd –listSites –authDomain corp.local –authAs administrator –authPassword VMware1!

                    NOTES:

                      • The first View Connection Server should show in the pod cluster owned by the first site.
                      • The second and additional View Connection Servers should show in their respective pod clusters owned by the second or additional sites.

                       

                      Step 10. Creating a Global Pool for Your Local Desktop Pools

                      Now you need to create the Global Entitlement or Global Pool for the Local Desktop Pool. This is the global pool which oversees all local desktop pools which will be associated.

                      Run the following command on the first View Connection Server.

                      Command:

                      lmvutil.cmd –createGlobalEntitlement –entitlementName [Global Entitlement or Parent Pool Name] {–scope [scope] ANY, [Specific Site Name], LOCAL} {[scope options] –isFloating or –isDedicated} –authDomain [AD.domain] –authAs [username] –authPassword [password]

                      Example:

                      lmvutil.cmd –createGlobalEntitlement –entitlementName Win7Floating –scope ANY –isFloating –authDomain corp.local –authAs administrator –authPassword VMware1!

                      NOTES:

                        • Scope Parameters:
                          ANY
                          [specific site]
                          LOCAL
                        • Pool Type:
                          Floating = –isFloating
                          Dedicated = –isDedicated
                        • The GlobalEntitlement creates the Global Pool which then contains local pools from each site.
                        • No response is shown to the command.

                         

                        Step 11. Repeat Step 10 for Additional Global Desktop Entitlements

                        Repeat the previous command for all Global Desktop Pool entitlements (e.g. If you have multiple desktop pools you wish for users to have global entitlements to, then run this step for each Global Desktop Pool entitlement. As an example, in this step we show creating the Global Entitlement for Win 8 Floating Desktops whereas in the previous step we showed creating Global Entitlement for Win 7 Floating Desktops.

                        Run the following command on the first View Connection Server.

                        Command:

                        lmvutil.cmd –createGlobalEntitlement –entitlementName [Global Entitlement or Parent Pool Name] {–scope [scope] ANY, [Specific Site Name], LOCAL} {[scope options] –isFloating or –isDedicated} –authDomain [AD.domain] –authAs [username] –authPassword [password]

                        Example:

                        lmvutil.cmd –createGlobalEntitlement –entitlementName Win8Floating –scope ANY –isFloating –authDomain corp.local –authAs administrator –authPassword VMware1!

                        NOTES:

                            • Scope Parameters:
                              ANY
                              [specific site]
                              LOCAL
                            • Pool Type:
                              Floating = –isFloating
                              Dedicated = –isDedicated
                            • The GlobalEntitlement creates the Global Pool which then contains local pools from each site.
                            • No response is shown to the command.

                             

                            Step 12. Validating the Global Pools

                            Now you need to validate the global pools were properly created. To do this, you need to list the global entitlements.

                            Run the following command on the first View Connection Server.

                            Command:

                            lmvutil.cmd –listGlobalEntitlements –authDomain [AD.domain] –authAs [username] –authPassword [password]

                            Example:

                            lmvutil.cmd –listGlobalEntitlements –authDomain corp.local –authAs administrator –authPassword VMware1!

                            NOTES:

                                  • Each Global Entitlement will show the SCOPE value set to ANY, LOCAL, or the specific site defined.
                                  • Each Global Entitlement will show the DEDICATED value set to TRUE or FALSE based upon whether you defined the entitlement as Dedicated or Floating.

                                   

                                  Step 13. Associate Local Connection Server Desktop Pools to Global Pools

                                  Now you need to associate the local desktop pools (also referred to as child pools) on the first View Connection Server to the GlobalEntitlement or parent pool defined in Step 10.

                                  Run the following command on the first View Connection Server.

                                  Command:

                                  lmvutil.cmd –addPoolAssociation –entitlementName [Global Entitlement or Parent Pool Name] –poolId [Child Pool] –authDomain [AD.Domain] –authAs [username] –authPassword [password]

                                  Example:

                                  lmvutil.cmd –addPoolAssociation –entitlementName Win7Floating –poolId Win7_Desktop –authDomain corp.local –authAs administrator –authPassword VMware1

                                  NOTES:

                                        • Pool ID (poolId) is the View Connection Server Desktop Pool ID defined when assigning the name and ID of the desktop pool during creation.
                                        • View Desktop Pool IDs DO NOT need to be of the same name across View Connection Servers in order for Global Entitlement to work.
                                        • It is the function of this command to tie the Global Pool ID to View Connection Server Pool ID.
                                        • This command must be executed from the connection server containing the Pool ID in question.
                                        • This must be done on a site by site basis.
                                        • No response is shown to the command.

                                         

                                        Step 14. Repeat Step 13 for Additional Global Desktop Entitlements Created in Step 11

                                        Repeat the previous command for all Global Desktop Pool entitlements created in Step 11. As an example, in this step we show associating the Global Entitlement for Win 8 Desktops whereas in the previous step we showed associating Global Entitlement for Win 7 Desktops.

                                        Run the following command on the first View Connection Server.

                                        Command:

                                        lmvutil.cmd –addPoolAssociation –entitlementName [Global Entitlement or Parent Pool Name] –poolId [Child Pool] –authDomain [AD.Domain] –authAs [username] –authPassword [password]

                                        Example:

                                        lmvutil.cmd –addPoolAssociation –entitlementName Win8Floating –poolId Win8_Desktop –authDomain corp.local –authAs administrator –authPassword VMware1!

                                        NOTES:

                                              • Pool ID (poolId) is the View Connection Server Desktop Pool ID defined when assigning the name and ID of the desktop pool during creation.
                                              • View Desktop Pool IDs DO NOT need to be of the same name across View Connection Servers in order for Global Entitlement to work.
                                              • It is the function of this command to tie the Global Pool ID to View Connection Server Pool ID.
                                              • This command must be executed from the connection server containing the Pool ID in question.
                                              • This must be done on a site by site basis.
                                              • No response is shown to the command.

                                               

                                              Step 15. Repeat Steps 13 once for each Secondary Site Created in Step 5

                                              Now you must associate the mirror local desktop (or child) pool to the local desktop (or child) pool which was associated in Step 13 on the first View Connection Server for the Secondary Site. This is done once for each additional Site on the secondary connection servers joined in Step 5.

                                              Run the following command on the secondary View Connection Servers.

                                              Command:

                                              lmvutil.cmd –addPoolAssociation –entitlementName [Global Entitlement or Parent Pool Name] –poolId [Child Pool] –authDomain [AD.Domain] –authAs [username] –authPassword [password]

                                              Example:

                                              lmvutil.cmd –addPoolAssociation –entitlementName Win7Floating –poolId Win7_Desktop –authDomain corp.local –authAs administrator –authPassword VMware1!

                                              NOTES:

                                                    • Pool ID (poolId) is the View Connection Server Desktop Pool ID defined when assigning the name and ID of the desktop pool during creation.
                                                    • View Desktop Pool IDs DO NOT need to be of the same name across View Connection Servers in order for Global Entitlement to work.
                                                    • It is the function of this command to tie the Global Pool ID to View Connection Server Pool ID.
                                                    • This command must be executed from the (secondary) connection server containing the Pool ID in question.
                                                    • This must be done on a site by site basis.
                                                    • No response is shown to the command.

                                                    NOTICE: This is one of the only commands which must be executed from a secondary connection server! Unless otherwise noted, all other commands are executed from the first (or primary) connection server.

                                                     

                                                    Step 16. Repeat Steps 14 once for each Secondary Site Created in Step 5

                                                    Now you must associate the additional mirror local desktop (or child) pools to the local desktop (or child) pools associated in Step 14 on the first View Connection Server for the Secondary Site. This is done once for each additional Site on the secondary connection servers joined in Step 5. As an example, in this step we show associating the Global Entitlement for Win 8 Desktops whereas in the previous step we showed associating Global Entitlement for Win 7 Desktops.

                                                    Run the following command on the secondary View Connection Servers.

                                                    Command:

                                                    lmvutil.cmd –addPoolAssociation –entitlementName [Global Entitlement or Parent Pool Name] –poolId [Child Pool] –authDomain [AD.Domain] –authAs [username] –authPassword [password]

                                                    Example:

                                                    lmvutil.cmd –addPoolAssociation –entitlementName Win8Floating –poolId Win8_Desktop –authDomain corp.local –authAs administrator –authPassword VMware1!

                                                    NOTES:

                                                          • Pool ID (poolId) is the View Connection Server Desktop Pool ID defined when assigning the name and ID of the desktop pool during creation.
                                                          • View Desktop Pool IDs DO NOT need to be of the same name across View Connection Servers in order for Global Entitlement to work.
                                                          • It is the function of this command to tie the Global Pool ID to View Connection Server Pool ID.
                                                          • This command must be executed from the (secondary) connection server containing the Pool ID in question.
                                                          • This must be done on a site by site basis.
                                                          • No response is shown to the command.

                                                          NOTICE: This is one of the only commands which must be executed from a secondary connection server! Unless otherwise noted, all other commands are executed from the first (or primary) connection server.

                                                           

                                                          Step 17. Verify Global Pool Membership on the First Connection Server

                                                          You now need to validate the Global Entitlement settings have been applied correctly. Note the validation command was executed once for each Global Pool Membership (in our example below, twice).

                                                          Run the following command for each Global Pool membership on the first View Connection Server.

                                                          Command:

                                                          lmvutil.cmd –listAssociatedPools –entitlementName [Global Entitlement or Parent Pool Name] –authDomain [AD.Domain] -authAs [username] –authPassword [password]

                                                          Example 1:

                                                          lmvutil.cmd –listAssociatedPools –entitlementName Win7Floating –authDomain corp.local –authAs administrator –authPassword VMware1!

                                                          Example 2:

                                                          lmvutil.cmd –listAssociatedPools –entitlementName Win8Floating –authDomain corp.local –authAs administrator –authPassword VMware1!

                                                          NOTES:

                                                                • Run both commands one right after the other.
                                                                • Note how the results only show remote associated pools.
                                                                • This information will also show up in the View Admin Console Dashboard under the newly created “REMOTE PODS” in the System Health window.

                                                                 

                                                                Step 18. Repeat Step 17 for Each Additional Global Pool Defined in Step 11

                                                                YRepeat the previous command for all Global Desktop Pool entitlements created in Step 11. As an example, in this step we show associating the Global Entitlement for Win 8 Desktops whereas in the previous step we showed associating Global Entitlement for Win 7 Desktops. Note the validation command was executed once for each Global Pool Membership (in our example below, twice).

                                                                Run the following command for each Global Pool membership on the first View Connection Server.

                                                                Command:

                                                                lmvutil.cmd –listAssociatedPools –entitlementName [Global Entitlement or Parent Pool Name] –authDomain [AD.Domain] -authAs [username] –authPassword [password]

                                                                Example 1:

                                                                lmvutil.cmd –listAssociatedPools –entitlementName Win7Floating –authDomain corp.local –authAs administrator –authPassword VMware1!

                                                                Example 2:

                                                                lmvutil.cmd –listAssociatedPools –entitlementName Win8Floating –authDomain corp.local –authAs administrator –authPassword VMware1!

                                                                NOTES:

                                                                      • Run both commands one right after the other.
                                                                      • Note how the results only show remote associated pools.
                                                                      • This information will also show up in the View Admin Console Dashboard under the newly created “REMOTE PODS” in the System Health window.

                                                                       

                                                                      Step 19. Entitle Users to the Global Pools

                                                                      The final step for configuring Global Name Space support is the user entitlements. This can be done by AD Group or AD User. Here we will use AG Groups since that will be the most common use case.

                                                                      You must do this for each group or user you wish to assign to each Global Pool. In the examples for this step we show entitling the CORP\DOMAIN USERS group to both the Win7Floating and Win8Floating pools.

                                                                      Run the following command on the first View Connection Server.

                                                                      Command:

                                                                      lmvutil.cmd –addUserEntitlement [--userName or --groupName] ["DOMAIN\username" or "DOMAIN\Group Name"] –entitlementName [Global Entitlement or Parent Pool Name] –authDomain [AD Domain] -authAs [username] –authPassword [password]

                                                                      Example 1:

                                                                      lmvutil.cmd –addGroupEntitlement –groupName “corp\Domain Users” –entitlementName Win7Floating –authDomain corp.local -authAs administrator –authPassword VMware1!

                                                                      Example 2:

                                                                      lmvutil.cmd –addGroupEntitlement –groupName “corp\Domain Users” –entitlementName Win8Floating –authDomain corp.local -authAs administrator –authPassword VMware1!

                                                                      NOTES:

                                                                            • Entitlements can be User or Group.
                                                                            • User Entitlement = –addUserEntitlement with a setting of –userName and a value of “DOMAIN\User Name”.
                                                                            • Group Entitlement = –addGroupEntitlement with a setting of –groupName and a value of “DOMAIN\Group Name”.
                                                                            • DOMAIN\User Name and DOMAIN\Group Name values must be in quotes if a space exists in the name.
                                                                            • No response is shown to the commands.

                                                                             

                                                                            Step 20. Validating Your Cloud Pod Architecture Configurations

                                                                            Using the View Client, authenticate to either the global name space or one of the connection servers directly. You will notice you can now see all global and local entitled desktops. This includes Local VDI Desktops, Local RDS Desktops, and Global Desktop Pools (VDI or RDS).

                                                                            It is also important to note, local entitlements are not needed for global entitlements to function (e.g. Users do not need to be entitled to local desktops for global desktop entitlements to function properly.

                                                                            At this point, you should test various connection scenarios to get an understanding how this works and why it can be of benefit.

                                                                            NOTES:

                                                                                  • Disable a local desktop pool on the first View Connection Server. You should only see the Global Desktop Pool (associated to the local desktop pool) provide the VDI or RDS desktop from a secondary View Connection Server.
                                                                                  • Disable a local desktop pool on a secondary View Connection Server. You should only see the Global Desktop Pool (associated to the local desktop pool) provide the VDI or RDS desktop from the first View Connection Server (or another associated secondary View Connection Server in the Global Pool).
                                                                                  • Reprovision groups or users to local desktop pools on the secondary View Connection Server(s). When reconnecting the Horizon Client to your global name space, what do you see? Why or why not (hint, what does global name space resolve to)? What happens when you connect directly to secondary View Connection Server instead?

                                                                                   

                                                                                   

                                                                                  Wrap Up and Call To Action:

                                                                                  This concludes the lab module on View Global Namespace Support provided by the Horizon View Cloud Pod Architecture feature.

                                                                                  Go and familiarize yourself with the installation of Horizon 6 with View and then take time to walk through the configuration of Cloud Pod Architecture and play with its various configurations in the Horizon 6 Introductory Hands On Lab. To access this lab directly, visit the Lab Registration Form to get started!

                                                                                  For more information on VMware Hands On Labs, visit hol.vmware.com and sign up!

                                                                                  Jun 132014
                                                                                   
                                                                                  Today VMware released an update to its virtualization management solution, vCenter Server. The update brings several fixes as documented in the release notes which can be reviewed in full here. The new versions are as follows: vCenter Server 5.5 Update 1b | 12 JUN 2014 | Build 1891313 vCenter Server 5.5 Update 1b Installation Package […]]> Today VMware released an update to its virtualization management solution, vCenter Server. The update brings several fixes as documented in the release notes which can be reviewed in full here.

                                                                                  The new versions are as follows:

                                                                                  • vCenter Server 5.5 Update 1b | 12 JUN 2014 | Build 1891313
                                                                                  • vCenter Server 5.5 Update 1b Installation Package | 12 JUN 2014 | Build 1891310
                                                                                  • vCenter Server Appliance 5.5 Update 1b | 12 JUN 2014 | Build 1891314
                                                                                    downloaded now from vmware.com

                                                                                  A quick overview of the updates contained in this release cover Security, Server Configuration and Virtual SAN

                                                                                  Security

                                                                                  • Update to OpenSSL library addresses security issues
                                                                                    OpenSSL libraries have been updated to versionsopenssl-0.9.8za,openssl-1.0.0m, andopenssl-1.0.1hto addressCVE-2014-0224.

                                                                                  Server Configuration

                                                                                  • Host profile answer file might not be applied when you reboot the ESXi host
                                                                                    After you restart the vCenter services, if you use Auto Deploy to reboot a stateless ESXi host, the host profile answer file might not be applied to the ESXi host and the host configuration might fail. This issue occurs if the reference host is not available.This issue is resolved in this release.

                                                                                  Virtual SAN

                                                                                  • Under certain conditions, Virtual SAN storage providers might not be created automatically after you enable Virtual SAN on a cluster
                                                                                    When you enable Virtual SAN on a cluster, Virtual SAN might fail to automatically configure and register storage providers for the hosts in the cluster, even after you perform a resynchronization operation.
                                                                                    This issue is resolved in this release. You can view the Virtual SAN storage providers after resynchronization.To resynchronize, click the synchronize icon in theStorage Providerstab.

                                                                                  For new installations review thevSphere Installation and Setupdocumentation. For upgrading from a previous version of vCenter Server, please review thevSphere Upgradedocumentation before proceeding.

                                                                                  VMware Fusion Technology Preview May 2014

                                                                                   Allgemein, Knowledge Base, Updates, VMware, VMware Partner, VMware Virtual Infrastructure, vSphere  Kommentare deaktiviert für VMware Fusion Technology Preview May 2014
                                                                                  Mai 222014
                                                                                   
                                                                                  Today the VMware Fusion team is providing public access to the VMware Fusion Technology Preview. We would like to get feedback from individuals using a wide range of hardware and software configurations. The VMware Fusion Technology Preview includes: VMware Hardware Version 11, including improved CPU support and upgraded USB 3.0 controller New icons in the […]]> Today the VMware Fusion team is providing public access to the VMware Fusion Technology Preview. We would like to get feedback from individuals using a wide range of hardware and software configurations.

                                                                                  The VMware Fusion Technology Preview includes:

                                                                                  • VMware Hardware Version 11, including improved CPU support and upgraded USB 3.0 controller
                                                                                  • New icons in the library show state of VMs
                                                                                  • Ability to configure per-VM hotkeys
                                                                                  • Support for configuring the amount of graphics memory for each VM
                                                                                  • Updated support for multi-monitor setups where one monitor is a Retina-class display

                                                                                  Additional details, including a list of what’s new, and the VMware Fusion Technology Preview May 2014 download are available HERE from the VMware Fusion Community.

                                                                                  Please post all of your feedback in the VMware Fusion Preview 2014 Community forum. Our Developers, Quality Assurance Engineers, Support Teams, Technical Writers, Product Marketing Managers, and Product Managers will be monitoring the forum to ensure that we collect your suggestions and comments.

                                                                                  Many thanks for helping us to improve VMware Fusion.

                                                                                  The VMware Fusion Team

                                                                                  Mai 082014
                                                                                   
                                                                                  Microsoft Windows XP end of support (AKA the XPocalypse) has come and gone, and we are all still here. However, a recent Microsoft security alert should give Windows XP users cause for concern as it potentially exposes them to serious security risks. Luckily, Microsoft issued a patch on May 1st – including Windows XP. The […]]> Microsoft Windows XP end of support (AKA the XPocalypse) has come and gone, and we are all still here.

                                                                                  However, a recent Microsoft security alert should give Windows XP users cause for concern as it potentially exposes them to serious security risks. Luckily, Microsoft issued a patch on May 1st – including Windows XP.

                                                                                  The issue is that XP users can’t expect Microsoft to continue to provide security updates for their operating system as support officially ended on April 8th.

                                                                                  If you must continue using XP for a while longer, you can run your critical Windows XP applications in a VMware Fusion virtual environment and get the following benefits:

                                                                                  • Forward compatibility—virtualization lets you run 12-year-old XP on today’s hardware.
                                                                                  • Reduced vulnerability—putting XP into a virtual machine isolates it, enabling you to turn off features that make it vulnerable.
                                                                                  • Safe state rollback—Fusion allows you to take periodic snapshots of a virtual machine that serves as a backup should your XP virtual machine become corrupted.

                                                                                  Click here to learn more about virtualizing Windows XP–and stay tuned for an upcoming blog with tips for what VMware Fusion users can do to protect XP running in Fusion from further security exploits.

                                                                                  Celebrate Earth Day and save on VMware Fusion

                                                                                   Allgemein, Knowledge Base, Updates, VMware, VMware Partner, VMware Virtual Infrastructure, vSphere  Kommentare deaktiviert für Celebrate Earth Day and save on VMware Fusion
                                                                                  Apr 212014
                                                                                   
                                                                                  Go green—consolidate all your PCs into one with Fusion Virtualization is a green choice because the technology allows you to run multiple virtual machines on one physical computer. When using Fusion 6 to run Windows on your Mac, you eliminate the need to have two computers, saving on energy costs and reducing your carbon footprint. […]]>

                                                                                  Go green—consolidate all your PCs into one with Fusion

                                                                                  Virtualization is a green choice because the technology allows you to run multiple virtual machines on one physical computer. When using Fusion 6 to run Windows on your Mac, you eliminate the need to have two computers, saving on energy costs and reducing your carbon footprint.

                                                                                  And, since Fusion 6 is optimized to give you fast performance while efficiently utilizing your Mac’s battery power, you save even more.

                                                                                  Make a green choice and save up to 20% on Fusion:

                                                                                  • Buy Fusion 6 Professional and save 20% off Regular List Price
                                                                                  • Upgrade to Fusion 6 Professional and save 20% off Regular List Price
                                                                                  • Buy Fusion 6 and save 10% off Regular List Price
                                                                                  • Upgrade to Fusion 6 and save 10% off Regular List Price

                                                                                  This offer begins on April 21, 2014, at 8:00 pm Pacific Time and expires on April 24, 2014, at 11:59 pm Pacific Time.

                                                                                  Apr 182014
                                                                                   
                                                                                  On April 17th we released VMware Fusion 6.0.3, a maintenance release. This update is recommended for all users of VMware Fusion 6 and Fusion 6 Professional. To download VMware Fusion 6.0.3, open VMware Fusion and select VMware Fusion > Check for Updates. For more details on Fusion 6.0.3, read the Release Notes. Thanks to the […]]> On April 17th we released VMware Fusion 6.0.3, a maintenance release. This update is recommended for all users of VMware Fusion 6 and Fusion 6 Professional.

                                                                                  To download VMware Fusion 6.0.3, open VMware Fusion and select VMware Fusion > Check for Updates.

                                                                                  For more details on Fusion 6.0.3, read the Release Notes.

                                                                                  Thanks to the Fusion customers reporting these issues to Fusion Support and discussing them with the VMware Fusion Community.

                                                                                  -The VMware Fusion Team

                                                                                  VMware VirtualCenter 2.5 Update 5

                                                                                   Allgemein, Updates, VMware ESX, VMware Virtual Infrastructure  Kommentare deaktiviert für VMware VirtualCenter 2.5 Update 5
                                                                                  Jul 162009
                                                                                   

                                                                                  VMware releases Update 5 for VirtualCenter 2.5

                                                                                  More information @ VMware Support website >> http://www.vmware.com/support/vi3/doc/vi3_vc25u5_rel_notes.html

                                                                                  New: Support for High Consolidation in VMware HA Clusters – VirtualCenter 2.5 Update 5 includes significant performance and scalability improvements to VMware HA. Use VirtualCenter 2.5 Update 5 for environments with more than 35 virtual machines per host in an HA cluster.
                                                                                  For information on the ESX Server host settings required for this scalability improvement, see ESX Server host settings required for environments with up to 80 virtual machines per host in an HA Cluster (KB 1012002).


                                                                                  VMware patcht zahlreiche Sicherheitslücken in seinen Produkten

                                                                                   Updates, VMware, VMware ESX, VMware Workstation  Kommentare deaktiviert für VMware patcht zahlreiche Sicherheitslücken in seinen Produkten
                                                                                  Apr 102009
                                                                                   

                                                                                  Via Heise Newsticker>>

                                                                                  Der Hersteller VMware hat mehrere Sicherheitsprobleme in seinen Produkten behoben und aktualisierte Fassungen für die Workstation, den Player, ACE, Server, ESXi und ESX veröffentlicht. Unter anderem lässt sich ein Fehler in einem virtuellen Gerätetreiber ausnutzen, um aus dem Gastsystem heraus den Wirt zum Absturz zu bringen. Ein ähnliches Problem weist laut Bericht der Treiber hcmon.sys unter Windows auf. Allerdings kann nur ein privilegierter Windows-Anwender den Absturz provozieren. Bei der Verarbeitung zu langer Parameter kann der Dienst vmware-authd ebenfalls abstürzen.

                                                                                  Auf Windows-Systemen können Angreifer einen Fehler im Treiber für das Virtual Machine Communication Interface (VMCI) sowohl auf dem Gast als auch im Wirt ausnutzen, um an höhere Rechte zu gelangen. VMware ESX ist davon aber nicht betroffen. Von einem Heap Overflow im VNnc Codec ist VMware ESX ebenfalls nicht betroffen. Auf anderen Systemen genügt es, einen präparierten VNnc-Film zu öffnen oder eine manipulierte Webseite zu besuchen, um Opfer eines Angriffs zu werden.

                                                                                  Zudem liegt nach dem Login das Passwort für den VirtualCenter Server im Speicher des VI-Clients und lässt sich dort auslesen. VMware ACE weist darüber hinaus ein Problem mit Shared Folders auf. Die Links zu den Updates für die jeweilige Version sind im Original-Fehlerbericht des Herstellers zu finden.

                                                                                  Siehe dazu auch:

                                                                                  VMSA-2009-0005 VMware Hosted products, VI Client and patches for ESX and ESXi resolve multiple security issues, Bericht von VMware