In a windows domain network, suppose there's one machine which is used most often to share files in the network. My question is: if this machine boots up and no user logs on - i.e. it is stuck on the logon screen...can other machines access the shared resources on this machine?
I'm guessing on a user getting locked out - this must be possible, but does it hold when no one has ever logged ons since the machine booted?
I am building an intranet application for a Windows Domain based network. It is a client-server application - the server being an ASP .NET web application and the clients - .NET 2.0 based desktop applications. I intend to use Active Directory and Group policies to install the client application across clients in the network.
Are there any general guidelines that need to be followed for building an application of this sort?
Any security issues to be aware of?
Is it okay to have a web application work as your server in an intranet solution of this sort - given that clients wouldn't communicate with the server using sockets - instead clients would communicate with the server using simple web service calls?
Anything in particular that I need to know before going ahead with this type of app-building?
How does this generally work?
Are logon scripts used? If yes, is there a standard script to trigger installation of softwares when a client logs on? (an example could really help)
Or is another method used?
I have a client server application - intended for use in workgoups.
The server is a web application, clients are .NET 2.0 based desktop applications.
Is there a way to push/force the setup of the client application on all machines in the network?
Any group policy equivalent/any way to centrally manage/push an installation on a windows workgroup based network?