You cannot start the SharePoint 2010 Administration Service service

To work around this problem, configure the computer so that the network does not retrieve trusted and untrusted CTLs. To do this, use one of the following methods:
Method 1 
Validate that boundary firewalls, router access rules, and downstream proxy servers enable systems that have update 2677070 installed to contact Microsoft Update. For more information about this requirement, see the following article in the Microsoft Knowledge Base. (This includes the URLs that the CTL update accesses.)
2677070 An automatic updater of revoked certificates is available for Windows Vista, Windows Server 2008, Windows 7, and Windows Server 2008 R2
Method 2 
Change the Group Policy settings. To do this, follow these steps:
  1. Under the Computer Configuration node in the Local Group Policy Editor, double-click Policies.
  2. Double-click Windows Settings, double-click Security Settings, and then double-click Public Key Policies.
  3. In the details pane, double-click Certificate Path Validation Settings.
  4. Click the Network Retrieval tab, click to select the Define these policy settings check box, and then click to clear the Automatically update certificates in the Microsoft Root Certificate Program (recommended) check box.
  5. Click OK, and then close the Local Group Policy Editor.
Method 3
Modify the registry. To do this, follow these steps. 
Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:
322756 How to back up and restore the registry in Windows
  1. Click Start, click Run, type regedit in the Open box, and then click OK.
  2. Locate and then select the following registry subkey: 
    HKLMSoftwarePoliciesMicrosoftSystemCertificates
  3. Right-click AuthRoot, select New, and then click DWORD.
  4. Type DisableRootAutoUpdate, and then press Enter.
  5. Right-click DisableRootAutoUpdate, and then click Modify.
  6. In the Value data box, type 1, and then click OK.
  7. Exit Registry Editor, and then restart the computer.
Method 4Increase the default service time-out. To do this, follow these steps:
Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:
322756 How to back up and restore the registry in Windows 
    Click 

  1. Locate and then select the following registry subkey:HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControl
  2. Right-click Control, point to New, and then click DWORD Value.
  3. In the New Value box, type ServicesPipeTimeout, and then press Enter.
  4. Right-click ServicesPipeTimeout, and then click Modify.
  5. Click Decimal, type the number of milliseconds that you want to wait until the service times out, and then clickOK. 
           For example, if you want to wait 60 seconds before the service times out, type 60000
  1. Exit Registry Editor, and then restart the computer.

Top 10 SharePoint 2010 Configuration Mistakes — and How to Fix Them

Microsoft SharePoint 2010 is a complicated beast, with more knobs and levels than you can shake a stick at. It’s no wonder we get some of them wrong from time to time. Over the past year and a half of installing SharePoint 2010, I’ve seen quite a few configuration mistakes, mostly at my own hands. In this article, I’ll cover 10 of these errors. I’ll explain what the correct configuration is, why it’s correct, and how to correct the setting in your farm. If you make all the changes in this article, you’ll have the beginnings of a beautiful farm — and one less likely to be ridiculed by your friends and neighbors.

Mistake #1: Scrimping on SharePoint’s RAM or Hard Disk Space

If I’ve seen it once, I’ve seen it a hundred times: a poor, defenseless SharePoint server working as hard as it can to keep users happy, but having its hands tied because of limited resources. This situation is usually a casualty of aggressive virtualization. Virtualization itself isn’t bad, but it must be done intelligently and without sacrificing SharePoint’s ability to do its job.
If SharePoint finds itself starved for RAM, it starts shutting off functionality so that it can fit into the available space. It also caches less in the web application pools and recycles those pools more often. Less caching and more recycles result in a degraded end-user experience, as SharePoint must compile the same ASP.NET code over and over. And no one likes unhappy users, not even their mothers.
The solution to this particular issue is easy: Add RAM. Microsoft has published the hardware requirements for SharePoint 2010 in the TechNet article “Hardware and software requirements (SharePoint Server 2010).”  These requirements state that at the very least, each SharePoint 2010 production server should have 8GB of RAM and a C drive with at least 80GB. In many cases, that won’t be enough. If your servers are in production, you can watch their memory utilization to see whether they use the entire 8GB of RAM. If so, they could use more. If your servers are not yet in production, you can use a variety of load-testing tools to simulate your intended load and see how the servers hold up. For example, you can download the Microsoft Load Testing Kit, part of the SharePoint Administration Toolkit.
As for your C drive, SharePoint itself doesn’t need much space, but Windows does. After all, your server has several years of Windows patches to look forward to. While you’re adding drive space to your machine, consider adding a secondary drive as well. This drive is a great place to store all the files that you use when you install SharePoint. All the third-party installation files can go there too. You can also have SharePoint put its log and Search index files on this drive. This approach takes some pressure off the C drive. Happy C drive and happy end users equal a happy SharePoint server administrator.

Mistake #2: Using Virtualized Microsoft SQL Server

