Friday, May 25, 2012
The problem with management tools
Management tools, whether they are for network, systems, nuclear power plants, or anything really, are really hard to get right. It's not that they can't report on errors, they can do that. In fact they can report on so many errors that you end up chasing so many errors you don't get to spend time on anything but chasing them.
Now what some people do is turn off everything, and then wait until something bad happens, go back and figure out what alert would have told them about it. This keeps you from missing an alert the second time, but also means you miss the first one. Not a bad approach but pretty time consuming as well.
Many systems have default warning values and while they are reasonable, they often times don't really match my particular environment.
For example we have a server that generally has 97% of disk space used. Now I know the argument is that's too close, you should add more space. But it's always been at 97%. It never fluctuates because none of the temp files are stored there. I don't need an alert every day that it is nearly out of disk space. If it hits 98%, maybe I want to know.
Now I can easily go in and set that particular threshold for that particular server, but there are literally millions of those in our environment. I would need a team just to go through and configure it once, let alone keep up with it. This obviously is not a very scalable approach.
What I really want is a smart configure tool. Really I want it to run and keep track of all the alerts and what it thought was wrong, and every day, or week ask me "How did things run?" If the answer was good. Reset the alerts to be high enough to not get tripped but low enough to alert me still.
Friday, May 18, 2012
What's your vendors CLOUD score?
Are you, like almost everyone, looking at moving to the cloud? Before you move your critical applications to a new provider check out their CLOUD score.
Company
Legal
Openness
Usability
Development
Company: Are they financially stable? Is there management team seasoned and well respected? Who invested in them? Are they making money or burning cash? Will they survive a disaster and be there for you still?
Legal: Is the legal contract right for you? Check out this blog post to see if you have added the right clauses to protect yourself. Having a good relationship is key, but if something goes south the contract is what the courts will look at, not what the sales team said over lunch.
Openness: Can you integrate with other systems easily? Can you move your data out if needed? Can they use third party authentication methods, like LDAP, or SAML? Do they have a "trust" site so you can see if they are having performance or reliability issues? Do they share there roadmap so you can plan appropriately? Is their knowledgebase available and useful?
Usability: Can users learn the tool quickly? Is training online available? Can you make domain wide changes with an administrator tool? Can you do bulk uploads? Is it easy to manage the system? Is it easy to work with support?
Development: How easy is it to cunstomize? Can you make meta changes from the user interface, or do you need a coding expert to make all changes? Do your developers know how to code in the language it uses? If not, how hard is it to find qualified developers, or train yours? Are the API's well written and robust?
If you ask all of these questions and are comfortable with the vendors answers, you can't go wrong. We use a spreadsheet that asks these questions and weights the scores giving us a result. Using the CLOUD score really helps us make the right decisions and avoid problems.
Company
Legal
Openness
Usability
Development
Company: Are they financially stable? Is there management team seasoned and well respected? Who invested in them? Are they making money or burning cash? Will they survive a disaster and be there for you still?
Legal: Is the legal contract right for you? Check out this blog post to see if you have added the right clauses to protect yourself. Having a good relationship is key, but if something goes south the contract is what the courts will look at, not what the sales team said over lunch.
Openness: Can you integrate with other systems easily? Can you move your data out if needed? Can they use third party authentication methods, like LDAP, or SAML? Do they have a "trust" site so you can see if they are having performance or reliability issues? Do they share there roadmap so you can plan appropriately? Is their knowledgebase available and useful?
Usability: Can users learn the tool quickly? Is training online available? Can you make domain wide changes with an administrator tool? Can you do bulk uploads? Is it easy to manage the system? Is it easy to work with support?
Development: How easy is it to cunstomize? Can you make meta changes from the user interface, or do you need a coding expert to make all changes? Do your developers know how to code in the language it uses? If not, how hard is it to find qualified developers, or train yours? Are the API's well written and robust?
If you ask all of these questions and are comfortable with the vendors answers, you can't go wrong. We use a spreadsheet that asks these questions and weights the scores giving us a result. Using the CLOUD score really helps us make the right decisions and avoid problems.
Friday, May 4, 2012
Stop micromanaging your network
Are you a micro-manager? I don't mean with your staff, with your network? Everyone knows that micro managing causes a drain on energy and efficiency with teams, but did you know it can do the same to your LAN?
In some networks, management traffic like SNMP, netflow and ICMP can use 30% of the bandwidth and can actually cause some of the issues you are trying to stop. Partly this is because of the broken paradigm we use to manage networks. We configure and manage everything separately.
What we really want is a way to communicate with the network and describe the behavior we want, and then let the devices work together to "make it so".
Imagine that you use SAP. (OK many of you do use SAP, so that's not too hard to do right?) SAP runs your company and is obviously very important. Now imagine you could tell your network, the whole network not device by device, that SAP was important so treat it as important.
Now maybe peer to peer traffic isn't important so you don't want to have that take up all of your resources, but if the resources are just sitting there doing nothing but costing you money, let it be used. Some traffic you just may not want on the network ever, either because you don't use it and want to mitigate risks, or it violates a regulation.
As new applications came on that are not classified and start to get used, the network should be smart enough to let you know. "Hey I've seen a lot of traffic using a new application called skype. What do you want me to do with it?"/ and you could communicate back, block it, make it important, make it un-important, and the network would know what that means, and configure itself to do that.
I think this is the future of network management. What do you think? Using things like onefabric, isaac and coreflow2 switches, we are well on the way to this vision of the future being a reality. Learn more by going to www.enterasys.com, or ask me.
In some networks, management traffic like SNMP, netflow and ICMP can use 30% of the bandwidth and can actually cause some of the issues you are trying to stop. Partly this is because of the broken paradigm we use to manage networks. We configure and manage everything separately.
What we really want is a way to communicate with the network and describe the behavior we want, and then let the devices work together to "make it so".
Imagine that you use SAP. (OK many of you do use SAP, so that's not too hard to do right?) SAP runs your company and is obviously very important. Now imagine you could tell your network, the whole network not device by device, that SAP was important so treat it as important.
Now maybe peer to peer traffic isn't important so you don't want to have that take up all of your resources, but if the resources are just sitting there doing nothing but costing you money, let it be used. Some traffic you just may not want on the network ever, either because you don't use it and want to mitigate risks, or it violates a regulation.
As new applications came on that are not classified and start to get used, the network should be smart enough to let you know. "Hey I've seen a lot of traffic using a new application called skype. What do you want me to do with it?"/ and you could communicate back, block it, make it important, make it un-important, and the network would know what that means, and configure itself to do that.
I think this is the future of network management. What do you think? Using things like onefabric, isaac and coreflow2 switches, we are well on the way to this vision of the future being a reality. Learn more by going to www.enterasys.com, or ask me.
Monday, April 30, 2012
My thoughts on this "Do You Have Klout? Employers Want To Know"
So Wired, Forbes and well everyone is talking about this article. Basically A guy applied for a job as a VP at a large marketing firm and got passed over because his Klout score was a 34. They hired someone with a 67.
Well that's how the story spins it, but the piece everyone seems to be forgetting is when they asked about his klout score, the guy had no idea what klout was. Now clearly not everyone follows the social media space that closely and there are a lot of sites that measure your social media influence, klout.com, peerindex.com, kred.com and those are the ones that are top of mind for me. If I looked I bet I could find another dozen easily.
Klout though is the biggest one and for a VP of marketing to not be aware of it, seems like a big miss. Maybe he has 15 years of experience, but if it was traditional print marketing and they are looking for a social marketing expert, I can see why they passed. He didn't sound like a good fit.
Now I'm not in marketing, I'm an IT guy, but if I was asked the klout question, my answer would be different.
"Well my klout score is currently 42, and while that's not as high a score as I think I deserve, the reason it is lower than I think is because klout currently only ranks, facebook, twitter and google plus. I spend a lot of time on linkedin which I think has more business relevance than facebook. In fact according to a recent study by hubspot linkedin is 4X more effective than twitter and 7x more effective than facebook on visit to lead conversions. I think when linkedin.com influence is included I would be more comparable to a mid 50"
That shows I understand how klout works, what it is, and can speak intelligently on why I like it and don't like it. Now maybe they still want someone who is a social medial rockstar with a score to match, or maybe they disagree that linkedin.com is a valid way to do business, or maybe they just want someone who tweets way more than I do.
Either way I think that's a better answer than "I don't know what klout is". Even if I didn't know what klout was, I would have asked a lot of questions on why they think it is relevant and how it compared to other scoring systems.
In summary I think the reason the guy wasn't hired was his lack of knowledge on social media and now really the fact that his klout score was lower. My opinion of course since I wasn't there...
Well that's how the story spins it, but the piece everyone seems to be forgetting is when they asked about his klout score, the guy had no idea what klout was. Now clearly not everyone follows the social media space that closely and there are a lot of sites that measure your social media influence, klout.com, peerindex.com, kred.com and those are the ones that are top of mind for me. If I looked I bet I could find another dozen easily.
Klout though is the biggest one and for a VP of marketing to not be aware of it, seems like a big miss. Maybe he has 15 years of experience, but if it was traditional print marketing and they are looking for a social marketing expert, I can see why they passed. He didn't sound like a good fit.
Now I'm not in marketing, I'm an IT guy, but if I was asked the klout question, my answer would be different.
"Well my klout score is currently 42, and while that's not as high a score as I think I deserve, the reason it is lower than I think is because klout currently only ranks, facebook, twitter and google plus. I spend a lot of time on linkedin which I think has more business relevance than facebook. In fact according to a recent study by hubspot linkedin is 4X more effective than twitter and 7x more effective than facebook on visit to lead conversions. I think when linkedin.com influence is included I would be more comparable to a mid 50"
That shows I understand how klout works, what it is, and can speak intelligently on why I like it and don't like it. Now maybe they still want someone who is a social medial rockstar with a score to match, or maybe they disagree that linkedin.com is a valid way to do business, or maybe they just want someone who tweets way more than I do.
Either way I think that's a better answer than "I don't know what klout is". Even if I didn't know what klout was, I would have asked a lot of questions on why they think it is relevant and how it compared to other scoring systems.
In summary I think the reason the guy wasn't hired was his lack of knowledge on social media and now really the fact that his klout score was lower. My opinion of course since I wasn't there...
Monday, April 23, 2012
Network spring cleaning...
Well Spring is finally here, at least in Boston. Spring is that time to look around and do some of those cleanup tasks that always get skipped. So here is my top 5 spring IT tasks.
5. Check for zombie devices. You know which ones I mean right? The server that should have been retired 3 years ago but never seems to actually get turned off. Everyone has some of these devices. I’ve got apache web servers that we “retired” years ago, but they are still online. Some of them are so old and shaky we have to restart the service every 5 minutes to “keep it working”. Clearly they should just go away. My goal is to review all the devices in my network and see what should go away.
4. Review usage reports. Do you have WAN links or uplinks that are constantly running at 90%. Probably need to upgrade them. Or do you have a few ports that constantly generate errors. Maybe not enough to cause an alarm, but enough that you should fix them. It could be as easy as a bad patch cable and help solve some of those weird issues that pop up every few months. I’m also a fan of walking through the data center and closets looking for red lights. Sometimes people miss the alert that goes out and the next thing you know the second drive in the RAID set went bad and you just lost data.
3. Update and test your DR plan. If you have a DR plan that hasn’t been tested, it won’t work. They never work the first time you try it. Never. Run a test and figure out what isn’t going to work before you need it. Along with this, check the business continuity type things, like redundant power supplies actually going to different circuits. If they both plug into the same power strip they aren’t done right.
2. Check backups. Not just to see if they have errors, actually compare it to the list of servers that are online and make sure that you are backing up, or at least aware of, anything that is online. Some systems may be online but not need to get backed up. Some active directory servers for example, or NIS slave servers and be rebuilt faster than restored anyway and they don’t store data. Not all AD servers are like this. If you aren’t sure back it up.
1. Check firmware and upgrade if needed. There are two schools of thought on this. “If it aint broke don’t fix it” and “Newer is better”. In my opinion, newer has better features which generally make life better, but be smart and make sure you understand and test the better features to make sure you are ready for them.
I’m sure everyone has their own list of maintenance that they want to do as well. If you want to add ideas, I’d love to hear them.
5. Check for zombie devices. You know which ones I mean right? The server that should have been retired 3 years ago but never seems to actually get turned off. Everyone has some of these devices. I’ve got apache web servers that we “retired” years ago, but they are still online. Some of them are so old and shaky we have to restart the service every 5 minutes to “keep it working”. Clearly they should just go away. My goal is to review all the devices in my network and see what should go away.
4. Review usage reports. Do you have WAN links or uplinks that are constantly running at 90%. Probably need to upgrade them. Or do you have a few ports that constantly generate errors. Maybe not enough to cause an alarm, but enough that you should fix them. It could be as easy as a bad patch cable and help solve some of those weird issues that pop up every few months. I’m also a fan of walking through the data center and closets looking for red lights. Sometimes people miss the alert that goes out and the next thing you know the second drive in the RAID set went bad and you just lost data.
3. Update and test your DR plan. If you have a DR plan that hasn’t been tested, it won’t work. They never work the first time you try it. Never. Run a test and figure out what isn’t going to work before you need it. Along with this, check the business continuity type things, like redundant power supplies actually going to different circuits. If they both plug into the same power strip they aren’t done right.
2. Check backups. Not just to see if they have errors, actually compare it to the list of servers that are online and make sure that you are backing up, or at least aware of, anything that is online. Some systems may be online but not need to get backed up. Some active directory servers for example, or NIS slave servers and be rebuilt faster than restored anyway and they don’t store data. Not all AD servers are like this. If you aren’t sure back it up.
1. Check firmware and upgrade if needed. There are two schools of thought on this. “If it aint broke don’t fix it” and “Newer is better”. In my opinion, newer has better features which generally make life better, but be smart and make sure you understand and test the better features to make sure you are ready for them.
I’m sure everyone has their own list of maintenance that they want to do as well. If you want to add ideas, I’d love to hear them.
Friday, March 2, 2012
Please no more cloud FUD
Even before I read about the Azure outage I knew some where someone had a cloud outage. I could tell because there seemed to be an uptick in the number of "I told you cloud wouldn't work" articles, tweets and blog posts. Please no more...
Now I don't work at Microsoft and don't have any secret knowledge about what happened, but reading the public posts, it sort of sounds like a leap year bug caused "service management to go down". I suspect during the fixing of this, some other issues were caused that impacted performance and caused intermittent stability.
Now I don't use Azure but "Service management" sort of sounds to me like any existing service would continue to work, but new ones can't be brought up. If that's the case that's not a real big deal. Admittedly it would stink if I was planning to launch my new hot startup on 3/1 and couldn't bring production online, but I've got to think that's pretty rare.
It's hard to disagree that a leap year bug shouldn't have been missed, but hey I've let some stuff slip through that in hindsight should have been caught. I mean who hasn't done "reboot" or worse "shutdown" hit enter and then said "Damn wrong window". Mistakes happen.
Mistakes happen in our own data centers too folks. Anyone that honestly has never had an outage either runs a "data center" consisting of an Xbox, Wii and Pentium PC in their parents basement, or makes so few changes that they are still running Sunos 4.1.3 because they aren't done testing that new Solaris stuff.
OK maybe there are a few folks that have been really lucky, but in today's environment we need to move fast. That means mistakes are going to happen.
Last year, or maybe two years ago now, we actually took quite a few servers down in our data center because of power. We actually have complete power redundancy and this should never have happened. Dual feeds, dual switch gear, generators, UPS, etc. The power even takes a different path through most of the building. Each cabinet has 2 (or 4) PDU's.
So what did we do? Well an administrator plugged in his servers and plugged them into 2 PDU's, one in the front, and one in the back. Unfortunately the redundancy is left and right. So even though it was in two PDU's they were both on A power.
We had to take one of the UPSes offline for maintenance and since we know we have redundant power we did this at noon. Looking back, not a great call. But it also wasn't the end of the world. We learned from it, corrected our mistakes and moved on.
No one said "See I told you we shouldn't have hired Rich". Well not that I heard anyway. My point is we all have outages, we all make mistakes, let's just stop with the silly "See cloud isn't reliable" every time someone has an outage.
Now I don't work at Microsoft and don't have any secret knowledge about what happened, but reading the public posts, it sort of sounds like a leap year bug caused "service management to go down". I suspect during the fixing of this, some other issues were caused that impacted performance and caused intermittent stability.
Now I don't use Azure but "Service management" sort of sounds to me like any existing service would continue to work, but new ones can't be brought up. If that's the case that's not a real big deal. Admittedly it would stink if I was planning to launch my new hot startup on 3/1 and couldn't bring production online, but I've got to think that's pretty rare.
It's hard to disagree that a leap year bug shouldn't have been missed, but hey I've let some stuff slip through that in hindsight should have been caught. I mean who hasn't done "reboot" or worse "shutdown" hit enter and then said "Damn wrong window". Mistakes happen.
Mistakes happen in our own data centers too folks. Anyone that honestly has never had an outage either runs a "data center" consisting of an Xbox, Wii and Pentium PC in their parents basement, or makes so few changes that they are still running Sunos 4.1.3 because they aren't done testing that new Solaris stuff.
OK maybe there are a few folks that have been really lucky, but in today's environment we need to move fast. That means mistakes are going to happen.
Last year, or maybe two years ago now, we actually took quite a few servers down in our data center because of power. We actually have complete power redundancy and this should never have happened. Dual feeds, dual switch gear, generators, UPS, etc. The power even takes a different path through most of the building. Each cabinet has 2 (or 4) PDU's.
So what did we do? Well an administrator plugged in his servers and plugged them into 2 PDU's, one in the front, and one in the back. Unfortunately the redundancy is left and right. So even though it was in two PDU's they were both on A power.
We had to take one of the UPSes offline for maintenance and since we know we have redundant power we did this at noon. Looking back, not a great call. But it also wasn't the end of the world. We learned from it, corrected our mistakes and moved on.
No one said "See I told you we shouldn't have hired Rich". Well not that I heard anyway. My point is we all have outages, we all make mistakes, let's just stop with the silly "See cloud isn't reliable" every time someone has an outage.
Wednesday, February 15, 2012
Thinking about going cloud? Have you asked these questions.
We use a lot of cloud applications and recently started asking a lot of questions. Frankly not all cloud applications or vendors are created equally and spending some time understanding what they really do can help avoid a disaster later.
This is the list of questions we ask. We send this list out and then do an hour or so phone call to review the answers with the vendors. We then use these answers to rank them in a weighted spreadsheet to help us make our decision. We also add in things like company relationship, user testing etc, but those aren't really things we ask the vendors about.
Anyway here is the list. I'd love feedback on what others ask.
Disaster Recovery and Business Continuity
Do you have redundant sites designed for auto-failover?
How long does it take for the redundant site to take over.
Does this include the time to decide to fail over?
What kind of RTO/RPO are in place and are they actually tested against?
Do you have geographic redundancy?
Can you restore accidentally deleted or corrupted data? How far back can you restore from?
What impact does a failed HD, server, cabinet, switch, data center have?
E-discovery
Is it possible?
Can we do legal holds by user, file, keyword?
Can we get access to “access logs” in the event we need to?
If so how far back can we get?
What does it show us?
Can we see who our users are sharing with?
If so can we easily remove access from an enterprise level?
Stability
Do you have a site like trust.salesforce.com for transparent operations?
Is it automatically updated with outages or performance alers?
Is code/data in escrow? If so how often does it get updated?
What is the migrate out plan like?
Can we request a backup of our data including any customizations?
Company financials
Are you private or publicly owned?
Are you cash flow positive? If not what is the cash burn rate and reserve?
Are you adding new customers? How many?
Do you track your NPS (Net Promoter Score)?
Authentication
Do you support automatic provisioning and de-provisioning of user accounts?
Do you support LDAP.RADIUS or even better SAML authentication and authorization back to us?
Do you use encryption? If so is it for data in flight, at rest or both? What kind of encryption is it?
Compliance and Privacy
Do we get notified of an investigation?
Can our data be seized as part of another companies investigation?
Is our data recoverable by your organization?
Do you have an SSAE16 or ISAE3402?
Are we allowed to have our third party auditors (or internal auditors) to audit your organization?
Contract
Please attach a copy of our master services agreement, terms and conditions or other contracts that we are using.
If you get bought by a competitor can I get my data out and go?
Are there financial penalties for service level agreement failure.
Are maximum increases baked in?
How much notice do you need to give us to terminate?
How much notice do we need to give them if we want to leave? I
Does the contract auto-renew? If so what are the terms?
Performance
Are you globally load balanced? If so explain.
Do you use Akamai or other CDN for better performance?
Who do you use for WAN connectivity?
Do you offer “offline” ability? If so it is automatic, or does the user need to know that they will be offline and plan accordingly?
Development
Do you offer built in integration tools to existing systems like SAP, salesforce.com, etc.
If not, how hard is it to build them?
What toolset is used for “custom development”
Support
Are you staffed 24/7?
Can we proactively request assistance if we are doing something off hours?
Is it onsite, email, phone, web or all?
What sort of response time is available?
What is the average tenure of the tier1 staff?
Is there a public knowledgebase available? Is it the same as the internal one or is it filtered?
Can anyone from Enterasys call, or do we only get a certain amount of “authorized users”?
Architecture
How quickly do new features show up?
Do we need to do anything or do we “magically” get them?
How much notice do we get for training users?
Is the system a true multitenant system?
Do you support multiple clients, like iphone, android, blackberry as well as tablets?
Is it strictly HTML5/browser based? If so which browsers and versions are supported?
Administration
Does the system support delegated administration?
How easy is it to automate tasks?
Can we apply roles to groups?
Do we get visibility into what is shared outside of the company, or what access has been granted to third party applications?
Can we enforce enterprise wide restrictions?
This is the list of questions we ask. We send this list out and then do an hour or so phone call to review the answers with the vendors. We then use these answers to rank them in a weighted spreadsheet to help us make our decision. We also add in things like company relationship, user testing etc, but those aren't really things we ask the vendors about.
Anyway here is the list. I'd love feedback on what others ask.
Disaster Recovery and Business Continuity
Do you have redundant sites designed for auto-failover?
How long does it take for the redundant site to take over.
Does this include the time to decide to fail over?
What kind of RTO/RPO are in place and are they actually tested against?
Do you have geographic redundancy?
Can you restore accidentally deleted or corrupted data? How far back can you restore from?
What impact does a failed HD, server, cabinet, switch, data center have?
E-discovery
Is it possible?
Can we do legal holds by user, file, keyword?
Can we get access to “access logs” in the event we need to?
If so how far back can we get?
What does it show us?
Can we see who our users are sharing with?
If so can we easily remove access from an enterprise level?
Stability
Do you have a site like trust.salesforce.com for transparent operations?
Is it automatically updated with outages or performance alers?
Is code/data in escrow? If so how often does it get updated?
What is the migrate out plan like?
Can we request a backup of our data including any customizations?
Company financials
Are you private or publicly owned?
Are you cash flow positive? If not what is the cash burn rate and reserve?
Are you adding new customers? How many?
Do you track your NPS (Net Promoter Score)?
Authentication
Do you support automatic provisioning and de-provisioning of user accounts?
Do you support LDAP.RADIUS or even better SAML authentication and authorization back to us?
Do you use encryption? If so is it for data in flight, at rest or both? What kind of encryption is it?
Compliance and Privacy
Do we get notified of an investigation?
Can our data be seized as part of another companies investigation?
Is our data recoverable by your organization?
Do you have an SSAE16 or ISAE3402?
Are we allowed to have our third party auditors (or internal auditors) to audit your organization?
Contract
Please attach a copy of our master services agreement, terms and conditions or other contracts that we are using.
If you get bought by a competitor can I get my data out and go?
Are there financial penalties for service level agreement failure.
Are maximum increases baked in?
How much notice do you need to give us to terminate?
How much notice do we need to give them if we want to leave? I
Does the contract auto-renew? If so what are the terms?
Performance
Are you globally load balanced? If so explain.
Do you use Akamai or other CDN for better performance?
Who do you use for WAN connectivity?
Do you offer “offline” ability? If so it is automatic, or does the user need to know that they will be offline and plan accordingly?
Development
Do you offer built in integration tools to existing systems like SAP, salesforce.com, etc.
If not, how hard is it to build them?
What toolset is used for “custom development”
Support
Are you staffed 24/7?
Can we proactively request assistance if we are doing something off hours?
Is it onsite, email, phone, web or all?
What sort of response time is available?
What is the average tenure of the tier1 staff?
Is there a public knowledgebase available? Is it the same as the internal one or is it filtered?
Can anyone from Enterasys call, or do we only get a certain amount of “authorized users”?
Architecture
How quickly do new features show up?
Do we need to do anything or do we “magically” get them?
How much notice do we get for training users?
Is the system a true multitenant system?
Do you support multiple clients, like iphone, android, blackberry as well as tablets?
Is it strictly HTML5/browser based? If so which browsers and versions are supported?
Administration
Does the system support delegated administration?
How easy is it to automate tasks?
Can we apply roles to groups?
Do we get visibility into what is shared outside of the company, or what access has been granted to third party applications?
Can we enforce enterprise wide restrictions?
Subscribe to:
Posts (Atom)