Scripts not pulling dependency files from local replication server
Hello,
I am still fairly new to the Kace world so I apologize if this is a simple fix (although I did google and read the Admin Guide to no avail).
We have 42 replication servers already setup simliar to the one shown here:
replication.jpg
I have setup the following Online Kscript to install RealVNC Ent. 4.6.3.
script.jpg
Each time I push the script to a location, the file is pulled from the Kace system here at our central office instead of their local replication server.
I have logged into a few of our replication servers and verified the VNC install file is there, but I am unsure if I am using incorrect Kace syntax within the script and causing my own issue.
Thanks for any help with this issue.
I am still fairly new to the Kace world so I apologize if this is a simple fix (although I did google and read the Admin Guide to no avail).
We have 42 replication servers already setup simliar to the one shown here:
replication.jpg
I have setup the following Online Kscript to install RealVNC Ent. 4.6.3.
script.jpg
Each time I push the script to a location, the file is pulled from the Kace system here at our central office instead of their local replication server.
I have logged into a few of our replication servers and verified the VNC install file is there, but I am unsure if I am using incorrect Kace syntax within the script and causing my own issue.
Thanks for any help with this issue.
0 Comments
[ + ] Show comments
Answers (5)
Please log in to answer
Posted by:
cmccracken
12 years ago
Do your test workstations show they are part of the C14 WORKSTATIONS label? Can the test stations access the listed share? Is the user you are accessing the share with a local user or domain user? (Mine are local to the NAS box of my replication agent, so I have to put safiler02\kace).
They are pulling from the central office because you have "Failover to K1000" checked, but we need to figure out why they are failing.
Casey
They are pulling from the central office because you have "Failover to K1000" checked, but we need to figure out why they are failing.
Casey
Posted by:
hambino
12 years ago
cmccracken,
Thanks for the reply. Yes, each of the workstations shows that they are attached to the C14 WORKSTATIONS label. I just logged on to one of the test machines with one of our most restricted (domain) users, and they still have access to the share. Under the replication share, for the "Download Path User/PW" and "Destination Path User/PW", we are using one of our domain login accounts domain\account and the corresponding password.
If I were to uncheck the "Failover to K1000" option, which log would show indications of errors?
Thanks for the reply. Yes, each of the workstations shows that they are attached to the C14 WORKSTATIONS label. I just logged on to one of the test machines with one of our most restricted (domain) users, and they still have access to the share. Under the replication share, for the "Download Path User/PW" and "Destination Path User/PW", we are using one of our domain login accounts domain\account and the corresponding password.
If I were to uncheck the "Failover to K1000" option, which log would show indications of errors?
Posted by:
rmeyer
12 years ago
Yes, I would check if it have more than one label aswell
Then check that the user/pass works for the UNC path via a "net use * \\server\path /user:domain\user Password" <-- it could be that it's missing "domain" in the username for correct login details (not easy to see behind the big red paint :) )
if it still don't work I'd try to enable debugging and watch the logs ( http://www.kace.com/support/kb/index.php?action=artikel&cat=2&id=519&artlang=en )
Then check that the user/pass works for the UNC path via a "net use * \\server\path /user:domain\user Password" <-- it could be that it's missing "domain" in the username for correct login details (not easy to see behind the big red paint :) )
if it still don't work I'd try to enable debugging and watch the logs ( http://www.kace.com/support/kb/index.php?action=artikel&cat=2&id=519&artlang=en )
Posted by:
cblake
12 years ago
Please verify that Machines are not part of more than one replication label. If they are then they will fail back to K1.
If that's verified, I'd try creating a zip with the dependancies at hand, creating a batch file to do the work of the script; then uploading the zip for use as a managed install; the MI uses you batch file as its command line. Might help narrow down if it's a bug or a configuration issue.
If that's verified, I'd try creating a zip with the dependancies at hand, creating a batch file to do the work of the script; then uploading the zip for use as a managed install; the MI uses you batch file as its command line. Might help narrow down if it's a bug or a configuration issue.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.