A Blog about SharePoint knowledge. Here you can find most information related to SharePoint Administration, SharePoint Development, My experience with SharePoint client, Information on SharePoint server and End user computing, SharePoint Study Materials etc. HAPPY Reading...!
Issue:Instant Messenger on Blackberry. When adding new contacts on the Blackberry within Instant Messenger, Contacts always remain unknown status. Contacts show up in contact list within messenger but status is "Presence unknown".
The correct method for adding contacts is to highlight your name in BB Communicator (BB Enterprise IM), then choose “Add a contact”. In the Sign-in Address field, you will type the user’s SIP address, which is not the same as their email address, although the two addresses may look the same. Using the person’s email address (ie. email@example.com) will not work, as Communicator uses the SIP address for identifying users (ie. firstname.lastname@example.org).
However, there is a bug using that method because it will try to associate the BB Communicator contact with a pre-existing contact card on your BlackBerry. Therefore, you will need to go through and create the BB contact first before adding the BB Communicator contact. There is also a problem where the “@” symbol may not resolve when performing a look-up function for the SIP address.
Recommend you add contacts through the desktop Communicator software, or the web Communicator client, instead of using the BB Communicator.
Note: Add contact on MOC and then use the same in IM on Blackberry.
From the main site collection, click the Site Actions button and choose Create from the dropdown Under Web Pages on the next screen, click Webpart Page.
Give the Web Part Page a name, choosing desired layout and choose where you would like it saved. Then click Create.
After you click Create, the page will open from the lib. Where you have saved it.
You can start editing the page from here by adding Web Parts of your choice and can edit the page later by going to the doc. lib where you have saved it.
Setting Web Part page as your SharePoint Home page
This can easily be done is SharePoint Designer. If you have not installed SharePoint designer as a part of Office 2007 Enterprise, I highly recommend it. If you do not have Office 2007 Enterprise edition, MS offers a free 30 day trial of SharePoint Designer to test out as well.
In SharePoint Designer, open the site where you saved the web part page you created. In my case it is located in my personal site. When I created the web part page, I chose to save in Documents. Hit the + and expand the Documents folder to find you Web Part page.
Drag the page out of the folder and below the default.aspx page.
This takes it out of the place is SharePoint where is it was stored to prevent other people from making changes. Now it is associated with the site only.
Right click on your web part page and select Set as Home Page.
Click OK to the message.
Click OK to the next message if it appears.
This will be renaming your old default page as default-old.aspx and will name the Web Part page as default.aspx page.
You can also preview thispage in your browser. Now you can see that your site has the web part page you created earlier, and you are able to edit the page accordingly. SharePoint Designer is incredibly powerful and you can do things much faster here than in SharePoint itself. Try it out for yourself.
If you have any queries/questions regarding the above mentioned information then please let me know. Thank you.
Use the following steps to create a new SharePoint Group:
·Choose Site Settings from the Site Actions and Click Modify All Site Settings.
·Click Advanced Permissions from the Users and Permissions column
Caution: Check if the site you are adding the group to is inheriting permissions from its parent site. The site is inheriting permissions from its parent if you see the following message: “This Website inherits permissions from its parent Web site. To manage permissions directly, click Edit Permissions from the Action menu.”
·To break Inheritance from parent site and give this site unique Permissions, click Edit Permissions from the Actions menu.
Note: You can switch back and forth between these settings as needed by selecting Inherit Permissions from the Actions Menu. However, it is important to realize that whenever a site is switched to inheriting permissions from the parent site, all unique permission settings within the site are discarded.
·Click OK on the confirmation pop-up.
·Click New to open the new menu, and select New Group.
·Type a Name and Description the new group.
Important: Use the following naming conventions.
·Enter the group owner information. The group owner will have complete control over this group, including modifying settings as well as adding or removing group membership. There can only be one group owner.
·Enter Group Settings, Membership Requests.
Caution: If you select yes for the Auto-accept requests option, any user requesting access to this group will automatically be added as a member of the group and receive the permission level associated with the group.
When we plan for an upgrade from MOSS 2007 or WSS 3.0 to SharePoint 2010 Products, we have different upgrade approaches as building blocks that can be used for optimal upgrade approach.
In-place upgrade: Use this approach to install the new version of SharePoint 2010 products on the same hardware that is used for the previous version. Upgrade the content and settings in the server farm as part of a single process.
Databases attach upgrade: Use this approach to upgrade the content for the environment on a separate farm. It doesn't upgrade any of the services or farm settings. Content databases can be upgraded in any order and can upgrade several databases at the same time. Using this approach, its possible to attach a Shared Service Provider database during DB attach upgrade, this will upgrade the profile information in the database. Using this approach, it’s not possible to upgrade the search database.
Hybrid approaches: A hybrid approach lets us to take advantage of in-place upgrade's ability to upgrade content and settings, while we take advantage of the speed of a database attach upgrade. The advantages of this method is
·Farm wide settings can be preserved and upgraded
·Customizations are available in the environment after upgrade, although manual steps may be required to upgrade or rework
I have just recently built a new SharePoint 2007 farm on a complete Windows 2008 R2 server platform and part of my standard build procedure is to implement a warm up routine, usually in the form of a script that is scheduled every morning to launch my SharePoint Web Applications. Most of you will most likely know what I am referring to here, the slowness that end users experience when loading a SharePoint site for the first time in the morning!?
By default IIS will recycle its worker processes during the night, in my case IIS 7.5 tells me this happens at 1:04 AM. You can locate this information in IIS Manager / Application Pools / Highlight your application pool in question and select Recycling under Actions / Edit Application Pool.
So what is recycling all about? Here is a brief primer;
Recycling is all about stopping any current w3wp.exe processes that are running for a particular Web Application Pool and starting a new one. The purpose of this maintenance routine is to clear the cache and start afresh! This routine obviously causes SharePoint to be quite slow when accessed for the first time after the recycling process. This is because when accessing a SharePoint Site/Page for the first time, that information needs to be re-compiled and loaded into memory again.
So what can we do about this first time slowness that occurs every morning? Wake SharePoint up!
There are arrays of scripts that have been developed by 3rd party developers that can be scheduled to run straight after the recycle occurs. These scripts are usually required to be modified for your Web applications in question.
With the introduction of IIS 7.5 and Windows 2008 R2 however, there is an actual module developed by the IIS team that will integrate directly with IIS allowing you to seamlessly enable your application pools to load your web applications after a recycle occurs. You can download the extension here; http://www.iis.net/expand/ApplicationWarmUp At the time of this writing, the Application Warm-Up module is still in beta, but I have been using it on our production servers for over a month without any hiccups.
So let’s begin our step by step guide. Download and launch the executable from the above site.
Click Install and then click Finish. As you can see, the installation process is quite simple.
Launch IIS Manager and click on one of your SharePoint Sites. In the middle pane, you will notice a new item listed under IIS titled, Application Warm-Up.
Double Click on Application Warm-Up.
Under Actions located on the far right pane, select Settings
Ensure that both options available are selected and ticked.
We also now need to add a request which is usually the main page of your SharePoint Site. This is achieved under Actions, Select Add Request and enters the URL of your SharePoint Site.
The last area that you will need to venture into is also located under Actions / Edit User Context. Here you will need to specify your Authentication settings, otherwise the module will not work and you will receive the below warning message in your Windows Application Even Log.
Description: The description for Event ID 1003 from source IIS Application Warmup Module cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
/default.aspx MACHINE/WEBROOT/APPHOST/SharePoint Central Administration v3/ Unauthorized
Here I have specified “Set Username and Type only” for the mode and “Windows” for the Type. Lastly, specify an account that has access to load the SharePoint Web Application
That’s all that is to it. All you need to do now is replicate this for each SharePoint Web application on each of your SharePoint Web Front Ends.
This neat little module has a number of advantages over scheduled scripts as it seamlessly warms up your SharePoint Web applications regardless of when the Application Pool is recycled including when you re-start your servers or re-start IIS. Please note, this little module also works with all ASP.Net applications!