Archive

Posts Tagged ‘SharePoint’

TCP/IP Ports of SharePoint 2016

January 24, 2017 Leave a comment

SharePoint 2016 huh?!
(Long time since I last posted anything real here…)

Actually, this post is by popular demand 🙂 This is the 2016 version of the post a wrote when SHarePoint 2013 was new, as you can see, not much has changed…I have updated a few lines with what I know now that I did not know then, thats it. Please let me know if I missed something.

The recommended approach is to create a GPO with these firewall rules and apply that rule to the SharePoint servers in your farm. Add all of them, best that way to avoid extreme t-shooting in the future.

Another but related recommendation is to configure the Loopback check funktion in Windows server to allow the FQDN’s of your web applications (Use the Loopback check tool).

List of ports used by SharePoint 2013 and its related services.
Reference links at the end.

Protocol Port Usage Comment
TCP 80 http Client to SharePoint web server traffic
(SharePoint – Office Online Server/Office Web Apps communication)
TCP 443 https/ssl Encrypted client to SharePoint web server traffic
(Encrypted SharePoint – Office Online Server/Office Web Apps communication)
TCP 1433 SQL Server default communication port. May be configured to use custom port for increased security
UDP 1434 SQL Server default port used to establish connection May be configured to use custom port for increased security
TCP 445 SQL Server using named pipes When SQL Server is configured to listen for incoming client connections by using named pipes over a NetBIOS session, SQL Server communicates over TCP port 445
TCP 25 SMTP for e-mail integration Cannot in 2016 be configured (Use SMTP ports other than the default (25).)
TCP 16500-16519 Ports used by the search index component Intra-farm only
Inbound rule Added to Windows firewall by SharePoint. (GPO may override this change)
TCP 22233-22236 Ports required for the AppFabric Caching Service Used by the Distributed Cache…
TCP 808 Search – Query processing component
Windows Communication Foundation communication
Search – Query processing component
(WCF)
TCP 32843 Communication between Web servers and service applications http (default) To use custom port, see references section
Inbound rule Added to Windows firewall by SharePoint
TCP 32844 Communication between Web servers and service applications https
Inbound rule Added to Windows firewall by SharePoint
TCP 32845 net.tcp binding: TCP 32845 (only if a third party has implemented this option for a service application)  Custom Service Applications
Inbound rule Added to Windows firewall by SharePoint
TCP 32846 Microsoft SharePoint Foundation User Code Service (for sandbox solutions)  Inbound on all Web Servers
Inbound rule Added to Windows firewall by SharePoint
Outbound on all Web and App servers with service enabled.
TCP 636 User Profile Synchronization Service/Active Directory Import Synchronizing profiles between SharePoint 2016 and AD using SLDAP (Secure LDAP)
TCP 5725 User Profile Synchronization Service Synchronizing profiles between SharePoint 2016 and Active Directory Domain Services (AD DS)
TCP + UDP 389 User Profile Synchronization Service LDAP Service
TCP + UDP 88 User Profile Synchronization Service Kerberos
TCP + UDP 53 User Profile Synchronization Service DNS
UDP 464 User Profile Service Kerberos change password
TCP 809 Office Online Server/Office Web Apps Office Online Server/Office Web Apps intra-farm communication.

References:

Security for SharePoint Server 2016
https://technet.microsoft.com/en-us/library/mt683473(v=office.16).aspx

TCP/IP Ports of SharePoint 2013
https://blog.blksthl.com/2013/02/21/tcpip-ports-of-sharepoint-2013/

 


___________________________________________________________________________________________________

Enjoy!

Regards

Twitter | Technet Profile | LinkedIn

Advertisements

Office 365 News – Move and Copy files and folders in OneDrive for Business

April 16, 2015 1 comment

 Office365logo       SP2013logo       SharedLove

Now, finally, we can move and copy files within our OneDrive for Business web GUI

Dokument

Some random document…

Some time, early 2015, Microsoft introduced the ability to move/copy files in OneDrive for Business. This has been one of the major obstacles for using OneDrive for Business as a E1 user without the Office applications installed locally. Or rather, as a Online only user no matter what license. As a long time SHarePoint user and technician, this is a long awaited feature in SHarePoint as well, so now I’m keeping my fingers crossed for this ‘simple’ little feature to appear there as well. (I do not for one second think that this has been easy to implement at all) In addition, the function is quick!

