3s-gtech

It really depends - one server has dynamic with a lower limit of 1GB, all the way up to 16GB for a web/DB server (that gets pretty loaded up at times). No SIMS so nothing that big needed. I just spec them based on usage and feedback.

Is your filtering getting in the way of Jamf? I’ve not tried with M4 models but got some M2s on it, and it works pretty well and consistently.

Don’t do the other two as RAID 0 though!

My HD6950 would like a word.

This is very welcome, if only to boost competition. The big two in the GPU space have been rather anti-competitive for the last five years.

Your boot image is broked. Drivers, something. Can you default it?

Can older devices boot to the TS?

I’m finding cheapo Amazon DP to DVI cables are extremely variable. Out of 90 odd I ordered I’ve had three dead out of ten tested - who’d have thought that thrown-together junk would be so unreliable 😅 Another cable from the box picked, and they work okay.

In your cases, I very much doubt it's the monitors themselves. It may be the impedance of long cable runs, the issue being that over time this may actually damage the display outputs so they subsequently don't work on shorter cables. My experience was just strangely similar. I like the AMD ones otherwise - I've taken one as my own desktop and it's a decent all-rounder. Mine has working ports though!

Lots of national sports fixtures and events in the area cancelled. Probably for the best!

Sadly, I've now just seen this happen on two M72s. AMD powered. It appears that in building these PCs, I've connected them to a monitor which I think has a duff DVI connection which has 'poisoned' the ports, so to speak (over a DP to DVI cable). The damage was quick, affected both DisplayPorts, and couldn't be fixed by changing cables or anything. Perhaps it's high impedance, blown protection circuits or chips. These machines have HDMI ports which work fine so I can use those (gutting, on a brand new PC!) but the dodgy monitor now goes in the bin.

I rather like ours, but it’s going to have rather a short life compared to the Nortel system it replaced (which lasted for over 20 years). Wonder what’ll happen when I ask our support to fit an IP card for the PSTN switch-off?

From a product support perspective, we've had this discussion recently - using CS6 does put you at some risk. Assess that risk and document it. Do we still use it? Hell yes. It's the best software suite/product we've ever bought, and all versions of the software are still useful aside from Flash. We use the serialisation, though I have been able to use the offline activation website in the last few days.

When you go to A3 and stop your AD licensing, your license may no longer be valid.

15 years later, the OP is probably living off the fat proceeds of their hustle - assuming so as they haven’t posted for 13 years. Stop spamming crap on dead threads!

“Wielding his axe, he doth cleath the crowd with sick riffs”

$ProfileName = 'AoVPN_device_profile' $ProfileXML = ' vpn.newtown-hs.powys.sch.uk IKEv2 Certificate SHA256128 AES128 AES128 SHA256 Group14 PFS2048 SplitTunnel true 172.x.x.x 24 172.x.x.x 24 true true true newtown.sch.uk ' $ProfileNameEscaped = $ProfileName -replace ' ', '%20' $ProfileXML = $ProfileXML -replace '<', '<' $ProfileXML = $ProfileXML -replace '>', '>' $ProfileXML = $ProfileXML -replace '"', '"' $nodeCSPURI = './Vendor/MSFT/VPNv2' $namespaceName = "root\cimv2\mdm\dmmap" $className = "MDM_VPNv2_01" $session = New-CimSession try { $newInstance = New-Object Microsoft.Management.Infrastructure.CimInstance $className, $namespaceName $property = [Microsoft.Management.Infrastructure.CimProperty]::Create("ParentID", "$nodeCSPURI", 'String', 'Key') $newInstance.CimInstanceProperties.Add($property) $property = [Microsoft.Management.Infrastructure.CimProperty]::Create("InstanceID", "$ProfileNameEscaped", 'String', 'Key') $newInstance.CimInstanceProperties.Add($property) $property = [Microsoft.Management.Infrastructure.CimProperty]::Create("ProfileXML", "$ProfileXML", 'String', 'Property') $newInstance.CimInstanceProperties.Add($property) $session.CreateInstance($namespaceName, $newInstance) $Message = "Created $ProfileName profile." Write-Host "$Message" } catch [Exception] { $Message = "Unable to create $ProfileName profile: $_" Write-Host "$Message" exit } $Message = "Complete." Write-Host "$Message" Ours. Run as a startup Powershell script directly. I updated this script for W11 - our W10 one didn't work on 11 but this works on both. Note: change 172.x.x.x to your own subnet.

Network adapter settings on the MDT server?

Talk online is that this is DNS related, possibly to your DC or MDT host. Have a good scrutinise.

Tried rebuilding your boot image?

The slow dying is not a classic driver issue - to me it strikes as either dying chipset or CPU, perhaps due to voltage issues on the cable runs - but what driver version are these using? Do you get a display of the splash or UEFI screens?

Is the deployment share mapping correctly, so you can access the Z: drive on the client? If not: net use z:\\\deploymentshare$ Then: z:\scripts\Litetouch.vbs If these don't work, something is broken on your MDT/WDS.

I still have the old Windows 10 removal script attached to the TS, but I don't think it works.

Server 2019 Our ADK is still the 10.1.19041 version. MDT 6.3.8456.1000 Deploying Windows 11 24H2 now with this setup. I have a CMD to pause the TS to allow the network adaptor to install and initialise (that helped with W10), plus some of the tweaks from above.

That makes it like whack-a-mole. Still doable, buy you'll need every server doing the share open so you can kill all instances!