Davit2005

Stopped yesterday here in South Herts. Still only -1 so if it snows It will prob settle as pavements have dried out since yesterday. Hoping it thaws out so I can go for a run without fear of slipping over. I don't mind running in snow as long as it is not ice.

Found the below link. This is the one thing that puts me off buying HP servers for home lab. Switches are normally fine for firmware but it seems HP have chosen to want service plans or is it CarePacks for firmware on HP Servers. https://support.hpe.com/hpsc/swd/public/detail?swItemId=MTX_4cffd6af93c442318a21c8981f

Lol, I was trying to install 2016 on a MicroServer Gen8 on Sunday, I gave up. About 5-6 years ago I believe I used the Smart Update Manager to update some HP blades at a previous employment. I wonder if that will help you?? https://www.hpe.com/uk/en/servers/smart-update.html

Domain joined PCs by default would normally get time from the Domain Controller that holds the PDC Emulator role for their time then the PDC should be configured to look at a reliable time source not it's BIOS. If they are not domain joined then I guess they should be pointed at a reliable time source directly

Water systems hacked, well they got in using TeamViewer https://www.theregister.com/2021/02/09/florida_water_hacked/

Light dandruff here yesterday but did get slightly heavier but now bac to dandruff again. Outside on my road (which is a fairly quiet side road) it looks like someone has sprinkled sugar sparingly.

Hopefully I'll pull my finger out and get out for my run on Saturday morning. A lot of fields near where I live are close to a river and are currently flooded, I've seen swans on a few and expecting to see no fishing signs pretty soon. Jus mostly inconvenience to vehicles and people using private roads and bridleways in between the fields, one so deep on Wednesday I couldn't actually run through it. A few sheep occasionally but they have been moved to higher ground,

Would suggest you have a backup internet connection for some redundancy. VOIP is a lot more flexible and will save money in that alone. No more running or using valuable data pairs just for phones as nearly all phones have a socket for the PC as well so simply make sure using a PoE switch or if that is not viable a power injector can work as well. Simply need to tag the VOIP vlan and then untagg the data for the PC. For testing you could set up a SIP trunk for very little money (you do not need a SIP trunk if you are only testing internally) and install 3CX (either the appliance or on a spare PC or evaluation server) or FreePBX. I use 3CX at home and can vouch for it's ease of use but a lot of people have successfully setup freePBX

Yeah it should be optional in public Preview, are MS not aware of the situation with so many people working from home and using their services.

Are you replacing existing Aruba APs, do you have controller or are they going to be cloud/standalone? And are you looking at the Aruba Instant-On or Aruba IAP/APs. Are you dead set on Aruba?? We use Aruba heavily with 2500 + APs and multiple controllers but we have remote offices using RAPs, Pools of IP addresses with provision for up to 40k IP addresses (20K in normal use), role based access and just find that this works flawlessly as package with our NAC provision including wired switches but that will not be same requirement for everyone.

I imagine this should be a different vlan for the phones, it is best to have phones on a different vlan. Can you check the IP address, subnet mask and gateway received on one compared to another. Do the MAC addresses of the phones show up on the correct DCHP scope on the DHCP server. You would probably have some options set on the phone vlan scope so the phones can get the downloads of the settings so t will be important for the phones to be getting an IP address from correct range.

Keep getting running injuries, getting old I guess. Cannot wait for swimming pools to be open but may just try and get my mountain bike fixed and start cross training. Roll on summer, getting fed up of running in dark, wading through huge puddles or sliding on mud but in summer I will be complaining about the heat so I cannot win.

If you have a LAGG group configured or not and just relying on spanning tree to block redundant links it does not matter as the core is acting as one switch and as long as you split between switches you should be fine. Of course if you rely on Spanning tree then one link will be blocked to prevent loops make sure the spanning tree is compatible as well as I have seen issues between devices that have had different Spanning tree protocols enabled. A LAGG link would be preferable as you can utilise both links but suggest checking if a LAGG can be configured between the Cisco switches and your edge switches most of the time it can but may need a bit of tweaking so just check to make sure.

Not really a Mesh but a ring. In a ring you could lose any one switch and it will just effect connectivity to that one switch. A mesh would be 3 connections on each switch so each switch has a connection to every other switch but I am not sure if that is supported in stacking or even needed TBH. You could split each switch to each core in theory.

Just had my first HMRC txt. If that link is true link it was registered yesterday Reported to 7726 and deleted.

