How to enable Windows 7 single sign-on for a website using Windows authentication

by Peter Tyrrell Wednesday, October 21, 2009 2:43 PM

Symptom

You visit an intranet website that uses Windows authentication with an IE browser on Windows 7 and expect to be logged in automatically with your current domain credentials. Instead, you are challenged for credentials. Once you enter credentials everything acts normally, but you expect a single sign-in scenario and it doesn't happen. If you visit the same URL with IE on another Windows OS within the domain, single sign-on works as expected.

Cure

A default local security policy in Windows 7 prevents LM and NTLM responses.

  1. Go to Local Security Policy > Security Settings > Local Policies > Security Options
  2. Select Network security: LAN Manager authentication level
  3. Change security setting to Send LM & NTLM responses

win7_secpol

Related

Tags: Windows 7

How to install Inmagic Webpublisher 12 on Windows 7

by Peter Tyrrell Wednesday, October 14, 2009 1:12 PM

Disclaimer: Not officially supported. Plunging heedlessly on...

1 - Back up INI files

First back up all your .ini files. Be sure you are getting the CORRECT copy of the ini file: the ini files in the Program Files directory are access-protected in Vista and Win7 because the Program Files area is a forbidden zone. You must open the ini file with elevated privileges, like with Notepad "run as administrator", and save it somewhere safe.

  • dbtwpub.ini
  • inmagic.ini
  • dbtext.ini

2 - Upgrade from previous version

If you want to upgrade from previous version of WPP instead installing a fresh copy, uninstall the previous version MANUALLY first, because the WPP 12 installer tries to uninstall without elevated permission, and thus fails.

3 - Run installer as admin

Run the WPP 12 installer with administrator privileges. If you have a setup.exe you can right-click to "run as administrator".

My preview version of the installer is an *.msi file only, which doesn't have a right-click "run as admin" option. Instead, I launch the msi with msiexec from an elevated command prompt:

  1. Search for "cmd.exe" from Windows Start Menu
  2. Right-click cmd.exe and "run as administrator"
  3. Change directory to location of the msi, e.g. cd c:\users\ptyrrell\downloads
  4. Run the msi with the msiexec /i option, e.g. msiexec /i "Inmagic DBText WebPublisher PRO.msi"

4 - Fulfill prerequisites

The installer is cleverer than previous versions when checking for prerequisites, so you'll probably have to go and install or enable various Windows features before continuing.

wpp12_prereqs 

IIS 6 Compatibility (IIS7 only) seems to be satisfied by enabling the "IIS Metabase and IIS 6 configuration compatibility" Windows feature.

wpp12_iis6

Be warned: if you don't run the installer with elevated privileges, you will continue to fail the prerequisite check even after installing/enabling the right prerequisites!

 

5 - Test the install

Restore your backed up ini files. Run a query on the sample cars textbase to ensure WPP is returning results as expected.

If you are installing on a 64 bit machine, you need to enable 32 bit applications on the relevant application pool as covered in this previous post called How to Install Webpublisher on 64-bit IIS 7.

6 - Be the star you know you are

You did it! Now cut out a cardboard star with safety scissors, pencil "STAR HACKER" on it, and get your mum to pin it to your chest, glitter optional. Salute yourself in the mirror. Star! Hacker!

Windows 7: blissfully tabbing to complete path in Explorer

by Ted Jardine Tuesday, August 25, 2009 11:39 AM

This'll be a short post, but there are many things I love about Windows 7, and many things I really like, but I've just discovered something that you might not have heard about yet: in Windows Explorer, you can now tab to complete the path in the address bar. For example, in the path below, I can type "Of" and then hit tab and it will automatically complete "Office" followed by the next backward slash, ready for me to continue on down the path.

