cancel
Showing results for 
Search instead for 
Did you mean: 

DLO 8 Desktop Agent does not start automatically on Windows 8.1

TimSR
Level 2

Hi folks,

I just upgraded to DLO 8.0 because I had some troubled with 7.6 SP1 and I thought to fix them by upgrading. But the troubles keep existing:

On Windows 8.1 Machines the DLO Desktop Agent won't start even though it's all installed correctly.The service is running and the agent is listed in the autostart. Yet, it does not start after logging in. I can't find any misconfiguration.

If someone has an idea, please let me know.

Greetings,

Tim 

1 ACCEPTED SOLUTION

Accepted Solutions

VJware
Level 6
Employee Accredited Certified

Does it start up without any errors if you launch the DLO Agent manually ?

If yes, then try the following steps one by one -

1) Ensure System, Everyone & Administrators have full permissions at the following paths:
- C:\Windows\System32\Tasks
- C:\Program Files\Symantec and C:\Program Files(x86)\Symantec
- HKLM\Software\Symantec\Symantec DLO and HKLM\Software\Wow6432Node\Symantec\Symantec DLO

2) Ensure the Symantec DLO Desktop Agent Change Journal Reader and the Windows Task Scheduler service startup type are set to automatic.

3) Run msconfig and click on the Startup tab. Ensure Symantec DLO agent is enabled.

4) If running any Antivirus software on the client machines, please add the Symantec DLO directory as an exclusion from scans.

5) Please perform the following steps as well:-
- Exit the DLO Agent.
- Stop the DLO Change Journal service.
- Delete all and any tasks related to DLO under the Windows Task Scheduler.
- Restart the DLO Change Journal service.
- Restart the DLO Agent.
- Log off or reboot the machine. Observe if the DLO agent starts up automatically or not.

6) Lastly, if the above does not work, edit the Global Options from the DLO console. Choose Options under Global Settings and uncheck the option - Time to delay Desktop Agent startup after user logs in. Delete the .settings folder from the client machine. (Default path is C:\Users\user\AppData\Local\Symantec\DLO). Open the DLO Agent so that it retrieves new settings from the DLO server. Exit the DLO agent and reboot the client machine. Upon start-up, observe if the DLO agent starts up automatically or not.

View solution in original post

2 REPLIES 2

VJware
Level 6
Employee Accredited Certified

Does it start up without any errors if you launch the DLO Agent manually ?

If yes, then try the following steps one by one -

1) Ensure System, Everyone & Administrators have full permissions at the following paths:
- C:\Windows\System32\Tasks
- C:\Program Files\Symantec and C:\Program Files(x86)\Symantec
- HKLM\Software\Symantec\Symantec DLO and HKLM\Software\Wow6432Node\Symantec\Symantec DLO

2) Ensure the Symantec DLO Desktop Agent Change Journal Reader and the Windows Task Scheduler service startup type are set to automatic.

3) Run msconfig and click on the Startup tab. Ensure Symantec DLO agent is enabled.

4) If running any Antivirus software on the client machines, please add the Symantec DLO directory as an exclusion from scans.

5) Please perform the following steps as well:-
- Exit the DLO Agent.
- Stop the DLO Change Journal service.
- Delete all and any tasks related to DLO under the Windows Task Scheduler.
- Restart the DLO Change Journal service.
- Restart the DLO Agent.
- Log off or reboot the machine. Observe if the DLO agent starts up automatically or not.

6) Lastly, if the above does not work, edit the Global Options from the DLO console. Choose Options under Global Settings and uncheck the option - Time to delay Desktop Agent startup after user logs in. Delete the .settings folder from the client machine. (Default path is C:\Users\user\AppData\Local\Symantec\DLO). Open the DLO Agent so that it retrieves new settings from the DLO server. Exit the DLO agent and reboot the client machine. Upon start-up, observe if the DLO agent starts up automatically or not.

TimSR
Level 2

Hi,

I already tried steps 1 to 5 with the 7.6 SP1 Agent which led to no success.

Step 6 seems to have been the solution to this issue.

Thank you,

Tim