As I said in mistake #1, virtualization isn’t bad. But virtualization allows administrators to make mistakes on a much grander scale. Take virtualizing SQL Server. In the context of SharePoint, this process can be especially painful. The main mistake I see when virtualizing SQL Server is overcommitting the host, be it through RAM, CPU, or drive space. Because everything in SharePoint is stored in SQL Server, if SQL Server is slow, SharePoint is slow.
The obvious solution is to move SQL Server to a physical box, on which it doesn’t need to share resources. Moving SharePoint’s SQL Server instance is easy, thanks to aliases. I’ve outlined this process, with pictures, at www.toddklindt.com/sqlalias.
If you can’t get a physical SQL Server box, then at the very least ensure that your virtualized SQL Server instance has a fighting chance. First, make sure that its virtual drives aren’t thin provisioned. I/O is one of the areas in which virtualized SQL Server struggles the most, and thin-provisioned drives exacerbate that problem. Also try to put the SQL Server guests’ virtual drives on their own spindles on the host. Doing so should improve I/O by preventing SQL Server from fighting other guests for time with the drives. Finally, you shouldn’t allow the virtualization host to overcommit its RAM. If the host must swap to meet its RAM obligations, then it’s slowing down SQL Server.
Brent Ozar has recorded a brilliant video on how best to virtualize SQL. Go get some wine and pizza, invite your fellow SharePoint admins, dim the lights, and watch that video. You’ll learn a lot.

 

Mistake #3: Using the Farm Configuration Wizard

Using the Farm Configuration Wizard was a pretty common mistake when SharePoint 2010 first came out but thankfully has diminished as our familiarization with SharePoint 2010 has increased. The wizard’s list of atrocities is long, so I’ll just cover some of the better known ones. First, and maybe most heinous, is that all the databases that the wizard creates have nasty globally unique identifiers (GUIDs) at the end of their names. The wizard also creates a content web app, at http://servername, that just doesn’t scale well. To add insult to injury, the wizard creates your My Site host on that same web app, at http://servername/my. Finally, the wizard encourages you to create service applications that you might not actually use. It’s tough to resist the siren song of those check boxes, I know.
The Farm Configuration wizard leaves its dirty handprints all over SharePoint, and it can be a challenge to clean up all of them. However, a few places can be easily fixed. Start with your web apps. Create a web app for My Site and give it a Fully Qualified Domain Name (FQDN), such as mysites.company.com. Create a My Site host at the web app’s root. Use the Windows PowerShell cmdlet Move-SPSite to move any My Site to one content database, and then attach that content database to your new web app. You’ll also need to adjust your User Profile Service and tell it about your new My Site location.
Next, clean up your service applications. Go through your list of service applications and delete any that you aren’t using. You gain no benefit from having a service application that you aren’t going to use for another six months. After you’ve deleted unnecessary service applications, stop the associated service instances (also called services on server) that power them. If possible, remove the GUIDs from the service application database names. The technique for completing these tasks varies among service application; the Microsoft article “Rename or Move Service Application Databases (SharePoint Server 2010)”  has directions for all the service applications. Of course, take good backups before doing any of this.

Mistake #4: Using an Incorrect URL when Creating a Content Web App

Like any relationship, SharePoint and Microsoft IIS have communication problems from time to time. Web app creation is one of those times. SharePoint doesn’t tell IIS about changes that you might make to a web app after it is created. For instance, if you create an Alternate Access Mapping (AAM) for a web app in Central Administration, you still need to go into IIS and add the host header for the new address.
The issue is compounded when SharePoint farms that you never thought would need to be accessible from the Internet suddenly need to be accessible from the Internet. Budding SharePoint administrators commonly give their web apps short URLs, such as http://portal, to save users some typing. Of course, that URL doesn’t route across the Internet, so the web app needs a fully qualified URL added to its stable of AAMs. Not only is this new URL not written to the IIS host headers, but it’s also missing from all the alerts, workflows, and anything else that saves URLs — all those items have the old URL hard-coded in. Because SharePoint didn’t write any additional URLs to IIS when they were created, it won’t write them to any new SharePoint servers that are added to the farm. Nor will SharePoint write these changes to IIS if the Microsoft SharePoint Foundation Web Application service instance is stopped and started.
This issue might not seem like a big deal, but it has bitten many people at the worst possible time: during an outage. In a few cases, administrators have lost or needed to rebuild a SharePoint server and forgotten about the host headers that they put in manually months earlier. SharePoint is up and going, but when browsing to SharePoint, end users get the blue IIS 7 splash page instead of the SharePoint page that they were expecting. Again, unhappy users usually mean unhappy administrators.
Because SharePoint writes host headers only when a web app is created, you can’t fixproblematic web apps. You’ll need to recreate them. That’s good news and bad news. The good news is that you won’t lose any of the content that your users worked so hard to create. The bad news is that you will lose all the settings that you worked so hard to create.
The first step is to make notes of all your web app settings. In most cases, there won’t be many, and you’ll be familiar with any changes that you made. Then, detach the content databases from your web app. Keep them safe; you’re going to need them. Next, make a copy of the web.config file for that web application. Some settings, such as forms-based authentication (FBA) and BLOB cache settings, are in that file. Finally, go into Central Administration and delete the web app. Tell SharePoint to delete the extra stuff. The scary part is over.
Now, recreate the web app, but do it right this time. First, enter the correct, fully qualified URL in the Host Header box. Do your end users a favor, and put the web app on port 80, as Figure 1 shows. Under the Security Configuration settings, accept all the defaults, even if you’re going to use Kerberos or SSL. You can change those settings later, and you want to make sure that the web app works correctly before you apply fancy security settings. Doing so helps in any troubleshooting that you might need to do. Under the Application Pool settings, pick an existing application pool. (I’ll explain why in the next section.)
Figure 1: Creating a new web app

