I’m posting this in case it’ll help anyone else out that may have access to some of the old Datto switches.

I work for a business that previously used Datto extensively (before they were sold to Kaseya) and we had a lot of old Datto hardware because of that. We’ve since moved on to other hardware solutions for clients but we kinda got stuck with this old hardware and I ended up taking some of the switches we had (an S24 and a E48) - I took them with the expectation that I’ll just use them as dumb unmanaged PoE switches. My employer tried to give these away for free through facebook marketplace and other similar sites just to get them out of their hair and would get people asking about them but nobody ultimately took them.

Well I did use them as unmanaged switches for a bit; I blocked internet access for them on my firewall just in case it was reaching out to the cloud, so nothing could potentially be modified suddenly. I recently spent some time looking into the console access on them to see if there’s anything there. After a bit of searching I found that if you factory reset them and prevent access to the cloud, they have a default openmesh password ( 0p3nm3$h! ) on the admin account which you can use to gain full access to the CLI and thus some level of management of the switch.

I then examined the running config and discovered they have a local web interface (and ssh and telnet) which is disabled by default and you can enable, you can also create other users on it for management. So, through the console I obviously enabled those to see if they function and to my surprise they indeed do function. So now I have proper 24 and 48 port managed PoE switches at my disposal which made me pretty happy.

Anyway, if anyone happens to stumble upon these switches (at least the S24 and E48 models) and you can use them, know that you can now fully manage them on your own if you so desire. The console connection requires a baud rate of 115200 and then you can just login with username admin and password 0p3nm3$h!. From there you can use the contextual help (?) to figure out the commands. To enable the web interface, after logging in you can do this: 

configure  
ip https  
exit  
save

then you can simply access it in a browser at https://{ip-address-of-switch} using an existing user account. For reference, to create an account you can use a command like this: 

configure  
username {USERNAMEHERE} secret {PASSWORDHERE}  
exit  
save

I did verify that changes made via the web interface do actually work and change the configuration, I half-expected it wouldn’t work but was pleasantly surprised it does.