File:LECTIO PW.png

2019-12-02T13:11:14Z

Rum:

LMS Settings

2019-11-08T08:56:57Z

Rum: /* Remove learner method */

Please note that the settings described below cannot be found in all LMS integrations. Furthermore, some LMS integrations may not use 'sites' but rooms, cohorts, drives, etc.

===Automation Type===
This is not in use yet.

===Remove learner method===
Learnes will be removed from inactive courses / sites when

*'''Deleted in AD / Left school''' : user is not active or not known in UMS (remember that students will exist in UMS as long as they have activities)
*'''Finished on activity/course''' : user is removed from the course in the administrative system

No matter what, if a student drops out of a course before the course ends, the student will be removed from the site.

If a students finishes an activity prior to the end of the activity itself, the student will also be removed from the site. Example:an activity is set to start at 01/01-2019 and finish at 01/07-2019. The student is set to attend the activity from 01/01-2019 to 01/04-2019. In this case the student will be removed from the site at 01/04-2019.

When there are no learners on a site, the site will be deleted by LMS.

===Delete sites===
A site is deleted when there are no more students connected to it in UMS. There are two ways to delete a site:

*'''Auto delete'''. The site will automatically be deleted in the system when there are no more students connected to it.

*'''Manual delete'''. The site will only be deleted in UMS and not in the system.

===Send mail to teacher(s)===
Send an e-mail to teachers when they are connected to a site.

===Start publishing days before===
This indicates how many days a site should be active before it is published and visible for students. This must be a lower number than 'Create Days before'.

===Create Days before===
This indicates how many days a site should be created before it is active. This must be a higher number than 'Start publishing days before'.

===Delete Days after end===
A site is closed when all students have been removed. 'Delete Days after end' indicates how many days the site should be in the system before UMS deletes it.

===Teachers' rights on sites===
What access should the teachers have when added to the site.

===Students' rights on sites===
What access should the students have when added to the site.

===SQL Groups===
If a site is created with a setting where SQL Groups are used, members of the security groups inserted here will have teacher rights and access to that site. Please note that the group name written only covers that specific security group. If there are several security groups with similar names, letters before '%' will cover all groups with those letters. I.e. if there are English 1, English 2, and English 3, the group name 'Eng%' will cover all three security groups.
[[File:LMS Settings SQL groups.png|none|thumb|447x447px]]

==FAQ==

===How long can a student access a SharePoint site and/or an OneNote Classnotebook ?===
Students that drop out from a course/class before scheduled activity end will be disconnected from the site / OneNote. Only students that fullfills the course/class will have access to the site / OneNote after activity ends.

LMS Settings

2019-11-08T08:56:18Z

Rum: /* Remove learner method */

Please note that the settings described below cannot be found in all LMS integrations. Furthermore, some LMS integrations may not use 'sites' but rooms, cohorts, drives, etc.

===Automation Type===
This is not in use yet.

===Remove learner method===
Learnes will be removed from inactive courses / sites when

*'''Deleted in AD / Left school''' : user is not active or not known in UMS (remember that students will exist in UMS as long as they have activities)
*'''Finished on activity/course''' : user is removed from the course in the administrative system

No matter what, if a student drops out of a course before the course ends, the student will be removed from the site.

If a students finishes an activity prior to the end of the activity itself, the student will also be removed from the site. Example:an activity is set to start at 01/01-2019 and finish at 01/07-2019. The student is set to attend the activity from 01/01-2019 to 01/04-2019. In this case the student will be removed from the site at 01/04-2019.

When there are no learnes on a site, the site will be deleted in LMS.

===Delete sites===
A site is deleted when there are no more students connected to it in UMS. There are two ways to delete a site:

*'''Auto delete'''. The site will automatically be deleted in the system when there are no more students connected to it.

*'''Manual delete'''. The site will only be deleted in UMS and not in the system.

===Send mail to teacher(s)===
Send an e-mail to teachers when they are connected to a site.

===Start publishing days before===
This indicates how many days a site should be active before it is published and visible for students. This must be a lower number than 'Create Days before'.

===Create Days before===
This indicates how many days a site should be created before it is active. This must be a higher number than 'Start publishing days before'.

===Delete Days after end===
A site is closed when all students have been removed. 'Delete Days after end' indicates how many days the site should be in the system before UMS deletes it.

