|
Hi Guido,
See inline
answers
We are not going to put more
time in this as we are not able to find the problem. Last week we had a user
where it first did not work and a day later it did work.... (nothing changed as
I know of). For those where it still does not work we provided a batch file to
re-create the H- mapping after the user has logged on
Greetz,
Jorge From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Grillenmeier, Guido Sent: maandag 28 februari 2005 9:27 To: [email protected] Subject: RE: [ActiveDir] OT: VERY STRANGE ISSUE - Windows 95 and Long File Names Hello Jorge and Paul,
...but it happens on all Win95 clients ?
ANSWER: that's the funny part... NO,
not on all Win95 clients
well, first of all, it may be wise to get rid of
Win95, but I'm sure you've been through all of that ("no time and budget to do
so right now", "it worked before, so why shouldn't it work now", "need to get
this working now and will fix my OS issue later")... Funny how companies
sometimes spend thousands of dollars for fixing problems that wouldn't exist if
they spend the same money to update their systems ;-) As you know,
I'm also currently supporting a Novell/AD migration with thousands of NT4
clients...
ANSWER: I know what you mean
that companies sometimes believe that it's cheaper to screw around and keep the
old crap running than implementing a new clean system. In short term they might
be true, but in long term the money that was used to keep the old crap running
could used to implement a new system and afterwards to have a huge party!
;-))
At the
same time we're migrating from the client/server concept to the SBC
concept. Users on Win95/98 have apps installed locally. In time, local apps
(I mean the exe that start the
app) are de-installed and they receive their new version
app through Citrix. When all apps are almost
done
Back to your problem: I hope it's fair to
assume, that you only have a limited amount of Win9x machines in the environment
and most other clients are WinNT and above so that anything you're going to
do to fix the Win95 issue now is of temporary nature - correct?
ANSWER: it's the other way
around. Mostly W95/98 and some NT based systems
(WNT/W2K/WXP)
If that assumption is correct, I wouldn't really do
any more work on this to solve the issue, as you already have it solved: just
re-map the homeshare for the Win95 clients during the execution of the login
script. You shouldn't have an issue simply checking the OS env-variable
and for all clients that are not equal to Windows_NT unmap and re-map the
homeshare. Assuming you want to map a share that contains the
logon-name of the user, it may be wise to pass the user's samaccount
name as a parameter to the logon-script (as far as I recall, Win9x clients
don't automatically get the username variable in their environment).
ANSWER: That's the fun part...
it's the mapping that created through the loginscript (NET USE H: /HOME)
that sometimes does not allow to rename to LFN. After the user has logged
and executes "NET USE H: /DELETE & NET USE H:
/HOME" the problem disappears. If I map the home directory
in the loginscript to another DRIVE it works without the error!!!??? Fun ain't
it?
/Guido From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Paul van Geldrop Sent: Friday, February 25, 2005 8:42 PM To: [email protected] Subject: RE: [ActiveDir] OT: VERY STRANGE ISSUE - Windows 95 and Long File Names Oh, And to add those finest
little details: Same users, same
documents on Windows 98.. no
problem. Open a document with a
long file name in the corresponding application, and ‘save as’ under another
long name.. no problem
either. Yeah, time for more
beer.. Regards, Paul -----Original
Message----- Hi,
During
our Novell/NT4 to W2K3 migration we are experiencing a very very strange issue
that we until now have not been able to solve. The
situation is: * The
Netlogon loginscript makes a H-mapping for a user to its homedirectory on the
windows file server The
issue: The
problem: The
VERY STRANGE ISSUES: * If we
in the command prompt type "NET USE H: /DELETE" and after that "NET USE H:
/HOME" (delete the H-mapping and create it again) the problem does not occur
--> ????? WTF is
this???!!! I have tried everything, at least I think I have, and it's making me
nuts. The
workaround we have until now is that we've sent those users a batch file that
recreates the H-mapping, but I would like to solve this by making it work in the
loginscript I'm
going to get a beer and play some darts Regards,
This e-mail and any attachment is for authorised use by the intended recipient(s) only. It may contain proprietary material, confidential information and/or be subject to legal privilege. It should not be copied, disclosed to, retained or used by, any other party. If you are not an intended recipient then please promptly delete this e-mail and any attachment and all copies and inform the sender. Thank you. |
Title: OT: VERY STRANGE ISSUE - Windows 95 and Long File Names
