Tag Archives: Windows Server

Windows Vista Tip – EnabledLinkedConnections

Windows Vista LogoOn Windows Vista when you map a drive under your admin account you will find that your mapped drive is not available after you switch to your full token via a RunAs or Consent dialog. This is by design because there are actually two tokens in play here. What happens is the LSA recognized that you are admin at logon and creates two logons. The first with a “filtered” token or non-admin which is used to render your desktop and the other containing your full token to be available after consent dialogs.\r\n\r\nBecause there are two separate logons there are separate logon ID’s.  When network shares are mapped they are linked to the current logon session for the current process token. Meaning you don’t have access to the network drive from the alternate logon. This can come into play with logon scripts and a number of other areas where you may require access to a network share from both tokens.\r\n\r\nIf you set the following key it will change how SMB shares are mapped. They will be mapped to a token, which means that LSA will check to see if there is a linked token associated with the user session and add the network share to that location as well. Basically all of this means that after setting this drives will be accessible from both tokens no matter which they are mapped under.\r\n\r\nHKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\r\n\r\nEnableLinkedConnections = 1 (DWord)\r\n\r\nDisclaimer: This is not supported by Microsoft and was never tested. Use at your own risk.\r\n\r\nNote: All images, brand names and code used in articles are property of their respective owners. Do not use them without written approval of the respective owner. Windows/ Windows 7 is trade mark of Microsoft Corporation.\r\n\r\n \r\n\r\n \r\n\r\nCredits to: Josh Phillips, Windows Connected

What is new in Firefox 4 Beta?

FireFox 4\r\n\r\n \r\n\r\n\r\n\r\n \r\n\r\nWhat is new?\r\n

\r\n
\r\n
\r\n
\r\n
    \r\n
  • Firefox 4 Beta 2 is available in 24 languages.
  • \r\n

  • Tabs are now on top by default on Windows and OSX – Linux will be changing when the theme has been modified to support the change.
  • \r\n

  • You can turn any tab into an “App Tab” by right-clicking on it and selecting “Make into App Tab” from the context menu.
  • \r\n

  • Web developers can animate content using CSS Transitions.
  • \r\n

  • Responsiveness and scrolling improvements from the new retained layers layout system.
  • \r\n

  • JavaScript speed improvements due to engine optimizations.
  • \r\n

  • Changes to how XPCOM components are registered in order to help startup time and process separation.
  • \r\n

  • See the complete changelist from the previous beta.
  • \r\n

\r\nAs well as these features from previous Firefox 4 Betas:\r\n

    \r\n
  • You can search for and switch to already open tabs in the Smart Location Bar
  • \r\n

  • New Addons Manager and extension management API (UI will be changed before final release)
  • \r\n

  • Significant API improvements are available for JS-ctypes, a foreign function interface for extensions.
  • \r\n

  • The stop and reload buttons have been merged into a single button on Windows, Mac and Linux.
  • \r\n

  • The Bookmarks Toolbar has been replaced with a Bookmarks Button by default (you can switch it back if you’d like).
  • \r\n

  • Crash protection for Windows, Linux, and Mac when there is a crash in the Adobe Flash, Apple Quicktime or Microsoft Silverlight plugins.
  • \r\n

  • CSS Transitions are partially supported.
  • \r\n

  • Full WebGL support is included but disabled by default at this time.
  • \r\n

  • Core Animation rendering model for plugins on Mac OS X. Plugins which also support this rendering model can now draw faster and more efficiently.
  • \r\n

  • Native support for the HD HTML5 WebM video format.
  • \r\n

  • An experimental Direct2D rendering backend is available on Windows, turned off by default.
  • \r\n

  • Web developers can use Websockets for a low complexity, low latency, bidirectional communications API.
  • \r\n

  • Web developers can update the URL field without reloading the page using HTML History APIs.
  • \r\n

  • More responsive page rendering using lazy frame construction.
  • \r\n

  • Link history lookup is done asynchronously to provide better responsiveness during pageload.
  • \r\n

  • CSS :visited selectors have been changed to block websites from being able to check a user’s browsing history.
  • \r\n

  • New HTML5 parser.
  • \r\n

  • Support for more HTML5 form controls.
  • \r\n

