Sheridan

No I'm still seeing the error in dcdiag I'm wondering whether to add the DNS service onto the Papercut server to see if it helps - we have multiple DNS servers so another won't hurt

Thread resurrection here, but has anyone managed to do this with a smoothwall? I've tried blocking vimeo.com and allowing the previously shown list to only allow embedded videos, but it doesn't work for sites with embedded videos like this: https://classroom.thenational.academy/subjects-by-year/reception/subjects/foundation/ Unless you have full access to vimeo you just get a blank screen? So with smoothwall it looks like you have full access to vimeo, or you unblock each video using its ID but there's too many to do this manually!

As soon as I add the delegation NS record the error appears, even thought the name server in the NS record resolves OK Very odd. At the moment I’ve only got the A record and NS record and the dcdiag error appears.

It must the NS entry - I edited the file to exclude all of the subnets, so it only had the A and NS and PTR records for the server created - Running dcdiag shows the same error. If I delete the NS entry for the zone it clears the error. I a bit baffled as it seems to be correct to me

We had a simple single server RDS 2019 setup before the pandemic (albeit a physical server it was a good 2 CPU, 80GB model) and it's been handling up to 50 concurrent sessions with no problems. As a precaution I added another spare physical server (only single CPU/24GB Ram) and load balanced it 70/30 and its been great. I was expecting complaints with 150 staff at home, but its never been more than 50 concurrent sessions thanks partly to a bigger usage of Google Classroom, which has shot right up When the situation settles I will probably revert back to the single server, I was pleasantly surprised how well it coped.

Yeah I put them in their script generator like that, 192.168.0.1/255.255.255.0 etc and so on I’ve removed the NS record only and it cleared the Dcdiag error but I’ve yet to check if the mobility server is still working on the iPads

This is the generated script - we have a core subnet (where the papercut server is) 8 other subnets where the clients are. It seems to work OK papercutdns.txt Running dcdiag on any DC shows this at the DNS stage dnserror.txt

When the mobility service is off or removed the ipads don't see the printer(s). I use the DNS method as mDNS only works across a single subnet - this is similar to the issues we have try to use airserver across subnets. Like I say the printing side is working well - but it bugs me to see dcdiag errors even when I know they don't affect the network performance!

Yes - those subnets relate to the where the clients and printers are both located We're using this for iOS devices (ipads) and they work - the Papercut printer appears and prints with authentication so its not like it doesn't work, just seems to be something off with the DNS config

I used their generated script and it seemed to work after I entered our domain name, server IP and subnets that the printers are on It created: An A record for mobility-print-host pointing to our Papercut server IP An NS record for pc-printer-discovery with the name server entry of mobility-print-host.domain.org Then in each of our subnets it created two PTR records in the reverse lookup zones: i.e something like: 192.168.1.0._udp._dns-sd.b with an entry of 0.1.168.192.pc-printer-discovery. 192.168.1.0._udp._dns-sd.b with an entry of 0.1.168.192.pc-printer-discovery. The only thing I can see that doesn't look 'right' to me is in the entries above, the FQDN is showing as ???.in-addr.arpa The printing works OK - its just the DC's that generate the error

I've added the Papercut Mobility server to allow our mobile devices to discover the print queues, which seems to be working fine. However the DCs now all show a DNS error in dcdiag - relating to the Papercut DNS entries I created (using their auto generated script) TEST: Delegations (Del) Error: DNS server: mobility-print-host.domain. IP:xx.xx.xx.x [broken delegated domain pc-printer-discovery.domain.] Our DNS is working fine - if I deleted all the Papercut entries it gets rid of the error. Have I missed something, or is this normal behaviour when using the DNS discovery method for papercut?

Its DFSR - and its seems like it is the duplicate Domain Admins issue. I created a batch file to remove and add the domain admins group from every single policy folder. Running this on all the DCs and letting replication take place and its all showing up ok! Running it on one DC didn't work, the 'hidden' entry mustn't replicate properly

No, no file screens on the new server - I’ve barely set it up yet I found an old thread saying that’s the acls sometimes have duplicate entries for the Domain Admins group, and when I checked it did seem to have 2. This was relating to 2008 server but I set this domain up back in the Server 2000 days! When I deleted the acl and recreated it that one gpo then disappeared from the list. So I’m not sure why but it seems my gpos may have odd entries in the permissions list, and I’ll have to find a way to check all 190 of them!

