Symantec for SharePoint needs to be installed on all SharePoint Servers in the SP2013 Farm?

I need a solution

Dear All,

I have a query regarding the Symantec Protection for SharePoint. Is it mandatory to install Symantec for SharePoint on all the SharePoint Servers?

We have 10 SharePoint Servers – 2 Web, 2 App, 2 Search query, 2 Search Component and 2 Search Crawl Servers. Do we require to install Symantec for SharePoint on all the 10 SharePoint Servers given above or only installation on 2 Web and 2 Apps are enough?

Please suggest., Thanks!

0

Related:

DLP Solution for SharePoint 2016

I need a solution

Trying to find out if Symantec has a compatible DLP solution for SharePoint 2016. According to this article posted last year it is not compatible with the new min roles features in SharePoint 2016: https://support.symantec.com/en_US/article.TECH246…

0

Related:

Modern Microsoft SharePoint Design: Overcoming Common Challenges – Part 3

EMC logo


This is the final installment to my 3-part series on common challenges customers are experiencing with modern SharePoint design. In the first two blogs, I talked about obstacles in implementing modern sites in SharePoint Online, including a new (“greenfield”) environment (Overcoming Common Challenges with Modern Microsoft SharePoint Design – Part I) and one with a mixture of modern and classic sites (Overcoming Common Challenges with Modern Microsoft SharePoint Design – Part 2). Now let’s focus on areas that should be considered when migrating from SharePoint on-premises to modern sites in SharePoint Online.

For those who still don’t know about Dell EMC’s consulting services practice for implementing Microsoft products – we’ve been partnering with Microsoft for 30 years! Yes, that’s right and personally, I live and breathe SharePoint, Project Online, and related services every day and have done so for the last 10 years.

Site Collection Hierarchy

Ok, so in the first blog, we established modern sites are all created as individual site collections. Most on-premises SharePoint farms consist of hundreds, if not thousands, of sub-sites nested within different site collections.This means that you’ll need to completely flatten your site structure as part of the migration to modern SharePoint Online sites.

A couple of things to consider are:

  • Site provisioning – most (if not all) migration tools currently create site collections using a classic SharePoint template. This means that you’ll need to develop a method of creating the modern SharePoint site before conducting the migration – either manually or through a tool like PowerShell.
  • SharePoint Hub sites – Hub sites are the method for re-structuring this site/sub-site relationship in modern SharePoint sites. However, there are some limitations to Hub sites (namely that there is currently a limit of 50), so you’ll need to plan how to use these to re-build your existing structure.

Migrating Security / Permissions

There are a couple of instances where security and permissions work differently in SharePoint Online than on-premises:

  • External sharing – sharing with external users (“guests”) is much easier in SharePoint Online. As you plan to migrate, you should work with site owners to understand if their site should allow external users (and then enable, if necessary) or how to re-share with external folks if they previously had access on-premises.
  • O365 Group permissions – modern team sites are connected to an O365 Group, which add some elements to the standard permission model. First, you’ll need to decide whether the site is “public” or “private” because a public O365 Group will open access to all users within the organization.  Secondly, you’ll need to determine which users need access to the O365 Group artifacts (“Documents” library, conversations, planner, etc.) as those permissions are managed separately from the SharePoint site.

In general, we often recommend that organizations take this as an opportunity to start fresh with their permissions in SharePoint Online. It is common that on-premises sites have been around for 10+ years and are a complete “rats nest” of permissions. Instead of migrating the mess (and then continue to make it messier), why not work with the site owners to re-share their site with only the people who actually need access?

Migrating Pages

Pages have been completely re-architected in modern SharePoint – and as a result, there is no current migration path for classic pages. This means that you’ll need to plan time to re-build all of your necessary pages in your newly migrated SharePoint site.  If your sites follow a standard layout, you can develop a PowerShell script to provision the modern pages with sections and configure some of the web parts and content. However, modern pages have a differing set of tools/web parts than classic sites, so doing so will not be as simple as mapping 1-to-1 and will require testing and some manual re-build where web parts don’t map properly.

Migrating Documents

