Why do i need to create a custome profile from a parent profile ?

One of the main reasons for creating custom profiles is that should one application require a tweak to some setting, say disabling Nagle's algorithm, if you only used the parent profile, then you would have to disable it for every application. Using custom profiles allows you to fine tune settings for only a single or a group of applications.

I usually create custom profiles that contain settings that can be used across a broad range of apps, and then create other custom profiles from there. iApps take this even further, and automatically create the necessary profiles.

There should be no real limit on the number of profiles that you could create. You'd likely run out of memory first.

Hope this helps.

If I may add, the parent profiles generally have settings in them that have evolved over years of testing and guidance - they are highly optimized. I would highly recommend, that if you have to make ANY change at all to a profile, that you do so in a child profile (to keep the parent profile in its original form).

That said, and more to Josh's point, creating modified profiles is a good way to set standards for different applications (ie. SharePoint compression profiles, etc.).

As for the "mandate", it's really more of a "protect you from yourself" sort of thing, where a child profile will contain the settings inherited from a (hopefully working) parent profile and only require minor adjustments.

Thanks Josh,

Cant i create a custom profile withour deriving from parent profile ? i want my own application custom settings and dont want to be derived from parent profile.

Thanks swap