bNetworked

OK .. I've been working through a few more things to try and get this sorted out based on your advice. This is an all-in-one install, so all the components are on one. The old server, after the migration took place, was shut down and is no longer running so it can't be connecting. I've removed it's computer entry from the listed computers - is there anywhere else that I need to remove a reference to it because it was a server? The new server's agent didn't seem to be picking up correctly, so I uninstalled it and reinstalled it - not sure what happened the first time, but it is registering in the console now. And I was about to write that now the server version is just coming back as a string of n/a n/a n/a ... but before I hit post on this I went back and checked and now it's coming up right with the Windows Server 2016. I guess it just took a few minutes to update what was going on. The note for upgrade has cleared and it seems to be good to go now. Thanks again for your efficient helpful assistance! Regards, Brian

I've been doing relatively well with the migration/upgrade project of my ESET ERA/ESMC server but I just hit a bit of an oddity. For the background, here's what I've done so far: -backed up database from My SQL on previous ERA host server -set up new ERA host server on Windows Server 2016 using MySQL database -got everything imported, up and running as ERA 6.5 I'm now working on upgrading to ESMC, which is also going well - I'm logging into the web console now and that's all gone quite smoothly. It is showing on the server that I'm running: ESET Security Management Center (Server), Version 7.0 (7.0.577.0)ESET Security Management Center (Web Console), Version 7.0 (7.0.429.0) So, it prompts me to upgrade because there's a newer version available. This is a little odd because I just downloaded this version half an hour ago ... so I guess that stand alone downloads off the web site aren't the latest updates? Anyway ... it throws an error that says "Failed to create task: the referenced repository package is not available." That's not the weird part ... the weird part is when I was checking to see how the versions I was running stacked up against what the latest version it wanted to install - on my Help | About page it says that I'm using the "Ubuntu (64-bit), Version 16.04" ... so ... there's a holdover in the database from the migration that hasn't picked up what system the migration/upgrade is running on. I'm thinking that this may be impacting the ability of the platform to run an upgrade if it's trying to do it using Debian style package management tools which are obviously not available on Windows Server 2016. Image of versioning and the Ubuntu reference attached. TLDR; How do I tell a migrated ERA/ESMC database that it's now running on Windows Server 2016 and not Ubuntu 16.04? Thanks for any help ... doesn't everyone love a puzzle? Cheers, Brian

Martin - Thanks. This cleared up my problem. Apparently I'd just been working on that too long yesterday and I saw the part where it said MySQL 5.6.22 and missed the two important words that - "and later." FYI - the innodb_log_files_in_group setting is not present in the my.ini file for the 5.7.x MySQL that I had installed. I think that the default setting of 2 may be implied, but I just added the settings variable to the my.ini file just to be sure. Thanks for your help on this ... it just needed to be looked at by someone else that hadn't been banging their head on the wall all day long. Cheers, Brian

I've got a project that I've started that involves: Migrating an ERA 6.5 server install on Ubuntu/MySQL to Windows Server 2016/MySQL, and then the Windows Server install is going to be upgraded to ESMC once complete. I need to use MySQL on Windows apparently because I've read that the database server has to be same in order for me to be able to export it from the MySQL/Ubuntu config to the Windows Server config. Here's what I'm trying to install: WIndows Server 2016 x64 MySQL 5.7.22 64 bit ODBC Connector 5.3.10 the problem that I'm running into is that no matter what I do, and what combination of software I run (I've tried different 5.7.x versions of MySQL, versions of 5.2.x and 5.3.x of the connector) I always get the error "the database server is not configured correctly." This is apparently usually attributed to a setting in the my.ini file, but I've changed that setting and even used the command line to dump the variables (SHOW CONFIG) to verify that it has indeed taken hold with max_allowed_packet set to 33M (or more, I tried 50m just for fun and that didn't matter either). I've gone through all the pre-requisites half a dozen times and double checked configs too. I've been banging my head on the wall for about 5 hours now and I'm out of ideas. I tried to search on the error in the forum here and I didn't get anything ... at the very least can someone point me to where install logs (or how to create them?) for the 64 bit ERA server install of 6.5 so that I can get some kind of detailed log of what is going wrong? Or does anyone have a good suggestion on how to resolve this? thanks, Brian