[THIN] Re: Relocating user profiles
- From: "Joe Shonk" <joe.shonk@xxxxxxxxx>
- To: thin@xxxxxxxxxxxxx
- Date: Wed, 12 Mar 2008 08:48:45 -0700
Ahem, this guy named Joe Shonk has script based on over at:
http://www.theshonkproject.com/index.php?option=com_content&task=view&id=27&Itemid=1
Joe
On Tue, Mar 11, 2008 at 7:21 PM, Rick Mack <ulrich.mack@xxxxxxxxx> wrote:
> Hi Christopher,
>
> I was reminded that Warren Simondson has a utility he wrote, REMPROF (
> http:// <http://www.ctrl-alt-del.com.au/files/remprof.zip>
> www.ctrl-alt-del.com.au/files/remprof.zip), that is much more functional
> than delprof. To quote the readme:
>
> REMPROF is a command-line utility to delete local user profiles that are
> NOT in use when this command is executed.
> This utility was written to replace the command DELPROF.EXE currently
> found in the MS Windows Resource Kit. This utility offers extra features
> that will be of benefit to all admins. REMPROF has the ability to delete
> user profiles on the local machine based on age, username, or SID
> association. If a username has been deleted from a Domain or Workgroup,
> the profile often still exists with only a SID assigned to identify it.
> REMPROF can delete these profiles completely from the file system and
> registry regardless of the profile age, and without removing existing
> profiles of the same age.
> This tool could be simply run from the command line at any time, or added
> as a SCHEDULED TASK for regular cleaning of user profiles, reducing the
> overall disk space used for locally based profiles.
> REMPROF will only function when executed by a user with ADMIN rights to
> the
> profile directory.
> Usage:
> REMPROF [/LIST|username|/A|/D:days|/AD:days] [/?]
> /LIST - List all user profiles currently not in use (Default).
> username - Delete user profile based on username.
> /A - Delete all user profiles that have no username association
> i.e. The username has been deleted in Active Directory but
> a profile still exists in form of a SID.
> /D:days - Delete all user profiles equal to or older than the number of
> days specified. NB: /D: without a number is equal to /D:0.
> /D:0 will remove CURRENT user profiles not in use.
> /AD:days - Delete all user profiles that have no username association
> and are equal to or older than the number of days specified.
> NB: /AD: without a number is equal to /AD:0.
> /? - show this help file
> REMPROF without parameters will execute the /LIST switch by default.
> This utility is FREEWARE and was written by Warren Simondson of
> Ctrl-Alt-Del IT Consultancy, Australia. www.ctrl-alt-del.com.au
> Although written for Terminal Server and Citrix environments, this
> application
> will function on non-TS/Citrix workstations and servers.
> This application has been tested on the following platforms:
> Windows 2003 Server SP1
> Windows 2003 Server SP1 w/ Citrix PS 4.0
> Windows 2003 Server SP1 (Terminal Server Application Mode)
> Windows 2000 Server SP4
> Windows 2000 Server SP4 w/ Citrix MF XP
> Windows 2000 Server SP4 (Terminal Server Application Mode)
> Windows 2000 Server SP4 w/ Citrix MF 1.8
> Windows XP Professional (domain member)
> regards,
>
> Rick
>
> Ulrich Mack
> Quest Software
> Provision Networks Division
> On Tue, Mar 11, 2008 at 12:39 PM, Christopher Trotier <ctrotier@xxxxxxxxx>
> wrote:
>
> > Rick-
> >
> > Thanks for your help. The registry key was what I was missing.
> >
> > Chris
> >
> >
> > *Rick Mack <ulrich.mack@xxxxxxxxx>* wrote:
> >
> > Hi Christopher,
> >
> > You're actually dealing with 2 different profile locations.
> >
> > Setting the TS profile location defines a location for storing the TS
> > profiles. User profiles get saved to there when you log out and read from
> > there when you log in. It's exactly analogous to a network profile location.
> >
> > But when users log on to the server, the operating system stores
> > a locally cached or transient copy of their profile on disk, normally under
> > C:\documents and Settings. You may see 3 different types of profile folder
> > names. The most common is just the users logon name, but it can also be
> > username.domainname. That's quite normal as opposed to when you're
> > having profile load/unload issues, when you'll see username.001,
> > username.002 etc. This can also happen after a server crash when
> > profiles weren't unloaded properly.
> >
> > The locally cached profile location is defined by a value under
> > HKLM\Software\Microsoft\Windows NT\CurrentVersion\Profilelist,
> > ProfilesDirectory. This value is normally %SystemDrive%\Documents and
> > Settings but can be changed to a different location if desired. If your C
> > drive is filling up, then changing the location to D:\documents and Settings
> > or whatever will work fine for any NEW user logons, but will require that
> > you run delprof first to be consistent.
> >
> > Deleting the locally cached profiles on logoff can also help a lot since
> > it means you won't have 2 copies of everything hanging around. This can be
> > done by enabling a group policy "Delete cached copies of roaming profiles",
> > (computer configuration > administrative templates > system > User
> > Profiles). Running the Windows 2003 resource kit utility, delprof, will also
> > help you clean up left over profiles.
> >
> > Lastly, iIt's always a good idea to use install UPHClean (Microsoft
> > utility, microsoft downloads) to make sure your profiles unload most of the
> > time, server crashes aside.
> >
> > regards,
> >
> > Rick
> >
> > --
> > Ulrich Mack
> > Quest Software
> > Provision Networks Division
> >
> >
> > On 3/11/08, Christopher Trotier <ctrotier@xxxxxxxxx> wrote:
> > >
> > > The servers in our new Citrix farm only have 10GB OS drives (a fight I
> > > lost). Since we have 80+ users, this is creating a space issue.
> > >
> > > I enabled a local GPO on each server to move the profiles to a share
> > > on the D drive of each server as they are created: Local Computer Policy |
> > > Computer Configuration | Admin Templates | Windows Components | Terminal
> > > Services | Set Path for Roaming TS PRofiles. I added Authenticated users
> > > and
> > > Everyone to the share.
> > >
> > > This is only partially working: the profiles are still being created
> > > on C:, but also on D:, although they are being appended with *
> > > .domainname* on the D drive. The bulk of the data is still being
> > > dumped on the C drive. Weirder still, the rights are not cascading down
> > > to
> > > the newly created profiles on the D drive – this shouldn't be an issue, as
> > > the System and the specific user's accounts still have rights to them.
> > >
> > > Any ideas as to what I may have missed?
> > >
> > > thanks for your time!
> > > ------------------------------
> > > Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try
> > > it
> > > now.<http://us.rd.yahoo.com/evt=51733/*http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ>
> > >
> >
> >
> >
> > ------------------------------
> > Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try
> > it
> > now.<http://us.rd.yahoo.com/evt=51733/*http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ>
> >
> >
>
>
> --
> Ulrich Mack
> Quest Software
> Provision Networks Division
>
Other related posts:
