You can use Powershell to get the block size of a Windows NTFS volume:
On newer systems:
Get-CimInstance -ClassName Win32_Volume | Select DriveLetter,Label, BlockSize | FT -AutoSize
On older systems, the Get-CimInstance may not be available, in which case you can use the (deprecated) Get-WmiObject:
Get-WmiObject -Class Win32_Volume | Select DriveLetter,Label, BlockSize | FT -AutoSize
If you need to rename all folders and files to lowercase on a case-sensitive filesystem (e.g. ext4 on linux), you can use the following at the bash prompt:
If rename is available (if you have Perl installed, then it usually is):
find . -depth -exec rename 's/(.*)\/([^\/]*)/$1\/\L$2/' {} \;
If you can't use rename, try this:
for SRC in `find my_root_dir -depth` do DST=`dirname "${SRC}"`/`basename "${SRC}" | tr '[A-Z]' '[a-z]'` if [ "${SRC}" != "${DST}" ] then [ ! -e "${DST}" ] && mv -T "${SRC}" "${DST}" || echo "${SRC} was not renamed" fi done
Attached is Microsoft's latest password guidance document.
With the application of the guidelines in this document, you should be able to get better overal security without compromising too much of the user-friendly experience.
Currently, it is not possible to configure the DNS suffix (search domain) for SSL VPN and IPSEC tunnels through the GUI, but it can be configured using the CLI.
For SSLVPN:
config vpn ssl settings set dns-suffix example.com example.org end
For IPSEC:
config vpn ipsec phase1-interface set domain example.com end
Changes are effective immediately. After configuring the setting, users will be able to resolve names using single names instead of FQDN.
An excellent TechNet-article explained how rules are evaluated in Windows Firewall, specifically in what order and which rules take precedence over others.
If for some reason the deployment of the VMWare vConverter agent fails, you can also copy the installer to the machine you wish to P2V and manually install it.
On the machine VMWare vConverter is installed, navigate to the location where it's installed (by default: C:\Program Files (x86)\VMware\VMware vCenter Converter Standalone), and look for the file VMware-Converter-Agent.exe. Copy over this file over to the target machine and run it to install the agent. Accept the defaults, including the TCP-port (unless your setup requires you to change it). Once finished, a service will have been installed and you will be able to connect to it using vConverter.
Found this article online about how vSphere virtualizes NUMA and how this is relevant to the configuration of vCPUs in your VMs:
https://www.opvizor.com/decoupling-of-cores-per-socket-from-virtual-numa-topology-in-vsphere-6-5
In the event of migrating your old vCenter Server to a new version (or from Windows to the appliance), it may become necessary to first clear out old historical data. Not only will this speed up the migration process considerably, it will also prevent certain issues which may block the migration from completing successfully.
VMWare provided a KB with database scripts which allow you to selectively purge historical data and decreasing the database size: KB 2110031.