selective scripting problem

I am using a VBS logon script to map network drives. The script runs perfect on most PCs, but there are a few random machines that will not run the script.
The Pcs are all xp pro, and i have the script set at the OU container level. When I assign the scirpt to the user profiles it works flawlessly, but once I move it to the OU certain PCs will not run the script.

I think its the PC as I had the user with the issue log onto a different pc and his drives mapped fine.
I have message boxes that appear if the drives map or if there is an error. I receive neither message on these defunct PCs. I am assuming the pc is not running the script at all.

Any help would be great!

 

.

 

Fast logon

disabled fast logon. Defunct Pcs lock up on log in. sounds like a network connectivity issue

 

You could test this by creating a script that fired a simple process that you could look for on the PC. Perhapsd a batch file that opened a command console (.BAT file with a single line containing: CMD).

If the problem is permissions or PC setup the script won't run. If it does run, but more complicated scripts won't then it could be a performance problem.

OUs aren't implemented very well in Active Directory (in my opinion). If they were you'd be able to set file access rights using them. I'm always wary of using them for anything more that symoblic links and simple grouping of users. Have you tried setting the script at the root? It may not be the best final answer, but would a least tell you if this is an OU issue.

 

I have the script currently popping up a box on the desktop whenever it runs. the PCs with the issue do not display this box. I tried linking the script from the netlogon folder, but same issue happens. Gave the everybody group access to the script file.

 

I think your problem may be that the PC aren't being registered correctly on the network. I'd try rejoining them to the domain/AD. It might be worth deleting the computers from the AD before rejoining them. I'd also set the PC to join a workgroup before setting them back to use your AD's domain, as this may give the set up a better clean out.

I'd also check the DNS settings to make sure that they are using the AD server as their DNS server.

Also back up the user profiles before you start playing around with the domain settings. I'd suggest using the "Files and Settings Transfer Wizard" to save profiles onto a central location (you need plenty of space as the backup will include the "My Documents" files). Then if fixing the problem results in users profiles being recreated, you'll be able to restore their settings using the migration wizard to copy in the saved files.

 

Make sure the pc's are in the newly created OU. Also make sure that conflicting policy's aren't being applied to the problem users / pc's. Some policy's have to be set to merge or override in order to get them to work properly together.

 

PCs

The policy is placed on the user configs. SO no it's on the PC's at all. I enforced the login script policy and still nothing. The user can log in to a different PC and get their drives. When I logged into their PC i did NOT get my drives. nor did th escript run at all. I am curiuse if there is some random setting on that PC that is blocking the script. I checked and scripts are enabled and the firewall is off......