What are /r/sharepoint's favorite Products & Services?

From 3.5 billion Reddit comments

If the original link does not work for you like it did for me you can find the video OP is referring to here.

You absolutely can.

https://powerbi.microsoft.com/en-us/documentation/powerbi-developer-integrate-tile/

https://powerbi.microsoft.com/en-us/documentation/powerbi-developer-overview-of-power-bi-rest-api/

You can either use the embed functionality which makes the report public, you can get tokens from PowerBI/OAuth service for the current user.

InfoPath is old hat and should be avoided at all costs.

A quick and easy solution would be to add a querystring parameter like: https://site.com/sitecollectionname/lists/listname/newitem.aspx?yourValueHere=2

On the newitem.aspx page in browser, edit it and drop in a script editor webpart with some javascript to pull from the url and use it to set the value on the form control. A sample method to get URL params can be found here

So in your script editor, you'd make a call like

var myvar = getURLParameter('yourValueHere');

Here is a Macro that will do this in onenote which is far better than a wiki page in sharepoint in my opinion, and every site already comes with a notebook.

https://getonetastic.com/macroland&id=01C7C254D45E462CB24B3246853B3032

Have you tried using the ServiceNow connector for Flow? It's both in preview and requires premium licensing - but wouldn't be overly complicated to connect the two.

It is unsupported to modify SharePoint's indexes in any way (or anything else in the SharePoint database, for that matter). See http://support.microsoft.com/kb/841057.

SharePoint also performs its own index optimization, so you shouldn't be running a maintenance plan that does so (see http://technet.microsoft.com/en-us/library/cc678870(office.12).aspx search for "index").

I'll be honest, we're pretty much using out of the box SharePoint with no customizations. The way we're structured makes doing everything client side with JQuery and CBS as our main tools the way to go. The most helpful new features were managed metadata and improved search. I personally was able to make great use of exporting the term store to XLIFF and sending them off for translation that way.

We were very close to eradicating content query until I revived them for the heroes/slider on the homepage and other pages. I'm really proud of that one even thought I think sliders are dumb. It's still some good code.

We decided not to use catalogs (due to many issues we had with them), standard top navigation (I put together the mega navigation). and machine translation.

My team talked about this more at [SPC].(http://channel9.msdn.com/Events/SharePoint-Conference/2014/SPC353)

Without spending a lot of cash, forms in SPO are super lacking. There is nothing, from Microsoft, to fill the void of InfoPath. I would work on moving away from it as you can already tell Microsoft forgot about it :)

There is a glimmer of hope that PowerApps will be the replacement. Still no official statement about that though :(

Have a look at Power Automate (fka Flows). It’s pretty far reaching and you can go fairly deep on it. That said there are a lot of templates there and you will probably find something there that fits your requirements.

Was able to find my answer, in case anybody was curious about this...

Office Web Apps Server only works with Sharepoint 2013 and other 2013 hosts (Exchange, Lync, ect...).

If you are on 2010 sharepoint, you will have to go with the Office Web Apps that gets installed on every one of your sharepoint servers.

source: http://technet.microsoft.com/en-us/library/jj219435.aspx

http://technet.microsoft.com/en-us/library/ff607933(v=office.14).aspx

Set-SPTopologyServiceApplicationProxy [-Identity] <SPTopologyWebServiceProxyPipeBind> -BadListPeriod <String> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<SwitchParameter>]] [-WhatIf [<SwitchParameter>]]

I haven't tried it personally, but it's definitely the sister cmdlet to the "Get" version. :)

It's SharePoint! Programmatically query the site statistics via spsite.usageinfo!

http://msdn.microsoft.com/en-us/library/microsoft.sharepoint.spsite.usageinfo(v=office.14).aspx