I've added a new 2019 server to our domain as a DC - currently its got 2012/2016 DCs in 2012 Domain level, and my intention is to migrate the 2012's to 2019 All is working as expected, no dcdiag errors, SYSVOL is populated etc - but when I run the GPMC infrastructure test it shows replication in progress (ACLs) for the new server - for every single GPO! I've checked everything I can but this error state will not go - repadmin shows no errors and replication is up to date. Add a new policy and it replicates to the new server! So I'm about the ditch using server 2019 for now, as I'm not convinced its working correctly, and MS offer no information for this other than the usual checks I've already done - which all show up OK! Has anyone else seen this behaviour with 2019?

We're running RDS RemoteApps on Server 2019 and we have an odd issue, that only seems to affect one user so far (although I bet there's more we don't know of) When running a remote desktop they try and attach a local file to their GSuite email (in Chrome) but it shows the error 'Cannot access \\server\path\...' The network path was not found' The path is valid and works fine for other users remotely, and the affected user when in school. They also cannot drag and drop files to an email in Chrome either, as they see the black circle as if its disabled, but again works when in school The odd thing is, I've tested with several other identical accounts (i.e staff and not admin) and they both work fine! I've deleted the affected users profile on the RDS server but it hasn't helped. No roaming profiles either, so this is puzzling me.

Its a blo--dy nuisance. I've just tested on 2 PCs side by side. Both identical in every sense - one works, one fails. Disconnected and reconnected the network cable on the working one, and now it fails as well. What sort of rubbish software are MS chucking out when Office fails like this, despite having a connection!

We get the same problem whether that is checked or unchecked (its unchecked by our GPP and has been for some time for another issue) This is a really annoying problem, Office simply won't use online clipart because this crappy network awareness service doesn't work properly! But in a room of 20 identical PCs it will work on some, but not others Even if I disable the ncsi probe (with GPO or registry settings) I still get the exclamation mark showing, which in turn breaks the Office clipart, despite everything resolving and internet is accessible.

Well it looks like the old Windows 7 bug where it says there is no internet connection, even though there is. I've disabled the nlasvc probe and reset/rebooted but random machines (identical hardware) will show the exclamation mark. When thats showing then Office doesn't even attempt to connect and generates the error. Looks like we're stuck with this bug for a long time yet.

We've had our meeting and effectively are open as normal on monday - with only the keyworkers/vulnerable kids in. All staff in though which is odd, although I suspect its all subject to change I also have parents who have illnesses that make them vulnerable, so will have to just phone them for the time being. My daughter was due to sit her GCSEs this year, she's devastated :-( and I can't do anything to help that

Spot on, I knew I was barking up the wrong tree, I was trying to do this in O365 Admin rather than Azue. D'oh!

I'm more of a GSuite admin, so bear with me for a noob O365 question! Despite using GSuite we also want students to be able to use the Office 365 for students download of Office 2019 that comes with our OVS-EES Agreement - therefore I've setup an AD synch (Azure AD connect) of their accounts to our O365 domain (which isn't really used) The users all appear now, but as unlicenses - and I can't see a way to assign them to the correct license, short of doing it manually for each student, which will take forever! I know I must be going around this the wrong way, so is there a way to import our student AD accounts and assign them to the Office 365 for Students license in one go?

Its the same for online video - but it comes up with the error immediately - and doesn't seem to have any errors on the smoothwall I guess an MS update has borked this, yet again.

Our Office 2016 'Insert online pictures' has suddenly stopped working for all the applications in the suite. When a user clicks it they immediately see a message: "You need an internet connection to insert online pictures. While you are offline, you can insert pictures from your computer." I'm assuming its a filtering issue, but we haven't changed anything on our Smoothwall, have MS changed the URLS for this? I can't see anything blocked in our smoothwall

They all use the Toshiba Universal 2 driver which I updated this week although it hasn’t stopped the issue Thing is, nothing has changed, the copier, the server, the driver and the client os are the same they were 1 year ago, and the problem only really surfaced for us about 1-2 weeks ago.

Its a total PITA as the affected schools are blaming us, and the leased copier companies are blaming us. I don't really have a solution as Microsoft seemed to have completely ballsed up printing in Windows 10/Server 2016/19 since day one.