Guys

 

This problem is doing my head in so I am oposting here to see if any of you IT bods have a clue....

 

Its a XP SP2 install, office XP etc etc etc on a laptop...

 

I want the user to be able to work from home loading her domain profile and then dial in etc etc, as do most users here without a problem....

 

However....

 

This laptop wont recongnise the already chached profile under Documents and settings unless its an administrator account...

 

What it does is keep building a new local profile (well, local roaming profile) with the extension .000, then .001 and so on......bloody annoying!!! :headvswal

 

If I log on with the domain admin or local admin account it doesnt do this so you'd think permissioney kinda problem, but I made everyone local admins to see if that helped but still no good????

 

I am about out of ideas and I cant find anything on Technet to help?!?

 

Any ideas guys? :confused: :confused:

I had this problem at home (networked) when I rebuilt the DC and used the same domain name etc....

 

In then end, I think I just dumped the locally cached profiles (all of them) and the networked roaming profile and let it create a new one.

Job done for me.

 

BTW, as far as I know, MS now advise making all users Local Admins - maybe they know somethign they aint telling us! (as if they would!!!!)

 

Have you checked any Group Policies?

There is I believe a policy which allows or disallows roaming profiles or something...

 

Hope that helps a bit mate

 

Steve

(IT Pretender!!)

Hi Steve

 

Well were using roaming profiles here but I have tested the problem with a non-roaming user and still the same problem??

 

Strange how it doesnt do it for the Admin accounts?!? Makes it lean towards permissions...hmmm?

 

We dont use group policies here yet mate, were still on an NT Domain until later this year.

 

If a it was a global issue then I would get this on all laptop users. Its just on this one laptop and its onyl admin profiles that can be found.

 

Its that classic message 'Windows cannot find you local profile and is attempting to log you on with a locally cached profile' followed by 'Windows cannot find your local profile and is logging you on with a temporary profile'.

 

Here's another thought, some part of the network account must be cached cus if you try and log with an network account that has never logged onto the PC before, it states that 'No domain controller is available' as you would expect. So, in essence, when the cached network accoutn logs on, XP is recongnising the fact that the network account has been used before, it just cant find the cached account, even though it is there?!? And the generates a new profile with the prefix .000 etc etc etc

 

WHY? I might end up ringing MIcrosfot at this rate?!? :headvswal :headvswal :headvswal

 

 

 

 

I had this problem at home (networked) when I rebuilt the DC and used the same domain name etc....

 

In then end, I think I just dumped the locally cached profiles (all of them) and the networked roaming profile and let it create a new one.

Job done for me.

 

BTW, as far as I know, MS now advise making all users Local Admins - maybe they know somethign they aint telling us! (as if they would!!!!)

 

Have you checked any Group Policies?

There is I believe a policy which allows or disallows roaming profiles or something...

 

Hope that helps a bit mate

 

Steve

(IT Pretender!!)

I would say you are right about perms. We just had 4 or 5 laptops come back in saying they cant find the DC, and one of the guys altered a GPO to change the perms...

 

I know you arent using GPO, but I'll find out from him which perms it changed as soon as he gets in,

 

Steve

Have you tried making the profile a mandatory one? I use this at work to stop people from making changes to desktop settings...

Have you tried making the profile a mandatory one? I use this at work to stop people from making changes to desktop settings...

 

All users here need to be roaming Angus, although I have tried without using a mandatory and roaming profile and allowed an account to operate of the locally cached profiles but still thsi doesnt work....

 

Fault now logged with Microsft.....are they Irish?!? lol :D

If the users need to be roaming, they can still be mandatory as this just stops them from amking changes. They will still download the profile when they log in but not be able to write back to it.

 

I am sure there is a policy change that solves this issue though..Technet should be able to help. I am sure we solved this with Windows NT4 on laptops here...was a long time ago though.