Yesterday I posted "Windows 7 x64 Drive mapping error.



The group I was working with is at a remote site so I posted what I had at
that time.



I now have a copy of the login results window and although there was an
invalid drive. That issue had nothing to do with the issue I am addressing
here.



It appears that on AMD64 machines client 2 sp1 ignores IF - THEN statements.



The login script results clip is:


Your current context is ***.***.*** Your current tree is: **** You are
attached to server *******.
Drive R: = *******\COMMON:SHARED \
LOGIN-LGNWNT32-440: The operation was attempted on an invalid drive.
Drive M: = *******\HOME:CHEMGRP\KPARMENDA \
S1: = Z:. [XXXXXXXX.Malott_Servers.:PUBLIC \]
S2: = Y:. [XXXXXXXX.Malott_Servers.:LOGIN \]
Drive I: = *******\COMMON:APPS\PCAPPS \
Drive W: = ********\COMMON:APPS\W95APPS \



****** denotes an OES2 SP1 server
XXXXXX denotes NW6.5 sp6 server



The thing to note here is THERE IS NO MAPPING FOR THE GROUP DRIVE - NOT EVEN
AN ATEMPT TO DO THE MAP. No error no nuthin'!



I support 25 research groups and each have their own group drive. To set
this up I use a set of "IF" "THEN" statements in the container login script.



Thes Statements are like:



IF MEMBER OF ".PMH_GRP.container context" THEN MAP G:=\\IP of OES
server\path on server\PMH_GRP
IF MEMBER OF ".PRH_GRP.container context" THEN MAP G:=\\IP of OES
server\path on server\PRH_GRP
IF MEMBER OF ".PWG_GRP.container context" THEN MAP G:=\\IP of OES
server\path on server\PWG_GRP
IF MEMBER OF ".RAI_GRP.container context" THEN MAP G:=\\IP of OES
server\path on server\RAI_GRP



These have always worked like a charm since windows 3x days. And continue
to work fine with client 2 sp1 on intel-based X64 machines.



Basedo n the login results window pasted above it appears that on AMD based
64 bit machines the client isn't even reading or attempting to execute these
statements.



Direct mapping statements that appear before and after the group drive
mapping statement work, but the conditional statments - no go.



I have checked the issue on x86 Intel based machines and there is no
problem - all statements in the login script work.



The problem appears to be limited to AMD64 machines.



Anyone else noticed this? Any Ideas?



Thanks

Bob T.