If you are moving any of your local network services into Azure it’s likely you don’t want to have to access them over the Internet and would rather have a VPN, and “private” IP addresses assigned to each of your Azure Virtual Machines. Here I go through how to set this up using my home lab and Azure tenancy as an example. Continue reading “Creating a VPN from your on-site network to Azure”
A few years ago when UEFI became much more common on new PCs I wanted to use the UEFI network boot, rather than the old style PXE boot, for imaging machines. This worked fine for computers sat on the same subnet and VLAN as the server, but getting this to work when the client device is in a different subnet took a bit of work.
A couple of years ago I wrote about the pain of getting Wake on LAN to work on HP switches. While this got some of my machines to work, there was still quite a large proportion (about 60%) that weren’t playing ball.
I’ve finally had a bit of time to look into this, so here’s everything I’ve gone through to get a lot more of the PCs powering up on command. Of course there will always be some PCs which just refuse to work (we have some Gigabyte H81M based machines where they just don’t Wake on LAN – whatever you do the LAN link drops when the power is turned off), and some older H61M based machines that are a bit hit and miss. Continue reading “Wake on LAN revisited”
I’ve been working at really cutting down the initial logon times – started last year, and again with me rolling out Windows 10 2004 I’ve had to struggle to remember what I actually did, one of the main reasons for my blog is helping out future Katy as she is very forgetful 🙂
This has always been something that has bugged me, as I remember in 2003 at university there was a Windows 2000/XP network with some sort of NetWare back end. The Windows 2000 PCs (libraries etc mostly) logged on in about 2 minutes, nice and speedy, but in the computing labs they ran XP and it was a 13 minute logon (literally 13 minutes as I timed it). Subsequent logons were also 13 minutes. Extremely frustrating, yet means I’ve always been dismissive of people complaining of a 90 second logon time.
I’m currently working from home and managed to get myself locked out of a PC (Long story involving Bitlocker). Only way out from this was to re-install Windows and then rejoin to the domain.
Re-install is easy as I have WDS configured on my home network. Re-joining the domain is easy, I could either do an offline domain join with Direct Access policies embedded, or just connect the FortiGate VPN and join the domain and run gpupdate. I went with the latter as it seemed like it’d be the easier option. As I’d used WDS, the PC was now part of my home network domain, so I removed it from the domain, renamed and rebooted. I then went and connected it to the work domain and ran gpupdate, all fine, and restarted the PC. That’s when it got weird.
So I received a 35% off code from British Gas to get Hive Active Heating. As my boiler works off a time clock only (no thermostat) I decided this’d be great as I’d no longer have to guess how long I need to turn it on to get the temperature up on a weekend, and then forget to turn it off and have it wasting gas while I’m at work during the week.
They say it has to plug directly into the router, etc etc. Well as my ISP provided router is in modem mode, this wouldn’t work.. it’d either not get an IP address, or take the IP address assigned to my actual router and break the rest of the network.
As part of setting up SCCM I wanted to get all PCs to wake-on-LAN to enable truly zero touch deployment. I’m using mostly HP v1910/1920 edge switches with a HP 5406zl core switch. To send WoL packets while testing I’m using a tool from http://magicpacket.free.fr/ (once all set up SCCM will be doing the wake on LAN packets).
I’ve since written a new post about Wake on LAN, which may be useful for troubleshooting.
Continue reading “Wake on LAN across subnets with HP switches”