HOW TO ADD SHARE THIS EGG TO BLOGGER

Hi Today,I want share Blogging Tips

•  Go to blogger--->Template--->Edit HTML
• Tick Expand Widget Template check box
• Search for </head> in your blogs HTML
• Copy and paste code below just above it.

<!-- Start Egg Bookmarking Gadget Code From http://rkarthikeyanpresents.blogspot.in/ --><script src='http://w.sharethis.com/gallery/shareegg/shareegg.js' type='text/javascript'/><script src='http://w.sharethis.com/button/buttons.js' type='text/javascript'/><script type='text/javascript'>stLight.options({publisher: &quot;bea50586-2b9f-448d-947a-01385f28e305&quot;, onhover:false}); </script><link href='http://w.sharethis.com/gallery/shareegg/shareegg.css' media='screen' rel='stylesheet' type='text/css'/><!-- End Egg Bookmarking Gadget Code From http://rkarthikeyanpresents.blogspot.in/ -->

• Next search for </body> in your blogs HTML
• Copy and paste code below just above it

<!-- Start Egg Share Code From http://rkarthikeyanpresents.blogspot.in/ --><div style='position: fixed; bottom: 2%; left: 2%;'><div class='shareEgg' id='shareThisShareEgg'/></div><script type='text/javascript'>stlib.shareEgg.createEgg(&#39;shareThisShareEgg&#39;, [&#39;facebook&#39;,&#39;twitter&#39;,&#39;googleplus&#39;,&#39;linkedin&#39;,&#39;blogger&#39;,&#39;stumbleupon&#39;,&#39;sharethis&#39;], {title:&#39; <data:blog.pageTitle/>&#39;,url:&#39;<data:blog.url/>&#39;,theme:&#39;shareegg&#39;});</script> <a href="">Blogger Gadgets</a><!-- End Egg Share Code From http://rkarthikeyanpresents.blogspot.in/ -->

IMPORTANT, MOVE THE POSITION OF THE GADGET: 

The Gadget is currently set to be in the minimal rightmost predicament of your blog but you can easily occurrence this.In Red above you can see side: 2%; remaining: 2%;.You can change Inferior to top for it to be at the top of the attender and unexhausted to just for it to be on the ethical of the attender.You can also change the percentages to somebody it more from the bottom/top and left/right.

Save Your Template.

That's it the gadget has been further to your blog.

Thanks
R.karthikeyan

windows 8 Keyboard shotcut and mouse navigation

IIS 8 Features

Internet Information server (IIS) 8 is available to the public for testing and even production workload testing.  Many system administrators have been anxious to kick the tires and to find out which features are coming.
I’ll include a high level overview of what we will see in the upcoming version of IIS.  The focus with this release of IIS 8 is on the large scale hoster.  There are substantial performance improvements to handle thousands of sites on a single server farm—with ease.  Everything that I mention below is available for download and usage today.
Forgive me if there are typos.  I’m writing this while at the MVP Summit in Seattle while trying to listen to another session at the same time.  Thanks to the IIS team who gave detailed demos on this yesterday and gave me permission to talk about this.

Real CPU Throttling
Previous versions of IIS have CPU throttling but it doesn’t do what most of us want.  When a site reaches the CPU threshold the site is turned off for a period of time before it is allowed to run again.  This protects the other sites on the server but it isn’t a welcome action for the site in question since the site breaks rather than just slowing down. 
Finally in version IIS 8 there are kernel level changes to support real CPU Throttling.  Now there are two new actions for sites that reach the CPU threshold.  They are Throttle and Throttle under load.  If you used WSRM to achieve this in the past, you no longer need to do so, and the functionality is improved over what is available with WSRM.
The throttle feature will keep the CPU for a particular worker process at the level specified.  Throttling isn’t applied to just the primary worker process, but it also includes all child processes, if they happen to exist.
The Throttle under load feature will allow a site to use all possible CPU if it’s available while throttling the worker process if the server is under load.
The throttling is based on the user and not specifically on the application pool. This means that if you use dedicated users on more than one app pool then it throttles for all of app pools sharing the same user identity. Note that the application pool identity user is unique so if you use the app pool identity user—which is common—then each app pool will be throttled individually.
This is a welcome new feature and is nicely implemented.

