Ric_

I'm not 100% but I think it is combined. It doesn't sound like you are going to be performing IDS or sending all your traffic down a VPN though so you should be fine. I did realise that it sounds like you will ultimately be switching to your Juniper firewall... Why not just add a second outside interface on that and then you just have to update the NATs to switch over to your new connection?

The ASA should be fine for what you describe. With noting, gigabit ports on a firewall does not mean you'll get gigabit throughput... The 5512-X is rated for 200Mbps of encrypted traffic though so you should be safe.

It depends on how your new connection is handed off. I'd assume you are getting something with an IP but if your external IP block is spare to that, the ASA won't really do the trick. The 5512-X didn't have a huge throughput either so it might be cutting it close friending upon the connection and what you plan to do. Fortunately, the smaller Cisco routers are pretty cheap so you can put one of those in front or add a less expensive device in front of the firewall. At the same time, it sounds like routing and firewalls may not be your strong suit so it may be advantageous to bring in a third party to set up what you want and then you can learn how to maintain it. Also... I've typically found ADSM makes horrible configs so you really need to know how to use the CLI. Likewise with the silly Cisco router GUI.

Started make two adapters and the cheaper one has always proved flakey in my experience (with blue screens in Windows 10)... The more expensive one which I think is ICUSB2321F (FTDI) works like a dream though.

Also don't forget your 2008 and 2008R2 machines which have the same end of life. These likely have more troublesome software. Whilst I'm at it, CentOS 6 ends only a couple of months later.

My boss didn't say I couldn't put a PO in for one.

Would something like this not suffice? https://github.com/guysoft/FullPageOS (admittedly not Firefox)

A while back I saw a really cool welcome kiosk that does almost what you need... of course I can't find a link to it now. Basically it ran an app that used the Lync client SDK to integrate the video calling bit and it even printed out a visitor badge. Anyway... I did find this LyncAutoAnswer by shanselman which may give your app people a bit of a start.

If you're being prompted for a password, then a password was sensibly configured by your predecessor - your serial settings are correct or you wouldn't see anything. Your only option is to reset the switch to factory defaults (two cocktail sticks needed for these I think). Even if you knew the IP at this point, you'd still need to know that password. Edit - also... I think these switches had a bug in some firmwares where auth caused a memory leak which slowly brought down your whole switch. It could be you just hit this so the power cycle suggestion may also help.

I haven't used this myself but I happened to get an email from Adobe the other day. Apparently, there's a thing called 'Packager' which I guess is the CCP that @Arthur mentioned. A little more detail at https://helpx.adobe.com/enterprise/package/help/creative-cloud-packager.html Once you've used that to make your MSIs, you should be able to deploy as normal through SCCM. There also looks to be loads of other information on the Adobe site about managing licenses and wotnot that may be of use to you.

I believe that the 2524 has a 9-pin serial port on the front. You'll likely need a 9-pin to 9-pin cable. The 'plugging in a serial cable' section of the instructions can be found at ftp://ftp.hp.com/pub/networking/software/59692353.pdf page 2-15.

I added a couple more for you

Way back I used ThinStation to do something very similar https://thinstation.github.io/thinstation/ - from what I remember it worked quite well to eek a little extra life out of some machines. I do seem to recall having to mess about a bit to get certain drivers to work but, like I said, this was some time ago. I even used this booting from floppy disks on some machines at the time since not all my NICs did PXE! Whilst trying to remember the name of ThinStation, I also came across OpenThinClient - Free OpenSource ThinClient Solution - openthinclient - I've never used this but it's management doofer may be handy since you have 30 things to set up.

A quick Google found a super simple script https://gallery.technet.microsoft.com/scriptcenter/Move-AD-Computer-Object-4ed2c5f8 It's not exactly what you want. You could simply create multiple files (one for each destination OU) or you could easily hack it to update the destination variable within the for loop. PowerShell is great

It's likely that the other guys are correct but could you not just go to the room named SERVER and count how many cables/sockets there are (I'd like to assume that the person testing the fiber also labelled them). You should also take a look at the switch stats since those ones in red are likely not performing great. You certainly shouldn't bank on getting 10Gbps over them. Whilst your playing with the switches, also take the time to add some bandwidth monitors to your connections between switches (something like Cactii will do the job and I've recently found OpenNMS super easy to use). The reason I suggest this is to make sure that you need the 10Gbps links - there's no point buying expensive switch ports and potentially having to upgrade fiber runs if your clients aren't approaching the limits of a 1Gbps link.