Figure 1: Creating a new web app

 

It is important to give your content databases distinct names. You should be able to look at a content database name and know exactly which web app that database goes with. This is another one of those things that doesn’t usually seem important but is priceless in a disaster-recovery situation. If the content databases that you detached from the web app before you deleted it didn’t have such names, then take this opportunity to right that wrong when you recreate the web app. Give the new content database a good name, then use the PowerShell cmdlet Move-SPSite to move the site collections to that new database. If your content database already has a good name, enter it during the creation of the new web app. If you had multiple content databases, attach the rest after the web app is created.
After the web app is created, you can tweak settings as needed. Most settings can be changed in Central Administration. If you made any changes to the web.config file of the original web app, now is the time to copy those changes to the newly created web.config file. You can use a program such as Notepad++  to compare the two files. You should now have a well-created web application that you can trust in times of crisis.

Mistake #5: Running Web Apps or Service Apps in Separate App Pools

Web apps and service applications run inside of an application pool, which is a W3WP.exe process that runs on your server. Unless you have reason to do otherwise, you should run all SharePoint web apps inside one application pool; the same goes for the service applications. Running each web app in its own application pool makes inefficient use of the server’s memory. Each application pool has a minimum overhead of more than 100MB, and its memory footprint increases as it caches content that’s rendered frequently. Figure 2 shows multiple W3WP.exe processes running as sp_webapps, the result of web apps running in separate application pools. We’ve all experienced SharePoint slowing first thing in the morning because the app pools recycle overnight and need to warm up and cache that content again. Well, multiple application pools mean that the same content is cached multiple times. Most users are impatient. I’m sure that studies would show that they spend the time waiting for SharePoint to respond by thinking of ways to punish us for SharePoint’s poor performance.
Figure 2: Result of running web apps in separate application pools

Figure 2: Result of running web apps in separate application pools

For service applications, this problem is easy to fix. First, make sure that you have a good service application pool to use. I recommend calling this pool Default SharePoint Service App Pool so that it floats to the top of all your drop-down lists. Use a dedicated sp_serviceapps account for the pool’s identity. Most service applications allow you to assign them to a new service application pool by modifying their properties in Central Administration. If the option is unavailable there, look for it in PowerShell.
Web applications are a tougher matter. There’s no easy, out-of-the-box way to change the application pool that a web app is using. Fortunately, we have PowerShell at our disposal. The steps to this process won’t fit in this article, but I outline them in detail in the article “How to change the App Pool ID of a SharePoint 2010 Web Application.” 

Mistake #6: Using One Account for Everything

Security is complicated, and SharePoint doesn’t necessarily make it any easier. Using just one account — maybe even the coveted Domain Administrator account — is so easy. We’ve all done it, even though it’s a bad idea. When you use an existing account, you open up SharePoint to several security issues. Anyone who knows the account password can do anything in SharePoint, so you can’t separate duties. You also lose the ability to audit who made which changes. And if that common account password is compromised or needs to be changed, you jeopardize SharePoint’s uptime as well. Even if you use one dedicated account for SharePoint, you leave yourself vulnerable to attack. If that account is compromised via a security exploit, the bad guys will have access to everything in SharePoint.
To fix this mistake, start by creating the accounts that I outline in this blog post . Add the sp_webapps and sp_serviceapps accounts as managed accounts. Use the techniques that I describe in Mistake #5 to fix your web app and service application accounts. You can change the default content access account for the Search service application at the Search Service Application page. Under Central Administration, Security, Configure Service Accounts, you can change the accounts that other processes use as well. (You can even change the Farm Account there. I’ve done so in test environments but haven’t been brave enough to do it in production.) If you’re using the User Profile Service, make sure that your new sp_userprofile account has the correct permissions in Active Directory (AD), and recreate your AD connection in the User Profile Service.
You can also use the steps that I describe in “How to create a SharePoint 2010 admin account and stop using sp_farm” to give an account the correct permissions to administrate SharePoint, without needing to use another highly privileged account.

 

 

Mistake # 7: Keeping Default SharePoint Database Settings