SSL Scalability
Unless you deal with large scale site hosting with many SSL certificates you may not have realized that there is room for improvement in this area. 
Previous versions of IIS have limited secure site density.  Each SSL site requires its own IP address and after adding a few SSL sites, startup performance becomes slow and the memory demand is high.  Every certificate is loaded into memory on the first visit to an SSL site which creates a large memory footprint and a long delay on the first load. 
In IIS 8 the SSL certificate count is easily scalable to thousands of secure sites per machine with almost instantaneous first-loads.  Only the certificate that is needed is loaded and it will unload after a configurable idle period.  Additionally, enumerating or loading huge numbers of certificates is substantially improved.

SNI / SSL Host Header Support
Using host headers and a shared IP address with SSL certificate has always been problematic.  IIS 8 now offers Server Name Indication (SNI) support which allows many SSL sites to share the same IP.  SNI is a fairly new feature (within the last few years) which allows host headers to work with SSL. It does this by carrying the target host name in the TLS handshake rather than the encrypted part of the packet.
IIS 8 makes SNI support a first class citizen in the site bindings.
Note that SNI doesn't work on all browsers. For example, Internet Explorer in Windows XP does not support SNI.  Read more about that from Eric Law's blog post. Over 85% of browsers is use today support SNI, but since it's not 100%, it will not work universally. However, like the adoption issue with host headers in the '90s, it will a fully supported before we know it. More details with a list of browsers can be found here: http://en.wikipedia.org/wiki/Server_Name_Indication
This sets the stage for sharing IP addresses which is extra important as ipv4 IPs become more valuable and consolidation of IPs becomes the trend. 

SSL Manageability - Central Certificate Store (CCS)
In IIS 7 managing SSL is labor intensive, particularly for server farms.  All certificate must be imported on every machine in the farm.  When setting up new servers you must account for time needed to import certificates when scaling out, and even on small server farms.  In previous versions keeping certificates in sync between servers is difficult to manage and often requires manual steps.
In IIS8 there is a new Central Certificate Store (CCS).  Central Certificate Store allows storing certificates on a central file share instead of each machine.  You can point the servers to a single network share, or use replication like DFS-R to sync the folders between machines.
Renewal and syncing is as simple as xcopying pfx files to the location that you specify when enabling CCS on the web server.  Enabling CCS is straight forward too.  It works very similar to enabling Shared Configuration.
CCS compliments the SNI functionality to support sites with multiple certs and a single IP.
The mapping of bindings to certificates uses a bit of magic … by convention rather than configuration. This is important for extremely large lists of certificates. Now you don't need to select them from a huge list. The value of the host header needs to match the name of the cert. Your CCS folder will have many .pfx files with names that match the domain name.  Basically the name of the .pfx files in the certificate store is the primary key.
If you use a wildcard cert then it needs to be named _.domain.com.pfx.
As you would assume, there is support for Multiple Domain Certificates (Unified Communications Certificate [UCC]). If you use multiple domain certificates using the subjectAltName feature of the certificate then you just create multiple copies of the pfx, one for each subjectAltName.
Note that you can use the old method which binds to by certificate identifier and it works the same as it did in the past.
Furthermore there is a neat feature for the central repository that allows grouping by expiration date, which groups by "Today / This Week / Next Week / Next Month / Later" which is handy for seeing which certificates are ready to expire.
With these changes to the certificates, it makes for a powerful solution for large scale webfarm hosting with multiple tenants.

Dynamic IP Restrictions
Information about this is already available on the web, but it's moving along and getting closer for the final release.

FTP Logon Restriction
Yay. A new FTP IP Restrictions module is coming! This is similar in concept to Dynamic IP Restrictions for HTTP. One of the key differences is that it does gray listing rather than black listing. When someone is blocked, they are only blocked for the sample period (e.g. 30 seconds). This is nice because it's enough to thwart or slow brute force and common name password attacks, but legit invalid attempts can continue to attempt to log in without waiting for long periods of time.
What's extra nice about having this feature is that you can set it slightly more sensitive than your domain username lockout policy so that brute force attacks don't cause your username to be locked out from too many invalid attempts. The FTP IP Restrictions can throttle the hack attempts without locking out your domain users.

