Duplicate profiles being created 1

[Andronium]

I have a few workstations that when a user logs in, sometimes the workstation will not use the existing profile for that user, but instead will create a new profile for the user in the following format: "c:\winnt\profiles\username.000"

Sometimes it will create more than one duplicate (ie. username.001, username.002 etc.)

I'm also having this same problem on a terminal server running Metaframe 1.8. I can't figure out what is causing this or how to stop it, and I'm getting sick of setting up new profiles for ppl.

Can anyone help?

 

[dball63]

I've seen that a few times myself. I'm not exactly sure but I think they were created when users logged onto 2nd domain or 2nd workgroup. Is that possable?

 

[CitrixEngineer]

MetaFrame/Terminal Server will do this if it can't find a path to the roaming profile.

Why this might happen is down to a number of reasons - mostly on the network connectivity/permissions side, or could be that the profile is still held open because of a rogue file.

You shouldn't have to create new profiles each time, though. Do you hold all roaming profiles on a separate file server to your T/S boxes?

 

[Andronium]

dball:
It's possible that some of them could be logging into a different domain/workgroup, but I don't think that's the cause. We have two terminal servers and only one is having this problem. Since both terminal servers are on the same domain and have a lot of the same users, if this were the case I would expect it to be happening on both servers.

CitrixEngineer:
I just checked the profile folder on the terminal server and there are ~50 profiles that have a duplicate profile created with the .000, and very few people, if any, are using a roaming profile.

It almost seems like something in the original profile is getting corrupted, so it creates a new one and doesn't use the original one anymore.

 

[CitrixEngineer]

I can't recommend strongly enough the implementation of roaming profiles for T/S users - especially if you have more than one T/S!

If a user logs onto one T/S then another, then their profile will no longer match that stored on the first. So T/S will create a nice new one.

Hope this helps

 

[Andronium]

I'm a little bit of a rookie with T/S so please bear with me... I don't understand how implementing roaming profiles on a T/S would be a benefit. Most of the citrix users also log on to workstations. I've grown a little gunshy of using roaming profiles because it always seems to create bandwidth problems if someone logs in in another building and has to d/l a huge profile accross the WAN. And of course nobody wants to use mandatory profiles.

I'm curious how you have your roaming profiles set up. Do you have it set up so that only the TS points to the roaming profile, or do your users use roaming on their workstations as well? Can you make any recommendations or point me to somewhere with some resources on the best way to implement roaming profiles, if indeed they are the best way to go for TS?

Thanks,
Andy

 

[ChelseaGirl]

Cross threading I think.

I think Citrix engineer means that if they have settings in an app that are stored in thier profile, and it is a roaming profile, those settings will travel with the user wherever they log on.

But that does not get around the problem of getting more than one profile eg user.000, user.001 - though I don't know if roaming profiles suffer from this "bug" but local ones definatly do.

 

[rfeenie]

Hello

We have a setup whereby local profiles are intermittantly being recreated to .000 .001 etc.
As mentioned above the users are 1st logging into domainA with a generic account, they then launch some lab software ( Analyst) which requires a logon to a different domain with the users specific account, its this account which suffers the duplication problem ( which results in a printing issue).

I think this is pretty much my problem, 2 domains used causing hte problems, the question is is there a fix as all we are doing just now if deleting the duplicate profiles and we can print Ok agian until the next time.

If in doubt get the Ball Pein Hammer out