Cancelling Onsave Event in MS CRM 2011 using java script

Some times we need to do some validations on javascript and that to be done on mostly onsave, so if the validation fails, we do not have to save the form.
In MS CRM 4.0 , it was different as follows
event.returnValue = false;

return false;

In MS CRM 2011, it will in different way as follows

1. need to pass the Context as follows onsave method of form
2. then use the context object inside Save function
function form_Save(executionObj){
executionObj.getEventArgs().preventDefault();}
thats it.

thanks,

yes.Sudhanshu

How to get Optionset values in MS CRM 2011 using javascript

below are the ways to get the Optionset details
get the object "<optioset_name>")
Xrm.Page.data.entity.attributes.get("aic_prmsalutation")

get the value
Xrm.Page.data.entity.attributes.get("aic_prmsalutation").getSelectedOption().value //also this will retrun the same int value

get the string value
Xrm.Page.data.entity.attributes.get("aic_prmsalutation").getSelectedOption().text//this will return the display string value not the int value
Xrm.Page.data.entity.attributes.get("aic_prmsalutation").getValue() // this will give the interger value as 96770000 like this

No Inactive (Deactivate) option for Case in MS CRM 2011

As we know there are Activate and Deactivate options for most of the entities.
But for case we do not have deactivate option where as it should be Cancel and Resolve states, but Active option is there in state.
SO case has "Active:,"Cancelled" and "Resolved" state.

thanks,

Date Comparision in MS CRM 2011, usnig javascript

Just use the below code and use your date attribute name.
here am chacking for DOB should not be future date.

    var stringDateValue = Xrm.Page.data.entity.attributes.get("<attributeName").getValue().toString();
    var strOfBirth = stringDateValue.replace("UTC+0800","");
    var dateOfBirth = new Date(strOfBirth );
    var currentDate = new Date();
    if(dateOfBirth > currentDate){
        alert("Date of Birth can not be Future Date.");
        return;
    }

thanks,
yes.sudhanshu

Force Submit in MS CRM 2011

As we were doing forceSubmit() in MS CRM 4.0, if there is a change in the field, by checking isDirty().
in MS CRM 2011 its bit different, as follow

//set the value to the attribute
        Xrm.Page.data.entity.attributes.get("<attributeName>").setValue("Value");
        Xrm.Page.data.entity.attributes.get("<attributeName>").setSubmitMode("dirty");

Other values for setSubmitMode() are
dirty : it will submit only if the value of the attribute has changed
always : it will submit the attribute's value always.
none : it will not submit at all

The default value for editable fields is ‘dirty’, which means that the value will be submitted to the server only when that data value is changed. For fields that do not get updated after the initial save of the record, such as createby, the default value is “never”. To force an attribute value to be submitted whether it has changed or not, use the setSubmitMode function with the mode parameter set to “always”.
Thanks,
yes.sudhanshu

SetFocus on MS CRM 2011 for tab, navigation and controls

there are some requirements in MS CRM , to set the focus on tab, navigation or on fields afetr doing some validations.

Set Focus for Tab
Xrm.Page.ui.tabs.get(0).setFous();

Set Focus for Navigation
Xrm.Page.ui.navigation.items.get(0).set Focus();

Set Focus for Fields (Controls)
(Xrm.Page.ui.controls.get("<attributeName")).setFocus();

but the last did not work for its onChange event.
so for that the work around is set the focus to some other field and get it back to the current field.
(Xrm.Page.ui.controls.get("<someOtherAttributeName")).setFocus();
(Xrm.Page.ui.controls.get("<currentAttributeName>")).setFocus();
Thanks,

yes.sudhanshu

checking a specific role by role name in MS CRM 2011

As in my Previous Post i have mentioned how to get the role GUIDs for the current user.
Here we can check if a specific role name belongs to the current user, cuz the role GUIDs may differ from system to system.
I found this on net, but there is a minor change.

var sameRole = UserHasRole("System Administrator");