Content from on-premises SharePoint can be migrated to SharePoint Online without much hassle – however, that doesn’t mean it doesn’t require some planning.  In classic SharePoint, users typically created multiple document libraries within a single site to separate different types of content. This can still be done on a modern team site, but the only documents that will show in the “Documents” link (which is part of the associated O365 Group) are the files in the default “Documents” library. So, as you plan your migration, you should work with site owners to determine if they would prefer all of their documents to show in that default library – and if so, how it should be re-organized.

Migrating Notebook / Calendars

OneNote notebooks and SharePoint calendars can be migrated to modern SharePoint sites – but, they will only be accessible through the SharePoint site. Let me explain.

  • Calendar – O365 Groups utilize an Exchange calendar for the default “Calendar” link in a modern team site. There isn’t currently a migration path for a SharePoint calendar to the associated Group calendar, so utilizing the default calendar requires a manual input of events in to the new calendar.
  • Notebook – Groups are also provisioned with a default OneNote notebook, which cannot be overwritten. If you’d like to have a single OneNote notebook on your modern team site, you will need to follow a manual method of connecting to both notebooks (in OneNote client) and using the “Move to” feature.

Lot’s to Consider….

Keep in mind, these are only some of the changes between classic and modern that should be considered when completing a migration. Also, while this blog focuses on migration to modern sites, but there is also an option to migrate to classic sites in SharePoint Online and utilize a mixed environment (see challenges from this type of environment in blog 2). As someone who’s completed many SharePoint migrations, I can tell you, they can often be more complex than they first appear. There are MANY areas (not covered here) that should be designed and well-planned before undertaking any SharePoint migration.

Summary

Leverage these tips as you consider and plan your SharePoint migration. If you’d like to have our Dell EMC SharePoint experts do it for you, we can help! Dell EMC is a gold-certified Microsoft partner and my consulting services team is responsible for all things Office 365 (including Teams, Yammer, Groups, Stream, etc.), SharePoint, Project Server/Project Online, Exchange, and Identity. We also work closely with Microsoft MVPs and the Patterns and Practice (PnP) community to leverage and improve the latest product features. Feel free to leave a comment below and I’d be happy to respond to you.

And, now I’m off to another SharePoint project…

The post Modern Microsoft SharePoint Design: Overcoming Common Challenges – Part 3 appeared first on InFocus Blog | Dell EMC Services.


Update your feed preferences


   

   


   


   

submit to reddit
   

Related:

Header Rewrite SG300

I need a solution

Hello together,

i have a problem with a sepecific Homepage where the http header is been rewritten by onknown reasons. May anyone can help me here.

Has the bluecoat any options to do such thing ? I’ve only found a option in the VPM (“Add Request Header Object”) but there isn’t such thing configured. So the normal header of the website should be used.

False Header after access the website through the Proxy:

User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.1; WOW64; Trident/7.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; .NET4.0C; .NET4.0E; MAFS; InfoPath.3; Open Codecs 0.85.17777)

This has to be the header instead:

User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; Trident/7.0; rv:11.0) like Gecko

0

Related:

Event ID 6457 (Windows SharePoint Services health model)

Event ID 6457 (Windows SharePoint Services health model)
Windows SharePoint Services 3.0

Applies To: Windows SharePoint Services 3.0

 

Topic Last Modified: 2008-04-27

The Windows SharePoint Services Tracing (SPTrace) service is used by Windows SharePoint Services 3.0 to manage trace output of the call stack. When trace logging is enabled, administrators can specify the path used to store the trace logs. This log file is reused by many applications that are built on top of Windows SharePoint Services 3.0.

Event Details  

Product:

Windows SharePoint Services

ID:

6457

Source:

Windows SharePoint Services 3

Version:

12.0

Symbolic Name:

ULSEvtTag_6457

Message:

Not enough free disk space available. The tracing service has temporary stopped outputting trace messages to the log file. Tracing will resume when more than %1 MB of disk space becomes available.

Resolve Free up disk space or relocate the trace log

Windows SharePoint Services 3.0 could not write to the trace log. This trace log contains information that is useful in troubleshooting issues.

Free up drive space

You can free up space on the drive containing the trace log by removing unneeded files. To perform this procedure, you must be a member of the Administrators group on the local computer.

Relocate the log file

You can change the location of the trace log to a partition that has more drive space.

To change the location of the trace log file

  1. In Central Administration, on the left navigation pane, click Operations.

  2. On the Operations page, in the Logging and Reporting section, click Diagnostic logging.

  3. On the Diagnostic Logging page, in the Trace Log section, type the new location for the trace log file in the Path box.

  4. Click OK.

