Monthly Archives: January 2017

SCVMM Logical Network Settings

Hi Experts

Trying to learn Hyper-V networking with Server 2016 and came across some important options available on SCVMM Logical Network Settings options.

I have 5 NICs and I would like to use according to below settings.

Management - 1 NIC


Public Communication (External) - 2 NIC (Team)


While creating Logical network I’m asked to select below options 

(1) One Connected Network with Two check boxes (A) Allow new VM networks created on this logical network to use network virtualization. (B) Create a VM network with the same name to allow virtual Machine to access this logical network directly. 

(2) VLAN based independent networks

(3) Private VLAN networks.

My concern/s

What are the use of these all three settings and how my Host network setup will fit on these three settings and their sub-settings? In another words, what setting will be suitable if I want to configure management network in my Hyper-V, Hosts? It One
connected network then what are the significant of two check boxes available under this option.


Read full post . . . .

Is Your Remote Access Secured with Multi-Factor Authentication?

63% of security breaches involve weak or stolen credentials, which highlights why authentication is often the weak link in the security defences of organizations. For hackers, stealing or guessing an employee’s credentials means they can “legitimately” enter company networks and, …


Related Stories

Continue reading..

Is Your Remote Access Secured with Multi-Factor Authentication?

63% of security breaches involve weak or stolen credentials, which highlights why authentication is often the weak link in the security defences of organizations. For hackers, stealing or guessing an employee’s credentials means they can “legitimately” enter company networks and, …


Related Stories

Continue reading..

Hyper-V replica and host at the same time

I’m trying to understand if Windows 2012 R2 Hyper-V server can run a normal workload at the same time as accepting replication from a remote Hyper-V server that’s also configured as host for other VMs as well as replication server.

Basically two locations with Hyper-V server or cluster replication between each other.

Is that technically possible to implement? 

For some reason, I can’t find anything that mentions this setup.

Thank you.

Memento Mori

Read full post . . . .

Updated Version of the Deployment Guide for Hadoop on VMware vSphere

The newDeployment Guide for Virtualizing Hadoop on VMware vSphere describes the technical choices for running Hadoop and Spark-based applications in virtual machines on vSphere. Innovative technologies and design approaches are appearing very regularly in the big data market; the pace of innovation has not slowed down for sure!