the below function will fetch the role GUID and it will chk , if its present in the Xrm.Page.context.getUserRoles() , list of GUIDs for roles.



function UserHasRole(roleName)
{
    var serverUrl = Xrm.Page.context.getServerUrl();
    var oDataEndpointUrl = serverUrl + "/XRMServices/2011/OrganizationData.svc/";
    oDataEndpointUrl += "RoleSet?$top=1&$filter=Name eq '" + roleName + "'";
    var service = GetRequestObject();
    if (service != null)
    {
        service.open("GET", oDataEndpointUrl, false);
        service.setRequestHeader("X-Requested-Width", "XMLHttpRequest");
        service.setRequestHeader("Accept", "application/json, text/javascript, */*");
        service.send(null);
        var requestResults = eval('(' + service.responseText + ')').d;
        if (requestResults != null && requestResults.results.length == 1)
        {
            var role = requestResults.results[0];
            var id = role.RoleId;
            var currentUserRoles = Xrm.Page.context.getUserRoles();
            for (var i = 0; i < currentUserRoles.length; i++)
            {
                var userRole = currentUserRoles[i];
                if (GuidsAreEqual(userRole, id))
                {
                    return true;
                }
            }
        }
    }
    return false;
}

//this will create the XMLHttpRequest object
function GetRequestObject()
{
    if (window.XMLHttpRequest)
    {
        return new window.XMLHttpRequest;
    }
    else
    {
        try
        {
            return new ActiveXObject("MSXML2.XMLHTTP.3.0");
        }
        catch (ex)
        {
            return null;
        }
    }
}

//just to compare the two GUIDs
function GuidsAreEqual(guid1, guid2)
{
    var isEqual = false;
    if (guid1 == null || guid2 == null)
    {
        isEqual = false;
    }
    else
    {
        isEqual = guid1.replace(/[{}]/g, "").toLowerCase() == guid2.replace(/[{}]/g, "").toLowerCase();
    }
    return isEqual;
}

thanks,

yes.sudhanshu

Retreiving User Roles in CRM 2011

this below OTB function will return the list of role GUIDs of the user belongs to.
Xrm.Page.context.getUserRoles()


yes.sudhanshu

Microsoft Dynamics CRM 2011 Licensing & Pricing Guide

Good and useful link

http://crmdynamics.blob.core.windows.net/docs/Pricing_Licensing_Guide.pdf

Blurred Field in MS CRM 2011

HI i got a weird thing in ms crm 2011.

i created an attribute from the form, this is a new feasiblility.

i did not add to form.

i felt the spelling was not correct.

with out publishing, i deleted the attribute and again created the same entity with proper spelling.

then i went to form and added the old attribute, its got added, then after saving i refreshed the form, i got the attribute as the side image.

thanks,

yes.sudhanshu

Error while importing solution "Fields that are not valid were specified for the entity" in MS CRM 2011

i Got the error message while importing a solution as  "Fields that are not valid were specified for the entity".

The screen is as attached .

The scenario i felt is as per by back track observations.

What changes i did is, i had a filed which was optionset (picklist).

then i deleted that and created a textbox with the same name.

then i tried to import the solution, so i got the error.

after i got only the caught it.

i just deleted the attribute and then created the same with a different schema name and imported the solution, it worked fine...

what is this??? how this behaves like this...

thanks,

yes.sudhanshu

Workflow Utilities for Delete, Share, UnShare records in MS CRM 2011

A good solution for this in Codeflex...
please refer the following one.
good utility, infact very good...
http://crm2011workflowutils.codeplex.com/

sooperb one...

Re-Open Closed TASK, Phone call, email or activities in ms crm 2011

Sometimes, there will be a need to re-open an activity which was marked as completed. Though it makes us feel like going to the relevant activity and just re-open (Much similar to re-activating a Quote). But the answer is NO (we cannot do that in the interface).
But, CRM provides you an option to do this with the help of  “On-Demand” PROCESSES formerly WORKFLOWS.
So, let us consider an example of re-opening an completed TASK, below are the steps,

