KACE Product Support

Would you please explain it further, If your kbox is unable to replicate to the remote share ?
couple of things you can check. 1. Kbox agent is installed on remote machine and it is working. 2. Are you using special characters in password ? i suggest use a-z, and 0-9 only.
Have you configured any schedule for replication ?

Regards,

Afzal

Thanks Afzal

Yes, I've checked the agents are present, and the password etc is OK, I retyped them. It's the same one I push agents with so I know it well :)

I have 13 rep shares, and 4 of them have started, done 20mb, and stopped - suspiciously similar numbers. The others have trickled all 1gb of my install kits to site real slow and sweet, but these are just sat there.

I've checked

• username & password
  
• disk space on the site server
  
• permissions on the target folder
  
• schedule (I just used the standard one supplied and set 10000 for high, 5000 for low for all my repls)
  

They can see the repls OK because they catalogue them but the data isn't being transferred.

Screen shot attached.

Any help much appreciated

At this point you can force the repliation form the Action button, and wait for few min to get the updated view. While truubleshooting i suggest us (0) in both Hi and Lo area. It is my past experiance that if there is any special Char in Password then replication will fail but since it is making catelog then it should not be the problem of password.

I tried this - or something like - I set 12-2 as Low - and saw it start, and the numbers changed and went down to 0, but next morning they're back as before and the rep shares at the far end are empty. It's set up right but failing somewhere and I can't find any error messages to tell me why

First place i'd check is the K1000 log on the server, just search for replication and you'll see some of the traffic there.

On a replication machine turn on debugging, then force replication. Check the kbot.log or amp.log depending on your version and look for replication there as well, you should see the calls going back and forth.

Next i'd check the event viewer on the replication machine to see the security logs to see if there are any errors occurring for authentication.

Last place i'd check is the system performance log to see if anything is jumping on eth0 to see if files are actually moving accross.

Thanks for this - it looks very useful; however I'm still waiting for my Jumpstart thing so some of it's a bit beyond me.

There's nothing in the security elogs

There's no kbot.log or amp.log on the replication target server. How do I turn on debugging please?

I know the agent is working OK because it ran my script I use to set up the share I use to deploy the KACE agent

The K1000 log on the server.. I can't find a Search option. There's some stuff like this; it looks like it's inventorying the shares
[2011-08-03 01:23:23 +0100] KBOX [info] Received share inventory upload from kuid: 59B290D5-5331-4EAB-AB95-DA3122F171E9
is the KUID for one of my won't-go repl servers and that looks normal (?) though I don't know what I'm looking for. I'd say it shows traffic can move to/from the server?




[2011-08-03 00:57:01 +0100] [amp_remove_expired] Starting...
[2011-08-03 00:57:01 +0100] [amp_remove_expired] No expired AMP messages to process at this time.
[2011-08-03 00:57:01 +0100] [amp_remove_expired] Done.
[2011-08-03 01:21:28 +0100] KBOX [info] [err] loadMachineDetail(153, MACHINE_NICS): no data reported from client.
[2011-08-03 01:21:28 +0100] KBOX [info] [err] loadMachineDetail(153, MACHINE_DISKS): no data reported from client.
[2011-08-03 01:23:22 +0100] KBOX [info] Received share inventory upload from kuid: 6B1368A0-B38D-4336-B181-F16A916BA6C5
[2011-08-03 01:23:22 +0100] KBOX [info] Share Inventory Parsing complete for 6B1368A0-B38D-4336-B181-F16A916BA6C5. Parsed 26 inventory records.
[2011-08-03 01:23:23 +0100] KBOX [info] Received share inventory upload from kuid: 59B290D5-5331-4EAB-AB95-DA3122F171E9
[2011-08-03 01:23:23 +0100] KBOX [info] Received share inventory upload from kuid: 0690686F-9BFC-4CD5-9ED0-20CD4475B892
[2011-08-03 01:23:23 +0100] KBOX [info] Share Inventory Parsing complete for 59B290D5-5331-4EAB-AB95-DA3122F171E9. Parsed 0 inventory records.
[2011-08-03 01:23:23 +0100] KBOX [info] Share Inventory Parsing complete for 0690686F-9BFC-4CD5-9ED0-20CD4475B892. Parsed 0 inventory records.
[2011-08-03 01:23:23 +0100] KBOX [info] Received share inventory upload from kuid: 5D4F6891-1417-4300-8014-10B49A978D3D
[2011-08-03 01:23:23 +0100] KBOX [info] Share Inventory Parsing complete for 5D4F6891-1417-4300-8014-10B49A978D3D. Parsed 0 inventory records.
[2011-08-03 01:36:32 +0100] KBOX [info] Received share inventory upload from kuid: 36527939-CA41-4E2A-9C81-BCF494C63A84
[2011-08-03 01:36:32 +0100] KBOX [info] Share Inventory Parsing complete for 36527939-CA41-4E2A-9C81-BCF494C63A84. Parsed 0 inventory records.
[2011-08-03 01:46:09 +0100] KBOX [info] Received share inventory upload from kuid: DF62B1B8-7AF8-4079-8A7F-424F879E8B50
[2011-08-03 01:46:09 +0100] KBOX [info] Share Inventory Parsing complete for DF62B1B8-7AF8-4079-8A7F-424F879E8B50. Parsed 26 inventory records.
[2011-08-03 01:46:29 +0100] KBOX [info] [err] loadMachineDetail(571, MACHINE_NICS): no data reported from client.
[2011-08-03 01:51:43 +0100] KBOX [info] Received share inventory upload from kuid: 2322971B-12B4-42D4-9097-A70FBFE0969E
[2011-08-03 01:51:43 +0100] KBOX [info] Share Inventory Parsing complete for 2322971B-12B4-42D4-9097-A70FBFE0969E. Parsed 26 inventory records.

you can search the KUID to determine the actual machine communicating, do this from the inventory screen and it'll show up. On the replication page do the shares show how much is waiting to be transferred?

Most of the time, yes. Every so often, it a bit odd, the 'to do' list disappears and the count goes to zero. Next time it checks in, it's all back waiting to be sent [:(]

easiest on debug is using the existing script provided by kace called "K1000 Agent Debug Log Enable (Windows)" this will place the Debug=True setting in the config file.

After a very long support path with KACE support we got to the bottom of this.

Despite anything one puts in the fields on the replication share config, the target folder and share needs write access given to the LOCAL SYSTEM account, which is what the agent uses to write stuff into it. The credentials one uses in the Destination Path field is only used to establish that the share exists at all.

Logical once you know but it took even KACE support some weeks to locate this information.

Some of my servers did, and some inherited from other sources didn't. Once I'd made that change, they all started off like gangbusters and I now have complete replication. Hip hip!