A prime example of this innovation is the rapid growth in Spark adoption for serious enterprise work over the past year or so, overtaking MapReduce as the dominant way of building big data applications. Spark holds out the promise of faster application execution times and easier APIs to use to build your application. A lot of innovation work is now going into optimizing the streaming of large quantities of data into Spark, with an eye to the large data feedsthat will appear from connected cars and other devices in the near future. This new version of the VMware Deployment Guide for Hadoop on vSphere brings the informationup to date with developments in the Spark and YARN (&#rsquo;Yet Another Resource Negotiator&#rdquo;) areas.

The YARNtechnology is the general name for the updated job scheduling and resource management functions that have now become mainstream in Hadoop deployments. The older MapReduce-centric style, once the central resource management schedulerin Hadoop, is now relegated to just another programming framework. MapReduceis stillused for Extract-Transform-Load (ETL) jobs, running in batch mode on a common resource management and schedulingplatform (YARN) - butnow,to a large extent,MapReduceis no longer the dominant paradigm for building applications. Spark is seen as muchmore suited to interactive queries and applications. Spark also runs as an example of another application framework on YARN, and that combination is popular in enterprises today - and so it is the focus of much of our testing currently, as you will see. Spark runs in standalone mode outside of the YARN resource manager context too, but that option is out of scope for the current Deployment Guide, as we see that less often within enterprises today. Of course, that may changein the future.

The previous (2013) version of the Hadoop Deployment guide for vSphere described the Hadoop 1.0 concepts (TaskTracker, JobTracker, etc.,) as they are mapped into virtual machines. That earlier version also contained a wide set of technical choices for the core architecture decisions you need to make. In the new version, the concepts in modern big data such as Spark and YARN are described in a virtualization context.

In the new version, we brought the main design approaches down to two or three (for example choosing DAS or NAS in the storage area) and we extracted the more complicated designs and tool discussions from it, so as to make it more readable and more focused on getting you started. The ideas described here will scale up to hundreds of nodes if you so choose, so they can be used in the large scale too, if you are going that way. That is shown in the medium-size and large scale example deployments that are given in the guide.

You can think of this blog article as a quick shortcut to information in the Deployment Guide.

The main choices to be made at an early stage in considering the deployment Hadoop on vSphere are given below.

These discussion points (apart from the VM sizing and placement ones) are not unique to virtualization and they apply equally in native systems too:

  1. Having identified how much data our new systems will manage, an early question is what type of storage to use. This question can be answered in several ways. An important choice is what type of storage to use. The Deployment Guide explores the use of Direct-Attached Storage (DAS) or an external form of storage for HDFS or a combination;
  2. Whether to use an external storage mechanism (e.g. Isilon NAS) that removes the management of the HDFS data from the now &#rsquo;compute-only&#rdquo; nodes or virtual machines
  3. What Hadoop software/services to place into different types of virtual machines
  4. How to size and map the correct number of virtual machines onto the right number of host vSphere servers.
  5. How to configure your networking so that the load that Hadoop occasionally places on it can be handled well.
  6. How to handle and recover from failures and assure availability of your Hadoop clusters.


The set of questions related to data storage come down toa core decision between dispersing your data out across multiple servers or retaining it on one central device. There are advantages to each of these.

The dispersed storage model (Option 1 above) allows you to use commodity servers and storage devices, but it means you have to manage it all using your own tools. If a drive or storage device fails in this scheme, then it is the system administrator’s task to find it,fix it and restore it into the cluster. The centralized model ensures that all of your data is protected in one place – and it may cut down on your overall storage needs. This reduction is due to avoiding the replication factor that applies with DAS-based HDFS.It can also make the data easier to manage from an ingestion and multi-protocol point of view. The Deployment Guide shows that both of these models will work fine with vSphere, using somewhat different architectures.

One other variant in storage is to use All-Flash storage on the servers in a similar fashion to DAS. This approach allows us to consider using Virtual SAN for hosting the entire Hadoop cluster, where earlier hybrid storage lent itself better to hosting the Hadoop Master nodes on the Virtual SAN-controlled storage. This All-Flash design for Hadoop on vSphere with VSAN is documented in a separate white paper from Intel and VMware.


Virtual Machine Placement

When taking your decisions about the placement of virtual machine onto servers, users have a distinct advantage in vSphere deployments. We don&#rsquo;t typically know about the server hardware configuration and the storage setup that our virtual machines will be deployed on, in many public clouds. That anonymity is where the flexibility of the public cloud comes from. Correct VM placement onto host servers and storage is very important for Hadoop/Spark however, as VM sizing and subsequent placement can have a profound influence over your application&#rsquo;s performance. That phenomenon is shown in the varied performance work that VMware has carried out on virtualized Hadoop – most recently in the testing of Spark and Machine Learning workloads on vSphere in particular. An example of the results from that work is givenhere

Other topics that are discussed in the Hadoop Deployment Guide are: system availability, networking, and big data best practices. There is also a set of example deployments at the small, medium and large-sized levels for Hadoop clusters. These are all in use either at VMware or at other organizations. You can start out with a small Hadoop cluster on vSphere and expand it upwards over time into the hundreds of servers, if needed.


There is a significant set of technical reference material also contained in the References section of the Hadoop on vSphere Deployment Guide that helps you delve into the deeper details on any of the topics covered in the guide. You can take one of the models described in the main text of the guide, or in the references section as your starting point for deployment and follow the guidelines from there. Using your Hadoop vendor’s deployment tool is recommended for your cluster, whether it be your first one or one among many that you deploy. We find that users want more than one version of their Hadoop distribution running at one time (and sometimes want multiple distributions as well). Virtualization is the way to go to achieve that more easily, with separate sets of virtual machines supporting the different versions.

We hope you enjoy the new Hadoop Deployment Guide material! For more information, you can always go to the main Big Data page.

The post Updated Version of the Deployment Guide for Hadoop on VMware vSphere appeared first on VMware vSphere Blog.

Read more..

NSX Growth and Success in 2016

Last week VMware hosted its Q4 2016 earnings call and shared financial results. VMware CEO Pat Gelsinger and the executive team have frequently highlighted VMware NSX growth and success on these calls. For Q4, NSX license bookings grew over 50 percent year-over-year. Annualizing our Q4 total bookings for NSX, it is now at a $1B run rate. With one month into 2017, we&#rsquo;d like to share more on NSX customer success in 2016.

Customer Success


Exiting 2016, we shared our latest customer count at more than 2,400, which is almost double the customer count from last year. In Q4 we also had the largest NSX-only deal, more than $10M. For every customer I meet with or hear about from my team, I am continued to be impressed how they choose to go about using NSX. We love to share these success stories, whether we&#rsquo;re talking about all the customers we had speaking at VMworld last year, or the many videos and case studies the team publishes regularly. These stories go into details on the significant NSX wins across multiple verticals and every major geography.

Customer Deployments & Expansion

Success for our team is when customers expand their use of NSX from one initial project to other key areas of their business. Commonly we hear customers start with NSX micro-segmentation to setup a robust security posture at one site, and then expand to a disaster recovery site to keep their applications in compliance. As the organization grows or acquires more sites, these capabilities of security and application continuity from NSX get deployed.

Another common expansion scenario also happens when NSX purchases occur initially with VMware products like VMware Airwatch, VMware Horizon 7, VMware Integrated OpenStack or VMware Realize Automation. NSX capabilities are not only fine tuned to support those solutions, but also provide the customer the benefits of network virtualization to support their overall SDDC journey.

These customers successes are supported by the more than 7,000 certified professionals that have achieved an NSX certification to date.

Customer Use Cases

We see nine use cases driving NSX adoption under three lead projects:


NSX embeds security functions right into the hypervisor. It delivers micro-segmentation and granular security to the individual workload, enabling a fundamentally more secure data center. Security policies travel with the workloads, independent of where workloads are in the network topology.

Application Continuity

NSX abstracts networking from the underlying hardware and attaches networking and security policies to their associated workloads. Applications and data can reside and be accessible anywhere. Move workloads from one data center to another, or deploy them into a hybrid cloud environment.


NSX lets you treat your physical network as a pool of transport capacity, with network and security services attached to workloads using a policy-driven approach. This automates networking operations and eliminates bottlenecks associated with hardware-based networks.

Follow this blog to hear more about Security, Automation and Application Continuity with VMware NSX throughout 2017.

Want to learn more about more about VMware NSX? Join an upcoming February Webcast Series!

  • Micro-segmentation Planning – What You Need to Know Feb 9
  • Networking and Security for Virtual Desktops & Mobile Devices Feb 16
  • NSX for Multi-site Deployments and Disaster Recovery Feb 23

The post NSX Growth and Success in 2016 appeared first on The Network Virtualization Blog.

Read more..

ROOMn 2017 : VMware partenaire incontournable d’une transformation numérique réussie

ROOMn invite tous les décideurs informatiques et chefs d&#rsquo;entreprise à participer à la 5ème édition de sa conférence sur l&#rsquo;activité mobile et numérique qui se tiendra à Monaco. Avec plus de 800 participants, 1 500 entretiens personnalisés et plus de 60 conférences et ateliers, ROOMn est l&#rsquo;une des manifestations sur l&#rsquo;activité numérique et mobile les plus importantes en Europe. Réunissant de nombreux dirigeants parmi les plus en vue du secteur, elle organise 3 jours de réflexions pointues sur la transformation numérique.

Du 7 au 9 mars, la conférence ROOMn sera l&#rsquo;occasion pour VMware AirWatch d&#rsquo;animer une session plénière et de présenter notre accompagnement dans la transformation digitale qui s&#rsquo;accélère depuis 2 ans.

Avec un Workspace utilisateurs encore plus présents dans les projets de nos clients en 2017, la simplicité d&#rsquo;usage et la sécurité d&#rsquo;entreprise sont au cœur des solutions VMware Airwatch. Elles facilitent l&#rsquo;accès aux applications d&#rsquo;entreprise, sécurisent les données mobiles et renforcent la productivité.

Que vous ayez la chance de participer à l&#rsquo;événement ou souhaitiez simplement vous tenir informé, connectez-vous à notre compte Twitter pour suivre les en direct a manifestation.

ROOMn 2017 a comme thème principal les perspectives de déploiement d&#rsquo;une stratégie numérique dans l&#rsquo;entreprise grâce à la technologie mobile. La présence de VMware est importante avec au programme :

Mercredi 8 mars
9h30 atelier : « Optimiser la convergence desktop mobile avec Windows 10 »

Pour optimiser Windows 10, il est indispensable d&#rsquo;avoir une plateforme de gestion associée à une console unique pour tous les types de terminaux : ordinateurs, smartphone, tablettes, portables … qui aide à une rationalisation du déploiement des terminaux, une expérience applicative unifiée, la protection des données, la gestion des mises à jour et d&#rsquo;autres fonctionnalités de sécurité avancées.

Jeudi 9 mars
9 h Session plénière : « Comment le digital workspace transforme-t-il les métiers ? »

Karim Djamai et Carla Sarkis expliqueront comment l&#rsquo;espace de travail numérique peut garantir l&#rsquo;accès à n&#rsquo;importe quelle application en tout lieu et à tout moment, quel que soit le terminal ou la taille de votre entreprise. Nous verrons à travers un témoignage client dans le secteur de l&#rsquo;énergie, l&#rsquo;apport du workspace dans la transformation de l&#rsquo;ensemble des métiers de l&#rsquo;entreprise.

10h45 atelier : « Comment contrôler en temps réel la sécurité des terminaux et du SI ? »

Malgré la multiplication des points d&#rsquo;accès, il est possible, en 15 secondes, avec les solutions novatrices AirWatch de protéger tous les terminaux tout en offrant une expérience utilisateurs simple et unique quelques soit le terminal.

Découvrez comment Vmware AirWatch facilite l&#rsquo;accès aux applications d&#rsquo;entreprise, sécurise les données mobiles et renforce la productivité mobile en nous suivant sur Twitter et en vous tenant informé de nos dernières mises à jour en direct.

Nous sommes impatients de partager avec vous l&#rsquo;ensemble de nos réflexions sur la transformation numérique et mobile lors de ROOMn 2017 ! Pour prendre part aux débats, suivez-nous sur Twitter et donnez votre avis sur #ROOMn2017.

Read more..

Network properties and shaes not working on Windows 2008 R2 Hyper-V virtual server

I’m running Windows 2008 R2 as a Hyper-V host. 
I have 5 VMs running on this host, all Win 2800 R2. On one of the hosts, I’m no longer able to modify the network configuration since patching this weekend. 
When I go into Network -> Properties it shows the server is on a domain and the access type is Internet, but the Connections field is blank, where on all of my other VMs it says “Local Area Connection” and it’s a hyper link to modify the network adapter
properties.  See below:

Also, from this server I cannot access shares on other file servers and the shares on this server cannot be reached. I can sign into the computer from both the Hyper-V host and from a remote console and it does reply to a ping command
by the VM server’s name.

I have rebooted the servers, I have removed the virtual network card and reapplied but nothing has helped.

The patches that were applied were KB3212642, KB3212646, KB3205402 (2 January security and quality rollups and 1 December .NET rollup packages) and KB3045316, the SQL 2008 SP3. 
These same patches were applied to about 20 other servers, none had issues.

Any ideas or suggestions?

Read full post . . . .

Wednesday’s (Feb. 8th) Wisdom Series Focuses on vRealize CMP

Register now and join us on February 8th at 8am PST for this technical session: Using Log Insight and vRNI with NSX.

This month’s webinar will focus on exploring the fundamental capabilities of vRealize Cloud Management Platform (CMP) and how the components work together to solve customer business and IT issues. You’ll also learn how Log Insight and Network Insight work together to help you plan, operationalize, and manage NSX.

The post Wednesday’s (Feb. 8th) Wisdom Series Focuses on vRealize CMP appeared first on Partner News.

Read more..

2nd Exam Option Available for VCP6-NV Certification

I am pleased to release the latest exam forVCP6-NV based on VMware NSX v6.2. This new exam (#2V0-642) gives you a second option for earning your VMware Certified Professional 6 - Network Virtualization certification.

Thank you to all of the exam developers, item writers, and beta exam tester who helped create this exam. If you took the beta exam, your results should be reflected in your transcript by the end of the month.

With the release of this new exam, we are also announcing the retirement of the older VCP6-NV exam (#2V0-641) on April 30,2017. If you have been preparing for that version of the exam please make sure you schedule your test date prior to then.

The post 2nd Exam Option Available for VCP6-NV Certification appeared first on VMware Education & Certification Blog.

Read more..

Go Que Newsroom Categories

Fatal error: Allowed memory size of 67108864 bytes exhausted (tried to allocate 36 bytes) in /home/content/36/8658336/html/goquecom/wp-includes/taxonomy.php on line 3361