Agent Install 5.3
Hi Guys,
If I push this out via GPO will i need to somehow get .net 1.1 on the machine as well? or is .net 1.1 just for agent 5.1?
Currently we have 5.1 in our enviroment and I am looking at ways to push the agent out as network push isnt working due to firewall issues.
Thanks
If I push this out via GPO will i need to somehow get .net 1.1 on the machine as well? or is .net 1.1 just for agent 5.1?
Currently we have 5.1 in our enviroment and I am looking at ways to push the agent out as network push isnt working due to firewall issues.
Thanks
0 Comments
[ + ] Show comments
Answers (7)
Please log in to answer
Posted by:
GillySpy
13 years ago
5.3 L10N is the latest version. Also called 5.3.47657 http://www.kace.com/support/customer/downloads.php
The next release will be 5.3 L10N AP1 -- due in a coupe of weeks.
It goes without saying that you should test software, including the agent, before deploying to every computer. Have you upgraded your server to 5.3 yet?
The next release will be 5.3 L10N AP1 -- due in a coupe of weeks.
It goes without saying that you should test software, including the agent, before deploying to every computer. Have you upgraded your server to 5.3 yet?
Posted by:
mac456
13 years ago
hey, thanks for the reply. I have only just taken on this project and the server was put in before me so as the agent is 5.1 I assume the server is too? is it a fairly straight forward process to upgrade to 5.3? is it all done from the dash? I haven't got access to the server ATM. thanks.
Posted by:
GillySpy
13 years ago
If you go to http://kace.com/support and click on downloads-> 5.3 files you will be taken to the upgrade instructions which include the links to downloa
Posted by:
Mariusja
13 years ago
Hi there,
I need some advice on a icon deployment.
Our setup is as follow:
We have 1300 replicates. Each replicate has got its own IP.
I need to deploy an icon to each desktop (13 000). The problem is that each branch icon is different because the icon must point to the replication share (local server) .We will need a script that will query the servers name or IP and the name or ip must be added to the icon.
In other words if the user double click the icon it must go to a directory to the local server c:\desktop\trainning documents. As mentioned it must point to its local server and not to another server because the data will be retrieved over the WAN and not the local LAN.
Hope this make sense??
I need some advice on a icon deployment.
Our setup is as follow:
We have 1300 replicates. Each replicate has got its own IP.
I need to deploy an icon to each desktop (13 000). The problem is that each branch icon is different because the icon must point to the replication share (local server) .We will need a script that will query the servers name or IP and the name or ip must be added to the icon.
In other words if the user double click the icon it must go to a directory to the local server c:\desktop\trainning documents. As mentioned it must point to its local server and not to another server because the data will be retrieved over the WAN and not the local LAN.
Hope this make sense??
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.