When SharePoint creates its multitudes of databases, it makes some bad assumptions. Take the autogrow settings: The database files grow by 1MB at a chunk, almost ensuring that they’re going to autogrow with every upload. Not only does this slow down SQL Server (which slows down SharePoint), but it also results in database files that are spread all over your drives in itty-bitty 1MB chunks.
SharePoint also creates most of its databases, notably the Config and Content databases, with the recovery model set to Full. Although this is great if you want to recover data, you must manage the process correctly or those sneaky .ldf files will slowly, methodically fill your hard disk. If you think users get upset when SharePoint is slow because of fragmented databases, you should see how angry they get when SharePoint stops completely because the SQL Server drives are full.
To fix this mistake, set your databases’ autogrow settings in such a way that they don’t need to grow frequently. For most farms, I recommend changing the 1MB autogrow to something like 500MB or 1GB. Autogrow should also be a last resort. Someone, either the SharePoint administrator or a dedicated DBA, should pregrow your databases so that autogrow is unnecessary.
Your recovery model setting needs to be consistent with your disaster recovery plans. If you need your transaction logs, make sure you’re performing routine log backups to keep those .ldf files in check. If you don’t need your transaction logs, then consider switching your databases to the simple recovery model. Doing so will keep your .ldf files from swelling up like a nasty bee sting.

Mistake #8: Not Enabling BLOB Caching

I don’t know about you, but I’ve never heard an end user say, “SharePoint is too fast. Could you get it to respond a bit more slowly?” We all want SharePoint to get files to the users as quickly as possible. However, more often than not, I see SharePoint farms without BLOB caching enabled. BLOB caching is one of the easiest and least expensive ways to improve SharePoint performance. Not only does it help to get files to users more quickly, but it also eases the burden on SQL Server. Everybody wins.
This might be the easiest solution so far: Enable BLOB caching, of course! BLOB caching is actually a function of IIS; SharePoint just takes advantage of it. Therefore, to enable BLOB caching requires a change to each web app’s web.config file on each server. Fortunately, the setting already exists and just needs to be enabled. By default, the web.config files are in a directory under C:inetpubwwwrootwssvirtualdirectories. Each web app has a directory and a web.config file. Open one of these files and look for the following line:
To enable BLOB caching, replace “false” with “true” and save the web.config file. You should also move the file to a directory on a drive other than the C drive. The maxSize parameter is measured in gigabytes, with a default of 10GB. If the space is available, you might want to increase this size.
If editing this file in Notepad on all your servers isn’t your idea of fun, you can use PowerShell to automate the process. You still need to perform the process on each server, but using PowerShell is quicker and reduces the chances of a mistake. To begin, download the script and save it to a file named blobcache.ps1. This script contains two functions: Enable-SPBlobCache and Disable-SPBlobCache. Each function takes a web app from the pipeline and enables or disables BLOB caching on that app. The code to enable BLOB caching on each web application in the farm looks like this:
                              PS E:InstallScripts> . .blobcache.ps1                              PS E:InstallScripts> Get-SPWebApplication | Enable-SPBlobCache 


Mistake #9: Not Installing a PDF iFilter

Most organizations have a tremendous number of PDF files in their SharePoint farms, and those files represent a wealth of information. End users want to be able to discover that information by using SharePoint Search. Getting users excited about SharePoint Search is a great way to get them excited about SharePoint in general.
Installing a PDF iFilter is fairly easy. Adobe has a free PDF iFilter that you can install. You can find the download link and detailed installation instructions in the Microsoft article “SharePoint 2010 – Configuring Adobe PDF iFilter 9 for 64-bit platforms.” You need to install the iFilter only on those SharePoint servers that run the Search Index role, although installing it on the rest of your SharePoint servers doesn’t hurt. If you have a large farm and want to reduce the time needed to index your PDF files, you can use thePDF iFilter from Foxit. This product has better performance than the Adobe iFilter but isn’t free.

 

 

Again, you can harness PowerShell to make this task easier. Brian Lalancette, creator ofAutoSPInstaller, wrote a great script that automatically downloads, installs, and configures a PDF iFilter, and this script has become my preferred method. The script is part of a larger package, so I’ve stripped out the relevant parts and posted them on this page.  Save that file as pdfsearch.ps1. The file contains two functions: Configure-PDFSearch and Configure-PDFIcon. The former installs and configures the iFilter; the latter adds a PDF icon to the SharePoint interface. As I describe for the script in Mistake #8, install the functions by dot-sourcing the pdfsearch.ps1 file and then executing the function.

Mistake #10: Not Pointing Your SharePoint Servers at Themselves

