Quantcast
Are you the publisher? Claim or contact us about this channel


Embed this content in your HTML

Search

Report adult content:

click to rate:

Account: (login)

More Channels


Showcase


Channel Catalog



older | 1 | .... | 7 | 8 | (Page 9) | 10 | newer

    0 0

    The SharePoint 2016 April 2017 Updates have been released. SharePoint Server 2016 (sts-x-none): https://support.microsoft.com/en-us/help/3178718 SharePoint Server 2016 (wssloc): https://support.microsoft.com/en-us/help/3178721 Office Online Server: https://support.microsoft.com/en-us/help/3127895/ Office Updates: https://support.microsoft.com/en-us/help/4016803 Consider using the SharePoint Patch Cmdlets available at SharePoint Updates for your farm!

    The post SharePoint 2016 April 2017 Updates appeared first on The SharePoint Farm.


    0 0

    With the release of the April 2017 Public Update, it is now possible to determine MinRole Compliance via PowerShell without any reflection! The process is simple, and as before, it returns a boolean value of true if compliant, false if not, and no value is returned when using the Custom role. To check on all servers in the farm, use: The output will be similar to: And that’s it!

    The post Determine MinRole Compliance via PowerShell Part 2 appeared first on The SharePoint Farm.


    0 0

    The SharePoint 2013 May 2017 Updates have been released: SharePoint Foundation 2013: https://support.microsoft.com/help/3191911 SharePoint Server 2013: https://support.microsoft.com/help/3191913 Project Server 2013: https://support.microsoft.com/help/3191912 Office Web Apps 2013: https://support.microsoft.com/help/3191888 Office Updates: https://support.microsoft.com/help/4020152 Consider using the SharePoint Patch Cmdlets available at SharePoint Updates for your farm!

    The post SharePoint 2013 May 2017 Updates appeared first on The SharePoint Farm.


    0 0

    The SharePoint 2016 May 2017 Updates have been released. SharePoint Server 2016 (sts-x-none): https://support.microsoft.com/help/3191880 SharePoint Server 2016 (wssloc): https://support.microsoft.com/help/3191884 Office Online Server: https://support.microsoft.com/help/3191915 Office Updates: https://support.microsoft.com/help/4020152 Consider using the SharePoint Patch Cmdlets available at SharePoint Updates for your farm!

    The post SharePoint 2016 May 2017 Updates appeared first on The SharePoint Farm.


    0 0

    For quite a few years the advice many consultants and administrators would hand out regarding SharePoint updates (hotfixes, security fixes, and of course Cumulative Updates) was “wait and thoroughly test”. Waiting was easy, but testing is always hard. In my personal experience, most companies do not have adequate test harnesses to cover the amount of basic testing that should occur in a production-like environment. This sometimes made CUs a “roll of the dice” for production deployments. And, in the past, certain fairly major issues with CUs have taken well over 4 months to be resolved; worse yet, these same issues would roll into moderate to critical security updates, preventing their deployment. Now that we have SharePoint 2016, that stance has changed. The patches are smaller, easier for Microsoft to test, and are released to a select group of individuals and companies prior to their public release. This allows Microsoft to receive reports and handle regressions prior to Patch Tuesday. Because of these improvements, the SharePoint Product Group now recommends SharePoint 2016 Public Updates be deployed immediately upon release to the public. Now, I certainly won’t put it against you to test the Public Updates in a production-like, but from personal experience, with regards to regressions, the 2016 Public Updates are significantly safer than any previous (or current!) SharePoint 2013 or lower patch level. For an official document, see the article Updated Product Servicing Policy for SharePoint Server 2016. The FAQ at the bottom of the article goes into the new stance on Public Updates. Question: Should I install the monthly Public Updates for SharePoint Server 2016 immediately or should I install them only if they contain a fix for a specific issue I’m having? Answer: Microsoft recommends that all customers install Public Updates for SharePoint Server 2016 as soon as they become available. Microsoft performs rigorous validation of each Public Update, both internally and with a select set of partners and customers before it is released to ensure it has the highest quality.

    The post SharePoint Product Group Stance on Public Updates appeared first on The SharePoint Farm.


    Warnning: Do NOT Get Caught While Searching!!
    Your IP : - Country : - City:
    Your ISP TRACKS Your Online Activity! Hide your IP ADDRESS with a VPN!
    Before you searching always remember to change your IP adress to not be followed!
    PROTECT YOURSELF & SUPPORT US! Purchase a VPN Today!
    0 0

    When upgrading the Secure Store database to SharePoint 2016, you may encounter an error if you have applied the May 2017 CU to SharePoint 2013. This CU increments the Secure Store database schema and prevents the upgrade to SharePoint 2016. The error message you’ll see in ULS will be similar to this. SharePoint Server 2016 is looking for a schema version of ‘15.0.2.0’ while the schema on the database was incremented to ‘15.0.3.0’ via the May 2017 CU for SharePoint 2013. Microsoft is aware of the issue. Likely the fix will reside on the SharePoint 2016 side via Public Update.

    The post Secure Store Database Upgrade to SharePoint 2016 Error appeared first on The SharePoint Farm.


    0 0

    The SharePoint 2013 June 2017 Updates have been released: SharePoint Foundation 2013: https://support.microsoft.com/help/3203428 SharePoint Server 2013: https://support.microsoft.com/help/3203430 Project Server 2013: https://support.microsoft.com/help/3203429 Office Web Apps 2013: https://support.microsoft.com/help/3203391 Office Updates: https://support.microsoft.com/help/4023935 Consider using the SharePoint Patch Cmdlets available at SharePoint Updates for your farm!

    The post SharePoint 2013 June 2017 Updates appeared first on The SharePoint Farm.


    0 0

    The SharePoint 2016 June 2017 Updates have been released. SharePoint Server 2016 (sts-x-none): https://support.microsoft.com/help/3203432 SharePoint Server 2016 (wssloc): https://support.microsoft.com/help/3203433 Office Online Server: https://support.microsoft.com/help/3203485 Office Updates: https://support.microsoft.com/help/4023935 Consider using the SharePoint Patch Cmdlets available at SharePoint Updates for your farm!

    The post SharePoint 2016 June 2017 Updates appeared first on The SharePoint Farm.


    0 0

    If you’ve installed a new SharePoint 2016 farm and have noticed that the Administration database is in an Upgrade Recommended status, it may be a bug if you’ve applied any post-RTM, up to and including the June 2016 Public Update. This issue appears on farms which have not activated Project Server via . Each SharePoint Content Database has a  table. In this table, each product (SharePoint, Project Server, among others) has one or more line entries for the version of schema that is applied to the database. Project Server has a  of . For a server without Project Server enabled, there is a single line entry with a  of . This appears to be the source of the problem. If this value is manually updated to the current schema version, or  in the case of the May 2017 PU, and the Administration database object invalidated, the database will be cleared of the upgrade recommended value. Of course it is not supported to manually update SharePoint databases (nor is it proper for how SharePoint is tracking Project Server schema updates!), but the SharePoint Product Group is investigating this particular issue with the Administration database.

    The post SharePoint 2016 Administration Database Upgrade Recommended Bug appeared first on The SharePoint Farm.


    0 0

    Just Enough Administration is a new feature of PowerShell in Windows Server 2016 and WMF 5.x which we can leverage across many enterprise applications, including SharePoint. It allows you to assign rights with “just enough” permission to perform a specific task or function. For example, we might want to allow a group of individuals to execute a timer job, but not change Managed Metadata Service Application settings, drop Content Databases, and so forth. Enter JEA! We’ll walk through a simple scenario of how to configure JEA for SharePoint. This scenario can be greatly expanded upon and does not cover all possible scenarios you may want to accomplish via JEA. The first step to configuring JEA is to create an Active Directory Security Group and add the members to the group for which JEA should apply. The next step is to enable PowerShell Remoting. On your SharePoint server, run . As we’ll be using a local account for JEA, explained in more detail below, we’ll need to add the machine account as a Shell Administrator. On your SharePoint server, create a new directory under called . Within that directory, create a new file,  with the below contents. Next, again in the directory , create a new folder named (the name can be anything, but follow the example on your first run through). Within the  directory, create a new directory named . We’ll create another module. The module file name must match the directory name, or  in our example. Within the  directory, create a  file. In PowerShell, create a module manifest based off of our new module. We do not need to make any changes to either of these files. The next step is to generate our Role Capabilities file. This file will define what cmdlets the defined group will have access to. Open this file in your favorite text editor. You’ll see there are quite a few lines commented out. We can either replace those lines with our specified text, or we can just create new line entries. Either route you go, make sure you only have one Key = Value pair for each named key. First, we’ll add the . This will import our module that loads the SharePoint snapin we previously created in the Modules folder. The next step is to define the cmdlets we want our users to have access to, changing the  value. In this example, we’ll allow the users to run  and . Save the file, these are the only changes we’ll make. The next step is to create our PowerShell Session Configuration file. First, define the roles. This value is based off of the Active Directory Security Group, for example, . The RoleCapabilities value, , is the same name as our previously created Role Capabilities file. You can have multiple Role Capabilities files with different definitions (e.g. GroupA might have access to  cmdlets while GroupB might have access to  cmdlets). A single group can also have access to multiple Role Capabilities. In this example, we’re only specifying a single group and capability file. If you need to specify multiple groups or Role Capabilities, just separate them with a comma. Next, create the configuration file. You’ll see a few different parameters in this cmdlet. The  is a parameter which, in essence, creates a Local Administrator session. We need Local Administrator for most, but not all, SharePoint cmdlets. This is the best way to use JEA, although there are other options such as gMSA, which I will not go into here. The  parameter is a directory (which must exist) that stores session commands. This allows you to review all executed cmdlets within the JEA sessions. The transcripts are written by LocalSystem and this folder should be locked down to prevent unauthorized access. Lastly, we’re passing in our  variable to . You can further edit this file via your favorite text editor, if required. Next, make sure you test your session configuration file! This can be accomplished via the below command. It must return True. If it returns False, you have an invalid configuration file. The last step server-side is to register the configuration file and restart WinRM. On your client workstation, run the following command to create a new remote session scoped to the JEA configuration. When connected, run . This should only list the default commands that are provided via JEA along with  and  from our example. Executing those commands should yield the expected output as if you were running them through a standard PowerShell session. JEA does have limitations. JEA sessions run in PowerShell No Language mode. This means you can’t use variables. Instead, you can craft functions that users of the JEA session can call. For example, let’s say you wanted to run the simple command . This would error out in the JEA session. The alternative is to create a function, such as the below function. While not best practice, for our example, add this function to the module we previously created,  at any point below the  line. Edit the file . Add a new line to expose our function. Enter a new JEA session and you can run the new function successfully, e.g.  or . This will show us the Application Pool information for the User Profile Service Application and Managed Metadata Service Application. While most changes to JEA configuration only require one to end and create a new remote session, changes to the Session Configuration File require that you unregister and register the configuration file again. A restart of WinRM may also be required. To complete this, run the below script based off of our example. Hopefully this will be useful to segregate personnel who need to have full administrative access to the farm, where JEA provides no value, versus those who need selective access to administer the farm, where JEA can play a valuable role in providing exactly the amount of access they require.

    The post Just Enough Administration for SharePoint PowerShell appeared first on The SharePoint Farm.


    Warnning: Do NOT Get Caught While Searching!!
    Your IP : - Country : - City:
    Your ISP TRACKS Your Online Activity! Hide your IP ADDRESS with a VPN!
    Before you searching always remember to change your IP adress to not be followed!
    PROTECT YOURSELF & SUPPORT US! Purchase a VPN Today!
    0 0

    The SharePoint 2013 July 2017 Updates have been released: SharePoint Foundation 2013: https://support.microsoft.com/en-us/help/3213563 SharePoint Server 2013: https://support.microsoft.com/en-us/help/3213569 Project Server 2013: https://support.microsoft.com/en-us/help/3213566 Office Updates: https://support.microsoft.com/en-us/help/4033107 Consider using the SharePoint Patch Cmdlets available at SharePoint Updates for your farm!

    The post SharePoint 2013 July 2017 Updates appeared first on The SharePoint Farm.


    0 0

    The SharePoint 2016 July 2017 Updates have been released. SharePoint Server 2016 (sts-x-none): https://support.microsoft.com/en-us/help/3213544 SharePoint Server 2016 (wssloc): https://support.microsoft.com/en-us/help/3213543 Office Online Server: https://support.microsoft.com/en-us/help/3213657 Office Updates: https://support.microsoft.com/en-us/help/4033107 Consider using the SharePoint Patch Cmdlets available at SharePoint Updates for your farm!

    The post SharePoint 2016 July 2017 Updates appeared first on The SharePoint Farm.


    0 0

    With the release of Workflow Manager CU4, it now supports Windows Server 2016 and SQL Server 2016! This is a welcome sign for those migrating to SharePoint 2016, especially where you can keep your Windows and SQL Server versions consistent (plus one less instance of SQL to manage!). Other benefits include AlwaysOn support and 5 server farms; previously only farms of 1 and 3 servers were supported configurations. Make sure to read the full KB4019220 in order to get information on the pre-reqs for the CU as well as for the new features of the CU. The download is available on the Microsoft Download Center. And of course, SharePoint Updates also has all Workflow Manager updates!

    The post Workflow Manager Now Supports Windows Server 2016 and SQL Server 2016 appeared first on The SharePoint Farm.


    0 0

    The SharePoint 2013 August 2017 Updates have been released: SharePoint Foundation 2013: https://support.microsoft.com/help/4011073 SharePoint Server 2013: https://support.microsoft.com/help/4011076 Project Server 2013: https://support.microsoft.com/help/4011074 Office Updates: https://support.microsoft.com/help/4036121 Consider using the SharePoint Patch…

    Continue reading

    The post SharePoint 2013 August 2017 Updates appeared first on The SharePoint Farm.


    0 0

    The SharePoint 2016 August 2017 Updates have been released. SharePoint Server 2016 (sts-x-none): https://support.microsoft.com/help/4011049 SharePoint Server 2016 (wssloc): https://support.microsoft.com/help/401105 Office Updates: https://support.microsoft.com/help/4036121 Consider using the SharePoint Patch Cmdlets…

    Continue reading

    The post SharePoint 2016 August 2017 Updates appeared first on The SharePoint Farm.


    Warnning: Do NOT Get Caught While Searching!!
    Your IP : - Country : - City:
    Your ISP TRACKS Your Online Activity! Hide your IP ADDRESS with a VPN!
    Before you searching always remember to change your IP adress to not be followed!
    PROTECT YOURSELF & SUPPORT US! Purchase a VPN Today!
    0 0

    In SharePoint 2016, it is currently not possible to generate a Master Key with the June 2017 through August 2017 PU. Attempting to generate a…

    Continue reading

    The post SharePoint 2016 Secure Store Master Key Bug appeared first on The SharePoint Farm.


    0 0

    The SharePoint 2016 September 2017 Updates have been released. This is also the release of Feature Pack 2. SharePoint Server 2016 (sts-x-none): https://support.microsoft.com/help/4011116 SharePoint Server 2016…

    Continue reading

    The post SharePoint 2016 September 2017 Updates (Feature Pack 2) appeared first on The SharePoint Farm.


    0 0

    The SharePoint 2013 September 2017 Updates have been released: SharePoint Foundation 2013: https://support.microsoft.com/help/4011132 SharePoint Server 2013: https://support.microsoft.com/help/4011116 Project Server 2013: https://support.microsoft.com/help/4011115 Office Web Apps 2013: https://support.microsoft.com/help/3213562/ Office Updates: https://support.microsoft.com/help/4040279 Consider…

    Continue reading

    The post SharePoint 2013 September 2017 Updates appeared first on The SharePoint Farm.


    0 0

    The Content Type Subscriber job which is responsible for synchronizing Content Types from the Content Type Hub to Site Collections will generate unwanted audit entries…

    Continue reading

    The post Content Type Subscriber Job Generates Unwanted Audit Entries appeared first on The SharePoint Farm.


    0 0

    The SharePoint 2013 October 2017 Updates have been released: SharePoint Foundation 2013: https://support.microsoft.com/help/4011173 SharePoint Server 2013: https://support.microsoft.com/help/4011177 Project Server 2013: https://support.microsoft.com/help/4011175 Office Web Apps 2013:…

    Continue reading

    The post SharePoint 2013 October 2017 Updates appeared first on The SharePoint Farm.


    Warnning: Do NOT Get Caught While Searching!!
    Your IP : - Country : - City:
    Your ISP TRACKS Your Online Activity! Hide your IP ADDRESS with a VPN!
    Before you searching always remember to change your IP adress to not be followed!
    PROTECT YOURSELF & SUPPORT US! Purchase a VPN Today!

older | 1 | .... | 7 | 8 | (Page 9) | 10 | newer