Explorer

Make sure you're keeping hydrated, I understand hunger can be a sign of dehydration.

So far no across three LA's. Surely they're mistaken?

Definitely not hate speech I'd say. I haven't come across this IRL anyway.

Oh for goodness sake. Santa Claus isn't directly pushing religion anyway. I'm not religious and correct me if I'm wrong but does Santa appear in the Bible at all because I'm fairly sure he doesn't? I wonder if VLC still changes its icon nearer Christmas.

Having some strange problems with Windows Updates on SCCM 1806. This is a recently installed system so it's something which has been present since setting this up. Whenever I click check for updates from a client PC I am getting the error 0x80244022.I've taken the following steps so far: Check that WsusPool is running - it is. Increased the maximum memory for the WsusPool Run the server cleanup wizard from the WSUS console Local group policy shows the correct WSUS server Doesn't appear to be a DNS issue as I can see the SCCM server from the client and the client from the SCCM server Here is the same error in the WUAHandler log:

I have it set so there is just an apps list and staff can pin their own apps if they want to. Students have a selection of frequently used apps pinned which they can't change.

That might explain why my Server 2016 KMS host is refusing to install our 2019 KMS key full stop. Getting 0xC004F015 which would indicate it's the wrong type of key and the 2016 one stays in situ. It would be good if Microsoft fix this soon as I really wanted to start getting 2019 LTSC out there especially now that SCCM is fully implemented.

Has anyone sussed out how the licensing works for Windows Server 2016. I'm finding different information on different websites. If I look under Relationship Summary I have the following information down for Server: [TABLE=class: GridViewBorderStyle] [TR=class: GridViewRowStyle] [TD=class: gridItemText GridViewFirstColumn]Servers [/TD] [TD=class: gridItemText]Windows Server - Standard[/TD] [TD=class: gridItemText]2012 R2[/TD] [TD=class: gridItemText, align: center]10[/TD] [TD=class: gridItemText, align: center][/TD] [/TR] [TR=class: GridViewAlternatingRowStyle] [TD=class: gridItemText GridViewFirstColumn]Servers [/TD] [TD=class: gridItemText]Windows Server CAL[/TD] [TD=class: gridItemText]2016[/TD] [TD=class: gridItemText, align: center]100 [/TD] [TD=class: gridItemText, align: center][/TD] [/TR] [/TABLE] Obviously I can ascertain from that, that we have 10 Server 2012 R2 licenses to use but the CALS are 2016. I'm assuming this flat out means that we cannot run 2016 and must use 2012 R2. But the strange thing is that in Downloads & Keys we have been given a KMS and MAC key for 2016. I've not long taken over the network manager role and I just want to make sure we're licensing properly. I'm going to be replacing some of our servers and would like to use 2016 but obviously I don't want to run it if we're not licensed to do so.

I don't know of any TX's called Telford. Are you talking about The Wreckin?

That never worked but something really interesting... I opened CMD & used sconfig to update the server & strangely after 2 days of trying to update it the usual way, it actually worked through the command line.

If only ours would do the same... I can't even get ours to update. It says Downloading Updates, a list of updates shows & then they all disappear, I've even left it on overnight & it's still stuck at 0%. Really weird, proxy settings are correct as I can browse the web, windows 10 has no problem downloading updates here so it's not any firewall settings or anything like that. Has anyone else experienced this? I wanted to get at lest one 2016 Domain Controller up & running by half term but not if I can't update it. If I can get the initial batch of updates done successfully I'll configure WSUS for 2016 updates but I just want to get the initial thing updated first before doing anything further or introducing any other 2016 servers.

Good info, useful.

Definitely time to move to Windows 10. No point using outdated OS's if the newer ones are available for use.

It's easier to just restrict access to it & change defaults than removing it. It'll just be reinstalled during the next feature update.

Which version are you installing?

Probably the best tool for the job. Why?

1511 Messed up every machine we tested it on. Same issue, the start menu stopped working. It's just an in place upgrade, completely different version of Windows, really stupid way of doing it - It makes sense on personal machines but maybe not so frequent. After testing Windows 10 on some classroom PCs with this, I've decided that we'll now be using LTSB for full deployment.

If you have had Windows 10 installed & activated it, just use the media creation tool & clean reinstall, it'll activate.

Hey. Been reading the forums for years and finally decided to sign up.