Kishore Rajendran's Blog https://docs.microsoft.com/archive/blogs/kishorerajendran/feed.xml Support Consultant at Microsoft Tue, 16 Apr 2019 05:16:07 GMT en-US hourly 1 Remote Desktop application for Windows 10 https://docs.microsoft.com/archive/blogs/kishorerajendran/remote-desktop-application-for-windows-10 Tue, 18 Aug 2015 10:23:00 GMT https://blogs.msdn.microsoft.com/kishorerajendran/2015/08/18/remote-desktop-application-for-windows-10/ This post has been migrated from an old blog which I used to maintain.

Please find the content here: https://blogs.msdn.com/b/windows10/archive/2015/08/18/remote_2d00_desktop.aspx

]]> Useful Keyboard Shortcuts for Windows 10 https://docs.microsoft.com/archive/blogs/kishorerajendran/useful-keyboard-shortcuts-for-windows-10 Tue, 11 Aug 2015 10:21:00 GMT https://blogs.msdn.microsoft.com/kishorerajendran/2015/08/11/useful-keyboard-shortcuts-for-windows-10/ This post has been migrated from an old blog which I used to maintain.

Please find the content here: https://blogs.msdn.com/b/windows10/archive/2015/08/11/windows10keyboardshortcuts.aspx

]]> Cortana for Microsoft Edge https://docs.microsoft.com/archive/blogs/kishorerajendran/cortana-for-microsoft-edge Tue, 11 Aug 2015 10:19:00 GMT https://blogs.msdn.microsoft.com/kishorerajendran/2015/08/11/cortana-for-microsoft-edge/ This post has been migrated from an old blog which I used to maintain.

Please find the content here: https://blogs.msdn.com/b/windows10/archive/2015/08/11/microsoft-edge-and-cortana-on-windows-10.aspx

]]> How to install Windows 10 https://docs.microsoft.com/archive/blogs/kishorerajendran/how-to-install-windows-10 Wed, 29 Jul 2015 10:15:00 GMT https://blogs.msdn.microsoft.com/kishorerajendran/2015/07/29/how-to-install-windows-10/ This post has been migrated from an old blog which I used to maintain.

Please find the content here: https://blogs.msdn.com/b/windows10/archive/2015/07/29/how-to-install-windows-10.aspx

]]> Microsoft Azure Forced Tunneling (for Azure Classic portal) - Redirecting all Internet traffic through on-premise location https://docs.microsoft.com/archive/blogs/kishorerajendran/microsoft-azure-forced-tunneling-redirecting-all-internet-traffic-through-on-premise-location Sat, 09 May 2015 04:11:00 GMT https://blogs.msdn.microsoft.com/kishorerajendran/2015/05/09/microsoft-azure-forced-tunneling-redirecting-all-internet-traffic-through-on-premise-location/ A common concern with customers when setting up a site to site network and linking a VM to one of its subnets is the flow of traffic to the Internet. Restricting the Internet bound traffic is a key security requirement for organisations which need to be enforced. Forced Tunneling allows you to block all Internet bound traffic and re-routes via on-premise allowing administrators to monitor and inspect all traffic.

Image source: https://azure.microsoft.com/blog/2014/10/29/networking-enterprise/

The above diagram illustrates a site to site VPN from Azure to a RRAS/VPN device on premise. It demonstrates a typical behaviour of the subnets in the Azure virtual network allowing the flow of traffic both via the S2S VPN and to the Internet. The implementation of Forced Tunneling forces all the traffic to flow via the S2S VPN connection to on-premise before being allowed to the Internet. How to implement Forced Tunneling? Implementing Forced Tunneling is simple and is achieved through four simple steps. Before proceeding, ensure that the following prerequisites have been met so that there are no errors. Prior to carrying out the below steps ensure that the Azure publish settings file has been downloaded and imported onto PowerShell. Steps on how to do this can be found here: https://azure.microsoft.com/en-gb/documentation/articles/powershell-install-configure/ 1. First we need to create a routing table which will be used later to associate it to the subnets in your virtual network. The cmdlet below creates a new routing table New-AzureRouteTable –Name <routeTableName> –Label <routeTableLabel –Location <azureDatacentreLocation>   2. Now we have created a routing table which needs a default route.  The cmdlet below adds a default route to the routing table. Set-AzureRoute –RouteTableName <routeTableName>  –RouteName <routeName> –AddressPrefix “0.0.0.0/0” –NextHopType VPNGateway 3. Next we need to add the routing able to one or multiple subnets within the virtual network. The cmdlet below associated the routing table created in the above steps to a specific subnet. To apply for multiple subnets use the same cmdlet and replace only the subnet name to the actual subnet. Set-AzureSubnetRouteTable -VNetName <vnetName> -SubnetName <subnetName> -RouteTableName <routeTableName> 4. Finally we need to add a default site. The cmdlet below selects a local site among the multi-site connections of the virtual network as the default site or tunnel. $DefaultSite = @(<defaultSiteName>) Set-AzureVNetGatewayDefaultSite –VNetName<vnetName> –DefaultSite <defaultSiteName>    Forced Tunneling is now set up on all configured subnets in a virtual network.

