Roaming profiles using terminal services

[dicenzog]

I'm using citrix in two locations. I only have control over a windows 2000 domain running citrix XPe with sp3. The other domain is using NT 4.0 and I do not hav control over their user accounts. When a user from the NT domain logs into citrix using a seamless app they get 2 error messages:

1. Windows cannot create profile directory DETAIL - the system cannot find the file specified
2. Windows cannot find the local profile and is logging you on with a temporrary profile.

These errors do not prevent any functionality from occuring, but this is being implementd in a production enviroment and it would be good to get rid of the error messgages. Any help anyone can provide would be greatly appreciated.

 

[JohnTcolo]

Check Microsoft article KB824141, it can cause this exact error and did so on our systems until we removed it.

 

[dicenzog]

I checked all our systems and we don't have KB824141 installed on any of them. Any other suggestions?

 

[JohnTcolo]

Are your rights correct to the path where these profiles are stored? Have you been using Roaming profiles in the past? If you check the My Computer properties on the Citrix server and the user profiles tab, do you see roaming profiles listed for your Citrix users?

Is this a NT 4.0 domain, or do you also have W2K servers in it?

 

[dicenzog]

Roaming profiles are not something that is normally utilized in our w2k domain. Users from the NT 4.0 domain are trying to authenticate into the w2k domain. When I log onto the system on my domain using their logon information from their domain it works correctly. When they try the same thing they get those two errors. This is the first time the NT 4.0 people are logging into the w2k domain so they do not have a profile yet. The defualt profile has read and execute permissions for the everyone group. Is there anything special that needs to be done to allow the server utilize the roaming profile? Once again I do not have any access to the user's account information. Let me know if I can provide any more information or clarification.

 

[JohnTcolo]

Well, I think it is a conflict between NT and AD from W2K. In the user properties in side Active Directory, there is a Terminal Services Profile tab that shows where the path for the profile. I would start by looking at this info. You may not have a path for some users, or rights may not be granted.

Good Luck.

 

[mitchero]

John,

Do you have documentation about KB824141 that describes a relationship wit the profile error?

Thanks,
Ron

 

[JohnTcolo]

Ron,

I don't have it readily available. I did go to Microsoft's web site, but they have changed the reference material since the issue was first detected by us in October of this year. We applied the patch one evening, and our Citrix users began calling us the next morning upon login attempts.

I did some research, identified this patch as the problem from a Microsoft document and uninstalled it. Problem was resolved immediately. I did forward the info to an outside consultant for inclusion in their knowledge base, let me contact my resource there and see what documentation she has.

I will let you know what I find.

John T

 

[dicenzog]

There were several ways I was able to sove the problem. There is a hotfix from microsoft for windows 2000 sp3. Knowledge base number: 817361. This hotfix has not been regretion tested and is not recommended to be installed unless it is critical. Microsoft recommends istalling sp4, which has the hotfix incorperated into it. There is a setting that can be reached from gpedit.msc which will only llow local profiles to be used on a particular machine. The path is computer configuration - administrative templates - logon - only allow local user profiles. Hope this helps!

 

[DDILL]

You need to identify the cause of this error before looking at applying a hotfix. Follow the basics first. Make sure you profile path is correct. Then log in as a user that recieves this error and try to access that profile path manually as the user. Be sure to check that you have permissions to all subfolders, etc when browsing.