Showing posts with label Sharepoint. Show all posts
Showing posts with label Sharepoint. Show all posts
11 Dec 2014
22 Aug 2014
SharePoint AAM for Dummies
I've never really understood Alternate Access Mapping called AAM. But when I started to use UAG and the SharePlus App it was necessary to understand the concept of AAM better.
I will not talk about how to configure AAM or the bindings in the IIS. There are lots of stuff out there. I want you to undestand the concept.
So I want to tell you how I made me understand AAM. There are three features of AAM
I will not talk about how to configure AAM or the bindings in the IIS. There are lots of stuff out there. I want you to undestand the concept.
So I want to tell you how I made me understand AAM. There are three features of AAM
- Internal URL
- Public URL
- Zone
- The internal URL is the URL that the SharePoint Server understands & accepts
- The public URL is the URL that the clients outside in the world knows
- A Zone is a logical container for a public URL with a name like "Interner" or "Extranet". It does nothing really special. You have 5 zones in SharePoint, means a max. of 5 public urls.
Explain AAM with some analogies
My name is Ihsan Baris. So when someone calls me "Baris" or "Ihsan" I'll respond to him. Some friends and my brother are calling me also "Biggy". Don't know why but I already accepted the nickname. These are my internal names.
So when a Japanese tries so pronounce my name, he would say "Balusu". If someone calls me "Balusu" I would not respond to him, although he wants to contact me. This is a public name for a Japanese.
So what I need is a mapping between the public and the internal name. Here comes AAM. A translator tells me that "Balusu" means "Baris" in Japanese, so I make the connection in my mind. In the AAM configuration it would look like:
Adding balusu as internal url to the default zone |
Now I recognize the name "Balusu" but I'll respond to this name always with: Yes I'm Baris and not with Yes I'm Balusu.
In an real example the client is typing http://balusu, the server gets the request but renders all links within the content with http://baris.
Making balusu public |
Real World Example 1
- Assume we have a SharePoint WebApplication with http://sharepoint for internal users.
- Now we want also external users to connect to our SharePoint with https://gate.sp.company.com.
- We don't want to deal with certificates and terminate the ssl on a proxy server like UAG. The UAG then rewrites the request to http://gate.sp.company.com and points to SharePoint Server.
- The SharePoint server returns all links with https.
The AAM configuration for this example would look like
Now we have 2 Urls which our clients know (Public URLs)
- http://sharepoint
- https://gate.sp.company.com
But we have 3 Url which SharePoint has to know because the UAG rewrites the url.
- http://sharepoint
- http://gate.sp.company.com
- https://gate.sp.company.com
And we know that we have to respond with https://gate.sp.company when we get a request with http://gate.so.company.com.
Real World Example 2
An other example is when you extend your web application. You can extend a web application if you want to have two diffent types of authetication e.g.:
- Windows Authentication for internal users
- Form Authetication for external users.
SharePoint makes then 2 web applications referencing the same content.
This example is easy. We have 2 public urls and SharePoint has to know both. This means we need 2 internal urls and 2 public urls.
When do you have to pay attention
- Web Service Calls: When a webservice call is made, there can be URLs as parameter within the web service call. Web Service calls are used by Mobile Apps like SharePlus or Colligo to get the lists and sites.
So when you enter the URL https://gate.sp.company.com into an app it will send a webservice call to https://gate.sp.company.com/xxx. As SharePoint does not know the https URL (no internal url) you will get an error here. - Search: I think there is a problem with contextual search and non-default zone url. You can only do contextual search within the URL of the default zone. Contextual search means e.g. a search within a list or site. Take care to put the main public url into the default zone.
- IIS Binding: If you add an internal URL into AAM it is not automatically binded within IIS. You have to do that manually. SharePoint AAM does not any changes within IIS.
- Aliases: If you have an alias like http://sharepoint for http://sharepoint.company.com you have to configure both URL in the AAM.
http://blogbaris.blogspot.com/2013/07/sharepoint-alternate-access-mapping-aam.html
3 Aug 2014
Moving SP 2010 from one to another domain
1. Change primary site collection administrator from domain user account to local account
Application Management --> Site Collection Administrators
2. Stop these services
- SQL Server
- SharePoint Administration
- SharePoint Host Controller
- SharePoint Search Service
- SharePoint Time Service
- SharePoint Tracing Service
3. Full backup SharePoint database
4. Change domain for SharePoint
5. Restart and login as administrator
6. Check above services if they started successfully. If not change service account from old domain user account to new domain user account
7. Change Alternate Access Mapping by opening SharePoint Central Administration --> Application Management -->Configure Alternate Access Mapping
URL Protocol: -->intranet.newdomain.local
Zone: Intranet
8. Check DNS record for SharePoint server in new domain
9. Test by entering new address into broswer
Good luck
Application Management --> Site Collection Administrators
2. Stop these services
- SQL Server
- SharePoint Administration
- SharePoint Host Controller
- SharePoint Search Service
- SharePoint Time Service
- SharePoint Tracing Service
3. Full backup SharePoint database
4. Change domain for SharePoint
5. Restart and login as administrator
6. Check above services if they started successfully. If not change service account from old domain user account to new domain user account
7. Change Alternate Access Mapping by opening SharePoint Central Administration --> Application Management -->Configure Alternate Access Mapping
URL Protocol: -->intranet.newdomain.local
Zone: Intranet
8. Check DNS record for SharePoint server in new domain
9. Test by entering new address into broswer
Good luck
Clone virtual machines in Hyper-V
As you know Hyper-V does not have an option to clone virtual machines, except when you use SCVMM. Because of this many admins need to use tricks so they don’t have to install and configure a new virtual machine from scratch every time they need a copy of Windows 7, or any other operating system. In this guide I’m going to show you two of the most popular ones, and they free. For this lab I have a Hyper-V server running on Windows Server 2008 R2 SP1, and a Windows 7 machine (reference machine) for cloning called Windows.7.Enterprise.
In this first example is important that the virtual machine should not have snapshots. The reference virtual machine (Windows.7.Enterprise) is located on the Hyper-V host C: drive, in a folder called HV-Machines. Inside HV-Machines folder create another folder and give it a distinctive name, so you can recognize it. I called mine Windows 7 Clone. Now copy the virtual disk (the *.vhd file) from the Windows.7.Enterprise machine to the Windows 7 Clone folder. If you want to, you can rename the copied virtual disk after the folder name, but is not necessary, is just that I like to have the virtual disk files named after the virtual machine that I will create.
Open Hyper-V manager and create a new virtual machine from the Actions pane. Give the virtual machine a name, and I recommend you name the virtual machine after the folder we just created “Windows 7 Clone”. It will be much easier when troubleshooting. Now choose to store the virtual machine in the folder “Windows 7 Clone”. This is only if you want to have the configuration files and the virtual disk in the same folder.
Continue the wizard until you reach the Connect Virtual Hard Disk page. Here instead of creating a new virtual disk we will go with the second option and use an existing virtual disk. Click the Browse button and select the virtual disk we just copied in the “Windows 7 Clone” folder.
Finish the wizard. Now we have an exact copy of the reference virtual machine. Don’t forget to change its name an IP address, if is a static one.
In the second example we are going to use the Hyper-V export function to clone the virtual machine. Using this method you can have snapshots and still being able to clone the machine. To start click the reference virtual machine (Windows.7.Enterprise) in the Hyper-V console, then in the Actions pane click the Export link.
On the Export Virtual Machine window click the Browse button and choose a place where to save this virtual machine, then click Export to start the process. Is going to take a while so be patient. When the export process is finished the Cancel export link in the Actions pane will disappear.
Back in Hyper-V manager console click the link Import Virtual Machine in the Actions pane.
In the window that opens we have two radio buttons and a check box. The first radio button, Move or restore the virtual machine (use the existing unique ID) is going to import the virtual machine and preserve its ID’s. This option is used when importing to a different Hyper-V server. If you import a virtual machine, and on the same Hyper-V server that ID already exists you will get an error message, and the import process fails.
The second radio button, Copy the virtual machine (create a new unique ID), like the name implies, it will create a new ID for the virtual machine you are importing. This is used when you use the same Hyper-V host to export and import virtual machines, like in our case. The check box is there if you want to import the same virtual machine for more than one time, without going through the export process again. Since we are using the same Hyper-V host to import the virtual machine, and another one (the reference machine) exists with the same ID, select the second radio button. Now click Browse and select the exported virtual machine folder, then hit Import. I changed the folder name because this is how I’m going to call my virtual machine in the Hyper-V console.
Looks like I have a warning message after the import process finished. This is because I forgot to unmount the Windows 7 ISO from the reference virtual machine before exporting. I’ll just ignore it and click Close.
The last step is to rename the virtual machine in the Hyper-V console so we can distinguish it from the original one. Again don’t forget to change its name and IP address if is a static IP.
That’s it folks, hope it was informative for you.
http://www.vkernel.ro/blog/clone-virtual-machines-in-hyper-v
5 May 2014
SharePoint service accounts
http://sharepointgeorge.com/2010/installing-sharepoint-2010-privilege-service-accounts/
http://onpointwithsharepoint.blogspot.com/2013/01/sharepoint-2010-service-accounts.html
http://onpointwithsharepoint.blogspot.com/2013/01/sharepoint-2010-service-accounts.html
17 Mar 2014
Hide Title field in SharePoint
Title field in SP can not be deleted but you can hide it by follow the below steps
Goto Advanced Settings and change the Allow management of content types? to Yes. Then click on Item under Content Types. Click on Title. Choose Hidden. This will disallow users from ever seeing or filling in the Title section. Make sure you go back and change the allow management of content types back to no. Hope this helps!
Goto Advanced Settings and change the Allow management of content types? to Yes. Then click on Item under Content Types. Click on Title. Choose Hidden. This will disallow users from ever seeing or filling in the Title section. Make sure you go back and change the allow management of content types back to no. Hope this helps!
13 Jan 2014
Edit email address for sharepoint 2010 user
A user's Email Address is stored within a profile property. By default a user isn't allowed to change his or her own e-mail address. The email address (Work e-mail) and whether or not user's can change their own can be specified in the settings of the User Profile Service Application.
- (As an administrator) open Central Admin
- Under "Application Management" click "Manage Service Applications"
- Locate and click the link "User Profile Service Application". If this one is not there you haven't created a User Profile Service Application yet.
- Under "People" there are two relevant links here. The first is "Manage User Properties", the second is "Manage User Profiles"
- Under "Manage User Properties" you can specify the settings for the Work e-mail property (i.e. whether or not the user is allowed to edit his or her own e-mail address).
- Under "Manage User Profiles" you can locate a user's profile and edit the e-mail address from there
By default it could take up to one hour to "see" the new e-mail address througout all web applications bound to the user profile service application. A timer job is taking care of this and you could kick this one of to run manually once by going to "Check Job Status" screen in Central Admin (_admin/Timer.aspx). Here locate the job definition with the title "User Profile Service Application - User Profile to SharePoint Full Synchronization", open the "Edit Timer Job Page" by clicking on the Job's name and then click the "Run Now" button.
Hope this helps!
10 Dec 2013
8 Dec 2013
1 Dec 2013
10 Nov 2013
"Setup Groups for this Site"
If you change your mind and want to create unique groups for sharepoint site after it was created there will be an issue because "Setup Groups for this Site" disappeared. Even you can create groups and make them to be default groups for the site but "Add users to Sharepoint Group" will not be available from drop down box of "your own" Site Owners group.
Luckily you can still get "Setup groups for this site" page appeared by this url
siteurl/_layouts/permsetup.aspx
Hope it will help
Cheers, BB
Luckily you can still get "Setup groups for this site" page appeared by this url
siteurl/_layouts/permsetup.aspx
Hope it will help
Cheers, BB
24 Oct 2013
23 Oct 2013
Increase size of SP template
To increase the maximum size, simply run the following stsadm command (from the C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN directory) replacing the propertyvalue to the new maximum size (in bytes):
stsadm -o setproperty -propertyname max-template-document-size -propertyvalue 150000000
11 Sept 2013
12 Aug 2013
Use list in parent site in custom list lookup field
What you need to do is create a site column at the top level site (IT) which is a lookup to your XXX list, then in your sub site you add the site column into your custom list.
From the parent site (the top level site where the list resides)
Go to Site Actions > Site SettingsUnder Galleries select Site ColumnsClick Create at the top of the listGive the column a title you will reference in your "child" listsSelect Lookup as the column typeSelect the site's column group to categorize the new columnSelect the list to lookup from the "Get information from" dropdownSelect the column of the lookup list you want to reference as the key in your "child" lists(I selected "Title (linked to item)" so that you can easily reference the parent item from your child list item)Click OK
From the sub-site (site that you need to create the child list)
From the All Items list vies, select Settings > List SettingsAt the end of the Columns list select Add from existing site columnsYou can filter the selections by selecting the group you associated the parent column with from the dropdownSelect the site column you created above and click the Add buttonClick OK and there you have it.
25 Jul 2013
Increase the SharePoint 2010 Upload File Size Limit
http://angler.wordpress.com/2012/03/21/increase-the-sharepoint-2010-upload-file-size-limit/
The Problem.
For teamsites and collaborations, sometimes it can be useful to upload big file size documents – which is allowed only partially by SharePoint and IIS. They both have different default settings for the maximum upload file size of a single document or file. They are:
- SharePoint Server 2010: 50 MB
- IIS7: ~30 MB
So, when trying to upload a big document, this results in the following error:
85 MB is simply too much for the above mentioned settings. Now, the solution section will show you how to fix this.
The Solution.
The good news is: This can be custom tailored to your needs, by simply following 3 steps. Here comes the first step:
1. Increase the SharePoint Upload Limit via Central Administration
First, you must increase the SharePoint 2010 upload limit.
- Central Administration
- “Manage Web Applications”
- Select desired web application row (don’t click on the title, just select)
- “General Settings” in the ribbon
- Under Maximum Upload Size, change the setting to the desired value (e.g. 200 MB in our example)
- “OK”
Now, the web app is equipped for receiving large files, but IIS7 will still prohibit it, resulting in the same error message as above. So, let’s move on to step 2.
2. Increase the IIS7 request length
Use the following command on the machine you are running the IIS 7:
%windir%\system32\inetsrv\appcmd set config -section:requestFiltering -requestLimits.maxAllowedContentLength:valueInBytes
In our case, we’ll simply put 200x1024x1024=209715200 bytes.
You will receive a confirmation message after applying the command. Please bear in mind that you will need to run the cmd.exe in administrator mode.
3. Increase the IIS7 connection timeout length (optional)
One more thing to keep in mind is the connection timeout settings: When you upload large files, depending on your connection speed it can happen that the connection times out. If you want, you can increase the connection timeout to a larger value. The standard is 120 seconds. This step is optional, but can become required if you have users with low speed internet connections.
- Open IIS
- Select the Web Application
- Click on Advanced Settings
- Expand Connection Limits
- Set the new value for Connection Time-out (seconds)
This is it – all done!
You users will now be able to upload larger files:
As usual, test any commands, configuration and settings on a test environment before applying them in production. Applying request lengths bears also some security implications to keep in mind. Use any advices and configurations at your own risk and evaluate risks before applying them.
18 May 2013
26 Apr 2013
Subscribe to:
Posts (Atom)