Download the file fmw_188.8.131.52.0_wls.jar (Executable Jar File).
I downloaded the file to my D:\downloads folder. Open Adminstrator:Command Prompt and extract the jar file with Java.exe as shown below. Install JDK if you haven’t done so.
c:\Program Files\Java\jdk1.8.0_131\bin>java.exe -jar d:\downloads\fmw_184.108.40.206.0_wls.jar
Follow the 7 steps.
Sql Server Configuration Manager
Sql Server Studio Management – Server Properties – Advanced
Connecting failed using OpenVPN Client Configuration in Asus RT-AC1900P
Wed Apr 26 15:26:37 2017 OpenVPN 2.4.1 x86_64-w64-mingw32 [SSL (OpenSSL)] [LZO] [LZ4] [PKCS11] [AEAD] built on Mar 22 2017
Wed Apr 26 15:26:37 2017 Windows version 6.2 (Windows 8 or greater) 64bit
Wed Apr 26 15:26:37 2017 library versions: OpenSSL 1.0.2k 26 Jan 2017, LZO 2.09
Enter Management Password:
Wed Apr 26 15:26:43 2017 WARNING: –ns-cert-type is DEPRECATED. Use –remote-cert-tls instead.
Wed Apr 26 15:26:44 2017 OpenSSL: error:0906D06C:PEM routines:PEM_read_bio:no start line
Wed Apr 26 15:26:44 2017 OpenSSL: error:140AD009:SSL routines:SSL_CTX_use_certificate_file:PEM lib
Wed Apr 26 15:26:44 2017 Cannot load inline certificate file
Wed Apr 26 15:26:44 2017 Exiting due to fatal error
Check if your client configuration file has keys & certificate value. It should not have this line below.
paste client certificate data here
paste client key data here
In OpenVPN, click Advanced Settings. Next, click Content modification of Keys & Certification
Click Export. You’re done! Now your client configuration file should have the keys and certificate value.
I want to enable Shared VMs but it failed to configure the Workstation Server.
The two services below failed to start, VMware Workstation 11 or 12 Pro on Windows 2008 R2.
- Stop/disable any anti-virus.
- Repair VMware Workstation Pro Setup.
- Restart server.
- All 5 services should be started at this point.
- Apply VMware Workstation update if any.
- Restart server.
- Verify services.
- Data (D:) has data -> Make a full backup!
2. MBR was created (2 volumes on Disk 1). Unallocated volume cannot be extended on healthy volume due to MBR Disk (< 2 TB).
3. Verify your backup!
4. Delete healthy volume.
5. Healthy volume deleted (2 unallocated volumes). Right click on Disk 1 and select Convert to GPT Disk.
6. GPT Disk converted, we now have 1 volume (> 2TB) on Disk 1.
7. Created new simple volume. Last step is restore data to the new volume (Data (D:)).
Add drives hot (server is online). Once physical disk(s) are added, you will see in OpenManage Server Administrator physical disks are at Ready status, not Foreign.
Disk 1 has two volumes (2048 GB NTFS and 743.87 GB Unallocated). First volume can’t be extended (grayed out) because Disk 1 was created with MBR disk.
To extend beyond 2 TB capacity, you need to convert Disk 1 to GPT disk, (GUID Partition Table).
- Make a full backup of Drive-D (Data).
- Delete data (D:) volume.
- Create new volume (GPT Disk).