How People Picker works ?

Recently have an issues with the people picker , so just understand how people picker works.

 

 

All you want to know about People Picker in SharePoint ( Functionality | Configuration | Troubleshooting ) Part-1

 

All you want to know about People Picker in SharePoint ( Functionality | Configuration | Troubleshooting ) Part-2

Workflow History Hidden list

Workflow error ? where to check ?  as what i know we have 3 place to check the log :

• http://[servername]/[sitename]/lists/Workflow%20History
• list settings > workflow settings > View workflow reports
• ULS log at \12\logs (CTRL + F search for Workflow Infrastructure )

Basic sharing on Code Access Security (CAS)

Controlling access to system resources ( Dir structures and file) 

WSS have 2 security approaches :

• user identity-based
• code identity-based [digital certificate or URL or site]

WSS is use .NET Framework , which is using code identity-based approach so call CAS


Levels of trust

• Full > unmanaged code
• High > cannot call unmanaged code and enterprise service but can send email using SMTP servers , also can access sockets and file system
• Medium >  SMTP and SQL but cannot access sockets and registry
• Low > read only application virtual dir and no network connectivity
• Minimal > have execute permission only

WSS have 2 policy ( Virtual server extedned to wss this policy will applied to)

• wss_minimaltrust.config
• wss_mediumtrust.config

WSS security setting for CAS:

• machine.config > c:\windows\micorsoft.net\framwork\V2.0.50727\config
• web.config

Web.config located

• top level conetn root > C:\Inetpub\wwwroot > configuration for web server
• web part resoucces of the global assemy cache
• CONFIG ….\web server extensions\60\config\ > define for other extending vs
• ISAPI ….for the /_vti_bin
• LAYOUTS > for /_layouts
• ADMIN > SharePoint CA

How to change the Sharepoint theme template option

C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\TEMPLATE\LAYOUTS\1033

 

have one file name SPTHEMES.XML , this is the file control the theme for SharePoint. if you want to add some custom theme make sure here is added

 

1033 is for English version , 1031 is German…if you have more so different language keep at different folder .

Utility to quickly reapply themes to sites collection

After MOSS SP2 Deployment have faced some problem on the theme, so we need to edit the CSS format then to make it take effect on all sites.

now the problem come in …we have so many sites and subsites how going to get it done? as you know we need to reapply the theme then the CSS only take effect.

Luckily have some good utility tool at coplex , is so call retheme.exe.

this help a lot, you can download it from CodePlex.

Below is the coding from the Codeplex reTheme :)


using System;
using System.Collections.Generic;
using System.Linq;
using System.Text;
using Microsoft.SharePoint;

namespace reTheme
{
    class Program
    {
        static void Main(string[] args)
        {
            string siteUrl;
            if (args.Length == 0)
            {
                Console.Write("Site Collection URL:");
                siteUrl = Console.ReadLine();
            }
            else
            {
                siteUrl = args[0];
            }

            try
            {
                using (SPSite site = new SPSite(siteUrl))
                {
                    foreach (SPWeb web in site.AllWebs)
                    {
                        Console.Write(web.ServerRelativeUrl + ": ");
                        try
                        {

                            string themeName = web.Theme;
                            web.ApplyTheme("");
                            web.ApplyTheme(themeName);
                            Console.WriteLine("OK");
                        }
                        catch (Exception e)
                        {
                            Console.WriteLine(e.Message);
                        }
                    }
                }
            }
            catch (Exception e)
            {
                Console.WriteLine(e.Message);
            }
        }
    }
}