Verify

Ensure that Windows SharePoint Services 3.0 can create, and write to, the trace log file.

To check if Windows SharePoint Services 3.0 can create, and write to, the trace log file

  1. In the SharePoint Central Administration Web site, on the left navigation pane, click Operations.

  2. On the Operations page, in the Logging and Reporting section, click Diagnostic logging.

  3. On the Diagnostic Logging page, in the Trace Log section, copy the path to the trace log file from the Path box.

  4. In Windows Explorer, navigate to the trace log file by using the copied path and open the file in Notepad, or another text editor.

    You should see log entries in the log file for events after the time that logging failed.

Related Management Information

Diagnostic system (Health model)

Windows SharePoint Services 3.0 health model

Related:

Event ID 7399 (Windows SharePoint Services health model)

Event ID 7399 (Windows SharePoint Services health model)
Windows SharePoint Services 3.0

Applies To: Windows SharePoint Services 3.0

 

Topic Last Modified: 2008-12-05

Several features of Microsoft Windows SharePoint Services 3.0 rely on scheduled background processes called timer jobs. Administrators can configure and schedule timer jobs by using Central Administration. When you use the Services on Server page in Central Administration to start or stop a service, a timer job is used to perform this action.

To improve the performance of Windows SharePoint Services 3.0, much of the data in the configuration database is kept in a local file-system cache, called the configuration data cache. Windows SharePoint Services 3.0 uses the timer service to keep this cache synchronized with the configuration database. Alternate access mapping is a feature of Windows SharePoint Services 3.0 that enables administrators to configure a load-balanced system by mapping an incoming URL to alternate URLs used by Windows SharePoint Services. Windows SharePoint Services enables administrators to create new SharePoint sites. Site owners and (depending on the site settings) site visitors can also create subsites.

Event Details  

Product:

Windows SharePoint Services

ID:

7399

Source:

Windows SharePoint Services 3

Version:

12.0

Symbolic Name:

ULSEvtTag_7399

Message:

%1

Diagnose

There was one or more problems in Windows SharePoint Services 3.0. The error can be caused by one or more of the following. Note: Investigate the failure in this order:

  • The Windows SharePoint Services Administration service is stopped or disabled.

  • The farm service account has insufficient permissions to write to the configuration data cache.

  • An alternate access mapping update failed.

  • Failed to create a SharePoint site.

  • A service instance provisioning failed.

The Windows SharePoint Services Administration service is stopped or disabled

In the Services MMC snap-in, check the “Windows SharePoint Services Administration” service. It should be started and configured as “Automatic”. To start the service, use the section titled Start the administration service.

The account has insufficient permissions to write to the configuration data cache

  1. Navigate to the %systemdrive%\inetpub\wwwroot\wss\config directory and open its property pages.

  2. On the Security tab, check that the following accounts have these permissions (see table below).

  3. To assign the correct rights see the section entitled Assign sufficient permissions to the configuration data cache.

 

Account

Permissions

WSS_ADMIN_WPG

Read and Write

WSS_RESTRICTED_WPG

Read and Write

An alternate access mapping update failed

Look in the Windows Event log for any events with the Source = “Windows SharePoint Services 3” and event ID = “6397”. These events will provide information needed to troubleshoot the problem, such as the Web application affected. To fix this, see the section titled Complete the alternate access mapping update.

You must be a member of the SharePoint Administrators group to perform this task:

To view alternate access mapping settings

  1. In Central Administration, click Operations.

  2. On the Operations page, in the Global Configuration section, click Alternate access mappings.

Failed to create a SharePoint site

Look in the Windows Event log for any events with the Source = “Windows SharePoint Services 3” and event ID = “6141”. These events will provide information needed to troubleshoot the problem, such as the Web site affected.

Resolve

To resolve this issue, use the resolution that corresponds to the cause you identified in the Diagnose section. After performing the resolution, see the Verify section to confirm that the feature is operating properly.

 

Cause

Resolution

The Windows SharePoint Services Administration service is disabled

Start the administration service

The service account has insufficient permissions to write to the configuration data cache

Assign sufficient permissions to the configuration data cache

An alternate access mapping update failed

Complete the alternate access mapping update

A service instance provisioning failed

Reprovision the service instance

