How can we improve the clustering platform and management in Windows Server?

← Clustering

Create a Hyper-V Cluster without AD

It's very important create hyper-v cluster without AD dependencies. For example you could use certificates to validate each node (like Hyper-V Replica between two hosts in workgroup)

139 votes
Sign in
(thinking…)
Sign in with: Facebook Google
Forgot password?
Create a password
Signed in as (Sign out)
Close
Close

We’ll send you updates on this idea

Silvio Di Benedetto shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

16 comments

Sign in
(thinking…)
Sign in with: Facebook Google
Forgot password?
Create a password
Signed in as (Sign out)
Close
Close
Submitting...
An error occurred while saving the comment
  • Patrick Gemme commented  ·   ·  Flag as inappropriate

    At the moment I wouldn't need to build one of these, but it does seem silly that it's required. I may want to build test environments or sandbox's without having to also build or use my test AD.

  • Edith commented  ·   ·  Flag as inappropriate

    Hola ! I need a cluster but i don`t have a DC and i don`t want configure a Domain
    It`s porssible use Failover Custer Feature for Windows 2012 R2 with out DC ??

  • Tony Valenti commented  ·   ·  Flag as inappropriate

    @Elden -

    Would you deploy EVERY Hyper-V Cluster this way?
    ---Yes.

    Why?
    ---I hate the cluster service's dependency on AD and computer names. I wish it would just use IP. I also really dislike clusters being "touchable" through AD. I would want System Center to manage the credentials for a "Cluster Admin" user on the Cluster and whenever an operation needs to happen, that user account is what logs into the cluster.

  • Tony Valenti commented  ·   ·  Flag as inappropriate

    I would love to see this implemented!

    We use HyperV for close to 3,000 VMs and I absolutely hate how much "Infrastructure" it takes to set up a cluster. I've always felt as though HyperV clusters were extremely brittle because of everything they rely on: Active Directory, DNS, Cluster Service, etc.

    I would love it if I could create a cluster that was essentially just referenced by the IP addresses in the cluster and nothing else.

  • Elden Christensen [MSFT] commented  ·   ·  Flag as inappropriate

    What are the scenarios you would deploy a cluster which was not domain joined?

    - Would you deploy EVERY Hyper-V Cluster this way?
    - Small deployments?
    - Branch office?
    - DMZ deployment outside firewall
    - Highly secure deployments?
    - Test / Dev?

  • Rafael Bernardes commented  ·   ·  Flag as inappropriate

    Portuguese: Obrigado a todos que estão votando! Vou falar pessoalmente com o PM do projeto sobre isso.

    Rob/Elden, now I think that you have to take a look and consider this feature :)

  • Rogéiro Molina commented  ·   ·  Flag as inappropriate

    I guess very importante, no buy another license to Windows Server for Active Directory!!!! Would reduce the final cost for the customer and it can improve the sales!

  • Aidan Finn commented  ·   ·  Flag as inappropriate

    The request is to create a HYPER-V cluster, not a SQL cluster. Removing AD from the equation would greatly simplify the deployment, configuration and cost of Hyper-V.

  • Elden [MSFT] commented  ·   ·  Flag as inappropriate

    With Win2012 R2 you can create an 'Active Directory detached Cluster', where computer objects are not created for cluster network name resources. This removes the requirement to have domain privileges to create a new network name resource, for example when setting up a new SQL Server instance. However, the nodes still must be joined to a domain.
    As I understand this ask, it is to take it the next step further... to allow creating a Failover Cluster with a set of member servers which are not joined to a domain at all.

  • John Marlin commented  ·   ·  Flag as inappropriate

    @Raj,
    Keep in mind that using the -AdministrativeAccessPoint DNS does not create a computer object for the CNO. Without the CNO, you do not have Kerberos. Kerberos is needed for Live Migrations. So doing this with a Hyper-V Cluster is going to limit you in what you can do.

Clustering: Security

Categories

Feedback and Knowledge Base

(thinking…)