psumner1992

We create the report based on class and include the following fields: Class Name Subject Class Teacher Then on the filter page: Class name begins with (prompt at runtime) And academic year (prompt at runtime) is set to 2020. When you run the report then, if your class names begin with the year, for example year 10, in the class name begins with field enter 10 and press ok. This will then return the results of all the teachers who are assigned to classes with class names beginning with 10 for the 2020 academic year. Hope this helps.

I created something similar a few years ago in SIMS, I think I did my report based on class as the focus and then class name as our class names begin with the year group so the filter could just look for the number. Will see if I can find the exact fields next week we used.

No apologies needed at all, every bit of advice I am extremely grateful of, I didn’t want to make any changes to the old sync just so I had an option of rolling back, although in the future I definitely would change it now to avoid these problems. We have made progress with Microsoft now, we’ve got it working by manually editing the MSConsistency ID in AD now and resyncing, we had an issue where we weren’t editing on the primary DC and the ID wasn’t replicating back quick enough so thought it wasn’t working. They are hopefully coming back to me early next week to see why we can’t get soft match working as I suggested could we calculate and update the IDs on bulk for the other 900 users but they suggested against it as it could be prone to errors, plus we need the soft match for groups as immutable ID doesn’t work with groups their only suggestion for groups currently is to delete them and start again, little bit troublesome when these groups are being used for Sharepoint site permissions.

Just to keep everyone informed I attempted this and due to the fact the old sync ID was based on ObjectGUID and not MSConsistency the ID’s didn’t migrate over with ADMT. The ability to set immutable ID to null has now been removed by Microsoft so at the minute I am having to force each one to match by logging into AzureAD and confirming both accounts are the same. Microsoft are looking at alternatives for me at the moment to see what they can do to rectify the fault. Think it might be a case of converting the online MSConsistency values and setting them manually in AD rather than trying to set the ID in AzureAD. Annoyingly it worked on my test tenancy. If I had changed the source anchor to MSConsistencyID prior then I probably wouldn’t have had this issue as ADMT probably would have migrated the value.

I have a feeling it’s objectGUID as it was set up a few years ago before the move to msds-consistencyguid, but will check Monday to see, if it is that’ll make things easier.

Thank you, I’ve got a test tenancy to test with so I’ll try with that first, take a copy of the ID’s and then try again with another VM and match if necessary before going with live system, it definitely is a death or glory moment. Can’t use the old sync server as this is currently on 2012 and we are upgrading everything to be 2019 on the new network.

Wondered if I could get some advice/reassurances on this please? We currently have an onsite AD domain syncing our users to Office365 with Azure AD Connect, but over the summer we are creating a brand new AD domain which we plan to sync to the existing Office365 tenancy, the o365 domain name is staying unchanged. I am looking for a way to keep existing AD users passwords the same and to ensure their existing O365 accounts don’t get deleted but sync up with the new AD domain. After a lot of research this is what I am planning to do: 1) Disable directory syncing in O365 2) Run the following PS script to clear ImmutableId for all users in office 365 to ensure soft matching takes place Get-MsolUser -All | Set-MsolUser -ImmutableId $null 3) Decommission old AAD connect server 4) Use ADMT to migrate existing accounts from old domain to new domain, ensuring UPN and proxy addresses get migrated over 5) Install AAD Connect on server in new domain 6) Test with a small batch of users in the syncing OU’s 7) Re-enable directory syncing in O365 8) Check accounts change from in cloud to synced, then continue with other users If any of you have completed this task before, have I missed any steps out or would you do anything differently? I have a call raised with Microsoft just to confirm the correct procedure but thought someone on here may have already been through this process in the past. Thank you in advance for any advice or support.

Firmware update arrived this morning and worked as planned, Paxton were very quick and helpful.

Thanks, yep it’s wired into the ACU and the reg numbers have all been added as tokens with the camera also visible in Net2, think it’s just the firmware needed for the camera to send the Paxton formatted data as I couldn’t find any other steps I’ve missed.

I think we have the same version slightly different model number, DS-2CD4A26FWD-IZSWG/P. Was it easy enough getting the firmware from Paxton as I’ve just emailed them as our camera is reading the reg plates but just not sending anything to Net2 so think I need this firmware to choose Paxton as the the Wiegand type? Any other setup tips?

