Visit the VSKEY Self-serve site. Enter your email address and username. This will send a link to your email where you can set a new password

We are currently running vSphere 6.7, therefore the virtual machine virtual hardware version is up to 15 (vmx-15).

Unfortunately, we do not support nested virtualization including ESXi, VirtualBox, HyperV, etc.

If you have VSS VSKEY credentials, please login to https://vss-portal.eis.utoronto.ca and click on thebutton (lower right corner).

If you do not any VSS VSKEY credentials, send an email to virtual.hosting@utoronto.ca and we will get back to you as soon as possible.

Self-Service Portal (https://vss-portal.eis.utoronto.ca) is only accessible using VSS VPN

To know further about changing your VM config, please visit Change CPU, Memory, Network, HDD specs after a VM is created.

Windows doesn't include the VMware Parvirtual SCSI driver in its inventory, thus we have to provide it during the installation. This could be done by requesting VSS the following:

• Mount the PVSCSI driver in the VM's floppy drive. 

• Load driver from floppy in the Windows Installer Wizard.

Once the driver is fully loaded, you will be able to start Windows installation as any other kind of HDD controller.

You can use either the vSphere Web Client or the vSphere Windows client to do so. Detailed steps can be found in this How-To article: Verify VMware Tools version.

This issue occurs when the Linux iputils package causes a delay in the boot process and to resolve this issue, see the RedHat Advisory RHBA-2013:1290 and install the proper patch. However, if the virtual machine remains stuck in the boot up process, please contact the VSS team to apply the workaround mentioned in the VMware KB Article 2048572

In order to present hot added memory right away, we need to set up the memory online. Refer to the VMware KB article Hot adding memory in Linux (1012764)

Virtual machine snapshots can be created via the VSS Portal or VSS Command Line interface. For more information, please refer to the following How-To article Request Virtual Machine Snapshot.

We have a public repository with hundreds of ISO images and any can be loaded as described in the following How-To article Load an ISO image in a Virtual Machine. Also, you can mount your own ISO to a virtual machine following this How-To article Upload an ISO image to VSS.

Yes. According to https://kb.vmware.com/s/article/59222 you should select Microsoft Windows Server 2016 (64bit).

Yes. When provisioning a new Virtual Machine or updating an existing Virtual Machine network adapter, select VSS-PUBLIC in the network tab. This network is DHCP based and you will receive a the IP address iallocated for your virtual machine once provisioned in the email confirmation.

Taking into account that we provide static IP addresses, you can use that IP address to register whatever hostname is needed. Since we only provide the IP address, you have to register the hostname by any of the following methods:

• If a hostname in ".utoronto.ca" is required, then you should contact EIS Network Engineering or use UT campus network admin tools available from https://netadmin.utoronto.ca/

• If a hostname outside of ".utoronto.ca" is required, then you have to contact a DNS registrar of your choice.

Please let us know what the hostname will be so that we can complete the PTR registration.

It is our best practice to install VMware Tools on each provisioned VM. Please, choose the right process according to your VM's platform listed in the following documents: Installing VMware Tools or Upgrading VMware Tools

Because operating system vendors do not provide built-in drivers for VMXNET3/VMXNET2 card, you must install VMware Tools to have a driver for the network adapter available. This is the case of Windows, which requires VMware Tools installed to load the VMXNET driver. Refer to the VMware KB article Installing VMware Tools in a Windows virtual machine (1018377) and install VMware tools on your VM, then the VM network adapter will be usable

First, remove the current installation of VMware Tools. Then install open-vm-tools, either by using a package manager or by downloading the appropriate package for your distribution. For more details, please consult the How-To article: Move from VMware Tools to Open VM Tools (open-vm-tools)

Even though the customization specification is applied, the end state of the task is failed according to /var/log/vmware-imc/toolsDeployPkg.log is FAILED. Based on the following KB: 

1.  Open the tmp.conf under /usr/lib/tmpfiles.d/tmp.conf file. Go to the line 11 and add the prefix # . For example: 

#D /tmp 1777 root root -

2. open the /lib/systemd/system/open-vm-tools.service file. Add the following line under [Unit]

After=dbus.service

3. Reload Unit:

systemctl daemon-reload