Start the administration service

You must be a member of the SharePoint Administrators group to perform this action.

To start the Windows SharePoint Services Administration service (if you can use at least one instance of Central Administration)

  1. Ensure that you can logon to at least one instance of Central Administration.

  2. In Central Administration, click Operations.

  3. On the Operations page, in the Topology and Services section, click Services on server.

  4. On the Services on server page, select the server you want to start the administration service on from the Server drop-down list.

  5. Select the Custom option.

  6. In the Start services in the table below section, next to Central Administration, click Start.

If the Windows SharePoint Services 3.0 Administration service still will not start, you need to reprovision Windows SharePoint Services 3.0. To do this, see the Reprovision the service instance section.

Assign sufficient permissions to the configuration data cache

Ensure that the WSS_ADMIN_WPG and WSS_RESTRICTED_WPG local groups have been granted permissions to write to the %systemdrive%\inetpub\wwwroot\wss\config folder.

You must have Modify permissions to the folder to perform this task.

Complete the alternate access mapping update

The event string for event 6397 will provide the alternate access mapping that failed. You can try to re-create the mapping using Central Administration.

You must be a member of the SharePoint Administrators group to perform this task.

To view or change alternate access mapping settings

  1. In Central Administration, click Operations.

  2. On the Operations page, in the Global Configuration section, click Alternate access mappings.

  3. To edit the mapping, click the mapping.

Reprovision the service instance

On the specified server, re-provision the service by using the Psconfig command. For more information about this command-line operation, see Command-line reference for the SharePoint Products and Technologies Configuration Wizard (Windows SharePoint Services).

You must be a member of the SharePoint Administrators group to perform this action.

To reprovision Central Administration by using the Psconfig command-line tool

  1. On the affected server, navigate to the Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN directory.

  2. Open the command line and type the following: psconfig -cmd adminvs -unprovision

  3. This will unprovision the service instance.

  4. Open the command line and type the following: psconfig -cmd adminvs -provision -port-windowsauthprovider onlyusentlm

  5. This will reprovision the service instance. The administration service should now work.

Verify

If the SharePoint Administration Service was restarted, run the Stsadm command stsadm -o execadmsvcjobs to ensure all tasks that required the administration service have been completed.

You must be a member of the SharePoint Administrators group to perform this task.

Related Management Information

Deployment and topology (Health model)

Windows SharePoint Services 3.0 health model

Related:

Event ID 6875 (Windows SharePoint Services health model)

Event ID 6875 (Windows SharePoint Services health model)
Windows SharePoint Services 3.0

Applies To: Windows SharePoint Services 3.0

 

Topic Last Modified: 2008-04-27

Windows SharePoint Services 3.0 enables you to bind an event handler to an event host (such as an entire site), a list, or a document library. For example, with this feature, you can use document library events to start other processes, such as workflow processes.

Event Details  

Product:

Windows SharePoint Services

ID:

6875

Source:

Windows SharePoint Services 3

Version:

12.0

Symbolic Name:

ULSEvtTag_6875

Message:

Error loading and running event receiver %1 in %2. Additional information is below.\n\n%3

Diagnose

One of two problems occurred. Either an event receiver raised an exception or an event receiver assembly could not be loaded. Determine which assembly was faulty, determine whether it was a Windows SharePoint Services 3.0 assembly, and then determine its status.

To determine the correct resolution

  • If the assembly cannot be found, or if it is corrupt, and it is not a Windows SharePoint Services 3.0 assembly, then you must uninstall the faulty assembly.

  • If the assembly cannot be found, or if it is corrupt, and it is a Windows SharePoint Services 3.0 assembly, then you must repair the Windows SharePoint Services 3.0 installation to restore or repair the assembly.

To determine which event receiver raised the exception and if it was a Windows SharePoint Services 3.0 assembly

  1. You can find the assembly name in the event string for the event receiver in event 6875 that has a source of “Windows SharePoint Services 3”.

  2. In Windows Explorer, on the Windows partition, in the WINDOWS\assemblyfolder, look for the assembly name in the list. If the assembly name begins with “Microsoft.Sharepoint.” then the assembly is a Windows SharePoint Services 3.0 assembly. If it does not, it might be a vendor-supplied assembly. Go to step 5 to determine the supplier of the assembly.

  3. Right-click the assembly and click Properties.

  4. In the Properties dialog box, on the Version tab, click Company Name in the Items name list. The Value box will display the name of the company that created the assembly.

    Note:
    The supplier might not have filled in this information.

