4

Disclaimer: Technically it's not "our" stack, but we have to use it so....

A webapp we built runs inside the company's network we built it for. Their IT are windows lovers, so everything has to run on Windows servers, even the tablets which are used to access said web app need to have windows.
Their company network isn't accessable from the outside world, so we have access via VPN to get into their network. But this isn't enough to access that shitty windows server our software runs on. After that VPN, you have to connect to a different VPN to which you can only connect to while you're inside the company's network. Then you have access to two servers, one the application is running on and one, well to see if you're changes were deployed correctly because the production server doesn't have a browser on it other than shitty internet explorer 8.

The only way to connect to the server is using RDP. Not even samba or so. To deploy the changes we made to our app, you need to copy paste the files from your local machine to the server. And don't get me started on running mssql migration with the shitty mssql console 😤😤

Why would anyone who isn't a complete idiot use Windows for servers or mssql in the first place????

Comments
  • 2
    Windows server and MSSQL is both great, if used the right way.

    Even I who are completely lost in Windows can fix stuff
  • 4
    I'm far from being a windows fan, really far, but with the right devops and sysadmins, i've seen windows based stacks and networks work really great. imho, the only thing that sucks no matter what, is TFVC.

    if in 2018 they're still running winserver2003, it is their problem, and they must be aware of it. aware in the sense that annoying waste of time on your side = annoying waste of money on theirs.
Add Comment