Share Point Server 2010 Alternate Access Mapping

Hello Experts, i have this question. I have to change my MOSS 2010 URl to some other name. But by default it picks up the servername. I need to install sharepoint on the other machine but i want the names of the url still having the same old server name.
Say my old URL is : http://OLDServer/SitePages/Test.aspx. After deploying my sites to other machines, it will be changed to http://NewServer/SitePages/Test.aspx. I want to change it back to http://OLDServer/SitePages/Test.aspx. So in a way, user will hit the old url and it will route to new one. Also I will discard our old server.

 I know about Alternate access mapping feature but i need to know exact step by step instruction, also how i will make a DNS entry in the DNS server. If possible, please give me complete steps.


Thanks Much.
resolution11Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

DBengineerCommented:
If I understood your questions correctly, following should work.

You have two WFE in two different farms under one domain/DNS and assuming it is not load balanced.

Create an A record in your DNS
http://www.youtube.com/watch?v=WYj7KSIn2Xo

Create two A records for example
•      Oldserver.mydomain.local ¿ point IP to ServerA (192.168.1.10)
•      Newserver.mydomain.local ¿ point IP to ServerB (192.168.1.20)

Note: mydomain.local is the domain name

OLD FARM:
(http://oldserver.mydomain.local) Alternate access mapping of ServerA


NEW FARM:
(http://newserver.mydomain.local) Alternate access mapping of ServerB


Cut over steps:
If you just wanted to point the http://newserver.mydomain.local and http://oldserver.mydomain.local pointing to servers other way round, make the following changes.
In the DNS change the IP address of DNS A record oldserver pointing to IP address of ServerB
In the DNS change the IP address of DNS A record newserver pointing to IP address of ServerA

Example:
•      Oldserver.mydomain.local ¿ point IP to ServerB (192.168.1.20)
•      Newserver.mydomain.local ¿ point IP to ServerA (192.168.1.10)

Sorry if this is not what you expected.
0
resolution11Author Commented:
Thanks DBenginner, Thanks for your answer. Creating DNS entries was very helpful.  Just more clarification. Yes you are right that I have WFE in two different farms under one domain/DNS and it is not load balanced. Now here is the scenario
Server A (OLD Server)(192.168.1.10) has url http://oldserver.mydomain.local 
Server B (New Server)(192.168.1.20)has url http://Newserver.mydomain.local 
Just mentioning my ask again: I need to deploy my sharepoint sites to new Server B. Once done, i still need to keep the url to show the old server name as users only know that name.
Once done, i will shutdown or remove the old server.
Steps:
1.    Create two A records for example
•      Oldserver.mydomain.local  point IP to ServerA (192.168.1.10)
•      Newserver.mydomain.local  point IP to ServerB (192.168.1.20
Q: will there not be any conflict for OLD server as its name already exits on DNS. Should i not just create 1 DNS entry for the new server only.

2. Configuring AAM:
Q: Do i need to go to both servers and do that or just the new Server.
Q: Do i need to do any bindings in IIS

Please bear with me. I am bit confused here.
And also can you please clarify the Last Part.

Thanks Much,
Harman
0
DBengineerCommented:
Please ignore the http://Newserver.mydomain.local if you are not going to keep the OLD FARM alive and if you are completely decommisioning that for good.

NEW FARM:

Make sure the AAM settings on the NEW farm has the same logical DNS name.

Once you are ready to do the production cut over, point the exisitng same (URL) A record to the new ipaddress of the new WFE, things should work fine as it used to work now.

Thanks
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SharePoint

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.