Re: VBS will not run on some machines, NO errors



Establish sorted file list pictures of good vs: bad machines.

----------------------------------

1. Use ms method of install (whatever)
2. Alternatively invoke "context menu" inf install.
3. Install before boot.
4. and so on. There are many methods.

------

You may also work it out in other ways.

***********************************************

"When I go to a command prompt on this server and type Wscript.exe"

Here the thing is not in the path. If a reg key prevents that, still it is
not in the path.

*************************************************

There is not preference of a computer of some files over others
as long the have the same name. (even when signed or 'system restorable')

*****************************************

This is the MS tragedy.

But may point you in a direction.









"TamaraSJ" <news@xxxxxxxxxxx> wrote in message
news:1164162606.368421.15550@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Hello everyone,

I have a couple .vbs files running via Group Policy during login. For
most computers on the network (2,500+) the scripts are running fine. I
have 2-3 computers (and one server); however, that will not run the
scripts.
The scripts are run by user but on a few machines they just don't seem
to run (these same users work fine on other machines, so I have it down

to machine). There are no error messages (not using On error, resume
next),
it just doesn't run (even when run from a command prompt).

I have researched this extensively. These are Windows XP and a newer
2003
server with nothing changed in the file associations or registry to
prevent vbscript.
I have also checked the virus software and nothing there. We also tried
re-installing
WSH 5.6 and none of these things worked.

When I state that we tried to run the script manually, I mean by
double-clicking and via command prompt. The script normally runs at
login via group policy.

When I go to a command prompt on this server and type Wscript.exe,
nothing happens. On most machines I receive the wscript.exe setting
box. This server (I also have two PCs with this issue) just won't run
the file and I can't find anything to explain it.

Any help would be greatly appreciated. I'm beating my head against a
brick wall on this one. I normally wouldn't care that the script
doesn't run on a server but this is a Citrix server that needs to run
the script. The other Citrix servers are running it with no problem.

Thanks again...... Tamara


.



Relevant Pages

  • Re: network slows down after SP2 install
    ... the machines updated from W2K still open and read the ... Locate the "Microsoft network server: ... Install SP2 for WIN XP and latest service pack for Office 2003 on ... Microsoft CSS Online Newsgroup Support ...
    (microsoft.public.windows.server.sbs)
  • Re: network slows down after SP2 install
    ... These machines cannot even run the program locally being disconnected from the server with a local copy of the database. ... Install SP2 for WIN XP and latest service pack for Office 2003 on ... Microsoft CSS Online Newsgroup Support ...
    (microsoft.public.windows.server.sbs)
  • Re: Exchange on VMWare
    ... I have found in the past that installing exchange on the dc then removing it ... Check to be sure that your virtual member server is also using your vm dc ... resources outside of my vm machines, I just want this member server ... However when i install exchange on the member server it cannot find the ...
    (microsoft.public.exchange.setup)
  • Re: Use Group Policy to assign computer startup scripts for 2007 Office deployment
    ... The Office 2007 pro install takes nearly 40 minutes, ... I just edited the local machine policy to run this script on ... Simplify Group Policy Troubleshooting with the NEW GPExpert ... machines under it. ...
    (microsoft.public.windows.group_policy)
  • Re: network slows down after SP2 install
    ... duo xp pro machines are the slower ones. ... terminal services as well on this server which is the domain controller. ... It is also odd that the physical network now cannot run ... machines with the SP2 install that prohibits running the program either ...
    (microsoft.public.windows.server.sbs)