• Create an new Workflow on the task entity.
• Select “On-Demand” under Available to Run.
• Click Add-Step and select Change Status.
• Select the entity as Task and set that to open and the below options as desired.
• Save and “Activate” the workflow.

Done with the workflow!
Now, select the desired task from the list of activities and select “Run workflow” – Pick the relevant one and click OK, we are done.

same way it can be done for phone call and email also...

yes.sudhanshu

Different user groups in AD for ms crm 2011

These folowings are the user groups needs to be created or MS CRM will create while instllations, and the responsibilties are also as follows.


PrivUserGroup

• The account that the CRMAppPool application pool uses
• The account that the ASP.NET process model uses
• The user account that runs the Microsoft Dynamics CRM installation
• The computer account on which the Microsoft Dynamics CRM-Exchange E-mail Router will be installed

ReportingGroup

• All Microsoft Dynamics CRM user accounts (this includes the user who is installing Microsoft Dynamics CRM)

SQLAccessGroup

• The account that the CRMAppPool application pool uses
• The account that the ASP.NET process model uses

UserGroup

• All Microsoft Dynamics CRM user accounts (this includes the user who is installing Microsoft Dynamics CRM)

PrivReportingGroup

• The computer account on which the Microsoft Dynamics CRM Data Connector for Microsoft SQL Server Reporting Services will be installed

An error has occured. {1}{0} in MS CRM 2011, while importing solution

i got the bellow error while importing a solution in ms crm 2011.

i just created the required files in my VPC as i colud not copy the solution.
Then i forgot to copy the content for each file.
then i compressed and tried to import it and i got the mentioned ERROR.
this is stupid error , but i got it.

hope this can help any one :D

subgrid label not displaying ms crm 2011

many people may have experienced this.

If you are putting the subgrid and you are trying to show the label on form by clicking "Display Label on Form" as in side pic, it will not show on form.

So to get that, you can select "View Selected" to specific View and save it.

Then the subgrid will be rendered with label as in the 3rd pic.

but in this you will get the view selector in the grid.

If you do not want it so, then create a field(textbox) as the same name as the grid name and by using JS code just hide the textbox and show the label of the textbox.

Hope this helps.

yes.sudhanshu

Minimum permissions that are required to install Microsoft Dynamics 2011 CRM Server

Installation options

You have two options when you install Microsoft Dynamics CRM with the minimum required permissions. You can let the Microsoft Dynamics CRM server Setup program create the security groups during the installation. Or, you can use pre-created Active Directory security groups.

You can also select to turn on the Auto Group Management functionality or to turn off the Auto Group Management functionality. By default, the Auto Group Management functionality is turned on. Microsoft Dynamics CRM automatically adds the appropriate user accounts and the appropriate computer accounts to the required Microsoft Dynamics CRM security groups. If you turn off Auto Group Management, Microsoft Dynamics CRM does not automatically add these accounts. In this case, a domain administrator or a user who has sufficient permissions must add the appropriate user accounts and the appropriate computer accounts to the required groups. These additions must be made after the installation and after any user is added to Microsoft Dynamics CRM.

Installation option 1: The Setup program creates the Active Directory security groups when you install Microsoft Dynamics CRM

1. Add the user account of the user who is installing Microsoft Dynamics CRM as a member of the local administrator group. To do this, follow these steps on the Microsoft Dynamics CRM server and on the computer that is running Microsoft SQL Server:
   1. Log on to the server as a user who has local administrator permissions.
   2. Click Start, point to Administrative Tools, and then click Computer Management.
   3. Expand System Tools.
   4. Expand Local Users and Groups.
   5. Click Groups.
   6. Right-click Administrators, and then click Properties.
   7. To add the account of the user who is installing Microsoft Dynamics CRM, click Add.
