Tag Info

Hot answers tagged

5

There are few security risks linked to Google Analytics. Your SharePoint site will not be hacked because you use Google Analytics. You cannot be 100% sure, but the only "safe" way is running log processing software on-premise or use built-in Web Analytics. However, I believe the largest risk are concerned with the legal aspect of possibly exposing internal ...


4

I happen to have a great exposure working with the Content Deployment in an authoring and production topology: Authoring and production farm The two-farm topology is a standard Internet site topology, and it is typical of topologies that are used to publish an Internet site. It includes two server farms: one to host the authoring site collection along with ...


3

There are lots of things that are recommended to make your SharePoint intranet successful. Some are: executive buy-in, training, incremental releases and updates, proper governance/assurance (as you prefer to call it), etc... You know your company's culture best, you will need to look at what has been successful and what has been unsuccessful and try to ...


3

I would think that a 3 stage environment would make a lot of sense if you were developing an internet. The staging environment gives you complete control over the page authoring environment. As you indicated you have a separate set of permissions for the users involved with authoring. In addition, when the pages are approved in the staging environment, ...


3

Here's the short version: Create a new blank SP project in Visual Studio. Add a new module and add your master page to this (in your case a copy of the Seattle master page with your changes). Configure this module to deploy to the master page gallery. Add a new feature (site collection scoped most likely) Include the module in the feature Add a feature ...


2

Check out the Intranet blog at http://www.intranetblog.com/ they have lots of good articles and reviews that should be helpful.


2

The technology will not make it "work", that's for sure. Executive buy in is important, but even better, executive behavior. Get them to stop emailing docs and put them in the Intranet, get them to blog, etc. Basically, lead by example. If they don't no one else will do what you want. Also look for quick win mini-apps that you can whip out fast. Paid ...


2

I just picked up a copy of SharePoint Design by WROX. So far I am quite impressed. It is ideal for users that need to get up to speed with design principles and different best practices for intranet and publishing portal developmentwith MOSS. It also covers general design principles and has many references.


2

Definitely possible as long as you are covered on licensing aspects. You can set the appropriate permissions on your internal web and configure your Alternate Access Mapping correctly and have the site accessible from outside or Alternatively you can build a simple asp.net control that exposes the document library via some custom work done by you. Mind ...


2

The advantages of multiple instances are limited in the scenario you've given. You are correct in what you're implying - that you could simply have one farm, with no content deployment. Editors could see unpublished content, and other users see published. Or, as the document you linked to says, you could have one instances and deploy to a different site ...


2

I saw two good posts about this earlier in the year: http://blogs.msdn.com/b/maximeb/archive/2010/04/01/what-sharepoint-2010-looks-like-with-internet-explorer-6.aspx http://blogs.msdn.com/b/maximeb/archive/2010/07/30/what-can-work-with-internet-explorer-6-and-sharepoint-2010.aspx Tags will work, but there is so much other stufff that doesn't that it makes ...


2

Check with Configure an Alternate Access Mapping in SharePoint 2010. http://technet.microsoft.com/en-us/sharepoint/ff679917.aspx


2

this is very easy: Extend it : this article and this but if you can learn how to configure it like professionals, do these steps: 1- design you can design it in multi layer : firewall - DNS - Router - ... 2- configure it for higher security with firewall or ISA Server or other solutions : this article 3- access the site by grant permission to your ...


1

It may depend on the security setting in Internet Explorer. Go to Internet Options > Security Tab. Select the Local Intranet zone, and click Sites. Uncheck the check-box *Automatically detect intranet network" option. Close the browser, open it again and sign in. See if the Sign out option is present.


1

All three options you list will work fine against multiple farms. As much as possible I'd stick with CSOM or REST. And as you want to work with both Documents and List items the CSOM is probably the best choice.


1

I would use jQuery to inject the dialog to every external link. Add jQuery and the following script to .master page, something like: $("a:not([href^='http://current.sharepointsite.com'])").click(function(){ alert("You're about to leave SharePoint"); }); Or use some ready made jQuery plugin here.


1

i think what your refering to is Minimal Download Strategy feature. Its purpose is to speed things up by loading as little resources as possible. Minimal download strategy (MDS) is new web technology used in SharePoint 2013 to save the bandwidth traffic and quick render the pages to the clients. MDS technique use a single .aspx page ...


1

Information architecture with SharePoint is not easy when you're just starting out with the product. The used terminology alone can be very misleading. A very good resource for knowing the differences between sites, site collections and web applications can be found here: http://technet.microsoft.com/en-us/library/cc263121.aspx In general you would want ...


1

It can depend on circumstance. But normally its best to create a new site collection. Web applications are quite resource hungry, the more you have the more load you are placing on the farm.


1

The problem is you probably have a load balancer in front or juniper itself is acting as a load balancer so it is ssl from browser to load balancer/juniper and http from load balancer to web server, so the request is actually recieved as http and that code interprets it as such and calls google analytics over http. We had a similar problem with juniper. The ...


1

I would recommend you to start with on how to create a Publishing page layouts and Content Types. Try packaging them with Master page and Branding using Visual Studio and you're good to go.


1

A "stretched" farm requires a 1Gbps/1ms connection between all SharePoint Servers and the SQL Server(s), so your situation doesn't fit that. You could run multiple farms, one in each location with the most frequently used documents on the local farm.


1

It really all depends on the culture and size of the organization. However some past examples would include something like tip of the day. It can be general on how to use sharepoint, or something specific to the industry. Other items could be a stock ticker, recent management blog posts, rss feeds that are industry specific, the company in the news, links to ...


1

As Jan Maximilian Winther Kristia points out, there aren't that many security risks using Google Analytics. As it tracks traffic on an internal site, you would want to make sure that Google Search Bots are disallowed. This can be done by making a Robot.txt file which tells Google's search bots to not index this site. Another option (which is highly ...


1

You could use some JQuery magic to pull through a view on this data into your MySites. Take a look at the JQuery Library for SharePoint Web Services. No need for Thanks Marc, thought I'd get there before you ;-)


1

I guess you are looking at security rather than just branding. Depending upon the requirement you can look at the following: Each department gets it's own sub-sites. With this approach all users who have access to the Root site will be able to see data from the sub-sites as the sub sites inherit the permissions. So to make the data visible only for the ...


1

It would be handy if you could share the format of the URLs with us, as well as let us know whether the sites are located in separate Web applications. It's likely the the links work fine for internal users because they are domain joined and their Web browsers consider the sites to be in the local intranet (e.g. if the domain is called "company.com" and ...


1

For business professionals and specifically for SharePoint theres no getting around reading the 1200+ pages in Planning and architecture for Office SharePoint Server 2007


1

2 weeks is a short time to launch if you haven't done anything yet. However get the buzz out there. I find you need to get some SharePoint champions on your side, individuals in the organzaabion that simply love SharePoint (preferbly not IT) and can offer some support. People that are passionate about the product will take your cause far and lead by example. ...


1

Definitely make sure your business sponsor plays an active role as an 'evangelist' in the organization, both above and below their level. I have seen many implementations fail that don't have an engaged business sponsor, just as often as those without a business sponsor. Here's another great article from SharePoint Joel as Lori pointed out earlier. ...



Only top voted, non community-wiki answers of a minimum length are eligible