Just thought yoo, when you say a startup script that maps drives...do you mean logon script or startup script? A Startup script isn't going to be able to map drives as the user hasn't logged in at that point.
Steve
Main Topics
Browse All TopicsI have users that get presented with the netlogon folder every time they log into the network. Is there an option that I can check in a GPO that prevents this from happening?
The window\folder is displayed as:
\\servername\netlogon
Sometimes the folder is not launched and an error is displayed in it's replacement. It reads:
Windows cannot fide '.idlis,,,,\\servername\ne
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Point of clarification. I had a group policy pointing to a batch file for logon scripts. Sorry about the confusion. I removed the file altogether and continue to see the folder appear when logging into the network. The folder displays the path:
\\servername\netlogon
I ran gpupdate and rebooted my computer to no avail.
Do the users have legacy scripts configured still in the profile section of their user in AD? Does this kick in after login or before the user logs in?
Anything in the hklmor hkcu \software\microsoft\window
Does it only happen when logging in on the network -- pull the network and login with a cached password (if enabled) or a local a/c
Steve
Do the users have legacy scripts configured still in the profile section of their user in AD? Does this kick in after login or before the user logs in?
> No
Anything in the hklmor hkcu \software\microsoft\window
> value not set
Does it only happen when logging in on the network -- pull the network and login with a cached password (if enabled) or a local a/c
>Only when loggin in on the network.
pull the network and login with a cached password (if enabled) or a local a/c
>??? I know cached creditentials is enable. Is this what your referring to?
Does it appear on a different machine as him, does he have a roaming profile.
If he has no roaming profile and it is coming up on a different machine then we need to look at scripts coming from AD etc. If it doesn't then it is machine related on his profile I would say .... silly question time ... but have you looked in his startup group!
if his profile is roaming then if it follows him it could be profile related -- try renaming his roaming profile and delete it off his machine locally then login again. If that doesn't resolve it delete it locally and rename the old one back.
Steve
OK so if it is not a roaming profile and follows to different machines - have you tried one he has not logged into before for instance - then it MUST be either a gp issue or legacy script for this user. Anything in the event logs at this time.... anything showing up in gpresult or even gpresult /v or gpresult /z
He is in the default domain GPO and it is very vanilla.
COMPUTER SETTINGS:
Applied Group Policy Objects
--------------------------
Default Domain Policy
The following GPOs were not applied because they were filtered out
--------------------------
Local Group Policy
Filtering: Not Applied (Empty)
The computer is a part of the following security groups:
--------------------------
BUILTIN\Administrators
Everyone
BUILTIN\Users
NT AUTHORITY\NETWORK
NT AUTHORITY\Authenticated Users
Domain Computers
Resultant Set Of Policies for Computer:
--------------------------
Software Installations
----------------------
N/A
Startup Scripts
---------------
N/A
Shutdown Scripts
----------------
N/A
Account Policies
----------------
GPO: Default Domain Policy
Policy: MinimumPasswordAge
Computer Setting: 5
GPO: Default Domain Policy
Policy: LockoutDuration
Computer Setting: 4294967295
GPO: Default Domain Policy
Policy: ResetLockoutCount
Computer Setting: 30
GPO: Default Domain Policy
Policy: MinimumPasswordLength
Computer Setting: 8
GPO: Default Domain Policy
Policy: LockoutBadCount
Computer Setting: 5
GPO: Default Domain Policy
Policy: MaximumPasswordAge
Computer Setting: 90
Audit Policy
------------
N/A
User Rights
-----------
N/A
Security Options
----------------
GPO: Default Domain Policy
Policy: RequireLogonToChangePasswo
Computer Setting: Enabled
GPO: Default Domain Policy
Policy: PasswordComplexity
Computer Setting: Not Enabled
GPO: Default Domain Policy
Policy: ForceLogoffWhenHourExpire
Computer Setting: Enabled
GPO: Default Domain Policy
Policy: ClearTextPassword
Computer Setting: Not Enabled
Event Log Settings
------------------
N/A
Restricted Groups
-----------------
N/A
System Services
---------------
N/A
Registry Settings
-----------------
N/A
File System Settings
--------------------
N/A
Public Key Policies
-------------------
N/A
Administrative Templates
------------------------
N/A
USER SETTINGS:
Applied Group Policy Objects
--------------------------
Default Domain Policy
The following GPOs were not applied because they were filtered out
--------------------------
Local Group Policy
Filtering: Not Applied (Empty)
The user is a part of the following security groups:
--------------------------
Domain Admins
Everyone
BUILTIN\Administrators
BUILTIN\Users
NT AUTHORITY\INTERACTIVE
NT AUTHORITY\Authenticated Users
LOCAL
Resultant Set Of Policies for User:
--------------------------
Software Installations
----------------------
N/A
Public Key Policies
-------------------
N/A
Administrative Templates
------------------------
N/A
Folder Redirection
------------------
N/A
Internet Explorer Browser User Interface
--------------------------
N/A
Internet Explorer Connection
--------------------------
N/A
Internet Explorer URLs
----------------------
N/A
Internet Explorer Security
--------------------------
N/A
Internet Explorer Programs
--------------------------
N/A
The mailbox isn't connected specifically to the user so as long as you don't delete the mailbox when deleting the user you can assing rights in teh Exchange tabs in the user in AD users and computers or as has been said exmerge in and out.... you can give his 'new' user rights to the mailbox before deleting / disabling the old a/c for a while if you prefer.
Good luck
Steve
I'm back. Sorry guys I was sent out of town. Nonetheless I've learned that It is best to run exmerge from a workstation that has Exchange Administrive tools loaded on it as opposed to running it directly from the server. Is the administrative tools on the exchange CD? I will google this info but I just wanted to inform you that I was back and was wondering if it can on the actual CD.
Business Accounts
Answer for Membership
by: dragon-itPosted on 2006-12-04 at 12:46:20ID: 18071668
What is in the startp script... is there anything in there that could be doing that... try isolating it. If this is a batch file then
p.txt 2>&1 up.txt 2>>&1
mkdir %userprofile%\logs
net use xyxyxyxy >%userprofile%\logs\startu
net use xyxyxyxy >>%userprofile%\logs\start
etc. to redirect all output and error output to a log file to see what is going on.
Secondly you could take out any @echo off at the top of the script and/or add pause commands in it to see where the error occurs.
or even temporarily remove the startup script. errors like that can easily be something like a command that has been remarked out but has a
command seperator in the middle, e.g.
REM This is isn;t used any more & it won't work
would try to run 'it won't work' as a command.
Few pointers? ask or post some more details if you want more
Steve