Did you say ALL of your user profiles are stored on ONE member server (which I assume is a W2K machine) If you have a 70 server Metaframe farm you may want more than one single profile server, (Bottleneck on the NIC there for sure, even with a multi processor multi NIC machine) just my 2 cents though. I assume with a farm of that size you are running XPe and you have thousands of users correct? (If you have 10-15,000 concurrent users, a 50 ticket a day profile issue is probably the least of your concerns!lol )
I assume also that you are using AD and not mixed?
It's tough to tell from these errors, but a roaming profile is an microsoft problem, not a Citrix problem, as you probably know. Roaming profiles and TS profiles are also, as you know, different. Kinda.. My question would be is this a TS profile issue, or a Roaming profile issue?
If you are not using Active Directory, and the profile server is not in AD this could be your problem... If all are in AD, then we can rule out some of the weird stuff that happens in mixed mode. Are all of our metaframe servers running in native mode also?
If all is Kosher in the 2K front, and considering the size of the farm, and assumd usership (that is a very big Citrix farm) I would look into decentralizing your profiles to specific regions, and see if this resolves some of your problems. You could spread them across your many Citrix servers for example...
UNless what you are telling us is that the profiles being stored on the Citrix servers themselves are problematic. Is this a clustered environment as well?
Sorry for all the questions...sometimes my train of thought becomes derailed...