gjefferies

Yes its a minimum of 16 core licences per CPU and then you can buy single core licences to make up what is needed. Some of our hosts only have 8 cores, so it has got very expensive for us. We renewed just before the broadcom takeover but were forced down the vsphere plus subscription route. Worth looking at this page, there is a powershell script which works out how many licences you need https://williamlam.com/2024/02/updated-inventory-calculator-scripts-for-counting-cores-tibs-for-vmware-cloud-foundation-vcf-and-vmware-vsphere-foundation-vvf.html

Have a look in event viewer there are specific Hyper-v event logs if you drill down and these normally tell you why a VM won't start. https://blogs.msdn.microsoft.com/virtual_pc_guy/2009/02/03/looking-at-the-hyper-v-event-log/

SCCM using the built in Windows Defender install on Windows 10 and 2016, so you don't need to install the endpoint client. https://technet.microsoft.com/en-us/library/hh508770.aspx?f=255&MSPPError=-2147217396 Cheers Gareth

Seem to have resolved the issue by doing the following 1. Add a MIME-Type for '.esd application/octet-stream' in IIS on the WSUS server. 2. Made the following changes in the IIS Application Pool for the WSUS Page: Queue Length: 25000 from 10000 Limit Interval (minutes): 15 from 5 "Service Unavailable" Response: TcpLevel from HttpLevel Private Memory Limit (KB): 0 from 18342456 3. edit the web.config ( C:\Program Files\Update Services\WebServices\ClientWebService\web.config ) for WSUS Stop the IIS and do following changes: replace with One of my test 2016 servers started to communicate with the WSUS Server and downloaded patches, the other didn't, but after disabling IPv6 this one also did too. They still report as Windows 10 though. Thanks Gareth

Thanks for your reply, Yes the WSUS server is up to date, regarding patches etc. I've come across other people with the issue regarding wsus not detect the o/s version, but the threads end without a fix. Cheers Gareth

Hi, I am currently testing Server 2016 and so far it is going well, but I have a problem with the 2016 server getting any updates from our WSUS server running on a 2012 R2 box. The 2016 server appears in the All computers in WSUS, but appears as o/s version Windows 10 and never reports in (Status Not yet reported in) When I check from updates from the 2016 server it returns error 0x8024401c I've manually installed the latest cumulative update on 2016 to see if that helped and it made no difference. I set a Windows 10 1703 computer to get updates from the WSUS Server and it reports and pulls down updates fine. Anyone else experience this problem and found a fix? Thanks Gareth

Hi, Your LEA will probably create a boundary in SCCM for your network and your local MDT server would probably become a Distribution point (DP) and PXE Point for your network, Storing things like apps, windows images, updates etc. Your WSUS server will probably will become redundant and you will select the updates to deploy from the sccm console (From their WSUS/Software Update server) and these will be packaged up on your local DP. The Microsoft Virtual Academy is a good source for free SCCM training, i've also used CBT Nuggets. Cheers Gareth

At the college I taught at they had a Dreamspark Premium account , and you can created keys for lab use. I have also used the evaluation copies too. Thanks Gareth

If your right click on Documents etc and select properties is it showing the network location or still local? Do you get the same delay if you browse to the UNC path?

Yes, I had a similar issue, I set the email address attribute for each of the users in Active Directory and the Cloud accounts changed to Sync'd with Active Directory. Thanks Gareth

Cool that works, many thanks Gareth

Hi, No I haven't made any progress on these, I have to get them out the door, so its currently a known issue.... Thanks Gareth

The additional services can be found in the registry at HKey_local_machine\system\CurrentControlSet\Services\SensorFusion and possibly SensorServiceDriver I've added them into a new built tablet and rebooted but it doesn't make any difference. Cheers Gareth

Yeah I have seen that website, Manually changing the screen works... So I am gonna come back to it... The only thing I can found is there is an additional service on the out of the box ones....

Hi, We have bought several linx 10 tablets and I have put our Windows 8.1 Enterprise build on, so I can join them to the domain etc Everything works great, execpt for the auto-rotation of the screen. It didn't work until I manually added in the Kionix Sensor Fusion device and Simple Device Orientation Sensor. Auto-rotation works i.e. the screen changes, but it seems to be 90 degrees out. i.e. When the tablet is landscape the screen is portrait etc. Anyone know how to resolve this? The ones out of the box work as expected. Thanks Gareth