Background Over the past few months I have met with a large number of clients with SharePoint 2007 implementations who are asking the SharePoint million dollar question , “Should we migrate our SharePoint 2007 environment to SharePoint 2010 or should we just go right to SharePoint 2013?” There are 3 or 4 major questions and a few variables to those questions that frame this conversion: What is the current state of your SharePoint 2007 environment?
We have SharePoint 2007 > What do we do?...If you are on SharePoint 2007, should you skip 2010 and go to SharePoint 2013?
1 Comment - no search term matches found in comments.
Oleson & Wagner’s template on MOSS 2007 includes two sections on policies: operational and application usage
I particularly loved asking the two questions during the thrilling and meteoric rise of SharePoint 2007, mostly because no one really had a clue and that allowed me to ask another question, “So do you think you’re aware of all the sites and all the content you have in SharePoint within your organization?”
• Our organization has been utilizing SharePoint since the 2003 version and we upgrade to SharePoint 2007 using a migration tool several years ago but we wanted to wait until SharePoint Server 2013’s release to move away from SharePoint 2007
My Users Thought “Awareness” Was a SharePoint Thing – Since Office 2007 and SharePoint 2007 hit the streets in our neighborhood in tandem, my users thought SharePoint awareness, .e.g. not having to separately Check-in/out, was part of SharePoint
EBS shipped with Service Pack 1 of Microsoft Office SharePoint Server 2007 (MOSS 2007) and was specifically designed to help organizations (overwhelmed with rapidly growing SharePoint databases) redirect the BLOB content into another storage environment (like SAN or NAS or File Systems) to help reduce the load on SQL and ensure performance and scalability for SharePoint. EBS can be used with both MOSS 2007 and SharePoint Server 2010, SQL Server 2005 and 2008
Or am I wasting my time with my SharePoint 2010 deployment or upgrade from MOSS 2007? I don’t want people thinking this new research was all for naught… in fact for at least the next year and a half I would profess that this will absolutely be one of the most useful pieces of guidance any organization looking to invest in SharePoint could have at their disposal
” SharePoint Validation Problem Areas – Best Practices Legacy markups & customizations can become a major issues in SharePoint 2007 to SharePoint 2010 Branding Migration efforts Silverlight Web Part(s) and where Microsoft is headed technologically (phasing Silverlight out) WebPartZone specific to SharePoint 2010 WebPartPage specific to SharePoint 2010 ImageField specific to SharePoint 2010 Rich Text Editor specific to SharePoint 2010 Silverlight Plugin Generator Problem SLPG doesn’t escape JavaScript code SLPG uses iframe to solve caching issue with Safari Solution Add comments before loading the JavaScript <script type="text/javascript"> //<!
Using other information as a guide, this means that just like O365 will not be renamed as features are added, a proposed SharePoint 2015 major release will be the last new 'name' and full development cycle that we have been used to since the release of 2007. Instead it seems that Microsoft will bundle features that go to the cloud first, and work on-premise, in future yearly service pack releases
3 Comments - no search term matches found in comments.
8403 Colesville Rd #1100Silver Spring, MD 20910USA
Phone: (301) 587-8202Toll free: (800) 477-2446Fax: (301) 587-2711Email: hello@aiim.org
JoinBenefitsLearn More
About UsTerms of Use