===Teachers' rights on sites===
What access should the teachers have when added to the site.

===Students' rights on sites===
What access should the students have when added to the site.

===SQL Groups===
If a site is created with a setting where SQL Groups are used, members of the security groups inserted here will have teacher rights and access to that site. Please note that the group name written only covers that specific security group. If there are several security groups with similar names, letters before '%' will cover all groups with those letters. I.e. if there are English 1, English 2, and English 3, the group name 'Eng%' will cover all three security groups.
[[File:LMS Settings SQL groups.png|none|thumb|447x447px]]

==FAQ==

===How long can a student access a SharePoint site and/or an OneNote Classnotebook ?===
Students that drop out from a course/class before scheduled activity end will be disconnected from the site / OneNote. Only students that fullfills the course/class will have access to the site / OneNote after activity ends.

UpdateImmutableID

2019-06-24T13:36:28Z

Rum:

This article describes how to extract immutable ID on users from a local AD / OnPremise AD and how to link this to Office 365. This is usefull when using AADC and users cannot be edited directly in the cloud.

====Step 1 - extract users as a list from SQL====
select distinct STUDIENR from students
where recordtype = 'employee'
and action = 'add'

Save results as "C:\users.csv"

====Step 2 - extract a list of Immutable ID's for users from local AD / onpremise====
Run the following powershell (elevated)
$usersTable = New-Object system.Data.DataTable “UsersTable”
$column1 = New-Object System.Data.DataColumn userPrincipalName,
([String])
$column2 = New-Object System.Data.DataColumn immutableId,
([String])
$usersTable.Columns.Add($column1)
$usersTable.Columns.Add($column2)
$users=Import-Csv -Path users.csv -Header “userSamAccountName”
foreach($user in $users)
{
$adUser = Get-ADUser -Identity $user.userSamAccountName
$adUserGuid = $adUser.ObjectGUID
$byteArray = $adUserGuid.ToByteArray()
$immutableId = “”
$immutableId = [system.convert]::ToBase64String($byteArray)
$row = $usersTable.NewRow()
$row.userPrincipalName = $adUser.userPrincipalName
$row.immutableId = $immutableId
$usersTable.Rows.Add($row)
}
$usersTable | Export-Csv “c:\UserExportIds.csv”
This will create a new CSV named UserExportIDs on c:\

<br />

====Step 3 - update Immutable ID on users in Office 365====
Change USERNAME@TENANT.onmicrosoft.com and USERPASSWORD in the following and run in powershell

$password = ConvertTo-SecureString -String "USERPASSWORD" -AsPlainText -Force
$LiveCred = New-object -typename System.Management.Automation.PSCredential -argumentlist "USERNAME@TENANT.onmicrosoft.com", $Password
$Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://outlook.office365.com/powershell -Credential $LiveCred -Authentication Basic -AllowRedirection
set-ExecutionPolicy remotesigned -Force
Import-PSSession $Session
Import-Module MSOnline
Connect-MsolService -Credential $LiveCred
$users = Import-Csv -Path “c:\UserExportIds.csv”
foreach($user in $users)
{
Write-Output $user.userPrincipalName
Set-MsolUser -UserPrincipalName $user.userPrincipalName -
ImmutableId $user.immutableId
}
The immutableID's have now been updated in Office 365.

Run AADC again and verify that users are linked correctly

UpdateImmutableID

2019-06-24T12:59:20Z

Rum:

UpdateImmutableID

2019-06-24T12:57:30Z

2018-04-05T12:16:01Z

Rum:

2018-04-05T12:01:38Z

Rum:

2018-04-05T11:41:23Z

Rum:

Oracle Driver

2018-04-05T11:28:48Z

Rum: Created page with "How to install Oracle Driver on UMS backend server"

How to install Oracle Driver on UMS backend server

MSGraphPermissions

2018-03-06T12:23:55Z

Rum: s

Setting MSGraph Permissions a long with Azure active directory, OneNote and SharePoint permissions is necessary for UMS to obtain access to the functions needed to create OneNote Class Notebooks and upcoming Teams integration.

