Long response for redirected

  • Thread starter Thread starter Milos Puchta
  • Start date Start date
M

Milos Puchta

Hi

I have very long logon time for users with
redirected folders in the Windows 2003
R2/SP2 Active Directory.

Is this normal response time of tens seconds
or should I find something misconfigured
in our system?

Regards,
Milos
 
In
Milos Puchta said:
Hi

I have very long logon time for users with
redirected folders in the Windows 2003
R2/SP2 Active Directory.

Is this normal response time of tens seconds
or should I find something misconfigured
in our system?

Regards,
Milos
Click to expand...

Check to make sure ONLY the internal DNS is sepecified for ALL internal
clients. Do not use an ISP's DNS server in their ip properties. If this the
case, please remove it from all machines, including the DC(s). Check DHCP
option 006 to make sure an ISP's or the router is not in there.

Other possible causes are a multihomed DC and a single label AD DNS name
(domain rather than the proper format of domain.com, domain.local, or
domain.milos, etc).


--
Regards,
Ace

This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP
Microsoft MVP - Directory Services
Microsoft Certified Trainer

Infinite Diversities in Infinite Combinations

Having difficulty reading or finding responses to your post?
Instead of the website you're using, try using OEx (Outlook Express
or any other newsreader), and configure a news account, pointing to
news.microsoft.com. Anonymous access. It's free - no username or password
required nor do you need a Newsgroup Usenet account with your ISP. It
connects directly to the Microsoft Public Newsgroups. OEx allows you
o easily find, track threads, cross-post, sort by date, poster's name,
watched threads or subject. It's easy:

How to Configure OEx for Internet News
http://support.microsoft.com/?id=171164

"Quitting smoking is easy. I've done it a thousand times." - Mark Twain
 
Ace

I have two DCs, every with primary DNS (because
of multimaster feature). Each DC has the primary DNS
record pointing to itself and secondary one to the other DCs
DNS. All external DNS requests are forvarded to public
DNS (This setting avoids error 1030 and 1058)
Name of DCs are FQDNs, dc1.nt.fel and dc2.nt.fel.
DC are multihomed with second NIC disabled.
There is about 4000 user accounts in AD 2003(native), but
only 1300 has been used PC and number of workstations is 42,
which is also the maximum of people working at the same time.
There are two Windows XP installations with many
applications on every PC
Every client (PC) has DNS parameter pointing to internal
DNSs "sitting" on DCs, primary to DC1 and secondary
to DC2. (Local network address is 192.168.31.0)
Profiles, home directories and redirected ditectories are
sitting on file server (No DFS is used). IP addresses of all
PCs are fixed (no DHCP)

Regards,
Milos
Check to make sure ONLY the internal DNS is sepecified for ALL internal
clients. Do not use an ISP's DNS server in their ip properties. If this
the case, please remove it from all machines, including the DC(s). Check
DHCP option 006 to make sure an ISP's or the router is not in there.

Other possible causes are a multihomed DC and a single label AD DNS name
(domain rather than the proper format of domain.com, domain.local, or
domain.milos, etc).
Click to expand...
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
 
One important addition: Because of problems with some
absence (time to time occurence ) of mapped home
drives, I have activated Wait for the network... GPO
parameter. With NON redirected directories the logon
process is much shorter that with redirection ENABLED
GPO....

Rgds
Milos
 
In
Milos Puchta said:
One important addition: Because of problems with some
absence (time to time occurence ) of mapped home
drives, I have activated Wait for the network... GPO
parameter. With NON redirected directories the logon
process is much shorter that with redirection ENABLED
GPO....

Rgds
Milos
Click to expand...

It appears your configuration looks fine. You say only 42 users are logged
on at any given time, so I wouldn't think accessing the servers during logon
times would be the problem with redirected folders. Maybe folder size? How
much data is being redirected? What folders? Are they huge or small? Is
there any synchronization going on as well? How many groups are the users
in? I've seen some installations with user accounts in 100 or more groups
take about 20+ seconds to logon just because of the enumeration occuring in
teh background.

Ace
 
Ace
It appears your configuration looks fine.
Click to expand...
For nonroaming user it works quickly

You say only 42 users are logged on at any given time
Click to expand...
This is the physical maximum. The phenomenon
does not rely on number of users, who are online.
Starting with "vanilla fresh user" the long response
is present in the first and second login ....(First is longer
because of profile creation)
I wouldn't think accessing the servers during logon times would be the
problem with redirected folders.
Click to expand...
It seems it is something behind this :-)
Maybe folder size? How much data is being redirected?
Click to expand...
At the beginning there is about 0,5MB (working average
is about 6MB, and usually no more than 30MB)
What folders?
Click to expand...
All except Start....
Are they huge or small?
Click to expand...
Nothing huge...
Is there any synchronization going on as well?
Click to expand...
No Offline
How many groups are the users in?
Click to expand...
No more than TWO levels in DC GPO plus one level on the PC.
I've seen some installations with user accounts in 100 or more groups take
about 20+ seconds to logon just because of the enumeration occuring in teh
background.
Click to expand...
Nothing like this. Users are in global groups (gg) and gg are included into
domain groups. Domain groups are included in local debugger group
on PCs and are uised for permission purposes in the file server
environment. All gg are in no access group, that is used to prevent
users from creating directories in C: drive root.

Regards,
Milos
 
In
Milos Puchta said:
Ace

For nonroaming user it works quickly


This is the physical maximum. The phenomenon
does not rely on number of users, who are online.
Starting with "vanilla fresh user" the long response
is present in the first and second login ....(First is longer
because of profile creation)

It seems it is something behind this :-)

At the beginning there is about 0,5MB (working average
is about 6MB, and usually no more than 30MB)

All except Start....

Nothing huge...

No Offline

No more than TWO levels in DC GPO plus one level on the PC.

Nothing like this. Users are in global groups (gg) and gg are
included into domain groups. Domain groups are included in local
debugger group on PCs and are uised for permission purposes in the file
server
environment. All gg are in no access group, that is used to prevent
users from creating directories in C: drive root.

Regards,
Milos
Click to expand...

Hmm. Not sure how to help, Milos. Since you do not have that many users,
maybe try taking a few of the users, mayincluding your own account, and put
them in another OU without the redirect GPO and compare the respose times.

Ace
 
Back
Top