Wsus for remote vpn and on-premise users
-
You can use Windows Update for Business. No need for WSUS.
-
@obsolesce said in Wsus for remote vpn and on-premise users:
You can use Windows Update for Business. No need for WSUS.
Is there any type of reporting in that?
-
@dashrender said in Wsus for remote vpn and on-premise users:
@obsolesce said in Wsus for remote vpn and on-premise users:
You can use Windows Update for Business. No need for WSUS.
Is there any type of reporting in that?
Looks like there's some built-in reporting in Azure.
-
@dashrender said in Wsus for remote vpn and on-premise users:
@obsolesce said in Wsus for remote vpn and on-premise users:
You can use Windows Update for Business. No need for WSUS.
Is there any type of reporting in that?
Yes, multiple methods of reporting... reporting out the ass.
-
@obsolesce said in Wsus for remote vpn and on-premise users:
@dashrender said in Wsus for remote vpn and on-premise users:
@obsolesce said in Wsus for remote vpn and on-premise users:
You can use Windows Update for Business. No need for WSUS.
Is there any type of reporting in that?
Yes, multiple methods of reporting... reporting out the ass.
As long as you have Azure AD - pretty sure you can use WUfB without it.
-
@dashrender said in Wsus for remote vpn and on-premise users:
@obsolesce said in Wsus for remote vpn and on-premise users:
@dashrender said in Wsus for remote vpn and on-premise users:
@obsolesce said in Wsus for remote vpn and on-premise users:
You can use Windows Update for Business. No need for WSUS.
Is there any type of reporting in that?
Yes, multiple methods of reporting... reporting out the ass.
As long as you have Azure AD - pretty sure you can use WUfB without it.
Can't?
-
So a little background about this company I'm trying to implement patch management, is that it's growing through acquisitions. There's currently about 12 locations, and I just heard recently they acquired another company, which adds it to 13 locations. I'm wondering if implementing an RMM will benefit this company for the future? They are growing at a fast rate, and it doesn't appear to be slowing down.
-
@fredtx said in Wsus for remote vpn and on-premise users:
So a little background about this company I'm trying to implement patch management, is that it's growing through acquisitions. There's currently about 12 locations, and I just heard recently they acquired another company, which adds it to 13 locations. I'm wondering if implementing an RMM will benefit this company for the future? They are growing at a fast rate, and it doesn't appear to be slowing down.
In my opinion, RMM almost always makes sense. It's weird that internal IT departments use it so infrequently. What makes it logical for MSPs also makes it logical for internal IT. There is little different between an MSP and internal IT. Once in a great while that difference could be reflected in different tooling. But typically, it would not. The similarities are too close.
Most internal IT today is heterogeneous and that almost guarantees that RMM is the right approach over more "traditional" internal tools. Most internal tools are built around homogenous LAN environments, not disparate heterogenous environments.
-
@scottalanmiller said in Wsus for remote vpn and on-premise users:
There is little different between an MSP and internal IT.
They are basically the same thing. In many cases the internal IT is a separate entity that basically bills the company and/or child companies, but is on the payroll of the company.
-
@obsolesce said in Wsus for remote vpn and on-premise users:
@scottalanmiller said in Wsus for remote vpn and on-premise users:
There is little different between an MSP and internal IT.
They are basically the same thing. In many cases the internal IT is a separate entity that basically bills the company and/or child companies, but is on the payroll of the company.
Yup, the key difference isn't their relationship to the rest of the org, effectively MSP, ITSP, Internal IT, etc. are all external in how they are approached. Only how they are paid really differs and the staff don't always see that.
What makes the two different is that an Internal IT department (even one treated as a consulting group) has only a single top level customer and MSPs have multiple. That's really it.
And that doesn't always make a real difference. If the top level internal IT customer doesn't force all underlying groups to unify under a single IT strategy you get an effective situation of multiple customers, sometimes as you said, even with separate billing.