When SharePoint works, it is magnificent. When it doesn’t work, it can be a nightmare to fix. For this reason, anything you can do to ease troubleshooting is time well spent. To that end, I make sure that every server in the SharePoint farm points to itself for all web apps. If I get sporadic reports about SharePoint not responding, I can easily use RDP to log in to each server and try to pull up SharePoint. If this attempt works, then I know that the server is working. If SharePoint does not come up, then I know in exactly which Microsoft User Location Server (ULS) logs to look for the relevant errors. No worrying about which web front end the load balancer sent my request to. The quicker you get to the correct log files, the quicker the problem is resolved.
Pointing your Search indexer at itself has another advantage: It improves performance for your end users. If you don’t point your Search server at itself, then when it starts to perform a crawl, it lets DNS do its work and then starts crawling whichever web front end DNS points it to. That server is most likely the same one that is sending pages to your end users. Making the server do double-duty means that everyone waits longer. Pointing the Search server at itself means that your web front end doesn’t need to handle that traffic and can get back to doing its #1 job: keeping users happy.
There is a simple fix for this mistake: Open the hosts file (C:windowssystem32driversetchosts) on each SharePoint box, and add all the URLs that SharePoint knows about. Point those URLs to 127.0.0.1, which translates to “this computer.” Figure 3 shows how this file looks in a typical SharePoint environment. This approach provides all the benefits that I’ve mentioned but uncovers a nasty beast: loopback detection. This monster, as well as how to defeat it, is scary and too long for this article, but you can read all about it in my blog post “Can’t crawl web apps you KNOW you should be able to crawl.” 
Figure 3: Hosts file in a common SharePoint environment

Figure 3: Hosts file in a common SharePoint environment

As you might have noticed, I’m a fan of using PowerShell to fix these mistakes, and #10 is no different. This script will automatically add all SharePoint’s URLs to your server’s local hosts file and fix the loopback detection beast in one fell swoop. Is there anything PowerShell can’t do?

Everybody Makes Mistakes

There are as many ways to screw up SharePoint as there are grains of sand on the beach. I ought to know; I think I’ve made them all. Twice. Although you might witness (or make) one or two of the mistakes in this article, the good news is that they can all be fixed. Just follow the instructions here, and your SharePoint farm will be tip-top in no time.
Reference: http://sharepointpromag.com/sharepoint-2010/top-10-sharepoint-2010-configuration-mistakes-and-how-fix-them

How do I fire an event when a iframe has finished loading in jQuery?

I have a strang requirement when I am working for the Sharepoint OOTB model Popup .
My Client wants to Hide default ribbons for the list.
So I thought about directly applying the css or jquery to hide that ribbon on the model dialog
but I found strange behaviour  from sharepoint , the ribbon is not hiding sometimes and due to that i got in some worse situation.
After some research about the jquery to use for hiding that ribbon using jquery I came across this useful link from stack overflow.
This is the function I have used to hide the Ribbon from the Iframe itself.

$(‘iframe’).load(function () {
// do something once the iframe is loaded
hideContactRibbon();  // My Custom function to hide ribbon
});

Basic Sitemap – Generate sitemap of WordPress, Blogger and Tumblr Blogs

Sitemaps are considered as the simplest and easy way for webmasters to inform search engines about pages or content on their sites. Making sitemaps can be complex but most times bloggers usually need only a basic sitemap generator. Basic Sitemap web app can be used to generate sitemap of blogs that are created on WordPress, Tumblr and Blogspot.

These sitemaps can then be submitted to Google and Bing webmaster tools for indexing.

Basic Sitemap Features

  • First of all go to Basic Sitemap. Then you can see page as shown in the figure.
  • In the left site you can see a text box. Enter the complete URL of your blog. For example http://example.blogspot.com. Avoid using country domains such as “.co.in” or “.co.uk“.

text box to enter blog address

  • Once the user entered the address of blog and press ‘generate sitemap’ button. Then it will automatically generate the link to sitemap.

automatically generate sitemap

  • Now copy the address generated by basic sitemap.
  • Open Google or Bing webmaster tools. For demonstration purpose I am using Google webmaster. You need to enter username and password of your Google or Bing account for opening webmaster tool.
  • Once the Webmaster site opens you can see your blog address as in the figure below. If it is not there press ‘Add URL’ or ‘Add Site’ button and add address of your blog. Now click on your blog address.

webmaster tool window

  • Now you are directed to new page. To the right hand side of the page you can see a Sitemap bar. Click on it.

Sitemap option

  • Then you are directed to new page. In this page you can see ‘Add/Test Sitemap’. Press it. In the popup window paste the URL that you copied. Then press ‘Submit sitemap’.

Submitting sitemap

That’s it, your blog’s sitemap is now submitted on Google. For more advanced web tools you can look up the official Google’s recommended list of 3rd party tools for creating sitemaps here.

Auto Refresh Chrome Webpages with Auto Refresh Plus

Posted: 12 Jun 2013 09:26 AM PDT

There are times when we need to constantly refresh a particular webpage just because that webpage is not loading or we want to see new content in that page. Hitting the Refresh button or the F5 button on the keyboard is the probably tiresome. In such cases, extensions like Auto Refresh Plus can be of some help to us.

Auto Refresh Plus is a nifty Google Chrome extension that can refresh a particular webpage for a pre-defined time interval. Auto Refresh Plus is also useful when you want to keep refreshing the page till that page shows some new content or lose some content. This feature is called Page Monitor.

