do we need to uninstal the exisiting AIS client or simply run the V2 client?
Arnie
Technology Tips and News
do we need to uninstal the exisiting AIS client or simply run the V2 client?
Arnie
You do not need to uninstall the AIS 1.5 client. The AIS 2.0 client will install along-side the AIS 1.5 client on the same machine. In fact both clients run and report inventory to their respective services.
This approach lets customers (large customers particularly) stage the deployment of the AIS 2.0 client over a period of time. During this roll out, they can still use AIS 1.5 since all the AIS 1.5 agents are still reporting inventory.
The recommended guidance is to deploy the AIS 2.0 agent. Once fully deployed, switch over to use AIS 2.0, and retire the AIS 1.5 agents from the AIS 1.5 console. This will cause the AIS 1.5 agents to stop reporting inventory, but the agent itself is still present on machines. At some later point, the AIS 1.5 agent can be uninstalled from machines as part of routine maintenance.
You do not need to uninstall the AIS 1.5 client. The AIS 2.0 client will install along-side the AIS 1.5 client on the same machine. In fact both clients run and report inventory to their respective services.
This approach lets customers (large customers particularly) stage the deployment of the AIS 2.0 client over a period of time. During this roll out, they can still use AIS 1.5 since all the AIS 1.5 agents are still reporting inventory.
The recommended guidance is to deploy the AIS 2.0 agent. Once fully deployed, switch over to use AIS 2.0, and retire the AIS 1.5 agents from the AIS 1.5 console. This will cause the AIS 1.5 agents to stop reporting inventory, but the agent itself is still present on machines. At some later point, the AIS 1.5 agent can be uninstalled from machines as part of routine maintenance.
You do not need to uninstall the AIS 1.5 client. The AIS 2.0 client will install along-side the AIS 1.5 client on the same machine. In fact both clients run and report inventory to their respective services.
This approach lets customers (large customers particularly) stage the deployment of the AIS 2.0 client over a period of time. During this roll out, they can still use AIS 1.5 since all the AIS 1.5 agents are still reporting inventory.
The recommended guidance is to deploy the AIS 2.0 agent. Once fully deployed, switch over to use AIS 2.0, and retire the AIS 1.5 agents from the AIS 1.5 console. This will cause the AIS 1.5 agents to stop reporting inventory, but the agent itself is still present on machines. At some later point, the AIS 1.5 agent can be uninstalled from machines as part of routine maintenance.
You do not need to uninstall the AIS 1.5 client. The AIS 2.0 client will install along-side the AIS 1.5 client on the same machine. In fact both clients run and report inventory to their respective services.
This approach lets customers (large customers particularly) stage the deployment of the AIS 2.0 client over a period of time. During this roll out, they can still use AIS 1.5 since all the AIS 1.5 agents are still reporting inventory.
The recommended guidance is to deploy the AIS 2.0 agent. Once fully deployed, switch over to use AIS 2.0, and retire the AIS 1.5 agents from the AIS 1.5 console. This will cause the AIS 1.5 agents to stop reporting inventory, but the agent itself is still present on machines. At some later point, the AIS 1.5 agent can be uninstalled from machines as part of routine maintenance.
You do not need to uninstall the AIS 1.5 client. The AIS 2.0 client will install along-side the AIS 1.5 client on the same machine. In fact both clients run and report inventory to their respective services.
This approach lets customers (large customers particularly) stage the deployment of the AIS 2.0 client over a period of time. During this roll out, they can still use AIS 1.5 since all the AIS 1.5 agents are still reporting inventory.
The recommended guidance is to deploy the AIS 2.0 agent. Once fully deployed, switch over to use AIS 2.0, and retire the AIS 1.5 agents from the AIS 1.5 console. This will cause the AIS 1.5 agents to stop reporting inventory, but the agent itself is still present on machines. At some later point, the AIS 1.5 agent can be uninstalled from machines as part of routine maintenance.
You do not need to uninstall the AIS 1.5 client. The AIS 2.0 client will install along-side the AIS 1.5 client on the same machine. In fact both clients run and report inventory to their respective services.
This approach lets customers (large customers particularly) stage the deployment of the AIS 2.0 client over a period of time. During this roll out, they can still use AIS 1.5 since all the AIS 1.5 agents are still reporting inventory.
The recommended guidance is to deploy the AIS 2.0 agent. Once fully deployed, switch over to use AIS 2.0, and retire the AIS 1.5 agents from the AIS 1.5 console. This will cause the AIS 1.5 agents to stop reporting inventory, but the agent itself is still present on machines. At some later point, the AIS 1.5 agent can be uninstalled from machines as part of routine maintenance.
You do not need to uninstall the AIS 1.5 client. The AIS 2.0 client will install along-side the AIS 1.5 client on the same machine. In fact both clients run and report inventory to their respective services.
This approach lets customers (large customers particularly) stage the deployment of the AIS 2.0 client over a period of time. During this roll out, they can still use AIS 1.5 since all the AIS 1.5 agents are still reporting inventory.
The recommended guidance is to deploy the AIS 2.0 agent. Once fully deployed, switch over to use AIS 2.0, and retire the AIS 1.5 agents from the AIS 1.5 console. This will cause the AIS 1.5 agents to stop reporting inventory, but the agent itself is still present on machines. At some later point, the AIS 1.5 agent can be uninstalled from machines as part of routine maintenance.
You do not need to uninstall the AIS 1.5 client. The AIS 2.0 client will install along-side the AIS 1.5 client on the same machine. In fact both clients run and report inventory to their respective services.
This approach lets customers (large customers particularly) stage the deployment of the AIS 2.0 client over a period of time. During this roll out, they can still use AIS 1.5 since all the AIS 1.5 agents are still reporting inventory.
The recommended guidance is to deploy the AIS 2.0 agent. Once fully deployed, switch over to use AIS 2.0, and retire the AIS 1.5 agents from the AIS 1.5 console. This will cause the AIS 1.5 agents to stop reporting inventory, but the agent itself is still present on machines. At some later point, the AIS 1.5 agent can be uninstalled from machines as part of routine maintenance.
You do not need to uninstall the AIS 1.5 client. The AIS 2.0 client will install along-side the AIS 1.5 client on the same machine. In fact both clients run and report inventory to their respective services.
This approach lets customers (large customers particularly) stage the deployment of the AIS 2.0 client over a period of time. During this roll out, they can still use AIS 1.5 since all the AIS 1.5 agents are still reporting inventory.
The recommended guidance is to deploy the AIS 2.0 agent. Once fully deployed, switch over to use AIS 2.0, and retire the AIS 1.5 agents from the AIS 1.5 console. This will cause the AIS 1.5 agents to stop reporting inventory, but the agent itself is still present on machines. At some later point, the AIS 1.5 agent can be uninstalled from machines as part of routine maintenance.
You do not need to uninstall the AIS 1.5 client. The AIS 2.0 client will install along-side the AIS 1.5 client on the same machine. In fact both clients run and report inventory to their respective services.
This approach lets customers (large customers particularly) stage the deployment of the AIS 2.0 client over a period of time. During this roll out, they can still use AIS 1.5 since all the AIS 1.5 agents are still reporting inventory.
The recommended guidance is to deploy the AIS 2.0 agent. Once fully deployed, switch over to use AIS 2.0, and retire the AIS 1.5 agents from the AIS 1.5 console. This will cause the AIS 1.5 agents to stop reporting inventory, but the agent itself is still present on machines. At some later point, the AIS 1.5 agent can be uninstalled from machines as part of routine maintenance.
You do not need to uninstall the AIS 1.5 client. The AIS 2.0 client will install along-side the AIS 1.5 client on the same machine. In fact both clients run and report inventory to their respective services.
This approach lets customers (large customers particularly) stage the deployment of the AIS 2.0 client over a period of time. During this roll out, they can still use AIS 1.5 since all the AIS 1.5 agents are still reporting inventory.
The recommended guidance is to deploy the AIS 2.0 agent. Once fully deployed, switch over to use AIS 2.0, and retire the AIS 1.5 agents from the AIS 1.5 console. This will cause the AIS 1.5 agents to stop reporting inventory, but the agent itself is still present on machines. At some later point, the AIS 1.5 agent can be uninstalled from machines as part of routine maintenance.
You do not need to uninstall the AIS 1.5 client. The AIS 2.0 client will install along-side the AIS 1.5 client on the same machine. In fact both clients run and report inventory to their respective services.
This approach lets customers (large customers particularly) stage the deployment of the AIS 2.0 client over a period of time. During this roll out, they can still use AIS 1.5 since all the AIS 1.5 agents are still reporting inventory.
The recommended guidance is to deploy the AIS 2.0 agent. Once fully deployed, switch over to use AIS 2.0, and retire the AIS 1.5 agents from the AIS 1.5 console. This will cause the AIS 1.5 agents to stop reporting inventory, but the agent itself is still present on machines. At some later point, the AIS 1.5 agent can be uninstalled from machines as part of routine maintenance.
You do not need to uninstall the AIS 1.5 client. The AIS 2.0 client will install along-side the AIS 1.5 client on the same machine. In fact both clients run and report inventory to their respective services.
This approach lets customers (large customers particularly) stage the deployment of the AIS 2.0 client over a period of time. During this roll out, they can still use AIS 1.5 since all the AIS 1.5 agents are still reporting inventory.
The recommended guidance is to deploy the AIS 2.0 agent. Once fully deployed, switch over to use AIS 2.0, and retire the AIS 1.5 agents from the AIS 1.5 console. This will cause the AIS 1.5 agents to stop reporting inventory, but the agent itself is still present on machines. At some later point, the AIS 1.5 agent can be uninstalled from machines as part of routine maintenance.
You do not need to uninstall the AIS 1.5 client. The AIS 2.0 client will install along-side the AIS 1.5 client on the same machine. In fact both clients run and report inventory to their respective services.
This approach lets customers (large customers particularly) stage the deployment of the AIS 2.0 client over a period of time. During this roll out, they can still use AIS 1.5 since all the AIS 1.5 agents are still reporting inventory.
The recommended guidance is to deploy the AIS 2.0 agent. Once fully deployed, switch over to use AIS 2.0, and retire the AIS 1.5 agents from the AIS 1.5 console. This will cause the AIS 1.5 agents to stop reporting inventory, but the agent itself is still present on machines. At some later point, the AIS 1.5 agent can be uninstalled from machines as part of routine maintenance.
You do not need to uninstall the AIS 1.5 client. The AIS 2.0 client will install along-side the AIS 1.5 client on the same machine. In fact both clients run and report inventory to their respective services.
This approach lets customers (large customers particularly) stage the deployment of the AIS 2.0 client over a period of time. During this roll out, they can still use AIS 1.5 since all the AIS 1.5 agents are still reporting inventory.
The recommended guidance is to deploy the AIS 2.0 agent. Once fully deployed, switch over to use AIS 2.0, and retire the AIS 1.5 agents from the AIS 1.5 console. This will cause the AIS 1.5 agents to stop reporting inventory, but the agent itself is still present on machines. At some later point, the AIS 1.5 agent can be uninstalled from machines as part of routine maintenance.
You do not need to uninstall the AIS 1.5 client. The AIS 2.0 client will install along-side the AIS 1.5 client on the same machine. In fact both clients run and report inventory to their respective services.
This approach lets customers (large customers particularly) stage the deployment of the AIS 2.0 client over a period of time. During this roll out, they can still use AIS 1.5 since all the AIS 1.5 agents are still reporting inventory.
The recommended guidance is to deploy the AIS 2.0 agent. Once fully deployed, switch over to use AIS 2.0, and retire the AIS 1.5 agents from the AIS 1.5 console. This will cause the AIS 1.5 agents to stop reporting inventory, but the agent itself is still present on machines. At some later point, the AIS 1.5 agent can be uninstalled from machines as part of routine maintenance.
You do not need to uninstall the AIS 1.5 client. The AIS 2.0 client will install along-side the AIS 1.5 client on the same machine. In fact both clients run and report inventory to their respective services.
This approach lets customers (large customers particularly) stage the deployment of the AIS 2.0 client over a period of time. During this roll out, they can still use AIS 1.5 since all the AIS 1.5 agents are still reporting inventory.
The recommended guidance is to deploy the AIS 2.0 agent. Once fully deployed, switch over to use AIS 2.0, and retire the AIS 1.5 agents from the AIS 1.5 console. This will cause the AIS 1.5 agents to stop reporting inventory, but the agent itself is still present on machines. At some later point, the AIS 1.5 agent can be uninstalled from machines as part of routine maintenance.
You do not need to uninstall the AIS 1.5 client. The AIS 2.0 client will install along-side the AIS 1.5 client on the same machine. In fact both clients run and report inventory to their respective services.
This approach lets customers (large customers particularly) stage the deployment of the AIS 2.0 client over a period of time. During this roll out, they can still use AIS 1.5 since all the AIS 1.5 agents are still reporting inventory.
The recommended guidance is to deploy the AIS 2.0 agent. Once fully deployed, switch over to use AIS 2.0, and retire the AIS 1.5 agents from the AIS 1.5 console. This will cause the AIS 1.5 agents to stop reporting inventory, but the agent itself is still present on machines. At some later point, the AIS 1.5 agent can be uninstalled from machines as part of routine maintenance.
You do not need to uninstall the AIS 1.5 client. The AIS 2.0 client will install along-side the AIS 1.5 client on the same machine. In fact both clients run and report inventory to their respective services.
This approach lets customers (large customers particularly) stage the deployment of the AIS 2.0 client over a period of time. During this roll out, they can still use AIS 1.5 since all the AIS 1.5 agents are still reporting inventory.
The recommended guidance is to deploy the AIS 2.0 agent. Once fully deployed, switch over to use AIS 2.0, and retire the AIS 1.5 agents from the AIS 1.5 console. This will cause the AIS 1.5 agents to stop reporting inventory, but the agent itself is still present on machines. At some later point, the AIS 1.5 agent can be uninstalled from machines as part of routine maintenance.
You do not need to uninstall the AIS 1.5 client. The AIS 2.0 client will install along-side the AIS 1.5 client on the same machine. In fact both clients run and report inventory to their respective services.
This approach lets customers (large customers particularly) stage the deployment of the AIS 2.0 client over a period of time. During this roll out, they can still use AIS 1.5 since all the AIS 1.5 agents are still reporting inventory.
The recommended guidance is to deploy the AIS 2.0 agent. Once fully deployed, switch over to use AIS 2.0, and retire the AIS 1.5 agents from the AIS 1.5 console. This will cause the AIS 1.5 agents to stop reporting inventory, but the agent itself is still present on machines. At some later point, the AIS 1.5 agent can be uninstalled from machines as part of routine maintenance.
You do not need to uninstall the AIS 1.5 client. The AIS 2.0 client will install along-side the AIS 1.5 client on the same machine. In fact both clients run and report inventory to their respective services.
This approach lets customers (large customers particularly) stage the deployment of the AIS 2.0 client over a period of time. During this roll out, they can still use AIS 1.5 since all the AIS 1.5 agents are still reporting inventory.
The recommended guidance is to deploy the AIS 2.0 agent. Once fully deployed, switch over to use AIS 2.0, and retire the AIS 1.5 agents from the AIS 1.5 console. This will cause the AIS 1.5 agents to stop reporting inventory, but the agent itself is still present on machines. At some later point, the AIS 1.5 agent can be uninstalled from machines as part of routine maintenance.
You do not need to uninstall the AIS 1.5 client. The AIS 2.0 client will install along-side the AIS 1.5 client on the same machine. In fact both clients run and report inventory to their respective services.
This approach lets customers (large customers particularly) stage the deployment of the AIS 2.0 client over a period of time. During this roll out, they can still use AIS 1.5 since all the AIS 1.5 agents are still reporting inventory.
The recommended guidance is to deploy the AIS 2.0 agent. Once fully deployed, switch over to use AIS 2.0, and retire the AIS 1.5 agents from the AIS 1.5 console. This will cause the AIS 1.5 agents to stop reporting inventory, but the agent itself is still present on machines. At some later point, the AIS 1.5 agent can be uninstalled from machines as part of routine maintenance.
You do not need to uninstall the AIS 1.5 client. The AIS 2.0 client will install along-side the AIS 1.5 client on the same machine. In fact both clients run and report inventory to their respective services.
This approach lets customers (large customers particularly) stage the deployment of the AIS 2.0 client over a period of time. During this roll out, they can still use AIS 1.5 since all the AIS 1.5 agents are still reporting inventory.
The recommended guidance is to deploy the AIS 2.0 agent. Once fully deployed, switch over to use AIS 2.0, and retire the AIS 1.5 agents from the AIS 1.5 console. This will cause the AIS 1.5 agents to stop reporting inventory, but the agent itself is still present on machines. At some later point, the AIS 1.5 agent can be uninstalled from machines as part of routine maintenance.
You do not need to uninstall the AIS 1.5 client. The AIS 2.0 client will install along-side the AIS 1.5 client on the same machine. In fact both clients run and report inventory to their respective services.
This approach lets customers (large customers particularly) stage the deployment of the AIS 2.0 client over a period of time. During this roll out, they can still use AIS 1.5 since all the AIS 1.5 agents are still reporting inventory.
The recommended guidance is to deploy the AIS 2.0 agent. Once fully deployed, switch over to use AIS 2.0, and retire the AIS 1.5 agents from the AIS 1.5 console. This will cause the AIS 1.5 agents to stop reporting inventory, but the agent itself is still present on machines. At some later point, the AIS 1.5 agent can be uninstalled from machines as part of routine maintenance.
You do not need to uninstall the AIS 1.5 client. The AIS 2.0 client will install along-side the AIS 1.5 client on the same machine. In fact both clients run and report inventory to their respective services.
This approach lets customers (large customers particularly) stage the deployment of the AIS 2.0 client over a period of time. During this roll out, they can still use AIS 1.5 since all the AIS 1.5 agents are still reporting inventory.
The recommended guidance is to deploy the AIS 2.0 agent. Once fully deployed, switch over to use AIS 2.0, and retire the AIS 1.5 agents from the AIS 1.5 console. This will cause the AIS 1.5 agents to stop reporting inventory, but the agent itself is still present on machines. At some later point, the AIS 1.5 agent can be uninstalled from machines as part of routine maintenance.
You do not need to uninstall the AIS 1.5 client. The AIS 2.0 client will install along-side the AIS 1.5 client on the same machine. In fact both clients run and report inventory to their respective services.
This approach lets customers (large customers particularly) stage the deployment of the AIS 2.0 client over a period of time. During this roll out, they can still use AIS 1.5 since all the AIS 1.5 agents are still reporting inventory.
The recommended guidance is to deploy the AIS 2.0 agent. Once fully deployed, switch over to use AIS 2.0, and retire the AIS 1.5 agents from the AIS 1.5 console. This will cause the AIS 1.5 agents to stop reporting inventory, but the agent itself is still present on machines. At some later point, the AIS 1.5 agent can be uninstalled from machines as part of routine maintenance.
You do not need to uninstall the AIS 1.5 client. The AIS 2.0 client will install along-side the AIS 1.5 client on the same machine. In fact both clients run and report inventory to their respective services.
This approach lets customers (large customers particularly) stage the deployment of the AIS 2.0 client over a period of time. During this roll out, they can still use AIS 1.5 since all the AIS 1.5 agents are still reporting inventory.
The recommended guidance is to deploy the AIS 2.0 agent. Once fully deployed, switch over to use AIS 2.0, and retire the AIS 1.5 agents from the AIS 1.5 console. This will cause the AIS 1.5 agents to stop reporting inventory, but the agent itself is still present on machines. At some later point, the AIS 1.5 agent can be uninstalled from machines as part of routine maintenance.
You do not need to uninstall the AIS 1.5 client. The AIS 2.0 client will install along-side the AIS 1.5 client on the same machine. In fact both clients run and report inventory to their respective services.
This approach lets customers (large customers particularly) stage the deployment of the AIS 2.0 client over a period of time. During this roll out, they can still use AIS 1.5 since all the AIS 1.5 agents are still reporting inventory.
The recommended guidance is to deploy the AIS 2.0 agent. Once fully deployed, switch over to use AIS 2.0, and retire the AIS 1.5 agents from the AIS 1.5 console. This will cause the AIS 1.5 agents to stop reporting inventory, but the agent itself is still present on machines. At some later point, the AIS 1.5 agent can be uninstalled from machines as part of routine maintenance.
You do not need to uninstall the AIS 1.5 client. The AIS 2.0 client will install along-side the AIS 1.5 client on the same machine. In fact both clients run and report inventory to their respective services.
This approach lets customers (large customers particularly) stage the deployment of the AIS 2.0 client over a period of time. During this roll out, they can still use AIS 1.5 since all the AIS 1.5 agents are still reporting inventory.
The recommended guidance is to deploy the AIS 2.0 agent. Once fully deployed, switch over to use AIS 2.0, and retire the AIS 1.5 agents from the AIS 1.5 console. This will cause the AIS 1.5 agents to stop reporting inventory, but the agent itself is still present on machines. At some later point, the AIS 1.5 agent can be uninstalled from machines as part of routine maintenance.
You do not need to uninstall the AIS 1.5 client. The AIS 2.0 client will install along-side the AIS 1.5 client on the same machine. In fact both clients run and report inventory to their respective services.
This approach lets customers (large customers particularly) stage the deployment of the AIS 2.0 client over a period of time. During this roll out, they can still use AIS 1.5 since all the AIS 1.5 agents are still reporting inventory.
The recommended guidance is to deploy the AIS 2.0 agent. Once fully deployed, switch over to use AIS 2.0, and retire the AIS 1.5 agents from the AIS 1.5 console. This will cause the AIS 1.5 agents to stop reporting inventory, but the agent itself is still present on machines. At some later point, the AIS 1.5 agent can be uninstalled from machines as part of routine maintenance.
You do not need to uninstall the AIS 1.5 client. The AIS 2.0 client will install along-side the AIS 1.5 client on the same machine. In fact both clients run and report inventory to their respective services.
This approach lets customers (large customers particularly) stage the deployment of the AIS 2.0 client over a period of time. During this roll out, they can still use AIS 1.5 since all the AIS 1.5 agents are still reporting inventory.
The recommended guidance is to deploy the AIS 2.0 agent. Once fully deployed, switch over to use AIS 2.0, and retire the AIS 1.5 agents from the AIS 1.5 console. This will cause the AIS 1.5 agents to stop reporting inventory, but the agent itself is still present on machines. At some later point, the AIS 1.5 agent can be uninstalled from machines as part of routine maintenance.
You do not need to uninstall the AIS 1.5 client. The AIS 2.0 client will install along-side the AIS 1.5 client on the same machine. In fact both clients run and report inventory to their respective services.
This approach lets customers (large customers particularly) stage the deployment of the AIS 2.0 client over a period of time. During this roll out, they can still use AIS 1.5 since all the AIS 1.5 agents are still reporting inventory.
The recommended guidance is to deploy the AIS 2.0 agent. Once fully deployed, switch over to use AIS 2.0, and retire the AIS 1.5 agents from the AIS 1.5 console. This will cause the AIS 1.5 agents to stop reporting inventory, but the agent itself is still present on machines. At some later point, the AIS 1.5 agent can be uninstalled from machines as part of routine maintenance.
You do not need to uninstall the AIS 1.5 client. The AIS 2.0 client will install along-side the AIS 1.5 client on the same machine. In fact both clients run and report inventory to their respective services.
This approach lets customers (large customers particularly) stage the deployment of the AIS 2.0 client over a period of time. During this roll out, they can still use AIS 1.5 since all the AIS 1.5 agents are still reporting inventory.
The recommended guidance is to deploy the AIS 2.0 agent. Once fully deployed, switch over to use AIS 2.0, and retire the AIS 1.5 agents from the AIS 1.5 console. This will cause the AIS 1.5 agents to stop reporting inventory, but the agent itself is still present on machines. At some later point, the AIS 1.5 agent can be uninstalled from machines as part of routine maintenance.
You do not need to uninstall the AIS 1.5 client. The AIS 2.0 client will install along-side the AIS 1.5 client on the same machine. In fact both clients run and report inventory to their respective services.
This approach lets customers (large customers particularly) stage the deployment of the AIS 2.0 client over a period of time. During this roll out, they can still use AIS 1.5 since all the AIS 1.5 agents are still reporting inventory.
The recommended guidance is to deploy the AIS 2.0 agent. Once fully deployed, switch over to use AIS 2.0, and retire the AIS 1.5 agents from the AIS 1.5 console. This will cause the AIS 1.5 agents to stop reporting inventory, but the agent itself is still present on machines. At some later point, the AIS 1.5 agent can be uninstalled from machines as part of routine maintenance.
You do not need to uninstall the AIS 1.5 client. The AIS 2.0 client will install along-side the AIS 1.5 client on the same machine. In fact both clients run and report inventory to their respective services.
This approach lets customers (large customers particularly) stage the deployment of the AIS 2.0 client over a period of time. During this roll out, they can still use AIS 1.5 since all the AIS 1.5 agents are still reporting inventory.
The recommended guidance is to deploy the AIS 2.0 agent. Once fully deployed, switch over to use AIS 2.0, and retire the AIS 1.5 agents from the AIS 1.5 console. This will cause the AIS 1.5 agents to stop reporting inventory, but the agent itself is still present on machines. At some later point, the AIS 1.5 agent can be uninstalled from machines as part of routine maintenance.
You do not need to uninstall the AIS 1.5 client. The AIS 2.0 client will install along-side the AIS 1.5 client on the same machine. In fact both clients run and report inventory to their respective services.
This approach lets customers (large customers particularly) stage the deployment of the AIS 2.0 client over a period of time. During this roll out, they can still use AIS 1.5 since all the AIS 1.5 agents are still reporting inventory.
The recommended guidance is to deploy the AIS 2.0 agent. Once fully deployed, switch over to use AIS 2.0, and retire the AIS 1.5 agents from the AIS 1.5 console. This will cause the AIS 1.5 agents to stop reporting inventory, but the agent itself is still present on machines. At some later point, the AIS 1.5 agent can be uninstalled from machines as part of routine maintenance.
You do not need to uninstall the AIS 1.5 client. The AIS 2.0 client will install along-side the AIS 1.5 client on the same machine. In fact both clients run and report inventory to their respective services.
This approach lets customers (large customers particularly) stage the deployment of the AIS 2.0 client over a period of time. During this roll out, they can still use AIS 1.5 since all the AIS 1.5 agents are still reporting inventory.
The recommended guidance is to deploy the AIS 2.0 agent. Once fully deployed, switch over to use AIS 2.0, and retire the AIS 1.5 agents from the AIS 1.5 console. This will cause the AIS 1.5 agents to stop reporting inventory, but the agent itself is still present on machines. At some later point, the AIS 1.5 agent can be uninstalled from machines as part of routine maintenance.
You do not need to uninstall the AIS 1.5 client. The AIS 2.0 client will install along-side the AIS 1.5 client on the same machine. In fact both clients run and report inventory to their respective services.
This approach lets customers (large customers particularly) stage the deployment of the AIS 2.0 client over a period of time. During this roll out, they can still use AIS 1.5 since all the AIS 1.5 agents are still reporting inventory.
The recommended guidance is to deploy the AIS 2.0 agent. Once fully deployed, switch over to use AIS 2.0, and retire the AIS 1.5 agents from the AIS 1.5 console. This will cause the AIS 1.5 agents to stop reporting inventory, but the agent itself is still present on machines. At some later point, the AIS 1.5 agent can be uninstalled from machines as part of routine maintenance.
You do not need to uninstall the AIS 1.5 client. The AIS 2.0 client will install along-side the AIS 1.5 client on the same machine. In fact both clients run and report inventory to their respective services.
This approach lets customers (large customers particularly) stage the deployment of the AIS 2.0 client over a period of time. During this roll out, they can still use AIS 1.5 since all the AIS 1.5 agents are still reporting inventory.
The recommended guidance is to deploy the AIS 2.0 agent. Once fully deployed, switch over to use AIS 2.0, and retire the AIS 1.5 agents from the AIS 1.5 console. This will cause the AIS 1.5 agents to stop reporting inventory, but the agent itself is still present on machines. At some later point, the AIS 1.5 agent can be uninstalled from machines as part of routine maintenance.
You do not need to uninstall the AIS 1.5 client. The AIS 2.0 client will install along-side the AIS 1.5 client on the same machine. In fact both clients run and report inventory to their respective services.
This approach lets customers (large customers particularly) stage the deployment of the AIS 2.0 client over a period of time. During this roll out, they can still use AIS 1.5 since all the AIS 1.5 agents are still reporting inventory.
The recommended guidance is to deploy the AIS 2.0 agent. Once fully deployed, switch over to use AIS 2.0, and retire the AIS 1.5 agents from the AIS 1.5 console. This will cause the AIS 1.5 agents to stop reporting inventory, but the agent itself is still present on machines. At some later point, the AIS 1.5 agent can be uninstalled from machines as part of routine maintenance.
You do not need to uninstall the AIS 1.5 client. The AIS 2.0 client will install along-side the AIS 1.5 client on the same machine. In fact both clients run and report inventory to their respective services.
This approach lets customers (large customers particularly) stage the deployment of the AIS 2.0 client over a period of time. During this roll out, they can still use AIS 1.5 since all the AIS 1.5 agents are still reporting inventory.
The recommended guidance is to deploy the AIS 2.0 agent. Once fully deployed, switch over to use AIS 2.0, and retire the AIS 1.5 agents from the AIS 1.5 console. This will cause the AIS 1.5 agents to stop reporting inventory, but the agent itself is still present on machines. At some later point, the AIS 1.5 agent can be uninstalled from machines as part of routine maintenance.
You do not need to uninstall the AIS 1.5 client. The AIS 2.0 client will install along-side the AIS 1.5 client on the same machine. In fact both clients run and report inventory to their respective services.
This approach lets customers (large customers particularly) stage the deployment of the AIS 2.0 client over a period of time. During this roll out, they can still use AIS 1.5 since all the AIS 1.5 agents are still reporting inventory.
The recommended guidance is to deploy the AIS 2.0 agent. Once fully deployed, switch over to use AIS 2.0, and retire the AIS 1.5 agents from the AIS 1.5 console. This will cause the AIS 1.5 agents to stop reporting inventory, but the agent itself is still present on machines. At some later point, the AIS 1.5 agent can be uninstalled from machines as part of routine maintenance.
You do not need to uninstall the AIS 1.5 client. The AIS 2.0 client will install along-side the AIS 1.5 client on the same machine. In fact both clients run and report inventory to their respective services.
This approach lets customers (large customers particularly) stage the deployment of the AIS 2.0 client over a period of time. During this roll out, they can still use AIS 1.5 since all the AIS 1.5 agents are still reporting inventory.
The recommended guidance is to deploy the AIS 2.0 agent. Once fully deployed, switch over to use AIS 2.0, and retire the AIS 1.5 agents from the AIS 1.5 console. This will cause the AIS 1.5 agents to stop reporting inventory, but the agent itself is still present on machines. At some later point, the AIS 1.5 agent can be uninstalled from machines as part of routine maintenance.
You do not need to uninstall the AIS 1.5 client. The AIS 2.0 client will install along-side the AIS 1.5 client on the same machine. In fact both clients run and report inventory to their respective services.
This approach lets customers (large customers particularly) stage the deployment of the AIS 2.0 client over a period of time. During this roll out, they can still use AIS 1.5 since all the AIS 1.5 agents are still reporting inventory.
The recommended guidance is to deploy the AIS 2.0 agent. Once fully deployed, switch over to use AIS 2.0, and retire the AIS 1.5 agents from the AIS 1.5 console. This will cause the AIS 1.5 agents to stop reporting inventory, but the agent itself is still present on machines. At some later point, the AIS 1.5 agent can be uninstalled from machines as part of routine maintenance.
You do not need to uninstall the AIS 1.5 client. The AIS 2.0 client will install along-side the AIS 1.5 client on the same machine. In fact both clients run and report inventory to their respective services.
This approach lets customers (large customers particularly) stage the deployment of the AIS 2.0 client over a period of time. During this roll out, they can still use AIS 1.5 since all the AIS 1.5 agents are still reporting inventory.
The recommended guidance is to deploy the AIS 2.0 agent. Once fully deployed, switch over to use AIS 2.0, and retire the AIS 1.5 agents from the AIS 1.5 console. This will cause the AIS 1.5 agents to stop reporting inventory, but the agent itself is still present on machines. At some later point, the AIS 1.5 agent can be uninstalled from machines as part of routine maintenance.
You do not need to uninstall the AIS 1.5 client. The AIS 2.0 client will install along-side the AIS 1.5 client on the same machine. In fact both clients run and report inventory to their respective services.
This approach lets customers (large customers particularly) stage the deployment of the AIS 2.0 client over a period of time. During this roll out, they can still use AIS 1.5 since all the AIS 1.5 agents are still reporting inventory.
The recommended guidance is to deploy the AIS 2.0 agent. Once fully deployed, switch over to use AIS 2.0, and retire the AIS 1.5 agents from the AIS 1.5 console. This will cause the AIS 1.5 agents to stop reporting inventory, but the agent itself is still present on machines. At some later point, the AIS 1.5 agent can be uninstalled from machines as part of routine maintenance.
You do not need to uninstall the AIS 1.5 client. The AIS 2.0 client will install along-side the AIS 1.5 client on the same machine. In fact both clients run and report inventory to their respective services.
This approach lets customers (large customers particularly) stage the deployment of the AIS 2.0 client over a period of time. During this roll out, they can still use AIS 1.5 since all the AIS 1.5 agents are still reporting inventory.
The recommended guidance is to deploy the AIS 2.0 agent. Once fully deployed, switch over to use AIS 2.0, and retire the AIS 1.5 agents from the AIS 1.5 console. This will cause the AIS 1.5 agents to stop reporting inventory, but the agent itself is still present on machines. At some later point, the AIS 1.5 agent can be uninstalled from machines as part of routine maintenance.
You do not need to uninstall the AIS 1.5 client. The AIS 2.0 client will install along-side the AIS 1.5 client on the same machine. In fact both clients run and report inventory to their respective services.
This approach lets customers (large customers particularly) stage the deployment of the AIS 2.0 client over a period of time. During this roll out, they can still use AIS 1.5 since all the AIS 1.5 agents are still reporting inventory.
The recommended guidance is to deploy the AIS 2.0 agent. Once fully deployed, switch over to use AIS 2.0, and retire the AIS 1.5 agents from the AIS 1.5 console. This will cause the AIS 1.5 agents to stop reporting inventory, but the agent itself is still present on machines. At some later point, the AIS 1.5 agent can be uninstalled from machines as part of routine maintenance.
You do not need to uninstall the AIS 1.5 client. The AIS 2.0 client will install along-side the AIS 1.5 client on the same machine. In fact both clients run and report inventory to their respective services.
This approach lets customers (large customers particularly) stage the deployment of the AIS 2.0 client over a period of time. During this roll out, they can still use AIS 1.5 since all the AIS 1.5 agents are still reporting inventory.
The recommended guidance is to deploy the AIS 2.0 agent. Once fully deployed, switch over to use AIS 2.0, and retire the AIS 1.5 agents from the AIS 1.5 console. This will cause the AIS 1.5 agents to stop reporting inventory, but the agent itself is still present on machines. At some later point, the AIS 1.5 agent can be uninstalled from machines as part of routine maintenance.
You do not need to uninstall the AIS 1.5 client. The AIS 2.0 client will install along-side the AIS 1.5 client on the same machine. In fact both clients run and report inventory to their respective services.
This approach lets customers (large customers particularly) stage the deployment of the AIS 2.0 client over a period of time. During this roll out, they can still use AIS 1.5 since all the AIS 1.5 agents are still reporting inventory.
The recommended guidance is to deploy the AIS 2.0 agent. Once fully deployed, switch over to use AIS 2.0, and retire the AIS 1.5 agents from the AIS 1.5 console. This will cause the AIS 1.5 agents to stop reporting inventory, but the agent itself is still present on machines. At some later point, the AIS 1.5 agent can be uninstalled from machines as part of routine maintenance.
You do not need to uninstall the AIS 1.5 client. The AIS 2.0 client will install along-side the AIS 1.5 client on the same machine. In fact both clients run and report inventory to their respective services.
This approach lets customers (large customers particularly) stage the deployment of the AIS 2.0 client over a period of time. During this roll out, they can still use AIS 1.5 since all the AIS 1.5 agents are still reporting inventory.
The recommended guidance is to deploy the AIS 2.0 agent. Once fully deployed, switch over to use AIS 2.0, and retire the AIS 1.5 agents from the AIS 1.5 console. This will cause the AIS 1.5 agents to stop reporting inventory, but the agent itself is still present on machines. At some later point, the AIS 1.5 agent can be uninstalled from machines as part of routine maintenance.
You do not need to uninstall the AIS 1.5 client. The AIS 2.0 client will install along-side the AIS 1.5 client on the same machine. In fact both clients run and report inventory to their respective services.
This approach lets customers (large customers particularly) stage the deployment of the AIS 2.0 client over a period of time. During this roll out, they can still use AIS 1.5 since all the AIS 1.5 agents are still reporting inventory.
The recommended guidance is to deploy the AIS 2.0 agent. Once fully deployed, switch over to use AIS 2.0, and retire the AIS 1.5 agents from the AIS 1.5 console. This will cause the AIS 1.5 agents to stop reporting inventory, but the agent itself is still present on machines. At some later point, the AIS 1.5 agent can be uninstalled from machines as part of routine maintenance.
You do not need to uninstall the AIS 1.5 client. The AIS 2.0 client will install along-side the AIS 1.5 client on the same machine. In fact both clients run and report inventory to their respective services.
This approach lets customers (large customers particularly) stage the deployment of the AIS 2.0 client over a period of time. During this roll out, they can still use AIS 1.5 since all the AIS 1.5 agents are still reporting inventory.
The recommended guidance is to deploy the AIS 2.0 agent. Once fully deployed, switch over to use AIS 2.0, and retire the AIS 1.5 agents from the AIS 1.5 console. This will cause the AIS 1.5 agents to stop reporting inventory, but the agent itself is still present on machines. At some later point, the AIS 1.5 agent can be uninstalled from machines as part of routine maintenance.
You do not need to uninstall the AIS 1.5 client. The AIS 2.0 client will install along-side the AIS 1.5 client on the same machine. In fact both clients run and report inventory to their respective services.
This approach lets customers (large customers particularly) stage the deployment of the AIS 2.0 client over a period of time. During this roll out, they can still use AIS 1.5 since all the AIS 1.5 agents are still reporting inventory.
The recommended guidance is to deploy the AIS 2.0 agent. Once fully deployed, switch over to use AIS 2.0, and retire the AIS 1.5 agents from the AIS 1.5 console. This will cause the AIS 1.5 agents to stop reporting inventory, but the agent itself is still present on machines. At some later point, the AIS 1.5 agent can be uninstalled from machines as part of routine maintenance.
You do not need to uninstall the AIS 1.5 client. The AIS 2.0 client will install along-side the AIS 1.5 client on the same machine. In fact both clients run and report inventory to their respective services.
This approach lets customers (large customers particularly) stage the deployment of the AIS 2.0 client over a period of time. During this roll out, they can still use AIS 1.5 since all the AIS 1.5 agents are still reporting inventory.
The recommended guidance is to deploy the AIS 2.0 agent. Once fully deployed, switch over to use AIS 2.0, and retire the AIS 1.5 agents from the AIS 1.5 console. This will cause the AIS 1.5 agents to stop reporting inventory, but the agent itself is still present on machines. At some later point, the AIS 1.5 agent can be uninstalled from machines as part of routine maintenance.
You do not need to uninstall the AIS 1.5 client. The AIS 2.0 client will install along-side the AIS 1.5 client on the same machine. In fact both clients run and report inventory to their respective services.
This approach lets customers (large customers particularly) stage the deployment of the AIS 2.0 client over a period of time. During this roll out, they can still use AIS 1.5 since all the AIS 1.5 agents are still reporting inventory.
The recommended guidance is to deploy the AIS 2.0 agent. Once fully deployed, switch over to use AIS 2.0, and retire the AIS 1.5 agents from the AIS 1.5 console. This will cause the AIS 1.5 agents to stop reporting inventory, but the agent itself is still present on machines. At some later point, the AIS 1.5 agent can be uninstalled from machines as part of routine maintenance.
You do not need to uninstall the AIS 1.5 client. The AIS 2.0 client will install along-side the AIS 1.5 client on the same machine. In fact both clients run and report inventory to their respective services.
This approach lets customers (large customers particularly) stage the deployment of the AIS 2.0 client over a period of time. During this roll out, they can still use AIS 1.5 since all the AIS 1.5 agents are still reporting inventory.
The recommended guidance is to deploy the AIS 2.0 agent. Once fully deployed, switch over to use AIS 2.0, and retire the AIS 1.5 agents from the AIS 1.5 console. This will cause the AIS 1.5 agents to stop reporting inventory, but the agent itself is still present on machines. At some later point, the AIS 1.5 agent can be uninstalled from machines as part of routine maintenance.
You do not need to uninstall the AIS 1.5 client. The AIS 2.0 client will install along-side the AIS 1.5 client on the same machine. In fact both clients run and report inventory to their respective services.
This approach lets customers (large customers particularly) stage the deployment of the AIS 2.0 client over a period of time. During this roll out, they can still use AIS 1.5 since all the AIS 1.5 agents are still reporting inventory.
The recommended guidance is to deploy the AIS 2.0 agent. Once fully deployed, switch over to use AIS 2.0, and retire the AIS 1.5 agents from the AIS 1.5 console. This will cause the AIS 1.5 agents to stop reporting inventory, but the agent itself is still present on machines. At some later point, the AIS 1.5 agent can be uninstalled from machines as part of routine maintenance.
You do not need to uninstall the AIS 1.5 client. The AIS 2.0 client will install along-side the AIS 1.5 client on the same machine. In fact both clients run and report inventory to their respective services.
This approach lets customers (large customers particularly) stage the deployment of the AIS 2.0 client over a period of time. During this roll out, they can still use AIS 1.5 since all the AIS 1.5 agents are still reporting inventory.
The recommended guidance is to deploy the AIS 2.0 agent. Once fully deployed, switch over to use AIS 2.0, and retire the AIS 1.5 agents from the AIS 1.5 console. This will cause the AIS 1.5 agents to stop reporting inventory, but the agent itself is still present on machines. At some later point, the AIS 1.5 agent can be uninstalled from machines as part of routine maintenance.
You do not need to uninstall the AIS 1.5 client. The AIS 2.0 client will install along-side the AIS 1.5 client on the same machine. In fact both clients run and report inventory to their respective services.
This approach lets customers (large customers particularly) stage the deployment of the AIS 2.0 client over a period of time. During this roll out, they can still use AIS 1.5 since all the AIS 1.5 agents are still reporting inventory.
The recommended guidance is to deploy the AIS 2.0 agent. Once fully deployed, switch over to use AIS 2.0, and retire the AIS 1.5 agents from the AIS 1.5 console. This will cause the AIS 1.5 agents to stop reporting inventory, but the agent itself is still present on machines. At some later point, the AIS 1.5 agent can be uninstalled from machines as part of routine maintenance.
You do not need to uninstall the AIS 1.5 client. The AIS 2.0 client will install along-side the AIS 1.5 client on the same machine. In fact both clients run and report inventory to their respective services.
This approach lets customers (large customers particularly) stage the deployment of the AIS 2.0 client over a period of time. During this roll out, they can still use AIS 1.5 since all the AIS 1.5 agents are still reporting inventory.
The recommended guidance is to deploy the AIS 2.0 agent. Once fully deployed, switch over to use AIS 2.0, and retire the AIS 1.5 agents from the AIS 1.5 console. This will cause the AIS 1.5 agents to stop reporting inventory, but the agent itself is still present on machines. At some later point, the AIS 1.5 agent can be uninstalled from machines as part of routine maintenance.
You do not need to uninstall the AIS 1.5 client. The AIS 2.0 client will install along-side the AIS 1.5 client on the same machine. In fact both clients run and report inventory to their respective services.
This approach lets customers (large customers particularly) stage the deployment of the AIS 2.0 client over a period of time. During this roll out, they can still use AIS 1.5 since all the AIS 1.5 agents are still reporting inventory.
The recommended guidance is to deploy the AIS 2.0 agent. Once fully deployed, switch over to use AIS 2.0, and retire the AIS 1.5 agents from the AIS 1.5 console. This will cause the AIS 1.5 agents to stop reporting inventory, but the agent itself is still present on machines. At some later point, the AIS 1.5 agent can be uninstalled from machines as part of routine maintenance.
You do not need to uninstall the AIS 1.5 client. The AIS 2.0 client will install along-side the AIS 1.5 client on the same machine. In fact both clients run and report inventory to their respective services.
This approach lets customers (large customers particularly) stage the deployment of the AIS 2.0 client over a period of time. During this roll out, they can still use AIS 1.5 since all the AIS 1.5 agents are still reporting inventory.
The recommended guidance is to deploy the AIS 2.0 agent. Once fully deployed, switch over to use AIS 2.0, and retire the AIS 1.5 agents from the AIS 1.5 console. This will cause the AIS 1.5 agents to stop reporting inventory, but the agent itself is still present on machines. At some later point, the AIS 1.5 agent can be uninstalled from machines as part of routine maintenance.