Want to see how it looks and works?

The following table lists the tested and verified behaviour of the Copy/Move functionality in OneDrive for Business:

Action Behavior Notes
Move File(s) Moves the selected file(s) to the designated target container Retains metadata Retains sharing Does not overwrite if filename exists, reports back error
Move Folder(s) Moves the selected folder(s) to the designated target container Recreates a new copy of the folder Retains sharing Does not overwrite if filename exists, reports back error
Copy File(s) Copies the selected file(s) to the designated target container Recreates a new copy of the file(s) with new metadata Does not retain sharing Does not overwrite if filename exists, reports back error
Copy Folder(s) Copies the selected folder(s) to the designated target container Recreates a new copy of the folder with new metadata Does not retain sharing Does not overwrite if filename exists, reports back error
Copy or Move in SharePoint N/A – ‘Send to’ a predetermined location is the closest we get in SharePoint Server or SharePoint Online N/A

How it looks in reality:

Move or Copy a single file

SingleFileMove1

Move or Copy multiple files/folders

MultipleFilesMove1

Select the target, check the ‘Copy’ box if you want to Copy and not Move

MultiMoveDialog

After copying/Moving, you will get a Little reciept in the top right corner

Shared15

Ok

or

SharedCopy

If one or many of the files allready exist at the target, they are not overwritten, not even with a new name or new version. You will instead get a note on this and the result

Error

Now, we all hope for the same in SharePoint! Until it comes, we all to this ‘simple’ feature say: FINALLY!

References and Credits

None at this time…

Credits & many thanks to

Everyone!   SP2013logo

_________________________________________________________

Enjoy!

Regards

Twitter | Technet Profile | LinkedIn

Office 365 guide series – Manage files and folders with PowerShell and CSOM

February 24, 2015 Leave a comment

 Office365logo       SP2013logo

How to manage files and folders with PowerShell and CSOM

DocLib1

How can we manage these items…?

This is a pure guide to using PowerShell to manage and manipulate files and folders, libraries and all document management related tasks in a SharePoint Online or OneDrive for Business environment.

The sections in this guide are:

– Prerequisites
– Load assemblies
– Load a CSOM Context
– Web
– List/Library
– GetFileByServerRelativeUrl and GetForlderByServerRelativeUrl
– Create a file from a local copy
– Create a folder from a local copy
– Set properties on a file
– Set properties on a folder
– ResolveUser (Function)
– GetItemProperties (Function)

Prerequisites

Before beeing able to do much in SharePoint Online or OneDrive for Business, you have to start using CSOM, or Client Side Object Model, this allows us to do pretty much everything we could do before using regular PowerShell and the SharePoint CMD’lets from the SharePoint PowerShell add-on.
Install assemblies:
Download and install ther latest version of the SharePoint Server 2013 Client Components SDK, this can be downloaded from here: http://www.microsoft.com/en-us/download/details.aspx?id=35585
After the SDK and the CSOM assembly DLL’s are in place, make sure you load the assemblies before calling them.

Load assemblies

 Add-Type -Path "C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\15\ISAPI\Microsoft.SharePoint.Client.dll"
 Add-Type -Path "C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\15\ISAPI\Microsoft.SharePoint.Client.Runtime.dll"

This will open up for usage of CSOM in PowerShell.

Load a context

$SPOUser = "administrator@blksthl.onmicrosoft.com"
# Uses a hardcoded password, use only during test/lab:
$SPOPassword = convertto-securestring "Password01" -asplaintext -force
# Better: $SPOPassword = Read-Host -Prompt "Please enter your password" -AsSecureString
$SPOODfBUrl = "https://blksthl.sharepoint.com/personal/jeffrey_lebowski_blksthl_com"
$Context = New-Object Microsoft.SharePoint.Client.ClientContext($SPOODfBUrl)
$Credentials = New-Object Microsoft.SharePoint.Client.SharePointOnlineCredentials($SPOUser,$SPOPassword)
$Context.RequestTimeout = 16384000
$Context.Credentials = $Credentials
$Context.ExecuteQuery()

