stratisphere Posted December 10, 2008 Posted December 10, 2008 (edited) Hi All, As promised in the previous thread about duplicate logins, i've seperated our software we use to manage this. Please consider this as Beta software. It may not work on your network. I've only tested it on ours. However please do let me know if you find any problems. At the moment the logging feature of it isnt complete. But thats being worked on. I'm just releasing it as-is for the moment as I promised this about a week ago now! Basically, it consists of a server and client. The client is totally managed by the server, no client side settings are needed. The way the client finds the server is via multicast, so if you have a subnetted network, you may find that a problem unless you relay multicast packets. There is the framework inside for clientside server settings... just havnt finished it yet Anyway, let me know what you think! (Oh yeh, simply run the client on user login... via gpo/script etc. If the user kills the process, it counts as a logout).DuplicateLoginManager.rar Edited December 10, 2008 by stratisphere cant spell 2
TheScarfedOne Posted December 10, 2008 Posted December 10, 2008 YAY - good work. Going on my test network now...
6Foot2 Posted December 10, 2008 Posted December 10, 2008 I am interested in this but I can't open the archive [RAR] file. I will try to remember to have a look at home. In the meantime I would like to check if it is suitable for use on our network. We have deployed a Vanilla solution with Server 2008 Standard 64 Bit on the server and XP Pro SP3 32 Bit on the workstations. Many thanks.
stratisphere Posted December 10, 2008 Author Posted December 10, 2008 Sorry, i meant to do it as a ZIP bit clicked the wrong option Use WinRAR and it should open fine. As for requirements; you need .net 3. There isnt any reason why it needs 3 other than I compiled against it, if thats a problem then lemme know and i'll compile against .net2 Other than that... thats about it. For the logging features (when they are done) the server will need access to a MySQL server, but other than that, clients need to simply be able to connect to the server on which ever you specified. By the way... the server settings may be buggered. If thats the case, put this in the same directory as the server and save it as config.xml true 127.0.0.1 4044 1000 true Multiple Login Detected Your account is logged in elsewhere. Please log off there before logging in. 30 true true false false false false
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now