asked on

TightVNC, ok to install on master workstation image?

Hello,

I am creating a master workstation image, with all our standard workstation software. The idea is to make copies of of the images (sysprep them) and then join each one to the domain, etc. My question is about installing TightVNC on the master image or not. When it is installed, the master image will of course have a temporary windows name and IP address and when a copy is made, the windows name/IP will gets changed to its production/final values.

So with all those changes and sysprep (SID, etc) being used; should TightVNC be installed on the master image or should it be installed clean on each workstation after it is joined to the domain?

Thanks!

David Johnson, CD

Doesn't matter.

For the sake of maintenance of images it does matter.. only use thin images.. install the applications separately this way if an application gets updated all you have to do is update the source file and not every image that might have that application baked into it

johnhiro007

ASKER

I guess my concern is deeper than if it can work, but does anyone know of VNC having any kind of special unique ID keys created when it is installed, some kind of unique identifier? Just like with Windows and the need to reset the SID with Sysprep, does VNC have a similar need security wise?

Or is it known that VNC security/identification is very simple; just a matter of changing the workstations host name and IP, and therefore having it installed into the base image certainly does not matter?

Thanks!

johnhiro007

ASKER

I guess I'm also looking for anyone knowing of any 'best practices' or official documentation from VNC on the subject either way...

Thanks!

johnhiro007

ASKER

Hello,

Could I get more details in addition to "Doesn't matter"? Any official documentation or real world use of installing TightVNC on the base image?

Thanks.

SOLUTION

Davis McCarn

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

SOLUTION

vivigatt

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

johnhiro007

ASKER

Hello,

Hi 'vivigatt', to clarify; the TightVNC install on the workstations is the 'server' and not 'client'/'viewer'. It is used so we can remotely control each workstation. When you say 'client' do you mean that you can remotely control that workstation (or can that workstation only control other VNC servers/hosts?).

Thanks!

SOLUTION

Davis McCarn

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

ASKER CERTIFIED SOLUTION

Steve

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial