I have about Windows 2008 R2 Remote Desktop Servers in farm. To the best of my knowledge they are all have the same update status and they are also goverened by the same GPO. Among others, users logging in via RDP execute a login skript mylogin.cmd
that maps a drive I: unless for some individual reasons they already have such a drive:
if exist I:\*.* goto havei
eventcreate /ID 1 /L APPLICATION /T INFORMATION /SO LogOnOffDebug /D "Try Map I:"
NET USE I: \\myserver\myshare /persistent:no
eventcreate /ID 2 /L APPLICATION /T INFORMATION /SO LogOnOffDebug /D "errorlevel = %errorlevel%"
if exist I:\*.* goto havei
eventcreate /ID 3 /L APPLICATION /T WARNING /SO LogOnOffDebug /D "This is bad"
:havei
As you see, I already added some lines to debug the problem, and this is what I observe: I find events 1 and 2 in Event Log, but not event 3. So apparently,
- the
NET USE
was executed because no I: files were seen, - the command executed without error,
- and after execution I: is visible.
That is precisely what should happen and it does happen so on all farm members.
However, on two of the machines the users do not see drive I: in their sessions afterwrads! The same drive that was checked to be visible during login script execution just as on the other farm members! This looks to me as if the drives mapped during script execution are not "exported"(?) to the normal session. Simply executing the very same login script afterwards during their running session helps and gives them their drives, but this is of course not a suitable remedy.
What could even be the difference between the many good and the few bad servers that causes such behaviour? (I might add, that this phenomenon has crept up recently and had not existed for several years before - so something must have been done to the bad servers recently , but I have no idea what)