Returns: $Context

Web

(Using $Context from the section on Context above)

$Web = $Context.Web
$Context.Load($Web)
$Context.ExecuteQuery()

Returns: $Web

List/Library

$SPODocLibName = "Documents"
$SPOList = $Web.Lists.GetByTitle($SPODocLibName)
$Context.Load($SPOList.RootFolder)
$Context.ExecuteQuery()

Returns: $SPOList

GetFileByServerRelativeUrl and GetForlderByServerRelativeUrl

In order to use the ‘Get…ByServerRelativeUrl’ methods you have to supply a relative path to the file or folder, this means a path starting from the FQDN.

Example 1
https://company.sharepoint.com/get/fileorfolder/by/relative/url
FQDN: https://company.sharepoint.com
ServerRelativeUrl: /get/fileorfolder/by/relative/url

Example 2
https://company-my.sharepoint.com/personal/firstname_lastname_company_com
FQDN: https://company-my.sharepoint.com
ServerRelativeUrl: /personal/firstname_lastname_company_com

Example file:

"/personal/jeffrey_lebowski_blksthl_com/documents/report1.xlsx"

Example folder:

 "/personal/jeffrey_lebowski_blksthl_com/documents/subfolder"

Create a file from a local copy

This can be accomplished in several ways, this is one:

1.
$LocalFile = Get-ChildItem -path "C:\Homedirs\jeff\report1.xlsx"
$FolderRelativeUrl = $SPOList.RootFolder.ServerRelativeUrl
$FileName = $LocalFile.Name
$FileUrl = $FolderRelativeUrl + "/" + $FileName
[Microsoft.SharePoint.Client.File]::SaveBinaryDirect($Web.Context, $fileUrl, $LocalFile.OpenRead(), $true)

Returns: New file created in SPO/ODfB

Create a folder from a local copy

$SPOFolder = $SPOList.RootFolder
$LocalFolder = Get-ChildItem -path "C:\Homedirs\jeff\" -Recurse -Include "folder1" 
$FolderName = $LocalFolder.Name
$NewFolder = $SPOFolder.Folders.Add($FolderName)
$Web.Context.Load($NewFolder)
$Web.Context.ExecuteQuery()

Returns: New folder created in SPO/ODfB

Set properties on a file

Input: $FileRelativeUrl, $SPOItemModifier, $SPOItemOwner, $ItemCreated, $ItemModified

$CurrentFile = $Context.web.GetFileByServerRelativeUrl($FileRelativeUrl)
$Context.Load($CurrentFile)
$Context.ExecuteQuery()
$ListItem = $CurrentFile.ListItemAllFields;
$ListItem["Editor"] = $SPOItemModifier; # Get object from ResolveUser
$Listitem["Author"] = $SPOItemOwner; # Get object from ResolveUser
$Listitem["Created"] = $ItemCreated;
$Listitem["Modified"] = $ItemModified;
$ListItem.Update()
$Context.Load($CurrentFile)
$Context.ExecuteQuery()

Returns: Folder stamped with new properties in SPO/ODfB

Set properties on a folder

Input: $FolderRelativeUrl, , $SPOItemModifier, $SPOItemOwner, $ItemCreated, $ItemModified

$CurrentFolder = $Context.web.GetFolderByServerRelativeUrl($FolderRelativeURL)
$Context.Load($CurrentFolder)
$Context.ExecuteQuery()
$SPOFolderItem = $CurrentFolder.ListItemAllFields;
$SPOItemOwner = ResolveUser $UserEmail # For ResolveUser see separate function described later in this post
$SPOFolderItem["Editor"] = $SPOItemModifier # Must be a userobject, see 'ResolveUser'
$SPOFolderItem["Author"] = $SPOItemOwner # Must be a userobject, see 'ResolveUser'
$SPOFolderItem["Created"] = $ItemCreated # In the format: "8/10/2013 7:04 PM", see 'GetItemProperties'
$SPOFolderItem["Modified"] = $ItemModified # In the format: "8/10/2013 7:04 PM", see 'GetItemProperties'
$SPOFolderItem.Update()
$Context.Load($CurrentFolder)
$Context.ExecuteQuery()

