3 ms·

Run Outlook in a Windows VM on Linux instead of doing your real work in a Linux VM on Windows.

saiya-jin 9y ago
not possible due to company policies. you wouldn't be able to connect to our network with linux desktop anyway. welcome to corporate world
likeclockwork 9y ago
So, someone wrote this reply and it got downvoted to death or they're hellbanned or something, I want to reply to it anyway. They said: not possible due to company policies. you wouldn't be able to connect to our network with Linux desktop anyway. welcome to corporate world The responder reveals themselves to be an "inside the box" thinker. You could shrink your windows partition, install Linux, boot Linux natively, boot the existing Windows partition as a VM in VirtualBox, assign your physical NIC to the Windows VM, and use the Windows VM as a gateway to the network.
- tolle 9y ago
  Being able to do something doesn't mean you are able to do it. Good luck with that setup if you are working in finance and something fucks up or there's an audit.
  - nnq 9y ago
    > Good luck with that setup if you are working in finance and something fucks up or there's an audit. ...don't most companies have a clear separation between (1) software engineers, whose job is pushing out code to cloud/servers/other-users (and who nobody should care what they use to develop that code that they push out), and (2) software users, who actually use the apps to push money/data around?! If you're working in finance you're either in group (1) where you can use mostly anything compatible with security policies, or in group (2) where you can use ONLY what's whitelisted. If you're the rare snowflake sitting in both groups at once, then you just use 2 different separate computers. And auditing only touches group (2) because they are the only ones handling money and real data, unless you're in a criminal case or something, where auditing would be done by computer security forensic experts anyway, who's by able to handle auditing the "exotic" setups of group (1). And if somebody is auditing the tech side, they would be looking at git repositories, ci servers, etc. ...not the places where code is pushed from.

not possible due to company policies. you wouldn't be able to connect to our network with linux desktop anyway. welcome to corporate world

likeclockwork 9y ago

So, someone wrote this reply and it got downvoted to death or they're hellbanned or something, I want to reply to it anyway. They said: not possible due to company policies. you wouldn't be able to connect to our network with Linux desktop anyway. welcome to corporate world The responder reveals themselves to be an "inside the box" thinker. You could shrink your windows partition, install Linux, boot Linux natively, boot the existing Windows partition as a VM in VirtualBox, assign your physical NIC to the Windows VM, and use the Windows VM as a gateway to the network.

tolle 9y ago
Being able to do something doesn't mean you are able to do it. Good luck with that setup if you are working in finance and something fucks up or there's an audit.
- nnq 9y ago
  > Good luck with that setup if you are working in finance and something fucks up or there's an audit. ...don't most companies have a clear separation between (1) software engineers, whose job is pushing out code to cloud/servers/other-users (and who nobody should care what they use to develop that code that they push out), and (2) software users, who actually use the apps to push money/data around?! If you're working in finance you're either in group (1) where you can use mostly anything compatible with security policies, or in group (2) where you can use ONLY what's whitelisted. If you're the rare snowflake sitting in both groups at once, then you just use 2 different separate computers. And auditing only touches group (2) because they are the only ones handling money and real data, unless you're in a criminal case or something, where auditing would be done by computer security forensic experts anyway, who's by able to handle auditing the "exotic" setups of group (1). And if somebody is auditing the tech side, they would be looking at git repositories, ci servers, etc. ...not the places where code is pushed from.