Unable to access from Network locations after UAC enabled

 

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

 

Article ID: 937624 - View products that this article applies to.

Expand all | Collapse all

SYMPTOMS

After you turn on User Account Control in Windows Vista or in Windows 7, programs may be unable to access some network locations. This problem may also occur when you use the command prompt to access a network location.

Note To turn on User Account Control, you click Allow in a User Account Control dialog box.

Back to the top | Give Feedback

CAUSE

This problem occurs because User Account Control treats members of the Administrators group as standard users.

When a member of the Administrators group logs on to a Windows Vista-based computer or to a Windows 7-based computer that has User Account Control enabled, the user runs as a standard user. Standard users are members of the Users group. If you are a member of the Administrators group and if you want to perform a task that requires a full administrator access token, User Account Control prompts you for approval. For example, you are prompted if you try to edit security policies on the computer. If you click Allow in the User Account Control dialog box, you can then complete the administrative task by using the full administrator access token.

When an administrator logs on to Windows Vista or to Windows 7, the Local Security Authority (LSA) creates two access tokens. If LSA is notified that the user is a member of the Administrators group, LSA creates the second logon that has the administrator rights removed (filtered). This filtered access token is used to start the user’s desktop. Applications can use the full administrator access token if the administrator user clicks Allow in a User Account Control dialog box.

If a user is logged on to Windows Vista or to Windows 7, and if User Account Control is enabled, a program that uses the user’s filtered access token and a program that uses the user’s full administrator access token can run at the same time. Because LSA created the access tokens during two separate logon sessions, the access tokens contain separate logon IDs.

When network shares are mapped, they are linked to the current logon session for the current process access token. This means that, if a user uses the command prompt (Cmd.exe) together with the filtered access token to map a network share, the network share is not mapped for processes that run with the full administrator access token.

Back to the top | Give Feedback

WORKAROUND

Important This workaround may make your system unsafe. Microsoft does not support this workaround. Use this workaround at your own risk.

To work around this problem, configure the EnableLinkedConnections registry value. This value enables Windows Vista or Windows 7 to share network connections between the filtered access token and the full administrator access token for a member of the Administrators group. After you configure this registry value, LSA checks whether there is another access token that is associated with the current user session if a network resource is mapped to an access token. If LSA determines that there is a linked access token, it adds the network share to the linked location.

To configure the EnableLinkedConnections registry value, follow these steps:

1. Click Start, type regedit in the Start Search box, and then press Enter.
2. Locate and then right-click the following registry subkey:
   HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System
3. Point to New, and then click DWORD Value.
4. Type EnableLinkedConnections, and then press Enter.
5. Right-click EnableLinkedConnections, and then click Modify.
6. In the Value data box, type 1, and then click OK.
7. Exit Registry Editor, and then restart the computer.

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

Nook Tablet rooting and installing cm10 Android