Removing Forced Tunneling

1. Delete a route table Remove-AzureRouteTable -RouteTableName <routeTableName> 2. Delete a route from a route table Remove-AzureRouteTable –Name <routeTableName> 3. Unassign a route from a subnet Remove-AzureSubnetRouteTable –VNetName <virtualNetworkName> -SubnetName <subnetName> 4. Unassign a default site from the virtual network VPN gateway Remove-AzureVnetGatewayDefaultSites -VNetName <virtualNetworkName>   List routing tables 1. List a routing table Get-AzureRouteTable [-Name <routeTableName> [-DetailLevel <detailLevel>]] 2. List a routing table associated to a subnet Get-AzureSubnetRouteTable -VNetName <virtualNetworkName>-SubnetName <subnetName>]]> Failed Request Tracing - IIS https://docs.microsoft.com/archive/blogs/kishorerajendran/failed-request-tracing-iis Fri, 08 May 2015 08:58:00 GMT https://blogs.msdn.microsoft.com/kishorerajendran/2015/05/08/failed-request-tracing-iis/ The introduction of IIS 7.0 in Windows Server 2008 included enhanced logging tools available as part of the web server role. Failed Request Tracing is one of these features introduced in IIS 7 and is still available in IIS 8.5 included as part of Windows Server 2012R2.

 

Failed Request Tracing captures trace events for a request when it fails, in a lot more detail than the IIS logs. We have the option to specify which failed requests should be captured, based on a specific error code or the time it takes to load an application. This feature can also be used on valid requests, not just failed requests. When a web server role is installed the default modules selected does not provide the functionality for Failed Request Tracing. The Tracing module, found under the Health and Diagnostics section of the role service, must be selected for installation. As a result of this many customers are not aware of this feature even though it has been available as part of the web server role in excess of 7+ years.

 

How to install Failed Request Tracing (FRT)

In order for FRT to be enabled specific modules, also known as role services, needs to be selected for installation as part of the web server role. In both Windows Server 2008R2 and Windows Server 2012R2 this module is Tracing, which can be found underneath the Health and Diagnostics section.

 

Image 1: Screenshot of the Add Role Services Wizard in Windows Server 2012R2

 

Image 2: Screenshot of the Add Role Services Wizard in Windows Server 2008R2

 

 

How to enable Failed Request Tracing (FRT)

Once the tracing module has been installed the link to enable FRT can be found in the IIS manager actions pane as illustrated below.

 


Image 3: Screenshot highlighting the location of FRT within the IIS Manager

 

Selecting the FRT link, as highlighted in image 3, will display the below dialog box to enable the feature. Tick the check box to enable FRT and specify the directory where FRT logs should be stored. It is recommended that logs are stored on a different partition to the system drive. There is also an option to specify the maximum number of trace files in the settings dialog box.

 

Image 4: Screenshot of the FRT settings dialog box

 

Please note that enabling FRT will affect the request processing speed of IIS. The feature will self tune itself should there be too many requests in a short period of time and there is no need to worry about the possible implications to the web server.

 

How to configure Failed Request Tracing (FRT)

In the connections pane, select Failed Request Tracing Rules. Ensure that a site or application is selected from the connections pane first prior to configuring the feature.

Image 5: Screenshot of the FRT rules feature

 

Click Add in the Actions Pane and the below dialog box will appear where a specific rule to capture a failed request can be set up. Select what should be traced, there are four options as shown in image 6.

Image 6: Screenshot of the FRT rules configuration dialog box

 

Next we need to define the trace conditions, there specify what should be traced, a specific error code(s), time taken or an event such as Error or Information. It is also possible to specify a range of status codes rather than just one. 

Image 7: Screenshot of the FRT rules configuration dialog box

 

The final step is to select the trace providers and the level of verbosity. Once all the providers have been selected, click finish. The FRT rule will now be visible on the IIS Manager.

Image 8: Screenshot of the FRT rules configuration dialog box

 

Each time when there is an occurrence of a failed request as per our rules, the traces will be captured and stored in the location specified in image 4. Click on the freb.xsl, as shown in image 9, to view the traces in a formatted web page through Internet Explorer.

 

 

Image 9: Screenshot of the FRT log

 

Image 10: Screenshot of the FRT in Internet Explorer

 

FRT can also be configured through the <traceFailedRequests> element located in the ApplicationHost.config configuration file.

 