Application Initialization Module
Previously known as the application warm-up module which was pulled for a time, now it's ready in full force as Application Initialization Module.
This allows spinning up sites and pages before traffic arrives and handling of requests in a friendly way while the application first loads. It's not uncommon for a site to take a minute or longer on the first load (yes SharePoint admins, we feel your pain).  This allows you to protect the end user from being the person that triggers this.
It's possible to set a warm-up page at the server level as a single setting, or you can use powerful URL Rewrite rules for more flexibility.
You can also ensure that your load balancer’s health test page doesn’t serve up a valid response until the site is fully initialized according to your preferences.  Then the load balancer will bring a node into rotation only after the entire warm-up has completed.

Configuration Scale
The IIS configuration files (e.g. applicationHost.config) can handle very large files with ease now.  There are substantial performance improvements in the upcoming version. Only administrators with large numbers of sites on the same server or server farm (think thousands) would have noticed before, but for large scale performance the new changes are paving the way for huge scale.

Web Sockets
It’s important to include Web Sockets in this list too.  Apart from some brief information I really haven’t looked into Web Sockets in detail yet so I’ll just include a great link from Paul Batum on it.  Web Sockets does require Windows 8 or later on the server side. 
All in all these are welcome changes.  While previous versions of IIS already did a great job of handling massive amounts of traffic, IIS 8 now can handle thousands (or tens of thousands) of sites and their extensive configurations on a single server farm.  With HTTP and FTP logon restrictions, CPU throttling, the Application Initialization Module, and large scale SSL and configuration improvements, IIS 8 brings a number of welcome improvements.

How to convert .htaccess rewriting rules into IIS.

Microsoft's Web Stack, many PHP applications are now hosted on IIS. As PHP is an open source, one of the advantages of using PHP is that you will find plenty of free script for ready to use. And basically these all ready to use scripts are written for LAMP model, so we might face some problem related to web server (Apache vs IIS) configuration while running these scripts on IIS. Recently one of my friend face similar problem with Apache rewrite rules while he deployed ready to use PHP script on IIS, and asked me to resolve it.

We need to convert apache mod_rewrite rules into IIS URL Rewrite rules to deploy PHP application on IIS. We can accomplish this task in two ways. 

First way

Open .htaccess file of PHP and manually convert each apache mod_rewrite rule in IIS URL Rewrite rule and then save it in web.config. Now loop through above process for total number of apache mod_rewrite rule ;)

Smarter way

Instead of manually loop through each apache mod_rewrite rule and converting it in IIS URL Rewrite rule, we can automate this process with IIS URL Rewrite Module. Earlier in one post we haveseen how we can use IIS URL Rewrite Module to set preferred domain. Following is the steps for converting apache mod_rewrite rules into IIS URL Rewrite rules.

Open URL Rewrite Module in IIS.

In Actions pane of right side, click on import rules. It will open Import mod_rewrite rules screen.

 

Browse through .htaccess file and click on import button

 

 You can see summary of converted rules in tree view. You can also verify converted rules in XML view.

 

After verifying each rule click on apply in Actions pane.

 

 That’s it, you have done. Now your all apache mod_rewrite rules are converted in IIS URL Rewrite rule and saved in web.config.

Thanks
R.karthikeyan

Team Foundation Server vs. Visual SourceSafe

Wikipedia defines Source control as “Revision control is the management of multiple revisions of the same unit of information.” In other words: Source control allows distributed work in teams of any size, at different locations, while avoiding conflicts in source code changes. There are two famous source control software by Microsoft: Microsoft Visual SourceSafe and Team Foundation Server. Here is the definition for each on according to Wikipedia:

• Microsoft Visual SourceSafe (VSS) is a source control software package oriented towards small software development projects. Like most source control systems, SourceSafe creates a virtual library of computer files.
• Team Foundation Server (TFS) is a Microsoft product offering source control, data collection, reporting, and project tracking, and is intended for collaborative software development projects.It is available either as stand-alone software, or as the server side back end platform for Visual Studio Team System (VSTS).

We have been using the VSS for a long time, but developers always experience some network troubles when working on VSS, as well as the limited features in it. Like we can’t generate a report on the daily work, also many times developers experienced loss in their updated files. But its never too late to improve our work and look for a better solutions to protect our code and control the team work. So the decision was made to replace the VSS with the TFS.
Here is a brief list of major differences between VSS and TFS:
Architectural Differences

• VSS: Read and write files and store them on the shared network folder
• TFS: .NET web service that stored files and items in a SQL Server database

Security and Project Rights

• VSS : All SourceSafe users are granted the same permission and have full access on all projects and files stored in SourceSafe
• TFS : Team server users are window user accounts. Users will have specific permissions and project-level permission. No need to give full access to users on SQL and on all projects, the Administrator can give different permission levels to different users.

