Deploying 'New' desktop evertime user logs in

  • Thread starter Thread starter Fee05
  • Start date Start date
F

Fee05

Here is my question. I have a bunch of dummy systems that are
currently DOS based and I am happy with. However the product they run
is now windows based. I want to be able to reset the desktop to a
standard 'ghost' for lack of a better word.

I.E.
I build the system to my specs and deliver, no matter what changes the
user makes during the day (desktop colors, background, etc.) I want the
system to reset to my original when they log in the next day. Thus
negating all changes the user was able to make.

I do not want to load a fortress(tm) type product that stops users from
doing anything, as they get in the way of productivity. I would rather
the desktop reloads to standard everytime time they log in, thus making
it the company standard and making the users bored of changing things
everyday.


Does the Symantec ghost product do this, or is there another (better)
choice for this.

Also I am not running a windows domain so remote user profiles is not
an option

thanks
 
Use the Guest account. It does not save the user profile, and cannot make
system changes.
 
Here is my question. I have a bunch of dummy systems that are
currently DOS based and I am happy with. However the product
they run is now windows based. I want to be able to reset the
desktop to a standard 'ghost' for lack of a better word.
I.E.
I build the system to my specs and deliver, no matter what changes the
user makes during the day (desktop colors, background, etc.) I want the
system to reset to my original when they log in the next day. Thus
negating all changes the user was able to make.
I do not want to load a fortress(tm) type product that stops users from
doing anything, as they get in the way of productivity. I would rather
the desktop reloads to standard everytime time they log in, thus making
it the company standard and making the users bored of changing things
everyday.
Does the Symantec ghost product do this,

Yes, ghost corporate does.
or is there another (better) choice for this.

Depends on how you define better.

Ghost corporate isnt exactly the easiest to use app around
and the documentation does leave a lot to be desired.
 
Fee05 said:
Here is my question. I have a bunch of dummy systems that are
currently DOS based and I am happy with. However the product they run
is now windows based. I want to be able to reset the desktop to a
standard 'ghost' for lack of a better word.

I.E.
I build the system to my specs and deliver, no matter what changes the
user makes during the day (desktop colors, background, etc.) I want the
system to reset to my original when they log in the next day. Thus
negating all changes the user was able to make.

I do not want to load a fortress(tm) type product that stops users from
doing anything, as they get in the way of productivity. I would rather
the desktop reloads to standard everytime time they log in, thus making
it the company standard and making the users bored of changing things
everyday.


Does the Symantec ghost product do this, or is there another (better)
choice for this.

Also I am not running a windows domain so remote user profiles is not
an option

The quick answer is that ghost will restore the desktop to its original
configuration. But it will restore everything else on the machine,
including all of the data, to the original configuration as well. Seems to
me like killing an ant with an atom bomb, and the time required is not
insignificant.

How large an installation is this? If it of any size then you are going to
need to either use multiple servers or have a standard image that you
multicast using the enterprise version of Ghost, but that brings its own
problems with activation, drivers, and the like.

If your users are running any NT derivative then the easy way to do what you
want is to simply configure a user account on each machine that does not
have the privileges necessary to change the desktop and force your users to
use that account by putting a password on the administrator account. That
is not going to "get in the way of productivity" any more than resetting
the desktop every night will. If the users _need_ to customize their
desktops in order to be productive then making them redo it every morning
is not a good use of their time.

What is the objection to the users customizing their desktops, anyway?
 
J. Clarke said:
How large an installation is this? If it of any size then you are going to
need to either use multiple servers or have a standard image that you
multicast using the enterprise version of Ghost, but that brings its own
problems with activation, drivers, and the like.

installation size is ~5-8 users at 5 remote sites
If your users are running any NT derivative then the easy way to do what you
want is to simply configure a user account on each machine that does not
have the privileges necessary to change the desktop and force your users to
use that account by putting a password on the administrator account. That
is not going to "get in the way of productivity" any more than resetting
the desktop every night will. If the users _need_ to customize their
desktops in order to be productive then making them redo it every morning
is not a good use of their time.

Thought about a limited user account, but the idea of blowing down a
complete 'clean' system is the end result we are looking for.
Althought the time frame is still up in the air (daily, weekly, etc).
Problem is that with inexperienced users (which these are) the daily
problems at the remote sites compound almost daily, and the ability to
get the user's call and just remotly reset the system to the corporate
standard is the end result.
What is the objection to the users customizing their desktops,
anyway?

The systems are not person specific they are location specific, so
keeping them all looking the same when a user steps up goes a long way
towards ease of use for the user. If the icon they need to run the
program is always in the same spot then they call me less to say they
can't find it. Ease of use is the best answer there
 
Fee05 said:
installation size is ~5-8 users at 5 remote sites

The remote part makes Ghost problematical unless you're imaging from a local
drive to a local drive. And if the user is running with administrator
privilege then he can blow away your local image.
Thought about a limited user account, but the idea of blowing down a
complete 'clean' system is the end result we are looking for.
Althought the time frame is still up in the air (daily, weekly, etc).
Problem is that with inexperienced users (which these are) the daily
problems at the remote sites compound almost daily, and the ability to
get the user's call and just remotly reset the system to the corporate
standard is the end result.

They're at remote sites? How big is their disk? How much bandwidth do you
have? If you're "blowing down a complete clean system" using Ghost then
you're moving at least several gigabytes of data to each machine.
Alternatively you could store the image locally but then you need to limit
the user's privilege at least to the extent that he can't wipe off Ghost or
erase the image.
anyway?

The systems are not person specific they are location specific, so
keeping them all looking the same when a user steps up goes a long way
towards ease of use for the user. If the icon they need to run the
program is always in the same spot then they call me less to say they
can't find it. Ease of use is the best answer there

Then everything the user does not need to change should be locked down.

Have you considered using vmware or Virtual PC to run the user in a virtual
machine with the physical machine locked down so that all the user can do
is start the virtual machine? Those are _very_ easy to blow away and
replace, it's just a matter of copying a file.
 
Back
Top