Microsoft SharePoint 2013:

CHANGE SERVER NAME:

Change the server name before changing it in SharePoint Central Administration
Restart the server.
Open cmd prompt:
Enter the command:

C:\Program Files\Common Files\Microsoft Shared\web server

extensions\15\BIN
Cd

Once the directory has been changed. Enter this command:

stsadm -o renameserver -oldservername <YourOldServerName> -newservername
<YourNewServerName>

The above will notify that the name was changed.

Change the urls in Alternative Access Mapping to access the webpage.

In this article, I would like to share the procedure to configure the alternate access mappings using
Central Administration in SharePoint 2013.
Uses of Alternate access mappings

It enables a web application that receives a request for an Internal URL in the one of the five
zones to return pages that contain links to the public URL for the Zone.

You can associate a web application by using a collection of mappings between internal and
public URLs. Internal refers to the URL of a web request as it is received by SharePoint
2013.

Public refers to the URL by which SharePoint will format links that correspond to requests
that match one of the internal URLs on that zone when it returns a response. The public URL
is the base URL that SharePoint 2013 uses in the pages that it returns. If the internal URL
was changed by a reverse proxy device, it can differ from the public URL.

Procedure to Configure alternate access mappings

Use the following procedure to configure alternate access mappings using Central Administration.
Step 1: Go to the Central Administration using a farm administrator account as shown below.

Step 2: In Central Administration, click system settings from the left navigation. Then you will be
navigated to the system settings page.

Step 3: On the system setting page, in the Farm Management section select the Configure
Alternate Access Mappings.

Step 4: When you click on the Configure alternate, you will be navigated to the Alternate access
settings page as shown below, then click on the Edit Public URL's.

Step 5: On the Edit public zone URL's page, select the site collection from the alternate access
mapping collection from the drop down as shown below:

Step 6: When you click on the change alternate access mapping collection option, you will get a
pop-up to choose the site collection as shown below. There you can select the site collection that
you want to add the URLs in Intranet, Internet, custom and Extranet.

Step 7: After selecting the site collection, you will have the option to add the URLs as shown below.

Step 8: Then give the URL in the text boxes, which zone you want to access the site and then click
Save.
Here I provided the Internet URL for public access.

Summary
In this article we have explored how to configure the alternate access mapping for a SharePoint web
application using Central Administration.

Run SharePoint Products Configuration Wizard:

Several Errors:
Document Conversions launcher Services Errors:
Open up the registry and browse to the following two keys:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office Server\15\LauncherSettings
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office Server\15\LoadBalancerSettings

In both locations, create a new DWORD (32 bit) key called AcknowledgedRunningOnAppServer. Give it
a value of 1.
Thats all there is to it. Go back to Services on Server and start the load balancer service.
Congratulations! Now ask yourself this, do you need this service in SharePoint 2013? To quote the KB:
The document-conversion services that were obsoleted in Microsoft SharePoint Server 2013 are not
secure when the services run in an environment in which the web front-end (WFE) server role is
located on the server that is running as an application server (that is, on the same server as the
services).
Maybe you would be better off heading back into Central Admin and turning it off. Its at least worth

SharePoint Server Search Error & Create Sample Data Error:

Go to :
C:\Program Files\Microsoft Office Servers\15.0\Data\Office Server\
Find the folder Analytics_+ guid.
Gave permissions to Everyone (do this at your own risk)
After this runn the configuration again There should be no more error setup was successful.

How to change the URL for SharePoint Central

Administration site

I have been working on configuring high availability for SharePoint servers (MOSS or
WSS), and for a little while I wasn't able to figure out the way to modify the URL for
SharePoint Central Administration site. So, basically you extend the Central
Administration web application (using GUI or psconfig command) to run on multiple
servers, and when you click on SharePoint Central Administration icon you're still
redirected to a specific SharePoint server instead of been redirected to the Load
Balancing URL. Anyway, as it turns out the URL has to be changed via registry on all
SharePoint servers. Weird?!
To change the URL for SharePoint Central Administration URL:

Open Registry editor

Backup the registry before making any changes!!!

Go to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Web Server

Extensions\12.0\WSS and change the value of CentralAdministrationURL to whatever
you want to be

Removing Alternate Access Mappings at command prompt:

Command:

Remove-SPAlternateURL -Identity "http://intranet.sp2013.com"

Alternate Access Mappings (AAM): Introduction

Each web application in SharePoint can be presented with up to five public
URLs. For instance, you might have allowed both intranet.local and
portal.fakedomain.com to make connections to your SharePoint 2013
portal. The public URLs are URLs that SharePoint displays through links.
Each of the public URLs must be assigned one of the five available zones.
You have to have a public URL assigned to the zone titled Default but the
others are just friendly labels that can be used in whatever fashion it makes
sense to you and your organization. The other zones are Internet,