\r\nDevelopers can find out about all the changes and new features at the Mozilla Developer Center.\r\n\r\n

\r\n

\r\n

\r\n

\r\n

\r\n

System Requirements

\r\n

\r\n
\r\n
\r\n\r\nBefore installing, make sure your computer meets the system requirements:\r\n
\r\n
\r\n
\r\n

\r\n

\r\n

\r\n

Windows\r\n\r\nOperating System\r\n
    \r\n
  • Windows 2000
  • \r\n

  • Windows XP
  • \r\n

  • Windows Server 2003
  • \r\n

  • Windows Vista
  • \r\n

  • Windows 7
  • \r\n

\r\nMinimum Hardware\r\n

    \r\n
  • Pentium 233 MHz (Recommended: Pentium 500  MHz or greater)
  • \r\n

  • 64 MB RAM (Recommended: 128 MB RAM or greater)
  • \r\n

  • 52 MB hard drive space
  • \r\n

\r\n \r\n\r\nMac\r\n\r\nOperating System\r\n

    \r\n
  • Mac OS X 10.4 and later
  • \r\n

\r\nMinimum Hardware\r\n

    \r\n
  • Macintosh computer with an Intel x86 or PowerPC G3, G4, or G5 processor
  • \r\n

  • 128 MB RAM (Recommended: 256 MB RAM or greater)
  • \r\n

  • 200 MB hard drive space
  • \r\n

\r\n \r\n\r\nLinux\r\n\r\nOperating System\r\n\r\nPlease note that Linux distributors may provide packages for your distribution which have different requirements. Firefox will not run at all without the following libraries or packages:\r\n

    \r\n
  • GTK+ 2.10 or higher
  • \r\n

  • GLib 2.12 or higher
  • \r\n

  • Pango 1.14 or higher
  • \r\n

  • X.Org 1.0 or higher
  • \r\n

\r\nFor optimal functionality, following libraries or packages recommended:\r\n

    \r\n
  • NetworkManager 0.7 or higher
  • \r\n

  • DBus 1.0 or higher
  • \r\n

  • HAL 0.5.8 or higher
  • \r\n

  • GNOME 2.16 or higher
  • \r\n

\r\nMinimum Hardware\r\n

    \r\n
  • Pentium 233 MHz (Recommended: Pentium 500 MHz or greater)
  • \r\n

  • 64 MB RAM (Recommended: 128 MB RAM or greater)
  • \r\n

  • 52 MB hard drive space
  • \r\n

\r\n\r\n

\r\nDownloading\r\n\r\n

\r\n

\r\n

\r\n

\r\n

\r\n
\r\n
\r\n
\r\n\r\nMozilla will provide Firefox 4 Beta for Windows, Linux, and Mac OS X in a variety of languages, though this first version is only available in English. Eventually you will be able to get the latest version of the Firefox 4 Beta in many languages. For builds for other systems and languages not provided by Mozilla, see the Contributed Builds section at the end of this document.\r\n\r\n

\r\n

\r\n

\r\n

\r\n

\r\n

Installing

\r\n

\r\n
\r\n
\r\n\r\nInstalling Firefox 4 Beta will not overwrite your existing installation of Firefox. You won’t lose any of your bookmarks or browsing history, but some of your extensions and other add-ons might not work until updates for them are made available.\r\n\r\n

\r\n

\r\n

\r\n

\r\n

\r\n

Uninstalling

\r\n

