![Agenda ,[object Object],[object Object],[object Object],[object Object],SharePoint](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)
Recommandé
Recommandé
Contenu connexe
Tendances
Tendances (19)
En vedette
En vedette (20)
Similaire à WSS 3.0 & SharePoint 2007
Similaire à WSS 3.0 & SharePoint 2007 (20)
Plus de Information Technology
Plus de Information Technology (20)
Dernier
Dernier (20)
WSS 3.0 & SharePoint 2007
- 1. WSS 3.0 & SharePoint 2007 Updates: The Tour Starts Here Presented by: JD Wade SharePoint Engineer, MCTS, MCSE Mail: jd.wade@hrizns.com Blog: http://wadingthrough.wordpress.com Twitter: JDWade FriendFeed: http://friendfeed.com/jdwade
- 16. Deployment Check Disk Space Backup and verify restore Backup OOB Files
- 17. Deployment Run DBCC CHECKDB on databases Run Orphan Repair Tool Stsadm –o databaserepair Document content databases Stsadm –o enumcontentdbs Check database sizes
- 18. Deployment Verify No Upgrade Timer Jobs Rename previous upgrade logs Disable anti-virus software (KB 936867) Defragment indexes in SQL (KB 943345) Backup
- 19. Deployment Stop WWW service on all WFE Preparetomove and Disconnect Content Databases Logon as Setup Run packages Cancel Wizard
- 20. Deployment Central Administration Run upgrade (KB 948780) Using psconfig
- 23. Deployment Start WWW service on all WFE Attach databases Install language pack updates Enable anti-virus software (KB 936867)
- 24. Deployment Backup Complete full crawl
- 29. Slipstream WSS-MOSS Copy Source to Installation Point
- 30. Slipstream WSS-MOSS Updates Extract the update package(s) <package> /extract:<path>
- 31. Slipstream WSS-MOSS Updates Delete the wsssetup.dll file(s) wsssetup.dll
- 32. Slipstream WSS-MOSS Updates Copy the extracted files to the Updates folder
- 33. Q & A
Notes de l'éditeur
- Determine the patch level of audience members (RTM, SP1, Infrastructure Update, Cumulative Update) Determine how many people are 32 bit versus 64 bit Ask how many people plan to deploy an update within the next 90 days Talk about support ending for SharePoint RTM in January 2009
- Check MON presentation
- Not prescriptive guidance, general guidelines, based on latest information available right now Review farm architecture Ensure adequate disk space (new binaries, increased index space needs, and upgraded logging) Backups should include any OOB files you customized Review new backup best practices http://technet.microsoft.com/en-us/library/cc706876.aspx For site collection size in GB 0-15 stsadm 15-100 SQL or DPM >100 DPM differential Always use sitelock!
- Rename log file-you may want to make a batch file to do this across a farm
- To speed up upgrade or if content DBs are greater than 25GB, preparetomove and then disconnect databases using batch file after documenting content database settings.
- Process is fully described in KB 948780
- Verify upgrade was successful using the upgrade log. Check the version number in CA. Specifics in deployment document
- Process is fully described in KB 948780
- If you detached databases, begin attaching again one by one, upgrade process will be done when they attach. There is a more advanced parallel upgrade process for very large farms available in deployment documents.
- Reasons for slipstreaming -Consistency and reduced time when building new farms -Allows you to add new servers to your existing farm -Required to install on Windows 2008