Recovering GUI in windows Server 2012R2 and .Net Framework feature dependency in windows server 2012/2012 R2

HPE Aruba Mobility Controller Besic Setup

 

Using CLI 

(Aruba) #configure terminal

Enter Configuration commands, one per line. End with CNTL/Z
 
(Aruba) (config) #ip dhcp pool Guest-User
(Aruba) (config-dhcp)#network 10.10.10.0 255.255.255.0
(Aruba) (config-dhcp)#default-router 10.10.10.1
(Aruba) (config-dhcp)#dns-server 10.10.50.1
(Aruba) (config-dhcp)#exit
(Aruba) (config) #service dhcp    //This command enables the DHCP service on the controller
(Aruba) (config) #end
(Aruba) #

(Aruba) #show ip dhcp database

DHCP enabled

# v-20
subnet 192.168.20.0 netmask 255.255.255.0 {
        option domain-name "10.30.156.130";
        option vendor-class-identifier  "ArubaAP";
        option vendor-encapsulated-options  "10.30.156.140";
        option domain-name-servers 10.30.156.140;
        option routers 192.168.20.1;
        range 192.168.20.2 192.168.20.254;
        authoritative;
}
# Guest-User
subnet 10.10.10.0 netmask 255.255.255.0 {
        option vendor-class-identifier  "ArubaAP";
        option vendor-encapsulated-options  "10.30.156.140";
        option domain-name-servers 10.10.50.1;
        option routers 10.10.10.1;
        range 10.10.10.2 10.10.10.254;
        authoritative;

Resolving First boot script error/ FQDN error while deploying VMware vCenter 6.0

Welcome Back ! Its been long time since my last post !!
 
First boot script error or FQDN error is a very commonly happened problem occurred while installing VMware vCenter Server Appliance 6.0

Symptoms

• The vCenter Server Appliance deployment fails to complete
• You see the error:
  Firstboot script execution Error. The supplied System Name vCenter_Server_FQDN is not valid.

 

Cause

This issue occurs if the fully qualified domain name (FQDN) is not resolvable during the vCenter Server Appliance's first boot. It means your supplied System Name is not valid.

Resolution

Step 1 

At 1^st check that your all ESXI host is added in your desired domain.

Follow below process for adding host in domain. 

From Host Node

Login Host >> Configure Management Network >> Custom DNS Suffixes

Type your domain name in Custom DNS Suffixes

 

From DNS Server Manager

Add pointer in Forward Lookup zone of your domain.

 

Step-2

Make sure your ESXI Host using IP address from same network of your Desired Domain and DNS server address is added in Host IP configuration.

Login Host >> Configure Management Network >> IPv4 Configuration

In this case my Domain network is 192.168.8.0/24

 

 

Step-3

All Host and desired vCenter Name, FQDN and IP address should saved in your Computer’s (from which machine you are installing Vcenter) etc.host section. 

Computer must be logged in Administrative mode.

Follow bellow process to go etc.host

Local Disk (C) >> Windows >> System 32 >> drivers >> etc >> host (open this file in note pad)

Step-4

Creating Valid FQDN for the vCenter you want to install.

Add a pointer in your DNS Server Manager using your desired vCenter name which will create the FQDN.

Step-5

While Installing vCenter

      A)      

Be sure that your chosen SSO Domain Name is NOT SAME as your Domain Name.

I used default vsphere.local as SSO Domain Name.

 

 B)

In System Name space use your previously created FQDN for the vCenter.

Hope your problem is now solved :)