\r\n
\r\n
\r\n\r\nYou can remove Firefox 4 Beta with the Add/Removes Programs utility on Windows, by moving the Firefox application to the Trash on OS X, or by deleting the containing folder on Linux.\r\n\r\nBy default, removing Firefox 4 Beta won’t remove your bookmarks, web browsing history, extensions or other add-ons. This data is stored in your profile folder, which can be found by going to the Help menu and selecting Troubleshooting Information…. The button next to the Profile Directory line in Application Basics will open your profile directory in your system’s file explorer.\r\n\r\nPlease note that if you keep your profile, any version of Firefox that you install after removing Firefox 4 Beta will continue to use the bookmarks, web browsing history, add-ons, and other data from this profile folder.\r\n\r\n

\r\n

\r\n

\r\n

\r\n

\r\n

Add-ons and Themes

\r\n

\r\n
\r\n
\r\n\r\nAdd-ons installed with previous versions of Firefox may not yet have been updated by their authors to work with this Firefox 4 Beta. If you wish to help test Add-ons, please install the Add-on Compatibility Reporter – your favorite Add-on author will appreciate it!\r\n\r\n

\r\n

\r\n

\r\n

\r\n

\r\n

Known Issues

\r\n

\r\n
\r\n
\r\n\r\nThis list covers some of the known problems with Firefox 4 Beta which will be resolved in future versions:\r\n\r\n
All Systems
\r\n
    \r\n
  • For some users, scrolling in the main GMail window will be slower than usual (see bug 579260)
  • \r\n

  • Some plugin content, like the media controls on older YouTube videos, will be initially drawn incorrectly. Scrolling or hovering over the affected areas restores them (see bug 579262)
  • \r\n

  • The popular video sites Hulu.com and Netflix.com are not displaying content to beta users due to bad “user-agent” detection in their code (see bug 580843 and bug 522957)
  • \r\n

  • The Bookmark Toolbar is turned off by default even on existing profiles (see bug 574514)
  • \r\n

  • If you try to start Firefox using a locked profile, it will crash (see bug 573369)
  • \r\n

\r\n

Microsoft Windows
\r\n
    \r\n
  • This beta will not start on Windows 2000 (see bug 577486)
  • \r\n

  • A rendering problem with Google Finance can lead to instability (see bug 579558)
  • \r\n

  • Some graphics drivers may not work properly with full screen Ogg Theora HTML video acceleration (see bug 564391)
  • \r\n

  • When using a Persona, the maximize, minimize and close window buttons will not appear, though they will still work (see bug 574833)
  • \r\n

  • When using the Windows “Classic” theme the toolbars and tab strip may appear gray for several seconds as Firefox starts up (see bug 574638)
  • \r\n

\r\n

\r\n

\r\n

\r\n

\r\n

\r\n

Troubleshooting

\r\n

\r\n
\r\n
\r\n
    \r\n
  • Poorly designed or incompatible extensions can cause problems with your browser, including make it crash, slow down page display, etc. If you encounter strange problems relating to parts of the browser no longer working, the browser not starting, windows with strange or distorted appearance, degraded performance, etc, you may be suffering from Extension or Theme trouble. Restart the browser in Safe Mode. On Windows, start using the “Safe Mode” shortcut created in your Start menu or by running firefox.exe -safe-mode. On Linux, start with ./firefox -safe-mode and on Mac OS X, run: cd /Applications/Firefox.app/Contents/MacOS/\r\n./firefox-bin -safe-mode \r\n\r\nWhen started in Safe Mode all extensions are disabled and the Default theme is used. Disable the Extension/Theme that is causing trouble and then start normally.
  • \r\n

  • If you uninstall an extension that is installed with your user profile (i.e. you installed it from a Web page) and then wish to install it for all user profiles using the -install-global-extension command line flag, you must restart the browser once to cleanse the profile extensions datasource of traces of that extension before installing with the switch. If you do not do this you may end up with a jammed entry in the Extensions list and will be unable to install the extension globally.
  • \r\n

  • If you encounter strange problems relating to bookmarks, downloads, window placement, toolbars, history, or other settings, it is recommended that you try creating a new profile and attempting to reproduce the problem before filing bugs. Create a new profile by running Firefox with the -P command line argument, choose the “Manage Profiles” button and then choose “Create Profile…”. Migrate your settings files (Bookmarks, Saved Passwords, etc) over one by one, checking each time to see if the problems resurface. If you do find a particular profile data file is causing a problem, file a bug and attach the file.
  • \r\n

