Windows updates are not enough…

So, you are feeling good about your systems because you have patch management setup or on your personal PC, you have automatic updates enabled. While that’s great since everyone knows you have to keep Windows patched or run the risk of vulnerabilities on your computer being exposed, it simply is no where near enough.

One of the biggest vulnerabilities now is Java. Unfortunately, Java needs updated so often and is so annoying about the way it updates, people pretty much shut it off. Add to that, the Java update loves to sneak crapware like the Ask.com toolbar into the update, and it’s no wonder the majority of Java run time environments aren’t current. The same could be said of Adobe Flash, Quicktime, Adobe Reader, etc.

Luckily, there is a simple way to manage all these updates by using a little program called Ninite. There is a free version for home users and there is a pro-version for businesses that need to set this up centrally.

For home users, you simply click all the apps you want to stay updated on the Ninite webpage and click download for the executable that you will run. If one of the programs you check isn’t already installed, the Ninite program will install it. Simply run this program on a regular basis to keep all the applications up to date. If you are savvy enough, you can schedule this with Windows Scheduled Tasks. Please make sure the Java update is one of the updates you choose.

For those of us who need to set this up centrally, there is the Pro version. With the Pro version, you can launch the application silently. You can simply create scripts to call the program silently with the applications you want to update and or install. You can specify update only if it’s installed or you can specify to install if not already there and update if it is. You can also output to a log. If you can do some programming, you can then parse that log file for any failures and alert yourself. You can also parse it for successes if you need to capture the data for reporting the status of updates across all your machines.

If you aren’t great at scripting, you can also launch the GUI and pick the machines to update and push the updates out. Who wants to do this manually though when you can automate it.

Lastly, from what I gather they have a Linux beta. I haven’t tested it, but from what I can see it’s for Ubuntu only right now. Updates on Linux are already very simple and can be automated, so I’m not sure what it brings to the table. I’ll have to check it out when I get some time. I’m running Linux Mint currently and updating is a cinch.

 

Our file server in the cloud powered by Egnyte

A few years ago, we decided to get rid of any server we could. We migrated from Exchange to Google Apps, moved our ticketing system from in house to hosted, and moved our Windows file server to Egnyte. I decided to write about this now, because a client was asking me about it.

For us, we didn’t need a typical file server. Most of us worked virtually. Even the users in the office were virtual considering everything resided at a datacenter. We had a site-to-site VPN setup between the office and the datacenter, and we had SSL VPN setup for remote users not in an office. Constantly accessing files via VPN gets old pretty fast though. We wanted our files quickly accessible while working on our day-to-day machines with no noticeable lag time as we dragged the files over our internet line. We also wanted the ability to share files easily and to have access from anywhere without VPN clients.

We looked at some of the bigger players at the time (Box, Dropbox, etc), and then we stumbled onto Egnyte. At that time, I couldn’t believe Egnyte was such an unknown because their solution was pretty damn impressive and extremely cost effective.

First I’ll explain our setup and then quickly go over some of the other features that we don’t use.

When I migrated our file server, I simply setup the folder structure that we had on our file server on Egnyte. I mirrored permissions as well. Then I simply used Egnyte’s drive mapping application on our file server to map a drive to Egnyte. From there, it was simple copy and paste.

Next, I had everyone download and install Egnyte‘s Personal Local Cloud software. This is a simple install where you’ll tell it where to store the local cache. Once the install is done, a web configuration interface opens up. From there, you enter your login credentials and specify which folders you want to sync locally.

That was it. Now, we were able to work with our files like they were local, but the PLC software would keep the cloud updated and everyone else’s local copy updated. It’s been a few years, and it’s still working well.

Since then, we’ve started using the mobile client on phones, tablets, etc, which all seem to work well.

There are some nice features if you are in an office, which we don’t personally use. Instead of installing the Personal Local Cloud on everyone’s machine, you can setup either their Office Local Cloud, which runs on a Netgear NAS, or you can set up the Enterprise Local Cloud, which is a VMware virtual machine. If you go this route, I recommend going with the ELC. It seems more reliable than the OLC. We have a client running both, and they had lots of issues with the OLC on the Netgear, which is why they are running both. It seems like many of those bugs have been worked out, but I’d still trust the ELC more than the OLC.

There are a few bad things about Egnyte. First, we’ve had issues with their support in the past. They have ramped up staffing on that, but we still have issues from time to time. Also, even though they have version control, which is a nice feature and a trash bin when you delete a file, you only have a certain amount of time before that file is purged from the trash bin. If you accidentally delete something and you don’t realize it before it’s purged from the trash, you risk losing it for good.

Also, they changed their web interface a year or so ago. I personally like the old interface better, but maybe I’m getting old. I’d recommend switching to classic.

All and all, it’s been a good choice for us. Maybe it’s something that will help you as well. If you have any questions, don’t hesitate to leave a comment.

Fortinet Fortigate won’t save changes – CFG_CMDBAPI_ERR

It seems like every time I have to make a change to one of our Fortigate firewalls, the changes won’t be accepted, and I get the error “CFG_CMDBAPI_ERR“. That might be even worse than a Microsoft error.

If you do some googling for the error, you will find most people tell you to restart the ipsmonitor process. This is done with the “diag test application ipsmonitor 99” command. This typically does the trick, but today it was not working for me.

To see what was using up resources, I entered the “diag sys top 1” command. The last field shows the memory used. In my case, the problem was forticron.

Now, you can’t restart forticron the same way you restart ipsmonitor. You have to kill forticron, and to do that, you first have to get the pid (process ID). At the “diag sys top 1” command screen, the pid is the number right after the process name, which is the second column. Next, hit the Q key to exit the process screen. Now enter “diag sys kill 11 <pid>” where <pid> is replaced with the pid you just got from the previous screen. That should kill the process. It did for me, and I was able to make the changes that I needed.

Hope this helps someone out there. I know it was a pain trying to find the fix when I needed it.