This might not seem like a big deal, but see how much time it saves navigating to "C:\Windows\Microsoft.NET\Framework64\v2.0.50727\Temporary ASP.NET Files". And yes, that's if you haven't already set up Executor/Launchy/Enso (note: does not work on x64)/Etc. to have a shortcut already to that particular location. However, it's even better than those launchy applications in that it's a) in Explorer already, b) it allows you to sometimes tab, sometimes type, sometimes arrow down to a selection, and c) hitting enter opens the current directory, but then you can go right back up with alt-d to the address bar and continue on again. If you use any of the above launchy-type applications, you'll know what I'm talking about. If you're not yet using one of them, hello?!? (and yes, while the new-in-Vista start button is an improvement, it's still not near as feature complete).

Another handy thing that I needed a third party app for before is the now-native "Copy as path" option for files (although you need to shift-f10 to open menu, or shift-left click to get it to show):

>Copy as path

Tags: tips | Windows 7

Inmagic Webpublisher works on Windows 7

by Administrator Wednesday, May 06, 2009 1:20 PM
I installed Windows 7 RC a few days ago and so far it looks like Inmagic DB/Textworks 11 and Webpublisher Pro 11 are compatible with it. Both must be installed in "run as administrator" mode, of course. See the post related to Vista installs for details and further links. This post for installing Webpublisher on 64 bit IIS 7 is still valid for Windows 7. Also Denise's warning against putting textbases in the Program Files folder still applies. (Virtualization spirits the files away out of the Program Files folder.) One thing unfortunately is insurmountable at this point: there is no WinHlp32 support for Windows 7 RC (though there will be when Windows 7 goes RTM) so no DB/Textworks help for me. I've memorized it anyway.

Inmagic DB/TextWorks and Vista Virtualization

by Denise Bonin Monday, July 07, 2008 5:10 PM

This post is a follow-up to Peter's post Inmagic WebPublisher PRO and Vista Virtualization, but specifically pertaining to DB/TextWorks. 

I recently had a client who created and added a bunch of records to a new textbase located in a folder under Program Files on her Vista-installed laptop.  When it came time to move the textbase off her laptop onto another computer she zipped up all the textbase files, copied the zip file to her thumb drive and prepared to unzip the files onto the other machine.  With files unzipped on the other machine (an older XP-installed desktop computer), she enthusiastically went to show off her newly created and populated textbase. 

Much to her surprise DB/TextWorks produced a disheartening message indicating that the textbase was empty.  How could this be, she had 170 records in the textbase when it was on her laptop and she had copied every textbase file from the correct folder on her laptop.  I got involved and we looked this way and that way - on both machines - and there was nothing that we could see that could indicate that the textbase could possibly be empty (the .btx, .dbt and .occ files were rather large).

The ah ha moment came when Kathy suggested that Peter had posted something about this on our Blog - back in March 2008 (see above link).  I had skipped over that posting because it had referenced WebPublisher, but in fact it told me exactly what I needed to know.  To change the text and code slightly from what Peter posted:

For instance, say DB/TextWorks indicates that a textbase is located at:

%Program Files%\Inmagic\Textbases

Vista detects that DB/TextWorks does not have permission to save to that location and copies the file to:

%Users%\<your account>\AppData\Local\VirtualStore\Program Files\Inmagic\Textbases

Subsequent read/write operations access the VirtualStore version of the file, even though DB/TextWorks will still think it is accessing the Program Files directory. Poor deluded DB/TextWorks.

It took about 1 minute to find the database files in the VirtualStore location - thank you Peter! - however, there was more, or in this case less, to come!  Two of the essential files were missing.  They were the .tba file and the .sdo file.  Why those two? Who knows?  However, combining the new found files (.acf, .btx, .dbo, .dbr, .ixl, .log, and .occ)  from the VirtualStore location with the .tba and the .sdo file from the presumed location – under Program files, allowed us to complete the textbase and transfer it to another location. 

The lesson learned here:

  • On a Vista machine DO NOT install textbases under Program files. 

And a Note: 

  • this problem only occurs with Vista's UAC (user account control) turned on.

Month List