\r\n

\r\n

\r\n

\r\n

How To Enable AJAX .NET Framework 3.5 on IIS7 Server

IIS versions before 7.0 did not require <handlers> for AJAX to work.\r\nIf you are installing AJAX on new IIS7 servers, you will have to make sure you have the following code in your web.config:\r\n

<!--  \r\n The system.webServer section is required for running ASP.NET AJAX under Internet \r\n Information Services 7.0.  It is not necessary for previous version of IIS. \r\n --> \r\n <system.webServer> \r\n <validation validateIntegratedModeConfiguration="false"/> \r\n <modules> \r\n <remove name="ScriptModule"/> \r\n <add name="ScriptModule" preCondition="managedHandler" type="System.Web.Handlers.ScriptModule, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35"/> \r\n </modules> \r\n <handlers> \r\n <remove name="WebServiceHandlerFactory-Integrated"/> \r\n <remove name="ScriptHandlerFactory"/> \r\n <remove name="ScriptHandlerFactoryAppServices"/> \r\n <remove name="ScriptResource"/> \r\n <add name="ScriptHandlerFactory" verb="*" path="*.asmx" preCondition="integratedMode" type="System.Web.Script.Services.ScriptHandlerFactory, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35"/> \r\n <add name="ScriptHandlerFactoryAppServices" verb="*" path="*_AppService.axd" preCondition="integratedMode" type="System.Web.Script.Services.ScriptHandlerFactory, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35"/> \r\n <add name="ScriptResource" verb="GET,HEAD" path="ScriptResource.axd" preCondition="integratedMode" type="System.Web.Handlers.ScriptResourceHandler, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35"/> \r\n </handlers> \r\n </system.webServer>

How To Fix ‘Microsoft.Jet.OLEDB.4.0′ error

\r\n

Problem:

\r\n

\r\n
Server Error in ‘/’ Application.

\r\n

——————————————————————–

\r\n

The ‘Microsoft.Jet.OLEDB.4.0′ provider is not registered on the local machine.

\r\n

Description: An unhandled exception occurred during the execution of the current web request.

\r\n

Please review the stack trace for more information about the error and where it originated in the code.

\r\n

Exception Details: System.InvalidOperationException: The ‘Microsoft.Jet.OLEDB.4.0′

\r\n

provider is not registered on the local machine.

\r\nSolution:\r\n\r\nYou will get this error on Windows Server 2008 R2 or Windows 7 64 bit. To fix it, switch your Application Pool from Native 64 bit to 32 Bit more under Advanced Settings.\r\n\r\nSuggestion:\r\n\r\nIt is also suggested that you upgrade your application to new ACE OLEDB provider, you can download from here.

How To Fix overrideMode=”Deny” Error (HTTP Error 500.19)

HTTP Error 500.19 - Internal Server Error\r\nThe requested page cannot be accessed because the related configuration data for the page is invalid.\r\nConfig Error\r\nThis configuration section cannot be used at this path. This happens when the section is locked at a parent level. Locking is either by default (overrideModeDefault="Deny"), or set explicitly by a location tag with overrideMode="Deny" or the legacy allowOverride="false".\r\n226:     <system.webServer>\r\n227:         <handlers>

