- Fix broken links after server migration how to#
- Fix broken links after server migration upgrade#
- Fix broken links after server migration free#
- Fix broken links after server migration windows#
Use Free broken link checker / dead links tools error404. The ‘My Documents’ folder now correctly maps to the users’ H: drive. With the help of Google Analytics, you can set up a custom report to track 404 errors from external links. Simply unticking the ‘Move the contents of Documents to the new location’ option resolves the issue. I selected this as I didn’t want users updating files on the old share, however, as ‘\\wsmdc01\home\username’ was no longer readable on the network, the Folder Redirection GPO was failing. One of the options when using the Microsoft File Server Migration Toolkit is to stop sharing the source file server shares once the files have been copied to the target file server. It turns out that the error is occurring because the ‘Move the contents of Documents to the new location’ setting is enabled in the Folder Redirection GPO below: The first error message isn’t too useful:īut the second message shows more promise: Still not enough information to take action really, but there are 2 cheeky errors showing in the ‘Policy Events Tab’: This gives us a clue, but we’ll keep looking. In this case, there is an exclamation mark next to ‘Component Status’ in the ‘Summary Tab’:
Fix broken links after server migration windows#
Here are the current settings for ‘GPO > User Configuration > Policies > Windows Settings > Folder Redirection > Documents’:īy Using the ‘Group Policy Results Wizard’ on an affected computer/user, we can troubleshoot this issue. The ‘Documents folder redirection’ GPO setting is not updating ‘My Documents’ to the new file server location. However, although the user home folders are correctly being mapped to the H: drive, by using this setting in user properties: or still work fine and are not broken) And like I told you in my post from last week - I found a way to repair those broken links by using the version history.I used the excellent Microsoft File Server Migration Toolkit to migrate files to our new file server on the weekend. And it only happens to internal links (other pages within Confluence and attached files). No, it just happens to links that were existing before the migration already. Otherwise, this operation cannot be customized. If desired, you can disable the automatic link updates when copying content. "If you create a new page with links and edit it, do the links break in the same way?" Yes, links in pages, lists, and libraries will be updated to reflect the new destination URL (though content will not be changed).
Restore Application Data and SQL-DB-Restore Backup of the complete "Application Data" Folder with subfolders. "What steps were taken to move the Confluence instance to the new server."ġ.
ORDER BY I'm sorry if my previous post was not clear. ) AS count FROM confluencedb.SPACES s INNER JOIN confluencedb.CONTENT c on s.SPACEID=c.SPACEID JOIN confluencedb.BODYCONTENT b ON c.CONTENTID=b.CONTENTID WHERE PREVVER is NULL AND b.BODY like '%%' This query shows also some not affected pages, but it makes life easier by finding pages out of hundreds. We also created a database query to find all affected pages. For fixing all links after database migration, I use this tool. The already destroyed links can be recovered manually by comparing the current pageversion with previous pages versions. After doing this, new pageupdates on old pages didn't destroyed old links anymore. All pages that was created before URL change in Version 6.5.1 lost their old links after saving.Īfter searching a bit longer for this issue I found this procedure with de-/reactivating Colaborative editing and restart indexing.
Fix broken links after server migration upgrade#
There is no issue any more.įirst we had Confluence 6.5.1, then we changed the URL which caused the problem as described and upgraded to 6.7.2.Īfter this upgrade to 6.7.2 the issue was still here. Thank you very much in I'm sorry if my previous post was not clear. The funny thing is that links that contain special characters like "&" or non-english special characters like "ö" work fine and are not affected by this issue.
Fix broken links after server migration how to#
Please tell me how to fix this bug on the whole confluence instance. I can't open every single page created within Confluence to save it and restore the prior version of it. Go to the version history and reproduce the prior version (before migration) Now the links somehow get repaired and it is possible to edit the page again without damaging the links.īut there must be an other option to fix this issue. Edit the page (don't do any change but just save the page to produce a new version)Ģ. I figured out that I can fix this behaviour by doing the following steps:ġ. (Even if I don't make any changes and just save the content after pressing the edit button the links on the page and all the links to the data which is attached to this page are broken.) I used the excellent Microsoft File Server Migration Toolkit to migrate files to our new file server on the weekend. But as soon as I started to edit an already existing page all the links on this page link to the page itself after releasing the page. Now I found a bug with the links within the page and a workaround which is not suitable for each site.Īfter migrating to the new server on the first view everything looked fine.
0 kommentar(er)
