To check if your district has Messenger configured, navigate to Communication > Messenger Settings > Email Settings and send yourself a test email by entering your email address and clicking Send Test Email. 

To see Messenger usage, navigate to Communication > Messenger Administration > Sent Message Log. If message logs exist, your district uses Messenger. 

Who to involve: Campus Administrator

1. Navigate to Communication > Messenger Settings > Messenger Settings
2. Update the Portal URL field to your new URL (Similar to your default (staff) Campus login URL but contains /portal/parents/. Use the District Search if you don't know your district's Parent Portal URL.)
3. Click Save.

To check if your district has LTI connections set up, navigate to Instruction > Settings > Digital Learning Applications Configuration.

If any applications are set up on this screen, select each one and look for any with an LTI Connection enabled. If one is enabled, your district uses LTI.

Who to involve: Campus Administrator

Navigate to Instruction > Settings >Digital Learning Applications Configuration > Settings & Management and click Auto-Configure.
The Campus Base URL will automatically update itself to your new district URL.

1. Navigate to System Settings > Custom Data and Links >SSRS Server Configuration.
2. If your district has a configuration set up, select it and analyze the Execution URL and Management URL.
   
   This applies to you if these URLs contain your old Infinite Campus domain. If the URLs do not reference your old Infinite Campus domain, your district may use a reporting server not hosted by Infinite Campus, in which case this does not need attention.

Who to involve: Campus Administrator; Reporting Server (SSRS) Administrator (optional)

1. Navigate to System Settings > Custom Data and Links >SSRS Server Configuration and select a configuration.
2. Update the Execution URL and Management URL to your new Infinite Campus domain. 
3. Click Save.
4. Click the Test Connection button to ensure your URLs are correct. 

This refers to the legacy method of setting up SSRS reports (i.e., not using the SSRS Configuration tools available within Infinite Campus).

Whoever set this up will have placed a .jsp on your Campus server at the file path listed in the URL field of the URL Link entry. 

The contents of that .jsp file likely make references to your Infinite Campus URL and need to be updated. The .jsp file must be updated to reflect any changes to your Infinite Campus URL.

1. Navigate to System Settings > Custom Data and Links > Custom Tool Setup.
2. Select each custom tool with a Tool Type = URL Link and check for URL values that end in .jsp. If so, you must update the .jsp file to refer to your updated Infinite Campus URL.

For example, 

Who to involve: Campus Administrator

If your district is now Cloud or Cloud Choice hosted:
You must update any references to your Campus URL within all .JSP files to reflect the new Campus URL. It's best to update your .JSPs with the new Campus URLs before the cutover. After the cutover, you can have your district's Authorized Support Contact provide the updated .JSPs to Campus Hosting through a case for a one-time upload.

If you anticipate needing to update your custom .JSP files in the future, we recommend considering the newer SSRS Dynamic Report Options approach (using the SSRS Server Configuration and SSRS Report Configuration tools) for creating custom reports. If this approach doesn't meet your needs, someone from your district will need to undergo the Package Building training provided by Campus Hosting to learn how to maintain your custom .JSPs. Your Authorized Support Contact can submit a case to Campus Hosting to request a quote for the Package Building training.

If your district is now In-District hosted (less common):
Assuming someone on your district's staff with server access configured this, have that person find this file on your Campus server and update the file to reflect any changes to the Campus URL.

Not to be confused with the more popular Data Extract Utility, the Data Extract Utility Client is a less commonly utilized, stand-alone program that compliments the Data Extract Utility and facilities the Data Extract Utility's PULL mode.

To check if your district utilizes this:

1. Navigate to System Settings > Data Utilities > Data Extract Utility (and Data Extract Zip Tool) and look for extracts with a Delivery Mode of PULL.

Who to involve: Whoever in your district installed the Data Extract Utility Client on any district server(s)

On any server that has the Data Extract Utility Client PULL mode tool installed:

• Delete the existing .bat and .preference files and recreate them using the Data Extract Utility Client tool (see instructions)
  
  OR
  
  

• Locate existing .bat and .preference files your district generated with the Data Extract Utility Client and modify every reference to your previous Campus URL to reflect any changes. You will not use your new Campus login URL verbatim but will reference it as you update the existing URLs.

Search for the Terminals tool within Infinite Campus. If you do not have this tool, you are not using the Infinite Campus Food Service (POS/Point of Sale) product.

Who to involve: Whoever in your district administers the Point of Sale terminals

For each Point of Sale terminal, do the following:

1. Open the Infinite Campus Point of Sale application
2. Enter the Admin PIN to get the POS Terminal Admin screen (if your district did not change the Admin PIN, the default Admin PIN is always 12345).
3. Click on the Edit Configuration button at the bottom of the screen.
4. Under Configurations, update the value in the Campus Login URL field to your district's new Campus login URL.
5. Leave Point of Sale Application Name and Point of Sale Terminal Name as-is.
6. Click on the Verify Campus button and click Save.
   (The Data Interchange URL should now reflect your new Campus URL.)
