Profiles Profiles Profiles

[Opium]

Hi, I am running Citrix XPFR1 on a one farm two zone W2k environment. We have been coming accross so many problems regarding user's roaming profiles, getting corrupted etc... Is the final solution really just to delete and recreate the profile? There is no other way? We only added 50 users for Citrix access which will eventually grow to over 2,000+. I am receiving so many calls already related to profile issues, am I safe to assume that I am going to have to get ready for chaos?

I am also running into a weird problem that I can't figure out. Basically we are migrating users from out NT4 domain to AD gradually so we have Citrix users from both domains. NT4 users logging into NFuse are receiving their login scripts. AD users logging into NFuse get their first initial drive mappings from out login script but when they closeout of an app and open it again they don't. By putting pause statements everywhere I basically found that it craps out when running the usrlogon.cmd. The specific line is when it is calling the Application Compatibility Scripts specifically ACRegL.exe. It is not capturing all the registry keys. It is capturing COMMON_START_MENU, COMMON_STARTUP, and COMMON_PROGRAMS. It is not capturing USER_START_MENU, USER_STARTUP, USER_PROGRAMS, MY_DOCUMENTS, TEMPLATES, and APP_DATA. Since this command is in the beginning of the usrlogon.cmd it returns an error and exits the batch file bypassing the call to run the company login script. Again, it works if the AD users logs in for the very first time. Somehow their profile gets corrupted even though they log off correctly because if I delete it and recreate it, the user does not have any errors.

Please help!

 

[jkazu]

I am about to upgrade to XPe from 1.8 on Win2k.
I don't know about the AD issue and scripts, but are your roaming profiles on a server other than win2k?
I found out that profile replication during logout can fail because non-win2k servers handle the file attributes differently when dealing with a read only file in a profile. This does not affect using a non-win2k server are a regular file server. It only affects profiles. I found it in an MS technet article. The profile copies to the remote location, but when it finishes, it must replace the old profile that is already there. If a read only file is there, the server can't change it's attribute to replace the old profile. The replication fails, the local copy is never removed and the whole process is aborted as the user disconnects, though it looks like a logoff. Your event viewer will show an error from USRENV.

 

[Opium]

I actually figured out what was wrong and it was kind of stupid. There was a GPO policy for roaming profiles excluding the Start Menu and Desktop so when the profiles were copying back up to the profile server, it was not copying everything back. That is why the profile kind of got corrupted.