SharePoint 2016: New site contents experience
I though of you showing all new site content which is going to come up in SharePoint 2016, below is the new look :)
Saturday, June 18, 2016
New features in SharePoint 2016
I am listing down some of the import new features for SharePoint 2016, i believe you find this interesting, all the references are from MSDN
·
Fast site collection creation using PowerShell command
"SPSiteMaster"
·
SharePoint Server 2016 Central Administration is now provisioned
on the first server in a farm by default when using the SharePoint Products
Configuration Wizard. Central Administration is not provisioned on additional
servers in a farm by default.
You
can provision or un-provision Central Administration on individual servers in a
farm, no matter what the server role is by using the following methods:
·
The Services on Server page on Central Administration > System
Settings
·
Windows PowerShell cmdlets:
New-SPCentralAdministration
Remove-SPCentralAdministration
·
The psconfig.exe -cmd adminvs operation
The
SharePoint Products Configuration Wizard
Hybrid sites features
This feature allows your users to have an
integrated experience while using SharePoint Server and SharePoint Online
sites:
·
Users can follow SharePoint Server and SharePoint Online sites,
and see them consolidated in a single list.
·
Users have a single profile in Office 365, where all of their
profile information is stored.
Large
file support
·
Previous versions of
SharePoint did not support uploading or downloading files larger than 2,047 MB.
SharePoint 2016 now allows you to upload or download larger files. You can
configure the desired maximum file-size limit on a per-web application basis in
your SharePoint farm.
·
SharePoint Foundation is no longer available in the SharePoint
Server 2016 release.
SharePoint Server 2016 doesn't support the standalone install
option, so it is no longer available in the setup program. Use the MinRole
during installation and choose one of the available install options. The Single
Server Farm option where everything is installed on the same computer is
supported for dev/test/demo purposes. When you use this option, you must install
SQL Server yourself and then run the SharePoint Server 2016 farm configuration
wizard
ForeFront Identity Manager client (FIM)
Earlier versions of SharePoint used ForeFront Identity Manager
client (FIM) to synchronize between Active Directory and SharePoint. SharePoint
Server 2016 no longer uses FIM as the synchronization client. The default
process is Active Directory Import. You can also use any synchronization tool
such as Microsoft Identity Manager 2016, or any third-party tool.
Excel
Services in SharePoint
Excel Services and its associated business
intelligence capabilities are no longer hosted on SharePoint Server. Excel
Services functionality is now part of Excel Online in Office Online Server
(this is the next version of Office Web Apps Server), and SharePoint users can
use the services from there
If you currently use Excel Services in SharePoint 2013 and
upgrade to SharePoint Server 2016 you must also deploy Office Online Server
with Excel Online to ensure Excel Services functionality remains available.
Mini Roles
By
using the new MinRole feature in SharePoint Server 2016, SharePoint farm
administrators can define each server’s role in a farm topology. The role of a
server is specified when you create a new farm or join a server to an existing
farm. SharePoint automatically configures the services on each server based on
the server's role, and the performance of the farm is optimized based on that
topology.
Server role
|
Description
|
Front-end
|
Service applications,
services, and components that serve user requests belong on Front-end web
servers. These servers are optimized for low latency.
|
Application
|
Service
applications, services, and components that serve backend requests (such as
background jobs or search crawl requests) belong on Application servers.
These servers are optimized for high throughput.
|
Distributed cache
|
Service
applications, services, and components that are required for a distributed
cache belong on Distributed Cache servers.
|
Search
|
Service
applications, services, and components that are required for searching belong
on Search servers.
|
Custom
|
Custom service
applications, services, and components that do not integrate with MinRole
belong on Custom servers. The farm administrator has full control over which
service instances can run on servers assigned to the Custom role. MinRole
does not control which service instances are provisioned on this role.
|
Single-server farm
|
Service
applications, services, and components required for a single machine farm
belong on a Single-Server Farm. A Single-Server Farm is meant for
development, testing, and very limited production use. A SharePoint farm with
the Single-Server Farm role cannot have more than one SharePoint server in
the farm.
|
SharePoint 2016: New document library experience in O365/SharePoint online
Today morning i have seen a popup asking to experience the new document library changes in our company website, check the new changes for document libraries, hope you love this.
Now we can see folders in a list or in a tiles view and change the metadata fields and save it as a view
Wednesday, June 15, 2016
Error: Sorry something went wrong...the file … has been modified by … on in document library or document set
Issue: i am seeing the above error while updating an item inside document library with document set content type, it is happening while updating the item using JQuery code in office 365 with REST calls, and i am do that update for checking out(updating a custom column called checkout) document set and then updating the field columns, so i am seeing this error for the second update of item properties for a document set.
Resolution:
I have resolved this issue by removing the versioning from that particular document library
and the also unchecked the "Automatically update the workflow status to the stage name" and the other JQuery code change which may help resolving the issue is to reload the list before doing a second update using CSOM
Wednesday, February 17, 2016
K2 Vs Nintex workflows for SharePoint
|
Areas
|
K2
|
Nintex
|
|
Business
|
·
Good tool for
representing processes visually
·
Support for
delivery of data to process approvers and other stakeholders that includes
the information they need to perform their role in the process in a friendly
format. Ability to show them the data they need to make a decision on a
variety of devices, and to record their decisions.
·
Good tools for
monitoring and reporting process performance and identify delays.
|
·
Nintex Workflow
is GUI base and easy to use. It is suited for workflows that are not too
complex. It would be great to have more in depth training and the user guide
has room for improvement as well
·
Nintex is a
great tool for a logical, tech-minded individual without official development
skills.
|
|
Support
|
·
K2 as has best
support and great community base
|
·
Nintex lags in
support
|
|
Advantages
|
·
User friendly
·
Reporting
capability
·
Auditing
capability
·
Workflow and
business process management
·
Line of
Business Data integration
·
Good for large
data pulling
·
Easy upgrade to
new versions
|
·
Non-technical
users can implement somewhat complex solutions.
·
Email
notifications easy.
·
Can see
workflow task history visually.
·
Administration
for Nintex is easy
|
|
Disadvantages
|
·
We
found SharePoint's built-in process tools clumsy, hard to re-use, and
not very powerful or flexible.
·
Getting setup
to where you're actually start using the product can be quiet complex and the
instructions are not quite clear
|
·
Error messages
are completely vague, making it extremely difficult to debug.
·
Failures occur
for random reasons.
·
Error
notifications get sent out too frequently which confuse users.
·
Have
performance issue when pulling larger lists
·
Support
nightmare for failed workflows.
|
|
Cost
|
·
K2 blackpearl
(enterprise) has a fixed cost for unlimited users and servers
|
·
Nintex has a
price per web front-end. This is key consideration when farming out
multiple SharePoint front-ends.
|
|
Integration
|
·
K2 blackpearl
provides exclusive activity/event library addressing common systems and
scenarios ( AD integration for user management, Exchange integration, SAP,
Salesforce,SharePoint integration for actions such as document management,
user management, CRM). It also provides excellent framework to connect to LOB
systems using Smart Objects. This helps developer’s focus on core process
logic than interface details.
|
·
Nintex also
is very tightly integrated with SharePoint and lacks integration ability to
external LOB in the enterprise.
·
It also
connects to databases and CRM systems, or integrating your SharePoint content
with social media platforms
|
|
Conclusion
|
·
K2 is for
medium to large budget, scaling to enterprise in IT pro-environment
|
·
Nintex is best
suited for small business solutions which deals with lesser data and business
can easily create workflows without any developer
|
.
Tuesday, September 8, 2015
Thursday, September 3, 2015
New Features in SharePoint 2016
- Role based configuration wizard for configuring a server role
- Front end
- Application
- Search
- Specialized load
- Distributed cache
- Zero downtime patching
- App launcher for on premise has been introduced
- Office 365 api's coming to On-premise
- No Standalone machine any more there should be two servers two install SharePoint now one for SharePoint and other for Sql server
- No Foundation version any more
- Build one and deploy into two environments(for one premise and office 365)
Subscribe to:
Posts (Atom)