Tag Archives: sharepoint migration experts india

Design Tips for SharePoint 2013 Apps on Tablets

The discussion on the tips for designing for the SharePoint 2013 Apps on tablets should essentially begin with the concept of minimal viable product. The idea is to enhance the user experience with Office 365 and Microsoft Office. Enterprises seem to be on the lookout for continuously updating the products to gain a strong competitive advantage and engaging in viable business in Office 365.

SharePoint site branding expertsWith the increase in the number of mobile devices and tablet users, it has become necessary for the SP 2013 apps to stay accessible as well as work effectively on these devices. Here is a list of tips on designing excellent SP apps for the tablets.

Always Go For Responsive Design
Whenever it comes to designing SP 2013 applications for tablets, a responsive design is a prerequisite. Now, for those working on a publishing site or planning to render it with a great look and feel, a responsive web design is must. Now, for those not using a custom master page as a basis for compatibility with other apps, a responsive design might not appear to be that suitable.

Maintain the Minimum Possible Width
Although the base resolutions vary depending on the landscape mode, majority of them have a width of 980 pixels. While the meta tags, JavaScript and CSS allow for control over the zoom behaviors and view port to a significant extent, it is always better to ensure that the columns in the tabular layout look impressive. This would also keep the initial investment to be made by the enterprise pretty low.

Make Efficient Use of CSS
The detailed pages for the varying entities in the form of matters and clients comprise a table at the top along with a set of tabs at the bottom, displaying related data. It is the entity as well as the data that work together in determining the number of columns in the header. On the other hand, for the clients, the columns denoting the phone numbers, address and notes are hidden especially, in cases where there is no data.

Now, these tables pose challenge because of the fact that both the width of the browser as well as the one that is required to display particular data within the table vary. The solution lies in using the base of 980 pixels, which renders a lower bound. Also, with a vertical alignment at the top, padding is explicit while word-break is natural.

Derive Benefits Out of the ‘Focus on Content’ Button
The ‘Focus on Content’ button appears at the upper right hand corner of the page. This is quite a beneficial feature and using it optimally can actually lead to an effective designing of SP 2013 applications for tabs.

Not Putting any Options in the Quick Launch Section
The pre-dominant belief is that while using a tablet, focus should always be laid on the content. However, it is better not to put any important option in the ‘Quick Launch’ section for this section can not be viewed by the tablet users and hence, the app will be of little significance for them.

Avoid Adopting the Minimal Download Strategy
The minimal download strategy is fine for those in any app web. However, this feature calls for some serious compatibility issues in certain browsers. The minimal download strategy can be disabled using the CSOM.

Prefer a Dynamic Sizing of Dialogs
While much of the discussions so far have been done with, height is also a matter of concern when it comes to using a dialog framework. It is always essential to go for dynamic alignment and setting the options depending on the natural height of the page.

With the above-mentioned tips and strategies, one can certainly develop suitable SharePoint 2013 apps for tablets. And while looking for SharePoint services India, make sure you are reaching out to companies who have solid credentials and have proven expertise in application development in SharePoint and have equally strong domain expertise as well.

We provide Sharepoint migration services. If you would like to know more about the expertise of our SharePoint site branding experts, please get in touch with us at Mindfire Solutions.

Advertisements

How To Control App Token Lifetimes in SharePoint 2013?

SharePoint has emerged to be one of the most beneficial web application development platforms these days. The newer versions of this platform have turned out to be of immense use for the business enterprises as, they assist in the successful accomplishment of several tasks and necessitate much less time and efforts. Now, developers are trying out more innovative ways of exploiting SharePoint so as to derive the maximum advantages out of this already useful platform. Controlling the app token lifetimes in SP 2013 is one area of concern that is emphasized upon to a significant extent.

SharePoint development companiesThe first question that arises in this regard is where one can control the app token lifetimes. However, when considered on a broader platform, it will be seen that the place of control is actually not so significant and that a highly advanced app like TokenHelper can be of substantial help. There are around one or two JWT tokens that are created if one goes by the IssueToken method. It is usually one when the app only token is being used and two tokens for the application and the current user. However, in both the events, the JsonWebSecurityToken is created and the parameter that is used to create the same determines as to how long it is valid.

