ThinApp TightVNC Server

This post was originally published on this site

Hi all,


I was just wondering if anyone had managed to ThinApp TightVNC server?


I have rolled out a windows 7 version to a virtual desktop and get all of the icons that I need.

VNC viewer comes up fine, and I can even use the viewer from a virtual desktop to connect to my reference VM where TightVNC is installed (installed locally).


When I run VNC server (the thinapp version), it shows the icon in the system tray and also the IP address of the VMware View VDI VM, but when I try to connect to the VM via a thinapped viewer it prompts for the password but then nothing happens, and I eventually get the connection was gracefully shutdown.



The scenario is, we have a wallboard which comes from a desktop pool via a thinclient, and we need multiple users to be able to access the wallboard without killing the session on screen.

I didn’t want to hard install VNC Server on to the desktop image because another pool uses the same image, and I also didnt want to create a separate desktop image (because that means its another desktop I have to keep up to date with patches), so the idea was to thinapp VNC server, run it, and then users could connect to it via the thinapp VNC Viewer (with AD rights applied).


The problem I think we have is that the thinapp version of VNC Server doesnt install the TightVNC Server service in to windows and that might be the issue, despite me being able to telnet to the port that VNC is using (5900)…


Anyone any suggestions?



How to migrate (p2v) VMS (Virtual Memory System)

This post was originally published on this site

Hi Team,


Can anybody tell how to migrate VMS (Virtual Memory System) ? Please do not confuse the term VMS. Please see the below description. Its an old OS used for UNIX. I have a requirement to migrate do P2V / migrate VMS to virtual environment. Not sure which converter support this? Or is it compatible with VMware? I do not know anything about this… Please help??


VMS: VMS was renamed OpenVMS when it was redeveloped for the Alpha processor. (OpenVMS is also the name now used on the VAX computer.) The “Open” suggests the added support for the UNIX-like interfaces of the Portable Operating System Interface (POSIX) standard. Programs written to the POSIX standard, which includes a set of standard C language programming functions, can be ported to any POSIX-supporting computer platform.




How can I uninstall the vCenter Standalone Converter?

This post was originally published on this site

My vCenter Standalone Converter 5.5 installation is corrupted on a Windows Server 2012 R2 server.  Using the typical uninstall procedure through the Control Panel results in a “Could not stop service” message.  This is the message I receive regardless of whether I try to uninstall, repair, or reinstall the application.  Can someone direct me to a list of the various files and registry entries that need to be deleted to effectively remove the application to the point where I can reinstall it again?  Thanks.