7. Under Load POS Data, click on the Data and Pictures button to perform a data load.

If your URL change has already occurred, you've confirmed your terminals' Campus Login URL field did not get updated by your district, and transactions have already occurred, have your district's Authorized Support Contact reach out to Campus Support through the Support Portal. A Campus Support advisor would need to remote into the machine and complete a re-insert of the transactions. Please be aware, this can be billable.

1. Navigate to Instruction > Settings > Google Drive Configuration
2. Check if Enable Google Drive is marked and the other fields in the tool are filled out. If so, your district has configured Google Drive Integration.

If you cannot navigate to the Google Drive Configuration tool, your district is not licensing Campus Learning nor actively using the Google Drive integration.

Who to involve: Whoever administers admin.google.com

Take note of your new Campus URL and provide it to your district's Google Admin.

These steps must be performed by your district's Google Admin, the same person who initially set up the Google Drive integration for your district. This is typically whoever manages admin.google.com (and therefore console.cloud.google.com) for your district.

1. Ensure you are logged into your Google Admin account, the same account used to set up the Google Drive integration initially.

2. Navigate to console.developers.google.com

   
   If the individual who originally set up the Google Drive integration within console.developers.google.com for your district is no longer employed at your district:
   
   

   You will probably not be able to find the Infinite Campus/Google Drive integration within console.developers.google.com, as it was stored directly under that person's Google account, so it must be accessed through that account. If this is your scenario, your current Google Admin may just need to recreate the Google project from scratch rather than modifying an existing project. See Google Drive Configuration > Show me the steps.
   
   

3. Select your Infinite Campus/Google Drive integration project from the drop-down menu.

4. Select Credentials

Now three changes must be made:

Web Application Client ID:

1. Under OAuth 2.0 Client IDs, for the client with a type of Web Application, select Edit (the pencil icon)
2. Under Authorized Javascript Origins, your previous Infinite Campus domain should be listed. Update this to reflect any changes to your Infinite Campus domain. For example, if your new Infinite Campus login URL is https://mydistrict.example.com/campus/mydistrict.jsp, the value here would need to be mydistrict.example.com
3. Select Save and return to the Credentials screen

API Key:

1. Under API Key, for your API Key (often named "API Key 1") either click on the name or select the three dots (⋮) and Edit API Key
2. Under Website Restrictions, your previous Infinite Campus domain should be listed. Update this to reflect any changes to your Infinite Campus domain. For example, if your new Infinite Campus login URL is https://mydistrict.example.com/campus/mydistrict.jsp, the value here would need to be mydistrict.example.com
3. Select Save

OAuth Consent Screen:

1. Select OAuth Consent Screen
2. Select Edit App
3. Under Authorized Domains, your previous Infinite Campus base domain should be listed. Update this to reflect any changes to your Infinite Campus base domain. For example, if your new Infinite Campus login URL is https://mydistrict.example.com/campus/mydistrict.jsp, the value here would be just example.com

If your district uses Google reCaptcha, updating the domain on Google's side is critical. If you do not take action after the URL change, users who trigger the captcha cannot log in until these steps are completed.

1. Navigate to User Management > Settings > Login Security Settings
2. Under Captcha Settings, check if Google reCaptcha is marked. If so, your district uses Google reCaptcha on the Campus login screen. 

Who to involve: Whoever in your district initially configured Google reCAPTCHA


To fix this:

1. Ensure you're logged into the Google account that was initially used to set up Google reCAPTCHA for your district
2. Navigate to www.google.com/recaptcha
3. Select Admin Console
4. On the Google reCAPTCHA admin screen, select your district's previously created reCAPTCHA setup from the drop-down menu.
   
   

   If you do not see your district's existing setup, you're probably not using the same Google account that was initially used to create the Google reCAPTCHA setup. If your district does not remember which Google account was initially used to create the Google reCAPTCHA setup, you may need to recreate it from scratch. See Login Security Settings > Google reCAPTCHA.
   
   

5. Select Settings (gear icon)

6. Under Domains, your previous Infinite Campus domain value should be listed. Update this (remove/re-add) to reflect your Infinite Campus domain changes. For example, if your new Infinite Campus login URL is https://mydistrict.example.com/campus/mydistrict.jsp, the value here should be mydistrict.example.com
7. Select Save

To check if your district has OneRoster connections, navigate to Instruction > Settings > Digital Learning Applications Configuration

If any applications are set up on this screen, select each one and look for any with OneRoster enabled. If one is enabled, your district uses OneRoster and must update its configuration.

Who to involve: Whoever in your district administers OneRoster configurations

In Infinite Campus:

