Search the Community

We have NPS configured to send accounting requests to our Sophos XGS for SSO. Recently NPS seems to have stopped sending the accounting data to the XGS, I've ran a packet capture and can see nothing is being forwarded to the XGS. No config changes were made prior to this so not sure why this is happening. I've recreated all policies and re-installed the NPS role but nothing seems to be resolving the issue Has anyone else seen this? Any help is greatly appreciated

Hi All Just wanted to ask everyone's opinion on what you think is best for an Primary school environment VMware or Hyper V? Thanks

Hello everyone, I have recently started to provide support to a small secondary school. They have a Server 2019 VM running on ESX and it's just started to Blue Screen. The VM is running the school's RD Gateway. The BSODs are either SYSTEM_SERVICE_EXCEPTION or ATTEMPTED_WRITE_TO_READONLY_MEMORY and it also shows NTFS.sys. Has anyone else come across this before and if so, how did you go about resolving it? Many thanks in advance.

I have server 2019 members just fine the domain controllers x3 are 2012r2 the forest and domain are functional 2008r2. I think I can just go for 2019 in place upgrade but people are mumbling about SMB1.0 needing to be enabled. Do I raise the functional level to 2012r2 (can i) just to tickle some memories for those who did this 5 years ago Once I get them to 2019 I can raise again to functional 2016? cheers

A local charity school has a free educational Azure account from Microsoft and Windows server 2016 on-premise. There is not any important information or policy to export before formatting the on-premise server. I upgraded the drives to SSD then installed Windows server 2019. I promoted the server to DC and enabled the Hyper-V. They want to disable USB, configure background image, create OU for each class....etc I created a new subnet for the server and one computer to test everything before joining the rest of computers to the new domain. I managed to disable the USB via group policy then added the provided image to be used as a background image. Those two policies are successfully applied but I the background image disappeared when I changed the DNS. I revert the DNS to the domain one but the configured image is still not showing. I deleted the user profile from the registry and it is working now. I am wondering if this is a normal behavior or I misconfigured the background image on the server side. Shall I configure the background image on the on-prem and on Azure or just on on-prem. Please advise.

Good morning, I have a print server running on server 2019. The print spooler is not stable. It keeps restarting, the only way i have gotten it working is to set Subsequent Failures to restart the service. The service will restart between 3-5 minutes. during this time one can print no issues. I think its a corrupted or outdated print driver. The drivers that are in use range from 2018 - 2006. So yea i would say their are some really old drivers on their. I know the print spooler is crashing but i cannot find what exactly the cause it. the event viewer has not been much help i have posted the errors i see below. Is their a process to track down the driver? Everything i read online just said to update all the drivers but nothing about tracking the down the exact one that is causing it. Aside from having Techs do a Clean up on the server, Update Currently used drivers, Remove unused/old Drivers and delete old queues. If that does not work the only other thing i can thing od is to build a new server and install everything fresh and manually move printers over. Their are 78 drivers Their are 81 Printers Thoughts?? I see the below but those files don't exist, which is why i says "The print spooler failed to delete the file" The print spooler failed to delete the file C:\Windows\system32\spool\DRIVERS\x64\PCC\prnms003.inf_amd64_9bf7e0c26ba91f8b.cab, error code 0x2. See the event user data for context information. The print spooler failed to delete the file C:\Windows\system32\spool\DRIVERS\x64\PCC\prnms002.inf_amd64_4d944e2fb3bcc43c.cab, error code 0x2. See the event user data for context information. The print spooler failed to delete the file C:\Windows\system32\spool\DRIVERS\x64\PCC\ntprint.inf_amd64_18b0d38ddfaee729.cab, error code 0x2. See the event user data for context information. The print spooler failed to delete the file C:\Windows\system32\spool\DRIVERS\W32X86\PCC\prnms003.inf_x86_dd2fd5b05c3d8604.cab, error code 0x2. See the event user data for context information. The print spooler failed to delete the file C:\Windows\system32\spool\DRIVERS\W32X86\PCC\ntprint.inf_x86_18b0d38ddfaee729.cab, error code 0x2. See the event user data for context information. I see this from time to time but it does not tell what the print driver is.... Document failed to print and was deleted because of corruption in the spooled file. The associated driver is: . Try printing the document again. Not much i could find out but about the below The print spooler failed to reopen an existing printer connection because it could not read the configuration information from the registry key S-1-5-21-636618257-2613738635-33974680-1377919\Printers\Connections. The print spooler could not open the registry key. This can occur if the registry key is corrupt or missing, or if the registry recently became unavailable. I see this every 3-5 minutes... The Print Spooler service terminated unexpectedly. It has done this 12 time(s). The following corrective action will be taken in 5000 milliseconds: Restart the service. And yes i know about Cleaning out C:\Windows\System32\spool\PRINTERS but this is the not the case as it will stop while that is empty/ no jobs coming in. Thanks

