Join Now Is there a workaround for mapping drives via login script in Windows 8. As I mentioned, it looks to me like you have something stopping you connecting to WMI (which is what happens on line 31) - perhaps an ACL in Group Policy is UAC is turned off completely on the machines I've been testing on. Had that problem once. :) 0 Pimiento OP Helpful Post 3runjack Sep 10, 2012 at 4:37 UTC 1st Post You'll need to go into the registry and add EnableLinkedConnections my review here
Microsoft provides a sample script, called launchapp.wsf that works around this problem by running your real logon script a moment later under the correct security context. All rights reserved. For some reason, when the logon script is run as a batch file, all of the drives map, even for users who are local admins. This doesn't happen if the logon.vbs script is ran via the actual logon script GPO, only in Task Scheduler. have a peek at these guys
It also clearly states in Microsoft's KB article for this workaround (referenced in the 3rd paragraph of my post) that it's unsupported - not a great situation for a production infrastructure. The drive mapping is actually to a DFS link, but I don't think that it is relasted to this. Thanks! 0 Text Quote Post |Replace Attachment Add link Text to display: Where should this link go? I'm using a vb script similar to the one below, the script runs using a group policy.
Thanks for the write up, this was driving me nuts but I never did get around to diving in to the "why" behind the problem. If you're not going to use Group Policy Preferences then you have two choices: Make the users standard users. Code 800A01A8. Network Drives Not Mapping On Startup Any help appreciated!
If I run the script manually from the SYSVOL folder the drive is correctly mapped. Enablelinkedconnections =1 Here is what I had to do. This running context is completely separate from the context you get when you right-click Command Prompt and launch as an administrator. https://www.experts-exchange.com/questions/28100865/Windows-7-Login-Script-Drive-Mapping-Not-Working.html I'm betting your users are Administrators, and because you have User Account Control enabled the users' filtered token, under which Explorer runs, doesn't have access to the "drives" that were "mapped"
In response to Stephen: If you care about getting the terminal services bit of the code working, I got this script running by setting the objWMI above where all the other Go Here Get 1:1 Help Now Advertise Here Enjoyed your answer? Network Drives Not Mapping Windows 7 Did the Gang of Four thoroughly explore "Pattern Space"? Windows 7 Enablelinkedconnections [email protected] November 5, 2010 at 20:36 Hey Patters, thanks for your reply.
Wednesday, June 02, 2010 3:03 PM Reply | Quote 0 Sign in to vote I'm experiencing the same issue with following config: TS server farmwith 2 servers Mandatory roaming profile for http://stickersweb.com/windows-7/windows-7-floppy-drive-not-working.php Open the default Domain GPO, navigate to: [Computer Configuration/ Policies / Administrative Templates / System /Logon] Enable "Always wait for the network at computer startup and logon". 2. Enforce policy setting. net use i: /delete) before mapping it. SEO by vBSEO ©2011, Crawlability, Inc. Users Network Drives Not Mapping
It seems to run in the users current context, unlike a vbs script. Higher up doesn't carry around their security badge and asks others to let them in. I think it probably has to do with Windows 7 forcing me to apply the GP under the Computer Configuration rather the the User Configuration. 0 LVL 43 Overall: Level get redirected here Post navigation ← Wake on LAN for VPNusers Sony VAIO P Windows 7 clean installguide → 48 thoughts on “Windows 7 login scripts and missing networkdrives” Eric July 16, 2010 at
to yes. Login Script Not Running Windows 7 As you'll probably have noticed, network drives connected in one context are not visible in the other. Yes anything under the "computer configuration" runs as the computer,i.e. "startup script" so run as the computer and can only see what the computer account can see and maps anything under
Drives would not map when using .vbs logon script. Set colProcessList = objWMI.ExecQuery("Select * from Win32_Process Where Name = 'rdpshell.exe'") For Each objItem In colProcessList objItem.GetOwner strUser, strDomain 'If we're an admin we can see all users' processes so we Help Desk » Inventory » Monitor » Community » Home Mapped Drives via Login Script not working in Windows 8 by A.Jenkins on Aug 27, 2014 at 1:22 UTC | Windows Windows 10 Logon Script Not Running StackList
Edited by jackiellowery Friday, August 01, 2014 6:56 PM Friday, August 01, 2014 6:55 PM Reply | Quote 0 Sign in to vote After working on this on-and-off for1 year, the You will need to install the preferences client via windos update on all workstations but it makes mapping drives much easier that scripting them. In the existing logon script where you have code such as: objNetwork.MapNetworkDrive strDriveLetter, strUNC objNetwork.RemoveNetworkDrive strDriveLetter Replace with: objShell.Run "net use " & strDriveLetter & " " & chr(34) & strUNC http://stickersweb.com/windows-7/windows-7-shutdown-script-not-working.php Any tips on remedying this?