2. If SQL Server Reporting Services (SSRS) is installed on a server other than the server on which you added permissions in step 1, you must add the Content Manager role at the root level for the installing user account. And, you must add the System Administrator role at the site-wide level for the installing user account. To do this, follow these steps on the Reporting Services server:
   1. Start Windows Internet Explorer, and then locate the following site:
      http://srsserver/reports
   2. On the Properties tab, click New Role Assignment.
   3. In the Group or user name box, type the user name of the user who is installing Microsoft Dynamics CRM, click to select the Content Manager check box, and then click OK.
      
      Note Use the following format when you type the user name:
      domainname\username
   4. Click Site Settings.
   5. Under Security, click Configure site-wide security, and then click New Role Assignment.
   6. In the Group or user name text box, type the user name of the user who is installing Microsoft Dynamics CRM, click to select the System Administrator check box, and then click OK.
      
      Note Use the following format when you type the user name:
      domainname\username
3. For the user account of the user who is installing Microsoft Dynamics CRM, add the following permissions to the organizational unit (OU) in the Active Directory directory service. You must do this step for the OU to which you select to install during the installation of Microsoft Dynamics CRM 2011.
   
   Permissions
   • Read
   • Create All Child Objects
   Advanced permissions
   • Read Permissions
   • Modify Permissions
   • Read Members
   • Write Members
   To add the permissions, follow these steps:
   1. Log on to the domain controller server as a user who has domain administrator permissions.
   2. Click Start, click Administrative Tools, and then click Active Directory Users and Computers.
   3. On the View menu, click Advanced Features.
   4. In the navigation pane, find the OU that you want to use for the Microsoft Dynamics CRM installation. To do this, expand the tree to the node that contains the security group.
   5. Right-click the security group, click Properties, and then click the Security tab.
   6. In the Group or user names list, click the user account of the user who is installing Microsoft Dynamics CRM if the account is listed. If the account is not listed, click Add to add the user account.
   7. In the Allow column, click to select the check box for the Create All Child Objects permission.
      
      Note By default, the Allow check box is selected for the Read permission.
   8. Click Advanced.
   9. In the Permission entries list, click Add, select the user account of the user who is installing Microsoft Dynamics CRM, and then click OK.
   10. In the Apply onto list, click Group objects.
   11. In the Allow column, click to select the following check boxes:
       • Read Permissions
       • Modify Permissions
   12. Click the Properties tab.
   13. In the Apply onto list, click Group objects.
   14. In the Allow column, click to select the following check boxes:
       • Read Members
       • Write Members
   15. Click OK three times.
4. Install Microsoft Dynamics CRM.

Installation option 2: Use the pre-created Active Directory security groups when you install Microsoft Dynamics CRM

1. Create the following security groups in Active Directory:
   • PrivUserGroup
   • PrivReportingGroup
   • ReportingGroup
   • SQLAccessGroup
   • UserGroup
   To create the security groups in Active Directory, follow these steps:
   1. Log on to the domain controller server as a user who has domain administrator permissions.
   2. Click Start, click Administrative Tools, and then click Active Directory Users and Computers.
   3. Expand the "Active Directory Users and Computers" tree to the root of the domain or to the specific organizational unit (OU) that you want to use to install Microsoft Dynamics CRM.
   4. Right-click the domain root or the OU that you want to use, click New, and then click Group.
   5. In the Group Name field, type the name of the group. For example, type PrivUserGroup.
   6. If the domain functional level is Windows Server 2003 or Microsoft Windows 2000 native, click Domain local in the Group scope list. If the domain functional level is Windows 2000 mixed, click Global in the Group scope list.
   7. Click OK.
   8. Repeat steps 1d through 1g earlier in this section to create each security group.
2. Add the user account of the user who is installing Microsoft Dynamics CRM as a member of the Local Administrator group. You must complete this step on the computer that is running the Microsoft Dynamics CRM server and on the computer that is running SQL Server.
   1. Log on to the server as a user who has local administrator permissions.
   2. Click Start, click Administrative Tools, and then click Computer Management.
   3. Expand System Tools, expand Local Users and Groups, and then expand Groups.
   4. Right-click Administrators, and then click Properties.
   5. To add the user account of the user who is installing Microsoft Dynamics CRM, click Add, and then click OK.