Morning all Trying to set up a few printers to deploy through group policy and ran into a problem. The printers will not deploy for love nor money, I've sorted point & print etc Ran through gpresult and noticed it's deploying from the secondary DC, which is fine however, when checking the policy settings on the 2ndary, the 'deployed printers' tab just literally isn't there. I'm wondering if it could be a sysvol replication issue, though there is nothing in the event logs and everything else seems to be fine. Main DC is server 19, secondary server 2012r2 Really has me stumped, just wondered if anyone has ran into similar issues or has any ideas? Thanks in advance.

Currently running 2012 on a single physical server with a number of VMs that has had most, if not all, of it's disks replaced over the years. More disks getting dodgy, so going to get a new (to us) box. Lots of questions (in bold) to follow! Basically, going to do a similar setup to the existing one: 2 SSDs RAID 1 to run the OS and possibly the VEEAM VM on with the other disks in RAID 5 for everything else. Does this make sense? Next up: 2022 or 2019? Time at that site is VERY limited, so I was considering cheating and just copying the existing VMs as VEEAM replicas in case the old machine dies - that way everything should be running from Day One. Feasible? Finally, I was planning on setting up 2022 (or 2019) "fresh" VMs and moving data and roles across at my leisure. Eventually there will be the same sort of setup but with all the servers on 2022 apart from probably the SIMS server that will remain as a replica (no longer use SIMS) and plan to remove it completely after 5 years. Or should the SIMS data be retained longer? Does the slow replacement idea sound viable? Once everything is hunky dory, the old server would have it's dodgy disks removed and used for offsite backup. Expect a lot more questions in September!

Hi We've just had a new server installed and domain built from scratch. Since we've had everything up and running again we can't conect to any external (outgoing) remote desktops connections. We keep getting the folowing error: The computer name and domain for the remote computer is correct. We're with exa-networks for firewall and filtering and they're adamant it's not them. All internal remote connections are working well and we can remote in to the site via offsite/mobile internet. We can also make external (outgoing) remote conections using a domain device to and mobile internet. We've also tried using domain admin account to establish a remote access connection to offisite server with not luck. Any thoughts on which step in the process we've missed will be greatfully recieved. Thanks in advance.

I have installed Windows Server 2019 Standard Eval with Desktop experience. The server is in a location where I cannot see it but I can hear it. My current server is W2012 R2. I have no issues with that server. For the 2019 server the error, exclamation, notify and other sounds do not work. Recycle Bin, device connect/disconnect/fail work. When I test each sound in the control panel they play fine. The Audio and Audio Endpoint Builder services are running. I can play mp3, mkv, avi, mp4 etc and audio works fine. I rely on the sounds because I can tell from the sounds what is going on since I can't see the server. Are specific sounds disabled in this OS or is there something wrong? When I install any OS I ALWAYS have the internet disconnected. As a result, in 2019 (but not on 2012 R2), Server manager can't get an IP address and uses the 169.254 address. When I later install the NIC drivers and connect the internet everything works, but I cannot get rid of the 169.254 address. It shows only in server manager. Ipconfig /all shows only the real adapters. How can I get rid of the redundant 169.254 address? The server is used for WSUS, IIS, ColdFusion, Macrium Reflect, MySQL and file storage.