If all 4 of the SG500 can become 1 logical stack. I'd aim for a ring topology with min 2 fibres between each building on different routes if possible with the switches in each powered from different UPS or power source if they do not have redundant power. If you have enough fibres would it be worth splitting the Hypervisors between each switch? Bearing in mind these are not modular switches with dual management etc. I've got 4 Aruba 2930f switches at home I don't think it matters which way you stack them but I'd look at possibly 1 > 2 > 3 > 4 and then back to one creating a Ring topology rather than a chain. With the Aruba 2930f you can use any front ports as long as speed of ports is matched with neighbour's. With the 2930f you only get a Ring with 3 or more switches cabled and configured appropriately

I'm not affiliated or linked to Unifi in any way but If anyone has the bug and wouldn't mind doing a packet capture on the LAN Ethernet interface connected to the AP in a hope to get some more info and see if the DHCP Discover is actually getting through to the network. I'm just be interested in results from a techie point of view. Basic DHCP procedure is as follows. Client Discover Server Offer Client Request Server Ack

Is phone trying to charge from Laptop causing power drain and disconnects? Is laptop plugged in when you test?

I'm not sure what current best practice is but I'd recommend not installing AD on a server running the Hyper-V role or vice versa. I'm not sure if it possible even.

Yes that should work @TechMonkey has a good point that you can save the typing by automatically adding the domain to what has been input at the prompt. In actual fact that's how I used to do it with AD and Azure years back.

Something like below to capture data which is then called later on. If you ever get into PowerShell get into the habit of commenting the scripts so you and anyone else gets the gist of what the script is doing. #Create a variable and ask it to wait for an input, name of variable for this does not matter as long as the same vairiable is used where the data is called $ObjectIDOrSomething = Read-Host "Enter the target email address" Connect-AzureAD Install-Module AzureAD # Call the data captured by the input Set-AzureADUser -ObjectID $ObjectID-Or-Something -AccountEnabled $false Get-AzureADuser -ObjectID $ObjectID-Or-Something |Revoke-AzureADUserAllRefreshToken Once you get into to powershel you can get quite creative, I am no expert but if you know what you want to do even if you have to break it down to small chunks a lot is possible. I can never remember much of the syntax because I do not use it a lot these days.

A LUN is a slice of some storage that you give to a host or hosts. Either connected by Fibre Channel or iSCSI You should be able to tie the access down to specific hosts, I'd suggest that when you setup the LUNs you do some form of Masking on the SAN. It is not difficult to do but INMO well worth it. Basicaly you give access to only hosts that should have access to the LUN. For instance if you were to mount a VMFS formatted LUN to a windows host with write permission you would prob corrupt it. Here is one such article on Google https://kb.netgear.com/23292/What-are-basic-LUN-concepts-I-need-to-know-before-using-my-ReadyNAS-OS-6-storage-system but you may beable to get some info from the manaufacturers of the SAN disk unit.

There used to be a way to do this without exporting but last time I used Hyper-V was over 10 years ago though and it was a bit convoluted to setup. VMWare ESXi/vCenter make this quite easy but you pay for the privilege but in the right scenario you can migrate VMs without turning them off and without having shared storage using vMotion or EVC if using same CPU manufacturer but slightly different chipsets. I have a number of servers at home which I use as production, with around 25VMs doing various stuff. pFsense can be virtualised, you may need to do some extra work like enabling promicous mode on the network settings of the virtual switch. There should be a few guides for it online. I've been running Virtual firewalls for last 4-5 years but migrating to pfsense on physical boxes now so I can reduce number of servers that I need 24/7. Veeam could be another way and there is a free edition of Veeam called Community edition which supports 10 workloads.

They have now released a new version 6.0.45 Fixed the multisite BUG, lol, speculation is rife. There are a few other changes to the GUI and moving of things around. Lawrence Systems has some more info CrossTalk Solutions https://www.youtube.com/watch?v=6GrRa9tNyCc

OK yeah to just tagg the vlans on the port of the HP 2930f that is connecting to the Unifi switch then on Unifi side either do add it to a profile (sorry do not have access to a Unifi switch anymore). You are better off doing routing on a switch to be honest than using a router on a stick approach. Whilst doing the vlan routing on firewall will make segregation by use of security rules easy you can do the same on most core switches by using access control lists and applying these where necessary. If you have not done any access control lists before just make sure you have physical access to the switch just in case you stuff something up and read up some documentation on doing them. You don't need to do them but just bear in mind that if you use a core switch and terminiate the vlans there that by default there is nothing stopping users being able to access servers/devices on other vlans that have their default gateway on the same layer 3 switch. Layer 3 switches are the way to go for vlan routing by sure.