3. If SQL Server Reporting Services (SSRS) is installed on a server other than the server on which you added permissions in step 1, add the Content Manager role at the root level for the installing user account. Then, add the System Administrator Role at site-wide level for the installing user account. To do this, follow these steps on the server that is running Reporting Services:
   1. Start Internet Explorer, and then locate the following site:
      http://srsserver/reports
   2. Click the Properties tab, and then click New Role Assignment.
   3. In the Group or user name box, type the name of the user who is installing Microsoft Dynamics CRM, click to select the Content Manager check box, and then click OK.
      
      Note Use the following format when you type the user name:
      domainname\username
   4. Click Site Settings.
   5. Under Security, click Configure site-wide security, and then click New Role Assignment.
   6. In the Group or user name box, type the name of the user who is installing Microsoft Dynamics CRM, click to select the System Administrator check box, and then click OK.
      
      Note Use the following format when you type the user name:
      domainname\username
4. If you want Microsoft Dynamics CRM to manage the Microsoft Dynamics CRM security groups that are created during the installation, add the following permissions to the security groups that you created in step 1 earlier in this section:
   
   Permissions
   • Read
   • Write
   • Add/Remove self as member
   Advanced permissions
   • List Contents
   • Read All Properties
   • Write All Properties
   • Read Permissions
   • Modify Permissions
   • All Validated Writes
   • Add/Remove self as member
   To add the permissions, follow these steps for each security group that you created in step 1 earlier in this section:
   1. Log on to the domain controller server as a user who has domain administrator permissions.
   2. Click Start, click Administrative Tools, and then click Active Directory Users and Computers.
   3. On the View menu, click Advanced Features.
   4. In the navigation pane, expand the tree to the security group, right-click the security group, click Properties, and then click the Security tab.
   5. In the Group or user names list, click the user account of the user who is installing Microsoft Dynamics CRM if the account is listed. If the account is not listed, click Add to add the user account.
   6. In the Allow column, click to select the check box for the Write permission. This action causes the system to automatically select the check box for the Add/Remove self as member permission.
      
      Note By default, the Allow check box is selected for the Read permission.
   7. Click Advanced.
   8. In the Permission entries list, click the user account of the user who is installing Microsoft Dynamics CRM, and then click Edit.
   9. Click to select the Modify Permissions check box in the Allow column.
   10. Click OK three times.
   Notes
   • By default, the following permissions are set to Allow:
     • List Contents
     • Read All Properties
     • Write All Properties
     • Read Permissions
     • All Validated Writes
     • Add/Remove self as member
   • If you will turn off Auto Group Management for the installation, you do not have to complete step 4.
   • For more information about Auto Group Management, see the "Auto Group Management options" section.
5. When you first log on to Microsoft Dynamics CRM, and every time that a user is added to Microsoft Dynamics CRM, you must complete the following actions:
   • To log on, use a user account that has the necessary rights.
   • Manually add the users and the computers to the appropriate security groups.
6. To use the pre-created Active Directory security groups, create a configuration file to point to Microsoft Dynamics CRM. To do this, create an XML configuration file that uses the syntax that is in the following example. Modify the variables as appropriate. The list that follows the sample code describes how to modify the variables that are in this example.
   
   In the following sample code, the XML file is named Config_precreate.xml. The domain name is microsoft.com. These names represent the actual names that you use. The Active Directory hierarchy is as follows:
   • root domain
     • Company Name OU
       • Company Name OU
   Sample code
   
   

   <CRMSetup>
      <Server>
           <Groups AutoGroupManagementOff="true">
               <PrivUserGroup>CN=PrivUserGroup,OU=Company Name,OU=Company Name,DC=<domain>,DC=<domain_extension></PrivUserGroup>
             <SQLAccessGroup>CN=SQLAccessGroup,OU=Company Name,OU=Company Name, DC=<domain>,DC=<domain_extension></SQLAccessGroup>
               <UserGroup>CN=UserGroup,OU=Company Name,OU=Company Name,DC=<domain>,DC=<domain_extension></UserGroup>
               <ReportingGroup>CN=ReportingGroup,OU=Company Name,OU=Company Name, DC=<domain>,DC=<domain_extension></ReportingGroup>
    <PrivReportingGroup>CN=PrivReportingGroup,OU=Company Name,OU=Company Name, DC=<domain>,DC=<domain_extension></PrivReportingGroup>
     </Groups>
       </Server>
   </CRMSetup>
   

   Modify the parameters in the example by using the following replacement values:
   • PrivUserGroup: The name of the PrivUserGroup security group
   • SQLAccessGroup: The name of the SQLAccessGroup security group
   • UserGroup: The name of the UserGroup security group
   • ReportingGroup: The name of the ReportingGroup security group
   • PrivReportingGroup: The name of the ReportingGroup security group
   • domain: The domain name
   • domain_extension: The domain extension
   Note For more information about all the configuration file parameters and samples, see the implementation guide.