Auto Refresh Plus is available for download on the Chrome Web Store. The extension is really simple to use. On installing, a small icon gets added to the top right of your Google Chrome browser. You can then set instructions with ease like so :

  1. Open the webpage that needs to be refreshed periodically.
  2. Then click on that icon and select the time interval. You can also set a time interval of your own.

auto-refresh-plus

That’s it. It was really simple to configure, right? Once done, that particular web page will continue refreshing automatically. You can now proceed your work with the other tabs. That tab will continue refreshing on it’s own.

Auto Refresh Plus comes with various options. You can enables sounds to notify you when Page Monitor triggers. You can also choose what sound is to be played by inserting the sound URL in the settings section. The settings section also shows options to auto start refreshing and also set a predefined URL to be refreshed.

You might also want to check out Notifycon, an extension that shows notification counts on pinned tabs.

If you are using Firefox, there is an addon that does a similar job.

Link: Auto Refresh Plus on Chrome Web Store

— This Post Auto Refresh Chrome Webpages with Auto Refresh Plus is Published on Devils Workshop .

Enable Two- Step Authentication for Twitter

Posted: 23 May 2013 08:45 AM PDT

Twitter_new_logo.pngToday, Twitter has rolled out an update that allows users to add a phone number to the account. The idea is simple. Every time a users signs-in there is added code that is asked. That code is sent to users via a text message.

So even if someone manages to guess a password, they would not be able to get the verification code from the users phone.

How to activate Twitter’s two-step authentication feature

  • Visit your Twitter profile on the browser and sign-in. Now on the right-hand corner you will see a gear shaped symbol.
  • Hover over it and it shows you the options to look up settings. Under Settings >> Account users can see a new option to titled Account Security.

account-security-cropped

  • We can add a phone number and also select the option to turn-on two step verification.

Here is a nice video demo by Twitter to help their users out

With this step Twitter joins Google and Dropbox in offering two-step verification for better security.

Do drop in your comments.

82 Useful keyboard shortcuts for Firefox

Table of Contents:

  1. Address Bar
  2. Search Bar
  3. Navigation
  4. Inside Webpages
  5. Search
  6. Bookmarks
  7. Firefox Features
  8. Firefox Windows
  9. Forms
  10. The Rest

minus1. Address Bar
alt+d or ctrl+l Jump to address bar
ctrl+enter Complete a .com address in address bar: adds "http" prefix and ".com" suffix to entry, then loads the page. Add alt to combination to load page in background tab.
shift+enter Complete a .net address in address bar: adds "http" prefix and ".net" suffix to entry, then loads the page. Add alt to combination to load page in background tab.
ctrl+shift+enter Complete a .org address in address bar: adds "http" prefix and ".org" suffix to entry, then loads the page. Add alt to combination to load page in background tab.
arrow up/arrow down in address bar Open URL history in address bar and navigate. Press enter to launch selected webpage
delete in address bar history Delete current entry from address bar history

▲ up

minus2. Search Bar
ctrl+k Jumps to search bar if installed (ctrl+e used to do so as well, but seems to be discontinued)
alt+arrow up/arrow down 
in search bar
Toggle search engines
arrow down/arrow up 
in search bar
Choose from previous searches. Press enter to choose selected search term
delete in previous searches Delete previous search entry

▲ up

minus3. Navigation
alt+home Jump to homepage
alt+arrow left/arrow right One page backward / one page forward
ctrl+t Open new tab in same window
ctrl+tab or ctrl+page down Jump to next browser tab
ctrl+shift+tab or ctrl+page up Jump to previous browser tab
ctrl+18 Jump to browser tab 1 – 8
ctrl+9 Jump to the rightmost tab regardless on how many tabs are open
ctrl+w or ctrl+q Close current browser tab
ctrl+shift+t Undo close browser tab

▲ up

minus4. Inside Webpages
alt+d, then press tab twice (or three times) Get "focus" on webpage for in-page keyboard navigation. Note the dotted frame around the page
arrow down/arrow up Scroll webpages up or down one line
page down/page up Scroll webpages up or down one page. space/shift+space does the same.
home/end Jump to beginning / end of webpage
tab/shift+tab Jump to next / jump to previous link
enter Open selected link in current tab
shift+ctrl+enter Open selected link in new foreground tab
ctrl+enter Open selected link in new background tab
shift+enter Open selected link in new window
alt+enter Download selected link
ctrl++/ctrl+ Increase or decrease text size
ctrl+0 Default text size
f5 or ctrl+r Reload page
ctrl+f5 or ctrl+r Reload page with cache override
escape Stop loading page
f6/shift+f6 Jump forwards / jump backwards between tab bar and page. To reach addressbar, press f6until reaching the tab (see dotted line around tab) and press tab
shift+f10 Open context menu of a hyperlink. Press arrow up or down or initial letter to select command
f7 Turn caret mode on or off (navigation with keyboard)
ctrl+a Select all, useful to copy and paste text out of webpages
ctrl+c Copy selected text
ctrl+p Print
alt+f, then v Print preview
ctrl+u Show page source
ctrl+s Save page as

