Hot answers tagged support
There should still be extended support available to companies. I actually still have clients that have paid support for Portal Server 2003. With that said, at some point it becomes cost prohibitive and I would suggest you make every effort to start planning for an upgrade.
READ COMMITTED SNAPSHOT ISOLATION is not supported by SharePoint. Review the presentation below by Lisa Gardner from the PASS Summit back in 2012 for more details. http://blogs.msdn.com/cfs-filesystemfile.ashx/__key/communityserver-components-postattachments/00-10-36-86-42/SQLNSharePoint_5F00_Frienemies.pptx
There is really no single set of best practices here. The best practice is usually what works best for a given organization. However, here are some important roles to consider: Administrator - The administrator should be able to support both the hardware and software involved as well as disaster recovery and some support (tier 3). This is sometimes split ...
Have run into this same issue many times. As an Admin, one of the ways I've tried to manage it is to make sure that every custom solution is packaged so that the packages can be deployed via stsadm (or PowerShell for future 2010 stuff). Also have also maintained that each solution should be created on a site that is in a site collection database of its own. ...
Before you explore options, you should consider your goals. I say this because each option provides a different level of coverage. You have one server now, but what happens a year or two down the road and you add servers into the farm? How will you back these servers up (or will you even need to)? What are your service level agreements (SLA) with the ...
Good question, the SharePoint solution framework helps manage many changes in a consistent, repeatable manner but doesn't cater for some farm level configuration such as search scopes, managed properties etc. To manage these types of changes I recommend scripting this configuration using stsadm and extensions such as the ones provided by Gary Lapointe. For ...
Its a broad topic, and easily one that could be split up in several questions... First and foremost (as Lori mentions also) solutions and features where applicable is a must if you want any degree of control with changes. As Lori also mentions, deploying these solutions should also be wrapped in scripts so that the API og stsadm usage is consistent (eg. not ...
There is a good description of the effects of the end of Mainstream support on MSDN Blogs. Summary Free support for Enterprise Agreements is over Don't expect any updates unless you paid for support last year and can prove it's a security vulnerability You must be on Service Pack 3 to receive extended support
If you follow the framework that should be used in SharePoint (items, features, packages etc) then you should be safe. Of course, using that framework you can replace out-of-the-box files, which is perfectly legit in some cases, but these files might get overwritten/restored by patching or it might cause side effects on other parts of the platform (it's up ...
To answer the question, the expected behaviour of SharePoint under memory stress is that page response times would increase dramatically as Windows tries to thrash memory pages to disk. Sending garbage back to the client is not what you would expect. These problems suggest something wrong with the server, but you talk about having this problem with several ...
Asside from logging on as them (which I do not recommend) you could create a test user and assign it the same permissions. I should mention that there are many good free screen sharing tools available now. One of them is SharedView by Microsoft. These will allow you to see the user's exact desktop as you talk with them.
Only top voted, non community-wiki answers of a minimum length are eligible