marketsons1985,
Good luck with that assimilation, if you can pull it off it will be a nice herd!
MWalkden,
I have ~25 WIN95B PCs at work that crack, logged in or logged off, the only problem I have is that the users turn them off. They are part of an NT domain, private TCP/IP network. I have a perproxy running on a WIN2K Pro PC, and it works fine.
DNETC doesn't show up in the task manager in WIN95B, but it does show up in the task manager for WIN NT and WIN2K if you do <ALT.<CTL><DEL> and look at tasks that are running. Most users don't know what they are, even if they do get there.
As far as managing the client as a service, you have to use the command line, or write some scripts like I did to do the functions I need, such as starting the service, stopping the client, updating, installing, uninstalling, etc.. I'm an old DOS guy, but I'm lazy and impatient, so I wrote scripts to do what I need quickly.
I also second the "Restart on Config Changes" option, as it also reduces time spent managing the herd. See lazy... above.
I also recommend setting up a log file, makes it easy to see what's going on with that cow.
SSP,
The service is setup to start automatically on re-boot. What I've found on the WIN95B PCs, is that if I stop the client service, then select "Close All Programs and Log In as A New User" option, then the service doesn't start. But I haven't tested that in a long time, it may have changed.
Ray