Computing option with "no funds"
-
@Dashrender said:
Considering the geographically disperse company you have there, AD (in general) will require either dedicated communication links or VPN tunnels. Either costly or potentially painful to manage (granted once a VPN site to site is up, you rarely have to deal with it).
Pertino works really well for this.
-
@scottalanmiller said:
@Dashrender said:
Considering the geographically disperse company you have there, AD (in general) will require either dedicated communication links or VPN tunnels. Either costly or potentially painful to manage (granted once a VPN site to site is up, you rarely have to deal with it).
Pertino works really well for this.
But as you mentioned work best with windows machines, not personally owned Chromebooks.
-
@Dashrender said:
But as you mentioned work best with windows machines, not personally owned Chromebooks.
Doesn't work on Chromebooks at all. But Chromebooks don't need it as they get their storage from Google.
-
Funny I'm in an office of very high end tech people discussing right now how many of them have managed to almost never work in an environment with AD at all.
-
@scottalanmiller said:
Funny I'm in an office of very high end tech people discussing right now how many of them have managed to almost never work in an environment with AD at all.
Are the machines those users are working on managed by the company at all? just curious.
-
@Dashrender said:
@scottalanmiller said:
Funny I'm in an office of very high end tech people discussing right now how many of them have managed to almost never work in an environment with AD at all.
Are the machines those users are working on managed by the company at all? just curious.
It's a mix. Sometimes they are, sometimes they are not. Both models exist and flourish. On the west coast, as we mentioned in another thread, I see unmanaged a lot, but away from that I see managed being the more common.
-
A lot of AD and group policy exists to prevent users harming themselves and/or the company. If I could stop working with dangerous idiots I'd be much more comfortable with getting rid of AD.
-
@Nic said:
Check out Tech Soup if you haven't already. They give stuff to non-profits. Also maybe check out electronics recycling centers for free old stuff.
Yup - I've been in the NPO arena now for about nine years,.. so I've used them plenty. In the past year I did learn of GrassRoots and can now add free hosting to the mix. Being a NPO is great... and also not. I like finding options that don't include spending buckets of money but still get the results needed.
I don't like to say I think outside the box,.. Id rather say - what box!
-
@scottalanmiller said:
@Dashrender said:
@scottalanmiller said:
Funny I'm in an office of very high end tech people discussing right now how many of them have managed to almost never work in an environment with AD at all.
Are the machines those users are working on managed by the company at all? just curious.
It's a mix. Sometimes they are, sometimes they are not. Both models exist and flourish. On the west coast, as we mentioned in another thread, I see unmanaged a lot, but away from that I see managed being the more common.
It might be a topic for another thread... but why would you go 'unmanaged' in a large office? How do you allocate security on network shares as easy as (at least I understand) you can with having a Domain and AD?
-
@g.jacobse said:
It might be a topic for another thread... but why would you go 'unmanaged' in a large office? How do you allocate security on network shares as easy as (at least I understand) you can with having a Domain and AD?
The same way Sharepoint online does, or Google Docs does. It's all done on the hosting solution. The local account doesn't matter. Web account does.
-
@Carnival-Boy said:
A lot of AD and group policy exists to prevent users harming themselves and/or the company. If I could stop working with dangerous idiots I'd be much more comfortable with getting rid of AD.
If you can provide all the required services via web pages or VDI or TS, and segregate the BOYDs from your production network, why do you need to care about the end device, the interfaces to the remote systems are what are protecting your data.
-
Not sure @Dashrender. I've worked with AD for so long I can't imagine life without it. I don't use VDI or TS and all my web services use AD credentials, so I don't know how the alternative would work. Would be interested to hear from people who actually do this.
-
I'm in the same boat as you. It's definitely hard to image users just having their own equipment, being responsible for their own equipment - yet still somehow providing all the needed accesses, but I can envision it being done.
What web services do you have using AD? Internally built web apps? Those could be transferred to a datacenter where you have a small connected node of servers, one or more running AD, the webserver prompts the user for their logon (the user doesn't care that it's AD), that logon is verified against the nearby AD server, tada... no more AD needed locally.
Of course this is probably not the best or even ideal way to move this to a hosted solution, but it's an option.
-
@Dashrender said:
I'm in the same boat as you. It's definitely hard to image users just having their own equipment, being responsible for their own equipment - yet still somehow providing all the needed accesses, but I can envision it being done.
What web services do you have using AD? Internally built web apps? Those could be transferred to a datacenter where you have a small connected node of servers, one or more running AD, the webserver prompts the user for their logon (the user doesn't care that it's AD), that logon is verified against the nearby AD server, tada... no more AD needed locally.
Of course this is probably not the best or even ideal way to move this to a hosted solution, but it's an option.
Not only that but you could also look at other authentication options. Something like OpenID or even an open source LDAP server could provide that mechanism.
-
Hosted AD is still AD though, right? Are we just talking about BYOD here? I'm not a fan of BYOD and have managed to resist it so far, though I'm sure it's only a matter of time. What happens when someone's personal device breaks and they can't use it to do any work?
-
@Carnival-Boy said:
Hosted AD is still AD though, right? Are we just talking about BYOD here? I'm not a fan of BYOD and have managed to resist it so far, though I'm sure it's only a matter of time. What happens when someone's personal device breaks and they can't use it to do any work?
That would be stipulated in policies, once you go BYOD the amount that you support is up to you and the management team. We haven't gone BYOD and probably never will.
-
If you don't have AD, how do you assigned policies on login? simple management of network shares and other resources such as networked printers and such?
Yes you can do quite a bit with hosted solutions,.. But,..
-
@g.jacobse said:
If you don't have AD, how do you assigned policies on login? simple management of network shares and other resources such as networked printers and such?
Yes you can do quite a bit with hosted solutions,.. But,..
With hosted solution you don't have network shared in the conventional ways anymore, you have files in Google Drive or in SharePoint. Navigation in these systems is similar to traditional shares though.
If you're using all web based services, what policies do you need to push to the users? As for printers, you create documentation on how to add the printers and you give that to the users. Or you setup the printer for them, once added, you probably don't have to do much more. Of course in this situation there would be no print servers, just direct printing.
-
@coliver said:
@Carnival-Boy said:
Hosted AD is still AD though, right? Are we just talking about BYOD here? I'm not a fan of BYOD and have managed to resist it so far, though I'm sure it's only a matter of time. What happens when someone's personal device breaks and they can't use it to do any work?
That would be stipulated in policies, once you go BYOD the amount that you support is up to you and the management team. We haven't gone BYOD and probably never will.
Agreed, going BYOD means completely rethinking your end user technology policies. You/your company has to decide how they want to handle users who's devices don't work, etc.
Like Carnival-Boy I can't see my office ever going that route for regular employees at least not without completely changing the culture. And I don't think they want that culture change.
-
@Carnival-Boy said:
A lot of AD and group policy exists to prevent users harming themselves and/or the company. If I could stop working with dangerous idiots I'd be much more comfortable with getting rid of AD.
Sure, but AD is not the only means of doing that. It isn't "AD" or nothing, it's "AD or an alternative."