(Or, give them a link to the analytics reports for the specified page: http://technet.microsoft.com/en-us/library/gg266383(v=office.14).aspx)

Um what I meant was "Downloading this tool called SharePoint Designer 2013 (SPD) https://www.microsoft.com/en-us/download/details.aspx?id=35491" and use it with your SharePoint Online site.

SPD 2013 can be used for both Online and On-prem even though its name is 2013.

You'll basically either have to do what tsears suggested for documents, or use Export-SPWeb/Import-SPWeb and just don't include user security.

http://technet.microsoft.com/en-us/library/ee428301(v=office.14).aspx

On the blog, where it says Creating the Chart... in that block, note these values: colors: ['#339933', '#903b3b', '#583596', '#447088', '#5a7952', '#838843']

Change them there hex values to what you want.

https://color.adobe.com/explore/?filter=most-popular&amp;time=month

Dan Holme has some great installation vids/explanations out there... first one i could find off the cuff: http://channel9.msdn.com/Events/SharePoint-Conference/2012/SPC083

But basically the installation account is going to get woven into alot of things that would be a nightmare to change (if possible) after the fact. ie you dont want this to be a user account unless they are a robot owned by the organization.

I too get the security auditing concerns, but everything those concepts are based on and those policy writers were taught know nothing of the Sharepoint-SQL(and AD[DCs]/Exchange for that matter) inner-workings/complexities when it comes to service accounts.

most do not need local login, again there are some great vids/breakdowns on which need what permissions, i.e. http://technet.microsoft.com/en-us/library/cc263445(v=office.15).aspx

http://jqueryui.com/tabs/

You have to wrap your web parts with divs that have an id that matches the links that call them. I also had to apply a float and width 100% to the ul container of the links to get it to look right inside of sharepoint.

I've used Google Charts in the past. Also if you don't want to code a solution, Amrein has some really helpful webparts for cheap. I think either of these solutions plus some CSS to make things pretty will get you want you need.

The best way is to use the Power BI desktop.

https://powerbi.microsoft.com/en-us/blog/publishing-oracle-data-to-power-bi-with-data-refresh/

Since PowerBI caches the data, you need to configure schedule refresh as well as a data gateway so the cloud can see your on-premises OracleDB.

You can embed PowerBI to sharepoint with a bit of javascript, the auth part is the most annoying, but with SPO SPFx there'll be a PowerBI webpart "soon"

I will try to answer you question, but there is no quick answer.

I have a decade and half experience in SharePoint intranets. Those department sites have been present in all company intranets I created/maintained. They are usually managed following guidelines like the ones that can be seen here:

https://docs.microsoft.com/en-us/sharepoint/governance-overview

As for the workflows that you mentioned, not all companies follow the same procedures. You need to define first what kind of approval processes do you need. Examples can be seen here:

https://flow.microsoft.com/en-us/templates/

You might need other sites, it depends on the departments/teams present in your company.

I do not know if those sites will suit your company needs. I would require more information about how your company functions before I could answer to that.

I do not know either if those departments would suffice to help your company grow up to 200 employees. I have never run a software company. You might need to post this particular question in other sub, if it is a question, I mean.

If you need more information or clarification of any of the points above you can PM me.

Edit:typos

Yes. You will need a per user or per app license to do so. It can be accomplished with a rest api call or an action called "Call child Flow". Call child flow action is only available on PowerPlatform solutions. Some references:

https://flow.microsoft.com/en-us/blog/call-flow-restapi/ https://docs.microsoft.com/en-us/power-automate/create-child-flows

The documentation has an example of an approval workflow, though it's very, very basic, and it seems to me that the author of that doc hasn't actually built workflows in SharePoint, as the end result is an email, not an approved doc.

One of the big changes in 2013 workflow was the addition of state machine workflow, ie, the ability to go to different stages based on a condition. This was possible in 2010, but only through complicated workarounds. And, it seems like we're back in that territory for flow, as flow doesn't support state machine workflows. But if you don't need anything too complicated, perhaps the above doc will help, you'd likely just need to modify it to update the doc to set the approval status in addition to sending the approval email.

UPSS no longer exists and Connection Filters cannot be used. If you use AD Import, you can implement LDAP filters instead. The other option, and the direct replacement for UPSS, is using MIM Synchronization.

Depends on if you're going to 2013 or 2010, but if you're doing 2010: http://www.harbar.net/articles/sp2010ups.aspx

It's just a tremendous thing to understand, and can save potential headaches.

Also, microsoft has provided several step-by-step articles: http://technet.microsoft.com/en-us/sharepoint/ee518643.aspx

My last 2010 install used 8 service accounts: Super Reader, Super User, User profile, content, Search, service apps, Web App, Farm.

Sharepoint 2013 requires at least 24GB of RAM when using all services, especially the search service application which uses most of the memory. Also, if you are running it on a VM, dynamic memory is not supported because of the distributed cache service.

It sounds like you want to perform a database attach upgrade. Essentially, that means that you build the new farm, create a copy of the content database from the old farm on the new one, attach the content database, and allow SharePoint to perform the upgrade process.

http://technet.microsoft.com/en-us/library/cc263299.aspx

Start at the source. Technet has some good resources. As the others have stated, there is a lot that you can and may be required to do. Understanding the basics is a great first place to start.

First, have you found this:

http://technet.microsoft.com/en-us/library/gg502595%28v=office.14%29.aspx

Also, at the above, be sure to find the link titled "Search Architectures for Microsoft SharePoint Server 2010". It's a poster that shows different sample search architectures, along with explanations.

edit: oh, and make sure your hardware is at the recommended level. I keep running into admins that are running sharepoint with hardware below the minimum...

2013 is super easy.

You just run a few powershell comands, run setup.exe, run a few more powershell commands, and you're set.

Deploy Office Web Apps Server http://technet.microsoft.com/en-us/library/jj219455.aspx#scenario1

Configure SharePoint 2013 to use Office Web Apps http://technet.microsoft.com/en-us/library/ff431687.aspx

from the sounds of it, you probably want to do a content db restore. You could do a backup from your existing server and restore to the new server assuming SP2007 has been setup on the new server.

http://technet.microsoft.com/en-us/library/cc263037(v=office.12).aspx

Agree with i_had_fun. The pickings are seriously lacking from third-party publishers on the subject. I've been setting up a test environment and using the Technet documentation at http://technet.microsoft.com/en-us/sharepoint/fp142366.aspx.

It is odd not to see lots of third-party stuff out there yet. Usually MSoft back-office products have lots of publishers with materials before the final product is rolled out.

Another shot in the dark here, but a couple ideas:

1. Permissions for Central Administration are not the same as the SP sites everybody uses. Perhaps you need to grant yourself permission as a SP Farm admin?

2. Have you configured Kerberos? Most advanced features of SP require Kerberos to be configured. It is a bit of a long process but SP relies heavily on it so you may take a look there as well, especially if you're using any advanced BI features. Note: Here's a Technet article to get you acquainted with the Kerberos technology.

My first recommendation to all SharePoint admins is to read this documentation: Plan for administrative and service accounts in SharePoint 2013

I have worked on so many problematic and broken farms because of misunderstandings or lack of knowledge about security and service accounts.

Then, like some has already suggested, install a full farm of your own, don't start the farm wizard but rather create service applications on your own so you figure out how it's all connected.

And learn about the different logical components of SharePoint and how they work together. For example:

• Config database
• Content databases
• Service application databases
• IIS web sites
• SharePoint root (14/15 hive), i.e. SharePoint related files stored on every server in the farm
• Virtual IIS folders and their connection to the SP root
• Config file hierarchy (machine.config/web.config etc)
• GAC
• Local security groups (WSS_WPG etc)
• Windows Services

> Ideally, I don't want Sharepoint storing any documents in a database

You dont have to (although there are performance benefits to storing small files in the CDB. I think this might make a bit more sense: http://technet.microsoft.com/en-us/library/ee748638.aspx

In terms of visualizing the files, you can maintain that same folder based approach to storage (although its not suggested). Worst case scenario you use Explorer view (WebDAV).

The biggest thing to wrap your head around and get the users to realize that a folder structure is really unsuitable to large scale collaboration. Unless someone is managing it, chances are it will spiral out of control eventually.

Recommended Read: http://www.amazon.com/Practical-SharePoint-2010-Information-Architecture/dp/1430241764/ref=la_B007JLODZQ_1_1?ie=UTF8&amp;qid=1355988105&amp;sr=1-1

If you have access to System Center Virtual Machine Manager (SCVMM) I would try a p2v. That's the only way I can think of to truly mirror your environment. Just "copy" the SharePoint, SQL Server and a DC. If your machines are already virtual you can simply clone them of course.

This is not the best solution in all cases. If you want to make sure you operate in the "real world" environment it is. Reason to not do this would be a huge environment. It can be difficult to strip that down. In that case rebuilding the farm as accurately as possible can be the better solution.

http://technet.microsoft.com/en-us/library/cc764232.aspx

The UPA doesn't update the UIL directly. That relies on the SharePoint Quick and Full Sync timer jobs (which punts information from the UPA to the UILs).

Sometimes this stops working properly, so you can run:

stsadm -o sync -listcontentdatabases 0

This shows when the last time the UIL has been updated by the sync sweep job.

stsadm -o sync -deletecontentdatabases 0

This deletes the history. Once this is run, re-run the User Profile Service SharePoint Full Sync timer job.

http://technet.microsoft.com/en-us/library/cc263196(v=office.12).aspx

Follow this process: http://technet.microsoft.com/en-us/library/cc263299(v=office.14).aspx

You're just performing a database attach-upgrade. You can do this at any point during the lifecycle of the SharePoint farm.

> Create a snapshot of each server in case something goes wrong. If you’re running a hardware setup, be sure to backup your system to an image file or use whatever your preferred backup software in case something doesn’t work out correctly.

My understanding is that you're going to have a bad time if you try to restore a farm by reinstating snapshots. See here.

> Do not use the Hyper-V snapshot feature on virtual servers that are connected to a SharePoint Products and Technologies server farm. This is because the timer services and the search applications might become unsynchronized during the snapshot process and once the snapshot is finished, errors or inconsistencies can arise. Detach any server from the farm before taking a snapshot of that server.

I'm using rclone on a linux machine to backup files from onedrive/sharepoint : rclone

&#x200B;

Edit : I use it for Syncing the files, not downloading the whole archive again and again.

http://channel9.msdn.com/

What's New for IT Professionals in SharePoint Server 2016 10:00AM to 11:15AM

In this session, we have a lot of new information for admins, sharing what's new and coming in the next on-premises version of SharePoint - SharePoint Server 2016 - with insights on hybrid, too. More detailed information to be posted as we get close to Ignite.

Use Client Side Rendering with the default list form. This will let you override the rendering of each control before it's rendered, specify custom validation, what to do when the control is initialized and how to retrieve/format the value. And it's not like you're messing with the default form web part itself - just remove your CEWP or clear the jslink property to restore it.

You can also override form layout to an extent (note this doesn't work well with some field types).

Our homepage has three columns in a 25-50-25% format. Left column is important links and quick-view of the company calendar. Center column is "news" that is a CQWP that grabs all of the sub-sites news and compiles them in one page. Right column is a search box and &quot;current weather&quot; widget.

You are never to touch the production SQL databases for Sharepoint (not even use a simple readonly query against it) but it is nice to know how the tables and databases are constructed so using your SQL skills on dev/test databases can only make you a better admin (or a better destroyer of Sharepoint farms).

There are some SQL jobs that are not optimized for Sharepoint which you would have to create or modify to get the most out of your Sharepoint. I haven´t looked into that much as I have the luxury of a SQL admin but this is something that a MPFE told me.

http://technet.microsoft.com/en-us/library/hh292622.aspx is a nice place to start.

Yeah, I noticed this as well. It seems you can have your config and content db's be "out of sync" with the bits installed on your farm. I wouldn't run it like this for a while (more than few hours or so), but it helps keep downtime minimal. The configuration wizard will still take down your sites as the databases are updated sequentially (it also has a nifty completion percentage, so you don't have to monitor Update.log).

So, yes, you still have to run the config wizard. It works very similarly to MOSS 2007, but you really should read this article to make sure you don't mess anything up - http://technet.microsoft.com/en-us/library/ff806338

well there is a document conversion feature that will convert word documents to pages (similar to wikis) in sharepoint 2010 with the enterprise license.

alternatively you can install open office on the computers that don't have office. you won't have any integration with sharepoint but at least you will be able to open up docs.

Office webapps is payable and quite expensive

In earlier version of SharePoint, you had your general SharePoint sites you would set up for teams, projects, and what not. But also, each user would have their own personal SharePoint site called a "My Site." Over time, this My Site evolved into what they now call OneDrive. So everyone's OneDrive is actually a SharePoint site on the back end, and that's why you see alot of confusing crossover between the two services.

That answers that question, and overall Office 365 is a bit confusing to try to understand how everything works together. If FastTrack isn't an option, I highly highly recommend getting a consultant or freelancer (upwork.com, freelancer.com, etc) to sit down with you for a couple hours. The few hundred bucks you may spend is well worth the man hours you will end up spending doing your own research and possibly doing something very wrong in your tenant.

For sure

Upwork.com is the best place to find freelancers for on-demand help. Well, not always help at the drop of a hat, but definitely in a reasonable amount of time.

You would probably get anywhere between 20-30 applicants. You can mark your job as "US Only," if that is required at your company. If you're not in the US, about half of the job postings are outside the US (to give you an idea of how international the site is).

The prompt depends though, you can get a pretty accurate location from the IP, which does not require any prompt, like so for example (using ipinfo.io):

$.get("https://ipinfo.io", function(response) { console.dir(response); }, "jsonp");

If OP wants news targeting based on the user's office ( eg. New York/Tokyo/Paris), that should be sufficient in most cases.

I had to find something for the same amount of images. I'm the SharePoint guy at work but I could not find anything that would make it user friendly.

There is a lot of info in the exif data and I wanted something that could use that.

In the end I went with http://daminion.net/

This is a stand alone client-server image library with lots of metadata options.

We have tried BitTitan, Mover.io, Sharegate...each of the descriptions of each talk about how they move libraries and files, and some refer to what they don't do, others don't mention their weaknesses. I have not checked out Avepoint or Metalogix yet. I'll see what those give us.

I think I get you. You want to use Azure AD to link together the multiple instances of O365. http://azure.microsoft.com/en-us/services/active-directory/

If anything can do it, it's Azure AD. Good luck!

I'm mostly familiar with Online. I *believe* that if you want to do something that like you are going to need to make a workflow with Designer. At this point, it is a free download: https://www.microsoft.com/en-us/download/details.aspx?id=35491

I don't know much about it but there are plenty of people here that should be able to help! Good luck!

I'm in the same boat as you and have been using Notepad++ as my editor. Jslint / jshint works for reviewing code formatting, it doesn't fix bad code but it does help.

This book helped get my feet under me: https://www.amazon.com/Custom-SharePoint-Solutions-HTML-JavaScript/dp/1484205456

This is a question that only have one answer - It depends! I can recommend you to take a look at my SharePoint Conference session where I discuss this based on my experience: http://channel9.msdn.com/Events/SharePoint-Conference/2014/SPC334

~~I had heard... somewhere, that things would improve on the Office 365 side with their current "change and break production" approach. But I have forgotten where I heard this. May be it was a dream.~~

No, not a dream. Office 365 Change Management processes announced at SPC289.

http://channel9.msdn.com/Events/SharePoint-Conference/2014/SPC289

Chris O'Brien details how it will work.

http://www.sharepointnutsandbolts.com/2014/03/Office-365-first-release-and-nda-preview.html

heh, wurd... i might actually play with that next time I'm on a dev tool box, ill post back if i do. sidenote/follow-up:

Simple blog on shitty work around (recreating all the views)

Changing the created date on the sql db that manages the views (ie the thing people shouldnt mess with)

Oh, BTW, might be able to/could just Stick a Content Editor Web Part or a [connected] Filter Part above it with the view links/simple filter options to supplement the shortfall, although the remake the views in order workaround is horrible per se...

You might want to use a combo of SharePoint and PowerApps. There is an Onboarding Template you can start with. https://powerapps.microsoft.com/en-us/blog/office-template-onboarding-tasks-now-available/

Take a look into Common Data Service

The Microsoft alternative is PowerApps. There is an on premises version of the product. It is not only a replacement for Infopath, but will allow you to develop all types of browser/mobile applications to interface with SharePoint. The simplest version of which is a form that will fill out a list in a SharePoint library. It features a lot of drag and drop features as well as automatic population of fields from your custom list. You can learn more about it at https://powerapps.microsoft.com/en-us/

SharePoint Vagabond - Microsoft Premier Field Engineer

this can be done using any of the google charts or highcharts - $590 for 1 dev.

you can set it up in SP designer creating empty data view webparts connecting it to the desired list and sticking jquery on top.

I did it long time ago will try to search my old files. edit: pricing

Highcharts is the best one out there, but you would have to use ECMAScript to get the data from the list and javascript/jquery to build the object used in rendering. I have no experience with Fusion, but my experience with Bamboo is that it is very limited.

Sounds like you're just getting started with Javascript. It's important to understand how Javascript works with HTML and CSS. When it comes to interacting with SharePoint using JavaScript you have 2 options. CSOM or REST. In my honest opinion REST is easier to learn and will help you moving forward

• Here are some examples of using REST and jQuery to add,update,delete items in SharePoint. https://social.technet.microsoft.com/wiki/contents/articles/31995.sharepoint-2013-working-with-rest-api-using-jquery-ajax.aspx

• the "Content Editor" web part will be your friend. This will allow you to add HTML, CSS, and Javascript to any page. You can also add a reference to jquery from here using

  <script src="yoursiteurl/SiteAssets/js/jquery-1.10.2.js"></script>

• You can use ChartJS for graphs. It's free and looks pretty nice. To summarize, you'll need to use REST to get data, simple javascript to transform that data, simple javascript to render the chart. http://www.chartjs.org/

Pretty much every list is exposed as a webservice. Pick your visualization package and render the data.

http://blogs.technet.com/b/fromthefield/archive/2013/09/05/working-with-sharepoint-list-data-odata-rest-and-javascript.aspx

Ive used http://www.chartjs.org/ before.

>I'm totally green and landed in this gig by happenstance.

Well, I guess braindead hiring practices are the real culprit here then.

Anyway, get started by reading this site: https://developers.google.com/chrome-developer-tools/

Let's break it down...

Part 1: The initial column setup (MyNewFormLink) creates a calculated column that provides a link to "NewForm.aspx?ClientVal=" + whatever the title of the list item you wish to provide. The point of this is to inject a parameter for you to use in Part 2.

Part 2: The tutorial instructs you to use a Content Editor Web Part to put HTML (and more specifically, Javascript) directly into the page. What it fails to mention is what the point of the first line is. >01 <script type="text/javascript" src="../../Javascript/jquery-1.3.2.min.js"></script>

This tells the webpage to pull in a library of functions for use known as jQuery. jQuery allows us to manipulate the webpage (or DOM) dynamically in Javascript shorthand. You will need to download jQuery and store the jquery*.min.js where SharePoint can access it and provide an appropriate src URL. Now to the actual code...

>Lines 03 & 27-37

The init_fields() function is executed first, and it seeks to locate the form's input fields for reference later.

>Lines 05 & 14-25

The getQueryParameters() is executed second, it checks the URL of the current page and pulls out any parameters.

>Lines 08-11

This specifically defines what data we wish to provide where. It checks if a ClientVal was provided in the URL, if so it searches to see if there is a "Title" field and then supplies the value accordingly.

Let me know if you need further elaboration.

This is not true according to these statements Jeff Teper made on SPYam ~1,5 years ago:

>Our approach is to continue to update our servers on our traditional cadence. We want to be clear the best experience comes through the cloud as customers will see many new Office 365 features this year. We committed to an on-premises release in 2015. We don't talk about N + 2 releases. We'll listen, learn and adapt to customers, partners and whaat is going on the market for the scope and timing of the next release but if you asked us today, we'd expect our general approach (cloud first/best, solid server upgrade) would stay consistent change in that timeframe.

And:

>“I don’t know how to say this more clearly. We plan to do future server releases. We committed to a timeframe for the next one. We never have communicated or contemplated that it’s the last one, and I’d ask you guys [to] help correct people who might make that up. Just we’re not getting ahead of ourselves and talking about plans, we’ve not made yet for n + 2, which we’ve never done in the history of the product.”

Source: https://www.yammer.com/spyam/#/Threads/show?threadId=332797011

My favorite places are Reddit, SharePoint Community, and O365 Technical Network on Yammer. I use Twitter, too, but you need a list of people for that.

You can create them using the free power bi desktop, link below.

Then you host the report in power bi service (office 365)

Then you integrate the reports with SharePoint pages. Not hosted in SharePoint, just presented.

https://powerbi.microsoft.com/en-us/desktop/

You didn't mention what SharePoint environment you have. You can do this with a document template if you have SharePoint Online and Flow. It may be exponentially more difficult on existing documents.

https://flow.microsoft.com/en-us/blog/generate-word-documents-in-your-flows/

No problem.

I'd also look into the new site layouts, there are some that are "Modern UI", like Communication and Group sites, and they are better in terms of performance, responsiveness and are generally where MS channels most of their new functionality. You could create an Office 365 group to have a look at it?

These also support the new development framework (SPFx), and if you f.ex. need an image rotator with some bells and whistles there are quite a few available from Github (requires npm/gulp to compile and deploy).

The only issue would be that 90% of the videos you find are made on classic sites, but that is bound to change as Modern UI increases in popularity.

In the same vein, you might want to look at Flow rather than SP Workflows for automation needs, these are much easier for an absolute beginner and also lets you tie in other systems.

top def isnt... you can tell because they have a packaged solution file for you to deploy (cant do that in o365).

if you are unable to do that you can get pretty far using the first half of that option (manaaged navigation) then just bumping the nav limit in the OOTB master page and do alot of CSS/JS hackery.

if you want a more comprehensive resource to that era i would suggest https://www.amazon.com/SharePoint-2013-Branding-Interface-Design/dp/1118495675/

I like http://www.barnesandnoble.com/mobile/p/javascript-and-jquery-jon-duckett/1119294449/2672716616875

There is another/similar/companion book on html/css.

Beyond books you wanna start digging around here: http://dev.office.com/patterns-and-practices

Is this a modern site collection, or classic that had been migrated from on prem in the past? If you go to library settings/advanced settings, scroll to the bottom and change the list experience to Classic Experience. Does this work? Do any of the files in your library have no file extension? Open with explorer (in IE) or map as a network drive and see if the files are visible any if any are missing an extension. If you can't do that, list them with Power Automate and see if this is the case. If none of this resolves your issue, I would create a new library and use PowerAutomate to copy all your files to the new library, then delete the old one and call it a day. Alternatively, you could use a migration tool like ShareGate or Microsoft's free offering, Mover.io to accomplish this.

content deployment is best for something like a pubic website. You have your internal farm with the authoring site, and on a schedule, it pushes the content out to a publicly accessible farm. The public farm is read only.

It should work for your situation, sounds like you have an admin site, and multiple client sites that need the content. The client sites are read only for the admin content.

Content deployment is site-collection wide though. You can't push to just one sub-site on all your clients, it would have to be it's own whole site collection at your admin side and the client side. Content deployment pushes everything. Content types, settings, lists, sites etc. It also has to have matching features. any features you have on your admin side also need to be deployed to the client side.

http://technet.microsoft.com/en-us/library/ee721058(v=office.14).aspx

if you can setup your client's 'admin' sites as their own site collection, this can work well for you. You can setup managed paths so that your client admin site copy is something like "http://client/adminSite" or something like that. The URL looks normal, but it's actually an entirely different site collection.

The content deployment destination sites do not HAVE to be read only, but if they aren't, expect to have problems when someone changes something on the destination and the source tries to push an update to it. I wouldn't recommend making changes to the destination site.

For the service applications it largely depends on what/how they are being used. Its possible you could simply start from scratch for 80% of them.

Each service app basically has its own database, 2013 has ~24 in total.

http://technet.microsoft.com/en-us/library/ee617150.aspx

I'm glad that this helped.

Here's the source of the information - http://technet.microsoft.com/en-us/library/ff431685.aspx; specifically the bullet points "On-premises in Microsoft SharePoint Foundation 2010 or Microsoft SharePoint Server 2010" and "On-premises in Office 2013".

Unfortunately, you'll probably wind up having to track down your LAR (Large Account Reseller) that you purchase your Microsoft products through, and get access to the Volume Licensing site to really figure out what you own and what you don't. Feel free to message me directly if you need some assistance with this; I have contacts in most of the LARS out there so I may be able to help you track this down.

Good luck. There are a lot of considerations, so it's hard to sum up anything in a short post. But perhaps start here:

http://technet.microsoft.com/en-us/library/cc789336(v=office.14).aspx

But, to try to summarize it just a bit. First, don't worry about sites/site collections to begin with, start with documents/data:

1. come up with a list of different types of documents that folks need to work with. (yes, creating an exhaustive list is a huge project, but start with a few).

2. Figure out who needs to have edit permission to those docs, and who needs to have read permission.

3. Figure out what folks do with the docs, and what the relationships are between different docs.

4. Using this info, figure out what libraries you will need to support all of the above.

5. Once you have the libraries figured out, then figure out how to structure the libraries into sites

6. Then, figure out how to structure the sites into site collections.

7. Make sure the above design doesn't exceed system boundaries, such as database size.

Quick example: you mentioned case studies. Who needs access to them? Do folks have access to all case studies? Or just some? What's the relationship between case studies and other types of docs?

Perhaps a few people create them, and everyone else needs read access. Then having one library that holds all of them might be perfectly appropriate. But, perhaps different groups create case studies and each group has their own approval process. In that case, perhaps a different library for each group (perhaps in different sites). And, perhaps a workflow to send finished case studies to a library for consumption.

Also, TechNet has some good guidance for the sizing of an OWA environment. If you're dealing with a relatively small amount of users and documents, you can probably just reuse an existing SharePoint server in your farm; however in some circumstances you'll need to add additional servers to your farm to handle the load. http://technet.microsoft.com/en-us/library/ff431682(v=office.14).aspx#bkmk_server_dist and http://www.microsoft.com/en-us/download/details.aspx?id=12768 (Office Web Apps Capacity Planning document). Certain Office Web Apps features are more taxing on servers than others.

This is probably your best resource: http://technet.microsoft.com/en-us/sharepoint/ee441229.aspx

I would start with the "Getting started with enterprise search in SharePoint 2010 Products" document.

Actually restoring the Config DBs from a backup will likely put you in an unsupported state - see 3rd bullet point from Considerations: http://technet.microsoft.com/en-us/library/ee428316(v=office.14).aspx I'd rebuilt the farm and move over the content DBs only, as blazaiev mentioned.

I'm going to search and find some documentation to support that, simply because we have some smaller departments that we can push that concept on. It would allow us to cut down on our physical file servers when they hit end of life. Do you know where you read that from Microsoft?

When I was first researching this concept, I came across this article that sort of turned me off to the idea: http://technet.microsoft.com/en-us/library/dd163523.aspx

Except for when you need to access you stuff through Https (a must for me, I would never setup SharePoint through Http).

These are a lot of questions to answer on Reddit... you might yield better results on some tech forum with a proper reward system :)

Anyway, just try googling any of this stuff (like "SharePoint term set", the first hit is this great article) and you'll often get the Microsoft help pages for each topics among the first hits. Those are usually pretty descriptive.

I'd run the PreUpgrade Checker...

http://technet.microsoft.com/en-us/library/cc262231.aspx

The report that comes out the other side will tell you two things, first, how clean of an admin you are. Secondly, what challenges you're going to face.

Mainly, things like Ghosted Pages, Orphaned Solutions, Missing Librarys, etc.

From here, spin up a new 2010 farm, do an Database-Attach/Upgrade. there are several ways to upgrade from 7 to 10, I recommend the Database-Attach/Upgrade for a couple of reasons. Its the only supported path to get from 10 to 13 and it leaves your old system operating.

http://technet.microsoft.com/en-us/library/cc262483.aspx

Maybe you already solved it, but I believe Get-SPDatabase + Delete() might be your solution.

EDIT: I've had exactly your problems, in my case the databases didn't show up in "Get-SPContentDatabase" after they were orphaned, I'd have to resort to Get-SPDatabase.

This is the expected behavior. There are a few different kinds of refiners and one of the default ones is the "Site" refiner, it usually shows up with the "Author" and a few others. What you have to remember is that in SharePoint nomenclature "Site" means "Site Collection" not sub site.

Since this is a default managed property I'm not sure that you can modify it in the way you're looking to. If you're really using FAST you could probably create a new managed property and add it to the refiner panel. You can do this with PowerShell, you would have to find a descriptive property like "Title" on the web to use and configure it as a deep refiner. Depending on the number of sub sites it can affect query performance though.. Check out http://technet.microsoft.com/en-us/library/gg193929(v=office.14).aspx for more info.

I think I answered my own question. It appears that SharePoint 2010 uses "Classic" authentication and SharePoint 2013 uses Claims Based authentication and there is a process you MUST do in order to transfer to Claims Based authentication. The upgrade process didn't make this clear (or I totally missed it) so I'll link the two different ways to upgrade this.

Being that my SharePoint production server is live, I'm not going to muck around with its authentication. I can't change it to claims based and then export the database so I'm going to use the method provided here.

There is another method to perform the authentication changes before you begin the upgrade and that method is here.

I'll report back when I attempt this to let you guys know if it worked for me.

UPDATE It worked for me. I just upgraded my permissions on my production setup to client based auth and re-exported the SQL database. No problems with permissions after spinning up the 2013 web application this time around.

This link can show you some of the new features in 2010 http://technet.microsoft.com/en-us/sharepoint/ee518670.aspx We actually started with 2010 Server . The company had already purchased it before I was even hired. Our Director mentioned it one day and asked if anyone woudl want to take ownership of the SharePoint project and I volunteered. I spent a good year and half reading, studying, testing VMs and took a SharePoint admin virtual class

We havent done full implementation yet and only have a few departments (out of 50 depts) that are currentl testing out some of the features. I am sure there are others on this forum that could offer some advice for you on upgrading to 2010.

http://technet.microsoft.com/en-us/library/ee748653.aspx

http://nikspatel.wordpress.com/2010/08/13/all-you-need-to-know-about-the-access-services-2010/

This should at least help get you started moving in a good direction.

I am not the only one... I am also learning Project server at the same time... I feel your pains on this one. Check out this link http://technet.microsoft.com/en-us/library/dd857479(v=office.12).aspx

It took me 5 days to find this.

I am not familiar with whether there are specific HIPPA/FISMA requirements, but from a software and technology standpoint there aren't major security risks for allowing anonymous access. The risk is in "dumb administrator" moves like having the default security setting allow anonymous access and forgetting to disable it on a new, sensitive site.

I looked into this in-depth in preparation for enabling extranet access on my intranet SharePoint deployment. Info here and here helped me with the steps necessary to do so safely. I've personally tried a variety of attacks and exploits, and have been impressed at how secure everything is.

LOL, has more to do with market scarcity here but wife does do Technical Recruiting sooo. These days its a bit harder unless I take a position downgrade which I may do for pure cash (titles are weird)

LinkedIn Premium is totally worth it because of how it boosts up your search relevance heavily. There was a period where if you googled SharePoint in North America I came up on the first page.

Wanna move up to Canada? https://www.linkedin.com/jobs2/view/57790961

My reasoning for not selecting multiple choice was so that it only included your largest farm version (in my case 2016), and not decommissioned or inactive/Pre-Production farms and that when a situation where you do administer multiple versions, be it a different job or simply your company has two versions running, you can explain why this may be (if you wish)

My reasoning behind doing this poll is to gauge what versions are actively being administered and to begin a discussion as to why we’re using the version/s we are, and what we may have planned in the future

I have created a New Poll if you’d like a multiple select version

Unless your site admins have heavily customised the design, the easiest way to know the version is just by looking at the UI: http://serverfault.com/questions/212107/how-can-i-tell-what-version-of-sharepoint-a-site-is-using-from-the-outside

Bindtuning.com is great. Makes branding pretty darn simple.

The patterns and practices group at Microsoft last week at ignite said its ok to use custom master pages in O365, you just have to be ok with making tweaks every month if something changes. Classic cost vs benefits.

Source: http://channel9.msdn.com/events/ignite/2015/brk4111

learning react should be separate from understanding the SharePoint Framework.

Simply go over the react tutorial: https://reactjs.org/tutorial/tutorial.html

Then learn the areas to apply react based on the SharePoint Framwork tutorial:

https://docs.microsoft.com/en-us/sharepoint/dev/spfx/web-parts/get-started/use-fabric-react-components

That should give you everything you need

The application pool will be for the search admin web site -- I'm not sure how you didn't have one automatically provisioned?

It sounds like you'll want to recreate and follow this guide to the letter. If you have the flexibility to do that (and you should) it will save you a lot of unnecessary troubleshooting headaches.

Hello, please look at this page, and locate a section of Software requirements / minimum requirements, and in the table locate the row "Single server with built-in database": http://technet.microsoft.com/en-us/library/cc262485.aspx

Basically, for single server install you do not need to have a separate installation of SQL server, SharePoint 2010 will use Windows Server's 2008 internal database. But of course this will be limited to 4 GB and some other limitations

I think this is the Excel web services update. If you are using SharePoint Server 2010 (not just Foundation), then I would install this as well, even if you are not using and do not plan to use Excel Services.

I am curious where you are going for patches. I normally use the SharePoint 2010 Update Center: http://technet.microsoft.com/en-us/sharepoint/ff800847.aspx

If not there, then the Update Center for Office. http://technet.microsoft.com/en-US/office/ee748587.aspx

I would get on a good cycle of applying CUs (cumulative updates, think mini Service Packs) in a timely manner (don't be more than 2 CUs behind). Don't install other SharePoint hotfixes unless it pertains to your exact problem. A CU doesn't ask you which components you want to patch, it gets them all. That's why I am a little curious why you have an update file for an individual service.

I found this and this I'm thinking migrating the site is what we want because it sounds like that will allow us to take our production.intranet.com and move it to development.intranet.com Or will that change our production site?

meestajason has some great points. one of them is that implementation is the easiest part. i'd add that, in addition to support/troubleshooting, design for large installs is "expert-level" material.

go for it. become an expert. in addition to getting the most important experience of serving clients:

1. read every forum you can where people are troubleshooting
2. invest in your own personal SP, that you depend on and use often (consider AWS, since Azure VMs aren't production-ready yet)
3. play with these: http://technet.microsoft.com/en-us/virtuallabs/bb512933
4. make a hyper-v server and lab at home