WampServer
Apache, PHP, MySQL
on Windows
Windows 2008... Is it possible to have Aestan Tray available to "all users"
Posted by:
kendor
(---.dyn.optonline.net)
Date: August 28, 2013 09:25PM
We are working in a collaborative environment where several users may be logged in via RDP to the same 2008 server doing different things.
It appears that the Aestan tray app is only available to the user that WAMP was installed as. Is there a way for it to be accessible by all users (e.g. stop/start, logs etc...)?
It appears that the Aestan tray app is only available to the user that WAMP was installed as. Is there a way for it to be accessible by all users (e.g. stop/start, logs etc...)?
Re: Windows 2008... Is it possible to have Aestan Tray available to "all users"
Posted by:
RiggsFolly
(---.as13285.net)
Date: August 29, 2013 12:46AM
Theoretically all you need to do is give access to ?:\wamp\wampmanager.exe to the other users.
But they will have to be able to Start and Stop services, which is not a normal facility available to standard user groups.
It might be simpler to change the wampapache and wampmysql services to start Automatically. Then hand out a set of shortcuts to the ?:\wamp\logs folder.
However this sounds like a recipe for major confusion, more than one person starting and stopping Apache and MySQL without the knowledge of the other. Also managing source updates will become a nightmare.
You might be better to give each developer there own copy of wamp. And use a source managment tool like GIT or CSV. Then have a LIVE version of the system on the Server that is updated in a managed fashion.
But they will have to be able to Start and Stop services, which is not a normal facility available to standard user groups.
It might be simpler to change the wampapache and wampmysql services to start Automatically. Then hand out a set of shortcuts to the ?:\wamp\logs folder.
However this sounds like a recipe for major confusion, more than one person starting and stopping Apache and MySQL without the knowledge of the other. Also managing source updates will become a nightmare.
You might be better to give each developer there own copy of wamp. And use a source managment tool like GIT or CSV. Then have a LIVE version of the system on the Server that is updated in a managed fashion.
Sorry, only registered users may post in this forum.
