profile slow loading

  • Thread starter Thread starter jan muller
  • Start date Start date
J

jan muller

Dear All,
I have a win2000 server running Active Directory with
a 15 user network and they are all using roaming
profiles. There are 4 users on Win2000 Pro clients, 5
users on WinXP Home, and another few on WinXP Pro. I have
just rebuilt the win2000 server and all the roaming
profile users login times have increased dramatically,
some over 5 minutes, and the users on the old win2000 Pro
clients can easily be 15 or 20 minutes. Any solutions?

Or, as the users don't really use roaming how do I
cleanly i.e. without loosing their setting and documents,
stop them loading the profiles from the server.

Thanks. Jan.
 
Not sure if they cache locally. I'm trying to learn
fast!!! How can I check?

This is just one dc, and everybody can see everybody, and
there are no remote sites. Just one small office on one
site.
-----Original Message-----
Are the profiles allowed to cache locally? If not then
Click to expand...
everytime a user logs on then they have to download their
profile.
Is this server you just created a dc (Assuming so) is it
Click to expand...
at a remote site? Does it have a Global Catalog -or- do
users have to go elsewhere. If you just built it and it
isn't the first dc in your domain it won't setup a gc and
then all your users have to go elsewhere to logon.
 
check the c drive after a user has logged off

c:\documents and settings\USERNAME

If the user name is there then they are cached locally. Odds are they are
since it doesn't sound like you have set anything odd up. Have you made
changes to your dns server?

How did you re-create your domain? It sounds like you destroyed the only
domain controller in your forest and rebuilt it, is that correct? If so did
you have to rejoin everybody back into your domain?

Paul Bergson MCT, MCSE, CNE, CNA, CCA
 
Yes, in that case all users are cached locally. And yes
we did completely rebuild the only dc, and then we had to
rejoin everybody. Now we have a couple of profiles for
each user who has logged on since, but these have been
rationalised/removed after copying the profile across to
the new user profile. Everything seems stable, but it all
seems so slow at login. Just wondering about removing the
ability of roaming profiles as practically no one seems
to use it?
J.
 
Unless these users have a real need this is of no value and just makes
things more complicated. You can even run into problems if a user logs onto
a machine that doesn't have an app loaded the icons are probably going to
reside on the desktop, etc... so when the user selects it is just going to
break.

Paul Bergson MCT, MCSE, CNE, CNA, CCA
 
So how do I cleanly turn off the loading of profiles in
the Active Directory? Prefereably without loosing any of
the local profile on any of the winXP (Pro and Home) and
win2000 Pro clients? J.
 
1) Go to users and computers and select a user
2) Select the profile tab
3) remove the info in the profile path entry

Paul Bergson MCT, MCSE, CNE, CNA, CCA
 
Many Thanks. Can I just confirm - should this be done
when the user is logged on, so the server cached profile
is disabled and the client then uses the local cache? Or
should it be done when the client is logged off, and is
therefore forced to use the local cache? I've just seen
clients loosing files when the server profile is disabled!

Many Thanks for all the advice, Jan.
 
Best while the user is logged off

Jan Muller said:
Many Thanks. Can I just confirm - should this be done
when the user is logged on, so the server cached profile
is disabled and the client then uses the local cache? Or
should it be done when the client is logged off, and is
therefore forced to use the local cache? I've just seen
clients loosing files when the server profile is disabled!

Many Thanks for all the advice, Jan.
Click to expand...
 
Maybe u can try to activate a dns on your DC and configure all your
client to point at that DNS server.
If u need internet access place isp dns only on your DC dns
 
Luca,

Just to clarify - in the Forwarders tab. Actually, assuming that the "."
zone was deleted, both Forwarders and Root Hints eventually become available
( in about four or five minutes after deleting the "." zone ). So, you
really do not *need* to use ISP DNS information in the Forwarders tab.
Please note that I always make use of the Forwarders tab, though.

Again, this is just for clarification. I do not want to start the whole
Forwarders / Root Hints discussion!

HTH,

Cary
 
Back
Top