Looks like they have fixed the issue and are restoring services now.

We also use item level targeting through user config policy and group policy preferences to assign printers to machines based on group membership or OU.

Does your PowerShell script map single libraries or does it do multiple ones? I’ve got a PS script to map each individual shared library for departments but would love something where I could add multiple ones together to simplify the process.

Try the section in this guide linked to enabling modern authentication. https://docs.microsoft.com/en-gb/azure/active-directory/hybrid/how-to-connect-sso-quick-start

We have found Office 2019 and Office365 have the best experience with SSO and OneDrive etc. If you have AADConnect setup with SSO for your users/devices then there should be very little else required. Over the Summer I am going to be supporting one of our local secondary schools through this process as we have already completed this successfully and started moving users to OneDrive for their storage earlier this year. I’ll take some notes to share, hopefully they’ll help others get through the process.

https://aadguide.azurewebsites.net/dirsync/aadconnect/ This is an old guide but gives you a feeling of what is needed.

Great, glad it worked. I remember I had to try a few different options before I got ours working but has been brilliant since setting up, best thing we ever did.

Our settings are: Registrar - Gamma IP Authentication - Do not require IP based Auth ID - main trunk number Options: Allow inbound calls - on Allow outbound calls - on Disallow video calls - on PBX delivers Audio - on Put public IP in SIP Via header - public IP Outbound Parameters: User part - CalledNum Host Part - GWHostPort Contact: User Part - AuthID Contact: Host Part - ContactURi Display Name - CalledName User Part - CalledNum Host Part - GWHostPort From: Display Name - OutboundLineID From: User Part - OutboundCallerID From: Host Part - GWHostPort User Agent - leave default Called Party Display Name - Default Called Party User Part - CallerNum Called Party Host Part - leave default Calling Party Display Name - OutboundCallerID Calling Party User Part - leave default Calling Party Host Part - GWHostPort PID Display - AuthID PID User Part - AuthID PID Host Part - ContactURi All other boxes set to leave default value. Hope this helps.

App-V is included as part of MDOP which is free for volume licensing customers with active software assurance through programmes such as OVS-ES. https://www.uis.cam.ac.uk/reports/ees-briefing-from-microsoft I would advise checking with your Microsoft Reseller though just to be 100% sure.

We have a mix of SOLUS for fixed desktop machines and then App-V package deployed with SCCM for staff laptops. This allows us to roll out the new version to staff laptops a few days before the main upgrade via SOLUS and staff on laptops simply double click the new shortcut on the desktop when we say it’s ready to use whilst continuing to run old version until this time and then we uninstall the old App-V package and remove old shortcut once new version is fully live. This allows us to update server and desktop machines overnight and staff come in the following day with all machines running latest version of SIMS with no downtime regardless of machine type. Not official Capita way, but has worked well with us over the last 3 years or so.

We have Gamma working with 3CX. I’m on annual leave at the moment but from what I can remember, we put the public IP into the options tab of the sip trunk and ticked Put Public IP in SIP VIA Header box to make sure it authenticated correctly. There was some back and fourth action with our ISP for firewall rules but eventually got it sorted, needed to make sure the traffic leaving our 3CX was using the public IP provided to gamma rather than shared IP from ISP otherwise it just wouldn’t register.

We sync room calendars from SIMS with Salamander up to room calendars in Office365. Then users wishing to book a room simply open their calendar, enter the date and time they’re interested in and it will show all the rooms available for the time in question. User chooses room, presses save and it adds it to the room calendar and their own calendar. Works very well.

We have it setup from Windows 7 days, can probably remove it, will be something for us to test over the summer to see what impact it has removing the redirection, but we have had no negative issues in having it redirected.

We have the OneDrive group policies configured for silently sign in users to the OneDrive sync client with their windows credentials. We use Azure AD connect to sync on-prem accounts to Office365 with seamless SSO configured. Machines are running the per machine version of OneDrive sync tool.

Local profiles and redirected appdata for staff and students for us has been much better than roaming profiles ever were, very rarely need to reset profiles anymore. First login times including OneDrive provisioning with silent SSO around 30-40 seconds, down to 15-20 seconds on future logins. Based on: win 10 1809 i5 (2nd gen & 3rd gen) 6GB - 8GB RAM 120GB - 240GB SSD