@scottalanmiller said:
@Carnival-Boy said:
How many companies have domain admins AND don't use WSUS/SCCM?
A fair number in the SMB and climbing because of the move away from WSUS in small environments to peer to peer.
I don't use WSUS in my environment. I spent more time managing it then I do from fixing bad updates from MS.
@scottalanmiller Just saw the original post was from December 20th... I wonder why it popped to the top of my SW feed.
I buy my phones outright all the time to keep monthly costs low.
Unfortunately where I live, AT&T is the only reliable service once you are outside of the city. But the family plan I am on with 4 phones is only $135/month.
I haven't upgraded my company yet. Still testing software.
@JaredBusch said:
@brianlittlejohn said:
Bad decision on Apple's part to have it on by default.
Bullshit. Bad parenting. It is impossible to unknowingly blow over you cell plan package with any of the top 4 carriers. The parent willingly ignored notices.
From the article.
That is his own damn fault then.
@JaredBusch I fail to see how I implied apple invented it...
Didn't read the article, but when the first mentioned this feature in one of the iOS 7 beta's i thought it was a bad idea to have it on by default.
Bad decision on Apple's part to have it on by default.
@JaredBusch I have an extended hyper-v replication setup over a vpn that works well, it lags behind occasionally, but is usually within 15 mins of the live data.
@BBigford said:
@brianlittlejohn said:
@BBigford said:
@brianlittlejohn The build is 516.32, how do you decipher your service pack from that?
You are on the RTM version. There is a SP and several CU updates since then.
How were you able to find out it is RTM?
On another note. I removed every user but me and the secretary... Meeting notice delivered just fine. Which means there is a problematic user, even though I checked each one and they are all current employees and accounts are all fine.
How many users were in it? It does seem like one of your user mailbox's may be causing your issue.
@BBigford
Last Line in 2013 Table
Release to Manufacturing (RTM) version of Exchange Server 2013
December 3, 2012
15.00.0516.032
@BBigford said:
@brianlittlejohn The build is 516.32, how do you decipher your service pack from that?
You are on the RTM version. There is a SP and several CU updates since then.
@BBigford Look at the table on the link I gave... The build number should be longer and start 15.* It has the powershell command to run to get it on the page as well.
@BBigford Its based on the build number.
https://technet.microsoft.com/en-us/library/hh135098(v=exchg.150).aspx
