That's why I'm saying they could be drug to court... but it would be pretty difficult for either side to prove anything unless there are recorded conversations (voice or email) and basically shows you are telling the client they don't need to purchase, then you're in trouble.

I am through worrying about this client.

According to the client "I understand and appreciate your thoughts I have already advised the cloud company I am interested in disaster recovery as this is one of the main reasons we are going outside of our office for server location.
I will let you know what I find."

@alexntg said:

@Dashrender said:

Alex, aren't your clients Scott's clients?

what would you recommend?

For advanced-user home use? Netgear makes some reasonable entry-level business APs. For the Apple-oriented household, Apple AirPorts can be configured for AP mode. If you're looking to go all-out with features like captive portals, VLANs, and central management, a jump up to Meraki may be an option, if one plans to get some heavy use out of it.

I've has great luck with Netgear ProSafe APs. I've had Apple Aurport too but found them to be unreliable. And very overpriced.

@alexntg Unfortunately, no. With this client I am lucky to even be involved in the hardware purchasing. Our main role there is software development. I keep carefully trying to get this work from the company that does it, but you know how that works.

@scottalanmiller said:

@alexntg said:

@scottalanmiller said:

Not the same idea. With SVN, for example, we can look up changes over time, do rollbacks, see who committed changes, deploy to other systems, do comparisons.

Both are good to have but version control is a different thing than those technologies.

I'm not sure about device comparison, but LANDesk does the remainder. It logs every action taken. if you push out a bad patch or package, you can roll it back/call the uninstaller.

That's pretty nice. Not free though 🙂

What's it matter if it's free? If it can save a few techs' worth of salary per year and makes managing thousands of computers much easier, it's paid for itself.

@Reymar.Esguerra said:

anyway thanks for your time @scottalanmiller for helping me 😄

No problem. And welcome to MangoLassi!

@technobabble said:

VM's would run on the data drive, correct?

Correct.

I've never read the Eula since I never considered installing it but I'm pretty sure that the time after the trial was actually a violation. The kind if stuff that the BSA looks for.

Another big ML win for Webroot!

Maybe it's a new update in 5.5. I've tested 5.0 and 5.1 and not seen it work on either of those.

@ambarishrh said:

@scottalanmiller Nice writeup on that actually.

Few of our servers are hosted in London and some in Vancouver. I was just wondering if loggly is safe enough to push all server logs. A centralised logging option is always in my mind, but am still thinking of having a self hosted log management server to collect and analyse logs from all our servers.

Loggly is the leading hosted log platform. It is likely safe to consider it safer than hosting your own log collection platform. Loggly is a major player.

Ah, I found a Chome plugin called 42 that lacks the tutorial stuff but is a nice, clean interpreter.

@Carnival-Boy said:

Out of interest, why is your client moving?

With mailboxes that large, I can only imagine the Outlook sync has issues at best.

Always good to see quality 3rd party Mac stuff

I actually started down that path in Q1 of 2013 when we deployed Elastix at my main site but ran out of time. Back then the T32G was not part of the configurator, but I did find this gem, which may help you:
link text.

I got as far as adding the T32G to the phone database on the server so that it would show as an option when Elastix detects the phone. But that's as far as I made it.

You bet. I was surprised when I found it. What a great idea. Now we just need OpenSuse support.

A single domain across both sites with a DC at each feels better at a first read. Very simple but keeping traffic from going over the WAN except as failover.

It's interesting I happened to see this thread today. We too have a Lanier copier similar to @Dashrender mentions above, and we were not able to do scanning to SMB because of Server 2012 R2's SMB version as well. We went with the Windows FTP server approach to get around it. Scan to FTP seems to work very well for pretty much every printer / copier we have that supports it.

Yes. It needs patched to get all of the updates. It is a mature release at this point.