Still getting double entries in the k1 after deployment with the k2
Guys I have had this issue for years. Still getting double entries of
freshly deployed machines in the K1.
When an existing PC is freshly redeployed with the k2 and renamed to
the to the previous name it had..... this shows up as a double entry in the K1.
And yes,,,,, I have the "Apply KUID to K1000 agent" task in the deployment.
it runs after the agent install.
But still getting this issue on a few machines. Which is funny. Why not all machines?
Help?
Answers (1)
I think there is a simple fix: you have this in the wrong order. Always apply the KUID BEFORE the agent install. This is because the agent install applies the KUID, so if it is not maintained previous to this is gets essentially wiped or something and new one assigned. I do not have a reference for this, I know from my own deployments and training through Kace a loooooooooong time ago. Please excuse my possible mis-quoting of the process for this reason.
Gist of it is, apply KUID first, then agent install, always.
Comments:
-
Ok Mashby. Thanks. Will try it! - akmagnum 3 years ago
