jrodirguezHow do you handle new machines coming into the network?
CCDaveWe handle new machines by adding a new Group Policy with a Logon Script to run the KcsSetup.exe out of the domain Scripts folder. Link this GP to the top of your domain structure and it will catch all new computers/servers that are added. Just make sure you update the KcsSetup.exe if you update Kaseya or your settings.
CCDaveWe use it in both situations: Original rollout (though I prefer LAN Watch) and adding new machines.
When you create the agent package there are command line switches you specify in the package. One of these (I can't remember which) tells the KcsSetup.exe to terminate if Kaseya is detected. This prevents any type of second install, which wouldn't work anyways. You can also bind administrator credentials into the package so the users don't need to have admin privlidges to run.
I like having this package running all the time like this so we catch when an existing machine is rebuilt.
jrodirguezI have a few agents installed on servers and when I attempt to scan the ip ranges it never updates, or at least it is taking at least 10-15 to show up on the install agent list. Is this normal? Sometimes it looks like it is not even scanning the ip range.
CCDaveWow, that's a great documented list for new installs! One big suggestion I have right off the bat is why you aren't using template agents to preform most of your configuration automatically.
dwujcikThe method we use for configuring is similar to templating. We'll configure the first WS the way we want it for that client, copy the settings to all of the other machines, then add the server stuff to the servers.
Every now and then we do it backwards and get "OMG Exchange isn't running and I can't start it" messages on the workstations... Then we laugh at the tech that did it (usually me).