ELA and DHCP with workstation logs
Does anyone else have an issue with the way ELA stores both the DNS name and the IP address to identify a workstation? I have an issue in which when a new computer gets a previous IP address that was used with a registered computer, I can not add the workstation because it states the computer already exists. There are situation that once a workstation is registered, it might receive a new IP address later (nature of dhcp), I am unable to add a new computer because it received the previous IP address. I submitted a ticket on this but support told me it is working as designed. I have a hard time believing no one else is experiencing this issue.
ELA works fine for my servers as they usually get a static address and their IP address never change but workstation are proving to very difficult to manage. And you cannot delete the workstation host to re-add them with their new IP address from ELA as it will delete all logs and archive files.
ELA works fine for my servers as they usually get a static address and their IP address never change but workstation are proving to very difficult to manage. And you cannot delete the workstation host to re-add them with their new IP address from ELA as it will delete all logs and archive files.
Am I alone in this frustration?
Topic Participants
David Stuller
Sam Shankar
Karthik Annavi
New to M365 Manager Plus?
New to M365 Manager Plus?
New to RecoveryManager Plus?
New to RecoveryManager Plus?
New to Exchange Reporter Plus?
New to Exchange Reporter Plus?
New to SharePoint Manager Plus?
New to SharePoint Manager Plus?
New to ADManager Plus?