Returns: Folder stamped with new properties in SPO/ODfB

ResolveUser (Function)

Function ResolveUser ($InputUPN)
# Resolves a user to a userobject
{
    $OutputUserObject = $Web.Context.web.EnsureUser($InputUPN)
    $Web.Context.Load($OutputUserObject)
    $Web.Context.ExecuteQuery()
    Return $OutputUserObject
}

Returns: UserObject for $InputUPN (UserPrincipalName/Email)

GetItemProperties (Function)

Function GetItemProperties ($InFileObject)
# Gets basic properties to set on files and folders
{
    $Global:ItemCreated = $InFile.CreationTime
    $Global:ItemModified = $InFile.LastWriteTime
}

Returns: Global: Variables for ItemCreated and LastWriteTime of $InFileObject (File or Folder)

Thats all for now, I hope that you let me know if there is anything that seems to be wrong or does not work. The problem with describing all this in a complete way, is that it is easy to leave something out and it is also difficult to test every aspect while writing. Time is limited for all of us…
Anyway, my goal was to write a post that covered what I was myself missing…I hope that this is it. And again, please let me know if there are any mistakes in here.

References and Credits

None at this time…

Credits & many thanks to

LabCenter – you guys always publish my articles!

My family, my parents, Ia and the kids!

SP2013logo

_________________________________________________________

Enjoy!

Regards

Twitter | Technet Profile | LinkedIn

Office 365 News – New document now supports Content types in SharePoint Online

February 18, 2015 2 comments

 Office365logo       SP2013logo

‘new document’ now supports Content types in SharePoint Online

Thank you Microsoft, Content types just got user friendly and easy to use and promote!

ContentTypes1x

The new- new document dialog

Before yesterday, I knew that the ‘new document’ button in a document library became useless when you enabled Content types in a document library. This has for me and many of my customers been a huge drawback since the ‘new document’ button was still there, in plain view and for the regular user, what they were meant to use.

This old behavious was that when you pressed on ‘new document’ in a document library with multiple content types, you got the upload document dialog.

Upload dialog2

Old behaviour

What I was so glad to discover yesterday, during a live demo at a customer, that this has been fixed now in SPO! Instead of the upload dialog, I could now get this:

ContentTypes1

Fixed!

One down!
Next step, make content types available to Office Online…(They still seem to require the Office Applications installed on the client, nothing for E1 users or less in other words…)
I would also like the new folder option back with the content types 🙂

References and Credits

None at this time…

Credits & many thanks to

Cramo, this is where I did the demo when this change presented itself to me! A pleasure to work with you guys!

 

SP2013logo

_________________________________________________________

Enjoy!

Regards

Twitter | Technet Profile | LinkedIn

Office 365 News – Unannounced Microsoft change to SharePoint Online access

February 17, 2015 2 comments

 Office365logo       SP2013logo

Microsoft recently made a change to the way users can access SharePoint Online, this may affect many thousands of customers without them knowing…

Licensex

It has been disclosed to me that Microsoft has implemented a change on all Office 365 tenants to the way an unlicensed user can access SharePoint Online services…in a bad way…

Previously, the behaviour was that if you did not give a user a the SharePoint license in Office 365, the user could not access SharePoint.
This is the expected behaviour and this is how most companies restricted access to SharePoint Before they were ready to offer the service to their organizations.
This is no more, or at least not the current behaviour…Microsft has ‘temporarily’ made a change that allows ALL users, with a license or not to have access to all SharePoint Services.
The imidiate affect may be that your organization sleeps safely in the belief that SHarePoint may not be accessed, except by you in IT or by a limited number of individuals, meanwhile, the users go crazy and start using SharePoint in ways you never intended…

Well, this is something I don’t like, I would like this change to be limited to the ones who specifically asked for it, and if you needed it, you could request it, not the other way around.

Note 1: If you find that you do not want this behaviour, you want access only to your licensed users. Open a Service Request with Microsoft and ask them to change it back, they will help you then.

Note 2: The change does not affect OneDrive for Business, unprovisioned users do not get access to their ODfB without the SharePoint license.

