7/10/2017 by Genady Vaisman
11/10/2016 by Vladi Gubler
3/29/2016 by Vladi Gubler
3/17/2016 by Vladi Gubler
The latest SharePoint version introduces a new setting that can be applied to each of the timer server instances: AllowServiceJobs
When this attribute is set to false, basically this server will not be able to execute timer jobs with SPJobLockType: Job ("Service Jobs").
This type of lock is needed to ensure that this timer job is executed only on one of servers, basically to prevent multiple executions of the same logic.
Several of our products are affected by this setting: Smart Import Pro, Smart Action Pro, Newsletter. These Products will not be able to function properly in regards of their background / timed functionality. Another impact may be on the installation process, in terms of failure in deploying required recourse files.
Mind that this behavior can be caused only on SharePoint 2016 farms, as previous versions did not allow this setting to be controlled.
You can use the following PowerShell script to determine the value of this property in your farm:
$farm = Get-SPFarm
$FarmTimers = $farm.TimerService.Instances
foreach ($ft in $FarmTimers)
write-host “Server: ” $ft.Server.Name.ToString();
write-host “Status: ” $ft.status;
write-host “Allow Service Jobs: ” $ft.AllowServiceJobs;
And the following script to enable it:
$farm = Get-SPFarm
$FarmTimers = $farm.TimerService.Instances
foreach ($ft in $FarmTimers)
if ($ft.AllowServiceJobs -eq $false)
write-host “Service jobs are NOT enabled on ” $ft.Server.Name.ToString();
write-host “Enabling service jobs”;
$ft.AllowServiceJobs = $true;
write-host “Service jobs are enabled on ” $ft.Server.Name.ToString()
This is the very first issue of our Partner Newsletter. We hope to be able to deliver a new issue every 2 weeks, informing you of product features, tips and tricks, implementation ideas and everything else you need to to boost your productivity and make Ultimate Forms the most invaluable tool in your toolbox. We understand that embracing a new platform is not without its challenges and we will do everything we can to make it as smooth as possible for you, because your success is our success as well.
We are actively looking for partners willing to share their story with others in a form of a short case study that we can then share with everyone through this newsletter. It doesn't have to be long (a page or two is more than enough) and you don't need to disclose any sensitive information. The goal is to create a productive and omnidirectional flow of ideas and best practices for everyone's benefit. We are considering various compensation mechanisms to make it worth your while. So please approach us with your ideas and we hope to see a partner case study in our next issue.
Several of Ultimate Forms components can interact with your Exchange Online:
- Alerts will send your alerts through Exchange Online mailboxes
- Import will import emails from Exchange Online mailboxes
- Print will send your print-outs to recipients through Exchange Online mailboxes
- Actions will automate printing and send the print-out through Exchange Online mailboxes
- Calendars will display your Exchange Online calendars in an app part, as well as allowing you to add new events directly from the app part
To be able to establish a secure connection to Exchange Online and send or receive items from Exchange Online, we have to receive a valid access token. Print is the simplest component, as it always runs interactively. When an access token is needed, you will be prompted for your consent (just once) and that's it. Pop-ups must be allowed so you will see the consent window.
For other components, it's a bit more complicated. As they mostly run in the background, there is no way to ask the user for the consent at runtime. We need to request an administrative consent beforehand instead. Because this consent applies to all the users of the tenant, a Global Administrator's consent is required. Depending on the component, it's given in different ways:
- Alerts: an administrator has to visit the Administration page (accessible from the gear icon in the top right corner of the Alerts page). There, click on the Grant button (at the button of Adminstration section). That's it, the app can now send alerts on your behalf. You can always retract your consent through your Azure administration settings.
- Import: when you first create an import profilee that uses Exchange Online, you will be prompted for consent. It is given just once, all subsequent profiles can be added without it.
- Actions: when you try to save a Print (or Active Directory) action, you will asked for consent, even if one has already been given in the past
- Calendars: when you add an Exchange data source, you will be asked for consent if it's the first ever Exchange data source.
That's it, not too complicated. Just make sure you have the necessary permissions, otherwise you will receive a Sign In error in the consent page and the error message will ask you to log in as an administrator.
Those of you coming from the on-premises environment are used to frequent version upgrades and try to keep your product up to date to take advantage of latest features and bug fixes. But how do you keep the app version up to date?
Well, the short answer is you don't need to. Because the app is hosted by us, it is always up to date. We constantly add new features and fix issue, to make sure you get the absolute maximum. Pay close attention and from time to time you will discover changes in the settings, new options, a more simplified approach and so on. Most server-side components require no action on your part.
The only components that do require some sort of intervention are the client-side form-oriented components (tabs, special columns and so on). The way these work is by uploading the latest scripts from our website into yours each time you save your settings. So when we release a new version of the script, it is not immediately available to your site, but must be uploaded by re-saving the settings. In some cases, the script is also cached by your browser and that cache might need to be manually cleared.
It doesn't mean that you actually need do anything proactively. The new script will be implemented when you take advantage of the new features and the old script is still functional and will work great.
So in conclusion: Office 365 approach gives you peace of mind, that's one of the greatest promises of the cloud!
We’ve all been in this situation – after a good long SharePoint based portal implementation – we start scratching our head to figure out what's the best way to back up the SharePoint farm and drown in the multitude of options – SharePoint native backup, stsadm or 3rd party products like AvePoint or EMC.
Now, Microsoft makes our life very easy by announcing Data Protection Manager as the main backup/restore application for SharePoint 2010.
Well, you might think that’s just another one of the many methods to protect SharePoint 2010 but DPM hides under its hood some pretty cool features which make it the #1 backup/restore application for SharePoint 2010. Here are some of them:
- Application Awareness – it is probably one of the most important features of DPM, DPM is aware that it's backing up SharePoint and not any other solution when backing up SharePoint databases. The meaning of this is that DPM works hand in hand with SharePoint and as the result of that the backed up data is more consistent as DPM makes sure that all the transactions that are occurring during the backup are taken into consideration.
- Item Level Recovery – DPM enables to recover a single object out of a full farm backup of a wide variety of SharePoint objects, such as documents, lists, document libraries, sites and sites collections.
- Protects SharePoint Search. In a large farm the search index can get rather big. In these situations - backing up search is crucial as in a case of disaster it could take very long time, even days, to index the farm again.
- Better Performance – DPM runs a very light agent which almost does not affect the farm production environment, with very low I/O, as it scans memory blocks to track changes in real -time.
- Self-Healing Backup Process – during the backup, if one of the backup objects, such as server or database, goes offline – DPM will proceed with the backup as planned and try to self-heal and add the offline object during the next planned backup.
- Reduce Storage Costs – DPM aims to use disks as the main backup storage and tapes for archiving. It's very understandable as disks are cheaper and more common than tapes and it's very easy and quick to restore data from them.
Furthermore, DPM reduces storage costs by minimizing backed up data by backing up only the changed blocks of data, meaning that every backup after the first full backup is approximately 5% (average daily data change on a SharePoint farm) of the whole farm data. That saves about 75% of storage space comparing to differential SharePoint native backup over a one month period.
- Search for Content (across Recovery Points). DPM enables to search the backed up data. It's very helpful if we want to perform an item level recovery, DPM search makes it very easy to locate an item to recover when needed and the time factor is crucial.
DPM is a great SharePoint 2010 backup/restore solution. And the fact it comes from Microsoft is a big advantage over other solutions as it integrates well with SharePoint within the backup/restore processes.
It very important to mention that DPM actually is the main Microsoft backup/restore solution for other Microsoft products such as Active Directory, Exchange, SQL, Virtual Server, file shares, System State and more. So it’s a great new backup/restore product family from Microsoft.
For more information – http://www.microsoft.com/dpm
Try it! There's also a 180 days evaluation download.