Reliability

• VSS : Since we are dealing with transfer of data through a network, operation cannot be rolled back if a problem occurred. In the rare cases when a problem such as the loss of network connectivity does occur in the middle of a write operation, the integrity of the affected files can be compromised and information lost.
• TFS : Team Foundation is a client-server application in which write operations occur in the database by way of stored procedures that are not subject to network connectivity issues and rolled back in the event of an error can be done. Thus no corruption of files occur, groups of files that contain dependent changes are all committed to the source control server at the same time.

Scalability

• VSS : Teams of twenty or less users, and database size is limited to 4GB
• TFS : up to 2000 users and can contain as much as a SQL Server database allows (terabytes)

Changesets

Both are databases organized hierarchically (folders contain files), files consist of versions, identified by number of date/time of creation.

• VSS : No changesets
• TFS : A changeset is a logical container in which Team Foundation stores everything related to a single check-in operation: file and folder revisions, links to related work items, check-in notes, a check-in comment, and other information such as who submitted the change. For more information

Add and Create

• VSS : Adding a file or folder creates a version of the parent in addition to the file. In the parent history, the action is recorded as “add” and in the file history; the action is recorded as “create.”
• TFS : adding a file or folder just creates a version of the file or folder itself with a “add” action. No version of parent is created for this action.

Rename, Delete, and Undelete

• VSS : these actions create a new version of parent;
• TFS : they create a new version of the item itself

Move

• VSS : When you move a folder, new versions of both the source and destination parent folders are created, with actions recorded on each parent that moves the folder into or out of the parent. No version for folder F is created.
• TFS : only a new version of F is created by using the “Rename” action.

 Check-Out and Check-In

• VSS : you must do an explicit check-out and check-in only if you are editing a file
• TFS : every action requires an explicit check-out and check-in

Features that Work Differently in Team Foundation

In the VSS:

• Silent Get operation when you check out a file
• Checkouts are exclusive, by default
• Does not store the merge history between two branches of files or folders

In TFS :

• Does not perform a silent Get operation when you check out a file
• Multiple users can check out and change the same item at the same time, you can lock a file in Team Foundation to prevent other users from checking it out or checking in changes
• Does have support for merge history. Without merge history

After all these new features in TFS, we are sure going to upgrade from VSS to TFS.

 

Thanks

R.karthikeyan

How to change xxxdomain.com to www.xxxdomain.com

This summary is not available. Please click here to view the post.

"The local policy of this system does not permit you to logon interactively" Solved

To resolve this issue, add allowed users to the Remote Desktop Users list:

1. Click Start, point to Settings, and then click Control Panel.
2. Double-click System, and then on the Remote tab, click Select Remote Users.
3. Click Add type in the user account name, and then click OK.
   
   If you are adding more than one user name, use a semicolon to separate the names.

Note: Adding users to the Remote Desktop Group requires that you are logged on through an administrator account.

Also, make sure that the Remote Desktop Users group has sufficient permissions to log on through Terminal Services. To do this, follow these steps:

1. Click Start, click Run, type secpol.msc, and then click OK.
2. Expand Local Policies, and then click User Rights Assignment.
3. In the right pane, double-click Allow logon through Terminal Services. Make sure that the Remote Desktop Users group is listed.
4. Click OK.
5. In the right pane, double-click Deny logon through Terminal Services. Make sure that the Remote Desktop Users group is not listed, and then click OK.
6. Close the Local Security Settings snap-in.

Fix it Utility

To fix this problem automatically, click the Fix it button or link. Click Run in the File Download dialog box, and follow the steps in the Fix it wizard.

Microsoft Fix it utility Downloading Link  50570

Notes

• Type the user account in the Users box during the installation of the Fix it solution.
• To add a domain user account to the local Remote Desktop Users group, use the following format:
  Domain\Username
• To add a local user account to the local Remote Desktop Users group, use the following format:
  Username or .\Username
• To add multiple user accounts to the local Remote Desktop Users group,use the semicolon(;) character as the separator.For example:
  Username1;Username2
• This wizard may be in English only. However, the automatic fix also works for other language versions of Windows.
• If you are not using the computer that has the problem, save the Fix it solution to a flash drive or a CD and then run it on the computer that has the problem.

Thanks
R.karthikeyan