Disclaimer

The sample scripts are not supported under any Microsoft standard support program or service. The sample scripts are provided AS IS without warranty of any kind. Microsoft further disclaims all implied warranties including, without limitation, any implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample scripts and documentation remains with you. In no event shall Microsoft, its authors, or anyone else involved in the creation, production, or delivery of the scripts be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample scripts or documentation, even if Microsoft has been advised of the possibility of such damages.

]]> Office 365: How to Import and Export PST files https://docs.microsoft.com/archive/blogs/kishorerajendran/office-365-how-to-import-and-export-pst-files Wed, 10 Sep 2014 10:46:00 GMT https://blogs.msdn.microsoft.com/kishorerajendran/2014/09/10/office-365-how-to-import-and-export-pst-files/ Importing and exporting PST files is straight forward however customers do get confused sometimes. Here is a short video on how to do this using an Outlook client.

 

[View:https://www.youtube.com/watch?v=HLykqd4jdMU&index=8&list=PLEXuFMEOTa_hhuYri8PrbckEVKx0HOv7V]

 

 

Disclaimer

The sample scripts are not supported under any Microsoft standard support program or service. The sample scripts are provided AS IS without warranty of any kind. Microsoft further disclaims all implied warranties including, without limitation, any implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample scripts and documentation remains with you. In no event shall Microsoft, its authors, or anyone else involved in the creation, production, or delivery of the scripts be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample scripts or documentation, even if Microsoft has been advised of the possibility of such damages.

]]> Office 365: Contacts Sharing https://docs.microsoft.com/archive/blogs/kishorerajendran/office-365-contacts-sharing Wed, 10 Sep 2014 10:42:00 GMT https://blogs.msdn.microsoft.com/kishorerajendran/2014/09/10/office-365-contacts-sharing/ Sharing contacts is really simple when using an Outlook client or through a web browser. Watch this short video to explore how this can easily be done.

 

[View:https://www.youtube.com/watch?v=HLykqd4jdMU&index=8&list=PLEXuFMEOTa_hhuYri8PrbckEVKx0HOv7V]

 

 

Disclaimer

The sample scripts are not supported under any Microsoft standard support program or service. The sample scripts are provided AS IS without warranty of any kind. Microsoft further disclaims all implied warranties including, without limitation, any implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample scripts and documentation remains with you. In no event shall Microsoft, its authors, or anyone else involved in the creation, production, or delivery of the scripts be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample scripts or documentation, even if Microsoft has been advised of the possibility of such damages.

]]> Office 365: Troubleshoot Outlook Connectivity https://docs.microsoft.com/archive/blogs/kishorerajendran/office-365-troubleshoot-outlook-connectivity Wed, 10 Sep 2014 10:36:00 GMT https://blogs.msdn.microsoft.com/kishorerajendran/2014/09/10/office-365-troubleshoot-outlook-connectivity/ Are you experiencing connectivity issues when using Outlook client? Watch this short video to explore a few quick steps that you can take to ensure your Outlook is back online.

 

[View:https://www.youtube.com/watch?v=yLKjafljdVY&index=6&list=PLEXuFMEOTa_hhuYri8PrbckEVKx0HOv7V]

 

 

Disclaimer

The sample scripts are not supported under any Microsoft standard support program or service. The sample scripts are provided AS IS without warranty of any kind. Microsoft further disclaims all implied warranties including, without limitation, any implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample scripts and documentation remains with you. In no event shall Microsoft, its authors, or anyone else involved in the creation, production, or delivery of the scripts be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample scripts or documentation, even if Microsoft has been advised of the possibility of such damages.

]]> Office 365: Calendar Sharing https://docs.microsoft.com/archive/blogs/kishorerajendran/office-365-calendar-sharing Wed, 10 Sep 2014 10:33:00 GMT https://blogs.msdn.microsoft.com/kishorerajendran/2014/09/10/office-365-calendar-sharing/ Sharing calendars using Office 365 accounts is identical to accounts hosted on premise using the Outlook client. This short video will guide you through the steps as well as how to share calendars using a web browser.  

 

[View:https://www.youtube.com/watch?v=-SpxhulCVnk&index=5&list=PLEXuFMEOTa_hhuYri8PrbckEVKx0HOv7V]

 

Disclaimer

The sample scripts are not supported under any Microsoft standard support program or service. The sample scripts are provided AS IS without warranty of any kind. Microsoft further disclaims all implied warranties including, without limitation, any implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample scripts and documentation remains with you. In no event shall Microsoft, its authors, or anyone else involved in the creation, production, or delivery of the scripts be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample scripts or documentation, even if Microsoft has been advised of the possibility of such damages.

]]>