Resolve

To resolve this issue, use the resolution that corresponds to the cause you identified in the Diagnose section. After performing the resolution, see the Verify section to confirm that the feature is operating properly.

 

Cause

Resolution

The third party assembly cannot be found, or it is corrupt

Contact the manufacturer of the faulty event receiver

The Windows SharePoint Services 3.0 assembly cannot be found, or it is corrupt

Repair Windows SharePoint Services installation

Contact the manufacturer of the faulty event receiver

If the faulty assembly is corrupt, and it is not a Windows SharePoint Services 3.0 assembly, you should contact the manufacturer of the faulty event receiver assembly for more information.

Repair Windows SharePoint Services installation

If the faulty assembly is corrupt, and it is a Windows SharePoint Services assembly, then you must repair the Windows SharePoint Services installation to restore or repair the assembly.

Note:
Repairing the installation will require you to restart the server. Web application modifications and other settings changes will be preserved. You must be an administrator on the server to perform this task.

To repair the Windows SharePoint Services installation

  1. Open Add or Remove Programs.

  2. Select Microsoft Windows SharePoint Services 3.0 from the list and click Change.

  3. In the Microsoft Windows SharePoint Services 3.0 wizard, select the Repair option and click Continue.

Verify

After the event handler assembly is either repaired or removed from all servers, retry the operation that triggered the event handler. These events should not continue to appear in the Windows event log.

Related Management Information

Event handlers (Health model)

Windows SharePoint Services 3.0 health model

Related:

Event ID 6142 (Windows SharePoint Services health model)

Event ID 6142 (Windows SharePoint Services health model)
Windows SharePoint Services 3.0

Applies To: Windows SharePoint Services 3.0

 

Topic Last Modified: 2008-04-27

When Windows SharePoint Services 3.0 is in Active Directory account creation mode, any user added to a site is automatically added to the Active Directory organizational unit identified for use by Windows SharePoint Services 3.0. When running in Active Directory account creation mode, every application pool that contains one or more sites must use an account that has permissions to create, read, and update accounts in the Active Directory organizational unit that the domain administrator configured for Windows SharePoint Services 3.0.

Event Details  

Product:

Windows SharePoint Services

ID:

6142

Source:

Windows SharePoint Services 3

Version:

12.0

Symbolic Name:

ULSEvtTag_6142

Message:

Insufficient permission to read user data for %1\\%2 from Active Directory.

Resolve Assign the application pool account sufficient permissions

In order for Windows SharePoint Services 3.0 to have permissions to create accounts in the sharepoint_ou organizational unit, the identity account for the SharePoint Central Administration v3 application pool and the identity accounts for any Web applications must have the correct permissions delegated to it.

To see which account is being used by the application pool for the site where you could not add a user

You must be a member of the SharePoint Administrators group to perform this task.

  1. In Central Administration Web, on the left navigation pane, click Application Management.

  2. On the Application Management page, in the SharePoint Site Management section, click Site collection list.

  3. On the Site Collection List page, you will see the site collections listed for a specific Web application. If you do not see the site collection that contains the site where you could not add a user, then click the drop-down list next to Web Application to switch to another Web application.

  4. On the left navigation pane, click Application Management.

  5. On the Application Management page, in the SharePoint Application Management section, click Web application list. The name of the Application pool will be to the left of the URL.

  6. In Internet Information Services Manager, expand the server node and then expand the Application Pools node.

  7. Right-click the application pool and click Properties.

  8. In the Properties dialog box, on the Identity tab, the account is shown in the User name box.

Verify

Ensure that a new user can be added to an end-user-accessible site. The action should succeed without error.

You must be a site administrator to perform this task.

To check if a new user can be added to an end-user-accessible site

  1. In the top level page of the site, on the left navigation pane, click People and Groups.

  2. On the Peoples and Groups page, click New, and then click Add users.

  3. On the Add Users page, type the user name in the Users/Groups box.

  4. Click the name-check icon to the right Users/Groups of the box.

If the name resolves (is underlined), the problem has been fixed.

Related Management Information

Active Directory Integration (Health model)

Windows SharePoint Services 3.0 health model

Related: