https://thesistips.wordpress.com/2012/03/25/how-to-write-your-introduction-abstract-and-summary/
- M522H-XYL8Q-W8X80-0X9RH-8E8H5
- Resolved with https://kb.vmware.com/s/article/2146361 - steps 1-2 + restart.
- Try each step individually to see if using only one step, group policy or Hyper-V, works.
root:54321qwert
http://192.168.254.136/
http://[fe80::20c:29ff:fe6b:7530]/ (STATIC)
I should probably use the static IPv6 address to avoid issues with VMware DHCP changing the IP if I restart the VM.
https://[fe80::20c:29ff:fe6b:7530]/ui/
- From
task1_4_vsphereclientinstall_4.PNG
- "All vSphere features introduced in vSphere 5.5 and beyond are available only through the vSphere Web Client. The traditional vSphere Client will continue to operate, supporting the same feature set as vSphere 5.0."
I could detail how to improve security by modifying the firewall rules to only allows vSphere Web Client connections from specific IPs.
Uploading via the vSphere Web Client doesn't work - frozen at 0%
- In the Web Client, enable SSH via
Host > Actions > Services > Enable Secure Shell (SSH)
- Download PuTTY/pscp.exe from https://www.chiark.greenend.org.uk/~sgtatham/putty/latest.html
- In the Web Client, find the path to
datastore1
by going toStorage > datastore1
and viewing theLocation
. - Use pscp.exe to push, over SSH, the ISO to the
isos
folder indatastore1
.
From the isos directory on workstation host:
C:\tools\pscp.exe -6 .\14393.0.161119-1705.RS1_REFRESH_SERVER_EVAL_X64FRE_EN-US.ISO root@[fe80::20c:29ff:fe6b:7530]:/vmfs/volumes/5af1d3e9-abd56f67-0cdf-000c296b7530/isos
- Attempting to connect to a console via the Web Client using IPv6 fails - see
task2_6_winserver2016_11_dc_issue1_2.PNG
See https://communities.vmware.com/thread/542726 for further information. - I could try upgrading the ESXi Host Client or I could just use the IPv4 address to access the consoles...
I think the latter option is easier.
https://192.168.254.136/ui/#/console/1
- Alternatively, I could just use the vSphere Client (desktop) for this part.
54321qwert*
I had to add a symbolic character to meet the complexity requirements...
I can't ping 8.8.8.8
as there is "No route to host". I think this is probably because I added the NAT network adaptor in VMware after installing ESXi.
- Can see network information for ESXi using commands at https://communities.vmware.com/thread/187557
- I need to find a way to get ESXi to pick up and configure the NAT.
- See screenshots task2_8*
- https://blogs.technet.microsoft.com/canitpro/2017/02/22/step-by-step-setting-up-active-directory-in-windows-server-2016/
- https://ittutorials.net/microsoft/windows-server-2016/setting-up-active-directory-ad-in-windows-server-2016/
54321qwert*
Done: use Domain Join when installing, create a local Client
account from which to change the DNS to point towards the DC.
-
Write up Task 3 and Task 4
-
Crop screenshots
-
Rescale screenshots overall
-
Fill out all todos
-
Purge serial numbers from repo before publicising:
- Remove from notes.md
- Remove
task1_1_downloadvsphere.PNG