• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 591
  • Last Modified:

Windows XP Professional, the Fast Logon Optimization feature


I am in the process of trying to improve the logon process for clients (Windows XP) logging on to our domain. One of the features I have read about os the Fast Logon Optimization Feature - where a user is logged on with cached credentials and then the system tries to connect to the network.

This is exactly the feature that I would like to get working. However, I did read the documentation which states that users with logon scripts or home directory do not take advantage of this feature.  

Is there a way around this? I tried doing a test with my computer by making the following change to group policy:

"Always wait for the network at computer startup and logon"  to disabled

It seems to still run the logon script and not use cache credentials.

Any advice would be appreciated.


2 Solutions
Mike KlineCommented:
Not sure of a way around that . It will still run those scripts it just ignores fast logon optimization
"...Fast Logon Optimization is always off during logon under the following conditions:
When a user first logs on to a computer.
When a user has a roaming user profile or a user object logon script.

Note that under the preceding conditions, computer startup can still be asynchronous. However, because logon is synchronous under these conditions, logon does not exhibit optimization...."
That setting is always debated I see some people say that it only helps a bit and is not that noticeable.  We have logon scripts and home folders where I am so it is a moot point for us
In my experience, the only time that policy is useful is in multi-user workstation environments where users are on and off of the a system multiple times throughout the day but are not specifically the owner of the machine, but where roaming profiles are not used and just about no user customization is done... so almost nothing fits the condition for it working with any great benefit when in a business environment with users that own their own systems, or with users that use different systems and have a roaming profile.
It only seem valuable for a generic system being used for POS or kiosk purposes where you do not want anonymous users, but the users do not personalize the systems in any way. Plus if different people uses the computer alternately throughout the day, even that breaks the value due to the user changing and effectively making the login a first login for them so that the domain has to be checked for policy and rights validation.
mbudmanAuthor Commented:
The main problem my end users are experiencing is that when the are connected to a network (their system detects a network connection) but not connected to our company LAN their systems hang while searching for a Domain that they cannot find Errors pop up in event viewr that the domain is not available. (which is the situation). I would like to avoid this time out if the domain is not available and use cached mode at this point in time in order to speed up boot process.

Any suggesitons?
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

Tackle projects and never again get stuck behind a technical roadblock.
Join Now