Background: We are a vitamin manufacturing company in Temp AZ. I’m am relatively (5 months) new to my position of sysadmin. We have an ERP called process pro that we utilize on 2 different terminal servers (win2k3 domain). One terminal server (windows 2008 r1) is for desktop users and it hosts a drive that is critical to the ERP. The second terminal server is running windows 2003 R2 and it is used for our handheld scanners in the manufacturing/packaging/shipping/receiving area. This server maps the drive on the other server for the ERP using drive letter U:. We have in place, a script that runs the following on login:
net use u: /delete /yes
net use u: \\server\ProcessPro$ /PERSISTENT:yes (renamed it "server" for securities sake)
On Friday last week we replaced our main switch that everything runs through. The swap went smoothly and we were able to communicate to the servers from every computer.
Problem: After the weekend we are having an issue with a specific mapped drive getting lost on our terminal server for the scanners. For a select few users, one of them being a domain admin and the other a standard user, the script fails to map the drive we need for the ERP. The script hasn’t changed for a long time before this and the accounts have been around for at least 3 months. I modified the script so that it only checks if the mapping is there and creates it if it isn’t.
net use u:
if errorlevel 1 goto create
exit
:create
net use u: \\server\ProcessPro$ /PERSISTENT:yes
Even after this change we are experiencing the same issue. Even if I manually map the drive and take off the script it loses the mapping when I logoff then log back in. I have spent some time troubleshooting the issue, along with trying to fix the underlying problem so we don’t need the script at all, and after failing, these are the facts I have come up with so far:
• It appears to be losing the mapping sometime between logout and the next login.
• It is only specific to the drive letter we are assigning the drive ( U: ). If we map it to any other letter it holds but the ERP still wont launch because it is programed to look specifically at U: (we cannot change this).
• It will stay for the administrator account at the drive letter “U:” but no other account.
• I ran rsop.msc and it still says that it ran the logon script upon login. (it was previously disabled).
• It holds other drives on different letters without issue.
• The issue is only on this one server.
• I didn’t see anything in the logs that would indicate a source of the issue.
Has anyone experienced this kind of an issue before? It seems very odd to me that it is drive letter specific.
Let me know if you need any clarification or more information. I will keep plugging away at this in the meantime.
Thank you for any help!