7. Run the Microsoft Dynamics CRM server installation. To do this, click Start, click Run, type C:\ServerSetup.exe /config C:\configprecreate.xml in the Open box, and then click OK.
   
   Notes
   • "C:\ServerSetup.exe" refers to the path of the ServerSetup.exe file on the installation medium.
   • "C:\configprecreate.xml" refers to the name and the path of the configuration file that was created.

Back to the top

Auto Group Management options

The Auto Group Management option is used to determine how the appropriate users and the appropriate computers are added to the security groups. Microsoft Dynamics CRM can add the users and the computers. Or, a user who has appropriate permissions in the Microsoft Dynamics CRM security groups can manually add the users and the computers.

For the Auto Group Management option, use one of the following methods. Use Method 1 to set the AutoGroupManagementOff option to "false" and to have Auto Group Management turned on. Use Method 2 to set the AutoGroupManagementOff option to "true" and to have Auto Group Management turned off.

Note The Auto Group Management option can be used only if you are installing Microsoft Dynamics CRM by using pre-created Active Directory security groups.

Note: When import organization wizard runs to import organization it considers AutoGroupManagementOff registry value to assign necessary SQL permissions on the imported database. If it's set to 1 import org wizard will not assign SQL permissions on the database, so SQL permissions may need to be assigned through SQL management studio after the import wizard succeeds. If it's set to 0 import org wizard will assign SQL permissions on the database. By default AutoGroupManagementOff reg value is set to 0.

Method 1: Set the AutoGroupManagementOff option to "false"

Because this setting is the default setting, you do not have to add anything to the configuration file. However, the following procedure is an example that describes how to set the AutoGroupManagementOff option to "false."

Create an XML configuration file that uses the syntax in the following example. Modify the variables as appropriate. To modify the variables that are in this example, refer to step 6 in the "Installation option 2: Use the pre-created Active Directory security groups when you install Microsoft Dynamics CRM" section as a guideline.

In this example, the XML file is named Config_precreate.xml. The domain name is microsoft.com. The Active Directory hierarchy is as follows:

• root domain
  • Company Name OU
    • Company Name OU

Sample code

<CRMSetup>
   <Server>
         <Groups>
  <Groups autogroupmanagementoff="false">
            <PrivUserGroup>CN=PrivUserGroup,OU=Company Name,OU=Company Name,DC=microsoft,DC=com</PrivUserGroup>
          <SQLAccessGroup>CN=SQLAccessGroup,OU=Company Name,OU=Company Name, DC=microsoft,DC=com</SQLAccessGroup>
            <UserGroup>CN=UserGroup,OU=Company Name,OU=Company Name,DC=microsoft,DC=com</UserGroup>
            <ReportingGroup>CN=ReportingGroup,OU=Company Name,OU=Company Name, DC=microsoft,DC=com</ReportingGroup>
 <PrivReportingGroup>CN=PrivReportingGroup,OU=Company Name,OU=Company Name, DC=microsoft,DC=com</PrivReportingGroup>
 </Groups>
