Vista/Windows 7 startup scripts

Taken from: http://windowsconnected.com/blogs/joshs_blog/archive/2007/02/20/windows-vista-tip-enabledlinkedconnections.aspx

Also discussed: http://support.microsoft.com/kb/937624/en-us

On 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.

Because 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.

If 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.

Disclaimer: This is not supported by Microsoft and was never tested. Use at your own risk.

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System
EnableLinkedConnections = 1 (DWord)

Internet Explorer 8 Showing blank or Connecting… tab

This is cause by an unregistered dll, usual one specific dll, Actxprxy.dll.

To re-register the dll under Vista:

  1. Click Start and in the search box type:
  2. regsvr32 Actxprxy.dll
  3. Now hold down CTRL+SHIFT (to use elevated priviledges) and press Enter.
  4. Restart the computer.

If this doesn’t fix the problem then repeat using the folowing files:

  • regsvr32 Shdocvw.dll
  • regsvr32 Oleaut32.dll
  • regsvr32 Mshtml.dll
  • regsvr32 Browseui.dll
  • regsvr32 Shell32.dll

Dell Bluetooth Module not detected after rebuild (XP & Vista)

This post gives a link to a Dell download to correct an issue whereby the Dell Bluetooth module 350, 355, 360 is not picked up in Windows XP, however, the module is also not detected in Vista either and this same tool can be used to correct the problem.

http://support.euro.dell.com/support/topics/global.aspx/support/dsn/en/document?journalid=733A1E8062C62D8FE040AE0AB5E1410D&docid=337367