Today I had a problem with a group of users that were trying to work with a very large PowerPoint file in SharePoint and didn’t realize until I downloaded a local copy of the file that it was too big to work with through Office Web Apps.
So I did some digging around to see if there was a way to possibly shrink the files, so I ended up finding something here:
In PowerPoint 2016 you can find the option here:
After doing a bit more digging, this actually applies to all Word, Excel, and PowerPoint versions from 2016 on down to even the Office 2010 versions.
So now I’d be curious if this could be automated somehow to do some major cleanup in PowerShell or something? Hmmm… maybe for another blog post later… hehehe.
Hope this helps if you need to free up some space in the future.
Recently I decided to jump into GitHub to share some of the scripts that I have used and created for my own benefit in order to see if this helps out any regular visitors of my blog as well.
You can check it out over at https://github.com/fentressbj
Going forward I will try to capture all of the relevant scripts that I have used over the years for configuration for building out different setups.
Of course if I use a script from another author I will absolutely try to provide credit. I think its dishonest not to do that if its not something you have written from scratch. If you take one and improve it or modify it, I think the original author should be given credit still. These days its extremely hard to be a content creator given some attitudes to share things without giving credit.
I hope this helps others and everyone enjoys my dive into learning more and more about GitHub.
Recently I was working on a migration of a couple of big sites moving them to their own content databases and it didn’t exactly turn out as I planned.
So more than anything, I wanted to use this post to describe what happened and mention some tips and other things that may help others out in the future if you ever run into trouble when trying to break out sites into their own databases.
Here are the major events that happened in the migration process:
- Created DB under central admin
- Used Move-SPSite to move one site from another content database
- Content stuck on Move-SPSite, never finished
- Restarted all servers
- When came back up, new destination database was in recovery
- Recovery process used all SQL resources, major slow down of farm (sad time)
- Looked into SQL logs to check status of recovery thinking new destination database would come back up
- Actually after recovery finished, I still had no access to content created in new content database
- Checked and under central admin checked site locks and quotas
- Turns out entire site still on old source DB
- Hadn’t been copied over, even though SQL showed a populated database
- Site lock had been switched on all the way to no access
- Users going to site would get a 403 forbidden message when trying to access
- Went under site locks and cleared the lock
- Once this was done, content access returned to normal
- Original content and under Central admin still said content was on source DB
- New destination content DB under still showed also that it contained no content
So in the end, the big lesson learned here was that even though I could check SQL and see that the new DB contained information, SharePoint hadn’t moved the site over to the new content database.
I did some research and there are timer jobs that run gradual site deletions, but I don’t think they applied here. Either that or I switched back to the original database before anything else was allowed to happen.
In the future, I may just use Backup-SPSite along with Restore-SPSite because that command also has the ability to specify a new database to put the site into when the backup is restored.
I hope these tips save you some time and headaches in the future.
I wanted to take some time and just thank everyone who came to hear me talk about SharePoint today at the Chattanooga Portals and Collaboration user group.
I really enjoyed the stories that we all shared and some of the ideas we threw around to get more people talking about SharePoint in our corner of the woods.
If you have any questions or would like to see this talk given again, let me know. I really did enjoy giving it and I hope I can tweak it a bit and give it to another group soon in the future.
You can find my slides at http://slidesha.re/1qqCc1L
I also have a set of links I will try to post here as well.
When SharePoint Server 2013 was first released, I was curious what new things I could do with it. I saw the new search capabilities, a different look and feel, a similar management interface, and several other BI things that made me happy. I then also realized that I support SharePoint Server and also the free version SharePoint Foundations. In SharePoint Foundations you get SOME of the things that makes SharePoint great (like Search for example), but with Foundations there are usually strings attached to that functionality.
In SharePoint, if you create your farm by clicking on all the defaults and using the wizards your databases look like this:
With SharePoint Foundations 2013, we don’t really have the option to create search by scripting with PowerShell… or do we?
Originally my research pointed me to Gary LaPointe’s blog here.
Which is great because this is in PowerShell and I can understand this, but it still doesn’t give us what we are wanting in the end like this:
Fortunately I found the following post by Jasjit Chopra’s blog here.
Finally!!! What we have been searching for all along! One thing to note at this time is that I have tried this myself on two different farm configurations (a three tier farm and a single box farm) and in both cases the search service and databases were created with the clean names and the service functions just fine.
I’m doing my happy dance now… enjoy!