It is for the app token that the TokenHelper makes use of a constant, which is known as TokenLifeTimeMinutes. By default, this constant has a value of 1,000,000, which leaves no scope of worrying except in cases where one wants to limit it. Now, for the user token, the constant is hard- coded by default for making use of a lifetime of 10 minutes. The values can be found as well as changed into whatever you want just with a little drilling into the IssueToken method.

With a deeper look into the code, it can be seen that the TokenHelper incorporates a delegate that is invoked in what is known as the GetClientContextWithAccessToken method. This method plays the important role in adding a bearer token to any particular request that comes into the SharePoint from the particular app of the user.

Now, if the user sets a breakpoint on that specific line of code and eventually step through the request from the app, none of the token ‘setup’ functions creating the ClientContext will be resulting in an HTTP call. At this point, the ExecuteQuery method has to be called on the ClientContext object. The request goes over the wire, the delegate fires and finally, the token is added to the request. While one can cache the access token obtained in the high trust app, there may not always be a justified reason behind doing so.

On the other hand, caching the app tokens is beneficial only at the time of using the relatively low trust apps. When such is the case, one has to save one or more trips to ACS for the purpose of accessing token at the time of caching them. In events where there are multiple users or several requests, the process helps. The only thing that one needs to be aware of in this regard is the right ways of caching the tokens for the low trust apps.

This is just a brief overview of the overall process of controlling application lifetimes in SharePoint 2013 along with a discussion about the use and benefits of the high trust as well as the low trust apps. However, it is a task that needs to be taken up by only the experts and pros in the field, who are aware of the processes and can therefore, adept in handling the same to produce faster results in less time.

You can hire developers from top SharePoint development companies in India who can help you build products within allocated budgets and time schedules.

We provide SharePoint CMS customization services. If you would like to know more about the expertise of our SharePoint developers, please get in touch with us at Mindfire Solutions.

The Problem with Leveraging SharePoint Records Management Services in Office365

The big question is, considering Office 365, where is Records Management fitting in? The old news is that SharePoint 2010 RM is not registering good performance within the e-discovery space. However, this is not considered a hindrance by most organizations.

SharePoint site migrationIt is a fact that IT is capable of pulling the objects which are essential to cater to the counsels’ expectations with respect to its own SOP or standard operating procedure, which generally incorporates a third party software. E-discovery has been performed by information technology more regularly and far longer than implementation of electronic retention by RM.

Automation is great
SharePoint 2010 RM services are capable of beautifully automating records declaration. They can be deployed successfully through mapping the records retention schedule across SharePoint 2010 RM.

The content types pertaining to the series can be holistically leveraged across site collections, followed by attachment of information policies. Then the indexing services to be run at particular intervals are recalculated.

The future hazards
Off-the-shelf SharePoint 2010 RM services are being trusted by corporate records programs. In an age where Records programs are entirely suspended or drastically squeezed, this is a quite inexpensive option for automated records declaration.

Since Office 365 lacks a related Records Center template, it is possible for the program to be vulnerable. The absence of automation can damage the program’s reputation. In case automated records declaration is leveraged in SharePoint also, the same might as well be in trouble.

What are the choices?
The necessities of the information architecture going beyond records policy amount to a textbook dilemma. Considering the case of information professionals, the design choice comes up with potentially long-term as well as negative connotations. In case an organization has automated records declaration through SP 2010 and its department of Information Technology is looking forward to embrace cloud services, it is a difficult choice. Deconstruction can be followed by manual records declaration implementation or the services of third party experts might be sought for devising something new.

Perhaps the best option in doing nothing in this particular case. First, something or the other will ultimately break. Secondly, this is a department that thinks forwardly and hence it cannot be visualized as restricting to one particular solution due to the lack of options. Thirdly, the employee turnover happens to be so high that the future administrator tends to lose all context pertaining to the architecture. Fourthly, retention schedules are subject to change and so unraveling of the Center for reconstruction in accordance with the new schedule is an enormous concern.

