SharePoint 2010 – How to create vanity URL for sub site

How to create a short URL or vanity URL for SharePoint Site, can be done, but it is NOT done through SharePoint. You would create it through IIS.

I don’t have my SharePoint installation in front of me so am doing this from memory, thus not entering the exact step by step at the detail I normally do. Email me if you have questions.

To understand what we are doing below, we are going to create one IIS virtual empty site for each sub-site you want a vanity URL for, and simply redirect that site to the exact absolute URL of the sub-site. We will create one application pool that is separate from the existing SharePoint application pools, and all vanity URLs share that one app pool to save resources.

1. Go to IIS.
2. Go to SITES right click and ADD a Web Site.
3. Name = SharePointVanityURLs  (This is so the App Pool can be named this, and they will all share the one app pool to save memory, you will rename this site to your first redirected hostname later)
4. Create New Application Pool = SharePointVanityURLs
5. Physical Path = c:\inetpub\wwwroot\wss\VirtualDirectories\1stVanityName
6. Host Name: 1stVanityName
7. OK
8. Click on your new web site.
9. Right click and select RENAME and change the name of the web site to 1stVanityName.
10. In the Actions Pane click Edit Permissions – Add Authenticated Users and click OK.
11. Click on your new web site.
12. In IIS section click Authentication – disable anonymous (unless using it) – enable Windows Authentication.
13. Still focused on the Windows Authentication in the right pane click Advanced Settings and deselect Enable Kernel-mode authentication.
14. Click on your new web site.
15. In IIS section, click HTTP Redirect.
16. Check Redirect requests to this destination.
17. Enter your absolute URL to your sub-site without the home page entered.
18. Check Redirect all requests to exact destination.
19. In the right pane click Apply.
20. Click on your new web site.
21. Right click and select Manage Web Site – Restart.
22. Enter a DNS record for this new vanity URL or short URL with an IP address that points to your Web Front End server or if using Load Balancing your VIP address.
23. Flush DNS server cache and client cache if needing to test right away. Client is Command Prompt type IPCONFIG /flushdns .

Repeat steps above for each vanity URL, but the remain web sites on #4 select to use the existing App Pool “SharePointVanityURLs” instead of creating new ones.

That’s it, it is that easy

SSRS Scale-out Deployment–How to remove Instance

If you need to remove a SSRS SQL Server database instance from Reporting Services Configuration Manager such as due to migrating a RS database from one server to another, you can do so by running the RSKeyMgmt command.

On your Report Server, open a command prompt and enter the following to find the GUID you want to remove.

RSKeyMgmt –l

The above parameter is a lower case “L” not a one.   That will return your list of machine instances. Mark and copy the GUID of the instance to remove. Then enter the following to remove that instance from that Report Server’s configuration.

RSKeyMgmt –r <GUID>

Yes or No: Y

Now your instance is removed from this RS configuration.

Reference Material:  http://msdn.microsoft.com/es-py/library/ms162822(v=SQL.110).aspx

SharePoint 2010 how to clear Config Cache.ini

There are many times you will need to clear your Configuration Cache ( Cache.ini ) on all your SharePoint servers, such as when a timer service is stuck in a stopping, starting or pausing state.

Personally I like to make clearly the Cache.ini on all servers apart of a monthly maintenance schedule along with applying windows updates. But in reality should not be neccessary regularly.

1. IMPORTANT STEP: Stop the Timer Service (OWSTIMER) service on ALL SharePoint servers in the farm.
2. Open windows on all SharePoint servers to the path Cache.ini is stored in, this can sometimes vary so search for it on C.
   
3. In SharePoint 2007 it is C:\Documents and Settings\All Users\Application Data\Microsoft\SharePoint\Config\GUID
   
4. In SharePoint 2010 it is C:\ProgramData\Microsoft\SharePoint\Config\GUID
   
5. Take a backup COPY of each cache.ini file and the XML folders and files.
   
6. Delete all the XML files from the directory, NOT the cache.ini.
   C: Drive:\ProgramData\Microsoft\SharePoint\Config\GUID
   
7. Open the cache.ini with Notepad and reset the number to 1 and press enter.
   
8. Save and close the file.
   
9. Perform the steps above on all SharePoint servers containing the cache.ini file.
   
10. Start the Timer Service OWSTIMER service on the SharePoint servers and wait for XML files to begin to reappear in the directory.

Important to remember that you cannot just do this on one server but all that contain the cache.ini file. Also you must delete the XML file prior to changing the cache.ini file.