Guest rhazzon Posted January 12, 2008 Posted January 12, 2008 I'm having a problem with my users set up for roaming profiles. It appears that Sun Java keeps adding a large directory \\server\profiles \username\Application Data\Sun for each of my users. This directory can be anywhere from a few megs to nearly 200 megs. As you can imagine the result is an extended logon/logoff time as the data is transferred to the client machine. Once a week I go in and view the size of each users profile. If I notice a large profile I go in and manually delete this directory. Are there any suggestions on how to deal with this problem in a more efficient manner? Thanks to all in advance! Russ Hazzon
Guest Anthony Posted January 13, 2008 Posted January 13, 2008 Re: Roaming profiles and Sun Java App Directory Russ, That's interesting. Obviously you can change the size of the cache or move it to a different place, in the Java console. However I didn't know where those settings are stored to change remotely. I ran Process Monitor and it seems to be in the file Application Data\Sun\Java\Deployment\deployment.properties. You can change whether cached or not, the size of the cache and the path, Anthony, http://www.airdesk.com "rhazzon" <russ@hazzon.com> wrote in message news:6c89a372-7629-4d3f-9fea-1f325249410a@u10g2000prn.googlegroups.com... > I'm having a problem with my users set up for roaming profiles. It > appears that Sun Java keeps adding a large directory \\server\profiles > \username\Application Data\Sun for each of my users. This directory > can be anywhere from a few megs to nearly 200 megs. As you can > imagine the result is an extended logon/logoff time as the data is > transferred to the client machine. Once a week I go in and view the > size of each users profile. If I notice a large profile I go in and > manually delete this directory. Are there any suggestions on how to > deal with this problem in a more efficient manner? > > Thanks to all in advance! > > Russ Hazzon
Guest harrykrishna.nospam@online.ie Posted January 13, 2008 Posted January 13, 2008 Re: Roaming profiles and Sun Java App Directory rhazzon <russ@hazzon.com> wrote: >I'm having a problem with my users set up for roaming profiles. It >appears that Sun Java keeps adding a large directory \\server\profiles >\username\Application Data\Sun for each of my users. This directory >can be anywhere from a few megs to nearly 200 megs. As you can >imagine the result is an extended logon/logoff time as the data is >transferred to the client machine. Once a week I go in and view the >size of each users profile. If I notice a large profile I go in and >manually delete this directory. Are there any suggestions on how to >deal with this problem in a more efficient manner? > >Thanks to all in advance! > >Russ Hazzon If you're on a domain you could add an exclusion to the roaming profile file list to prevent these files from roaming. Open GPMC and expand User Configuration --> Administrative Templates --> System --> User Profiles and have a look at "Exclude directories in roaming profile"... HTH Ha®®y HarryKrishna.nospam@online.ie
Guest Lanwench [MVP - Exchange] Posted January 13, 2008 Posted January 13, 2008 Re: Roaming profiles and Sun Java App Directory rhazzon <russ@hazzon.com> wrote: > I'm having a problem with my users set up for roaming profiles. It > appears that Sun Java keeps adding a large directory \\server\profiles > \username\Application Data\Sun for each of my users. This directory > can be anywhere from a few megs to nearly 200 megs. As you can > imagine the result is an extended logon/logoff time as the data is > transferred to the client machine. Once a week I go in and view the > size of each users profile. If I notice a large profile I go in and > manually delete this directory. Are there any suggestions on how to > deal with this problem in a more efficient manner? > > Thanks to all in advance! > > Russ Hazzon You might approach this differently. With roaming profiles especially (but also on a domain in general) I strongly encourage you to usefolder redirection - for My Documents, Application Data, and Desktop. Redirect all of thse via group policy, to subfolders of a folder set up for users on the server (\\server\users$\%sername% .....). Check your group policy options for more info on this. If you don't keep your profiles tiny they will cause you no end of grief! Here's my boilerplate on roaming profiles.... --------------- 1. Set up a share on the server. For example - d:\profiles, shared as profiles$ to make it hidden from browsing. Make sure this share is *not* set to allow offline files/caching! (that's on by default - disable it) 2. Make sure the share permissions on profiles$ indicate everyone=full control. Set the NTFS security to administrators, system, and users=full control. 3. In the users' ADUC properties, specify \\server\profiles$\%username% in the profiles field 4. Have each user log into the domain once from their usual workstation (where their existing profile lives) and log out. The profile is now roaming. 5. If you want the administrators group to automatically have permissions to the profiles folders, you'll need to make the appropriate change in group policy. Look in computer configuration/administrative templates/system/user profiles - there's an option to add administrators group to the roaming profiles permissions. Notes: * Make sure users understand that they should not log into multiple computers at the same time when they have roaming profiles (unless you make the profiles mandatory by renaming ntuser.dat to ntuser.man so they can't change them). Explain that the last one out wins, when it comes to uploading the final, changed copy of the profile. * Keep your profiles TINY. Via group policy, redirect My Documents at the very least - to a subfolder of the user's home directory or user folder. Also consider redirecting Desktop & Application Data similarly..... so the user will have: \\server\home$\%username%\My Documents, \\server\home$\%username%\Desktop, \\server\home$\%username%\Application Data. Alternatively, just manually re-target My Documents to \\server\home$\%username% (this is not optimal, however!) If you aren't going to also redirect the desktop using policies, tell users that they are not to store any files on the desktop or you will beat them with a stick. Big profile=slow login/logout, and possible profile corruption. * Note that user profiles are not compatible between different OS versions, even between W2k/XP. Keep all your computers. Keep your workstations as identical as possible - meaning, OS version is the same, SP level is the same, app load is (as much as possible) the same. * Do not let people store any data locally - all data belongs on the server. * The User Profile Hive Cleanup Utility should be running on all your computers. You can download it here: http://www.microsoft.com/downloads/details.aspx?familyid=1B286E6D-8912-4E18-B570-42470E2F3582&displaylang=en Roaming profile & folder redirection article - http://www.windowsnetworking.com/articles_tutorials/Profile-Folder-Redirection-Windows-Server-2003.html
Recommended Posts