Manual records retention can also be considered as an option. However, it is an inferior one:

  • In-Place RM exists till today within Office 365, although it has been reduced to a mere status symbol. A one or a zero, which implies that either the record exists or it does not. In fact, the option for management of the same from the back-end is not available with the Administrator. The good news is that interaction with the end users is possible. On the other hand, the bad news is that until and unless the C-level stresses on and communicates its requirement, end users would definitely have to time for annual review. Destruction does not take place.
  • For devising out-of-the-box manual RM services within Office 365, the best way is the creation of a Records sub-site for each site collection. In every ways, the same folders should be used as are planned for the SP 2010 Records Center. The content types may be bypassed entirely and the same information policies may be used directly behind every folder.

Those objects which are required to be declared as records can be copied from the major site collection pages to the Records sub-site’s suitable folder. Since it is the case of a copy (wherein move is not available), the metadata changes should be noted and the peer should return to the original object for deleting it.

For initiation of a solution, the help of a third party may always be solicited. On one hand, it is being demonstrated that you need a compromise. Migration to the cloud cannot be hindered. On the other hand, you wish to make use of your cordial partnership with IT very meticulously at this point. Since Records is your project, it should not go to the backseat, being assigned with cleaning up legacy data.

On the positive side
In case you are going for RM in Office 365, the positive point is that it is convenient to edit retention periods. As discussions are held with each peer for planning of their folder structures, the maps need to be edited. It should be explained why and how folders pertaining to every site collection are a component of a bigger process-oriented schedule. Moreover, site permissions need to be unraveled for rebuilding them. After all, there is once more the opportunity to describe the mission as well as the significance of the program. As your IT department gears up for handling 2014 projects, it’s a great idea to seize the moment for RM in Office 365.

If you were to attempt a SharePoint site migration project to Office365, understanding of these choices and pros and cons would ensure a successful migration.

We provide SharePoint bespoke development services. If you would like to know more about the expertise of our SharePoint developers, please get in touch with us at Mindfire Solutions.

Top 8 Ways to Mitigate Risks in SharePoint Deployment

Deployment of the useful web application development platform of SharePoint involves certain risks. The SharePoint sites, which primarily include the SharePoint Online and the hosted SharePoint farms, have high chances of falling prey to some of the serious content security risks. Considering the fact that SP Online is highly preferred by all types of enterprises today for regulation of data, securing this data is a dire necessity. In fact, organizations are often found facing certain problems when it comes to maintaining the security of the data in SharePoint. The risks need to be mitigated without any wastage of time to ensure smooth work flow.

SharePoint bespoke developmentHere is a brief overview of the risks involved in SP deployment along with the possible ways of reducing their effects.

1. Less Awareness about SharePoint Content

The lack of awareness about SP content is a prominent risk in the deployment of this particular web application development platform. The two main ways of spreading increased awareness are implementation of the governance guidelines along with providing of content classification. The end users should be trained accordingly for performing periodic scans of content. Teams also have the option of making use of the SP metadata as well as workflows to pass the sensitive information to the secure locations.

2. Failing to Secure the Content in SP Servers, Transit and Endpoints

Securing the content in the SharePoint servers as well as endpoints is necessary. Enterprises must make it a point to implement solutions that ensure the security of the content on the SP servers as well as the backups through access control and encryption. Additionally, the teams should also go for a whole-disk encryption for endpoints and most essentially, laptops. The SSL encryption for data in transit should also be enabled by the security administrators.

3. Misconfiguration of the Access Controls and Permissions

This is yet another risk that often poses a problem in the deployment of SharePoint. The solution lies in auditing the existing SharePoint permissions and then reviewing or creating of the corporate access control policies. Following this, the SP permissions should be aligned with the corporate directory services, by which, the administrators can get an idea about the usage of inheritance as well as unmanaged item-level permissions.

4. SP Platform Security Risks

The SharePoint platforms need to be hardened by means of disabling the ports as well as services that are not essential to the functioning of the platform. Regular patching apart from whitelisting of applications also helps in reducing the risks of platform security.

5. Failing to Limit the Administrator and Service Accounts

One essential way in which the risk of failing to limit the administrator as well as service accounts can be reduced is by limiting the privileges on service accounts. Disabling the install account and not using the shared administrator accounts are other prominent ways of mitigating this particular risk.

6. SP System Architecture and Network Configuration Issues

