Now, the logon.vbs does not seem to be loading. Is there anything else I can try, to get this working.
Thanks again
Be systematic. Use this debugging method:
1. Copy the script and batch file into a local directory on one of your XP boxes.
2. For troubleshooting purposes make a cleanup file. If your script maps drives j:, k:, l:, and m: create a cleanup.bat file which has these contents.
net use j: /d
net use k: /d
net use l: /d
net use m: /d
This will unmap the drives for debugging purposes.
3. Next, try manually running the script. On one of your XP boxes, go out to a command prompt. CD to the directory where you put the local copy of the script and the launcher bat file.
4. Run the vbscript file manually. Don't double-click it; at a command prompt run cscript logon.vbs from the directory where you have the local copy. Troubleshoot the vbs code first.
5. After you get the vbs code working, then create your launcher batch file to contain the cscript command.
6. If you have trouble getting the code to run at all, check your antivirus software, firewall, and local security policy on the XP boxes. Any one of these may have a rule that prevents VBscript from running. You should create an exception (hopefully a granular exception just to allow this specific vbs file, not a blunt instrument that allows all vbs to run)
7. Once you get the script running on the local box, then copy it up to the netlogon share. Again, make sure the files are world-readable.
8. Try running the script manually at a command prompt on an XP box. First run cscript locally with the path to the logon script as your argument, e.g. cscript \\eboxservername\netlogon\logon.vbs.
9. After you can run the vbscript manually using the local cscript command, troubleshoot the launcher batch file.
If you go through these steps you should be able to get it working. Start local, start simple.
Without trying to give a full WSH course, here are some pointers:
Apostrophe (unshifted character just to the left of the Enter key) can be used to comment out a line in the vbscript. Comment out lines to make your script simpler while you're debugging.
For each procedure you are executing, insert a command like this one to help the troubleshooting process:
wscript.echo "the script got this far."
This will give you some screen output to let you know how far the script got - be a bit more descriptive in your prompts.
While debugging insert this command at the top after Option Explicit (you can comment out the option explicit command as well)
on error resume next
this will allow the script to keep running even after errors, though if there is a compilation error the script still will not run.
Also make sure you have the latest version of the script processor loaded. At a command prompt enter cscript with no arguments. The logo will be the first part of the response - current version is 5.7, generally what is installed with XP is 5.6. You can get 5.7 here:
http://www.microsoft.com/downloads/details.aspx?FamilyID=47809025-D896-482E-A0D6-524E7E844D81&displaylang=enThose are general troubleshooting and debugging guidelines. Good luck!
Rob