Hi.
i just thought i would post this ...
i created a site and used the BLANK Template and then i tried to create Taxonomy Structure ...
but the Terms Store link was nowhere to be found ..
Check the solution here
regards
Bradley Chetty
Tuesday, June 14, 2011
SharePoint 2010 Support Checklist
Hi.
There was a need for a SharePoint Support Checklist as support was becoming reactive rather than preventive. So I have setup a weekly Support check where we log on to the SharePoint Environment and perform a few checks for instance Crawls, backup ....Etc
Support Checklist SharePoint (Farm Environment)
1. Backup:
Verify that the previous backup operations completed.
STSADM Backup .
PowerShell Script Backup .
SQL Backup .
VM Backup .
2. Content Crawl:
Browse to the Search Administration Page and make sure the crawls are running. Check the full and incremental crawls.
Also check the crawl logs and pay particular attention to the errors.
Full Crawl.
Incremental.
Log Crawl Errors.
3. Check Event Log:
Please prioritize and rank the errors in the event log and then report it to the respective Support Teams.
4. Check Central Administration Issue List:
Please prioritize and rank the errors in the issue list and then report it to the respective support teams.
5. Check HDD Space:
Central Administration warnings will be issued if your C: partition doesn't have double your "physical" RAM free. Although this approach is recommended, our client’s environments are not ideal so make sure there is at least 20 Gigs free space on the c:\ on each server on the farm.
Server 1 >20 Gigs free
6. *Liaise with Users Directly:
This should be done on a monthly basis and it will strengthen relationships with clients.
7. Check CPU and Memory Performance:
Open up Task Manager and verify that the CPU usage is below an average threshold for 50 % for CPU and memory usage is below an average threshold of 70%. Make sure that a crawl isn’t currently in progress.
CPU <50%
Memory <70%
8. Check IIS and services:
Make sure all the application pools are started. Do not attempt to start any application pools rather log a call to the respective Support team.
Also check the various services are started on the server:
All Sharepoint service. e.g SharePoint timer
SMTP service if applicable
9. Check the size of the site collections:
Log on with farm credentials and check the size of the site collections.
10. Check SharePoint Server usage in Web Analytics reports:
Spot check on these reports to make sure that the predefined jobs are running and web analytics for the site is pulling data.
11. Hotfixes and service packs:
Make sure there are no service packs or updates waiting to be installed. Please let the respective Support Teams know of the updates / cumulative updates waiting to be installed. Company policy will have to be ahered too with regard to the updates/service packs.
There was a need for a SharePoint Support Checklist as support was becoming reactive rather than preventive. So I have setup a weekly Support check where we log on to the SharePoint Environment and perform a few checks for instance Crawls, backup ....Etc
Support Checklist SharePoint (Farm Environment)
1. Backup:
Verify that the previous backup operations completed.
STSADM Backup .
PowerShell Script Backup .
SQL Backup .
VM Backup .
2. Content Crawl:
Browse to the Search Administration Page and make sure the crawls are running. Check the full and incremental crawls.
Also check the crawl logs and pay particular attention to the errors.
Full Crawl.
Incremental.
Log Crawl Errors.
3. Check Event Log:
Please prioritize and rank the errors in the event log and then report it to the respective Support Teams.
4. Check Central Administration Issue List:
Please prioritize and rank the errors in the issue list and then report it to the respective support teams.
5. Check HDD Space:
Central Administration warnings will be issued if your C: partition doesn't have double your "physical" RAM free. Although this approach is recommended, our client’s environments are not ideal so make sure there is at least 20 Gigs free space on the c:\ on each server on the farm.
Server 1 >20 Gigs free
6. *Liaise with Users Directly:
This should be done on a monthly basis and it will strengthen relationships with clients.
7. Check CPU and Memory Performance:
Open up Task Manager and verify that the CPU usage is below an average threshold for 50 % for CPU and memory usage is below an average threshold of 70%. Make sure that a crawl isn’t currently in progress.
CPU <50%
Memory <70%
8. Check IIS and services:
Make sure all the application pools are started. Do not attempt to start any application pools rather log a call to the respective Support team.
Also check the various services are started on the server:
All Sharepoint service. e.g SharePoint timer
SMTP service if applicable
9. Check the size of the site collections:
Log on with farm credentials and check the size of the site collections.
10. Check SharePoint Server usage in Web Analytics reports:
Spot check on these reports to make sure that the predefined jobs are running and web analytics for the site is pulling data.
11. Hotfixes and service packs:
Make sure there are no service packs or updates waiting to be installed. Please let the respective Support Teams know of the updates / cumulative updates waiting to be installed. Company policy will have to be ahered too with regard to the updates/service packs.
Tuesday, June 7, 2011
SharePoint 2010 Upgrade
Hi.
While doing a Upgrade from SharePoint 2007 to SharePoint 2010 a few issues i came across.
Issue1:
When i did the backup of the 2007 environment it was in a read-only state ... i then proceeded to restore this DB to the new server and then upgrade the DB. all went along fine until i wanted to do the Visual Upgrade and the options were grayed out?
Solution: i went back to the 2007 environment and switched it off read-only mode did the backup and restored that backup ..and PRESTO ..the options were there ....
Issue2:
I had a lot of health issues with regard to the clean install. you can either go and disable the rules like this or you can work thru each one. most of then had a "Fix Automatically" which you should do and SharePoint tries to resolve it.
Issue3: the farm account needed "Replicated Directory Changes Permissions" in AD. Solution: just give it permissions by following the article.
Issue 4: when a people search was done the url that it linked too ould not resolve ...
when i had setup mySite i provided it with a path that it should use but ALAS!!! ...it doesnt do this. Solution: you would need to run crawl on the content sources and make sure the crawl account used has access to the Service "User Profile Service Application".
Issue 5: when completing the final step and moving users into the SharePoint ... please make sure that the users exist in the new Domain .....
so now i have a sucessful Upgrade from SharePoint 2007 to SharePoint 2010 complete with MySites and public profiles .......DONE!!!!!!!!!1
Just a side note ...the hardest part was getting the User Profile Synchronization job to work.
a very exciting project which i really enjoyed ...
Till the next issue/problem
Bradley
While doing a Upgrade from SharePoint 2007 to SharePoint 2010 a few issues i came across.
Issue1:
When i did the backup of the 2007 environment it was in a read-only state ... i then proceeded to restore this DB to the new server and then upgrade the DB. all went along fine until i wanted to do the Visual Upgrade and the options were grayed out?
Solution: i went back to the 2007 environment and switched it off read-only mode did the backup and restored that backup ..and PRESTO ..the options were there ....
Issue2:
I had a lot of health issues with regard to the clean install. you can either go and disable the rules like this or you can work thru each one. most of then had a "Fix Automatically" which you should do and SharePoint tries to resolve it.
Issue3: the farm account needed "Replicated Directory Changes Permissions" in AD. Solution: just give it permissions by following the article.
Issue 4: when a people search was done the url that it linked too ould not resolve ...
when i had setup mySite i provided it with a path that it should use but ALAS!!! ...it doesnt do this. Solution: you would need to run crawl on the content sources and make sure the crawl account used has access to the Service "User Profile Service Application".
Issue 5: when completing the final step and moving users into the SharePoint ... please make sure that the users exist in the new Domain .....
so now i have a sucessful Upgrade from SharePoint 2007 to SharePoint 2010 complete with MySites and public profiles .......DONE!!!!!!!!!1
Just a side note ...the hardest part was getting the User Profile Synchronization job to work.
a very exciting project which i really enjoyed ...
Till the next issue/problem
Bradley
Subscribe to:
Posts (Atom)