Hi gang,
We have a number of remote users logging on the their machines using cached profiles. We do set the profile up while connected to our network and domain before we send the machine out to them. The users do not have connections to our domain at their site, hence the use of the cahced profiles.
As it stands, it appears that only our XP Pro clients have this issue and not Win NT4 clients.
For a while, users logon using their cached profile just fine. Then one day, they can't. They are told the domain is no longer available. Not sure, but the timing appears to be around 90 days when this error pops up.
We have scratched our heads and tried in vain to search the web, but have not found an answer. We are now starting to see a flood of calls to our helpdesk from our remote users and we just don't have a clue.
Any one have some thoughts?
Thanks,
Michael
We have a number of remote users logging on the their machines using cached profiles. We do set the profile up while connected to our network and domain before we send the machine out to them. The users do not have connections to our domain at their site, hence the use of the cahced profiles.
As it stands, it appears that only our XP Pro clients have this issue and not Win NT4 clients.
For a while, users logon using their cached profile just fine. Then one day, they can't. They are told the domain is no longer available. Not sure, but the timing appears to be around 90 days when this error pops up.
We have scratched our heads and tried in vain to search the web, but have not found an answer. We are now starting to see a flood of calls to our helpdesk from our remote users and we just don't have a clue.
Any one have some thoughts?
Thanks,
Michael