\r\nIf you get the error above, you have to make a change in ApplicationHost.config file. To fix this error follow the steps as  below:\r\n

    \r\n
  • Open ApplicationHost.config file in notepad This file is located under C:\Windows\System32\inetsrv\config
  • \r\n

  • Search for <location path=”Default Web Site” overrideMode=”Deny”>
  • \r\n

  • Replace with: <location path=”Default Web Site” overrideMode=”Allow”>
  • \r\n

\r\nChange “Default Web Site”  with the name of your website.\r\n\r\nNOTE: On 64 bit Windows, if you are using 32 bit editor or File Manager, you will NOT be able to see any files in the config folder. Navigate using Windows Explorer or Notepad in native 64 bit mode.

How to Create Rewrite Rule in web.config

If you need a domain URL redirection from yourdomain.com to www.testdomain.com or vise versa, you can do something like this:\r\n\r\nPlace either of these (depending on what you’d like done. And edit to match your domain) inside the <system.webServer></system.webServer> tags in the web.config of the domain.\r\n

<rewrite><rules>\r\n<rule name=”Add WWW prefix” >\r\n<match url=”(.*)” ignoreCase=”true” />\r\n<conditions>\r\n<add input=”{HTTP_HOST}” pattern=”^testdomain\.com” />\r\n</conditions>\r\n<action type=”Redirect” url=”http://www.testdomain.com/{R:1}”\r\nredirectType=”Permanent” />\r\n</rule>

\r\n—————–\r\n

<rule name=”Remove WWW prefix” >\r\n<match url=”(.*)” ignoreCase=”true” />\r\n<conditions>\r\n<add input=”{HTTP_HOST}” pattern=”^www\.testdomain\.com” />\r\n</conditions>\r\n<action type=”Redirect” url=”http://yourdomain.com/{R:1}”\r\nredirectType=”Permanent” />\r\n</rule>\r\n</rules></rewrite>

\r\n

Note: This is applicable on websites hosted on IIS 7.0 or 7.5 (on Windows Server 2008).

Backup IIS7 ApplicationHost.config and Settings

\r\n
Internet Information Services 7 (IIS7) doesn’t use metabase-like file from IIS6. Instead the settings and configuration are stored in schema files and applicationHost.config files.\r\n\r\nSince the configuration files are different, the old IIS6 tools will not be able to backup IIS7 settings.\r\n\r\nThis is the new script that you can use to backup your IIS7 web servers.\r\n\r\n1. Using notepad or any text editor create a file backupiis7.cmd\r\n\r\n2. Insert the following code and save the file:\r\n
\r\n
Code:

\r\n

@echo off\r\ncls\r\n\r\npushd "%WinDir%\System32\inetsrv"\r\n\r\necho.| date | find /i "current">datetime1.tmp\r\necho.| time | find /i "current">datetime2.tmp\r\n\r\nfor /f "tokens=1,2,3,4,5,6" %%i in (datetime1.tmp) do (\r\n  echo %%n>datetime1.tmp\r\n)\r\nfor /f "tokens=1,2,3,4,5,6" %%i in (datetime2.tmp) do (\r\n  echo %%m>datetime2.tmp\r\n)\r\nfor /f "delims=/ tokens=1,2,3" %%i in (datetime1.tmp) do (\r\n  set TMPDATETIME=%%k%%i%%j\r\n)\r\nfor /f "delims=:. tokens=1,2,3,4" %%i in (datetime2.tmp) do (\r\n  set TMPDATETIME=D%TMPDATETIME%T%%i%%j%%k%%l\r\n)\r\n\r\nappcmd add backups %TMPDATETIME%\r\n\r\ndel datetime1.tmp\r\ndel datetime2.tmp\r\n\r\nset TMPDATETIME=\r\n\r\npopd\r\necho.

\r\n

\r\n3. The IIS7 configuration will be backed up at the following path:\r\n

\r\n
C:\Windows\System32\inetsrv\backup

\r\n

\r\nNOTE: you can also use Task Scheduler to automate backups.

\r\n