Windows Profiles

[Sarah M]

I want to make modifications to the default profile (desktop ,start
programs,
settings, etc..)once and not for every user. I then want to Ghost the image
so all users have the same settings. I don't have zenworks or other similar
utilities. The problem is that when I make the setting changes they are not
retained when the user logs in for the first time. (they get the initial
defaults)

Is there a way to setup the computer up so that any local user logginng in
gets the same profile?

If I used a static user the Novell client wants me to log in twice if there
is a
different local user than the Netware user.

also, I remember in NT4 you could copy the profile. There is no DC, can you
copy a profile without a DC?

Thanks for any advice.

 

[Keith V. Klenke]

one way of doing it is setup the administrator account to be exactly how you
want it to be, then create an additional administrator level user, login as
that user, copy the ntuser.dat from under administrator & replace the
default user's ntuser.dat. Remove 2nd administrator account. Now anyone new
who logs in will be configured the way you configured administrator.

btw, make sure you move a quicklaunch folder under defaultuser where it goes
in other profiles, otherwise it wont create one.

You could also just use zenworks policies to setup manditory look & feel.

For your double login issue use there is a very easy solution, which is yes,
you DO have zenworks -

zenworks for desktops 2.0 starter pack - it is completely legally
free, & is what many of us use, even in a xppro environment

using zenworks for desktops (even 2.0 startpack for free out on the
internet - search for zspenu.exe, about 23mb, keep in mind 4.x is the
current version out & 2.0 is eol, so there is no "new" support for it,
however for xp/2k dlu it will work fine) "DLU" that will keep local
passwords synced & managed for nds for the workstations, and no more having
to create them manually.

In order for it to work, you have to make sure the DLU user policy is setup
&
associated correctly, & you have to make sure the latest nwclient is
installed with the "workstation manager" component configured to the correct
tree name. The easiest way to do this for your entire organization would be
through ACU (automatic client update).
http://www.appdeploy.com/packages/detail.asp?id=108