Forget about rooting and looking for obscure filers with vers 47 in them - i did that already...   Here is all you need to install cm10 on our nook tablet...   taken from: http://www.mobileread.com/forums/showthread.php?t=200004  Thanks to livramax Installing CM 10 Internally on Nook Tablet I've been running CM10 build by XDA Developer Succulent version 12/08 on SD card since its release ten days ago, and its reliable/stable performance has crossed the threshold for me to finally take the plunge and install it internally on emmc. FWIW, here the process I used to install CM10 internally on my 16GB Nook Tablet (i.e., on its emmc) (caveat emptor: adopt/follow it at your own risk). Create on SD card a Primary FAT32 partition, and set the partition ID type for the partition to 0x0C FAT32 LBA and set its Active flag. Once this is done, the partition should appear as a (read/write accessible) drive under Windows. If you are going to use this card for backing up your NT, keep in mind that each backup will require at least 600MB (for a barebone stock or CM config) and size the partition accordingly. Obtain and copy to the SD card the following files: MLO, u-boot.bin, and flashing_boot.img in SD_boot.zip obtained from http://iamafanof.wordpress.com/2012/...r-nook-tablet/ either one of the two recovery program image files: cwm_6012_sd.img (ClockworkMod Recovery (aka CWM)) in CM9-10_CWM_v6.0.1.2_8-16gb_tools_sdcard.zip, or twrp_2220_sd.img (TeamWin Recovery Project (aka TWRP)) in CM9-10_TWRP_v2.2.2.0_8-16gb_tools_sdcard.zip from http://forum.xda-developers.com/show....php?t=1640958, rename it to recovery.img. If you want to try out (or use) both, name your alternate choice altboot.img. the file cm-10-yyyymmdd-UNOFFICIAL-acclaim.zip from http://iamafanof.wordpress.com/2012/...let-uploading/ the file gapps-jb-20121011-signed.zip from http://goo.im/gapps/gapps-jb-20121011-signed.zip Put the SD card into the NT, and boot from its power off by inserting a powered USB cable. Press and hold the N button as soon as CyanoBoot comes up to get the boot menu to display. Select either SDC Recovery (or Alternate Boot depending on which recovery tool you want to use). Select Backup to backup your current NT config (/boot, /recovery, /system, and /data). Before proceeding to next step, see note (ii) near the end of this post. Select Wipe data & factory reset. Select install zip from SD card and install cm-10 zip file. Select install zip from SD card and install gapps zip file. Select power of and remove SD card from NT and power NT on again using the power button (alternatively you can just remove SD card and select reboot). Once the NT boots up, set up the wifi connectivity and your google account info. If you had previously used Google backup service your apps will be auto-downloaded (but not their settings will not be auto-restored) A few additional points worth noting: Installing CM10 ROM and gapps will override your NT's BN-provided boot, recovery, ROM, and Apps, so make sure that you backup all this stuff using backup process in step #5 above, safekeep the backup data on your PC/Laptop and better yet archive it on CD/DVD. Your media files in the NT media partition BN allocates for user should be intact. To play it safe you should do the above in 2 phases: steps 1 through 5, then exit recovery and remove and mount SD card on PC to verify that backup data got newly created; then insert SD card and continue steps 6 through 9. See this post for an overview of CWM and its menu navigation using the NT buttons. TWRP provides comparable functions but uses a user-friendly touchscreen based interface. CWM and TWRP use different backup archive formats, so keep this in mind if you decide to switch. Furthermore, CWM has changed its format going from release 5.x to 6.x, so I think it would be prudent to save a copy of the recovery program together with the backup data it generated. (FWIW I prefer the tar/zip compatible backup data structure TWRP uses (which CWM 5.x had also used) over the BLOb structure which CWM 6.x use -- but YMMV). To restore from backup data, boot into SD card select from boot menu the same recovery program that was used to create the backup data, then select the particular backup dataset (indexed by date/time) you want to reinstall on your NT. I would advise against blindly using other functions of the CWM and TWRP without looking up info and researching to understand what they really do. See my post at http://forum.xda-developers.com/show...7&postcount=31 for more "Info, Pointers, and Tips for Risk Mitigation in Rooting and Custom-ROM Flashing". Last edited by livramax; 05-11-2013 at 11:54 AM.    taken from: http://www.mobileread.com/forums/showthread.php?t=200004

How repair OST and PST files - Exchange and Outlook for Office 2010

http://office.microsoft.com/en-us/outlook-help/repair-outlook-data-files-pst-and-ost-HA010075831.aspx

disable autoRun in XP

Open the registry editor and navigate to the key:


HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Policies\Explorer.


Create a DWORD (32-bit) value named NoDriveTypeAutoRun. If it doesn't already exist.


Right-click the new value and click Modify. Set the hexadecimal value to 000000FF (the decimal equivalent of 255). Now, you can type all the preceding zeros, but you don't need to. You can just enter FF.

source:  http://www.techrepublic.com/blog/itdojo/disable-autorun-on-windows-xp-and-vista-with-a-quick-registry-hack/1010

Setting up Launchy to access your Firefox favorites

Store the exported favorites html file in here:

Currently Launchy 2.0 will only search %APPDATA%/Mozilla/Firefox/... for bookmarks.html, so a workaround would be to make a link or copy your FF bookmarks.html there.

Note: Do you work with different Firefox profiles? Please check C:\Documents and Settings\[User name]\Application Data\Mozilla\Firefox\profiles.ini. I think that Weby takes the first line containing "Path=" and extracts the path where to look for the bookmarks.html file. Verify that this first entry points to the Firefox profile you use and, as advised by begesf, if it contains the bookmarks.html with the links you expect. Also note that, at least under WinXP, Firefox may only (re-)export the bookmarks.html file when closing the application.