Not running scripts

Hello,

I have this problem of not running logon scripts, I have come up with the problem being that to many people log on at one time causesing it to get skipped, how can I stop this? I am wanting it to only be on the one server, so all users can access it and if it needs to get updated it is easy to do. It seems to only affect the Windows 7 machines. Though sometimes XP machine do it too.

I do have this code in it, should I make it so it randomly makes and number between 100 and 200 and then run it?

-->

'Wait until the user is really logged in
strUserName = ""
While strUserName = ""
WScript.Sleep 100 ' Wait 1 second
strUserName = WSHNetwork.UserName
Wend

strUserDomain = WSHNetwork.UserDomain

<--

Thank you, C3sium

server 2008 (r2) or 2003 (r2)?

this helps with the issue if we know which server its based on

Hello,

It is on windows server 2003 entiprise edition SP2

Thank you, C3sium

I think scripting on windows 7 is different because when I have been looking at wmi and other examples on the ms website or else where it states which operating systems support which ever methods you are using, also in the script example I did not see the creation of the network object ie

Set WshNetwork = CreateObject("Wscript.Network")

Or

Set WshNetwork = Wscript.CreateObject("Wscript.Network")

Also 1000 ms is one second , not 100 or 200.

Other then that I don't have much time to look into it now but will come back to this later unless srochford or someone else can assist you in the mean time.

A few thoughts

1. Have you set GP to 'Always wait for network at startup and logon'?
2. Have you set run logon scripts synchronously in GP?

Hello,

The script runs fine when one at a time, but it is when it runs at the same time... it fails

Also I did not write the script, or setup the GP. :)

I will have a look at that tomorrow cookie, and report back.

C3sium

Quote:

---

Originally Posted by C3sium

Hello,

The script runs fine when one at a time, but it is when it runs at the same time... it fails

Also I did not write the script, or setup the GP. :)

I will have a look at that tomorrow cookie, and report back.

C3sium

---

I've had issues with scripts becoming unreliable when there's load on the servers as well but setting those two settings has always solved the problems.

Hello,

I have found both of those commands in the GP and have enabled both of them.
Looks like I have found a new job, Looking through the GP :( and testing....

I will give that a go today, see how they go over the course of the day and report back.

Thank you Jamie.

Hello,

After a few periods of testing, it has reduced the number of computers affected but not completly.
Any more ideas?

Thank you, C3sium

Just a thought, how many domain controllers do you have?

Hello,
We have 2 domain controllers, and they mirror each other.
Anyone got any ideas?? I had to run the script 10 times last period, very over it!
C3sium

And the scripts are running from the netlogon share, and not a shared folder, yes?

maybe way off the mark here so apologies in advance but if you did a gpupdate on both servers and then did a force replication and then tried again would that help ?

Quote:

---

Originally Posted by C3sium

Hello,

After a few periods of testing, it has reduced the number of computers affected but not completly.
Any more ideas?

Thank you, C3sium

---

As the others say check that your scripts are replicating to all of the netlogon folders.

Can you clear the event log on an affected client then reboot it and check the event log again. Post any errors.

It might be worth posting the script as well, what is it doing, drive mapping etc?


You said it's affecting Windows 7 and XP boxes right?

Quote:

---

Originally Posted by Dos_Box

And the scripts are running from the netlogon share, and not a shared folder, yes?

---

The scripts are running from \\mserver\NETLOGON which is shared and student can access this folder and contents(more than likly they can change it too).

Quote:

---

mac_shinobi;
maybe way off the mark here so apologies in advance but if you did a gpupdate on both servers and then did a force replication and then tried again would that help ?

---

Can you post help on this topic to make sure I do it correctly.

Quote:

---

cookie_monster

As the others say check that your scripts are replicating to all of the netlogon folders.

Can you clear the event log on an affected client then reboot it and check the event log again. Post any errors.

It might be worth posting the script as well, what is it doing, drive mapping etc?


You said it's affecting Windows 7 and XP boxes right?

---

When I compare the scripts they are the same, from the two servers.
I will try to post the script and check the logs in the morning, at the moment it is 8:30pm here.
the script remove drives then map the drives and maps printers and set default printer.
Yes Windows 7 desktop(dell 780) and laptops(thinkpad r500) and some XP desktops.

If you have any more ideas let me know.

Thank you, C3sium.