We've recently issued our staff with laptops which have always on VPN configured. However, they randomly fail to connect to the VPN Server. I've been remoting onto them, removing the profile and re-adding which seems to sort the issue. This just happened on mine and I was able to manually restart the connection using rasdial so it's not a server/connectivity issue. Has anyone else experienced this? If so how did you resolve it? We're running Windows 10 Education 1909 and the VPN Server is Server 2019 Standard Any help is greatly appreciated

Hi, Just looking to deploy server 2019 RDS via the add roles and features. I have created a new Server 2019 VM. This is not on a domain controller. Has anyone else had any issues installing RDS? The firewall is currently disabled. I am getting an error in the event viewer: update remote-desktop-services of package remote desktop services role failed to be turned on server 2019 Thanks in advance

Hi, So I have managed to setup RDS via quick start server 2019. I have remote apps setup and working well. I have been experimenting with publishing a full desktop but because I used quick start I have added a reg entry to add the remote desktop icon to the remoteapps page. Just a quick question can more than one user login to this remote desktop full at one time? Thanks again

Link: Think your VMware snapshots are all good? Guess again if you're on Windows Server 2019 [The Register]

Hey, thank you in advance for any comments, tips etc. Facing a peculiar issue on two file servers, it was originally just one. However, the second one has started doing the same thing, whereby file access for reading/writing is very slow, and disk active time shows 100% in resource monitor. It feels like a hardware issue; however, the two file servers are at different schools, run on similar but different hardware, and both run Windows Server 2019 Std full patched. The hardware the two VMs run on is similar, HPE Servers; one has an HPE MSA 1050 with 10Gb iSCSI connections (2 each in multipath active active, so 20Gb in total), and the other has 12Gb SAS (2 each in multipath active active so 24Gb in total) with the same HPE MSA 1050. The MSA 1050s themselves each have 24 x 1.2Tb 10k SAS disks in a RAID10 volume. The HV hosts run 2019 Datacenter and are also fully patched. Ther other virtual machines on the failover cluster as well as other large file server arent affected at all. Things we have tried. Turning off Sophos Uninstalling Sophos Turning off Windows Defender and Real-time scanning Deduped the Data to be none dedupe (one server is still deduped) Re-Installed the OS Recreated the VHDX and restored from backup all the data Drivers on the Hyper-V hosts for storage controllers Setup hyper-v replication to a spare none SAN-based server and replicated the server to this, then swapped the servers round live so the primary one was running from the spare server; this seemed to solve the issue strangely, so is this a hardware issue? I moved it back to the failover cluster, and it appeared to be fine but then started with the active time again shortly after. Upgraded Veeam to the latest version as though it might be CBT causing the issue. However, I haven't yet turned off CBT as I can't find a guide on how to achieve this completely. Screenshot of the error with sensitive data covered over. Any pointers would be greatly appreciated. Thanks

Hello, i am after a bit of advice as have been struggling with this issue ever since the summer: Previous to the summer all of our servers were running on Vmware ESXI 6.5 on a HPE ProLiant DL380 Gen 9. During the summer we migrated to Hyper V 2019 on Intel Server System R2308WFTZS. The migration went smooth except for that all of the migrated Vms have a write speed of around 20mb and a read speed of 800mb+.. This is causing issues with staff/student file shares etc. All the VMs were converted to a Gen 1 hyper V VM. The host speeds are 800mb+ read and write. The intels are connected by 10gb fibre and have NVME drives for storage. I have tried the following with no fix: 1) Convert the whole Gen 1 VM to Gen 2 VM - still slow write 2) Convert the HDD from Gen 1 to Gen 2 and make a new Gen 2 VM from scratch and attach the HDD - - still slow write 3) Install the latest guest VM drivers - still slow write 4) Restore the server from a backup - still slow write If i run a disk speed test on the VMs the read/write is normal so i am assuming somewhere down the line it is the link between the host an the VM which is causing the issue. If i make a brand new Gen 2 server from scratch the speeds are fine. The network driver on the VMs is 2006 which seems a bit odd.. Basically after any advice from anyone who has any experiance with HyperV as most of my knowledge was with VMware. Thankyou.