tag:blogger.com,1999:blog-70135334797663426392024-03-14T07:40:35.516-07:00Share the PointDiscussion on collaboration, Cloud and computing. bob hookerhttp://www.blogger.com/profile/04097911020395990362noreply@blogger.comBlogger1186125tag:blogger.com,1999:blog-7013533479766342639.post-32318748947282416592016-12-19T11:19:00.001-08:002016-12-19T11:19:55.092-08:00Three Object Stores: the Good, the Bad and the Ugly<table align="center" cellpadding="0" cellspacing="0" class="tr-caption-container" style="margin-left: auto; margin-right: auto; text-align: center;"><tbody>
<tr><td style="text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEj7MysG4d9GnREeo1ZYA7rOpVdq_16vICXRV9Z4X2BXPbtf3hVaW7UyhZBljl3JQCUuVG7a_kt9vLabsdccn7IQ7lS-4eUA3aymjcww96bAWpcXgFT-mi3clXeFmfaloUozmeiICgsN/s1600/aws.tiff" imageanchor="1" style="margin-left: auto; margin-right: auto;"><img border="0" height="378" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEj7MysG4d9GnREeo1ZYA7rOpVdq_16vICXRV9Z4X2BXPbtf3hVaW7UyhZBljl3JQCUuVG7a_kt9vLabsdccn7IQ7lS-4eUA3aymjcww96bAWpcXgFT-mi3clXeFmfaloUozmeiICgsN/s640/aws.tiff" width="640" /></a></td></tr>
<tr><td class="tr-caption" style="text-align: center;">AWS S3 Object Storage</td></tr>
</tbody></table>
<div class="separator" style="clear: both; text-align: left;">
I have been looking at the different Object storage cloud services. Don't worry if you don't know what Object storage is, only think of it as a way to store lots of buckets or containers. These buckets or containers are only one level deep. This makes them very cheap and its the better way to store you documents online that are write once and read many. So documents getting lots of read and writes should stay in SharePoint, but these documents may get lots of reads, like a web site or massive backup or archive store.</div>
<div class="separator" style="clear: both; text-align: left;">
<br /></div>
<div class="separator" style="clear: both; text-align: left;">
I won't go on and on like I sometimes do at home about all the great things Object storage can do. I will just give you an overview as kind of a power user and designer.</div>
<div class="separator" style="clear: both; text-align: left;">
<br /></div>
<div class="separator" style="clear: both; text-align: left;">
<b>Above is the AWS S3 storage for Object storage.</b> It sets the standards, look at all those ready to configure features. You can directly host as a static web page, and that means JavaScript web page people. And rules to lower cost storage right there, what is there not to love.</div>
<br />
<table align="center" cellpadding="0" cellspacing="0" class="tr-caption-container" style="margin-left: auto; margin-right: auto; text-align: center;"><tbody>
<tr><td style="text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEh94IqhPdDh7asmFXin5G1etSRENrZyHKTDse9oKxNjMf59JLaNXg1uuwYlmYWyJbI-Q0P6gpmbYDJRuNNxCsR5hYTVliMWXAdbmTwuckgVujXNL1v5DBeAiBzWDT9sN0Lhvq29_81W/s1600/IBM.tiff" imageanchor="1" style="margin-left: auto; margin-right: auto;"><img border="0" height="386" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEh94IqhPdDh7asmFXin5G1etSRENrZyHKTDse9oKxNjMf59JLaNXg1uuwYlmYWyJbI-Q0P6gpmbYDJRuNNxCsR5hYTVliMWXAdbmTwuckgVujXNL1v5DBeAiBzWDT9sN0Lhvq29_81W/s640/IBM.tiff" width="640" /></a></td></tr>
<tr><td class="tr-caption" style="text-align: center;">IBM Bluemix Object Storage, and little else</td></tr>
</tbody></table>
<div class="separator" style="clear: both; text-align: center;">
<span id="goog_285623228"></span><span id="goog_285623229"></span><br /></div>
<div class="separator" style="clear: both; text-align: left;">
<b>IBM Bluemix has a nice Object Storage </b>with a nice overview interface, tells you how much the Enterprise is storing is nice. But beyond that its not much really.</div>
<br />
<table align="center" cellpadding="0" cellspacing="0" class="tr-caption-container" style="margin-left: auto; margin-right: auto; text-align: center;"><tbody>
<tr><td style="text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiUp-8cPi2Di_OwoX5BfxKI2TLfjczz89MC2TkMI16-r9wxrnQDgCDi8ZXHWzHa4lWlBiLCupsUfqrSrKhyphenhyphenwutg3nToqe_QnmtRTTEo_IEqxiRvQQCuMybX6DYvK1Vfm450Ti-498D8/s1600/ms.tiff" imageanchor="1" style="margin-left: auto; margin-right: auto;"><img border="0" height="380" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiUp-8cPi2Di_OwoX5BfxKI2TLfjczz89MC2TkMI16-r9wxrnQDgCDi8ZXHWzHa4lWlBiLCupsUfqrSrKhyphenhyphenwutg3nToqe_QnmtRTTEo_IEqxiRvQQCuMybX6DYvK1Vfm450Ti-498D8/s640/ms.tiff" width="640" /></a></td></tr>
<tr><td class="tr-caption" style="text-align: center;">Okay I know this is Azure, and it seems I will need to pay something now</td></tr>
</tbody></table>
<div class="separator" style="clear: both; text-align: center;">
<br /></div>
<div class="separator" style="clear: both; text-align: left;">
I don't know what to think about storage in Azure. I think this above is how you would set up Azures alternative to AWS Object storage. Really I am not sure and I am going to have to pay something to find out. This I think comes just as part of Microsoft double strategy of hybrid Cloud and Platform to Services a Service patterns. Though Object store is a Platform it is a pretty low level one, now much consulting revenue down the road and Microsoft indifference to this space shows. </div>
<div class="separator" style="clear: both; text-align: left;">
<br /></div>
<div class="separator" style="clear: both; text-align: left;">
What I first though when I started looking at Cloud storage is that outside of SQL server Microsoft had one answer: Office 365 especially OneDrive and SharePoint Online.</div>
<div class="separator" style="clear: both; text-align: left;">
<br /></div>
<div class="separator" style="clear: both; text-align: left;">
To be just OneDrive does offer an answer and an answer that probably will work most of the time. The focus is more on the customers. Object storage is in a way a competition to Office and SharePoint. I could very well skip rolling out full Office 365 to give my users Object storage spaces. I would myself first load massive shared files of little understood value in Object storage rather than OneDrive.</div>
<div class="separator" style="clear: both; text-align: left;">
<br /></div>
<div class="separator" style="clear: both; text-align: left;">
And at this point, Object Storage is Amazon Web Services. </div>
<div class="separator" style="clear: both; text-align: left;">
<br /></div>
<div class="separator" style="clear: both; text-align: left;">
And the future of data store? </div>
<div class="separator" style="clear: both; text-align: left;">
<br /></div>
<div class="separator" style="clear: both; text-align: left;">
Okay here is the prize, a wild speculation on the kind of data store you could make here. A massive data store with the files entirely store in JSON. A node set of bots. The bots can handle all channels of request, from simple enterprise search and ECM storage to voice requests or IM requests, to email help systems. You can have your companies main data in semi-structured form accessible via a wide range of channels and enhanced with cognitive technology or running Spark machine learning applications.</div>
<div class="separator" style="clear: both; text-align: left;">
<br /></div>
<div class="separator" style="clear: both; text-align: left;">
<br /></div>
<br />bob hookerhttp://www.blogger.com/profile/04097911020395990362noreply@blogger.com0tag:blogger.com,1999:blog-7013533479766342639.post-48254349779306491512016-12-19T05:46:00.004-08:002016-12-19T05:46:44.225-08:00Server-less, the ultimate Cloud destination<blockquote class="twitter-tweet" data-lang="en">
<div dir="ltr" lang="en">
"Server-less, the ultimate Cloud destination" <a href="https://t.co/DIz3p0ig1f">https://t.co/DIz3p0ig1f</a> by <a href="https://twitter.com/bob_hooker">@bob_hooker</a> on <a href="https://twitter.com/LinkedIn">@LinkedIn</a></div>
— (((Bob))) (@rober1236Jua) <a href="https://twitter.com/rober1236Jua/status/810810967567335424">December 19, 2016</a></blockquote>
<br />
<br />
Last post on Cloud conversion dealt with dealing with massive migration business logic, and I suggested you try and manage complexity by breaking your information worker tasks in to those you don't understand and are custom, and those that are general tools leverage by users. General tools that give users freedom should be managed by SaaS, the most famous being Office 365 and Salesforce. The others should be migrated to IaaS in mass to reduce complexity of migration. If you are not happy with this simply model you need to budge at 6 month to 1 year application rationalization and conversion project.<br /><br />I am going to skip that for a later post and concentrate now on how to make new things with a Cloud.<br /><br />You will be migrating your existing systems to IaaS VMs, but for new solutions you will find that the best thing to do is PaaS, where you consume code or data storage without having to worry about infrastructure.<br /><br />To do this you use the state of the art framework called Serverless Architecture. This will be nothing new to experienced web developer. If you create something on GoDaddy you get some code and you load it up. You configure a MySQL or NoSQL store or log file for data storage, and you just let it run.<br /><br />Traditionally this has been the test and dev world for developers, and as soon as an application work it was often moved to a Enterprise hosting solution where a set of servers needed to be defined to run the different layers of the application. A coder who just wrote a bunch of code now had to think about breaking logic and data up to sit in layers, and the specifications for the layers. Other experts had to harden the servers and as you could now install .exe code people rushed to create add ons to give the servers better performance at the cost of vendor or even server lock in.<br /><br />Well with Amazon products like Lambda for storing code logic, S3 Object storage to create scalable storage without servers, and DynamoDB, Redshift and RDS you can build a scalable solution without ever defining the servers.<br /><br />Yes servers still exist, but it is AWS that worry about the servers. You also have the added benefit that no one on the planet can connect the servers running and the code you have created. This provides great deal of security as human attacks on the server farm can't get your stuff, or even find it.<br /><br />Personally I think the best part of Serverless design is that experienced web developers will have to learn next to nothing. All the AWS tools are easier to use than the alternative server based solution. Coders can concentrate on defining the logic, the data and being sure that the solution is responsive enough by design. AWS will provision new CPUs and SSD as needed, you won't even see it.<br /><br />This is far cheaper and easier to maintain than legacy systems that sit on boxes.<br /><br />And what is the negative, well there is a degree of vendor buy-in with deploying systems this way that does not happen when you install code on VM in the Cloud running standard OSs.<br /><br />I personally am not so worried about his because as the effort to create new code becomes shorter Enterprises will do what web developers who hosted on IPs will have done long ago, develop quickly and make solutions that are easy to migrate. Also with the expanding pace of digital transformation the life-cycle of any bit of code will start to be shorted than your hosting agreements with AWS.<br /><br />There are some political issues to worry about. As a manager you have to be a bit more aware that certain people might not be comfortable with change. Don't ask an assessment of server free design from the people's who make a living hardening servers, they will find everything wrong with it.<br /><br />Rather it might be smart to start building your team around security, architecture, code and UX; with the traditional role of networks and infrastructure being reduced over time.<br /><br />You should start reducing the time an effort between a desire in your staff and a tool. Everyone sort of becomes a developer. You don't have to wait 6 weeks to get some boxes built or permission to expand the VM estate, you just press some buttons.<br /><br />Make sure that when you start you have an empowered Serverless team with a budget, they need to be able to say yes to things. They also need to be fail first and fail fast kind of people as you don't have to buy expensive servers to try something.<br /><br />So what is it all about?<br /><br />Well after telling the Why now its time for the what.<br /><br />Put simply, server-less is building your solution bases on SaaS or PaaS elements rather than hosting them on Virtual Machines.<br /><br />So for example if you have some code you want to run in a web server in the Cloud. The dumb thing to do is to by a Instance of EC2 the size you need and load the code on to that. It cost more and you have to do a great deal of configuration. Using Containers like Docker reduce the cost but you now have to manage a container service and still manage you containers as you would on-premise.<br /><br />If you know AWS you might think to deploy your code in Elastic BeanStalk, which is a better option. You can store you persistent code on cheap Object S3 storage rather than EBS, and you only start up tiny web servers when the code is needed. But still Elastic Beanstalk will create load balancers, EC2 instances and S3 for you, and if you solution is not well written or heavily used you may end spending the same as just hosting it on EC2 with EBS attached storage.<br /><br />Rather load your code up to Lambda. you create a Lambda function, define the underlying engine and provide the code directly to it along with instances and interfaces.<br /><br />For front ends the user needs to face rather than creating conplex server side pages create HTML 5 pages with JavaScript. If you call WebSockets to call your Lambda functions via an API gateway. This way you can store you site on S3 Object storage. Data can be stored on PaaS like DynamoDB, Redshift or RDS.<br /><br />So there is you have it, fairly <br />
<script async="" charset="utf-8" src="//platform.twitter.com/widgets.js"></script>
bob hookerhttp://www.blogger.com/profile/04097911020395990362noreply@blogger.com0tag:blogger.com,1999:blog-7013533479766342639.post-3526997534862085902016-12-16T03:47:00.002-08:002016-12-16T03:47:53.776-08:00Office 365 vs AWSI am not talking here of the task of AWS vs Azure, but the fully SaaS Office 365 vs the PaaS and IaaS of AWS.<br />
<br />
These 'opinions' I have been gained by hard experience, and though things are changing I think I am coming to close to a general set of principles about how larger enterprises should work.<br />
<br />
If you are a start up you can stop reading here, start up has massively unique opportunities to save money with technology that a bank or government department will not have. I am talking about medium to large established companies and agencies with established IT.<br />
<br />
Firstly just migrating existing VM and containers to the Cloud as IaaS is not going to save you much money. I have seen this at both ends, in the detailed planning phase for migration with both AWS and Microsoft Azure and working with a live IaaS system that hosted all the servers of a major enterprise.<br />
<br />
Right up front I will tell you that if you move all your servers to IaaS either AWS and Azure and do nothing else, you are going to not see much difference between on premise and Cloud. For firms that consume managed services the two are going to be pretty much the same, you get a bill and the bill is going to be pretty much the same.<br />
<br />
So to get the benefit of Cloud you need to make transformations, and what I am seeing is that it is best to break your entire IT estate in to 2 major groups.<br />
<br />
I know officially what you are suppose to do is review the business case for each system you migrate over, deciding a final destination based on the application and rationalising the application before you migrate.<br />
<br />
In a live talk this is when you ask a room for of CIO and CTOs how many have a full understand of the business cases for their applications and the latest architecture they use.<br />
<br />
The reality is a data center is going to be full of lots of systems that are not fully understood to anyone in IT as a group. You may have certain people who fully understand a system or group of systems, but as you move out you inevitably get a poorer and poorer understanding.<br />
<br />
And lets be honest, you are unlikely to have staff or afford experts who have the skills to go to each team that manages a system, to get a full understanding of the business and technical parts and communicate accurately to management. <br />
<br />
The hard truth is that in established IT systems you can only do so much discovery, a full discovery is prohibitive by cost and time and frankly may not really even be possible. If you have been around for more than 10 years you have a great deal of legacy stuff maybe one guy remembers and each time you talk to the one guy he keeps harping on about....well we all work with technical experts don't we. <br />
<br />
<br />
What migration to the Cloud has to deal with is uncertainty. Uncertainty is just a part of life, it seems to be backed in to the very fabric of the Universe and IT, if anything, only increases it as systems become more complex. <br />
<br />
So what you need to think is 'what kind of uncertainty does this service face.'<br />
<br />
What I would suggest as a first pass is looking at specific vs general uncertainty. <br />
<br />
Specific uncertainty is what we usually always think about. A system sitting on a server is old, it has a wide range of users many sharing the same login access, and it lacks updated documentation. You know the system is doing something, but you can't be fully sure of what. It was designed for a specific task that may be only partially understood, and users are unable or unwilling to communicate and cooperate with anyone wanting to change their systems.<br />
<br />
We all know this.<br />
<br />
But there is a very different kind of uncertainty that we don't fully grasp. The uncertainty of what is in emails, SharePoint or Word documents, what is entered in the Salesforce.com of CRM systems or lives in SAP.<br />
<br />
We know a great deal about these systems as they are industrial standards, but because they are widely used applications, but you can't understand what is inside of them, how people are using them and what value they really create.<br />
<br />
These two types of uncertainly should be managed in two different ways in the Cloud.<br />
<br />
Traditionally AWS manages the first, you have a mass of VMs you know you need on your estate. So you migrate them to the Cloud, which in itself saves no money. So how do you save money?<br />
<br />
You look at the usage patterns and start modifying up time, CPU count, storage, bursting and commercial things like reserved or spot instances to save money. What you do in this you take the high level view looking at how the systems perform as servers to assign more agile systems to them. You also may migrate things to better platforms, ending a larger EC2 Windows server with IIS to run PHP to a BeanStalk with stores data on S3 and load balances micro servers to meet just in time demand.<br />
<br />
But what about SharePoint, Exchange, CRM, does this work?<br />
<br />
Here I would say the different kind of uncertainty means a different kind of road to cost savings. You know perfectly well how these systems are architected and what they do, and you could reduce costs, but you have an opportunity to leap frog all of that, and move to the most optimal Cloud hosting directly by moving to SaaS directly in the form of Office 365.<br />
<br />
In these system where you know the kind of tasks that people do, but have no idea the meaning to them of what they are doing and, as you would need to run two companies to know what everyone in the first is doing all the time with data, you probably are best just to start defining the roles that can use standard software. Actually as the skills of workers increase they tend to use more tools than forms, Excel, Word, PowerPoint and SharePoint are flexible platforms.<br />
<br />
Rather than migrating these servers my experience is you will save way more money pushing an all in with Office 365, and a major effort to see how may existing systems written with say .NET can be provided by SharePoint sites. <br />
<br />
So to sum up:<br />
<br />
<br />
<ul>
<li>If you have a lot of little boxes running code you don't fully understand for reasons that are unique to a community you are probably better migrating them in mass to AWS and working on reducing their consumption latter on by turing servers off, allowing autoscaling, and migration to better platforms.</li>
<li>If you have a massive system that many or all employees use for various different reasons, that is fully Enterprise, you are better looking at buy a SaaS replacement.</li>
</ul>
<div>
<br /></div>
<div>
The main point is that you can only really know so much about the details of your IT, and in only so much accuracy, you need to plan for moving things in mass without disruption, and then how you save money. </div>
bob hookerhttp://www.blogger.com/profile/04097911020395990362noreply@blogger.com8tag:blogger.com,1999:blog-7013533479766342639.post-78345496131976161092016-02-09T06:48:00.003-08:002016-02-09T06:48:34.789-08:00Tools for the Cloud: OneNote, Delve, Skype and SwayOne thing that makes me a bit frustrated is people using Office 365 to only deploy Office to use Exchange Online and Office Pro Plus.<br />
<br />
While certainly getting ride of your Exchange server online and up to 15 versions of Office for your users on different devices is a massive ROI, but the Cloud is a lot more than just reduced cost in old IT services, it opens up new IT possibility.<br />
<br />
And to embrace this there are 5 tools in Office 365, and my opinion on if they are of value or not.<br />
<br />
<ol>
<li><b>OneNote </b>Notebooks are an obvious new web application, essentially they are simple concept, a electronic notebook that you can post any time of information, that you can link to meetings, you can share and link from many devices. OneNote is Microsoft tool in this and it is so much more than just a new kind of Word. Think of it as Word 2.0. You can not only take notes but you can also share notes. If you do a Skype for business you can share a page from OneNote among the members and OneNote will even tell you who participated in the meeting. OneNote will like with Outlook so email invites and notifications with a OneNote page will update automatically.</li>
<li><b>Delve</b> Finally a real collaboration tool with real benefits. See the public slides and documents most shared and viewed by your close co-workers Delve is the ultimate collaboration system. It comes with Office 365 and lets you 'work like a network'. If you are using your Office 365 tenant as a primary source of data storage Delve can vastly improve how well informed workers are about what is going on.</li>
<li><b>Skype for Business. </b>Skype for Business is an amazing tool, the problem is that its hard not to feel like it is a spy tool. Workers are being watched by it constantly, if you print something out and review it for a half hour without touching your computer it goes grey. What I see is that when people use Skype for Business, or any presence tool really, they start filling their calendars up with exaggerated to bull-shit meetings and other things to keep their Skype for Business looking busy. I have learned to ignore the red and just phone people, most likely they are just calendar concealing what they are really doing. To be valuable Skype needs to tell people if it is a good time to call or not, but being the worst ever spy tool is not a way of doing this. This single one feature, if not re-assigned to give users more privacy, could doom the entire workload. That is sad because having a seamless flow from VOIP, to conferences, to email to IM is amazing. </li>
<li><b>Sway</b>, I have to be honest I don't get it. We need another PowerPoint tool? </li>
<li><b>PowerBI</b>, its just a trimmed down version of Excel held in to the limits of HTML5. I think you are better off learning PivotTables. </li>
</ol>
bob hookerhttp://www.blogger.com/profile/04097911020395990362noreply@blogger.com0tag:blogger.com,1999:blog-7013533479766342639.post-34679586284021540892015-08-11T02:51:00.001-07:002015-08-11T02:51:16.904-07:00SharePoint getting lost in the Cloud?My experience is that though most Office 365 users include SharePoint (sites) in their tenant, the real use is coming from Exchange Online, Office ProPlus, and OneDrive. <br />
<br />
Most people seems to think OneDrive settles the document storage needs.<br />
<br />
They are wrong in a number of ways.<br />
<br />
The most obvious problem is a OneDrive is that when you lose a staff, and end their license, all their documents go with them. <br />
<br />
What you need is a central place to put key documents and lists that you company needs beyond a single users. These documents you might want version controlled, assigned with metadata, and searchable.<br />
<br />
What you want is Sites which is SharePoint in Office 356. Better yet SharePoint with Delve, allowing your users to see the socially most significant documents in circulation.<br />
<br />
Planning a proper Sites configuration is not technically hard but it is a lot of work to create a good Information Architecture, that is a plan of sites and subsets.<br />
<br />
Here are some simple rules:<br />
<br />
<br />
<ol>
<li>Regardless of what anyone says the hard limit for supported Sites is 200 GB. So if you have a lot of content to store make many sites.</li>
<li>Don't rely on your company structure to provide the structure for the sites, rather find out what people need or let teams design they own layout.</li>
<li>Keep it clean and simple, don't worry too much about colours or new layouts. Spend effort on design of layout and making it easy to use over making it look a certain way.</li>
<li>Use Wikis, they are easy light weight way to store data.</li>
<li>Keep pushing users to it, if they have a question don't write an answer when a link in a wiki exists, have the search for it in the wiki. Get users to learn the independent way of looking for things, break the ask first habit.</li>
<li>Have people who have keeping SharePoint up to date and clean as part of their jobs.</li>
<li>Find energetic people who want to work with Sharepoint.</li>
</ol>
bob hookerhttp://www.blogger.com/profile/04097911020395990362noreply@blogger.com0tag:blogger.com,1999:blog-7013533479766342639.post-27735100686365152582015-08-11T02:27:00.000-07:002015-08-11T02:27:08.016-07:00Identity: Cloud for Sync vs AD FSLots of people using Office 356 seem to assume they just need AD FS. <br />
<br />
What AD FS gives you primarily is Single Sign On, this also enables you to connect your Office 365 to a number of other Cloud services provided by Microsoft like CRM and Azure.<br />
<br />
<b>But there is a cost of AD FS. To get this benefit you need to to build a 5 server farm, with load balancers.</b><br />
<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="http://4.bp.blogspot.com/-10u1SwiZTR0/T5Ym8340YTI/AAAAAAAAA1s/FgnU18mZ2uI/image_thumb%25255B5%25255D.png?imgmax=800" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" src="https://4.bp.blogspot.com/-10u1SwiZTR0/T5Ym8340YTI/AAAAAAAAA1s/FgnU18mZ2uI/image_thumb%25255B5%25255D.png?imgmax=800" /></a></div>
<br />
<b>This servers farm will create a number of single points of failure: load balancers, firewalls, web servers (2) of them and AD FS servers (2). </b> You need to create and manage these servers.<br />
<br />
Now if you use simple sync, using AADS or AADC or what ever it will be when you read this, you need only one server and all it does is updates identities from AD, including sending a HASH or a HASH of the password.<br />
<br />
So what it the difference for users. Users in the worst case without AD FS 2 you users log in to their computer, they then open the web page and log in again with the same credentials. The worst case is that they need to login twice. <b>Normally users just save their passwords so they only need to enter it when they change browsers or machines, or when their password changes.</b><br />
<br />
From a user perspective you get maybe 10 re-entries of a password THEY MUST KNOW to get on their computer in the first place. <b> With Federation you get rid of those 10 actions a year, actions the staff will know in every case how to manage, at the cost of a single point of failure and 5 boxes and 2 load balances.</b><br />
<br />
Frankly its hard to make the case.<br />
<br />
If management demands SSO I would suggest you go over the facts above, point out that servers like Twitter, Facebook, Hotmail, Gmail, Instagram, and Snap Chat work across devices without Single Sing On.<br />
<br />
You will save money and effort by treating Office 365 as what it is, a Cloud toolbob hookerhttp://www.blogger.com/profile/04097911020395990362noreply@blogger.com0tag:blogger.com,1999:blog-7013533479766342639.post-73700690345384619392015-08-11T01:55:00.001-07:002015-08-11T01:55:48.170-07:00Web 1 to Web 2 to Web 3<iframe src="http://www.slideshare.net/TotalSocialMedia/slideshelf" width="615px" height="470px" frameborder="0" marginwidth="0" marginheight="0" scrolling="no" style="border:none;" allowfullscreen webkitallowfullscreen mozallowfullscreen></iframe>bob hookerhttp://www.blogger.com/profile/04097911020395990362noreply@blogger.com0tag:blogger.com,1999:blog-7013533479766342639.post-68655127610455742282015-05-06T05:33:00.001-07:002015-05-06T05:33:17.607-07:00Understanding the Difference Between Microsoft Azure & Amazon AWS | Plur...<iframe allowfullscreen="" frameborder="0" height="270" src="https://www.youtube.com/embed/b9WQ4Fms-Ho" width="480"></iframe>bob hookerhttp://www.blogger.com/profile/04097911020395990362noreply@blogger.com0tag:blogger.com,1999:blog-7013533479766342639.post-10356481343181055942015-05-06T05:32:00.001-07:002015-05-06T05:32:20.132-07:00SharePoint 2013: Getting Started (Tutorial)<iframe allowfullscreen="" frameborder="0" height="270" src="https://www.youtube.com/embed/FO7oq4bzuo8" width="480"></iframe>bob hookerhttp://www.blogger.com/profile/04097911020395990362noreply@blogger.com0tag:blogger.com,1999:blog-7013533479766342639.post-62095606339894907752015-05-06T05:31:00.001-07:002015-05-06T05:31:57.311-07:00PowerShell Commands in SharePoint | Bestdotnettraining<iframe allowfullscreen="" frameborder="0" height="344" src="https://www.youtube.com/embed/Qo4-9VWG51I" width="459"></iframe>bob hookerhttp://www.blogger.com/profile/04097911020395990362noreply@blogger.com0tag:blogger.com,1999:blog-7013533479766342639.post-6845582002378433742015-05-06T05:29:00.001-07:002015-05-06T05:29:30.800-07:00Exam Prep: 70-331 and 70-332 - MCSE: SharePoint (Microsoft SharePoint Se...<iframe allowfullscreen="" frameborder="0" height="270" src="https://www.youtube.com/embed/e2_v7E2jjdE" width="480"></iframe>bob hookerhttp://www.blogger.com/profile/04097911020395990362noreply@blogger.com1tag:blogger.com,1999:blog-7013533479766342639.post-85137785461736382122015-04-17T03:02:00.000-07:002015-04-17T03:02:48.933-07:00Value of Adding a domain to Office 365 (way more than you might think)<div style="text-align: center;">
<iframe allowfullscreen="true" frameborder="0" height="180" marginheight="0" marginwidth="0" scrolling="no" src="http://hub.video.msn.com/embed/37d0daf3-e6ea-43fb-9898-3bacec41283e/?vars=bWt0PWVuLXVzJmJyYW5kPU1TX09mZmljZSZsaW5rYmFjaz1odHRwcyUzQSUyRiUyRnd3dy5iaW5nLmNvbSUyRnZpZGVvcyZsaW5rb3ZlcnJpZGUyPWh0dHBzJTNBJTJGJTJGc3VwcG9ydC5vZmZpY2UuY29tJTJGZW4tdXMlMkZhcnRpY2xlJTJGVmVyaWZ5LXlvdXItZG9tYWluLWluLU9mZmljZS0zNjUtNjM4M2Y1NmQtM2QwOS00ZGNiLTliNDEtYjVmNWE1ZWZkNjExJTNGdWklM0Rlbi1VUyUyNnJzJTNEZW4tVVMlMjZhZCUzRFVTJTI2ZnJvbUFSJTNEMSUyNnZpZGVvSWQlM0QlN0IwJTdEJTI2ZnJvbSUzRCZjb25maWdDc2lkPU1TTlZpZGVvJmNvbmZpZ05hbWU9c3luZGljYXRpb25wbGF5ZXImc3luZGljYXRpb249dGFnJmZyPXNoYXJlZW1iZWQtc3luZGljYXRpb24=" width="320"> <a href="https://support.office.com/en-us/article/Verify-your-domain-in-Office-365-6383f56d-3d09-4dcb-9b41-b5f5a5efd611?ui=en-US&rs=en-US&ad=US&fromar=1&videoid=37d0daf3-e6ea-43fb-9898-3bacec41283e&from=shareembed-syndication" target="_new" title="Video: Set up your domain in Office 365">MS_Office Video: Set up your domain in Office 365</A></iframe></div>
<br />
Adding a domain name to your Office 365 is a key part to making your People Centric Enterprise work. Its pretty simple to do, but it will give your firm a unified email domain while still working with Office in the Cloud. No more having to either maintain a an on-site Exchange Server or have to give people a gmail or hotmail address for your business.<br />
<br />
<br />
Its technically easy to do, as the video shows, but its worth thinking about how this all fits in the new People Centric Enterprise. <br />
<br />
Your domain name is more than just a company name, it should be a brand, a personality and identity that reflects something about what you want to tell the world. By being able to assign all your users names with your domain, the same domain as your web page, you create a Cloud based identity. Users can see that your web page, your Office 365 and your email and Lync are all part of a single surface that they can contact from any device anywhere.<br />
<br />
Having a single domain that for the web site and the internal messaging and collaboration builds a sense of unified working, where the people are not being made to fit in to boxes. Rather your domain becomes a large tent where your workers, your partners and your customers can find ways to communicate, learn and share around your business.bob hookerhttp://www.blogger.com/profile/04097911020395990362noreply@blogger.com1tag:blogger.com,1999:blog-7013533479766342639.post-17823345351523423472015-04-13T12:15:00.002-07:002015-04-13T12:15:42.239-07:00Ravello looks amazing<iframe allowfullscreen="" frameborder="0" height="360" src="https://www.youtube.com/embed/1W62OT1amfE" width="640"></iframe><br />
<br />
This the demo but can the cloud really be this easy? I am registering for a demo and will see.bob hookerhttp://www.blogger.com/profile/04097911020395990362noreply@blogger.com0tag:blogger.com,1999:blog-7013533479766342639.post-17894971902755086402015-03-27T05:17:00.000-07:002015-04-24T13:52:08.367-07:00The world of a SharePoint professional is about to change<iframe frameborder="0" height="355" scrolling="no" src="http://guides.officeignite.com:80/embed/5m" width="560"></iframe>
SharePoint IT generally involved a great deal of infrastructure and server specification, build and test. This can be very time consuming, and it was my experience that from the first requirements gathering to build would often take months. My own way of working was to create a virtual machine of SharePoint and work with the client early on, to provide Agile designing.<br />
<br />
But over time this caused its own problems. My virtual machines would generally not use AD, they would have a express database, and I would use the some server admin account to run all of the Server Accounts, making for a less than robust account.
So over time I would use a better VM provided with AD, DNS, and SQL, but this itself became something of a project. I could copy the boxes over but to build them in client environments was not a full dev box task.
From an initial requirements gathering to a running system kept taking months.<br />
<br />
The best way was to get a company that already had SharePoint and then start doing the requirements gathering, but this meant that the organization had to commit to SharePoint before really knowing what the use case would be, not very likely.
Office 365 solves these problems nicely. You can get the client a demo site with 25 to 250 users in a matter of hours or days at the most and be working in a preparation project in the first week.
But this does not mean that technical skills are not longer needed, its just that they are moving more to things like connectivity, sync, app development, security and identity management.<br />
<br />
That is why I have included the video above, it is part of one of the new skills every SharePoint IT pro needs now, creating AD FS integration between existing legacy AD on-prom and Azure AD running your SharePoint 2013. Even if you never do this in your job you need to fully understand what is involved and the risks involved.
Previously AD was just there, you worked with what you had as a SharePoint expert. But today you need to be more aware of how AD works, and the problems of integrating existing ADs, and all their potential problems, in to the Cloud.bob hookerhttp://www.blogger.com/profile/04097911020395990362noreply@blogger.com0tag:blogger.com,1999:blog-7013533479766342639.post-24243199596917871142015-03-24T06:27:00.002-07:002015-03-24T06:27:30.475-07:00Office 365 and Domainsn our personal life most of us are more than happy to have email accounts that end in googlemail.com or hotmail.co.uk or apple.com. It actually makes it easier for people to find us, they need to only learn our prefix. The problem is few of us have our names as googlemail accounts, we end up using cute phrases or putting numbers at the end of our names.<br />
<br />
<b> When you get an Office 365 account you get a domain inside of the onmicrosoft.com domains. </b><br />
<br />
This means if you register something like loveworks as your company name you will get emails and logins that end loveworks.onmicrosfot.com and your emails will be of the form <b><username>@loveworks.onmicrosoft.com.</b><br />
<br />
<br />
Again for a smaller company this might be fine, but for a larger firm or a firm with more established presence on the web you might want to use an existing domain, or register a new domain so your users can got to a URL like <b>loverorks.com rather than loveworks.onmicrosoft.com.</b> This is probably a minimal step for users who are moving to Office 365 and here is the easiest clearest video I have found to do this: <br />
<iframe allowfullscreen="true" frameborder="0" height="180" marginheight="0" marginwidth="0" scrolling="no" src="http://hub.video.msn.com/embed/8fd9ba4b-35b6-40e0-9537-20e428c39e0d/?vars=bWt0PWVuLXVzJmJyYW5kPU1TX09mZmljZSZsaW5rYmFjaz1odHRwcyUzQSUyRiUyRnd3dy5iaW5nLmNvbSUyRnZpZGVvcyZsaW5rb3ZlcnJpZGUyPWh0dHBzJTNBJTJGJTJGc3VwcG9ydC5vZmZpY2UuY29tJTJGZW4tdXMlMkZhcnRpY2xlJTJGU2V0LXVwLXlvdXItY3VzdG9tLWRvbWFpbi1pbi1PZmZpY2UtMzY1LTg0ODJkNmFlLWRmZTktNDc5Mi1hYmMzLTFkMmNiZDNmOGNiNyUzRkNUVCUzRDElMjZDb3JyZWxhdGlvbklkJTNEY2RiYWNhZTktMTFmMy00MTc1LTg2MzYtZjkwODdjZTNiZGNlJTI2dWklM0Rlbi1VUyUyNnJzJTNEZW4tVVMlMjZhZCUzRFVTJTI2ZnJvbUFSJTNEMSUyNnZpZGVvSWQlM0QlN0IwJTdEJTI2ZnJvbSUzRCZjb25maWdDc2lkPU1TTlZpZGVvJmNvbmZpZ05hbWU9c3luZGljYXRpb25wbGF5ZXImc3luZGljYXRpb249dGFnJmZyPXNoYXJlZW1iZWQtc3luZGljYXRpb24=" width="320"> <a href="https://support.office.com/en-us/article/Set-up-your-custom-domain-in-Office-365-8482d6ae-dfe9-4792-abc3-1d2cbd3f8cb7?ctt=1&correlationid=cdbacae9-11f3-4175-8636-f9087ce3bdce&ui=en-US&rs=en-US&ad=US&fromar=1&videoid=8fd9ba4b-35b6-40e0-9537-20e428c39e0d&from=shareembed-syndication" target="_new" title="Video: Use custom domains in Office 365">MS_Office Video: Use custom domains in Office 365</A></iframe>
<br />
Now say you are an even more mature company with an existing Active Directory on premise and lots of applications running using your Active Directory. You still want to use Office 365 for mail, messaging and collaboration but you want to keep your existing Active Directory and manage your identities on AD. This makes things much more complex. You can sync your identities between the on-prem and Office 365.
<br />
<br />
I will cover steps to do this in later blog posts.<br />
<br />
For now let me say this is something you really need to think about. If you can live with a separate AD in the cloud and your users have two logins and two passwords to remember its probably best to live with it. By synching your on-prem AD to Azure AD used by Office 365 you are inviting a lot of work. If you only have less than 100 employees, or a lot of contract workers who never get in your AD, or no onsite AD then its best to keep everything in the Cloud.<br />
<br />
Sync can be great and this is an amazing features of Microsoft, but its worth thinking that millions of people have email addresses in the cloud that they use everyday, without worrying about online sync. It might be good to start thinking Cloud-First, keeping things off premise as much as possible.bob hookerhttp://www.blogger.com/profile/04097911020395990362noreply@blogger.com0tag:blogger.com,1999:blog-7013533479766342639.post-79108683668582373182014-09-09T03:13:00.002-07:002016-02-09T06:41:07.055-08:00Office 365 brings it all together, finally<iframe frameborder="0" height="600" scrolling="no" src="http://guides.officeignite.com:80/embed/6w" width="100%"></iframe><br />
<br />
SharePoint Online as part of Office 365 is the Enterprise product I have been waiting for since 1999. Finally all the benefits of web, single location, access anywhere, shared community standards and online storage along with security and resiliency are in one place.<br />
<br />
<b>Make no mistake about it, this is going to be the Microsoft's biggest impact on the economy since Office and Windows 95. With Office 365 it now possible for any firm, no matter how small, to start, on day one, with Enterprise level content management, VOIP, IM, and collaboration. </b>(I wrote this in 2014 and clearly stand by it now)<br />
<br />
The cost of starting a new business has just gotten a great deal smaller, and the ease that existing businesses can reconfigure themselves, collaborate with outside organisations, and to bring in contractors and prosumers is now a fraction of what it was.bob hookerhttp://www.blogger.com/profile/04097911020395990362noreply@blogger.com0tag:blogger.com,1999:blog-7013533479766342639.post-2412857669111973172014-06-24T07:04:00.000-07:002015-04-10T15:00:09.427-07:00A Windows with Linux under the hood<b>Opps update is that is story is now invalid, MS is out of this business.</b><!-- Place this tag in your head or just before your close body tag. --><script src="https://apis.google.com/js/plusone.js" type="text/javascript"></script><!-- Place this tag where you want the widget to render. --><br />
<br />
<div class="g-post" data-href="https://plus.google.com/114298483458899933963/posts/4TGkaVm1Vqi">
</div>
,BR />
Actually for some time I have been predicting a MS-Linux machine of some kind. Windows, once the backbone of MS business, is becoming less and less important in a world dominated by multi-channels and Cloud, and as Windows is less and less important as a core product it becomes a difficult to maintain mass of legacy code. I have to be frank that I have given up on Windows, but I still work extensively with Microsoft. The two are no longer a contradiction. I think the X2 Android Microsoft phone could be the first step for a generation of new devices, that offer the UI experience of Windows Metro but via HTML, running Linux, Unix and Android under the table.bob hookerhttp://www.blogger.com/profile/04097911020395990362noreply@blogger.com0tag:blogger.com,1999:blog-7013533479766342639.post-43545138174178031292014-04-28T07:27:00.001-07:002014-04-28T07:27:27.372-07:00Basic SharePoint 2013 Build<iframe allowfullscreen="" frameborder="0" height="315" src="//www.youtube.com/embed/rqDNYkzP1WU" width="560"></iframe><br />
<br />
A fairly good introduction to SharePoint 2013 build I found, go for a learner but this is not how you will set up a proper farm.<br />
<br />
<a href="http://nikpatel.net/2011/06/23/why-you-shouldnt-use-the-farm-configuration-wizard-to-build-production-sharepoint-2010-farm/">After you learn this take a look at this blog post which tell you more about Service configuration</a>. A lot of sites use Service Configuration wizard, but its best to get the powershell scripts for Service Configuration, <a href="http://www.sharepointusecases.com/2011/01/automate-sharepoint-2010-farm-configuration-with-powershell/">which you can get here</a>.bob hookerhttp://www.blogger.com/profile/04097911020395990362noreply@blogger.com0tag:blogger.com,1999:blog-7013533479766342639.post-70998516062552922242014-01-22T15:35:00.000-08:002014-01-22T15:35:35.720-08:00Powershell to restore a site collection without changing the existing security group membersRecently I had an requirement to update a wiki site collection from live, using PowerShell backup and restore, to a training environment. The requirement further stated that the memberships of the existing training site should be kept. <br />
<br />
Though this seems like an fairly easy requirement it turned out not to be something that could be done with Backup-SPSite and Restore-SPSite code, so I developed the code below, which works in a test environment I created.<br />
<span style="font-family: Courier New, Courier, monospace;"><br /></span>
<br />
<div class="im" style="background-color: white; font-size: 13px;">
<span style="color: blue; font-family: Courier New, Courier, monospace;">Add-PSSnapin Microsoft.SharePoint.<wbr></wbr>Powershell<br /><br />$oldm = Get-SPuser -Web "<a href="http://win-l31vicrc3b5/" target="_blank">http://win-l31vicrc3b5/</a>" -Group "Team Site Members"<br />$oldo = Get-SPuser -Web "<a href="http://win-l31vicrc3b5/" target="_blank">http://win-l31vicrc3b5/</a>" -Group "Team Site Owners"<br />$oldv = Get-SPuser -Web "<a href="http://win-l31vicrc3b5/" target="_blank">http://win-l31vicrc3b5/</a>" -Group "Team Site Visitors"<br /><br />Restore-SPSite "<a href="http://win-l31vicrc3b5/" target="_blank">http://win-l31vicrc3b5/</a>" -Path C:\backup\back.back -Force<br />$newm = Get-SPuser -Web "<a href="http://win-l31vicrc3b5/" target="_blank">http://win-l31vicrc3b5/</a>" -Group "Team Site Members"<br />$newo = Get-SPuser -Web "<a href="http://win-l31vicrc3b5/" target="_blank">http://win-l31vicrc3b5/</a>" -Group "Team Site Owners"<br />$newv = Get-SPuser -Web "<a href="http://win-l31vicrc3b5/" target="_blank">http://win-l31vicrc3b5/</a>" -Group "Team Site Visitors"<br /><br />foreach ($spuser in $newm){Remove-SPUser -Web "<a href="http://win-l31vicrc3b5/" target="_blank">http://win-l31vicrc3b5/</a>" -Identity $spuser -Group "Team Site Members" -confirm:$false}<br />foreach ($spuser in $newo){Remove-SPUser -Web "<a href="http://win-l31vicrc3b5/" target="_blank">http://win-l31vicrc3b5/</a>" -Identity $spuser -Group "Team Site Owners" -confirm:$false}<br />foreach ($spuser in $newv){Remove-SPUser -Web "<a href="http://win-l31vicrc3b5/" target="_blank">http://win-l31vicrc3b5/</a>" -Identity $spuser -Group "Team Site Visitors" -confirm:$false}<br /><br /><br />foreach ($spuser in $oldm){Set-SPUser -Web "<a href="http://win-l31vicrc3b5/" target="_blank">http://win-l31vicrc3b5/</a>" -Identity $spuser -Group "Team Site Members" -confirm:$false}<br />foreach ($spuser in $oldo){Set-SPUser -Web "<a href="http://win-l31vicrc3b5/" target="_blank">http://win-l31vicrc3b5/</a>" -Identity $spuser -Group "Team Site Owners" -confirm:$false}<br />foreach ($spuser in $oldv){Set-SPUser -Web "<a href="http://win-l31vicrc3b5/" target="_blank">http://win-l31vicrc3b5/</a>" -Identity $spuser -Group "Team Site Visitors" -confirm:$false}<br /><br />write-host "Done"</span></div>
bob hookerhttp://www.blogger.com/profile/04097911020395990362noreply@blogger.com0tag:blogger.com,1999:blog-7013533479766342639.post-87733726178903742262014-01-10T08:19:00.002-08:002014-01-10T08:19:58.669-08:00AvePoint's DocAve 6 makes SharePoint administration better<table align="center" cellpadding="0" cellspacing="0" class="tr-caption-container" style="margin-left: auto; margin-right: auto; text-align: center;"><tbody>
<tr><td style="text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgCWRWecsK1pXZjUL-bJ8-e4PYiJ1SYX0ac-jf93msH_9oaEkyepljdTGKvA5ftpyjmeJQLxOlwv4dJO-plZpzINMpVocRjLIw77s6I74TlDMPTG43wmp2Mf68aG7boV0uOEMWoilKj/s1600/docAve1.tiff" imageanchor="1" style="margin-left: auto; margin-right: auto;"><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgCWRWecsK1pXZjUL-bJ8-e4PYiJ1SYX0ac-jf93msH_9oaEkyepljdTGKvA5ftpyjmeJQLxOlwv4dJO-plZpzINMpVocRjLIw77s6I74TlDMPTG43wmp2Mf68aG7boV0uOEMWoilKj/s1600/docAve1.tiff" height="492" width="640" /></a></td></tr>
<tr><td class="tr-caption" style="text-align: center;">Adding a user to large set of Document Libraries is now a snap</td></tr>
</tbody></table>
<br />
Over the years working with SharePoint some of the main user issues I get are these:<br />
<br />
<ol>
<li>Can I manage the columns of folders in dozens of sites around the Enterprise?</li>
<li>Can I add a user to a large number of sites easily?</li>
<li>Can I move a large number of document libraries from different site collections in to one site collection, or the other way around?</li>
<li>Can I turn on versioning with a single click on every document library in the farm.</li>
</ol>
<div>
Using SharePoint Central Admin there are no ways to do this, you have to create complex PowerShell coding which is time consuming and frankly its hard to find PowerShell scripts. Now I love PowerShell myself but it not really what you want your admins doing all day, you want them giving your users value.</div>
<div>
<br /></div>
<div>
That is why I am so excited about AvePoint's DocAve 6, which gives you a central admin UI, separate from SharePoint central Admin, that allows you to do these kinds of things, and many more.</div>
<br />
<br />
<table align="center" cellpadding="0" cellspacing="0" class="tr-caption-container" style="margin-left: auto; margin-right: auto; text-align: center;"><tbody>
<tr><td style="text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhiYJPC6X1dNb2X9BGeXZ1RrONonzeCYxS7d0MQfiOSYSiZlHmQ4srurxcQHG0u_zCCUZsjAOFH-GQ0c5tyeBsIATjOeYusIr2pnR3s0Lpv1ucJtNKBoDHF_7kVz5-cduODTHT8FBNL/s1600/docAve2.tiff" imageanchor="1" style="margin-left: auto; margin-right: auto;"><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhiYJPC6X1dNb2X9BGeXZ1RrONonzeCYxS7d0MQfiOSYSiZlHmQ4srurxcQHG0u_zCCUZsjAOFH-GQ0c5tyeBsIATjOeYusIr2pnR3s0Lpv1ucJtNKBoDHF_7kVz5-cduODTHT8FBNL/s1600/docAve2.tiff" height="450" width="640" /></a></td></tr>
<tr><td class="tr-caption" style="text-align: center;">Moving content from one site to another is easy with DocAve 6 rich UI</td></tr>
</tbody></table>
In my initial set of tests on DocAve 6 running against a SharePoint 2010 Foundation farm on a VM I was able to easily add and remove users from a large set of document libraries in one go, manage column of a large group of document libraries, and move content from a document library in one site collection to another.<br />
<br />
This is really the right tool to be managing Central Admin for a large Enterprise estate.<br />
<br />
A good case study, and one I see all the time, would be situation where each project got its own site collection with a template. Now each site collection has edited its template so that the same information is encoded different between different projects. <br />
<br />
With DocAve 6 its possible to clean up the document libraries, to make them more consistent and to clearly she what columns different teams have created. You can also move all the document libraries in different site collections in to one managed site collection, making things more central.bob hookerhttp://www.blogger.com/profile/04097911020395990362noreply@blogger.com0tag:blogger.com,1999:blog-7013533479766342639.post-82350354844116025722013-11-22T08:45:00.001-08:002013-11-22T13:04:16.754-08:00SharePoint 2013 major disruption in UI and UX<table align="center" cellpadding="0" cellspacing="0" class="tr-caption-container" style="margin-left: auto; margin-right: auto; text-align: center;"><tbody>
<tr><td style="text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEivqB_oQkByPSWmogWuldqQXDCqsZWnL86BIZxxONMtZF99_Vr9gl3eiPwXF8xVWoff-KtzKUuoHpI5yXHkHGaYVhlCAZF9nyKdIHvkijq8UhjPTTkKoKqc77P7eOzSHWzSB9JnFqXB/s1600/Office365.tiff" imageanchor="1" style="margin-left: auto; margin-right: auto;"><img border="0" height="334" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEivqB_oQkByPSWmogWuldqQXDCqsZWnL86BIZxxONMtZF99_Vr9gl3eiPwXF8xVWoff-KtzKUuoHpI5yXHkHGaYVhlCAZF9nyKdIHvkijq8UhjPTTkKoKqc77P7eOzSHWzSB9JnFqXB/s640/Office365.tiff" width="640" /></a></td></tr>
<tr><td class="tr-caption" style="text-align: center;">SharePoint 2013 Team Site in Office 365 is a major change in UI, making a more tablet friendly simply design</td></tr>
</tbody></table>
One of the most striking things about SharePoint 2013 is simply how it look. The new SharePoint is a radical brake from all earlier UIs. SharePoint 2013 UI is more tablet friendly and simpler, with larger objects and less clutter. SharePoint is also reducing the number of objects the confront the user.<br />
<br />
<table align="center" cellpadding="0" cellspacing="0" class="tr-caption-container" style="margin-left: auto; margin-right: auto; text-align: center;"><tbody>
<tr><td style="text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEi8IxQtHZsmfGKBrTwN-X9njbDjsfmO8nOtnVMbtF0x7HPhc-gPHZIX4dq_X74wd0Y7vdoIj_iCX7JRIwRK-CW7v_rPlt7NVgWhGTkYwHHFhX0SKQRGTHC1k32ctTPVMnAS1-Sk7PCl/s1600/2010TeamSite.tiff" imageanchor="1" style="margin-left: auto; margin-right: auto;"><img border="0" height="368" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEi8IxQtHZsmfGKBrTwN-X9njbDjsfmO8nOtnVMbtF0x7HPhc-gPHZIX4dq_X74wd0Y7vdoIj_iCX7JRIwRK-CW7v_rPlt7NVgWhGTkYwHHFhX0SKQRGTHC1k32ctTPVMnAS1-Sk7PCl/s640/2010TeamSite.tiff" width="640" /></a></td></tr>
<tr><td class="tr-caption" style="text-align: center;">SharePoint 2010 Team Site has most of the same features as the 2013 site, but is fully grounded in the PC world or mouse clicks. Imagine trying to manage this thing with a finger.</td></tr>
</tbody></table>
I am finding SharePoint 2013 much easier to work with than SharePoint 2010, and a greater improvement over 2010 than 2010 was over 2007.<br />
<div>
<br />
<table align="center" cellpadding="0" cellspacing="0" class="tr-caption-container" style="margin-left: auto; margin-right: auto; text-align: center;"><tbody>
<tr><td style="text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhrmBU8PDoCHRZeaoC-Gkam683ZMMw73KSoQNztb4Jfly35m9a74BzRxWircFryRpeBu2BhadjxAGaG0g-pUbtuZPn6oVfBAQ3M7qS7JdUIW-CErjIbZLx1s0mhmDsezGokGro0Qvaq/s1600/2007.jpg" imageanchor="1" style="margin-left: auto; margin-right: auto;"><img border="0" height="412" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhrmBU8PDoCHRZeaoC-Gkam683ZMMw73KSoQNztb4Jfly35m9a74BzRxWircFryRpeBu2BhadjxAGaG0g-pUbtuZPn6oVfBAQ3M7qS7JdUIW-CErjIbZLx1s0mhmDsezGokGro0Qvaq/s640/2007.jpg" width="640" /></a></td></tr>
<tr><td class="tr-caption" style="text-align: center;">SharePoint 2007, while the UI changes between SharePoint 2007 and 2010 were in large part cosmetic, SharePoint 2013 is a real change in how people will be able to interact with SharePoint.</td></tr>
</tbody></table>
<div class="separator" style="clear: both; text-align: center;">
<br /></div>
I think it would be a major mistake to think this is just a skin deep transformation, which it is easy to think. Working with the new SharePoint 2013 you quickly see that it is mostly the same as 2010 under the hood. But the new UI also comes with a new App model, new RESTful web services interface that returns JSON and ATOM, new JavaScript API model for cross domain communication. <br />
<br />
Microsoft is embracing disruptive web technology from places like Google, Twitter, Facebook and the start-up culture of open interfaces. Things are going to change a great deal, SharePoint silo nature may change for something more like Twitter.<br />
<br /></div>
bob hookerhttp://www.blogger.com/profile/04097911020395990362noreply@blogger.com0tag:blogger.com,1999:blog-7013533479766342639.post-53362012430940425132013-11-18T15:28:00.002-08:002016-02-09T06:38:48.403-08:00A use case for SharePoint 2013 App Model<div class="separator" style="clear: both; text-align: center;">
<a href="http://i.msdn.microsoft.com/dynimg/IC599129.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" src="http://i.msdn.microsoft.com/dynimg/IC599129.png" height="390" width="400" /></a></div>
<div class="separator" style="clear: both; text-align: center;">
<br /></div>
<div class="separator" style="clear: both; text-align: left;">
There probably is a heavy temptation for managed services providers who host large data centers that are sold as Clouds, to continue to develop Full Trust Web Parts even when going to SharePoint 2013. Web Parts are what coders are used to, they may have a large library of existing Web Parts as WSP files that run in full trust. This is possible, and it means working pretty much as you always did.</div>
<div class="separator" style="clear: both; text-align: left;">
<br /></div>
<div class="separator" style="clear: both; text-align: left;">
<b>But if you are like most managed service providers I know you have some kind of internal structure between your infrastructure providers who build and maintain the farms and the application and solutions providers who face the customers and develop SharePoint from a raw out of the box in to something more specific and rich for their needs.</b></div>
<div class="separator" style="clear: both; text-align: left;">
<br /></div>
<div class="separator" style="clear: both; text-align: left;">
<b>This DevOps work has been traditionally very difficult to manage in SharePoint. When you would develop a solution to run in SharePoint 2010 you would hand it off to a deployment management team who would have to review the code for security risks, and impact on the servers. Since the code would run in the Farm it had an Enterprise level impact. </b>This would involve extensive documentation and review, and complex levels of support for your solutions. In the end you would probably be dependent on a different department of the company to deploy your work but still own the risks if they made a mistake.</div>
<div class="separator" style="clear: both; text-align: left;">
<br /></div>
<div class="separator" style="clear: both; text-align: left;">
<b>By adopting a SharePoint 2013 App Model you can move away from this.</b> Two teams, even if they work in the same company can concentrate on what they are best at. Infrastructure can concentrate on meeting SLAs, providing backup and DR and applying patches. </div>
<div class="separator" style="clear: both; text-align: left;">
<br /></div>
<div class="separator" style="clear: both; text-align: left;">
Solution providers can create partial trust solution that use .NET SCOM or REST and JSON to create rich interfaces that are hosted in other domains, perhaps even other server farms with different domain controllers. You now no longer have the tight link between the people installing SharePoint farm and the developers of solution, in fact you can separate your teams so that one applications team can create solutions, potentially in PHP or Ruby or anything really, that work off more than one SharePoint 2013 farm.</div>
<div class="separator" style="clear: both; text-align: left;">
<b><br /></b></div>
<div class="separator" style="clear: both; text-align: left;">
<b>And if your clients decide to not renew the hosting contract with SharePoint to go with Office365 or another vendor, you don't necessarily lose your applications business.</b> You can still provide your application solutions simply by changing the RESTful web link. You can de-risk big SharePoint deployments by breaking hosting from solutions, allowing your customer the option to keep one if they are unhappy with the other. </div>
<div class="separator" style="clear: both; text-align: left;">
<br /></div>
<div class="separator" style="clear: both; text-align: left;">
So it makes solid business sense even for established big players to embrace JQuery and RESTful and build App that run in separate domains using OAuth and OData to communicate with SharePoint, creating UI in HTML 5 and CSS 3 because after all we all hated SharePoint OTB UI (admit it).</div>
<div class="separator" style="clear: both; text-align: left;">
<br /></div>
<div class="separator" style="clear: both; text-align: left;">
The potential is perhaps even greater for smaller firms. Now a smaller firm with a team of talented web developers who know about JQuery, mobile, tablets, RESTful, OData and rapid design can muscle in on a space that previously only the provider could have. And I speak from hard earned experience when I say that the big guys will be more than happy to have third party code isolated in its own IIS server rather than installed on perm SharePoint farm. </div>
<div class="separator" style="clear: both; text-align: left;">
<br /></div>
<div class="separator" style="clear: both; text-align: left;">
It also my experience that the culture that makes a first rate development and business solutions firm (agility, innovation, creativity and social understanding) is often different than what makes a first rate hosting firm (stability, precision, technical expertise, compliance and control). With the App Model the the create web designers don't make anything you host on the SharePoint Domains and the systems admins are not going to dictate solutions to the creatives. You can have a more comfortable distance between application developers culture and hosting culture, and we all know sometimes IT people don't play nice together.</div>
<div class="separator" style="clear: both; text-align: left;">
<br /></div>
<div class="separator" style="clear: both; text-align: left;">
<b>Really it is worth taking the time to really think through the changes to the ecosystem that Cloud hosting of SharePoint and App solutions will bring. </b>SharePoint has had a series of evolutionary changes since 2003 and its made some of us lazy (looks down in shame). New SharePoint releases were a matter of learning a few new features and services. But the App Model is a much more revolutionary change and it will change the business model.</div>
<div class="separator" style="clear: both; text-align: left;">
<br /></div>
<div class="separator" style="clear: both; text-align: left;">
Be ready or you will lose. </div>
<br />bob hookerhttp://www.blogger.com/profile/04097911020395990362noreply@blogger.com0tag:blogger.com,1999:blog-7013533479766342639.post-11373964210934020902013-10-22T03:35:00.000-07:002013-10-22T03:35:08.758-07:00JavaScripts and Cross Domain in SharePoint 2013The most exciting new feature in SharePoint 2013 for an old web developer like me is the embracing of JavaScripting, JQuery and open standards. Now more and more of what is done will be done in JavaScript, a language almost all developers know, and less in C#<br />
<iframe frameborder="0" height="415" marginheight="0" marginwidth="0" scrolling="no" src="http://hub.video.msn.com/embed/f3f30039-0542-4b8a-885a-72fa46d8b01d/?vars=bWt0PWVuLXVzJmJyYW5kPU1TX09mZmljZSZsaW5rYmFjaz1odHRwJTNBJTJGJTJGd3d3LmJpbmcuY29tJTJGdmlkZW9zJmxpbmtvdmVycmlkZTI9aHR0cCUzQSUyRiUyRnd3dy5taWNyb3NvZnQuY29tJTJGb2ZmaWNlJTJGcHJldmlldyUzRnZpZGVvaWQlM0QlN0IwJTdEJmNvbmZpZ0NzaWQ9TVNOVmlkZW8mY29uZmlnTmFtZT1zeW5kaWNhdGlvbnBsYXllciZzeW5kaWNhdGlvbj10YWcmZnI9c2hhcmVlbWJlZC1zeW5kaWNhdGlvbg==" width="740"> <A href="http://www.microsoft.com/office/preview?videoid=f3f30039-0542-4b8a-885a-72fa46d8b01d&from=shareembed-syndication" target="_new" title="SharePoint 2013 cross-domain calls">MS_Office SharePoint 2013 cross-domain calls</A></iframe><br />bob hookerhttp://www.blogger.com/profile/04097911020395990362noreply@blogger.com0tag:blogger.com,1999:blog-7013533479766342639.post-57868362405005439292013-10-17T09:50:00.000-07:002013-10-17T09:50:19.725-07:00Microsoft Office embraces the concept of Apps<div style="text-align: center;">
<iframe frameborder="0" height="180" marginheight="0" marginwidth="0" scrolling="no" src="http://hub.video.msn.com/embed/61ce61c7-cb0b-4236-9d96-41b0094b0398/?vars=bWt0PWVuLXVzJmJyYW5kPU1TX09mZmljZSZsaW5rYmFjaz1odHRwJTNBJTJGJTJGd3d3LmJpbmcuY29tJTJGdmlkZW9zJmxpbmtvdmVycmlkZTI9aHR0cCUzQSUyRiUyRnd3dy5taWNyb3NvZnQuY29tJTJGb2ZmaWNlJTJGcHJldmlldyUzRnZpZGVvaWQlM0QlN0IwJTdEJmNvbmZpZ0NzaWQ9TVNOVmlkZW8mY29uZmlnTmFtZT1zeW5kaWNhdGlvbnBsYXllciZzeW5kaWNhdGlvbj10YWcmZnI9c2hhcmVlbWJlZC1zeW5kaWNhdGlvbg==" width="320"> <A href="http://www.microsoft.com/office/preview?videoid=61ce61c7-cb0b-4236-9d96-41b0094b0398&from=shareembed-syndication" target="_new" title="Imagine apps for Office 2013 and SharePoint 2013 in 90 seconds">MS_Office Imagine apps for Office 2013 and SharePoint 2013 in 90 seconds</A></iframe><br /></div>
<div style="text-align: center;">
</div>
<div style="text-align: left;">
The concept of the app, a small piece of special purpose code sold or distributed on the web, is catching on to Microsoft. The greatest thing about the new app model for Office and SharePoint 2013 is not only is it built on web standards like HTML 5, CSS and JavaScript, but it is sold and distributed in a business model people will easily understand: the app store.</div>
<div style="text-align: left;">
</div>
<div style="text-align: left;">
You can buy an app on an app store, or have one developed to special task either inserted directly in to the tools you use like Excel or on SharePoint.</div>
<div style="text-align: left;">
</div>
<div style="text-align: left;">
I personally am looking at Excel apps, as I think for Big Data this is going to be a killer app.</div>
bob hookerhttp://www.blogger.com/profile/04097911020395990362noreply@blogger.com0tag:blogger.com,1999:blog-7013533479766342639.post-34102282694527786342013-10-17T05:09:00.000-07:002013-10-17T05:09:33.915-07:00Apps model for Office and SharePoint 2013<iframe style="height:540px;width:960px" src="http://channel9.msdn.com/Events/Build/2012/2-008/player?w=960&h=540" frameBorder="0" scrolling="no" ></iframe>
Things are changing in the App world for SharePoint, Microsoft is doing what it does best, copying what other people have already made. And Office and SharePoint are embracing the App model based on open web standards.bob hookerhttp://www.blogger.com/profile/04097911020395990362noreply@blogger.com0