Reputation
1,418
Next privilege 2,000 Rep.
Edit questions and answers
Badges
5 19 26
Impact
~302k people reached

  • 0 posts edited
  • 0 helpful flags
  • 25 votes cast
Feb
13
awarded  Notable Question
Oct
14
awarded  Stellar Question
Aug
10
awarded  Popular Question
Jul
29
awarded  Yearling
Jul
2
awarded  Famous Question
May
11
comment Prevent Windows Server 2012 from forcing a reboot after updates
It's 2015, my system is up to date, I still see no option under windows update settings titled "Don't start a countdown when I log in". This is an epic fail.
May
11
comment Prevent Windows Server 2012 from forcing a reboot after updates
This is the stupidest behavior I've ever seen in regards to automatic updates. It will actually wait for you to log in, then start a countdown timer that will force a reboot. So if you log in to do something, it basically sets a time bomb on your work window. This is almost at stupid as how the "shut down" command does the opposite and prevents a shut down by telling you to not turn off your machine because it installs updates; meanwhile the "shutdown without installing updates" command is hidden in the ctrl-alt-delete menu. It makes no sense.
Apr
10
awarded  Notable Question
Mar
26
awarded  Notable Question
Nov
26
awarded  Yearling
Oct
14
awarded  Popular Question
Sep
30
awarded  Popular Question
Sep
17
awarded  Notable Question
Aug
11
awarded  Popular Question
Jul
2
awarded  Curious
Mar
25
revised How to route traffic over an active VPN tunnel by domain name?
added 713 characters in body
Mar
25
revised How to route traffic over an active VPN tunnel by domain name?
added 729 characters in body
Mar
25
revised How to route traffic over an active VPN tunnel by domain name?
added 176 characters in body
Mar
25
answered How to route traffic over an active VPN tunnel by domain name?
Mar
25
comment How to route traffic over an active VPN tunnel by domain name?
I figured it out. I had to assign different subnets in the IPv4 routing services of the server in order to ensure the servers got different addresses. My first server allocates addresses in the subnet 192.168.1/24 and the other one allocates addresses in the subnet 192.168.2/24, which results in them getting different server IPv4 addresses (e.g. 192.168.1.1 and 192.168.2.1). I can now address them independently, the firewall is set up to allow sharing protocols only from those IP addresses, and everything is working fine. No 3rd party software required.