▲ up

minus5. Search
ctrl+f or / Open "quick find" window and searches phrase as you type
' (apostrophe) Open "quick find" (links only) window
ctrl+g or enter or f3 Find next occurrence of search term.
ctrl+shift+g or shift+f3 Find previous occurrence of search term.
escape Close search window

▲ up

minus6. Bookmarks
ctrl+b or ctrl+i Show or hide bookmark sidebar
ctrl+shift+b Organize bookmarks
ctrl+d Add bookmark
ctrl+shift+d Bookmark all tabs. In the "create in" menu, use alt+down to choose bookmark destination
alt+b, then press az or number Open bookmark menu and press first letter of a bookmark name to load them. More than one entry with the same letter, requires to repeatedly pressing the letter and hit enter

▲ up

minus7. Firefox Features
ctrl+j Open or close download window
ctrl+h Show or hide browsing history
ctrl+shift+del Clear private data (menu)
ctrl+o Open file
ctrl+l Open Location
alt+f Open file menu
alt+e Open edit menu
alt+v Open view menu
alt+s Open history menu
alt+b Open bookmark menu
alt+t Open tools menu
alt+h Open help menu
ctrl+/ Show / hide Add-On Bar (holding add-ons)

▲ up

minus8. Firefox Windows
ctrl+n or alt+f+n Opens new browser window
ctrl+shift+w or alt+f4 Close browser window
alt+space Opens the title bar menu (default Windows feature)
alt+space+enter Restore Window (default Windows feature)
alt+space+x Maximize Window (default Windows feature)
alt+space+n Minimize Window (default Windows feature)
f11 Turn full page view on or off (default Windows feature)

▲ up

minus9. Forms
tab/shift+tab Jump to next or previous form element
space Activate or deactivate radio buttons and check boxes
alt+arrow down Select from a drop-down menu
ctrl+cctrl+x and ctrl+v Copy, cut or paste selected text (when working in forms)
arrow up/arrow down Select previously used form entries
shift+delete Delete previously used form entries

▲ up

minus10. The Rest
ctrl+shift+i Open or close webpage Inspector
ctrl+shift+j Open Java Error Console. Press escape to close
f1 Firefox (online) help

Yahoo’s Big Day: Buys Tumblr and offers 1 TB space with Flickr

Yahoo has just capped off a very significant day for themselves. Firstly they have announced the acquisition of the blogging platform Tumblr. In the second announcement, Flickr has now rolled out 1 Terabyte free storage for all users. This is a big deal for Yahoo which has recently struggled to keep its users and more importantly find new users.

The Tumblr Acquisition

Yahoo has bought Tumblr for a estimated $1.1 Billion. That is a lot more money than say Facebook shelled out for Instagram. So what does Yahoo gain from Tumblr?

Tumblr - Yahoo

Image Credit

  • Flickr has 300 million unique visitors on it and has over 900 posts published every second.
  • The Yahoo+ Flickr deal will grow traffic by 20% and its audience will go up by 50%. This increases the advertising opportunities.
  • Mobile seems to be a focus for Yahoo with Tumblr’s acquisition.
  • Yahoo’s CEO in her own Tumblr blog announced that Tumblr will be treated as an independent entity and their CEO David Karp will remain. More importantly in her own words she assuaged the feelings of Tumblr’s community with the quote “We promise not to screw it up”.

Flickr gets 1 TB free space

Flickr is still very popular and its not surprising Yahoo chose to make big announcements with it.

Flickr - 1 TB Space

  • Flickr users get 1 TB storage space free. That means if you upload 6.5 Megapixel photo on Flickr, you can upload half a million of them and for free.
  • The big storage size means Flickr now remain relevant as a storage option especially with the rise of backup options from Google and Apple.
  • Pro Flickr account users will continue to get unlimited storage space and have stats show up for visits on their photos. But new users cannot signup for Pro accounts. That basically means Flickr Pro is more or less going away in time.

Flickr might have rebooted with huge storage space but it will be interesting to see how it manages to complete with the likes of say Google+ which offers to store photos from a phone directly to the cloud. This helps freeing up space on the phone without worrying about losing any photos.

What are your views on Yahoo’s big announcements today? Do drop in your comments.

— This Post Yahoo’s Big Day: Buys Tumblr and offers 1 TB space with Flickr is Published on Devils Workshop .

Fwd: [Devils Workshop] “5 Fun USB accessories that will transform your workspace”

Office life rarely comes with any included amenities, but that doesn’t mean you have to live with a drab and depressing work space. Our computers can also be used as a source of power for some very handy and fun USB accessories. Majority of these devices are readily available online over Amazon or Rediff for Indian readers.

#1. Drink Cooler – When You Need to Chill

