We just recently ran out of disk space on the C:\ of a Server 2008 R2 box,  so I moved the clu-prod folder from C:\Program Files (x86)\Symantec\LiveUpdate Administrator\clu-prod to the D:\ and created a junction. Functionaly the clu-prod folder is working fine, the share was recreated and can be accessed.

During the process I stopped and restarted both the 'LUA Apache Tomcat' and 'LUA PostgreSQL' service.   When I restarted them they both came up fine with no errors and I tried the LUA console on the local PC and it is working.  However when I try and access the LAU remotely through the web admin (http://server:7070/LUA)  it just goes nowhere and times out.

We use SEPM for the vast majority of our clients and SEPM gets it's updates from this LUA server,  they are both on the same host.  Running a manual LU from SEPM 'seems' to go through fine,  i.e it runs through and finds no new updates.

Though we have some clients that connect directly to the LUA and they are now failing!  Any ideas?

LUA version is 2.3.0.71.

Hello,

Please check these Threads:

https://www-secure.symantec.com/connect/forums/unable-connect-remote-dc-lua-23

https://www-secure.symantec.com/connect/forums/live-update-administrator-221-fails-work

Hope that helps!!

Thanks for you time.

I should have mentioned I have traweled through the forums lookign for a solution already and had come across those posts already.  Doesn't seem to fit.

The LUA server was working perfectly prior to this so all I did was :

1. LUA server working but C:\ full
2. Copy C:\ProgramData\Symantec\Symantec Endpoint Protection\12.1.1000.157.105\Data\Definitions\VirusDefs to D:\VirusDefs
3. Stop both LUA services
4. Delete C:\ProgramData\Symantec\Symantec Endpoint Protection\12.1.1000.157.105\Data\Definitions\VirusDefs
5. Create a Junction for C:\ProgramData\Symantec\Symantec Endpoint Protection\12.1.1000.157.105\Data\Definitions\VirusDefs to D:\VirusDefs
6. Re-create share with same permissions
7. Start both LUA services

So the clu-prod share is working (i.e \\server\clu-prod) and if I log in locally on the LUA server using http://localhost:7070/lua it is workign fine.  But if I try to log in remotely from another PC http://server:7070/LUA it is failing now,  and it also looks like the liveupdate from the SEPM servers is now failing also.

Again,  this was working perfectly about 5 minutes before this change,  the only thing changed was moving the clu-prod and creating the junction.

I guess first question is - will this even work?

And thanks again for your help and time!

Hello,

Whart products are you trying to download content for?  And is this one job trying to download everything all at once?

If so, that could be your problem there.  For example: SEP 11 and 12, client and server, V2 and non-V2, Mac and non-Mac, hub and non-hub.... if the temp location, permanent stoarge location and distribution center are all on one disk, that could very well total up to more space than the LUA server can handle in one go.

Secondly, I believe moving the clu-prod and creating a junction is not supported.

Here's an article many have found helpful:

Managing LiveUpdate Administrator 2.x Space Usage
https://www-secure.symantec.com/connect/articles/managing-liveupdate-administrator-2x-space-usage

Try a series of smaller jobs and it should work fine.  Also, have a look at what you need and what LUA is actually configured to go get--- there are usually some tuning steps that can cut the burden way down.

Hope that helps!!

Running both SEPM and LUA in same box is not recommendable.

LiveUpdate Administrator 2.x and Symantec Endpoint Protection Manager on the Same Physical Server

Is there any special reason to do so?

Hi mhouston100,

A couple of points:

We use SEPM for the vast majority of our clients and SEPM gets it's updates from this LUA server,  they are both on the same host. 

The SEPM and LUA should never be on the same server.  It's unsupported.  Here's an article on the subject:

LiveUpdate Administrator 2.x and Symantec Endpoint Protection Manager on the Same Physical Server
Article: TECH105076   |  Created: 2008-01-05   |  Updated: 2011-07-11   | 
Article URL http://www.symantec.com/docs/TECH105076 
 

Is there a specific reason why LUA is being used if the SEPM has internet access-?  Generally, in an all-SEP environment, the SEPM can do an efficient job of downloading and distributing everything its clients need.  LUA is a great product when used in the circumstances for which it was designed.

If there is a reason, I recommend upgrading the version of LUA that you are using:

LUA version is 2.3.0.71.

I recommend upgrading to LUA 2.3.1, and installing it fresh on a server that does not have a SEPM installed.  That should work fine.

Here are a couple articles about LUA that may help:

https://www-secure.symantec.com/connect/articles/managing-liveupdate-administrator-2x-space-usage

https://www-secure.symantec.com/connect/articles/helpful-liveupdate-administrator-2x-analogy

Please do keep this thread up to date with your progress!