Taken from the Microsoft site…
REDMOND, Wash. — May 29, 2007 — Microsoft Corp. today announced that Microsoft® Office SharePoint® Server 2007 has received U.S. Department of Defense (DoD) 5015.2 certification. Endorsed by the National Archives and Records Administration, the 5015.2 standard on which the DoD certification is based serves as the benchmark for government and corporate organizations that manage records and documents.
“As government regulations around information management and preservation have increased, many organizations have taken a hard look at their records management practices,” said Jeff Teper, corporate vice president of the Office SharePoint Server Group at Microsoft. “We made enterprise content management a major focus during the development of Office SharePoint Server 2007, and we’re pleased that our customers can now have the confidence of knowing it has been approved through the DoD’s rigorous 5015.2 certification process.”
Microsoft utilized the SharePoint platform in meeting the DoD 5015.2 criteria, integrating Exchange Server 2007 and extending SharePoint Server 2007’s records management capabilities with an add-on pack that will be available free to customers later this year.
But I heard the add on pack introduces performance problems due to security changes to support DOD and therefore isnt supported in a production environment…go figure.
- Project Sponsorship – does the project have an appropriate level of sponsorship within your organization?
- Governance – does your organization have a goverance plan to make sure the project is architected and executed properly?
- Information management – what data will reside within the Portal? What are your legal and privacy obligations? International laws? Liabilities?
- Capacity Planning – do you have a capacity plan in your design?
- Systems Design – do you have a design that is compliant? Have you taken into consideration the user and data requirements? Implications of your network?
- Information Architecture – do you have an information architecture that delivers value and is extensible? Managable? Do you have a common vocabulary? Have you aligned the information architecture with staff and management job goals and tasks?
- Distributed Aurthoring – do you have a plan and ownership model for content authoring?
- Branding – do you have a branding design and plan that meets requires from both a look and feel and cost of ownership perspective?
- Operations – have you planned for operational impacts? Help Desk, training, support scripts, monitoring and alerts, backup and restore, reporting (Usage compliance, search queries etc…), reporting to name a few.
- Expertise – do you have people with the appropriate level of experience? Have done this before (and not just in their lab)?
- The Schedule – https://www.msteched.com/public/agenda.aspx
- The Keynote – http://www.microsoft.com/events/teched2007/agendaspeakers.mspx
- The Attendees Party – http://www.microsoft.com/events/teched2007/attendeeparty.mspx
See you there!
- Multiple SSPs does not necessarily mean multiple index servers. The indexing role for each SSP can be on the same physical server or separate servers. Things such as crawling schedules and the number of user queries will be key information that will impact the decision.
- There is a 50-100 million document/item limit per index and query server (Depending on the Micosoft documents you read). Up to now, I have not run into capacity issues that would dictate having multiple SSPs. When multiple SSPs have been needed it has been due to business requirements, e.g., indexing requirements for confidential data, or controlling what internet/extranet users can search.
- There is no out of the box solution for federating search requests across indexes and aggregating the results.
You can associate each Web application with only one SSP. The first SSP created is marked as the default SSP for the farm. All Web applications that do not have an explicit SSP assigned use the default SSP.
The application pool identity accounts of Web applications that will need to use a shared service from an SSP must be granted access to the SSP. When you create a Web application, the application pool identity of the Web application is automatically associated with the default SSP.
All shared services exist as a tightly bound cluster of services. This means that if you create a SSP, it will contain all services. These services include User Profiles, Excel Calculation Services, BDC, Search, and Usage Reporting. All shared services are turned on at the SSP level. For example, you cannot turn off the Search service and expect all other shared services to work correctly.
Every SSP you create must have an associated administration site. The administration site is used for managing application level settings and configurations for the SSP.
Microsoft has publised several documents at http://technet2.microsoft.com/Office/en-us/library/5465aa2b-aec3-4b87-bce0-8601ff20615e1033.mspx?mfr=true
- DocAve enables fast backup and restore of business critical documents in a live environment, addressing all shortcomings inherent in the native SharePoint backup tools
- Browser-based interface (integrated with Active Directory) allows monitoring of ALL SharePoint farms
- Point&Click Content Management allows dynamic growth and change of the SharePoint topology and facilitates electronic records management.
- Item-level archiving with full index and search support saves valuable server space
- Auditing module allows tracking of all user interactions in Sharepoint, also helps companies to be compliant with various standards, such as HIPAA and Sarbanes-Oxley.
- Complete disaster recovery tool ensures 24×7 availability of all SharePoint farms
More information is available here http://www.avepoint.com/products/DocAve4_0.htm and a whitepaper is available here http://www.avepoint.com/download/MOSS_2007_Backup_Strategies.pdf
- How do I size my environment realistically (Without guessing)?
- What sort of hardware do I use?
- Size your servers to support the projected capacity over the next 3 years
- Use 64 Bit servers for Index and SQL Server
- Use 32 bit servers for Web
- Use GB LAN connections between the servers
- Use GB LAN connections between MOSS servers and the servers to be indexed
- Estimate your total storage requirements and double it
- Multiple your storage requirement by 1.3 to estimate your index