Renaming the Reporting Services computer in a Team Foundation deployment

The dashboards in SharePoint displayed reports from Reporting Services. The dashboards use a special page “TfsRedirect.aspx” which will take data from the Team Foundation Server and redirect to the correct page. These data are cached on the server hosting the SharePoint. This cache has be to cleared so that the next call to TfsRedirect.aspx will correctly retrieve the new Reporting Services computer name.This page enables access to other team project resources such as the associated SQL Server Reporting Services report folder, Team Web Access site or process guidance. You can perform the following steps to clear the cache from the server hosting the SharePoint:

1. Open a web browser.
2. Go to “http://<computer_name>/sites/<team_project_collection_name>/<team_project_name>/_layouts/TfsRedirect.aspx?tf:Type=ReportList&tf:ClearCache=1&tf:Test=1” (without the quotes).

The following are the explanations on parameters of the above URL:

1. The parameters starting with tf: are used by the TfsRedirect.aspx page.
2. The tf:Type parameter indicates the redirection type.
3. The tf:ClearCache=1 parameter indicates to clear the Team Foundation Server cache in SharePoint.
4. The tf:Test=1 parameter indicates the we only want to test the redirection and display debugging data (e.g. settings and cached data) instead of redirecting to another page.

My Tech Insights 2014 – Office 365 Edition Slides

Thank you for attending my session at Tech Insights 2014 – Office 365 Edition! I hope you have all managed to return to your daily cycles with ease after the event. It was my pleasure to have you and hope you enjoyed your time at Tech Insights 2014 – Office 365 Edition. As promised, I am posting my slides for my session. :)

Enjoy!

Download URL:

Develop, Build, Package, and Deploy SharePoint and Office Apps with Napa Development Tools

Tech Insights 2014 – Office 365 Edition

I will be speaking “Develop, Build, Package, and Deploy SharePoint and Office Apps with “Napa” Development Tools” at “Tech Insights – Microsoft Cloud Office 365 Edition”. Many thanks to the event organizer for inviting me as a speaker at the event. The event will be held at Microsoft Malaysia Sdn Bhd, Level 26, Tower 3, Petronas Twin Towers, Persiaran KLCC, 50088 Kuala Lumpur on July 9, 2014.

Session Synopsis:
One of the biggest issues in getting started with SharePoint development are the steps you need to go through, and the heavy duty machine you need to invest in, to create a development environment for a SharePoint and Office developer. With the introduction of SharePoint and Office apps, everything has changed! With the advent of apps – for both Office and SharePoint in Office 365, you can actually develop compelling functionality for this cloud-based environment. In this session, you will learn how to build, package, and deploy SharePoint and Office apps with Napa.

110

How to buy an app from the SharePoint Store

Prerequisite:
To add an app to a site, you must have at least Full Control permissions for that site. If you are a Site Owner, you already have this permission.

Procedures:
(1) On the site where you want to add an app, click the Settings button, and then click Add an app.
(2) On the Your Apps page, click SharePoint Store in the left-hand navigation.
(3) Use the Categories on the left to filter the selection and browse for the app that you want.
(4) Click the app you want to add. Click Details or Reviews to learn more about the app.
(5) If you are buying this app, use the drop-down list under the price to specify whether you are buying it for your own use, or for use by several people. If required, specify the number of user licenses that you want to buy.
(6) To buy the app click Buy It. (If it’s a free app, click Add it.)
(7) Follow the steps to log on with your Microsoft account to buy the app.
(8) When you are asked whether you want to trust the app, review the Terms & Conditions and the Privacy Statement from the app developer, and then click Trust It.
(9) The app will now appear on the Site Contents page. You can go to the app by clicking it on the Site Contents Page, which takes you to the app.
(10) Done! :)

Installing Hyper-V Manager on Windows 7

Recently one of my clients asked me whether it is possible to install Hyper-V Manager on Windows 7. I was puzzled at the question. Upon further questioning my client, I was informed that due to compliance issue they can only install Windows 7 as most of their applications are not certified for Windows 8 and above yet.

After much consideration, I decided to explore whether we can really install Hyper-V Manager on Windows 7. Thanks to Remote Server Administration Tools for Windows 7 with Service Pack 1. There is indeed a way to install Hyper-V Manager on Windows 7. To install Hyper-V Manager on Windows 7, you can follow the following steps:

1. Download and install Remote Server Administration Tools from:

http://www.microsoft.com/downloads/details.aspx?FamilyID=7D2F6AD7-656B-4313-A005-4E344E43997D&displaylang=en.

2. Install either the 32-bit or 64-bit versions of the Remote Server Administration Tools depending on what version of Windows 7 you are using.
3. Go to Start, point to Control Panel, and then click on Programs.
4. Next, you will see an option to Turn Window features on or off. Click on this option.
5. Expand Remote Server Administration Tools.
6. Expand Role Administration Tools, find the option for Hyper-V Tools, check the checkbox, and then click OK.
7. We are done! You can now type Hyper-V Manager at the Start Menu or go to Start, point to Administrative Tools, and then click Hyper-V Manager.

Refresh version control cache on client computers

To prevent workspace errors from occurring, the data cache on client computers must be updated after certain maintenance operations. After you move, restore, rename, or fail over a data-tier or application-tier server or after you recover from a failure such as a hardware malfunction, you must refresh the version control cache on client computers.

To refresh the version control cache, each user runs the tf workspaces command on any computer that must be updated. They must update any computer that uses version control and that connects to a team project collection whose databases were relocated.

To refresh the version control cache on client computers, you can perform the following steps on the client computer:

1. Open a Command Prompt window with administrative permissions, and change directories to Drive:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE. I’m assuming that you are using Visual Studio 2013.

2. At the command prompt, enter the following command, including the URL of the collection, which includes the server name and the port number of the new server:

tf workspaces /collection:http://ServerName:Port/CollectionName

In the example deployment, a developer needs to refresh the version control cache for a project that is a member of the DefaultCollection collection, which is hosted in the VSALM deployment of Team Foundation Server. He types the following string:

tf workspaces /collection:http://VSALM:8080/tfs/DefaultCollection

NOTE: To use the tf workspaces command on the client computer, your Read permission must be set to Allow.

Follow

Get every new post delivered to your Inbox.