We are trying to reduce the size of roaming profiles to improve our log on
times.
1st.
We are initialy trying to remove unnessary files from our Default Profile,
that is used when a user logs on for the first time.
It's presently 5.5mb, which seems a lot.
a file list is included below, my question is what can be deleted cause it's
not required?
2nd.
I believe we can restrict or exculde files or directorys being included in
the roaming profiles. Presently our users profiles can be anywhere between
6-25mb.
I think this can be done in Group Policy, can any point me to any help on
this subject, and again sugest files/directorys that can be left out to
reduce size and imporve log on time?
Steve Audus wrote:
> We are trying to reduce the size of roaming profiles to improve our
> log on times.
>
> 1st. We are initialy trying to remove unnessary files from our
> Default Profile, that is used when a user logs on for the first time.
>
> It's presently 5.5mb, which seems a lot. a file list is included
> below, my question is what can be deleted cause it's not required?
5.5 MB isn't bad at all. It gets worse as various applications save data
to the Application Data folder. In my organization, a profile under 30
MB is fabulous, but I'll settle for people keeping them under 100 MB.
That's assuming, of course, that you're not trying to load a roaming
profile under a telephone modem...
> 2nd. I believe we can restrict or exculde files or directorys being
> included in the roaming profiles. Presently our users profiles can be
> anywhere between 6-25mb. I think this can be done in Group Policy,
> can any point me to any help on this subject, and again sugest
> files/directorys that can be left out to reduce size and imporve log
> on time?
The policy you're looking for is in User Configuration/Administrative
Templates/System/User Profiles. It's "Exclude directories in roaming
profile." Enter a series of directories, rooted at the user profile,
separated by semi-colons, that are to be local only. For instance, a
fictional example:
My Documents\My Music;Application Data\Google;iTunes
Our log on times are shocking and most of our profiles less than 15mb.
But it's not a network problem as once logged on, every thing flys.
Profile Limit
If I stick the limit to say about 8mb, how will this effect users with very
large profiles.
It says about warning users "you need to move some items from your profile
to network or local storage.", but our users are 11-16yrs old students and we
lock down their access very strongly to stop them messing about, so they
wouldn't have access alter their own profiles.
Excluding Folders
We already split the app data to another server, to try to speed up log on,
So I have checked out one user, a profile directory of 4.5mb and an
Application Data of 7.41mb. Is it just trial and error to work out, which
directories are not required?
(Note My Documents have never been included in Profiles)
Thank you any further help,
Steve
"David Trimboli" wrote:
> Steve Audus wrote:
> > We are trying to reduce the size of roaming profiles to improve our
> > log on times.
> >
> > 1st. We are initialy trying to remove unnessary files from our
> > Default Profile, that is used when a user logs on for the first time.
> >
> > It's presently 5.5mb, which seems a lot. a file list is included
> > below, my question is what can be deleted cause it's not required?
>
> 5.5 MB isn't bad at all. It gets worse as various applications save data
> to the Application Data folder. In my organization, a profile under 30
> MB is fabulous, but I'll settle for people keeping them under 100 MB.
>
> That's assuming, of course, that you're not trying to load a roaming
> profile under a telephone modem...
>
> > 2nd. I believe we can restrict or exculde files or directorys being
> > included in the roaming profiles. Presently our users profiles can be
> > anywhere between 6-25mb. I think this can be done in Group Policy,
> > can any point me to any help on this subject, and again sugest
> > files/directorys that can be left out to reduce size and imporve log
> > on time?
>
> The policy you're looking for is in User Configuration/Administrative
> Templates/System/User Profiles. It's "Exclude directories in roaming
> profile." Enter a series of directories, rooted at the user profile,
> separated by semi-colons, that are to be local only. For instance, a
> fictional example:
>
> My Documents\My Music;Application Data\Google;iTunes
>
> --
> David
> Stardate 8573.7
>
Thank you very very interesting, I have never considered that the amount of
GPO's on a user account could affect log on times.
As a school we have a large number of policies in place, mainly to restrict
students from accessing things their shouldn't and making changing on
workstations etc.
Luckly we don't have to worry about things like remote offices or even
syncing, as students have home folders that is re-direction and not part of
thier profile.
But how would you advise I progress testing the profiles.
I was thinking just initialy taking one student user, testing their log on
time serval workstations, to get an average time. Then taking elements out of
the mix to see the difference, i.e. taking out logon scripts, taking out
GPOs, taking out certain folders from their roaming profile, even limiting
thier profile size.
What do you think ? Thank for any advise.
Steve
"Enterprise IT System Administrator" wrote:
> The PERFECT ROAMING PROFILE is to stop it from GPO.
> In my organization, we tried different GPOs and the result will only
> increase the boot time, thus we made decision to stop it and remove all GPOs
> associated with roaming profiles. Roaming profile especially worse when u
> have offices across the board.
>
> The way we do it is to setup projects using iShared Mobiliti as a projects
> to synchronize favourite, cookies, app data, .ost . Of course the SID will
> never be able to sync. User can control when to sync and increasing boot time
> dramatically.
>
> You get to decide what you want to backup/Sync to your local document server
> or even remote portable hard drive since we have quite a lot of remote users.
>
> Nicholas
> System Manager
>
> "Steve Audus, Chaucer BEC, Sheffield UK" wrote:
>
> > David,
> >
> > Our log on times are shocking and most of our profiles less than 15mb.
> > But it's not a network problem as once logged on, every thing flys.
> >
> > Profile Limit
> > If I stick the limit to say about 8mb, how will this effect users with very
> > large profiles.
> > It says about warning users "you need to move some items from your profile
> > to network or local storage.", but our users are 11-16yrs old students and we
> > lock down their access very strongly to stop them messing about, so they
> > wouldn't have access alter their own profiles.
> >
> > Excluding Folders
> > We already split the app data to another server, to try to speed up log on,
> > So I have checked out one user, a profile directory of 4.5mb and an
> > Application Data of 7.41mb. Is it just trial and error to work out, which
> > directories are not required?
> > (Note My Documents have never been included in Profiles)
> >
> > Thank you any further help,
> >
> > Steve
> >
> >
> > "David Trimboli" wrote:
> >
> > > Steve Audus wrote:
> > > > We are trying to reduce the size of roaming profiles to improve our
> > > > log on times.
> > > >
> > > > 1st. We are initialy trying to remove unnessary files from our
> > > > Default Profile, that is used when a user logs on for the first time.
> > > >
> > > > It's presently 5.5mb, which seems a lot. a file list is included
> > > > below, my question is what can be deleted cause it's not required?
> > >
> > > 5.5 MB isn't bad at all. It gets worse as various applications save data
> > > to the Application Data folder. In my organization, a profile under 30
> > > MB is fabulous, but I'll settle for people keeping them under 100 MB.
> > >
> > > That's assuming, of course, that you're not trying to load a roaming
> > > profile under a telephone modem...
> > >
> > > > 2nd. I believe we can restrict or exculde files or directorys being
> > > > included in the roaming profiles. Presently our users profiles can be
> > > > anywhere between 6-25mb. I think this can be done in Group Policy,
> > > > can any point me to any help on this subject, and again sugest
> > > > files/directorys that can be left out to reduce size and imporve log
> > > > on time?
> > >
> > > The policy you're looking for is in User Configuration/Administrative
> > > Templates/System/User Profiles. It's "Exclude directories in roaming
> > > profile." Enter a series of directories, rooted at the user profile,
> > > separated by semi-colons, that are to be local only. For instance, a
> > > fictional example:
> > >
> > > My Documents\My Music;Application Data\Google;iTunes
> > >
> > > --
> > > David
> > > Stardate 8573.7
> > >
The Perfect Roaming Profile ? 
Linear Mode
