Feb 01, 2016 Thomas Ehler Uncategorized 1
Warning:
Running a Domain Controller in VMware setup the wrong way, can damage your existing Domain!
Please take care to setup the server VM as NAT’ed, according to this post.
First, In VMware, open VM-ware “Virtual Network Editor” to locate the predefined NAT network
Then open “NAT Settings” to see IP-Range and Default Gateway – Make notes!
I strongly suggest :
# Disable Indexing on all drives (makes a racket of noice on rotating disks!)
gwmi Win32_Volume -Filter “IndexingEnabled=$true” | swmi -Arguments @{IndexingEnabled=$false}
# Use small memory dump at system failure
# 0=None, 1=Complete, 2=Kernel, 3=Small, 7=Automaticg
wmi Win32_OSRecoveryConfiguration -EnableAllPrivileges | swmi -Arguments @{DebugInfoType=3}
# Change setting to: Do not automatically restart at system failure
gwmi Win32_OSRecoveryConfiguration -EnableAllPrivileges | swmi -Arguments @{AutoReboot=$false}
See more settings at:
http://johansenreidar.blogspot.dk/2013/06/windows-server-2012-vm-template-tuning.html
Restart the Server.
Jun 11, 2020 0
May 29, 2019 0
Apr 09, 2019 0
Aug 09, 2018 0
Jun 11, 2020 0
May 29, 2019 0
Apr 09, 2019 0
Aug 09, 2018 0
One thought on “Post 2. VMware setup with 2012 Domain controller”