</CRMSetup>

Method 2: Set the AutoGroupManagementOff option to "true"

1. Create an XML configuration file that uses the syntax that is in the following example. Modify the variables as appropriate. To modify the variables that are in this example, refer to step 6 in the "Installation option 2: Use the pre-created Active Directory security groups when you install Microsoft Dynamics CRM" section as a guideline.
   
   In this example, the XML file is named Config_manageoff.xml. The domain name is microsoft.com. The Active Directory hierarchy is as follows:
   • root domain
     • Company Name OU
       • Company Name OU
   Sample code
   
   

   <CRMSetup>
      <Server>
            <Groups AutoGroupManagementOff="true">
               <PrivUserGroup>CN=PrivUserGroup,OU=Company Name,OU=Company Name, DC=microsoft,DC=com</PrivUserGroup>
             <SQLAccessGroup>CN=SQLAccessGroup,OU=Company Name,OU=Company Name, DC=microsoft,DC=com</SQLAccessGroup>
               <UserGroup>CN=UserGroup,OU=Company Name,OU=Company Name, DC=microsoft,DC=com</UserGroup>
               <ReportingGroup>CN=ReportingGroup,OU=Company Name,OU=Company Name, DC=microsoft,DC=com</ReportingGroup>
    <PrivReportingGroup>CN=PrivReportingGroup,OU=Company Name,OU=Company Name, DC=microsoft,DC=com</PrivReportingGroup>
     </Groups>
       </Server>
   </CRMSetup>
   

2. Add the appropriate user accounts and the appropriate computer accounts as members of the following groups.
   
   Note You must follow this step only if the AutoGroupManagementOff option is set to "true."
   
   PrivUserGroup
   • The account that the CRMAppPool application pool uses
   • The account that the ASP.NET process model uses
   • The user account that runs the Microsoft Dynamics CRM installation
   • The computer account on which the Microsoft Dynamics CRM-Exchange E-mail Router will be installed
   ReportingGroup
   • All Microsoft Dynamics CRM user accounts (this includes the user who is installing Microsoft Dynamics CRM)
   SQLAccessGroup
   • The account that the CRMAppPool application pool uses
   • The account that the ASP.NET process model uses
   UserGroup
   • All Microsoft Dynamics CRM user accounts (this includes the user who is installing Microsoft Dynamics CRM)
   PrivReportingGroup
   • The computer account on which the Microsoft Dynamics CRM Data Connector for Microsoft SQL Server Reporting Services will be installed
   To add the accounts, follow these steps for each group in the list:
   1. Log on to the domain controller server as a user who has domain administrator permissions.
   2. Click Start, click Administrative Tools, and then click Active Directory Users and Computers.
   3. In the navigation pane, expand the tree to the node that contains the security group, right-click the security group, click Properties, and then click the Members tab.
   4. To add a user account, click Add, and then click OK. To add a computer account, click Object Types, click to select the Computers check box, and then click OK.
3. To verify which account the CRMAppPool application pool uses, follow these steps on the computer that is running the Microsoft Dynamics CRM server:
   1. Click Start, click Administrative Tools, and then click Internet Information Services (IIS) Manager.
   2. Expand the computer name.
   3. Expand Application Pools.
   4. Right-click CRMAppPool, click Properties, and then click the Identity tab.
   The NetworkService account and the LocalSystem account are both represented by the "domainname\computername $" account. Therefore, if you must add the NetworkService account or the LocalSystem account to a security group, you must add the "domainname\computername $" account.
   
   If the Configurable option is selected, you must add the specified user account to the security group. The specified user account appears in a text box.
4. To verify the account that the ASP.NET process model uses, follow these steps on the Microsoft Dynamics CRM server:
   1. In Windows Explorer, open the following folder:
      C:\WINNT\Microsoft.NET\Framework\v1.1.4322\CONFIG
   2. Right-click Machine.config, click Open With, and then click Notepad.
   3. Search for the word "username" in the text. The file contains multiple instances of the word. Locate the fifth instance of "username" that is in the text. The value for the fifth instance of "username" is the account that the ASP.NET process model uses.
   The SYSTEM account and the computer account are both represented by the "domainname\computername $" account. Therefore, if you must add the SYSTEM account or the computer account to a security group, you must add the "domainname\computername $" account.
   
   If a user name is specified in the Machine.config file, you must add the specified user account to the security group.

