How M$ shakedown stupid corporations
-
https://docs.microsoft.com/en-us/azure/virtual-machines/windows/time-sync
Time sync is important for security and event correlation. Sometimes it is used for distributed transactions implementation. Time accuracy between multiple computer systems is achieved through synchronization. Synchronization can be affected by multiple things, including reboots and network traffic between the time source and the computer fetching the time.
Azure is now backed by infrastructure running Windows Server 2016. Windows Server 2016 has improved algorithms used to correct time and condition the local clock to synchronize with UTC. Windows Server 2016 also improved the VMICTimeSync service that governs how VMs sync with the host for accurate time. Improvements include more accurate initial time on VM start or VM restore and interrupt latency correction for samples provided to Windows Time (W32time).
Like really ? they cant update a service in Windows 2012 ? I get it they make money that way but the explanation is stupid . You can like provide an update that will replace the service executable ? the only way is too deploy new servers OS on 2016 ? I dont know even if you can like upgrade from 2012 to 2016... what a mess thank god for
GNU/Linux -
@Emad-R said in How M$ shakedown stupid corporations:
https://docs.microsoft.com/en-us/azure/virtual-machines/windows/time-sync
Time sync is important for security and event correlation. Sometimes it is used for distributed transactions implementation. Time accuracy between multiple computer systems is achieved through synchronization. Synchronization can be affected by multiple things, including reboots and network traffic between the time source and the computer fetching the time.
Azure is now backed by infrastructure running Windows Server 2016. Windows Server 2016 has improved algorithms used to correct time and condition the local clock to synchronize with UTC. Windows Server 2016 also improved the VMICTimeSync service that governs how VMs sync with the host for accurate time. Improvements include more accurate initial time on VM start or VM restore and interrupt latency correction for samples provided to Windows Time (W32time).
Like really ? they cant update a service in Windows 2012 ? I get it they make money that way but the explanation is stupid . You can like provide an update that will replace the service executable ? the only way is too deploy new servers OS on 2016 ? I dont know even if you can like upgrade from 2012 to 2016... what a mess thank god for
GNU/LinuxThey are specifically talking about VMs here - talking about 2016 seems old. Wouldn't it be 2019 now? Also If the VMs get their time from the hypervisor - that's completely free, so no shakedown there.
Now Azure, which is what you specifically quoted - no clue there, and if you're running in the Azure cloud, then I'm guessing you have rights to use 2016+ there anyway from your licensing, so again, no shakedown.
I suppose this could be an issue for on prem servers with a 2012 server acting as a time source... but as @scottalanmiller constantly says - If you are using MS products - then one of the things you are agreeing to by using MS products is that you will continue to PAY for the upgrades as they are released - so again, not really a shakedown, because you should already be completely prepared to spend the money to move to the new versions. If you can't afford that, then why in the world are you using Windows in the first place?
-
doesnt change that it is still stupid. Also in the Windows scene, 2012 is current. 2008 is old.
-
@Emad-R said in How M$ shakedown stupid corporations:
Also in the Windows scene, 2012 is current. 2008 is old.
Eh? 2012 might be LTSB, but it's definitely not current. That would be 2019.
-
@Dashrender said in How M$ shakedown stupid corporations:
@Emad-R said in How M$ shakedown stupid corporations:
Also in the Windows scene, 2012 is current. 2008 is old.
Eh? 2012 might be LTSB, but it's definitely not current. That would be 2019.
Says the Linux guy.... @Emad-R is right though. In the Windows world, 2012 is what most consider "current". Doesn't make it right, but that's the general thought process in MS ecosystems.
-
@RojoLoco said in How M$ shakedown stupid corporations:
@Dashrender said in How M$ shakedown stupid corporations:
@Emad-R said in How M$ shakedown stupid corporations:
Also in the Windows scene, 2012 is current. 2008 is old.
Eh? 2012 might be LTSB, but it's definitely not current. That would be 2019.
Says the Linux guy.... @Emad-R is right though. In the Windows world, 2012 is what most consider "current". Doesn't make it right, but that's the general thought process in MS ecosystems.
But Microsoft themselves don't think this way. Just because a client of there's does, doesn't change the fact that 2012 is an old OS.
-
@DustinB3403 said in How M$ shakedown stupid corporations:
@RojoLoco said in How M$ shakedown stupid corporations:
@Dashrender said in How M$ shakedown stupid corporations:
@Emad-R said in How M$ shakedown stupid corporations:
Also in the Windows scene, 2012 is current. 2008 is old.
Eh? 2012 might be LTSB, but it's definitely not current. That would be 2019.
Says the Linux guy.... @Emad-R is right though. In the Windows world, 2012 is what most consider "current". Doesn't make it right, but that's the general thought process in MS ecosystems.
But Microsoft themselves don't think this way. Just because a client of there's does, doesn't change the fact that 2012 is an old OS.
But that does not change the fact that businesses that run all Windows consider 2012 basically current.
-
@RojoLoco said in How M$ shakedown stupid corporations:
@DustinB3403 said in How M$ shakedown stupid corporations:
@RojoLoco said in How M$ shakedown stupid corporations:
@Dashrender said in How M$ shakedown stupid corporations:
@Emad-R said in How M$ shakedown stupid corporations:
Also in the Windows scene, 2012 is current. 2008 is old.
Eh? 2012 might be LTSB, but it's definitely not current. That would be 2019.
Says the Linux guy.... @Emad-R is right though. In the Windows world, 2012 is what most consider "current". Doesn't make it right, but that's the general thought process in MS ecosystems.
But Microsoft themselves don't think this way. Just because a client of there's does, doesn't change the fact that 2012 is an old OS.
But that does not change the fact that businesses that run all Windows consider 2012 basically current.
Then I will again parrot @scottalanmiller - those aren't real businesses, but hobby businesses. No one who is running a real business considers 2012 current. What do they really honestly think that MS has not released a newer version in more than 7 years? (6 if the customer is actually on 2012R2)
-
@RojoLoco said in How M$ shakedown stupid corporations:
@DustinB3403 said in How M$ shakedown stupid corporations:
@RojoLoco said in How M$ shakedown stupid corporations:
@Dashrender said in How M$ shakedown stupid corporations:
@Emad-R said in How M$ shakedown stupid corporations:
Also in the Windows scene, 2012 is current. 2008 is old.
Eh? 2012 might be LTSB, but it's definitely not current. That would be 2019.
Says the Linux guy.... @Emad-R is right though. In the Windows world, 2012 is what most consider "current". Doesn't make it right, but that's the general thought process in MS ecosystems.
But Microsoft themselves don't think this way. Just because a client of there's does, doesn't change the fact that 2012 is an old OS.
But that does not change the fact that businesses that run all Windows consider 2012 basically current.
Let me guess - they also consider Windows 7 current as well? Even though TV ads have been blasting about Windows 8, 8.1 and 10 for better than 6 years?
-
You have not seen much of "real business" then, I cannot disclose info, but I think this corp is like multi-million revenue.
Thats how it is ins real world, they get bloated and move slower, thats what happen when corp grow, if you keep it startup-ish vibe and "move fast and break things" you will be running the latest but not everyone is like that.
Besides windows painfull upgrading process helps you to stick to whats running.
And no on the client side, its all Win10 ... sadly we use Win10 to manage Linux machines
I hate that mremote/putty shit -
@Emad-R said in How M$ shakedown stupid corporations:
You have not seen much of "real business" then, I cannot disclose info, but I think this corp is like multi-million revenue.
Thats how it is ins real world, they get bloated and move slower, thats what happen when corp grow, if you keep it startup-ish vibe and "move fast and break things" you will be running the latest but not everyone is like that.
Besides windows painfull upgrading process helps you to stick to whats running.
And no on the client side, its all Win10 ... sadly we use Win10 to manage Linux machines
I hate that mremote/putty shitThis is false.
Big business makes quite an effort to stay current in the Windows world, especially if they are multi-billion $$ company. They HAVE to. It's not a choice.
It's constant change going on, all the time. 2019 is current, when a server is needed at all. Most are really going serverless when possible, lots of SaaS, Cloud, etc.
You might be thinking of U.S. defense companies. I mean they run old shit and pay millions and billions to maintain OAF software support.
-
Dude you neglect alot of company that uses network isolation as security, and DMZ and LAN based security. They invest and policies and change controls forms instead of upgrading
-
@Obsolesce not even multi-billion companies. That's where it takes more time to get things implemented...
-
@dbeato said in How M$ shakedown stupid corporations:
@Obsolesce not even multi-billion companies. That's where it takes more time to get things implemented...
No it doesn't. It's way faster. Or, it can be. But I know the real answer is it depends. Many SMBs barely ever stay current. One could, and it could be done in a day if they have one easy server to upgrade.
On the other hand some multi-billion $ companies are continually updating, staying on top of things. And because it's a priority, systems are current while other smaller companies are still on 2008 R2...
I'm not saying all, it does depend, but I think it's not good to generalize, because in my own personal experience, it's the smaller guy's who are much further behind.
-
To get accurate time sync on windows you install ntp. It's as simple as that.
The W32time service in Windows is to ntp, what timesyncd in linux is to ntp - a simple and not-accurate but often good enough time sync for clients.
BTW, already back in the Windows 3.1 days you had something called Tardis that you would run for NTP sync. Windows own time service was only designed to keep time reasonably synced for kerberos and stuff like that. I think it appears first in Windows 2000 Server.
-
@Obsolesce said in How M$ shakedown stupid corporations:
@dbeato said in How M$ shakedown stupid corporations:
@Obsolesce not even multi-billion companies. That's where it takes more time to get things implemented...
No it doesn't. It's way faster. Or, it can be. But I know the real answer is it depends. Many SMBs barely ever stay current. One could, and it could be done in a day if they have one easy server to upgrade.
On the other hand some multi-billion $ companies are continually updating, staying on top of things. And because it's a priority, systems are current while other smaller companies are still on 2008 R2...
I'm not saying all, it does depend, but I think it's not good to generalize, because in my own personal experience, it's the smaller guy's who are much further behind.
from my exp it is the opposite.
-
It's not about the size of the company, it's how much regulation they are required to follow. Financial companies don't do that shit because they would fail common controls if they have poor practices or use vulnerable software.
Other examples would be NIST 800-53 controls or HITRUST. While they can be annoying to implement and not all are necessary relevant for everyone, they force a good overall security posture.
Without forcing security controls companies will continue to do stupid shit. I'd really like to see something like GDPR here in the US. HIPAA is in an obvious need of a revamp as well.
-
@Emad-R said in How M$ shakedown stupid corporations:
doesnt change that it is still stupid. Also in the Windows scene, 2012 is current. 2008 is old.
2012 is old. 2012 R2 is the oldest thing you can run and not be totally embarrassed. If your business runs 2012, it gives the impression that they are failing. 2012 R2, you can excuse as being old but marginally acceptable. I've not seen anyone that considered 2012 viable these days.
-
Aren't they talking about the hypervisors Azure is using? Which I believe used to be a modified version of server 2008 R2? So now being server 2016 would be good news, and thus the improved time syncing.
-
@Emad-R said in How M$ shakedown stupid corporations:
You have not seen much of "real business" then, I cannot disclose info, but I think this corp is like multi-million revenue.
But it doesn't sound like a serious business. You can make money in all kinds of incompetent ways. But not running like a business, not having the ability to execute.... sounds like a joke. There are reasons that sometimes companies get trapped and once in a great while there is a valid excuse for not being able to upgrade. But these are insanely rare.
