Search the Community

The latest Vmware appliance not being able to join the domain after you set it up. I've deployed the era_appliance.ova 4 times now, each time keeping track of how what I put in to allow this appliance onto my domain. Ive followed the directions and haven't been able to come up with anything. The appliance never shows up in AD, so I know it isnt getting onto the domain, the account I use is a domain admin, and I made sure the pass was correct. Obviously I have searched the forums for anything relevant, but am surprised to find out that something so epic as troubleshooting documentation about not being able to get this thing onto the domain doesn't really jump out at you when you put in phrases like - CANT GET THIS THING ONTO THE DOMAIN. Ive put in every string of words I thought of to come up with anything, and tbh I could totally be missing it, because its labeled in some esoteric, or should I say ESETERIC formula. Any one else have this issue starting out? Is it a simple mistake I'm making?

ERA appliance appears to be broken once SMB1 has been removed from the network. We removed it because "it was not required", at least not by any Microsoft or Apple machine. But the ERA appliance appears to require it. We had decided to remove SMB1 with the recent string of vulnerabilities. the following is how SMB1 was removed from ALL machines: sc.exe config lanmanworkstation depend= bowser/mrxsmb20/nsi sc.exe config mrxsmb10 start= disabled Set-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters" SMB1 -Type DWORD -Value 0 –Force this is our current version of the appliance: (6.3) ESET Remote Administrator (Server), Version 6.3.148.0 ESET Remote Administrator (Web Console), Version 6.3.114.0 Problems: could not log into the web console with our domain credentials to the ERA appliance. We can log in using the local web server account. workstations no longer getting updates from the ERA Appliance trying to import the data from our 6.3 appliance to a newly downloaded 6.5 appliance fails. What are our options now that SMB1 is permanently removed form our network? How do we migrate the DB from a 6.3 appliance to a new 6.5 appliance? And then how do we make the 6.5 appliance work in a <<SMB1 Disabled>> environment? With the mounting number of vulnerabilities in SMB1 and NTLM, more people will start to shut these old technologies off.