Drink Cooler USBDrink Cooler USB

If your desk has a lot of tech equipment on it, you’ve probably noticed the unfortunate effect that your hot computer has on your ice-cold beverage. Never let the line between iced tea and hot tea get blurred again. Keep your drinks cold all day long with a handy USB drink cooler.

#2. Tengu – For Lonely Solo Projects

Tengu USBTengu USB

If talking to yourself is starting to feel a bit sad, enlist Tengu to keep your company. This little legendary Japanese creature plugs into your USB drive and mouths along with whatever he hears, whether it’s your voice or the sound of music. When it’s quiet, he’ll simply drift off to sleep.

#3. Mini-Fridge

Mini Fridge USBMini Fridge USB

Everyone likes to have a refrigerator close by but that is always not possibly in a big office. This mini-fridge plugs into your USB drive and keep your drinks safe at your desk. The tiny cooler is just the right size for a single can.

#4. Cup Warmer – Because Cold Coffee is Gross

Cup Warmer USBCup Warmer USB

Accidentally taking a swig of stone cold coffee can instantly ruin any day. Make sure this never happens to you again by keeping your warm drinks snug and cozy on a heated pad that plugs right in to your USB drive.

#5. Desk Lamp

Desk Lamp USBDesk Lamp USB

If your desk is in the annex, you may find that you mysteriously fall to the bottom of the maintenance team’s list when those buzzing lights dim and go out one by one. This USB desk lamp offers just enough light to keep you going.

With the right toys and gadgets, you can remedy the worst cubicle crises and keep your little corner of the office bright.

These USB gadgets are basically for fun and some are entertaining while others just fun. Ideally they are not the most efficient if used on a laptop. These sort of USB gadgets work best on desktop PCs which do not rely on a battery like a laptop or notebook.

Do you also have similar USB devices which are unique? Do share them with me in your comments

Add the icon (DocIcon) of the file-type to a custom xsl-template when using the ContentByQueryWebPart (CQWP)

by Eric Bartels

In one of my current projects it was required to show the recent documents inside the site collection along with its associated icon. Of course our friend theContentByQueryWebPart (CQWP) comes in.
But how do I get the icon of the document?

The result

CQWP with the associated document icon

Don’t do it again

One could start to use a long list inside an xsl:choose to fetch each extension… But why do a file-extension mapping again when this is already specified inDOCICON.XML?

Give me my icon

  1. Create your ContentByQueryWebPart (CQWP) and export it.
  2. Export the webpart
  3. Locate the CommonViewFields-property and change it from
    <property name="CommonViewFields" type="string" />

    to

    <property name="CommonViewFields" type="string">HTML_x0020_File_x0020_Type,Text;File_x0020_Type,Text</property>

  4. Edit the ItemStyle.xsl or even better create your own My_ItemsStyle.xsl and create a custom template which uses these new ViewFields.
    <xsl:template name="TitleOnlyWithIcon" match="Row[@Style='TitleOnlyWithIcon']" mode="itemstyle">      <xsl:variable name="SafeLinkUrl">          <xsl:call-template name="OuterTemplate.GetSafeLink">              <xsl:with-param name="UrlColumnName" select="'LinkUrl'"/>          </xsl:call-template>      </xsl:variable>      <xsl:variable name="DisplayTitle">          <xsl:call-template name="OuterTemplate.GetTitle">              <xsl:with-param name="Title" select="@Title"/>              <xsl:with-param name="UrlColumnName" select="'LinkUrl'"/>          </xsl:call-template>      </xsl:variable>      <xsl:variable name="LinkTarget">          <xsl:if test="@OpenInNewWindow = 'True'" >_blank</xsl:if>      </xsl:variable>      <div class="item link-item">          <!-- Here comes the icon -->          <span class="icon">              <img src="/_layouts/images/{ddwrt:MapToIcon(string(@HTML_x005F_x0020_File_x005F_x0020_Type),string(@File_x005F_x0020_Type))}" alt="{@DocIcon}" style="vertical-align: middle;margin-right:4px" />          </span>          <a href="{$SafeLinkUrl}" target="{$LinkTarget}" title="{@LinkToolTip}">              <xsl:value-of select="$DisplayTitle"/>          </a>      </div>  </xsl:template>
  5. Change the ItemStyle-property inside the webpart-definition to match your custom template. (TitleOnlyWithIcon in this case).
  6. Import the webpart

Again there is some magic

If you refresh your page I’m sure you get an error. The magic here is to tell the xsl-stylesheet where to find the MapToIcon-function which resides inside the ddwrt-namespace.

The MapToIcon-function does the mapping of the icon by taking the mapping-information from the DOCICON.xml. So even if your icon is not named like the SharePoint ones the icon will be found. My icon here was named icon-pdf.gif for the pdf-file.

Conclusion

The use of the MapToIcon-function is the best method to get the icons. No need for custom “xsl:choose-statements” or “/_layouts/images/ic{@DocIcon}.gif-hacks”.