I am delighted to write this post as I have achieved and learned quite a lot in the process of resolving a permissions issue. I had a strange requirement for one of my clients about restoring users and permissions deleted on site and document library level. There is only way to get around the issue is to restore the whole database, unless you have any third party tool in place to take care of the situation just to restore permissions. But as users have recently uploaded several year end reports, created several folders with lots permissions inheritance broken, which they were not prepared to lose. So restoring DB is out of scope. I was stuck in a strange situation on what to do. My initial thoughts were to restore the DB from the day before on the test server and export and import list permissions using Garry Lapointe’s export and import commands. But the issue was on the new folders created on live DB, when I try to import list security, all users were removed on new folders created on live. Then the option was to merge both the exported XML from live and test to overcome this new folder issue and restore permissions back to how it was before. Let’s start on how to: 1. First download Liquid XML tool, which is a handy tool to do most of your work. 2. Restore DB on your test server (I will not be covering on how to restore DB on SQL Server) 3. Run blow commands on the library where you would like the permissions removed, on both test and live servers. Continue reading
- Performing Physical environmental Checks
- Performing and Monitoring Backups
- Checking Disk Usage
- Checking the Event Viewer
- Monitoring Server Performance
- Monitoring Network Performance
- Archive Event Logs
- Check for Security Updates
- Review SLA Performance Figures
- Archive Data
- Environmental Tests
- Database Maintenance
- Security Checks
- Capacity Planning
- Disaster Recovery Test
As needed Tasks
- Full Security Audit
- Update Performance Baselines
- SharePoint Health Analyze
As part of my 2007 to 2013 migration project, I had to move my sites to separate content database (Within MOSS) and a web application. There are other blogs written about moving my site using STSADM mergecontentdb and all, it works absolutely fine but in some environments if there are any custom entries on web.config on your actual portal, where you are moving your my sites from, it could cause some weird .net errors.
Let’s start with the steps on moving my sites and then fixing the error, it’s just simple solution, but you will end up spending hours, hope this will help.
Note: Minimum of Service Pack 1 is required to work below solution.
1. Create a separate web application and name it MySiteshost and Wss_Content_MySites name to content database. Continue reading