1. Navigate to Digital Learning Applications Configuration > select your vendor > select your active OneRoster connection > Edit.
2. Copy out the Base URL and Token URL. These values will need to be updated within your OneRoster vendor's system.

In your OneRoster vendor's system:

The exact steps vary by vendor. Find the configuration screen in your OneRoster vendor system where the Infinite Campus credentials were initially entered and update the Base URL and Token URL.

 Some systems only require you to enter the Base URL. Systems' terms vary, so compare the format of the existing value to confirm it's the field you're looking for. 

For some vendors, credentials are entered on the backend by that vendor's support team rather than via a configuration screen within the vendor's system. Contact your vendor's support team for assistance.

To check if your district has Google Classroom connections, navigate to Instruction > Settings > Digital Learning Applications Configuration and look for Google Classroom. If present, select Google Classroom and see if any connections are enabled. 

Who to involve: Whoever administers admin.google.com at your district

When your Campus URL changed, your OneRoster Base URL also changed. Your district initially provided that OneRoster Base URL to Google Classroom, so now that it has changed, you need to update the corresponding value within Google Classroom so Google Classroom can continue to sync to your site.

In Infinite Campus:

1. Navigate to Digital Learning Applications Configuration > Google Classroom > select your active OneRoster connection > Edit.
2. Copy out the Base URL. This value will need to be updated within Google Classroom. You will also need to take note of the Client ID and Client Secret, as Google will make you re-confirm them.

In Google Classroom:

These steps must be performed by your district's Google Admin, the same person who initially set up the Google Drive integration for your district. This is typically whoever manages admin.google.com (and therefore console.cloud.google.com) for your district:

1. Navigate to https://classroom.google.com/admin
2. Select Update. (Do NOT select Remove.)
3. Enter the credentials from your Infinite Campus' Google Classroom connection, then select Update:
   • OneRoster Base URL (Host URL)
   • Client ID (Access Key)
   • Client Secret (Secret Code)

1. Navigate to User Management > Settings > SAML - SSO Service Provider Configuration
2. Check to see if your district has SSO configured and enabled (the Enable SAML Single Sign On checkbox is marked). If yes, your district utilizes SAML SSO, and your Identity Provider will need updated URL information. 

Who to involve: Whoever in your district administers your Identity Provider system

In Infinite Campus, complete these steps for each Infinite Campus environment (production, sandbox, staging, etc.) your district has configured to use SSO:

1. Navigate to SSO Service Provider Configuration and select your SSO configuration
2. Make note of the following values:
   • Service Provider Metadata 
   • Single Sign-On URL 
   • Single Sign-Out URL

These next steps must be completed by whoever in your district is the admin of your Identity Provider system. The exact steps vary depending on the Identity Provider you use. Reach out to your Identity Provider's support team if you need guidance on where to find the fields to update.

1. Log into your Identity Provider system.
2. Navigate to wherever SSO apps are configured in your Identity Provider system. Typically your district will have set up multiple Infinite Campus apps, one for each Infinite Campus environment you sign into with SSO: production, sandbox, staging, etc.
3. Edit your Infinite Campus app. Some Identity Providers will list only the Service Provider Metadata URL, whereas others will show the Single Sign-On URL and Single Sign-Out UR (not all Identity Providers support a Sign-Out URL). Update these values to reflect your new Campus URL.

A note on Entity ID:

You may see a value in your Identity Provider system called Entity ID. This corresponds to the "Campus (Service Provider) Entity ID value" on the SSO Service Provider Configuration screen in Infinite Campus. Although this value is derived from your initial Campus URL, it is a unique identifier and not a true URL, so its value does not change when your Campus URL changes. This means you do not need to change your Entity ID in your Identity Provider system.

If you want to change the Campus (Service Provider) Entity ID value in Infinite Campus for some reason, you can do so. However, ensure you also change it in all your non-production environments to correspond (i.e., your Sandbox site should have the same identifier that is in Production followed by _sandbox, or your Staging site the same identifier that is in Production followed by _staging, or whatever the site type is). When a non-production site is refreshed, its Campus (Service Provider) Entity ID reverts to the production value_sitetype, so it's important to be consistent on this value between environments. You do not need to change the Entity ID in your Identity Provider if you have not changed it in Infinite Campus.

If you're unsure whether your district utilizes ODBC connections, your district's Authorized Support Contact can contact Infinite Campus through the Support Portal, and we can confirm whether your district has requested ODBC account access.

After that point, if someone in your district has provided an ODBC connection string to some system, they're expected to keep a record of that.

Who to involve: Whoever has configured any systems, applications, or vendors to make use of ODBC access

If your district has configured any services to connect directly to the Infinite Campus database via an ODBC connection, Managed Services should have provided a new ODBC connection string as part of your URL change process. Be sure to update the ODBC connection string in any service that your district has configured to connect to Infinite Campus via ODBC connection.