• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Help: Windows 2000 Server --> Win95 domain scripting

I have a Windows 2000 domain with Win95 workstations and I have a script located in c:\WINNT\SYSVOL
SYSVOL\DOMAIN\SCRIPS\

Which goes something like:

NET USE H: \\server\username

Windows 95 IS NOT picking up the fact that I want it to run this script from the server. It totally ignores the script.

I found THIS on MS KB:
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q142672

Does that mean that NO ONE has ever ran a script on a Win95 station from an NT/2000 serve
Thanks
 
how does windows 95 know to run this script? Are you trying to execute it as a per-user logon script?
I've made win95 clients run startup scripts before so it can be done...
 
Well I specify in users and computers in the profile section of that domain user to run a certain script on the server.

Win95 should pick that up when it logs onto the domain.
 
Hi there. By Default, Windows 95 does not run any Windows 2000 logon script specified in the Domain Group Policy. You'll likely have to install the Active Directory extensions on your Win95 machines for them to apply the Group Policy. If the script(s) you are wanting to execute are written in VBScript or WScript, then you'll have to install the runtimes on the Win95 machines for them to be able to run them. I hope this helps as I have had no experience in having Win9x machines in my domain since it is strictly NT 5.x.
 
Those logon scripts are not part of group policy, and should be processed by win9x clients.
It could be that the script is running, but the command is failing.
Try changing the script to something simple that you can check like "echo itworks>C:\script.log" to check it isnt running at all.

Are the clients told to log onto an NT domain, and are you giving them user level access control?
 
Back
Top