7 replies
by jimbb
Some shortcuts to a local app, (C:\Program Files\Somewhere\app.exe) end up in your roaming profile with the reference to the machine where you made that shortcut, so C:\ is replaced by \\machine\c$\. Find the app and change the shortcut, and your required logon will be gone.
There is some registry key that avoids this, but I'm afraid I lost track of it...:-
Jim
by shanghai sam
by nsa13
Answer #1 pretty much hits it on the mark. For example, if it was a standard build or ghost machine and some software was mapped to another location that could've done it. Or, a network install of a program.
Even a standard user can map a hidden share drive. The question is, will they be given access. =) When NT recieves the request for that share it begins its challange/response looking for the user to give proper credentials. Thats why the user is confronted with a logon box for thatshare. Because, his current access privledges aren't sufficient so NT's requesting that he provide new credentials.
Look in the users profile, his logon script, his START directory, his AT scheduler, a rogue batch or .ini file...just plain anything that is trying to initiate the connection.
If your seeing this on multiple roaming profiles I'd say that theres a problem in your build process, imho. Try to determine the simularities and differences between those persons and you'll isolate the fault.
GL
by shanghai sam
by nichomach
The key you're after is:
HKCU\Software\MS\Win\CurrentVersion\Policies\s\Explorer
Insert the following value:
DWORD
LinkResolveIgnoreLinkInfo=1
Hope this helps, I found it a royal pain in the fundament as well...
by shanghai sam
by pchw
This discussion is closed to new replies.
Trending Windows Forum posts
Sort by Trending