Today we’re going to dive into something that admins have been doing for years: deploying Adobe Reader via Group Policy. You would be hard-pressed to find a company that doesn’t use PDFs, and while options for viewing and editing PDFs have greatly increased, the official Adobe Reader application remains the go-to PDF viewer for most companies.
Unfortunately, Adobe Reader is prone to high-risk security vulnerabilities. To help mitigate the risk of using Reader, one must be sure to keep the application up-to-date. Group Policy allows us to not only deploy the application, but also to push out new versions as they are released. Working out how, exactly, to accomplish that can take a bit of work, but this tutorial should help to clear things up.
As I’ve worked my way through the various oddities of Windows 10, I’ve found that most applications work great. For the most part, anything that worked on Windows 7 works on Windows 10. Visual Basic 6 (VB6) has been one of the few exceptions, so far.
Why install Visual Basic 6? It’s a long-dead program, after all. Well, like many companies out there, mine has a few proprietary programs that were written, long ago, in VB6. The apps work great, so it just hasn’t made sense to spend the time and/or money it would take to upgrade them to VB.Net. Yet, we still need to be able to make minor changes to the programs now and then.
We could keep an old XP machine around just for VB6, or set up a virtual instance of XP, or go for either of those options with Windows 7 (VB6 installed on Win7, though not perfectly). Instead of going those routes, though, I decided to look into getting VB6 properly installed on Windows 10. These notes should work for the Pro and Enterprise editions of both Visual Basic 6 and Visual Studio 6.
Microsoft Office 2003. Are you still running it? You really shouldn’t be, as Microsoft is ending support of the product in less than a month. Well, since I know many are still running Office 2003, and are likely to (unwisely) continue to do so for a while, this bit of info may prove to be of help to someone, somewhere, sometime.
Dell laptops have long come with built-in Bluetooth capability. This is great for those of us who enjoy the use of Bluetooth headsets, mice, keyboards, etc. With built-in Bluetooth, you don’t need an extra USB dongle. This is especially important on certain Dell laptops, as the number of available USB ports is rather limited. In fact, this port limitation is exactly what led me to revisit a rather old Bluetooth compatibility issue.
I recently discovered an interesting little problem while troubleshooting an Outlook 2003 issue, and figured it might be of help to other users out there. I’d come across the problem before, but didn’t remember the solution. So, this article is just as likely to help me in the future as it is anyone else.
I recently ran into an issue on a server running version 11 of Symantec Endpoint Protection (SEP). I was able to track down the solution, and it greatly improved the performance of Symantec Endpoint Protection Manager (SEPM). Read on for the full details.