mrwoberts

Thank you for clearing that up. Why on earth couldn't Capita have just put an entry in the 'Fixes in this Release' document and we probably wouldn't be having this conversation. I'm also a little confused about 25058, since I don't see that in Solus - meaning that it hasn't been released to us by SSU. Anyone from Capita care to give us an explanation about the mess that has unfolded from the CTF import mess-up.

On the server that is reporting this error, what do you get when you run this command from a cmd prompt fsutil usn queryJournal

Here are a couple of Edugeek threads that may help... http://www.edugeek.net/forums/windows-server-2016/207993-windows-server-2016-stuck-restarting.html#post1781538 http://www.edugeek.net/forums/windows-server-2016/204222-windows-server-2016-slow-update.html http://www.edugeek.net/forums/windows-server-2012/208306-upgrading-server-2016-a.html EDIT: Here's an MS link in case you'd like to do an in-place upgrade... https://www.microsoft.com/upgradecenter/scenario/WS2008R2-on-prem-to-WS2019

On a separate note, I personally would not be migrating to 2016 at this stage - 2019 at least has the major benefit of an improved patch system, whereas 2016 can have problems applying patches - hit and miss for some.

Glad you asked this. I have seen the SIMS Summer upgrade in our Solus, but not Patch 25040 - despite our SSU suggesting we apply it (they release the patches to us). The blurb from them is, "Patch 25058 inserts System Check ID 100 and can be found in SIMS - Tools/System Diagnostics/Database Diagnostics" Looking at the details of the patch it suggests it is a Spring related patch, but as Esteban hints above, it is not included in the Summer release. I am applying the patch this evening, then upgrading to the Summer release next week. If I were making your decision I would backup the DB and apply the patch, then run the database diagnostics.

You're right, it suggests 2012 R2 can go directly directly to 2019, but the standard 2012 has to go via 2016. https://www.microsoft.com/upgradecenter/scenario/WS2012-on-prem-to-WS2019 https://www.microsoft.com/upgradecenter/scenario/WS2012R2-on-prem-to-WS2019

https://www.microsoft.com/upgradecenter/scenario/WS2012-on-prem-to-WS2019 Seems to suggest a multi-step upgrade path. Is that absolutely essential or are folks just whacking in the 2019 ISO and setting off from there?? EDIT: Apologies, I posted the wrong link (2008R2 to 2019)... Corrected link (2012 to 2019)

In my experience, once teachers have used a touchscreen they never want to go back - teach in a classroom that doesn't have one. Looking at some of those issues, I'd say the angle thing is probably quite common across the three different brands I've installed, but it's never been a show stopper. I do think the SMART screens are not as amazing as I had hoped they would be, and I agree there can be a slight delay sometimes. Double clicking on the SMART screen is painful - hit and miss as to whether it worked, so teachers tap 50 times to be sure (exaggeration) The screen I've kind of settled on for now is the BenQ RM6501K. Not premium, but they just do the job really well. Plus the sound bar below the screen is way better than the SMART screen sound. Edit: Forgot to add that the SMART screens are also very very fussy about things being pinned around the bezel of the screen. Lost count of how many times I've been called to a classroom to investigate 'random' touch interference, only to find the teacher had pinned phonics cards or other such stuff in the way of the bezel sensors. This shouldn't really be done on any IR based touchscreen, but I just think the SMART screens are more fussy about it.

Whaaaaaaaaaat! Come on bruv, spill the beans. How did you do it?

Had a problem myself recently with proxy settings. My problem was that even though they were removed, unless you use IE/Edge, or unless I actually went into the Control Panel - Internet Settings, the new settings weren't being refreshed. I had to create a script to force a refresh, since we use Chrome. if you're still having a problem it might be worth going into the control panel - internet settings and just verifying they're removed. One separate problem I had was on the server. For some bizarre reason, the proxy settings of the SYSTEM user seemed to be trumping the settings of the admin user! I basically searched the entire registry for the name of our old proxy and it found a few results.

Another option, although not the best way, but it should work.. Use this tool RegConvert to convert your .REG file into a .BAT or .VBS to which you can then run at startup... Alternatively, this command will import the registry file reg import RegExportFile.REG - run it from a batch script...

I really enjoy seeing solutions like this, it's how I learn :-) Just a thought... How does does this respond if SIMS was open, or even opened during the update? - A suggestion for the above scenario could be to rename the pulsar file prior to the update? - Potentially check for a running pulsar process before the update?? and kill the process if appropriate??

