vRealize 7.4 Automation Installation Wizard fails with message:
Time offset for <IAAS HOSTNAME> is missing. Please wait for it to be populated.
IaaS host is Windows 2016.
I am having the exact same problem. I have tried numberous ways of trying to fix it, including deleting the VM for the vRA Appliance and re-deploying it. My name resolution is working fine and I even have my windows server (2016) connected to our labs stratum 1 server. I installed ESXi 6.5.0 on a seperate server that is set to UTC time, which apparently you cannot change anymore. I also tried following a very thorough guide from this website I found https://adventuresinclouds.com/2016/01/17/installing-minimal-vra-7-part-1-which-version-for-the-lab/ and still no luck. Not sure what I am missing. Any help would be much appreciated.
Oh, I see. I didn't even think of that. It is always the simplest of things that end up being the source of the problem :smileysilly:
Thanks for your help, I will get the latest version of vRA and try again.
Still no luck,daphnissov because I am just using this as a test environment I couldn't find a trail download for vRA version 7.3.1 or 7.4. So instead I just downgraded my Server to Windows Server 2012 R2 Standard. After setting everything back up again, time offset is still missing and I don't get why. Is it possible that I am missing a component in Windows Server to get this to function, because now it is a fresh install. When I finished installing vCenter, I installed SQL Server 2012 Express as part of the Update Manager install, rather than having a separate SQL Server. I am just doing an embedded deployment just so I can test things out in the lab. While this website has been tremendous help with setting up a bunch of features https://adventuresinclouds.com/ I made a few changes. I don't have Active Directory in place, the installer for vCenter doesn't like domain controllers, and I don't really want to have a whole other server, virtual or physical, just for AD. I just have DNS and also instead of a VCSA I went with the Windows version of vCenter Server. If you have any other ideas, let me know. I am still fairly new to vSphere as a whole, so I am kind of figuring it out as I go.
I think you not having AD is playing a part in this. Even though you have a lab, you really need to build AD. If you don't want to stand up MS AD, you can easily use something like Zentyal Linux in a 1 x 1 VM to give you that plus DNS. In my experience, I've never deployed a vRA stack without this and am not even sure it's supported to do so.
Also, I'd highly *highly* recommend you throw that Windows vCenter away and deploy the appliance version. Not only is it more performant but it's much easier to install and configure and doesn't require a separate SQL server (but vRA IaaS components still do).