Why not just replace the drive mapping with a UNC path? -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Anthony Youngman Sent: Friday, July 06, 2007 7:04 AM To: [email protected] Subject: RE: [U2] UD Phantom Credentials
Ouch !!! I can tell you WHAT is happening. How you solve it is a policy issue, not a technical issue. Basically, drive mappings are system-wide, not user-related. If you have multiple processes/users all wanting their own unique drive mappings, sorry it's not going to happen! We had this exact problem - our backup script on our servers had its own drive mappings. Our dear consultant (until we screamed at him once we realised what was happening) had this nasty habit of (a) using our server as his personal workstation, and (b) forgetting to log off. The ramifications were many and annoying, including such things as failed backups... Anyways. You have to have a policy saying that either (a) THIS is the set of drive mappings on the server and THEY MUST NOT CHANGE, OR (b) every process needs to set its own drive mappings on login, and every process needs to be aware of every other process that does this to avoid a collision, and no users are to leave the console logged in to mess things up. Your call ... Oh - by the way - stick a "net use disconnect" whatever the syntax is before every connect. That way, at least if there's no-one logged in holding the drive, you'll get rid of whatever setting it's been left at. Otherwise, if they did a "remember this setting", your process will load their mapping, then your explicit mapping will fail with "drive letter already in use". Cheers, Wol -----Original Message----- From: Bill Haskett [mailto:[EMAIL PROTECTED] Sent: 06 July 2007 09:56 To: [email protected] Subject: [U2] UD Phantom Credentials A look at Google tells me this is some kind of drive mapping problem associated with a possible conflict with non-administrator users and the "net use" command. It so happens that I've mapped an ftp server's drive onto the UD server (Windows) as the "N:\" drive. To get UniData to use this "shared" directory, on the other server, I have to insert !net use N: \\sftpserver\ftpdir {password} /user:{sftpserver\userid} ...into the LOGIN paragraph (it appears this has to be run at each invocation of a UD shell, aka UD login). I then create a (VOC) entry: ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/ ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
