User Profile
IanMurphy48
Brass Contributor
Joined Jul 17, 2020
User Widgets
Recent Discussions
Re: Windows 2019 time service - sincronizing to best of three
Dave Patrick yeah, it does look like the fastest responder wins. Not exactly the best logic to be following. I haven't found any way to improve the situation either. I'll keep digging and post something here if I find a solution.1.2KViews0likes3CommentsWindows 2019 time service - sincronizing to best of three
I recently had a problem at a client of mine where one of their DCs syncronized its clock to an ntp server which was incorrect. ( http://www.ntppool.org/scores/ shows the moment the time was incorrect.... an hour out). It caused problems for a few hours as that affected their building management systems which sync their clocks with the DC. In the morning lights didn't automatically switch on and aircon systems started late due to the time difference The MS documentation says that the service will establish the most accurate clock to use as its source, but doesn't indicate if this occurs on every clock check or just once on service-startup? I always have two ntp sources configured on DCs. In this case the time service seems to have just consulted one and shifted its clock back by a full hour in one jump. My question is, is there any way to get it to query, say, 3 ntp servers and only have it make changes if at least two of the three coincide, thus avoiding the problem of an ntp server returning a wildly incorrect value for a brief time?Solved1.4KViews1like5CommentsRe: Force Teams desktop client update
This is awesome. In one link you've supplied more information than every other MS or Forum posting I've found on the subject. Why on earth couldn't MS just have posted this list and let people decide which version to install. Most will just go for the Production build in any case. Thank you very much.19KViews1like0CommentsRe: Force Teams desktop client update
StevenC365 Given the long history of MS doing precisely that, my answer is a resounding yes. MS fixes bugs which affect a lot of people or which create a lot of noise. I changed nothing, but the Teams issue disappeared a few weeks later, without so much as a reboot (I rarely reboot)... so, yes, it was a teams bug fixed by a Teams update.... why couldn't I just have installed the latest version? Ah, yes, because the latest version is never available for download. I currently have an issue at a client who is running office 2010 (still). All of a sudden some users have the Teams Icon in outlook, despite that not being supported in 2010. Some users, but not all, and I can't download the same version for everyone, so some people have the icon, some don't. Those that don't have it of course want to know why their neighbour is able to organise meetings from Outlook and they can't. All online help still says that this functionality does't exist. Isn't this release policy just great...18KViews0likes0CommentsRe: Force Teams desktop client update
StevenC365 >It is quite unlikely that any specific build would cause the issues you describe, >and that would seem to be largely verified by it remaining after a reinstall. >I would be looking into driver versions perhaps. It is *extremely* likely that a specific build would cause the issues I describe. Its called a bug. Thats why we update software. Its the principal reason for updating software. Drivers being out of date is just being ridiculous. You can always say that about anything. Why would only Teams, not much more than an advanced chat app, be affected by this magic driver issue when all the other stuff, using more advanced system features, is stable. Also, in my own case I know my driver set is up to date as I do update whenever something is available. On a client machine it would be less often, but in my case its all up to date and Teams still crashes constantly with no log. I'm basing this on supporting hundreds of desktops. If applications like Solidworks, office or the myriad of programming tools people use crashed, the users would be on the phone. They're not, but a lot of people do report that they missed teams chat messages because it was closed. Just Teams, which makes it pretty unlikely that all those desktops (with different models, different makes and different drivers) have issues which just happen to affect Teams and only Teams.135KViews0likes3CommentsRe: Force Teams desktop client update
ChristianBergstrom I have no problem with having the users running 1.3.0.3xx or 1.3.0.2xx versions, but what I see happening is the same as is happening with Win10. Most installations just update, but you end up with a significant number which are just orphaned and never update. With win10 you download an iso and update from that and... no problem, so why didn't they auto update? I'm seeing the same with Teams. Hundreds are running a more or less recent version, but then maybe a couple of dozen machines are seemingly 'stuck'. The msi installer simply does nothing to either the machine wide or profile installed versions when executed on these machines. Frustrating.137KViews1like1CommentRe: Force Teams desktop client update
StevenC365 Your faith in MS to just get everyone onto the best version for them is .. interesting. Given MSs history of just abandoning clients with major issues due to bugs, it seems unlikely that they are going to do any differently with Teams. Indeed, I manage around 450 desktops and I see a wide range of versions installed going from 1.2 through to 1.4. I reinstalled my own desktop yesterday with the latest version on the MS page and I've ended up with 1.4.0.2879, while I have desktops which are running 1.4.0.3484 - which I can't find anywhere. My machine also says I have the latest version, which is obviously wrong as I had a more recent version before the wipe and reinstall. I was forced to wipe Teams from my own machine because it was crashing every few hours. Nothing was displayed when it crashed. The window just closed. Wipe and reinstall has made no difference. It still crashes. So do colleagues. I would like to get everyone up to the same version and to not use the profile installed version... but no, this is almost impossible. In theory when you install the machine-wide version then the profile version should be removed. Never happens. Updating the machine wide will sometimes result in the profile version also updating, sometimes not. The idea that MS will just manage from the cloud this is laughable. What was wrong with just having an MSI installable product, like every other product?137KViews0likes8Comments
Recent Blog Articles
No content to show