Most people would skip over the remainder of the article after reading that this issue was resolved after the release of Vista SP1. Reading on, one would learn that even with the hotfix, a registry entry must be created which will allow client side programs such as Office pass their credentials through to the server.

The following registry entry must be created:

1. Click Start, type regedit in the Start Search box, and then press ENTER.
2. Locate and then click the following registry subkey:

   HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WebClient\Parameters

3. On the Edit menu, point to New, and then click Multi-String Value.
4. Type AuthForwardServerList, and then press ENTER.
5. On the Edit menu, click Modify.
6. In the Value data box, type the URL of the server that hosts the Web share, and then click OK. Note You can also type a list of URLs in the Value data box.
7. Exit Registry Editor.
8. Restart the WebClient service or reboot the PC.

Reference

• KB 943280

Update

Lifehacker has a screenshot tour.

A solid 95/100 on the Acid3 test is refreshing though.

I have updated Heather’s style sheet to cover any parts that her’s was missing (at least in Internet Explorer 7 and FireFox 2.0.XXX).

The updated CSS can be found here.

You can retrieve the current logged in NT user name from a Content Editor web part with a combination of Javascript and ActiveX with the following:

<script type="text/javascript" language="javascript">

var objUserInfo = new ActiveXObject("WScript.network");
document.write(objUserInfo.ComputerName);
document.write(objUserInfo.UserDomain);
document.write(objUserInfo.UserName);

</script>

It is important to keep in mind that this method will not return any information from IIS or the current site being browsed, so the user name we retrieve within the ActiveX control has the potential to be different from the user name the user is currently logged in to the SharePoint instance with.

A reference to the “Wscript.Network” object can be found here.