In our domain we are having quiet a problem getting our mandatory profiles to work correctly. For the most part they work well, but it seems whenever the computer at which the person is at is not shut down correctly, at least we think this is the problem, it gives an error the next time they try to log on and will not let them log in. This is the error in event viewer, i deleted our server name: Windows cannot copy file \\(shared profile path I deleted the server name)\Documemts and Settings\Local Settings\Temporary Internet Files\Content.IE5\SFM1IH8Z\completeapp;jsessionid=2klU8Bq9ueRBjvCR4LR6iL2aztfuzStIBX9EMSoGNNGZ1Mzkj3cx!2090656596!adv2prodwlserver2.tgslc.org!7001!7002!2041377203!adv2prodwlserver1[1].htm to location C:\Documents and Settings\kiosk\Local Settings\Temporary Internet Files\Content.IE5\SFM1IH8Z\completeapp;jsessionid=2klU8Bq9ueRBjvCR4LR6iL2aztfuzStIBX9EMSoGNNGZ1Mzkj3cx!2090656596!adv2prodwlserver2.tgslc.org!7001!7002!2041377203!adv2prodwlserver1[1].htm. Contact your network administrator. DETAIL - The filename or extension is too long. We have had this problem for quiet sometime now and are stumped. The only fix we have is to manually delete the profile on their local computer whenever they get this error. We tryed the registry/group policy to delete the profile on log off, but when the computer is not shut down correctly it doesn't make much difference because it does not log off. As you can imagine this has become a real hastle, and we now have an additional 4 computers using a mandatory profile, a different one btw with the same problem. We have the shared folder giving them full access, any ideas? or anyone who has expierienced something similar?

We have the same problem here with our mandatory profiles and are beginning to see some problems on our roaming profiles. This started early in the year and has been getting worse. We go around each week and delete the local cached profiles so students can login. I have searched Microsoft Knowledge Base but haven't found anything similar. I know our computers are shutdown properly, so I don't think that is the problem for us. I have looked at our group policy but don't see anything that might limit the number local cached profiles. We are running Windows 2000 Server and Windows 2000 Pro on the workstations. Any ideas or suggestions will be appreciated.

We also had this problem with our Windows 2000 workstations using mandatory profiles stored on a Windows 2000 server. I assumed that the error message actually indicated the problem: that is, a filename of one of the temporary internet files was too long to be deleted in Windows. This doesn't happen all of the time; it sort of depends on what pages the user hit on Internet Explorer. We also started out trying to delete the cached copies of the profiles. We found that we couldn't delete them in Windows; we had to delete them from a DOS shell. (Since the DOS emulator truncates the filenames anyway, it doesn't have a problem with filename lengths?). Anyway, I tried a) setting the profile to delete the temporary internet files everytime you start Internet Explorer, b) relocating the spot where temporary internet files are stored to a location OUTSIDE of the profile location, and c) setting the GPO to delete the cached profile on logoff. None of this worked consistently. What DID work MOST OF THE TIME was to write and assign (via GPO) a logoff script (using the %username% variable) to delete the c:\documents and settings\%username%\local settings\temporary internet files\content.ie5 folder and its contents upon user logout. This solves the problem in all cases except when a user a) hits one of the sites that creates a cached copy of a webpage with a really long name AND b) that user also fails to logout properly (thus, the logout script fails to execute). This still leaves us having to occasionally remote in and delete the folder via a DOS shell, but this happens very infrequently compared to what was happening before. BTW, I have also combed Microsoft's Knowlegebase, with no success in finding info on this problem.