Was recently pointed to a helpful Microsoft page that lists Known Issues for their Windows 10 and Server releases https://docs.microsoft.com/en-gb/windows/release-information/status-windows-10-1809-and-windows-server-2019 Useful to see Known Issues and Resolved Issues, including the patch that issue was fixed in.

That's exactly what I was thinking Thanks for your help, I'll update you with my progress, although I may not attempt this remedy until I've recovered some courage :-)

Just a further question. What powershell command is recommended to force an AD/Azure sync?

Just had a flashback from earlier today! Let me just check I've understood you. On the ADMIN domain - delete the user (redundant user, but seems to be the anchor for the real email account) - Wait for AD sync - then Powershell, like my life depends on it, making sure that the Immutableid is photon torpedoed back to the 80s On the CURRICULUM domain - edit the user to add their email, proxyaddress, and point login domain to the school email address - Wait for AD sync - Update my will to leave all my worldly possessions to my pet turtle Felix Does that sound right?

Managed to nearly give myself a heart attack today. Background School has two AD domains (admin.school and curriculum.school) and uses AD Connect to sync passwords to O365 Nearly all users are on the curriculum domain, with just the office staff still on the old admin domain, which I'm trying hard to get rid of. Over the Easter break I rebuilt the office staff PCs and joined them with fresh accounts to the curriculum.school domain. Pretty much everything has gone as planned, with the exception of the O365 AD Sync. Currently the AD Sync tool is tuned in to both domains and was happily syncing user passwords to the cloud. When I created the new users on the curriculum domain (you can see where this is going), the Sync tool had a fit, quite rightly, saying that there are duplicate email addresses (paraphrasing). So, I thought to myself, I'll just remove the references to the email accounts on the admin domain - removed user email address, proxyaddress, and changed user logon 'domain' to be the plain @admin.school domain (was previously the email domain). This unleashed a world of pain! It created duplicate new users, renamed the old users (the original account where all their emails are) and promptly rejected any emails to the old account because they were now apparently destined for this new account. After hours of panicking and frantically trying to undo this folly, the sync is now 'happy' pointing back to the redundant admin domain users, and the real user can now access their email as before, but clearly this setup is not helpful going forward. Problem How do I dig myself out of this hole and do this user sync-migration properly? I would like to maintain the link (sync) for these handful of users that I've already moved over to the curriculum domain? Otherwise I'm of a mind to totally disable the AD Connect and start from fresh (if that's even a wise idea, I honestly don't know) Forgive me if my description of is not clear, my brain is totally fried and my nerves are shot to pieces If you're going to reply to say that this is a 5 second fix, I truly do want to hear that, but at least give me some time before you lay that one on me

So if we focus then on the changes that [were] made before the reboot Were Windows updates applied? Have any non-SIMS related changes been made to the server before this problem occurred - between this recent reboot and the previous reboot (possibly last month when if you applied Feb/March updates)

When you say you're trying to RDP from desktop to server, are you using the Dameware software, or the Microsoft RDC client? I don't know anything about the Dameware software, but could we perhaps take that out of the equation for the minute - temporarily remove it from the SIMS server ....

2nd and 3rd command from the SIMS server

Actually, this looks like a simpler way to test a remote connection Powershell Test-NetConnection -ComputerName "fqdn_of_your_sims_server" -Port 3389

Looks good. Can you just confirm whether a Windows 10 PC is able to RDP into that server? Also, can you see if the 3389 connection is 'connectable', using this Powershell script (.PS1) from an affected client PC $Connection = New-Object Net.Sockets.TcpClient try { $Connection.Connect("localhost",3389) if ($Connection.Connected) { $Response = "Open" $Connection.Close() } } catch [system.Management.Automation.MethodInvocationException] { $Response = "Closed / Filtered" } Write-Host $Response $Connection = $null And can you post the output of these two Powershell commands Get-ItemProperty 'HKLM:SYSTEM\CurrentControlSet\Control\Terminal Server' and Get-ItemProperty 'HKLM:SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp' | Select-Object PortNumber

You need to run the (native) 64 bit version of Powershell, not the Powershell (x86).

Can a Windows 10 client connect to the server? From the affected server, via the VM host connection, what results do you get when you issue this command (from the cmd prompt). netstat -a | find "3389" EDIT: Also, just double check the network on the affected server is domain, assuming it's joined to your domain, otherwise it should be private Powershell Get-NetConnectionProfile

Not blank, but points to a basic sims.ini, which isn't redirected, but is added to the client sims.ini upon installation of SIMS. Here's mine [setup] SIMSDirectory=\\MY_SERVER.admin.school\simshare\SIMS SIMSSetupsDirectory=\\MY_SERVER.admin.school\simshare\SIMS\Setups Folder=SIMS Applications