The reason given by Microsoft representatives is this: Microsoft recognizes assigning licenses to users that are synced to the O365 services is cumbersome for larger tenants, to alleviate this pain point; a temporary change has been released to SharePoint Online that will allow users to access SharePoint Online even without license.’

 

References and Credits

None at this time…

Credits & many thanks to

Pihlen!

 

SP2013logo

_________________________________________________________

Enjoy!

Regards

Twitter | Technet Profile | LinkedIn

Office 365 News – Newly Introduced security feature in SPO hides the Web Designer Galleries

February 2, 2015 3 comments

 Office365logo       SP2013logo

Newly introduced security feature in SharePoint Online hides the Web Designer Galleries, Save site as template and a lot more too…

AdminSPO Admin setting (with a dead link)

During the end of 2014, beginning of 2015, a new security feature in SharePoint Online has been rolled out. The feature in itself is great, it has been introduced to (From the SharePoint admin interface):

Control whether users can run custom script on personal sites and self-service created sites.  Note: changes to this setting might take up to 24 hours to take effect.

What is good to know without Reading too much on this feature, is that these things for example will be missing:

Site feature Behavior Notes
Save Site as Template No longer available in Site Settings. You can still build sites from templates created before scripting was disabled.
Save document library as template No longer available in Library Settings. You can still build document libraries from templates created before scripting was disabled.
Solution Gallery No longer available in Site Settings. You can still use solutions created before scripting was disabled.
Theme Gallery No longer available in Site Settings. You can still use themes created before scripting was disabled.
Help Settings No longer available in Site Settings. You can still access help file collections available before scripting was disabled.
Sandbox solutions Solution Gallery will not appear in the Site Settings so you can’t add, manage, or upgrade sandbox solutions. You can still run sandbox solutions that were deployed before scripting was disabled.
SharePoint Designer Site Pages: No longer able to update web pages that are not HTML.Handling List: Create Form and Custom Action will no longer work.Subsites: New Subsite and Delete Site redirect to the Site Settings page in the browser. Data Sources: Properties button is no longer available. You can still open data sources.

For a good detailed description of what the feature does, have a look here. It affects mostly Everything and since it is activated by default, a lot of settings and functionality is suddenly missing. The feature has two ‘levels’, for personal sites and for self service created sites. (for me, it affects all site Collections)

Turn scripting capabilities on and off (Microsoft support article)
https://support.office.com/en-us/article/Turn-scripting-capabilities-on-and-off-1f2c515f-5d7e-448a-9fd7-835da935584f?ui=en-US&amp

The feature in itself is great, but perhaps, since it removes so much of the default functionality, it should have been left off be default? Or, would cause some kind of popup to all affected users?

Well, it is here now anyway…lets consider the feature a great idea, it increases the built in security of SharePoint Online and OneDrive for Business!

The complete list of settings affected and webparts missing: Save Site as Template, Save document library as template, Solution Gallery, Web Designer Galleries, Theme Gallery, Help Settings, Sandbox solutions, the Blog Archives, Blog Notifications, Blog tools Blog Webparts, the Business Data Actions, Business Data Item, Business Data Item Builder, Business Data List, Business Data Related List, Excel Web Access, Indicator Details, Status List, Visio Web Access Business Data Webparts, the About This Community, Join, My Membership, Tools, What’s Happening Community Webarts, the Categories, Project Summary, Relevant Documents, RSS Viewer, Site Aggregator, Sites in Category, Term Property, Timeline, WSRP Viewer, XML Viewer Content Rollup Webparts, the Document Set Contents, Document Set Properties Document Sets Webparts, the HTML Form Webpart, the Content Editor, Script Editor, Silverlight Webpart Media and Content Webparts, the Refinement, Search Box, Search Navigation, Search Results Search Webparts, the Catalog-Item Reuse Search-Driven Content Webparts and the Contact Details, Note Board, Organization Browser, Site Feed, Tag Cloud, User Tasks Social Collaboration Webparts.

References and Credits

None at this time…

Credits & many thanks to

Everyone!   SP2013logo _________________________________________________________ Enjoy!

Regards

Twitter | Technet Profile | LinkedIn