garethEds

Ahh this one is the Surgeon. I know which other one you mean - I've seen it appear on my 'box' Gareth

Things I am watching at the moment and enjoying.. The Mandalorian New Amsterdam The Morning Show Gareth

Send everyone home for the day.

Afternoon, Just thinking about browsers and Windows 10. What are people going to do when Microsoft release their newest version of Edge in January? Isn't it based on the same code as Chrome? Will you ditch Chrome and standardise on the new Edge? Or will you offer your users the choice? Cheers Gareth

Cheers Pal - have to ask, can you recommend a specific version? Gareth

Yip - that was it. Doh me. Gareth

Morning, Can anyone recommend a decent backup storage NAS box for Veeam? We have two older Buffalo link stations but one has died and the other is showing errors - so I need to replace them asap. Cheers Gareth

Morning All, I've just rebuilt a 2019 server. All is going well. I've sorted the NICS and I've attached it to the P2000 using iSCSI in Server Manager. However - on our other servers this has created a directory on the C drive which has been mapped to the P2000 drives and I can see what is on them. How did I do this before? I simply cannot remember at all. This is all part of our cluster rebuild - but I cannot move on until I can see the P2000 from this newly built server. Any ideas? Gareth

Hi All, Need to pick your collective brains. I have two servers in a cluster. They can see each other, all can ping each other on all networks. However, when I move a virtual machine to the second server, it cannot be pinged from the outside world or itself. Live and Quick migration both work. I have a VM Traffic teamed network - which can ping the other servers and can ping the main network. Just nobody can ping the VMs on that second server. The management network is separate from the VM Traffic network - but I cannot for the life of me work out how the VM traffic gets out onto the network. It clearly does from the first server but I cannot find the difference between the first and second servers. I've checked the HyperV server virtual switch settings and all seem ok. On the first server it can. What am I missing? Gareth

Update: Have ordered a newer Intel based network card so I can remove the Broadcom one. Hopefully it will improve things. Gareth

Cheers Pal - it does indeed. Gareth

Of course - it seems it was this tick box in the Storage area of Failover Cluster Manager. It's still not perfect. The storage is failing over without issues but every now and again we are losing connection to one of the drivers. Gareth

Sorted it now - it was an annoying tick in the box. Yes - we are 2019. Wish I hadn't bothered. Gareth

So I'm really starting to get frustrated with Hyper V now. It was all running great on Server 2016 and then I go and upgrade. Sigh. Live Migrations are sporadic and I cannot now get the P2000 to failover if one server dies. If I restart Server 1 all the virtual machines on Server 2 suddenly go into panic and pause. Surely the whole point of having a SAN connected to failover is that the nodes can work without each other. Arghghgh. Tearing my hair out. Gareth

Evening, So as previously stated, our HyperV in place upgrade didn't go as well. As such I've started clean installing the Server. I've built Server 2 and put it back into to cluster. Everything is validating correctly (Still need to rebuild Server 1). HOWEVER - Quick migration works nice when the machines are turned off. Live migration works well from Server 1 to Server 2 but will not go back. It generates an error. I've pinged all the networks from each server and they are all fine. What would you guys be looking for here? Cheers Gareth

It says that none of them can talk to each other on any of the cluster networks. Gareth

I thought it could be the drivers: Server 1 / Server 2 - same spec 2 x 2 Port 1Gb 361T Driver: Intel / 10-05-2019 / 12.18.8.22 1 x 4 Port 1Gb 366i Driver: Intel / 10-05-2019 / 12.18.8.22 Server 3 HP NC 375T PCI Express Quad Port 1Gbit Driver: QLogic Corp / 01-10-2014 / 5.3.30.1001 HPE Ethernet 1Gb 4Port 331FLT Driver: HP / 25-10-2017 / 20.8.5.0 I'm going to look at drivers online to see if there are better ones. Gareth

Right - the cluster network is fixed. Now the next issue..... UDP Port 3343 - seems the servers have closed port 3343. I've re-opened the ports on all HyperV servers in Windows Firewall - but none of the networks can talk to each other. When we validate the cluster this is the error we are getting. I've opened the ports. Gareth

So is this the way forward from WSUS? Gareth

Evening all, So the in-place cluster upgrade that went very well has now started showing issues. It was all fine last MOnday when I left it. When I went to check today there were several hundred cluster errors. The CSV/Cluster network (as it's named) couldn't talk between the three servers - the three servers are 192.168.0.1, 10.168.0.2 and 192.168.0.3 - all have the same subnet and nothing has changed since the 2016 install (except the in-place upgrade). When pinging between the servers we are getting 'TTL Expired in Transit' errors. On one server the CSV/Cluster network isn't even showing as recognised - saying a network cable is unplugged (but it isn't). This is the first of the issues I am trying to solve. I've checked all the network drivers and all I can think of at this moment is that on the third server, there is a 4 port NIC with a driver from 2014. There are no drivers for 2019 that I can find. All servers are HP 380g8 (e and p models). I've put all of the virtual machines onto one server at the moment whilst I try and sort out the cluster. Everything else seems to be working - except the networking. Any advice anyone? Cheers Gareth

I read about doing this - is it considered bad? Gareth

Isn't anything you don't select left in there? I assumed they were - and you choose the ones you want to remove. Gareth

Bit of a negative post here @mavhc - and it doesn't really answer my question. Our MDT/WDS is working just fine on 2012r2 and has been for a while now. Quite a while too. WSUS is fine and working without any issues - for Windows 10 etc. Not everyone will go towards inTune so Microsoft would be a bit dull to do this. I'm sure they are not that dull. So - back to the original question.... Gareth

Have a look at the Powershell commands here. https://www.winhelponline.com/blog/reinstall-photos-app-windows-10/ Gareth

Morning All, Our HyperV cluster is now updated to 2019 and has been stable since Monday - so I'm happy the project was a success. Now comes the job of updating all the virtual machines. Some are 2012r2 and some are 2016, but would we benefit from upgrading all of our virtual machines to 2019? Am I right in thinking 2019 hosts work better with 2019 virtual machines or doesn't it really matter? What is the general thinking? Do services like MDT and WSUS work better now on 2019 than they do on 2012r2 or 2016? Cheers Gareth