Forum
Posts 1 - 10 of 26 First | Prev. | 1 2 3 | Next | Last | All
Topic: «DeviceLock Service not stoppable»
« Previous topic | Next topic »
|
Fred Goldbeck
User profile Posts: 19 Joined: 08/20/2007 |
Hi,
we want to update DeviceLock-Service from 5.71 to 6.2. By executing the MSI, the Service is updating itself. Now the problem: under version 5.71 the service was able to stop/start with Administrator privileges. After Installing the Service-MSI (6.2) the Service is not start/stoppable, even "Default Security" is enabled or special Administrators are defined. In all cases the service keeps unconfigurable... What can we do, that the service after installing dont denies its configuration? |
||
| Posted: 11/29/2007 14:45:46 | |||
|
Roman Gaditskiy
Guest |
Have you tried to use the consoles from 6.2 version to configure the service? | ||
| Posted: 11/29/2007 14:54:36 | |||
|
Fred Goldbeck
User profile Posts: 19 Joined: 08/20/2007 |
Hi after installing the service-msi the service was not able to stop.
After that, wie tried to configure the service by using the 6.2 console. In all cases at the menu "DeviceLock Administrators" the service keeps unstoppable, also after system-reboot. We tried that on several machines, which are in Domains and some which are not in Domains (without group policies). At all machines the service all times is unstoppable after upgrade from 5.71 to 6.2 |
||
| Posted: 11/29/2007 15:20:30 | |||
|
Roman Gaditskiy
Guest |
It is not quite clear what you mean by saying it. If you need to stop the service use "dlservice -e" command. Please, describe your problem in more details. Have you succeeded in configuring the service with the consoles from new version? What console do you use (DeviceLock Management Console or DeviceLock Enterprise Manager)? |
||
| Posted: 11/29/2007 15:28:33 | |||
|
Fred Goldbeck
User profile Posts: 19 Joined: 08/20/2007 |
Hi, the stopping of the service by "dlservice -e" works fine but we want to stop the service by Windows service-console or with WMI-Scripts. That doenst work. | ||
| Posted: 11/29/2007 15:46:39 | |||
|
Roman Gaditskiy
Guest |
This is not recommended. The service should be stopped using the mentioned command. |
||
| Posted: 11/29/2007 15:56:00 | |||
|
Fred Goldbeck
User profile Posts: 19 Joined: 08/20/2007 |
its not a bug, its a feature, right? | ||
| Posted: 11/29/2007 16:06:28 | |||
|
Timour Gousseinoff
Senior Technical Support Engineer Editor User profile Posts: 276 Joined: 06/28/2005 |
Exactly. Extended components protection, so to say. | ||
| Posted: 11/29/2007 17:52:00 | |||
|
Fred Goldbeck
User profile Posts: 19 Joined: 08/20/2007 |
It may be better, that the customer can decide, how secure their clients will be configured.
For supporting our 1500 clients it will be much easier by scripting the services with Microsoft WMI-technology than manually to stop the dlservice with dlservice -e on each machine. |
||
| Posted: 11/30/2007 10:32:26 | |||
|
Ekaterina Vavilova
Technical Support Engineer Editor User profile Posts: 568 Joined: 06/27/2007 |
You can create a logon script, keeping in mind command "dlservice.exe -e" | ||
| Posted: 11/30/2007 11:02:59 |
Posts 1 - 10 of 26 First | Prev. | 1 2 3 | Next | Last | All
Stay in contact with us through:
