I have Vista Ultimate on a SBS 2003 network. I have several network shares mapped to the Vista machine. When I start a program from "start as administrator", and then try to access the network shares through the program, they are shown with a red x in the icon. I can click on them and they expand properly. The red x then disappears until I reboot. This problem only shows up when I run a program as administrator. I am logged on as an administrator. Several of the shares are on the SBS 2003 server but one is a NAS. All the shares exhibit the same behavior. The shares are not shown as connected when I use net use from a command prompt (as administrator) either. Once I open the share, they show as connected. Until I reboot.The shares work fine when accessing them in normal mode. I have Quickbooks which must run as administrator and the autobackup function doesn't run unless I access the mapped drive manually before I run the backup. Any thoughts?

I would appreciate any ideas on this problem. I suspect it's something to do with the two security tokens you get as an administrator in Vista but I haven't found a solution yet. Even using a logon script to set up the shares using net use doesn't solve the problem. It seems Vista just doesn't want to automatically connect to these shares in the elevated "administrator" mode. I have checked the share permissions and the NTFS file permissions on these shares and have given "everyone" full control in both cases to no avail. I'm sure others are having similar problems. Any help would be appreciated.

Hi, Thank you for the post. Yes, you are right. This issue occurs because the administrative accounts have two split tokens. Based on my tests, this issue should be resolved by logon script since Group Policy and logon scripts are processed by using the elevated user token. This means that the network drives should be available for the program (run as administrator) after they are mapped by using logon script. Ive included the steps of deploying the logon script for your reference: ==================== 1. Click Start, type gpedit.msc in the Start Search box and press Enter. 2. In the Group Policy Object Editor, Expand User Configuration > Windows Settings > Scripts (Logon/Logoff), and double-click Logon in the right pane. 3. In the Logon Properties window, click Add, click Browse. 4. Right-click the space in the \Logon, select New and Text Document. 5. Right-click the new Text Document, select Edit, and type the net use command to map the network drive (for example, net use Z: \\192.168.3.1\share). 6. Save the file, and rename this .txt file to .bat file (please make sure that the extension of the file is displayed so that we can convert the .txt file to .bat file) 7. Click OK to add the .bat file to logon script. 8. After that, please logoff and logon to check if the network drives are available for the program (run as administrator). If the issue persist, please launch cmd with elevated token and type net use to confirm if the Status of the network drives is OK. Hope it helps. Sincerely, Joson Zhou Microsoft Online Community Support

Joson, That did the trick. I was almost sure I tested this with a logon script but I guess I didn't. This problem sure seems like a bug in Vista. I wonder if SP1 will fix it. Anyway, thanks for your help.

Hi, Thank you for your update and I am happy that it works. The behavior is caused by UAC. Based on my further research, I noticed that this issue has been reported and our related team is investigating it. However, currently there is no update on whether this behavior will be changed in the future. Thanks for your time and efforts. Have a nice day. Sincerely, Joson Zhou Microsoft Online Community Support