From: Howard Goldstein on
The company I work for has an application that users access via a network
connection. Senior management has decided to install the application on a
group of workstations that users can log onto in case of a network outage and
work locally on the workstations until network access is restored.

The issue is being able to log onto the workstations when the network is not
accessible. They want the users to be able to access the application with
their domain accounts so they were asking me about the availability of using
a cached profile.

Obviously a cached profile will only work if a user has logged onto the
workstation previously. That plus the fact that the default for storing
cached profiles is the last ten users (it can be changed with a registry hack
but the maximum is fifty)

Senior management does not feel this will meet their needs. The subject
came up of installing ADAM on these workstations and having that authenticate
the users when they try and log on.

I'm not sure this will work since when a user logs on DNS will query for a
domain controller to authenticate the user and ADAM is not a DC. I was
wondering if anyone can verify whether this would work or not.