![]() ![]() When you’re using Active Directory to manage user identities and devices like you company computer, the simple act of logging in successfully each day handles a lot of things behind the scenes as to determining who you are, what groups you belong to, and other domain-related features like group policies.īut what if you’re using a computer that isn’t tied to (or even knows about) your domain? Maybe you’ve got a Mac (like me) or a Linux PC that isn’t joined to the domain. And, given such a system, you probably have access defined to things like SQL Server via your domain credentials (probably through group membership). Most often, this is Microsoft’s Active Directory. If you work for a company, chances are you’re subject to some kind of network identity management system. It can run on Windows, on a Mac, and even on Linux with an appropriate desktop experience installed. You need not take my word for it take a look at how many products and components now have been ported to Linux and/or Mac. It’s getting less and less important what kind of hardware you’ve got on your desk and more about where the things you’re trying to connect to are. Today though, we live an increasingly cross-platform and cloudy world. Granted, I’m totally making this up but if you ever make a trip to a decent sized technical conference centered around SQL Server, I think if you took a straw poll, I bet I’d be closer than not. That probably still holds true for my totally-made-up-just-now statistic of 80-90% of the general SQL Server users out there. Likewise, if you worked for an organization that had SQL Server running, you probably were subject to being part of an Active Directory domain. Time was, if you were a SQL Server-based administrator/analyst/developer you probably were locked into using a Windows-based machine. This ain’t your daddy’s Windows-only world
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |