- Oct 23, 2000
- 9,200
- 765
- 126
I apologize if this has been answered already, but I've searched here and on the FaD forums and can't find a solid answer.
As some of you already know, a moronic contractor killed my FaD install at one of the offices I take care of, and even though the boss said I could put it back, I know the idiot contractor will try to zap it again and I can't tell the boss to sack the contractor because he's a close family friend of the boss. :disgust:
So....
I want to install FaD using the new version's ability to run as a service, but I have a couple of questions first:
1) If I do a centralized install on the server can I still run the client as a service on the workstations considering the fact that users have to be logged in to the domain to access files there? Workstation policies are set up so that users have to be logged in to the domain to access local and shared network resources on the workstations as well so putting the 'server' on a PC would have the same restrictions. I'd really like to stick with a server install since that makes it extremely easy to track the progress of all of the clients using FADSpy (individual installs would mean I have to share folders on each of the individual workstations, which I'd rather not do if I don't have to).
2) Regardless of whether I put the client on each individual PC or put it on the server, can the service be configured to not show up in Task Manager so the moron can't see that it's running and try to remove it again? If it can't be completely hidden, can it be set up as a system service so that it can't be killed from within Task Manager?
I'd really like to get the 20 PCs at this office up and running again, so I'd appreciate any input you can give me.
Thanks,
Fardringle
As some of you already know, a moronic contractor killed my FaD install at one of the offices I take care of, and even though the boss said I could put it back, I know the idiot contractor will try to zap it again and I can't tell the boss to sack the contractor because he's a close family friend of the boss. :disgust:
So....
I want to install FaD using the new version's ability to run as a service, but I have a couple of questions first:
1) If I do a centralized install on the server can I still run the client as a service on the workstations considering the fact that users have to be logged in to the domain to access files there? Workstation policies are set up so that users have to be logged in to the domain to access local and shared network resources on the workstations as well so putting the 'server' on a PC would have the same restrictions. I'd really like to stick with a server install since that makes it extremely easy to track the progress of all of the clients using FADSpy (individual installs would mean I have to share folders on each of the individual workstations, which I'd rather not do if I don't have to).
2) Regardless of whether I put the client on each individual PC or put it on the server, can the service be configured to not show up in Task Manager so the moron can't see that it's running and try to remove it again? If it can't be completely hidden, can it be set up as a system service so that it can't be killed from within Task Manager?
I'd really like to get the 20 PCs at this office up and running again, so I'd appreciate any input you can give me.
Thanks,
Fardringle