Sheridan

Its odd, as our domain PCs are UK in everything - and Edge has a policy show use Uk. When I check the users mailbox with 'Get-MailboxRegionalConfiguration -Identity' and it shows the correct en-GB region and date/time formats! Yet when in Excel 365 it defaults to English US so the date fields are wrong, which is causing issues with users creating files on site (saved on one drive) and then opening them either on or off site in the web app as the dates are all wrong for us!

Printing was a really easy thing to to deal with until W10 came along and its been a complete pain since!

These are both exactly the same on the server

This seems to be a recent thing, or its just being noticed more recently but whenever users are in Word/Excel in 365 the region is US even though our PCs, Edge, Chrome etc and tenancy are all set to UK but it insists we're US Is there no way to force the locale across 365 apps, as its a total pain with dates etc?

Not that I can see, as the primary app being used to test this is Word and the problem appears (or not) for the users whatever they use to access the printer properties

This is the odd behaviour - on the Printer server the preferences show the Page Layout as greyed out - but on the client where the printer is deployed it is showing as enabled (for me anyway, but not the user affected as they see the same on the server!)

Yeah the GPO that deploys printers (per user/targeted by computer OU) is fairly simple We don't have any feature locks in Papercut and the driver has been deleted and reinstalled on the affected PC What's even odder is the same user logs into a computer in the same OU and the driver options aren't greyed out! So its only for that user on that PC - even though the combination isn't unique in GPO/OU terms So User A on Computer A is has greyed out options User B on Computer A is fine User A on Computer B is fine User B on Computer B is fine! Computer A and B are identical (same hardware, same deployed OS and same OU) User A and B are in the same dept/OU and GPO settings! My brain hurts....

Success! Finally thanks to Autodesk intervening we have been given access again Sheerid were just a brick wall but Autodesk managed to get us re-validated

That’s the weird thing with this, two users of the same computer getting the same printer and same policies and will get the greyed out option and nothing I can see will reset it! Even removing their profile entirely makes no difference and the printer settings they see (usually when accessing the properties via Word) are identical to the other users but one a couple of print layout options greyed out i could have sworn I’d seen this before by my memory is letting me down on that one!

We run a few networked printers on a Windows print server managed by Papercut. Printers are deployed by GPO and generally all working OK However we have had some weirdness with the driver settings for some users - for example the settings for 'Multiple pages per side' are greyed out for some users of a PC, but not others The printer drivers are all the same (Lexmark V2) and are pushed from the server What's odd is if I login with a test account - they get the correct driver settings. Login as one of the users with the issue and the option is greyed out! Even if I delete their profile and they log back in the issue persists I vaguely remember seeing something like this issue years ago, but can anyone jog my memory as to what the heck is going on?

I can't see that on our ASA - but it does seem that is whats happening to users on a fairly random basis - they will connect fine, and then disconnect for whatever reason (sleep, wifi drops etc) and then the ASA shuns them for 60 minutes as its seen that as a threat I guess I can just disabled the 'Shun hosts detected by scanning threat' as I'm not sure how much help it is if its blocking legitimate connections

Our Cisco ASA VPN works fine - but an odd thing happens when clients PCs go to sleep (or drop wifi briefly) A successfully connected PC goes to sleep, and then once woken up the vpn client is dropped and will not reconnect (and still shows in the ASDM monitoring page) However, even if you Logout the session via ASDM the client cannot connect - saying it cannot contact the server. If they wait an hour (and it seems to be pretty specific to that!) then they can reconnect again I can't find a setting anywhere that would prevent reconnection within an hour - is there something that would prevent this? Even when sessions had been logged out at the ASA end as well? On further investigation it appears the client ip (or ISP ip) is being added to the shun list - which has a default timeout of 60 minutes which explains the complete blocking - but why its adding client source IPs to the shun list just because it disconnects is an odd one!

They don't seem to offer any way to start a new claim - its done online via sheerid and they say no and basically close the ticket with a message saying they won't discuss it further! We also didn't get any warnings about expiry - I suspect they're blacklisting us for some unknown and bizarre reason

Well good luck to anyone facing the same problem! Autodesk says sheerid get to decide who uses their products sheerid say we aren’t a school (even though we’ve previously been eligible for years!) autodesk say they can’t help because…..and loop What a shambolic system