The system architecture as well as network configuration issues related to the SharePoint can be reduced by putting a dedicated SP web front end in a DMZ and by making use of a single-function-per-server approach. Hardening of the SP, OS as well as the database as per the best practices is also highly recommended.

7. Issues Related to SP and Malware

Risks arising from SharePoint as well as Malware can be solved by implementation of the server malware solution along with a regular updating of the anti-virus definitions.

8. Difficulty in Performing Backups and Providing DR Capability

The only possible way in which this problem can be solved is by performing annual backups as well as tests and restoring them on a regular basis.

Managing the above-mentioned security risks through an application of the appropriate security controls helps in reducing the level of content security as well as compliance risks in SP to a great extent. If you were to attempt a SharePoint site migration project, understanding of these best practices would ensure a successful migration.

We provide SharePoint bespoke development services. If you would like to know more about the expertise of our SharePoint programmers, please get in touch with us at Mindfire Solutions.

Migrating from MOSS 2007 to SharePoint 2013- Don’t Miss Out on these 10 Tips

The much popular and preferred web application development platform, SharePoint, comes up in newer versions at frequent intervals. Business entrepreneurs need to update themselves with the upgraded technology to ensure deriving the maximum benefits out of the applications, devices and platforms. SharePoint is undoubtedly one among the most beneficial technological advancements that affects business operations and increases the overall level of efficiency to a great extent.

SharePoint site migrationMigrating from MOSS 2007 to SharePoint 2013 is interesting as well as challenging. The process involving SharePoint site migration is also complex at the same time though the complexity depends upon the kind of customization available. Many of the SharePoint environments are often integrated with the external systems by means of the Business Connectivity Services or the custom connectors. The complex environments often pose challenges to the process of migration and it is here that few factors need to be taken into consideration. Here is a list of tips on executing a successful migration from MOSS 2007 to SharePoint 2013.

1. Following a 2-Step Approach

Migration of content from the SharePoint 2007 to 2013 version is a two- way process in cases where no 3rd party tools are used. The first step is to upgrade MOSS to a temporary 2010 version by means of database attach and the second is to move the content to the 2013 version in very much the same process. Third Party tools like that of the AvePoint can also be made use of. Cleaning up the content prior to the migration is equally essential.

2. Migrating the Code

Migration of the code is an important step that has to be done manually as, the code is a primary component in migration. The prevalent code has to be evaluated and analyzed in details before building the overall solution or migrating the code. It is necessary to analyze a lot many things to find out if they work with newest version of SharePoint. These include the code- based customizations, third- party tools, add- ins, web parts and so on.

3. Determine the Functionality of the Customization

The process revolving around the migration, as already said, is quite complex, which calls for the fact that certain customizations might not work out in the desired manner. Now, for customizations that are necessary but turn out to be incompatible, the cost as well as the efforts that need to be put into it have to be considered. Ensure remediating the customization in every possible way, for instance, reusing the core source to avoid reinventing the wheel and thereby, reducing the cost and effort.

4. Make the Customization Ready for All Versions

Whenever the remediation is done, the customization becomes applicable for not just the 2013 version but also the 2010 version of SharePoint. One must ensure that the customization is actually ready for all versions.

5. Consider the Permission and Authentication Model

When it comes to the Migration, special emphasis needs to be put into the new security model for building the entire solution with greater efficiency. It is advisable for anyone to do the permission migration and code migration separately. This helps in isolating and identifying the particular permission related issues that are likely to occur.

6. End User Training and Adoption

Moving users from MOSS 2007 to SharePoint 2010 requires training the users to enable them discover the difficult aspects of using SP 2013. The entire IT department of a business enterprise must become familiar enough with the usage of the newest mode of this web application development platform. Effective training paves the way for familiarity of the system and this in turn, leads to a better use of the development platform.

7. Finding Out Sites Customized with SharePoint Designer

It is necessary to determine as to what had been done with the sites that were customized with the SharePoint Designer. The URLs as well as the site owners with the few ‘one off’ sessions need to be identified to find out what actually had been done with them.

8. Installing or Upgrading to the SQL Server

