-
All responses Most smiled responses
-
I can't say I know. There are a lot of possibilities. Are there any errors in the event log on the client machine? Is it on all machines or specific one? There may be software installed on the client machine that is causing the issue. If you can find an error message or log please send it along and I will see if I can be of more help.
-
If you would to connect oracle database to SharePoint 2010 TechNet has a really great article at http://msdn.microsoft.com/en-us/library/ff464424.aspx that explains how to setup Business Connectivity Services to bring in Oracle data. Additionally, Excel, Visio, Access, and Reporting Services are also able to use Oracle data by using the Microsoft connection wizard. For more information visit http://blog.mclaughlinsoftware.com/microsoft-excel/how-to-query-oracle-from-excel-2007/, http://social.technet.microsoft.com/Forums/en-US/sharepoint2010setup/thread/61a531b5-7fea-44db-8b75-704b5bb25c50/, http://msdn.microsoft.com/en-us/library/ms156450.aspx, http://technet.microsoft.com/en-us/library/dd220591.aspx, http://stackoverflow.com/questions/4891387/how-can-i-import-the-contents-of-an-oracle-database-into-visio-to-create-an-enti, http://msdn.microsoft.com/en-us/library/ms156450.aspx, and http://msdn.microsoft.com/en-us/library/dd220591.aspx . If none of these solutions suit your needs, you can always build a custom solution that uses the System.Data.OracleClient namespace to query the Oracle database, return the results, and then render the information in a format of your choosing. I hope this information helps and gives you some options to explore.
-
PS. You can also consolidate list information using LINQ. Check out this article as well http://msdn.microsoft.com/en-us/library/ff742311.aspx.
-
Hi Jim,
There are number of way you could do it. If you do a quick Bing search for “SharePoint 2010 list consolidation” or “SharePoint 2010 list aggregator” you will notice that there are a lot of third party products that can help you bring together your information. This is probably the simplest way to get what you need.
If you are like me and like to do it yourself here are a few more options. Andrew Connell and Todd Baginski wrote a web part called “TBAC Content Monster Web Part for SharePoint” (CMWP) that you can download at http://archive.msdn.microsoft.com/ContentMonsterSPWP that allows you to aggregate data across websites unlike the standard out-of-the-box content query web part. The CMWP was built for SharePoint 2007, but the source code is included so you can compile it against SharePoint 2010’s API.
An out-of-the-box solution you can use combine, filter, and display your data is creating a solution with Reporting Services. Reporting Services reports have the ability to bring in information through web services. As luck would have it every SharePoint list is accessible through web services with the correct security permissions. Read more about building a Reporting Services report with SharePoint list data set at http://nikspatel.wordpress.com/2010/06/11/step-by-step-consuming-sharepoint-2010-lists-data-in-the-ssrs-2008-r2-reports/ . You will have to have a dataset for each list. You can create multiple tables to display the data or to combine the information you can create multiple sub-reports that rollup the information into one larger report. Not ideal, but it will work. Excel can be used is much the same way. Check out TechNet’s Using SharePoint lists as data sources with Excel Services (SharePoint Server 2010) at http://technet.microsoft.com/en-us/library/gg576960.aspx for more information on connecting Excel to SharePoint lists.
The last solution I can think of is going with a custom solution. You can use the SharePoint API to cycle through web application and site collections to use the SPSiteDataQuery class to find your list with a site collection. For more information about using SPSiteDataQuery visit http://www.srinisistla.com/blog/Lists/Posts/Post.aspx?List=01f20192-49aa-4e73-975b-782314f02a0a&ID=75&Web=56ee3901-627b-490f-ba09-db3c0623d63b or http://msdn.microsoft.com/en-us/library/microsoft.sharepoint.spsitedataquery.aspx. You can join multiple data tables using the merge method and then attach the consolidated data table to any type of control you would like. You could use an ASP.NET DataGridView control, a Silverlight data grid control, or even a reporting services report.
There are a few ideas for you and I hope this helps answer your question. -
I also found this article by dux today that explains how to sync Excel spreadsheets and SharePoint lists together using an Excel 2007 Add-In. It is definitely worth checking out http://sp.meetdux.com/archive/2010/03/30/Sync-Excel-SharePoint-2010.aspx.
-
Well I not exactly sure what you want to do. From what I understand you shouldn’t have your documents on a file share and in SharePoint. There would be at least two set of files and linking new and delete files would be hard to maintain.
If the files are within SharePoint Foundation, then the out-of-the-box search will include the documents in the search results. If the files are on the file share, then SharePoint Foundation alone will not allow you to search file shares because it doesn’t include SharePoint 2010 Search Connector Framework. You can install Search Server Express 2010 at http://www.microsoft.com/enterprisesearch/en/us/search-server-express.aspx, which is free, to search file shares and include the results within SharePoint Foundation. See http://social.technet.microsoft.com/Forums/en/sharepoint2010setup/thread/3294d73f-b127-439e-88af-c78c70f9a9e2 for more information on installing Search Server Express 2010 with SharePoint foundation. To show the files on the file share in SharePoint you can use a page viewer webpart on SharePoint webpage and add a path to your network drive. Check out http://www.bfcnetworks.com/configure-sharepoint-2010-search-for-crawl-file-servers/ for more information.
I hope this information as helped and please feel free to write back if I did not answer your question fully. -
Well I can tell you this, if you go to TechNet and look at the minimum software requirements for Microsoft Project Server 2010 the article says the following:
“At a high-level, the key requirements for Project Server 2010 are as follows:
• The 64-bit version of Windows Server 2008 Service Pack 2 or Windows Server 2008 R2
• Microsoft SharePoint Server 2010 Enterprise version
• For a farm deployment, database servers must be the 64-bit version of Microsoft SQL Server 2008 with Service Pack 1 (SP1) and Cumulative Update 2, Microsoft SQL Server 2008 R2, or Microsoft SQL Server 2005 with Service Pack 3 (SP3)
• Microsoft Internet Explorer 7, Microsoft Internet Explorer 8, or Microsoft Internet Explorer 9 for Microsoft Project Web App user access"
To read more about Microsoft Project Server 2010’s software requirements at http://technet.microsoft.com/en-us/library/ee683978.aspx. -
asked by Liakath
Hi Liakath,
From Excel you can only import into a new SharePoint list. The only way to get around this is to open your SharePoint list in datasheet view and copy and paste the data from the spreadsheet into the datasheet view of the list. Your spreadsheet columns need to match the SharePoint list exactly to copy and paste the information in correctly. There are other third-party products you can explore as well if you need a more robust solution. -
To quote John D. Ross from this SharePoint forum response at http://social.technet.microsoft.com/Forums/en-US/sharepoint2010setup/thread/2283d53c-50fd-4571-a6aa-f6eb6e91e2c5 "You can specify another drive -- but SharePoint will still put the information in the root folder (../14) on the C drive. It doesn't take up a ton of space. What takes up the most space on a SharePoint server are the index, log, and database files all which can easily be moved to another drive." I personally always install on the C:\ drive and have the log files stored on another drive because they can grow in size, but there are no hard fast rules. All the installations of SharePoint I have seen have also been on the C:\ drive. Hope this helps.
-
If you would like to learn SharePoint 2010 without having the software you should check out my post at http://www.the14folder.com/2010/07/27/sharepoint-2010-virtual-labs/ for all the latest SharePoint 2010 virtual labs. All you need is a web browser (IE7 or higher to be exact) and you can work through the tutorials to learn about SharePoint. If you want to install SharePoint 2010 on your work or home computer you will need Windows 7, Windows Vista, or Windows Server 2008 SP2 or higher. TechNet has a really great article to help you set up your training environment at http://msdn.microsoft.com/en-us/library/ee554869.aspx. I hope this helps.
-
No problem. I am so glad it was helpful. Congrats on starting your SharePoint journey!
-
-
asked by Liakath
Hi munnaprecious,
I read your question on the Microsoft forums and answered it to the best of my abilities. I must admit that your question was hard to understand. This is what I think you are saying.
You are working for a university and you’re getting exam results in Excel, .mdf, .bak, and .txt file formats. You are combining the results into a SQL database so the data is all in one place. You had an ASP.NET website, but now you are trying to display the results in SharePoint. You created a web part in a feature and solution, but developing it is slow and uploading your new solution each time there is an error is time consuming. I think you are asking if there is a better way to develop and display the exam results in SharePoint.
To answer your questions it really depends. You said you had an ASP.NET website before. Did you create a user control to display the results in your aspx page? If you created a user control in your ASP.NET website then you can use a web part load the user control into SharePoint for you. Check out http://msdn.microsoft.com/en-us/library/ff649867.aspx#Y1596. With a user control web part you may be able to use the work you did in the ASP.NET website and alter the code a little bit to incorporate SharePoint security.
The other way you may want to consider displaying your results is with Reporting Services reports. I am assuming that you have a full version of Microsoft SQL Server. Reporting Services reports are easy to create and even easier to deploy. You can deploy your reports to a Reporting Services report server or directly into SharePoint. You restrict displaying data based on security and/or student ID, though it will take a little bit of planning. For more information about SharePoint and Reporting Service visit http://technet.microsoft.com/en-us/library/bb326358.aspx and http://msdn.microsoft.com/en-us/library/ms159170%28v=sql.100%29.aspx.
In SharePoint 2010, you can also create a connection you’re SQL Server database and allow teachers to add and modify exams results using SharePoint lists and Business Connective Services. This would give teachers a way to enter exam results without having to send you an Excel spreadsheet or text file. You will need to do some planning around security, views, backups, and tracking changes made my teacher’s in case of mistakes. For more information about Business Connective Services visit http://msdn.microsoft.com/en-us/magazine/ee819133.aspx and http://technet.microsoft.com/en-us/sharepoint/ee518675.
I hope I answered your question and gave you some things to think about. It sounds like you might need additional help. I would suggest seeking out a Microsoft partner in your region that can look at your situation specifically and give you additional advice. To find a Microsoft SharePoint Partner near you check out http://sharepoint.microsoft.com/en-us/partners/Pages/Pinpoint.aspx. -
Preventing users from deleting items in SharePoint is a common issue. The recycle bin in SharePoint 2010 helps prevent the permanent deletion of files, folders, and sites, but you still need administrative assistance sometimes to restore the item. Ideally, the user's security permissions should be configured to restrict their access so they don’t even have the option to delete. You could break the security inheritance on the folder and change the permissions so that certain users cannot delete the folder, but the files in the folder will inherit the authorization permissions. You could also break the inheritance of each file in the folder, but that would be time consuming and hard to maintain when new files are added. You could probably create a workflow to give each added file the correct permissions, but all the unique permissions would get messy to maintain in the future.
To prevent any item from being deleted in a list or a site I would use an event handler if security permissions will not due. Event handlers are a compiled module of custom managed code that responds when specific SharePoint triggering events take place. In our case, we would want attach our event handler to the list and wait until the list fires an ItemDeleting event. An ItemDeleting event will run your custom code just before it starts deleting the folder. In your code you want to stop SharePoint from executing the rest of the SharePoint deletion code by cancelling the event.
Check out my blog post at http://www.the14folder.com/2011/07/20/prevent-accidental-deletion-sharepoint/ to see instructions on how to create an event handler to stop a folder from being deleted. -
Steven Ma on the Microsoft forums gave you an awesome reply. Check out his response at http://social.technet.microsoft.com/Forums/en/sharepoint2010setup/thread/0838eedb-13b1-4a24-96f5-53750a18a20c and view the article at http://sharepointcoding.wordpress.com/2010/04/16/performancepoint-2010-dashboard-designer-an-unexpected-system-error-has-occurred-when-adding-a-data-connection/ . It sounds like your issue exactly. Make sure you followed all the steps. Let me know if you are still having an issue.
-
Unfortunately there isn't much you can do. I have experienced the same issue myself. The problem is that the virtual labs share server resources and the search indexing strains the server to the point that I think the server shut downs the image. Indexing content can take along like as well. I have seen Fast search crawl content for days. I would continue the lab and just ignore the fact that search won't return the results you are expecting. The idea is understand where functionality is located within SharePoint so that it the future you can set it up for yourself in a real environment. You can also try contacting TechNet support and see if they can help resolve this issue (http://technet.microsoft.com/en-ca/subscriptions/bb521230.aspx).
-
The short answer is yes. The SharePoint Timer Service (owstimer.exe) is a Windows service. Services in Windows must be created in a Windows Service application project or another .NET Framework–enabled project that creates an .exe file when built and inherits from the ServiceBase class. The owstimer.exe was likely compiled using managed code as an .exe assembly and as such the runtime is started automatically by mscoree.dll when the .exe is run.
For more information about Windows services visit http://msdn.microsoft.com/en-us/library/d56de412%28v=vs.80%29.aspx.
For more information about hosting the Common Language Runtime visit http://msdn.microsoft.com/en-us/library/9x0wh2z3%28v=vs.71%29.aspx.
For more information about SharePoint’s owstimer.exe visit SharePoint 2010 Architectures Overview (http://msdn.microsoft.com/en-us/library/gg552610.aspx) and Creating Custom Timer Jobs (http://msdn.microsoft.com/en-us/library/cc406686%28v=office.12%29.aspx).
Thank you for your question and please feel free to follow up with any additional questions you may have about the SharePoint Timer Service.
~The 14 folder -
Yes it is possible.Check out Steve Curran's post "Using Documents Sets in the SharePoint Client Object Model" at http://sharepointfieldnotes.blogspot.com/2010_06_01_archive.html. It is a really good positing and I think you will find all the information and code you need there. Thank you for your question and feel free to write back if you have any additional questions.
Cheers,
The14Folder -
This is a very interesting question anonymous visitor. It sounds like you are doing your homework before doing your migration which is great. I think the best way to answer your question is to briefly speak about how workflows work. The following summaries how workflows are executed from start to finish:
1. A person or process initiates some action that causes the workflow to begin. In SharePoint 2007, workflows can be:
* Started on demand by a user by using the SharePoint user interface.
* Started or resumed in response to the On Item Created event for an item in a list or document library.
* Started or resumed in response to the On Item Changed event for an item in a list or document library.
* Started or resumed programmatically through the SharePoint object model.
* Started programmatically through the Workflow Web service.
2. Once the workflow begins a process is created to execute tasks or actions in the workflow code. Not all workflows use the same hosting process.
* Workflows started from the SharePoint user interface use the W3wp.exe process that is specific to the IIS Web application the workflow was initiate from.
* If the workflow uses DelayActivity code or has a noncatastrophic error when the workflow instance begins then the Owstimer.exe server process is the host process. The Owstimer.exe is the SharePoint timer service process and is used in this context to start workflows when DelayActivity code is used or to try executing a failing workflow again at a later time.
* When an external application (such as a console application, Web service, or Windows Communication Foundation service) creates items programmatically through the SharePoint object model, the process running the code becomes the workflow host.
3. The workflow determines what action needs to perform next and executes the code.
4. If the workflow needs to wait for a response before it can continue, then the SharePoint event handlers tell the Windows Workflow Foundation Runtime Engine to put the workflow to sleep using the SQL workflow persistence service.
1. When a workflow becomes idle the Windows Workflow Foundation Runtime Engine calls the SQL workflow persistence service to save the workflow state into the content database of your SharePoint website.
2. The SQL workflow persistence service assigns correlation tokens for the workflow and to each task as that the workflow engine can use unique identifiers to map events and actions to the correct workflow object. Next, the SQL workflow persistence serializes the workflow object turning into a binary string, and then saves it with a unique Workflow Instance ID to the SharePoint content database. This process is called dehydration.
3. Once the workflow object is safely stored within the database the memory used to run the workflow is released and the workflow is considered to be put to sleep.
5. When SharePoint receives a response to carry out the next action from ones of its event handlers, the Windows Workflow Foundation Runtime Engine wakes up the sleeping workflow using the SQL workflow persistence service. When the new response data and the data from the store workflow object the workflow can run the code to perform the remaining actions.
1. When a user or system respond to a workflow action, the unique Workflow Instance ID is passed to the Windows Workflow Foundation Runtime Engine and SQL workflow persistence service finds the workflow object in the SharePoint web application’s content database.
2. When the Windows Workflow Foundation Runtime Engine retrieves and deserializes the workflow object from the database, it performs many checks to ensure that the workflow object is mapped to the correct response. The checks ensure the workflow DLL has the correct namespaces, entities, and correlation tokens. The process of retrieving the workflow object is called hydration.
3. Once the workflow object is successfully retrieved and passed all its checks the workflow is awake and is able to execute the rest of the action code.
6. Steps 3 to 5 are repeated for each action as necessary until the workflow is complete. Once the workflow is complete, the workflow status is updated and the workflow memory and hosting process are released.
To answer your question there are ways that workflows might not make it through the migration process. The following are situations you should consider before migrating your SharePoint 2007 workflows to SharePoint 2010:
1. A person or process initiates some action that causes the workflow to begin as a migration occurs: Workflows that are executing code are processing data in the memory of the server. If you begin a migration while the workflow is still in memory it is possible for the information and the workflow instance to be lost. Before starting your migration it wise to make sure that your SharePoint sites are not able to be accessed by users. This ensures that no new workflow instances are initiated and any workflows that were running are hopefully completed or sleeping within the SharePoint web application content database.
2. Identify any custom workflows that use DelayActivity code: The DelayActivity code delays an activate workflow from executing. If a workflow becomes completely idle during the delay and the UnloadOnIdle method is set to true, then the workflow may be unloaded from memory, put to sleep, and then reloaded into memory when the specified delay time expires. If the UnloadOnIdle method is set false then the workflow will remain in the server’s memory and may be lost during a migration process. You want to ensure no new workflow instances are initiated and any workflow that were running are hopefully completed or sleeping within the SharePoint web application content database.
3. Make sure any external applications do not start workflows during the migration process: If you have external applications in your company interacting with SharePoint you want ensure that no new workflow instances are initiated. The workflow instance could be in memory and could be lost. Again the best strategy to limit access to the SharePoint environment.
4. Ensure all custom workflow code is working correctly before the migration: If your workflow is not working correctly then the Owstimer.exe server process might trying to reactive the workflow action repeatedly. Especially if you are moving content databases to another SharePoint 2010 farm, this workflow instance could get lost. Make sure custom workflow code is in working order by checking the event and SharePoint logs on your server. Once the code is corrected the workflow will either finish or become idle and be saved to the content database.
5. Run the pre-upgrade checker to look for potential issues: The pre-upgrade checker reports missing customizations and issues with orphaned sites, and more, so that you can address these issues before you perform your upgrade. The pre-upgrade checker also checks your workflows for the following issues:
* 956447 (http://support.microsoft.com/kb/956447/): The ModifiedWorkflowActionsFile rule in Pre-Upgrade Checker can warn that the default declarative workflow actions file has been modified
* 956448 (http://support.microsoft.com/kb/956448/): The CustomWorkflowActionsFiles rule in Pre-Upgrade Checker in Windows SharePoint Services 3.0 Service Pack 2 can warn that custom .ACTIONS files exist in the farm
* 956449 (http://support.microsoft.com/kb/956449/): The ModifiedWebConfigWorkflowAuthorizedTypes rule in Pre-Upgrade Checker for Windows SharePoint Services 3.0 Service Pack 2 can warn that Web.config files contain modified authorized types for workflow
If the pre-upgrade checker is not run and the issues not corrected it is possible that your workflow will not work correctly. For more information about the pre-upgrade checker that comes with Office SharePoint Server 2007 with Service Pack 2 visit TechNet’s Run the pre-upgrade checker article at http://technet.microsoft.com/en-us/library/cc262231.aspx.
6. Check to see if the Workflow Auto Cleanup timer has been disabled: If your Workflow Auto Cleanup timer job is disabled in your Office SharePoint Server 2007 environment, make sure that you disable this timer job in your new environment also. If this timer job is enabled in the new environment and disabled in the previous version environment, you might lose workflow associations when you upgrade. For more information about this timer job visit Disable preservation of workflow history at http://technet.microsoft.com/en-us/library/ee662522.aspx.
If you are using out-of-the-box SharePoint workflows do not worry too much. Microsoft developers know how to handle their own solutions and migrate them forward correctly. You will notice in the web.config files of the SharePoint 2010 virtual directories that there are redirect statements so that if code is looking for the SharePoint 2007 DLLs they are redirected to the SharePoint 2010 workflow DLLs. These DLLs likely have code for the old SharePoint 2007 workflow actions and also the new SharePoint 2010 workflow actions. By having two sets of code the old workflow actions can finish correctly and then any new workflows going forward will use the new SharePoint 2010 workflow actions.
When it comes to your custom workflow code make sure all the code is copied on the SharePoint 2010 environment and that any web.config or app.config settings are already in place. When the websites are finished being migrated you want everything to be in place so that workflows can complete their jobs.
If you are moving between farms remember that you want to make sure that your workflows are either completed or sleeping in the content database of your site. Any workflows in memory have the highest risk of getting lost or not finishing as the processes will not be active in your new farm.
I hope I have answered your question and gave you some things to think about. Thank you for submitting your question and good luck on your SharePoint 2007 to 2010 migration. Please feel free to send any additional questions you may have.
For more information about SharePoint workflows visit http://www.the14folder.com -
Planning for SharePoint 2010 can be difficult and find the right documentation to help you can even be harder to find. With SharePoint 2010, Microsoft has been pretty good about producing documentation. You will not find one document that explains start to finish how to go about your project. How to implemented SharePoint 2010 is different for every company and its needs. The following are five general stages that every company should go through to properly plan and execute their SharePoint environment:
1) Evaluation: This stage involves installing a version of SharePoint 2010 to use and explore. You want to make sure that SharePoint is the right fit for your company and understand how it can be applied to help meet your strategy goals.
2) Planning and Architecture: This stage involves creating the blueprints of how your SharePoint 2010 environment will be built, configured, and maintained. Planning and architecture is often over looked or simplified because companies have immediately needs they want to satisfy. I cannot express how important it is to properly plan your SharePoint environment. If you do not spend the time up front you will surely spend more time and money in the end when your environment crashes, has very poor performance, or has become too unwieldy to maintain.
3) Configuration and Development: This stage involves building your SharePoint environment based on the documents produced from the planning and architecture stage. You want to have a good idea of the best practices you should follow while developing customizations to ensure long term scalability and maintenance. You should always have a development, staging, and production environment. Everything that is built by developers should be thoroughly tested in the staging environment before being deployed to the production environment.
4) Deployment: This stage involves preparing and moving your code and configurations to your production environment. This can involve deployment of code, training of users, and content migration.
5) Support and Daily Operations: This stage involves administration of the infrastructure. You will want a back up and disaster discovery plan in place. Additionally you will want to schedules monthly outages to apply major code customization, software updates, and performance enhancements.
In case you have not evaluated SharePoint 2010 you should know that you can download a trail version of the software from the TechNet evaluation center at http://technet.microsoft.com/en-us/evalcenter/ee388573.aspx that is good for 180 days. If you are thinking about running a virtualized environment you can download a demo Hyper-V image from the Microsoft Download Center at http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=751fa0d1-356c-4002-9c60-d539896c66ce that can be also used for 180 days and includes Microsoft Office Communication Server 2007 R2, Microsoft Visual Studio 2010, Microsoft SharePoint Server 2010 Enterprise Edition, Microsoft Office Web Applications, Microsoft FAST Search for SharePoint 2010, Microsoft Project Server 2010, Microsoft Office Professional Plus 2010, Microsoft Visio 2010, Microsoft Project 2010, and Microsoft Office Communicator 2007 R2. Please visit the http://www.the14folder.com for more information on SharePoint 2010 Editions at http://www.the14folder.com/2010/05/12/microsoft-sharepoint-2010-editions/, Hardware Requirements for SharePoint 2010 at http://www.the14folder.com/2009/12/15/hardware-requirements-for-sharepoint-2010/, and Software Requirements for SharePoint 2010 at http://www.the14folder.com/2010/02/20/softeware-requirements-sharepoint-2010/.
From your question is sounds like you would like to start stage 2. Microsoft’s TechNet website has a whole section devoted to planning and architecture at http://technet.microsoft.com/en-ca/library/cc261834.aspx. The TechNet website includes planning worksheets at http://technet.microsoft.com/en-ca/library/cc262451.aspx and <a technical diagrams at http://technet.microsoft.com/en-ca/library/cc263199.aspx that you will find handy. The Microsoft Download Center at http://www.microsoft.com/downloads/en/results.aspx?freetext=SharePoint+2010&displaylang=en&stype=s_basic also has guides, worksheets, and white papers on SharePoint 2010 that provide a lot of useful information. I also recommend checking out Dux Raymond’s website at http://sp.meetdux.com/default.aspx. Dux Raymond is a certified Project Management Professional and wrote a book called SharePoint for Project Management at http://oreilly.com/catalog/9780596520151/ that speaks about SharePoint 2007, however it will still be very relevant. Apress is also coming out with a book called Pro Project Management at http://apress.com/book/view/9781430228295 with SharePoint 2010 that may be useful, however I have not read this book as well. Additionally, at www.the14folder.com I have a section in my right side of the screen with links completely devoted to resources for SharePoint 2010 planning that you may find interesting.
You should definitely do your own research, however I would also recommend talking to a SharePoint consulting firm in your area. SharePoint is a big product and good consultants can help you avoid common pit fall that they have learned the hard way through experience. To find a SharePoint consulting firm in your area please visit the SharePoint partner finder at http://sharepoint.microsoft.com/en-us/partners/Pages/Pinpoint.aspx.
Thank you for asking your question and I hope my response has helped you. I plan to talk more about this particular topic in greater detail in future posts. Please feel free to ask any additional questions you may have. Good luck!
~The 14 Folder
-
Loading...
The 14 Folder’s Bio
Where everything you need to know about Microsoft SharePoint 2010 lives