I must be doing something fundamentally wrong here as it seems to ignore any NPS setting. When I test the login page with correct credentials I'm logged in fine - but the NPS logs on the RDS server and also the NPS/MFA show no logins (logging is set to show failed and successful attempts on both) My RDS server's NPS is set to authenticate to 'TS GATEWAY SERVER GROUP' which only contains one server (the NPS/MFA server) and the RDS Gateway RD-CAP is pointing to that server yet it authenticates somewhere correctly (without MFA) as it logs in when using correct credentials! What I can't get around is why its not redirecting the authentication to the seperate NPS/MFA server as there's nothing else to configure!

Thats exactly what I'm trying to do, seems better to use an existing working Radius/MFA setup but my RDS doesn't seem to attempt to connect to it Any more info would be helpful!

Thanks, I'm going to add another Radius server and add the MFA extension and use that - at least it keeps things seperate and leaves the working vpn setup alone (which I can remove when this is working!)

Hmm, I wonder if I should just add the Azure extension for NPS on the RDS server - this is really only a test as we only need the RDS server for maybe a year or so!

I'm just testing something and getting nowhere so I thought I'd do a sanity check with fellow Geeksters We currently have an old VPN that authenticates via an internal Radius server. That radius server has the Azure MFA component and it works fine. VPN users connect and authenticate and then respond the the MFA prompt on their phone What I'm planning to to do is implement an RDS server - and set it to authenticate using the existing Radius (with Azure MFA) server - so when a user logs in to the RDS server they login and authenticate via MFA I've setup a RDS server and set the RD Gateway Server RD-CAP to be the existing Radius/MFA server and set NPS on the RDS server to use the existing NPS server as a remote Radius server. However I'm either missing something trying something that isn't possible as when I test the connection it logs in without and MFA, and the Radius server with MFA shows no authentication requests so it must still be going through NPS on the RDS server Is this possible? Or do I need to setup a different way to use Radius with Azure MFA for the RDS server?

We've been using Autodesk Inventor for years here under the Education Network license (which allows us to use it on site with a license server) However our license has been expired as we are apparently no longer eligible (although according to the rules we still as - we're a single school academy!) and Autodesk use some third party (SheerID) to validate this Problem is Sheerid (whoever they are!) say No, and Autodesk say its not their problem and we have to contact Sheerid - who haven't replied to any messages! Just wondering if anyone else has been cut off like this? We're now going to have to find an open source alternative and re-jig the curriculum thanks the stubbornly unresponsive third party! Also, any recommendations for education suitable replacements for Inventor would be gratefully received 🙂

We do use Sophos, but there have global Exclusions in place since it was implemented (a few years ago) for the relevant Solus/SIMS folders This does seem to just be an issue since the Summer 25 update - when we ran the Spring 25 update (same AV and settings, same client OS, same Solus 3 server) we had hardly any issues and they were just the usual random failed install (i.e solus not working on client pc, or pc not online etc) There isn't a way to Deploy an update to single computer to test is there? Any deployment picks up all of the clients/server regardless of whether they're in the target list or no, and I don't want to keep trying a full deployment

That’s basically everything I’d tried so far with this affected pc. I’m still getting the previous ‘errors have occured’ on other stations as well. This was a perfectly working system last when we last ran the Spring updates so I’m not sure why it’s become so problematic As for this specific pc I ran the locally downloaded package manually and copied over the connect.ini file and it now works, so it’s not like the package has any issues or corruption. This isn’t really a good solution for the rest though!

We're still having issues - fresh client install (traces deleted)m and re-downloaded to the server several times. Runs through and shows the same 'one or more errors occurred ' but the error seems to be a different one now: Sims.Solus3.Agent.PackageDeployer.PackageException: Failed to validate signature. ---> System.Security.SecurityException: Failed to validate signature. This error was previously fixed by a full delete of the client but that isn't working now

Yup just seen this update has been replaced in SCCM so will test the deployment of this one instead!

I'm seeing some weird results as well, I deployed the registry to a couple of groups and in one case it worked after three reboots and the other worked a day later without any intervention (and no reboots at all) and they're the same hardware and os level I think I'll just deploy the Aug CU after the registry fix has been deployed network wide and see which ones fail