== Creating App Registration ==
Go to [http://portal.azure.com Azure Portal] and login with you admin account( the same UMS uses).

When logged in goto Azure Active Directory:
[[File:MSGraph1.png|thumb|none|900x900px]]

Go to App registrations
[[File:MSGraph2.png|thumb|none|900x900px]]

Click on New application registration
[[File:MSGraph3.png|thumb|none|900x900px]]

Give the new App a name ex. "UMSGraph", Choose "Web app / API" in Application type, set "Sign-on URL" to "http://localhost". After setting Application Permission values click "Create"
[[File:MSGraph4.png|thumb|none|900x900px]]

You will return to previous screen, here click "your new app"
[[File:MSGraph5.png|thumb|none|900x900px]]

Click "Required permissions"
[[File:MSGraph6.png|thumb|none|900x900px]]

Click "Add"
[[File:MSGraph7.png|thumb|none|900x900px]]

Click "Select an API"
[[File:MSGraph8.png|thumb|none|900x900px]]

Click "Microsoft Graph"
[[File:MSGraph9.png|thumb|none|900x900px]]

Click "Select"
[[File:MSGraph10.png|thumb|none|900x900px]]

Click the left topmost checkbox next to "APPLICATION PERMISSIONS", and scroll down to next section.
[[File:MSGraph11.png|thumb|none|900x900px]]

Click the checkbox next to "DELEGATED PERMISSIONS"
[[File:MSGraph13.png|thumb|none|900x900px]]

Click "Select"
[[File:MSGraph15.png|thumb|none|900x900px]]

Click "Done"
[[File:MSGraph16.png|thumb|none|900x900px]]

Click "Add" again

Click "Select an API"

Click "Office 365 SharePoint Online"
[[File:MSGraph17.png|thumb|none|900x900px]]

Click "Select", as before - click the checkbox next to "APPLICATION PERMISSIONS" and "DELEGATED PERMISSIONS" and click Select.

Click "Done"

Click "Add" again and "Select an API"

Click "OneNote"
[[File:MSGraph18.png|thumb|none|900x900px]]

Click "Select", as before - click the checkbox next to "APPLICATION PERMISSIONS" and "DELEGATED PERMISSIONS" and click Select.

Click "Done"

Click "Windows Azure Active Directory" Permission.

Click the checkbox next to "APPLICATION PERMISSIONS" and "DELEGATED PERMISSIONS" and click "Save"

Select "Windows Azure Active Directory"

Click the checkbox next to "APPLICATION PERMISSIONS" and "DELEGATED PERMISSIONS" and click "Save"

[[File:Azure Active Directory.png|thumb|899x899px|none]]

Now click "Grant Permissions"
[[File:MSGraph19.png|none|thumb|900x900px]]
Click "Yes"
[[File:MSGraph20.png|none|thumb|900x900px]]
Permissions are now set.

Click "Properties"
[[File:MSGraph21.png|none|thumb|900x900px]]
Copy "Application ID" into Configurator ([[#SharePointOrganizationSettings|see last Picture]]) .
[[File:MSGraph22.png|none|thumb|900x900px]]
Click "Keys"
[[File:MSGraph23.png|none|thumb|900x900px]]
Set "DESCRIPTION" to ex. "UMS1" and choose "Never expires" in the "EXPIRES" Setup dropdown
[[File:MSGraph24.png|none|thumb|900x900px]]
Click "Save"
[[File:MSGraph25.png|none|thumb|900x900px]]
Copy the Key in the "VALUE" into Configurator ([[MSGraphPermissions#SharePointOrganizationSettings|see last Picture]]) !!! ATTENTION !!! the key value will never be visible again so ensure to copy it.
[[File:MSGraph26.png|none|thumb|900x900px]]

== Setup UMS to use Application just Created ==
In the UMS Configurator go to Modules->Office 365 and click "SharePoint organization settings"
[[File:UMSConfiguratorSharepointOrganizationSettings.png|none|thumb|600x600px]]
Choose your SharePoint organization setting and click "Edit..."
[[File:UMSConfiguratorSharepointOrganizationSettingsEdit.png|none|thumb|600x600px]]
<span id="SharePointOrganizationSettings">Input</span> your "Tenant Name" ex. "cortenso.onmicrosoft.com", paste the previously copied Application ID into "Client ID" field and paste previously copied KEY into "Client secret" and click "Ok"
[[File:UMSConfiguratorSharepointOrganizationSettingsEditWindow.png|none|thumb|600x600px]]
You are now all set to use the new MS Graph integration.

__FORCETOC__