Apart from upgrading to the Windows Server 2012, installing a new SQL server 2012 or upgrading to the SQL server 2008 is rather necessary. It is equally necessary to determine as to whether the SQL Server 2005 box had been dedicated to the SP or if there were other databases installed in it in clusters.

9. Considering the Power Users

Any business enterprise going for a migration must have some power users, who are particularly adept in handling this advanced web application development platform. There will be several requests for the automation of paper- based processes. Experts will facilitate deriving the maximum ROI on the business process automation.

10. Upgrading to the Microsoft Office 2010

The point is apparently but is often missed out by many. To provide a perfect user experience following the migration, upgrading to the Microsoft Office 2010 is essential to help in the training for the upgrade.

The above- mentioned tips allow for not just a successful migration but also making it useful for the business enterprises.

We provide SharePoint bespoke development services. If you would like to know more about the expertise of our SharePoint programmers, please get in touch with us at Mindfire Solutions.

Tips for Effective Migration to SharePoint 2013

In the recent times, with Microsoft launching SharePoint 2013, a large number of businesses are considering migration to this new edition to enhance their business processes. In fact, this new version of SharePoint is anticipated to revolutionize the way in which companies are building links amongst their knowledge workers, business processes as well as business-related content worldwide. This platform includes novel features such as enhanced document management capabilities with respect to sharing and contributing content, enhanced social features along with a renewed search experience. SharePoint 2013 is speedily positioning itself as one of the much sought after technology for the introduction of crucial organizational initiatives in the areas of social collaboration, enterprise content management and web content management.

SharePoint developers

The advanced features of Sharepoint make it vital for organizations to take certain points into consideration prior to adopting this latest platform. Let us discuss some of the guidelines that should be followed in order to achieve effective migration to SharePoint 2013.

1. Take care of hardware requirements: In case of SharePoint 2013 servers, minimum of 8 GB RAM and four 64-bit cores is needed for small environments while medium environments require 16 GB RAM. For every server operating in SharePoint 2013, location within a single data center is essential.

2. Operating system requisites: The ideal operating system incorporates 64-bit edition, R2 SP1 Windows Server 2008. The 2012 Windows Server operating system can also be utilized. You must consider migration to 64-bit servers before any other upgrade or migration.

3. Decide upon the destination before starting off: Doing this gives you a clear-cut idea of where you are heading to and this allows you to go for proper channelization of the resources at hand. For example, if you are using SQL 2012, use Windows 2012 along with an Office Web Application Server.

4. Divide current customizations into categories: It is advisable to categorize the customizations into three categories. The first category constitutes items such as custom authentication provider that would stop the project. You need to have solutions for this, or else the migration would not be a success. The second category comprises items that would not put a halt to the project but are required to be completed. It is good to address them once the migration is completed. Items that need to be eliminated make up the third category.

5. Realize environmental alterations: When you are deciding to go for Windows 2012, the environmental change that takes place needs to be taken into consideration. The SMTP server role has been deprecated by Windows 2012 and depending on the information, decision needs to be taken as to whether to use a more intricate configuration or go for installation of the deprecated feature.

6. Get every migration step scripted: This task involves restructuring site hierarchy, mounting content databases.

7. Conduct dry runs: While performing dry runs, you must follow a sequential guide. Through the dry runs, it is quite convenient to identify the disk space and timing requirements.

8. Go for proper space and time planning: Once the disk space and the upgrade time required are identified depending upon the dry runs, you can take necessary action. For instance, by adjusting the SQL server memory, the time for mounting as well as upgrading SharePoint can be decreased.

9. Follow dry runs with test: The only thing that separates a live run from a dry run is that the data is not updated, hence the end result should simulate the live migration. Taking this into account, through utilization of an alternate access mapping, it can be opened up to selected end users for testing, in order to validate the overall usability and the basic functionality.

10. Set up destination environment: It is advisable to configure and prepare to the maximum extent prior to migration. Once the configuration of the environment is done, the same will ensure smoother migration.

The above mentioned tips would go a long way in helping you plan your SharePoint 2013 migration. They will definitely help you enhance the overall efficiency of your SharePoint application development team.

We provide custom SharePoint development services. If you would like to know more about the expertise of our expert SharePoint developers, please get in touch with us at Mindfire Solutions.