Intranet, Extranet, and Custom. Tip: You can remember public URLs as
the addresses that are displayed by SharePoint to the users.
Each public URL has at least one internal URL that corresponds to it. The
internal URLs are the addresses that SharePoint 2013 accepts and are bound
to the SharePoint web application in IIS. Note that only the default zone that
you create when you create the web application is added to the IIS bindings
for the site in IIS. Any other alternate access mappings you create have to
be created in the bindings list for the site.
By default, when you create a public URL it also creates an internal URL in
the same zone. This is great because it bridges the connection that you
assume will be there. With both an internal and public URL for
hr.intranet.local in the same zone, a user can type in hr.intranet.local to
get to their SharePoint 2013 site, and SharePoint will recognize it as
an internal URL. Then, since its recognized as an internal URL,
SharePointdisplays the public URL registered to the same zone back to the
user in the address bar and in the links displayed on the SharePoint sites.
And since you can have multiple internal URLs pointed to the same public
URL, you can work some magic with changing the results that people type
in. This can be very helpful for teaching your users that they dont have to
type in the FQDN for the SharePoint site or for enforcing HTTPS on a
SharePoint web application.

Managing Alternate Access Mappings in

SharePoint 2013 with PowerShell
You can use PowerShell to manage all aspects of your Alternate Access
Mappings in SharePoint 2013. You can use the following cmdlets to control
your internal and public URLs: Get-SPAlternateURL, New-SPAlternateURL,
Set-SPAlternateURL, and Remove-SPAlternateURL.

List Alternate Access Mappings with PowerShell

Using the Get-SPAlternateURL cmdlet, you can find the existing AAM
settings for a web application.

You can also limit the results by zone, web application, or a mapped external
resource through the use of thezone, webapplication,
and resource parameters. The zone parameter can be used by itself or with
either the webapplication or resource parameter, but the webapplication and
resource parameters cannot be used together.

1Get-SPAlternateURL WebApplication http://portal.intranet.local Zone Default

Creating a New Alternate Access Mapping with

PowerShell
Alternate Access Mappings can be created with the NewSPAlternateURL cmdlet.
Like the Get-SPAlternateURL, you can use this command on either web
applications or external resources, but not both at the same time. Whether
youre creating your new alternate access mapping for a web application or
for an external resource, you have to supply the value for the
mandatory URL parameter.
You can also specify the zone for the new AAM with the Zone parameter.

New-SPAlternateURL WebApplication http://portal.intranet.local URL https://portal.domain

Zone Internet

If you want to create an internal URL, then you can specify that with the
Internal switch parameter. If this switch isnt used, a public URL is created.

New-SPAlternateURL WebApplication http://portal.intranet.local URL http://portal.domain Zone

Internet Internal

Change an Alternate Access Mapping with PowerShell

One of the main things you might want to change on an AAM is which zone
its registered in. You can only change the zone of an internal URL. If you
want to change a public zone URL, you would just change the URL or remove
the mapping.
Changing a zone on an internal URL makes sense because the internal URLs
are the mappings that make the translations happen between what a user
types into their browser, and what the URL looks like when it resolves. So
changing that translation is something that makes sense. Just changing the
zone of a public URL doesnt really change anything for us, since the zones
are only labels and dont have any real impact (you can have Internet traffic
coming into the Intranet zone and vice-versa).

Change the Zone of an Internal URL

1Get-SPAlternateURL http://staff | Set-SPAlternateURL Zone Custom

Change the URL of a public URL

1Get-SPAlternateURL http://mysite.local | Set-SPAlternateURL https://mysite.local

Remove an AlternateAccessMapping with PowerShell

If you realize that youve made a mistake with one of your alternate access
mapping entries, you can remove it from SharePoint. You cant remove the
entries with Remove-SPAlternateURL.

Get-SPWebApplication http://intranet.local | Get-SPAlternateURL Zone Internet | RemoveSPAlternateURL

If youre scripting this, it can be helpful to make use of the Confirm parameter to prompt before deletion to make sure that youre
aware of what youre doing. Likewise, if youre testing your code and want to
make sure your script works but not actually remove the AAM at this time,
you can use the -Whatif parameter to run through the process without
actually deleting the AAM entry.

Wrapping-Up AAM
Administering SharePoint 2013 means, more and more, learning and
embracing PowerShell. Even when working with something like Alternate
Access Mappings, which can be done from Central Administration, you can
often get more accomplished quicker by bypassing Central Administration
and just performing command line administration through PowerShell.