source : http://support.microsoft.com/kb/946677/en
http://technet.microsoft.com/en-us/library/dd979225.aspx

case resolution form can not be customized in ms crm 2011

As per the image, its completely read only.

even the attributes are not customizable, like from business required to not required.

So to make it customizable, just hide the existing Resolve Case button and put your own and on click call your own cusomt page(aspx or silver light page) and in that page you can put your fields to be captured.

But while doing so, you can not capture the record in Closed Activities in the case.

There are work arounds, u can make the enity editable to true in the DB, but risks are there wt can it do.

to do so, do not delete existing fields, just hide it and pass some default values and use ur custom fileds on for to capture the values.

You can customize the Views, so ypu can put yoyr colummns.

Network ports for Microsoft Dynamics CRM

Network ports for Microsoft Dynamics CRM

This section describes the ports that are used for Microsoft Dynamics CRM. This information is helpful as you configure the network when users connect through a firewall.

Network ports for the Microsoft Dynamics CRM Web application

The following table lists the ports used for a server that is running a Full Server installation of Microsoft Dynamics CRM. Moreover, except for the Microsoft SQL Server role, and the Microsoft Dynamics CRM Connector for SQL Server Reporting Services server role, all server roles are installed on the same computer.

Protocol	Port	Description	Explanation
TCP	80	HTTP	Default Web application port. This port may be different as it can be changed during Microsoft Dynamics CRM Server Setup. For new Web sites, the default port number is 5555.
TCP	135	MSRPC	RPC endpoint resolution.
TCP	139	NETBIOS-SSN	NETBIOS session service.
TCP	443	HTTPS	Default secure HTTP port. The port number may differ from the default port. This secure network transport must be manually configured. Although this port is not required to run Microsoft Dynamics CRM, we strongly recommend it. For information about how to configure HTTPS for Microsoft Dynamics CRM, see "Make Microsoft Dynamics CRM 4.0 client-to-server network communications more secure" in the Microsoft Dynamics CRM Installing GuideMake Microsoft Dynamics CRM client-to-server network communications more secure .
TCP	445	Microsoft-DS	Active Directory directory service required for Active Directory access and authentication.
UDP	123	NTP	Network Time Protocol.
UDP	137	NETBIOS-NS	NETBIOS name service.
UDP	138	NETBIOS-dgm	NETBIOS datagram service.
UDP	445	Microsoft-DS	Active Directory service required for Active Directory access and authentication.
UDP	1025	Blackjack	DCOM, used as an RPC listener.

Network ports that are used by the SQL Server that runs the Microsoft Dynamics CRM Connector for SQL Server Reporting Services server roles

The following table lists the ports that are used for a computer that is running SQL Server and has only SQL Server and the Microsoft Dynamics CRM Connector for SQL Server Reporting Services server roles installed.

Protocol	Port	Description	Explanation
TCP	135	MSRPC	RPC endpoint resolution.
TCP	139	NETBIOS-SSN	NETBIOS session service.
TCP	445	Microsoft-DS	Active Directory required for Active Directory access and authentication.
TCP	1433	ms-sql-s	SQL Server sockets service. This port is required for access to SQL Server.This number may be different if you have configured your default instance of SQL Server to use a different port number or you are using a named instance.
UDP	123	NTP	Network Time Protocol.
UDP	137	NETBIOS-NS	NETBIOS name service.
UDP	138	NETBIOS-dgm	NETBIOS datagram service.
UDP	445	Microsoft-DS	Active Directory service required for Active Directory access and authentication.
UDP	1025	Blackjack	DCOM, used as an RPC listener.

referred from plannning document.