Nice job guys, just based on no flash and overall responsiveness this will really make it easier to get weaned off of the c# client.

Agreed. Very snappy!

Hey Guys! Excited to test this out. When running the server-configure.bat on my VC, it creates three files that are different than what you have in the PDF. Also, all three files are zero bytes. When running the batch file, I get this status update:
E:\h5client>server-configure.bat
Generating store.jks file...
The system cannot find the path specified.
The system cannot find the path specified.
The system cannot find the path specified.
I'll keep messing with it tomorrow. Running VC6 on Win2012.

Usually the zero byte files are due to incorrect command prompt permissions.

Can you try by opening an Administrator level command prompt and rerunning the .bat file?

Hi guys

With regards to this error, the script is assuming vCenter Server is installed on the default path. In this case as it was in mine I had to change the below 2 lines to the correct path:

SET KEYTOOL=C:\Program Files\VMware\vCenter Server\jre\bin\keytool.exe

SET VECS_CLI=C:\Program Files\VMware\vCenter Server\vmafdd\vecs-cli.exe

I just changed the drive letter on mine to D and the script ran correctly.

That was it. Thank you Tom. We have all vCenter components installed on the E drive, so replacing c: with e: in the batch file did the trick. Thank you so much!

I'm getting an error trying to import this with 'Import-VApp' through PowerCLI:

Import-VApp : 28/03/2016 20:04:38 Import-VApp The certificate used to sign the OVF package is not valid.
(Untrusted)

Should this be properly signed?

I will check, I don't remember anyone reporting this before.

It's possible it's signed with a VMware certificate that we all have installed in our systems so it's recognized. I will ask around.

Is it blocking you from deploying completely, or are you able to work around it with security settings changes?

Read up on the PowerCLI API reference, and I can use '-Force' to ignore the certificate warnings. Thanks Dennis.

I couldn't get this to work. I followed the instructions but just get asked to put in my password every time it tries to run a command and the command such as mkdir then fails

I switched the shell back to the appliance shell but now I can't SSH back into the vCenter Server, putty just quits on me.

"mkdir not found" usually occurs because the vCenter appliance shell was not set to bash, and was still on appliancesh

Being unable to ssh back into the vCenter appliance is usually because the "chsh" command did not succeed correctly.

Do you still have the terminal output?

Seems every time I change the shell on the vCenter Server I can't login again

login as: root
Welcome to vSphere Web Client Appliance
root@192.168.10.70's password:
Last login: Mon Mar 28 19:18:35 UTC 2016
Last login: Mon Mar 28 19:18:35 2016 from
Identity added: /root/.ssh/id_rsa (/root/.ssh/id_rsa)
localhost:~ # /etc/init.d/vsphere-client configure --start yes --user root --vc 192.168.10.180
Connecting to SSO server, you will be prompted for user's credentials
The authenticity of host '192.168.10.180 (192.168.10.180)' can't be established.
ECDSA key fingerprint is 44:c7:7b:d8:55:a1:00:a9:94:b8:2f:6b:5c:b8:9a:12 [MD5].
Are you sure you want to continue connecting (yes/no)? yes
Password:
Password:
bin/bash: No such file or directory
Creating /etc/vmware/vsphere-client/config directory
Creating /etc/vmware/vsphere-client/vsphere-client directory
Creating /etc/vmware/vsphereFeatures directory
Generating keystore file and property files.
Password:
bin/bash: No such file or directory
Downloading keystore file and property files.
Password:
bin/bash: No such file or directory
mv: cannot stat ‘/etc/vmware/vsphere-client/webclient.properties’: No such file or directory
mv: cannot stat ‘/etc/vmware/vsphere-client/ds.properties’: No such file or directory
mv: cannot stat ‘/etc/vmware/vsphere-client/vsphereFeatures.cfg’: No such file or directory
Password:
bin/bash: No such file or directory
Configuration process was not successful.
vSphere Client Web Server is not configured, please use the '/etc/init.d/vsphere-client configure' to configure:
localhost:~ # Welcome to vSphere Web Client Appliance
mv: cannot stat ‘/etc/vmware/vsphere-client/webclient.properties’: No such file or directory
mv: cannot stat ‘/etc/vmware/vsphere-client/ds.properties’: No such file or directory
mv: cannot stat ‘/etc/vmware/vsphere-client/vsphereFeatures.cfg’: No such file or directory
Password:
bin/bash: No such file or directory
Configuration process was not successful.
vSphere Client Web Server is not configured, please use the '/etc/init.d/vsphere-client configure' to configure:
localhost:~ #
-bash: Welcome: command not found
localhost:~ # root@192.168.10.70's password:
> Last login: Mon Mar 28 19:18:35 UTC 2016
> Last login: Mon Mar 28 19:18:35 2016 from
> Identity added: /root/.ssh/id_rsa (/root/.ssh/id_rsa)
> localhost:~ # /etc/init.d/vsphere-client configure --start yes --user root --vc 192.168.10.180
> Connecting to SSO server, you will be prompted for user's credentials
-bash: root@192.168.10.70s password:
Last login: Mon Mar 28 19:18:35 UTC 2016
Last login: Mon Mar 28 19:18:35 2016 from
Identity added: /root/.ssh/id_rsa (/root/.ssh/id_rsa)
localhost:~ # /etc/init.d/vsphere-client configure --start yes --user root --vc 192.168.10.180
Connecting to SSO server, you will be prompted for users: No such file or directory
localhost:~ # The authenticity of host '192.168.10.180 (192.168.10.180)' can't be established.
> ECDSA key fingerprint is 44:c7:7b:d8:55:a1:00:a9:94:b8:2f:6b:5c:b8:9a:12 [MD5].
> Are you sure you want to continue connecting (yes/no)? yes
> Password:
> Password:
> bin/bash: No such file or directory
> Creating /etc/vmware/vsphere-client/config directory
> Creating /etc/vmware/vsphere-client/vsphere-client directory
> Creating /etc/vmware/vsphereFeatures directory
> Generating keystore file and property files.
> Password:
> bin/bash: No such file or directory
> Downloading keystore file and property files.
> Password:
> bin/bash: No such file or directory
> mv: cannot stat ‘/etc/vmware/vsphere-client/webclient.properties’: No such file or directory
> mv: cannot stat ‘/etc/vmware/vsphere-client/ds.properties’: No such file or directory
> mv: cannot stat ‘/etc/vmware/vsphere-client/vsphereFeatures.cfg’: No such file or directory
> Password:
> bin/bash: No such file or directory
> Configuration process was not successful.
> vSphere Client Web Server is not configured, please use the '/etc/init.d/vsphere-client configure' to configure:
> localhost:~ #
>

Same Issue any update on how to get a round it

Worked through this with Bryan, looks like the OVA download may have gotten messed up. After redownloading and redeploying it looks like it's working.

Yes all working now thanks. Very nice.

On your VC can you run "ls /bin/bash" and see if that file exists? If it's easier you can email me directly at dennislu vmware.com

Hello Dennis. I have the same mkdir error. It seems that bash isn't enabled by default. I have tried this: https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2100508, but still no luck. Have you got any ideas? The output for the ls/bin/bash is
<
No such file or directory
>

Thank you.

When you SSH into the vCenter Server Appliance, what shell do you get? The Instructions PDF has some commands about what the appliancesh looks like, or how to detect what your current default shell is, can you try those?

The default shell is still appliancesh, not the bash, despite I have followed the instruction and this kb https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2100508 to modify the kernel boot options. The output for ls /bin/bash now is:
<
/bin/bash
>