Trying to help the technically challenged... so mainly myself.
日本語訳が必要な方は、コメントをください。
Subscribe to this blog
Follow by Email
Happy Sys Admin Day!
Get link
Facebook
Twitter
Pinterest
Email
Other Apps
Happy Sys Admin Day!! Hope your boss or groups you work with appreciate the day to day work on the dark side of the moon you do everyday. http://www.sysadminday.com/
Summary: Long story short, Fire TV Stick (2nd Generation) doesn't allow you to calibrate the screen, software wise, forcing you to use your TV settings (if available) to fit the screens content within it's borders. Super annoying for some apps, but you can fix this dumb issue as I was able to. If your TV allows you to adjust its settings, then you'd be fine as well, but the Vizio I have, has no such setting. Solution: Get the Amazon Fire TV instead. It's only slightly more expensive, but doesn't suffer the problems the Fire Stick does. Workaround: First you have to enable ADB debugging ( step 1 here ) on your fire stick. Next you'll need the ADB provided w/ Android Studio , or you can install w/ brew on the Mac . I prefer brew cause it's easier, keep following steps described by Amazon page if you are using Windows. Open Terminal brew cask install android-platform-tools Next find the IP address of your Firestick Settings --&
Summary: Unable to connect to ESXi/vCenter server with Connect-VIserver cmdlet, get the following error: "The SSL connection could not be established, see inner exception." Be sure to "Set-PowerCLIConfiguration -InvalidCertificateAction:Ignore" if you plan to connect to an ESXi/vCenter that does not have trusted certificate. Interestingly, something must've changed recently because the PowerCLI module actually would output a more descriptive message about setting your PowerCLIConfiguration. This appears to be the case w/ Powershell Core 6.1. I'm actually unsure when this behavior started happening and whether is module or powershell related. Regardless, figured I'd post this since I was initially confused myself when running some things on another system.
The VPN client was unable to successfully verify the IP forwarding table modification. A VPN connection will not be established. Summary: I started running into issue utilizing Cisco AnyConnect on my Mac basically complaining about not able to overwrite IP forwarding tables. This was on 4.6.x. Since my VPN endpoints were not providing me w/ an updated client and w/ no access to Cisco Anyconnect downloads, my only option was to try openconnect. It was totally worth it, here is why and how to set it up. PreReqs: Homebrew Installing OpenConnect: Launch MacOS Terminal brew install openconnect Getting VPN IP's/DNS Endpoints from AnyConnect: The information is typically located in your profile xml files located here: /opt/cisco/anyconnect/profile/somethingsomething.xml In the xml file, you are looking for "<HostAddress>typicallyaDNSName.com</HostAddress>" entry. These are your VPN endpoints that you would need to pass to openconnect. Using
Comments