Hi, I've had a look at the the drive mapping through WSAM PDF and we're still having issues. A bit of background first... Clustered (A/P) SA4500s, running 6.5R1 (build 14599). We run Outlook/Exchange and a number of our users have PST data files out on our NAS. When in the office, a user boots his/her machine and part of the login process is a VB script that maps the network drives. I have added NetBios as a supported WSAM application, and added the server holding the network drives in the WSAM allowed servers. I have also added two of our AD servers to the "allowed servers" since the VB script that does the drive mapping is located on our AD servers. So here's the issue... 1) I have set the UNC path to the session start script in the "Options" section of SAM. It never loads/works. I don't see any errors, but the drives are not mapped on remote machines using SAM. 2) It takes ages for the WSAM icon to turn blue. I'm guessing that this is because it's waiting for the script call to time out? 3) Our users are getting this annoying pop-up from Outlook since it cannot connect to the network PST files (the root issue from which all of the others have arrisen). So you see- if the drives mapped via the script, then there would be no PST error. So how do I get this blasted VB script to launch correctly, which might very well resolve the slow-load issue as well? When you right click WSAM and go under the details tab, you see the correct servers (two AD servers and the network file server) and applications defined (NetBIOS and Outlook.exe). I know this has to be one or two simply changes, but so far I haven't been able to figure them out!! Any help would be appreciated. :)
... View more