Jump to content

psumner1992

Members
  • Posts

    69
  • Joined

  • Last visited

Reputation

105 Excellent

2 Followers

About psumner1992

Personal Information

  • Location
    Willenhall
  1. 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.
  2. 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.
  3. 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.
  4. 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.
  5. 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.
  6. 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.
  7. 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.
  8. Firmware update arrived this morning and worked as planned, Paxton were very quick and helpful.
  9. 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.
  10. 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?
  11. Looks like they have fixed the issue and are restoring services now.
  12. 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.
  13. 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.
  14. 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
  15. 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.
×
×
  • Create New...