Here's a way to get Yesterday today and tomorrow... I'm not a super proficient Perl programmer.. but htis is what I could cobble together...

#!/usr/bin/perl my $today=time(); #Todays time in seconds since ~Jan 1, 1970 my $yesterday=localtime($today - 86400); #Subtract 86,400 seconds (one whole day) my $tomorrow=localtime($today + 86400); #Add 86,400 seconds (one whole day) $today=localtime($today); #Convert today into a proper date/time format. print "Yesterday: $yesterday\n\r"; print "Today: $today\n\r"; print "Tomorrow: $tomorrow\n\r";

@Carnival-Boy said in Office 2013 Vs 365 vs 2016 Products:

I haven't noticed much difference between 2013 and 2016. It looks a little nicer. I don't believe there are any main differences, just lots of little tweaks.

Evolution, not revolution. 2013 was actually a pretty big change from 2010, that can't do that again for a while. I've not used 2016 but my understanding is that it is very much a "tweak" upgrade.

I'm interested in knowing how the MS secure email works, I've been considering using it when I move to O365. Man, it sounds pretty bad.

That whole interface setup is a joke! You always end up having to have both sides code specifically for the other.. so much for a GD standard!

@johnhooks said in ssh_exchange_identification: Connection closed by remote host:

Also a good way to use a web management interface without opening up http and https.

I do that a bit.

@scottalanmiller said

Cool. So the numbers hold up, but no explanation as to why. Something is certainly amiss.

Don't you believe in magic?

@brianlittlejohn said in Iphones and Exchange sync problems:

@Dashrender There also was an edit button back pre IOS7 i believe instead of the circle i button

The edit button is still there.

Microsoft's model is:

user 1,2,3,4 > Global Security Group > Domain Local Group > $resource

I noticed someone put in domain\Users (which is a built-in group), instead of using Domain Users. I'm skeptical to think that this works because of security group nesting... Domain Users is a member of domain\Users (built-in) but I have never saw someone use that built-in group before....
0_1461775381653_users.png

@Dashrender said in BackBlaze vs. CrashPlan:

@BBigford said in BackBlaze vs. CrashPlan:

reasoning behind trying BB & CP. Our other servers and Windows workstations are backed up with System Center DPM, which allow for immediate restore after running a successful backup.

Well, that's case case with most products - though it sounds like CP has some sort of indexing it has to do on the server side post backup - so that's a drag.

Are there any more traditional backup products that can be used - hate to mention them, but something like Backup Exec - something that can backup to a local system, then push to a cloud source.

Also, I'm wondering - why do you need to worry about end point computers? Can't your users save all there work to a network drive?

We could use something like Unitrends, but there are only about a dozen Macs so the cost isn't justified. I think we would end up running a few thousand if I remember right. I put OSX Server 10.11 on a laptop to test the new functionality. Not nearly as good as it used to be, and it was never really that good.

Sorry @scottalanmiller and @JaredBusch (not bragging but the solution is very simple)

Below is a working result of the setup and backup job.

0_1461757462888_XenCenterMain_2016-04-27_07-42-16.png

What unknown device is showing? Maybe a screenshot?

Did you reboot post install? 😛

Now THIS is the kind of chatter this thread deserved, LOL.

@JaredBusch said in AOL - Exchange - email received calendar event not so much?:

@scottalanmiller said in AOL - Exchange - email received calendar event not so much?:

I wonder if my ICQ is still out there. No idea what it was anymore.

Also apparently, the 6 digit account numbers had some kind of internet fame in the early 2000s. There was huge hacking news about people stealing 6 digit ICQ accounts. No idea why.

Because they were very short, I had two 6 digit ones, because I got them so long before that, I also had much shorter ones (the lowest was 1000 in the original ICQ protocol) I arbitrarily created by purging the original accounts.

Whether or not it still exists, the answer is: probably. Only suspended users and paying users are purged after about 10 years, so there are literally about 80 million accounts going unused across the entire infrastructure that will never be used again.

@Dashrender said in MS removed SharePoint from Business plans:

VDI seems complex in licensing.

That is the only exception that I could think of, but is that really complex? I think the complexity is that people don't want to learn and/or admit what VDI is and make the complexity in understanding VDI, not in understanding VDI licensing.

@BRRABill said in Backup MX or no?:

So, to answer the question posted about that article, if you are interested in making sure your e-mail gets delivered, then ignore that article.

The article is fine, you just have to read it to see the context. This is the context setting piece:

They do this as secondary records usually point to email servers that deploy little or no security checks such as those you’d find at some ISP’s for example. This encourages the spamming servers to keep sending even more as they can see it’s being accepted and so the vicious circle continues.

Basically we see people seeing up a second MX and not maintaining it.

So instead of telling people to get a clue and manage their servers, they say to just do things poorly. It's more of "we assume that you won't take good advice, so we'll give you more bad advice based on that assumption."

If you truly assume that you simply won't properly maintain the second SMTP MTA, then sure, don't have one. But that applies at a much more general level. Let me provide a best practice that supersedes all of this:

Best Practice: Never run a server or IT resource that you do not properly maintain.