Google Chrome Scroll Anchoring

Scroll Anchoring is a new feature of Google Chrome 51 and newer that prevents visible jumps of the active page when offscreen content changes.

You may have experienced the following situation when using a browser like Google Chrome: you load a page and some text is loaded quickly. You begin to read the text and scroll a bit or a lot, and suddenly the page begins to scroll automatically as other elements, images or media, are added to the page.

You lose sight of the position you were at when that happens. This scroll jumping can be confusing, as you need to locate the position on the page when things started to jump around to continue reading.

These visible jumps, when you start to scroll while a page is loading, is problematic on the desktop, and maybe even more so on mobile devices.

Scroll Anchoring


Scroll Anchoring has been designed to prevent these visible jumps from happening in Chrome. Basically, what the feature does is adjust the page in the background without jumping away from the part that is visible on the screen.

The feature is not enabled by default but part of the browser’s experimental flags. These features are not yet ready for prime time, or need further testing, before Google makes a decision whether to integrate it natively in Chrome or remove it again.

To enable scroll anchoring in Google Chrome, do the following:

  1. Make sure you are running at least Google Chrome 51. Easiest way to find out is to load chrome://version/ and check the version that is displayed.
  2. If that is the case, load chrome://flags/#enable-scroll-anchoring to jump directly to the preference.
  3. On mobile, you may find it easier to load chrome://flags and use the built-in search to find anchor to jump to it instead.
  4. Switch it to enabled to turn it on.
  5. Restart google Chrome to complete the change.

The feature is available for all desktop versions of Google Chrome, for Chrome OS and for Chrome on Android.

To turn it off again, repeat the process outlined above but switch the preference to disabled this time to do so.


Using Process Monitor to measure logon times

FIrst Aid for it support

Did you ever get complaints about slow logon times for users running on a Terminal Server? Probably the answer is yes, but what is slow? And can I measure this with hard numbers? Yes you can do this… By using Process Monitor! And I will show you how.

Step 1

Logon to the server with the local Administrator account and start Process Monitor.

Stop the capture and clear everything, this prevents the ProcMon from using unnecessary resources for now.


Step 2

Edit the Filter as follows. Add the processes winlogon.exe, userinit.exe and explorer.exe

Also filter to only show process Start and Exit.


– Winlogon.exe: You can see the first process to kick of is the Winlogon.exe. It is starting on logon and ends when a user clicks the start => logof button.

– Userinit.exe: Next one to launch is the userinit.exe process which includes various user initializations. This process will also…

View original post 165 more words

User Accounts Do Not Show Up in the Windows SBS Console

If you have created user accounts with the native windows tools, and you wish to display them in the Windows SBS Console, then perform the following steps:

  1. Open the Windows SBS Console.
  2. On the Users tab under Users and Groups, click on Change user role for user accounts.
  3. Choose the user role that you wish to assign to the user account(s), and choose whether you are replacing or adding permissions to the account(s).
  4. Under Select user accounts, mark the checkbox next to Display all user accounts in the Active Directory. You should see the user account(s) that are missing from the console.
  5. Select the account(s) that you wish and click the Add>> button.
  6. Click on the Change User Role button to finish.

How to perform clean install of Take Control on a single device

If Take Control requires a clean install, perform the following steps:

    1. From the Dashboard disable Take Control on the device
      1. Double click the device
      2. Select Remote Access > change Setting: to Off > select OK
    2. Monitor the Summary tab to see when Take Control changes from Active to Not Installed
      1. To speed up process, right-click device > select Re-run Checks
    3. Verify Take Control is not listed under add/remove programs
    4. Delete takecontrol_7_setup or takecontrol_8_setup file from machine
      1. 32 bit: C:\Program Files\Advanced Monitoring Agent\features
      2. 64 bit: C:\Program Files (x86)\Advanced Monitoring Agent\features
    5. From the Dashboard enable Take Control
      1. Double click the name of the device
      2. Select Remote Access > change Setting: to Use Policy Setting (On) or On> select OK
    6. Monitor the Summary tab to see when Take Control changes from Not Installed to Active
      1. To speed up process, right-click device > select Re-run Checks