This guide explains two methods for downloading files from OneDrive using either the web version or the OneDrive client application.

1. Go to your web browser and navigate to office365.fdu.edu

Office 365

2. Sign in using your FDU account, enter your FDU username and password, complete DUO MFA verification by selecting “Approve”, and then select your Microsoft account (your FDU account)

3. After signing in, you will be taken to Web Outlook by default
4. Click the “App Launcher” (9 dots in the top-left corner)

5. Click “OneDrive”

6. In the left column, click “My Files”

7. All files on your OneDrive will be displayed under My Files. To select all files, hover to the left of “Name”

8. Unselect any OneNote notebooks

9. Click “Download” icon

10. OneDrive will prepare a .zip file which will download to your computer

1. Install the Microsoft OneDrive client for Windows or macOS

2. After installation, open OneDrive on your computer

2. When prompted, sign in using your FDU email and password

3. Review the default OneDrive folder location and click “Next”

4. When prompted to back up folders, click “I’ll do it later”

5. In the “Get to know your OneDrive” window, click “Next”

6. In the “Share files and folders” window, click “Next”

7. In the “All your files, ready on-demand” window, click “Next”

8. In the “Get the mobile app” window, click “Later”

9. When “Your OneDrive is ready for you” appears, click “Open my OneDrive Folder”

10. OneDrive setup is now complete
11. Locate your folder in OneDrive and drag or copy the files to your computer. Ensure files are saved outside the FDU OneDrive folder

After transferring your files, unlink your account using the steps below:

For Windows

1. Click the “OneDrive” icon in the taskbar

2. Click the “Gear” icon

3. Click “Quit OneDrive”

4. Confirm by clicking “Close OneDrive”

Your OneDrive account is now unlinked.

For macOS

1. Click the “OneDrive” icon in the top menu bar

2. Click the “Gear” icon

3. Click “Quit OneDrive”

4. Confirm the action

Your OneDrive account is now unlinked.

Download Limitations

• You cannot download files directly from the Shared view. Open the file and save a copy to your preferred location.
• The Download button may disappear if you refresh the page while viewing a folder. Go up one directory and return, or close and reopen the tab.
• Download limits include: 250GB file size limit; 10,000 total file limit; 10,000 files per folder.
• When downloading multiple compressed files (e.g., .zip or .mp4), the size limit is 10GB per .zip file and 20GB total.
• Files protected by sensitivity labels or IRM larger than 4MB will not be included in a bulk download. Download these files individually.

In the past, website subscriptions and renewals were approved by University Systems and Security (USAS), as the department held the role of both Information Security and Networking. An email would be sent to the department, and approval would be gained via an email response.

With the separation of Information Security from University Systems and Networking (USAN), a new process has been created to better serve those within the FDU community that utilize external websites for services.

Moving forward, requests for website subscriptions and renewals should be requested through this form below:

If information is missing, a representative of the SAMI Service Desk might reply inquiring more about the request. When all information has been gathered, the ticket will be forwarded to our Information Security Officer. They will review the request, engage the Networking team if necessary, and then either approve or deny the request (via email response) or inquire further, before closing out the ticket.

We hope this new process will help identify, track, and move requests quickly through the process.

Revised: May 1, 2025
Last Revised: February 1, 2024
Prior Revision: February 1, 2024

1. POLICY STATEMENT

FDU has implemented the FDU Alert system to expand and enhance its emergency notification methods. In the event of an emergency, FDU Alert may be used to provide pertinent information and instructions to FDU students, faculty and staff through voice, text messaging and/or E-mail. FDU Alert uses a mass notification system that sends emergency messages instantly and simultaneously to registered mobile phones, wireless devices and E-mail addresses.

Reason For Policy

This policy establishes the proper use and testing of the FDU Alert Emergency Notification System (FDU Alert).

Who Should Read This Policy

Members of the University Community including Students, Faculty, Staff, as well as all other individuals who have been registered to receive FDU Alert emergency notifications.

Website Address For This Policy

The website for this policy as well as other related FDU Alert information can be found at the following URL or by clicking on Web Shortcuts on the top right of the FDU Homepage.

Alert System

2. DEFINITIONS

These definitions apply to these terms as they are used in this policy.

Emergency	A sudden unforeseen crisis, usually involving danger, which requires immediate action.
FDU Alert System	The University’s emergency notification system is designed to alert, warn and inform registered members of the University Community of what to do in case of an emergency, a disaster, a crisis or any other situation that affects the FDU community. For example, receiving these alerts and messages could keep you from driving to campus only to find that a power failure has closed the campus.
FDU Alert Authorizer	Individual who has the authority to assess an emergency and activate the FDU Alert Emergency Notification System; this individual is authorized to contact an authorized Sender.
FDU Alert Sender	Individual who has been trained and is authorized to facilitate the actual sending of an Emergency Notification message.
Crisis	An unstable event or situation of extreme danger or difficulty, which is often sudden or unexpected, that disrupts the normal operations of the institution or its educational mission and threatens the well-being of personnel, property, financial resources and/or the reputation of the institution.
Timely Warning	Refers to the need to provide timely notification to the University Community after it is determined there is a credible threat to campus persons or property or when information is considered vital to the University community.
SMS	Refers to the Text Messaging method of FDU Alert delivery.
FDU Alert Spokesperson	An individual may be identified to respond to, and act as University spokesperson, to inquiries by students, faculty, staff, parents and others about an FDU Alert. Inquiries may be forwarded to the FDU Alert Spokesperson via the special call forwarding alert hotline.

3. OVERVIEW

Any time that an emergency situation arises, either on campus or in the immediate area of the campus, that in the judgment of an FDU Alert Authorizer poses an ongoing or continuing threat to the campus community, a campus “Timely Warning” will be issued. This warning may be issued through the FDU Alert system by one, all, or a combination of the following delivery methods.

• Voice mail or telephone notification
• E-mail
• Posted on the University website
• Posted notices
• Public address announcements
• Direct contact with individuals

Whenever possible, the FDU Alert Authorizer will consult with the University Director or Associate Director of Public Safety or another Authorizer prior to using FDU Alert messaging capabilities.

In an emergency, and upon activation by Authorizers and Senders, FDU Alert will send notifications to registered individuals at one, some, or all of the following registered points of delivery.

• Work Phone
• FDU E-mail
• Cell Phone
• SMS (Text Message)
• Alternate E-mail
• Home Phone
• Parent/Significant Other E-mail
• Parent/Significant Other Phone
• Parent/Significant Other SMS (Text Message)
• Parent/Significant Other Cell Phone

To provide the safest possible environment for students, faculty, staff, and visitors to FDU campuses, the University will strive to provide timely, reliable notifications by all possible means in the event of emergency. Generally, an emergency is any incident that involves the possibility of death, serious injury, or the threat of death or serious injury to people, or to University facilities, materials or property.

Fairleigh Dickinson University uses a variety of methods to provide emergency and safety information, including mass notification systems, web pages, door-to-door assistance from on-site staff and Residence Hall assistants, over-the-air broadcasts, and a consolidated communications system. Collectively, these capabilities are called “FDU-Alert“.*

The communication system permits broadcast messages to be sent quickly as voice calls to office, local home, or cell phones, and as text messages to cell phones or University and external E-mail accounts. This system will be used to announce and provide guidance in an emergency or crisis and to communicate relevant critical updates.

If an emergency occurs near but not on an FDU campus, and in other situations in which emergency responders determine and report that no apparent or imminent threat to that campus exists, an advisory may be posted on informational web sites, E-mails, or text messages only. In these cases, you may not receive an emergency notification directly to your phone.

University administration or individual campuses may, as an authorizer deems appropriate, use the communications system for other urgent messages related to administration or operation, such as campus closings due to adverse weather, unusual situations, or utility outages.

---

*More information about these services, as well as current emergency status or preparedness information for FDU, is planned for availability on the University’s emergency preparedness website once established.

4. POLICY

Proper Use of FDU Alert

FDU Alert is offered not to replace but to augment existing emergency notification methods, which include: University-wide broadcast E-mails, online updates via web and coordinated use of public media outlets, fire alarms, public address systems, and signs.

Any time that a serious situation arises either on campus or in the immediate area of the campus that in the judgment of the University Director or Associate Director of Public Safety, and whenever possible, in consultation with other members of the UEMT as applicable, poses an ongoing or continuing threat to the campus community, a campus “Timely Warning” will be issued. This warning may be issued through the FDU Alert system, voice mail or telephone notification, E-mail, posted on the University website, posted notices, public address announcements, and direct contact with individuals.

If, in the opinion of the local law enforcement authority, a message would hinder the police response or investigation and the local law enforcement authority has requested that we not send out a message, no message may be sent without the specific authorization of the President, or FDU legal counsel.

Limited Use of FDU Alert

Although the use of other emergency notification method(s) will be determined on a case-by-case basis, FDU Alert should only be used in the following situations:

1. an imminent threat of physical danger to the campus community;
2. a campus closure; and
3. certain Campus Crime Alerts as determined by Public Safety;
4. off-campus events that could impact health, safety, life or access to a campus.

The above situations can include but are not limited to ongoing criminal incidents, fires, chemical leaks, pandemics, campus-wide utility failures (such as gas, electrical, or water), and extreme weather conditions that result in a campus closure (e.g. snow/ice storms) or pose an imminent threat of physical danger to the campus community (e.g. tornado within close proximity to campus).

FDU Alert Authorizers

Only the people in the following positions have the authority to activate the FDU Alert emergency message system and author an appropriate message:

• President of the University
• University Provost & Senior Vice President for Academic Affairs
• Senior Vice President for Finance & Administration
• Campus Executives
• Deputy Campus Executive, Metropolitan Campus
• Associate Vice President for Communications
• Executive Director of Communications and News
• Director of Public Safety, Florham Campus
• Assistant Director, Public Safety, Florham Campus
• Director of Public Safety, Metropolitan Campus
• Campus Investigator, Public Safety, Metropolitan Campus
• Campus Executive, Vancouver Campus
• Business Manager, Vancouver Campus

FDU Alert Authorizers (“Authorizers”) have the authority to activate the system without consulting other Authorizers; however, when circumstances permit, an Authorizer should consult with at least one other Authorizer before sending a message.

FDU Alert Authorizer Responsibilities

Responsibility of Creating FDU Alert Messages

Authorizers have the responsibility to write and disseminate the appropriate message to be sent by Sender. For consistency, simplicity, and to minimize confusion, whenever possible, the Authorizer should base the message on one of the sample alert messages included in the Standard Operating Procedures manual.

This responsibility carries forward to writing and disseminating subsequent messages that must be sent to keep the recipients apprised of the status of the emergency event through to the conclusion of the emergency event with the transmission of an “All Clear-Resume Normal Schedule” message.

In the event more than thirty (30) minutes has passed while an emergency event is in progress, and there is no new information to communicate, the Authorizer should write a message(s) stating that the status of the emergency event remains the same, e.g., “Investigation continues, will communicate updates as new information becomes available.”

Messages should be written to support text to speech. Minimum or preferably no use of abbreviations and acronyms should be used. All messages must include an appropriate lead-in, for example, “!!FDU Florham Emergency Alert!!,” which includes where appropriate, the campus affected. Examples of these lead-in statements are included with the sample messages in the FDU Alert Confidential Operations Manual.

Responsibility of Authorizer to Prepare Additional Information

Alert Notifications and Updates Published via the FDU Website

Detailed messages and updates regarding the FDU Alert can also be made available on the University Website. Should it be necessary or appropriate to post additional information on the FDU website, it is the responsibility of the Authorizer to work with the Vice President for Communications or designee, to prepare and post the information on the University website in a timely manner. As this information will have wide and general exposure, it is critical to ensure that the information is current, correct, adequate, and consistent with the University messaging strategy.

It is the responsibility of the Authorizer, or designee as assigned by the Authorizer and the Vice President for Communications or designee, to keep vigil over the messaging to ensure accuracy and timeliness and message removal upon event termination.

FDU Alert Spokesperson to Other Inquiries

FDU Alerts will stimulate telephone inquiries to the switchboard, Residence Life, Public Safety, Enrollment Services & other key offices. Callers should be directed to the University mailbox for announcements and updates. In the unusual event where it is determined to be necessary to have a Spokesperson available for call handling, callers will be directed to a special hotline with ultra-call forwarding setup to transfer to the FDU Alert Spokesperson.

The FDU Alert Spokesperson is an individual identified by the FDU emergency response teams to respond to inquiries by students, faculty, staff, parents, and others about an FDU Alert. Inquiries will be forwarded via the special call forwarding alert hotline.

The following are attributes for The FDU Alert Spokesperson:

• Must provide contact information (and back up) to the switchboard and emergency management teams
• Must be available to take calls continuously throughout the emergency*
• Must be aware of the event and current activities and commentable actions
• Must be media aware
• Must have the power to speak to the event with autonomy and authority

---

*A special phone number with Remote Call Forwarding will be utilized for this purpose.

Emergency Event Status Reports on the FDU Website

The FDU Website Homepage provides an FDU Alert Icon under Web Shortcuts that links to a dedicated webpage containing information on the current status of the University’s operations. As referenced above in Section 4.3.1.3, in the event there is an emergency, the Authorizer will work with the Vice President for Communications or designee to prepare and post a message providing current information concerning the emergency event and the status of the University’s operations, which will be posted on the website.

FDU Alert Senders

FDU Alert Senders (“Senders”), upon the request of Authorizer(s), have the authority to activate the system, enter messages under the direction of the FDU Alert Authorizer(s), and initiate the send message process. All FDU Alert Senders are provided with appropriate access to the secured FDU Alert emergency notification system and necessary training.

Sender names and contact information are included in the FDU Alert Operations Manual.

FDU Alert Senders Responsibilities

Senders are required to respond to Authorizer requests to facilitate the timely activation of the FDU Alert System. Senders acknowledge that time may be of the essence and will fulfill the request or immediately notify another Sender to fulfill the request. The transfer of such transfer of control requires Authorizer and/or emergency response team acknowledgment.

FDU Alert Senders will advise the FDU Alert Authorizer(s) when the message send process has been initiated and the sender can confirm delivery of such messaging.

Message Content

Any message sent using FDU Alert should be as brief as possible and should, if appropriate, typically contain the following information:

• The reason for the message;
• Any response required;
• Location (campus) of event;
• The duration of the emergency and any relevant dates and times;
• Methods to obtain further information; and

When circumstances permit, before sending a message, Authorized Senders should consult with the relevant University administrator(s) regarding message content.

While brevity and abbreviations will reduce a message size, care must be taken to ensure that all messages are brief, concise, accurate, and understandable. Sample messages are included in the FDU Alert Confidential Operations Manual.

After Message Review

After a message is sent using FDU ALERT, the Authorized Senders and the University Emergency Management Team will meet as appropriate to discuss the emergency, the results of the alert, and compliance with the FDU Alert Policy.

FDU Alert System Testing

System Wide Delivery Testing

Once every Fall and Spring semester, a live test of the FDU Alert system will be conducted. During the test, one or more messages will be transmitted to every individual registered in the system using every delivery method for each point of contact (phone, e-mail, SMS, etc.) The FDU Alert message(s) sent during the test will clearly state “THIS IS A TEST,” so that it is clear that there is no actual emergency.

FDU Alert Senders

At least once per calendar month, FDU Alert senders will test the FDU Alert system by sending themselves a test message. The message sent during this test will clearly state “THIS IS A TEST BY AUTHORIZED SENDER,” so that it is clear that there is no actual emergency

Service Provisioning

Regular Reminders to University Community to Register/Update FDU Alert Individual Database Record

The effectiveness of any alert system depends upon the accuracy of the contact information in its database. All students, faculty, and staff will therefore receive notices/reminders prior to the semester’s scheduled test to review/update their emergency contact information. Emergency contact information can be modified at any time by logging onto Self-Service.

5. EMERGENCY LEVELS AND INSTITUTIONAL MESSAGING GOVERNANCE

The following are three levels of emergencies and suggested methods of communications and notifications for each. No other use of this FDU Alert System is permitted.

Level 1 Emergency – Informational

Circumstance:

• incident has occurred
• incident is contained and/or well defined
• continuing activity/investigation
• caution conditions exists
• timely follow up communications required

Examples include:

• natural disaster
• aircraft crash, or similar event, near campus
• major structural collapse
• snow closings
• elevator accident
• must know information – (e.g. “Because of bad weather the University will close at…” and “An electrical cable to the SUB has been damaged and electrical power will not be restored until…”)

The “Authorizer” should use the following formats: E-mail/WWW/Text Messaging/Posted Notices/Public Address Announcements. Based on the event and any unusual circumstances, voice messaging may be used at the “Authorizer’s” discretion…

Level 2 Emergency – Life and Safety Alert

Circumstance:

• incident has occurred and/or is continuing
• incident is contained but may be extensive
• cautions exist
• continuing/on-going activity/investigation
• timely follow up communications required

Examples include:

• bomb threat
• contained/small scale explosion/fire
• act of violence on campus
• fire confined to an area
• contained/small hazardous material spill or release
• buildings without electricity, heat or water
• major building flooding

The “Authorizer” should use the following formats: E-mail/WWW/Text Messaging/Posted Notices/Public Address Announcements/Direct Contact with Individuals as necessary.

Level 3 Emergency – Imminent Life or Safety Alert – Immediate Action Required

Circumstance:

• incident has occurred and/or is continuing
• scope of incident may be undefined
• alert action required
• cautions exist
• continuing/On-going activity/investigation
• time is of the essence follow up communications

Examples include:

• evacuations
• on-going violent campus demonstrations
• intruder alerts
• radiological incident
• contained or uncontained hazmat/hazardous material spill or release
• large explosion/fire
• aircraft crash, or similar event, on campus
• acts of terrorism
• confirmed explosives devices

The “Authorizer” should use all available formats: Voice Message/Voice Mail/E-mail/WWW/Text Messaging/Posted Notices/Public Address Announcements/Direct Contact with Individuals as necessary

No other use of this FDU Alert System is permitted.

6. FDU ALERT EMERGENCY NOTIFICATION SYSTEM:  CONFIDENTIAL OPERATIONS MANUAL

The Confidential Operations Manual is provided to all members of the University Emergency Management Team. The following information will be included in the Confidential Operations Manual.

• Notification Process
• FDU Alert Authorizer Contact List
• FDU Alert Sender Contact List
• Recipient Groups
• FDU Alert Activation Options Screen
• Sample Messages

---

Neal Sturm
Vice President and CIO
sturm@fdu.edu

Gail Lemaire
Office of Risk Management
gail_lemaire@fdu.edu

---

Section – About

Part : What is FDU Anywhere?

What is FDU Anywhere?

FDU provides remote access to many software applications typically found in university computer labs. This new Virtual Desktop Infrastructure (VDI) gives users access to a Windows desktop environment along with many General Lab Software, without requiring downloading and installing programs on a user’s personal equipment. The service, called FDU Anywhere, is powered by University Systems and Networking (USAN) and can be found at anywhere.fdu.edu.

FDU Anywhere

Using FDU Anywhere is like walking into one of FDU’s computer labs. Upon logging in with your FDU NetID and password, you will have access to the virtual platform. To find a list of currently available software on FDU Anywhere, use the FDU Software Catalog. A listing of available Free and Open Source software can also be found by visiting the FDU Software Catalog.

The FDU Software Catalog provides an up-to-date catalog of software available to Faculty, Staff, and Students at the university:

Part : System & Network Requirements

System & Network Requirements

System Requirements

FDU Anywhere is a powerful resource with a lightweight footprint. In order to utilize FDU Anywhere, you must have the following:

• Any device with a browser that supports HTML 5 will work. HTML 5 is supported by almost all desktop and mobile browsers including Google Chrome, Apple Safari, Microsoft Edge, and Mozilla Firefox
• An internet connection
• FDU NetID credentials

Network Requirements

For the best experience, while using FDU Anywhere, your network should:

• Have a download speed of at least 5Mb/s or more
• If your download speed falls below 5Mb/s, the connection could become unstable and cause issues with your stream
• Have an upload speed of 5Mb/s or higher
• An upload speed of 5Mb/s is enough to use a basic mouse, keyboard, and controller. More bandwidth-heavy devices such as webcams, microphones, and external storage devices can use up to 100Mb/s
• Wired network connections are preferred over Wi-Fi network connections whenever possible
• Wired network connections are more stable and offer more bandwidth over Wi-Fi

For graphics-intensive applications, like Adobe Creative Cloud and Autodesk, we recommend using a wired network connection instead of Wi-Fi, ideally with a bandwidth of 5 Mbp/s.

Wi-Fi networks with 5Ghz rated wireless connections are preferred over 2.4Ghz wireless routers and provide better performance.

VPN Applications and Connections

Testing your Connection

Your experience with FDU Anywhere greatly depends on your internet connection. Testing your connection can help you identify and correct most issues.

To test your Internet connection speed, click the link below:

Internet Speed Test

Section – Basics

Part : Using FDU Anywhere

Using FDU Anywhere

FDU Anywhere is available to all students and accessible by following the instructions below:

Accessing FDU Anywhere

1. From any web browser, visit “anywhere.fdu.edu“

FDU Anywhere

2. Use your FDU Credentials (NetID and associated password) to complete the login to the FDU Anywhere

General Lab

2. The selected app or desktop opens in a new browser tab

Log Out of FDU Anywhere

Logging out is a critical step in making sure others continue to be able to easily access FDU Anywhere services. To log out of FDU Anywhere, follow these steps:

1. Click the Windows “Start” button
2. Click your “Name“
3. Click “Sign Out“

4. On the upper left-hand side, click the “Hamburger” menu icon

5. Click “Log Out“

6. Click “OK” to confirm Logout

Automatic Session Logout Policy

To help make FDU Anywhere as available as possible to all students, accounts that have been inactive (or idle) for 15 minutes will automatically be logged out.

Part : Accessing and Using OneDrive

Accessing and Using OneDrive

There are many ways in which you can access and save files within FDU Anywhere. Fairleigh Dickinson University highly recommends saving all files on your FDU Microsoft 365 OneDrive which is accessible within FDU Anywhere. There will be a first-time setup and initialization process required to use OneDrive within FDU Anywhere.

Setup and Initialization Process

Accessing your Microsoft 365 OneDrive account is done easily by following these instructions:

1. From the FDU Anywhere General Lab, single click on the “OneDrive” icon found on the Windows desktop

2. Enter your FDU NetID and click “Next”
   • Follow the FDU standard single sign-on prompts to complete the login process

3. You have successfully logged into OneDrive, click “Next“

4. Microsoft OneDrive may prompt you to backup your folders, click “Next” to skip this step

5. A brief overview will be given on OneDrive, to begin, click “Next“

6. When the tutorial is finished, click “Later“

7. OneDrive setup is complete and ready to use. Click the “X” to close the window or “Open My OneDrive Folder” to access files

Using OneDrive

Using Microsoft OneDrive within FDU Anywhere is very similar to accessing, saving, and opening files on a computer. Just open up File Explorer and look for OneDrive – Fairleigh Dickinson University.

Part : Working With Files

Working With Files

Zipping Files

if you need to zip files to submit them to Webcampus, please follow these instructions:

1. Click the file or folder

2. Click on 7-zip then click “Add to Archive“

3. Change Archive Format to “zip” like in the picture below, then click “OK” to zip your files

The zip archiving process could take some time depending on the size of the file. Once completed, the file will be in the same location as the folder. You can then email or upload your file to your professor.

Alternate Way to Zip Files

1. Click “Start” on the taskbar on the left-hand side
2. Type “7zip” and click on 7-zip File Manager that appears

3. Navigate to the location of your saved file/folder and click to highlight, then click the “Add” button at the top

5. Change “Archive Format” to “zip” and then click “OK” to zip your files

The file will now be zipped and you will find your file in the same folder as the project folder or file you wanted to zip.

Submitting Files to WebCampus

To successfully submit your coursework to WebCampus, it is best to use the Google Chrome, Mozilla Firefox, or Microsoft Edge web browser located on the desktop of FDU Anywhere.

To submit your coursework to Webcampus, you can log on from within FDU Anywhere. For more information on Webcampus visit:

Part : Keyboard Shortcuts

Keyboard Shortcuts

Sometimes you may want to copy and paste content from your own computer to an FDU Anywhere desktop or application. You can do this using the copy-and-paste menus or keyboard shortcuts, for example, “Ctrl+C” and “Ctrl+V“.

If you cannot copy and paste for any reason, we recommend using our FDU OneDrive service to access any files not found in FDU Anywhere.

Windows OS to FDU Anywhere

1. Highlight the text you want to copy from your computer
2. Press “CTRL+C” to copy the selected text
3. Move the cursor to the paste location in FDU Anywhere
4. Press “CTRL+V” to paste the text

Your macOS to FDU Anywhere

1. Highlight the text you want to copy from your computer
2. Press “COMMAND+C “to copy the selected text
3. macOS also supports “CTRL+C“

4. Move the cursor to the paste location in “FDU Anywhere“
5. Press “CTRL+V” to paste the text

Section – Support

Part : Getting Support

Getting Support

SAMI Support

Part : Network Optimization

Network Optimization

If you are experiencing issues while using FDU Anywhere, please use the following tips as guidelines to help improve your experience.

Power-cycle your Modem/Router

Power cycling your modem and router allows them to reset and re-establish a connection to your Internet Service Provider (ISP). Shut down your computer and unplug your modem/router. Plug them back in after 60 seconds and watch the lights on your modem/router. Once the lights are on and steady, start your computer.

Keep all your Local Components Up-to-date

Check that your modem/router and your local computer are totally up to date. This includes the operating system, driver, and browser updates.

Disconnect/Turn off any Devices that are not in use

Some devices could be using bandwidth while on standby. Gaming consoles, for example, might download and install updates. Turn off these devices to keep your bandwidth free.

Use an Ethernet Cable

Using a wired Ethernet connection will make your connection more stable and eliminate additional latency compared to a wireless connection.

Change your Wi-Fi Configuration

If a wired Ethernet connection is not possible or your device requires a wireless connection:

• Connect to a 5GHz wireless network. Some routers offer both 2.4GHz connections and 5GHz
• Place your devices (such as a computer or smartphone) and your router closer to each other

As part of an ongoing effort to combat phishing scams and enhance email security, the Office of Information Resources and Technology (OIRT) is implementing the Domain-based Message Authentication, Reporting & Conformance (DMARC) protocol. DMARC monitors mass mailing, hosted vendor applications, and mail servers used to send emails on behalf of the University (e.g., fdu.edu, wc.fdu.edu).

Important Email Delivery Requirements

For Individual FDU NetID Users

No action is required. You can continue to use Outlook as you normally would.

For Mass FDU Email Users

Fairleigh Dickinson University prioritizes information security and is enforcing these email authentication standards to ensure reliable and secure email delivery. All non-FDU services used by FDU users and departments must adhere to these best practices to ensure proper delivery of emails to FDU recipients. Failure to comply will result in email delivery failures.

If you plan to use any new service to send emails to FDU users, you must submit a DMARC Request form at least one month in advance. For any existing email delivery issues, submit a SAMI ticket.

DMARC Form

As an FDU user, you generally won’t need to manage the technical details of DMARC unless specifically requested by OIRT. While DMARC is typically managed by your email provider, individuals or departments using external services like CRM tools (e.g., Constant Contact, MailChimp) for bulk emailing must ensure that DMARC is enabled within those platforms. This helps prevent messages from being marked as spam.

OIRT will provide guidance and work with the service provider after you submit a DMARC Request form.

For those interested in the technical aspects of this email security standard, continue reading below.

How DMARC Works

DMARC is an email authentication, policy, and reporting protocol that operates in two primary ways:

• It detects unauthorized activity and specifies how to handle unauthorized emails (e.g., placing them in the spam folder).
• It identifies legitimate senders, including emails sent by FDU or approved/verified email services.

DMARC uses two key technologies to verify emails:

What is it?

Domain Keys Identified Mail (DKIM) verifies the identity of an email sender to prevent email spoofing. It acts as a unique electronic signature, allowing recipients to confirm that a message claiming to be from you was indeed sent by you.

Why is it important?

DKIM helps email hosts (e.g., Microsoft, Google) detect phishing attempts. By verifying the message’s signature, DKIM ensures that the sender address belongs to its rightful owner and confirms that the message has not been tampered with during transit.

How does it work?

DKIM adds a hidden, unique digital signature to your outgoing emails. A public “key” is published online under your domain or subdomain. When a recipient receives your email, their system uses this public key to verify the signature. If it matches, the email is confirmed as authentic and unaltered, helping it reach the inbox and preventing spoofing.

What is it?

Sender Policy Framework (SPF) is like a digital “authorized senders” list for a domain. When an email arrives, the recipient’s system checks whether the sending server is approved by the domain owner. If the server isn’t on the list, the email may be flagged as spam or rejected.

Why is it important?

SPF helps prevent spammers and phishers from forging the “from” address in email messages. It allows email hosts (e.g., Microsoft, Google) to verify that the server sending the email is authorized to send on behalf of the specified domain.

How does it work?

Your email provider (e.g., Microsoft 365) publishes a list of authorized servers that can send emails on behalf of your domain. When a recipient’s mail server receives a message, it checks this list to verify the sending server. If the server is authorized, the message is considered legitimate. If not, the recipient’s mail server may reject, quarantine, or flag the message as spam based on its policy.

1. PURPOSE

The FDU IT Business Relationship Management Office (BRMO) Charter Framework defines how OIRT builds and maintains strong working relationships with the University’s academic and administrative departments. It creates a clear model for communication, planning, accountability, and partnership so that each department has a known IT contact and a consistent experience working with OIRT.

OIRT exists to serve FDU’s students, faculty, staff, and the larger mission they support. Serving that mission well requires more than technical skill. It requires understanding what each part of the University needs, when it needs it, and why it matters. BRMO formalizes the relationship work that strong IT leaders at FDU already do naturally, making it more consistent, visible, and scalable across the department. As FDU grows in ambition and complexity, OIRT must also grow in its ability to serve as a true institutional partner.

Today, the quality of the relationship between OIRT and a given department can depend too much on individual initiative. Some departments feel well served and well informed. Others experience IT as difficult to navigate. They may be unclear about who to contact, what is being worked on, or how to raise a concern or opportunity. This inconsistency is not a reflection of effort. It reflects the absence of a shared model for how OIRT engages with the University. BRMO establishes that model so every department receives the same quality of partnership regardless of who their IT contact happens to be.

2. DEFINITIONS

These definitions apply to the following terms as they are used in this charter.

BRMO	The Business Relationship Management Office (and Officer) is the function within OIRT that owns, manages, and develops the relationship between the IT organization and the University’s academic and administrative departments. It is not a help desk or an escalation queue, though it can support escalation when needed. Its main role is to create a strategic partnership with the associated business unit.
BRMO Practitioner	An IT leader assigned responsibility for managing the relationship with one or more business units. Practitioners are usually existing IT leaders, not a separate team.
Business Partner	A leader or representative from a University department who works with IT to share needs, priorities, and planning considerations.
Stakeholder	Any faculty member, staff member, or student affected by technology decisions made by IT. Each stakeholder group should have a Business Partner who can represent its interests.

3. FRAMEWORK OVERVIEW

How BRMO Fits Within FDU IT Governance

BRMO is the relationship layer of OIRT governance. It operates continuously through regular meetings, conversations, and planning cycles so IT remains connected to the University day to day and month to month. In addition to standard intake channels, BRMO Practitioners identify significant needs through relationship conversations and make sure those needs are shaped and elevated to IT leadership for planning, prioritization, and decision-making.

Business Relationship Management

Business Relationship Management (BRM) is the practice of building and maintaining a strategic partnership between IT and the departments it serves. It includes understanding business needs, communicating IT capabilities and constraints, aligning technology investments with departmental priorities, and making sure the value of IT is understood by the people who rely on it. At FDU, BRMO does not create a new team. It formalizes work already being done by IT leaders and raises it to a consistent institutional standard.

What BRMO Is and Is Not

BRMO Is	BRMO Is Not
A structured model for how OIRT builds and maintains relationships with University departments	A help desk or escalation queue for IT support issues
A way to surface technology needs, challenges, and ideas from the University to IT	A project management office or delivery function
Proactive engagement, not reactive ticket management	A guarantee that every request will be fulfilled
A bridge between departmental needs and IT planning and governance	A replacement for existing IT service channels
A feedback loop that helps OIRT understand whether it is delivering value	A committee that only meets and produces reports

BRMO is an active practice embedded in how IT leads.

4. STAKEHOLDERS AND RELATIONSHIPS

BRMO Practitioners (IT Side)

BRMO Practitioners are IT leaders, typically directors, managers, or senior staff, who are assigned responsibility for managing the relationship with one or more University departments. Each Practitioner serves as the primary OIRT point of contact, advocate, and communication channel for assigned business partners. They are responsible for understanding their partners’ environment, surfacing needs into IT planning, and making sure partners stay informed about relevant OIRT activities, initiatives, and decisions. At FDU, being a BRMO Practitioner is not an extra assignment. It is a core leadership expectation.

Business Partners (University Side)

Business Partners are the leaders or designated representatives of FDU departments who engage with their assigned BRMO Practitioner. They may include deans, department heads, administrative directors, or delegates. Their role is to represent departmental technology needs and priorities, participate in regular engagement sessions, raise ideas and challenges, and provide feedback on OIRT services and initiatives. Business Partners are not expected to be technical. They are expected to be honest about what is working, what is not, and where technology could better support their goals.

Relationship Alignment Model

Each major University department or functional area is assigned a primary BRMO Practitioner. The CIO’s office maintains the master relationship map and reviews assignments annually or when organizational changes occur. Assignments should reflect the Practitioner’s subject matter knowledge, existing relationships, and workload. Where a department has complex or high-volume technology needs, a secondary Practitioner may be assigned. The goal is simple: no department should ever have to wonder who their IT contact is.

5. OPERATING MODEL

Core Responsibilities of a BRMO Practitioner

• Maintain a regular meeting cadence with assigned business partners, at minimum quarterly and ideally monthly for active or complex relationships.
• Set and share a standing agenda that covers ongoing OIRT activities relevant to the department, open items, and space for new topics.
• Surface project ideas and technology needs from the University into OIRT planning and prioritization processes.
• Communicate proactively so partners do not learn about OIRT changes, outages, or initiatives from someone else first.
• Serve as the escalation path when a business partner has a concern that normal service channels have not resolved.
• Represent the business perspective in internal OIRT conversations, planning sessions, and prioritization discussions.
• Track and follow up on open commitments.
• Share an annual OIRT roadmap summary relevant to each department so partners understand what is planned and why.

Meeting Cadence and Engagement Model

• Monthly or bi-monthly one-to-one meetings between the Practitioner and the primary Business Partner, typically 30 to 60 minutes.
• Quarterly business reviews for higher-complexity relationships that include a broader view of IT services, performance, and upcoming changes.
• Annual planning conversations to align IT priorities with departmental goals for the coming year.
• Ad hoc check-ins as needed for urgent issues, major projects, or significant changes.

Practitioners should maintain brief notes from each meeting and track open items. A shared document or email summary is enough. The goal is continuity, not paperwork for its own sake.

How Needs Surface and Get Addressed

When a Business Partner identifies a technology need, challenge, or idea, the BRMO Practitioner receives it, assesses it, and connects it to the right path within IT.

• Operational issues: directed to the appropriate IT service team, with the Practitioner monitoring for resolution.
• Enhancement requests: logged and brought into the appropriate IT planning cycle.
• New capability ideas: assessed for fit and, if viable, brought to IT leadership for prioritization and planning.
• Information needs: answered directly by the Practitioner.

No idea or need should go unacknowledged. If IT cannot address something, the Practitioner is responsible for explaining why and, where possible, offering alternatives.

Escalation Path

If a business partner has a concern that cannot be resolved at the Practitioner level, the escalation path is BRMO Practitioner, then IT Director or Manager, then CIO. Business Partners should always know where their issue stands and who is accountable for it.

6. DESIRED OUTCOMES

For Business Partners

• A known, trusted OIRT contact who understands the department’s goals and constraints.
• Confidence that OIRT is aware of departmental needs and actively working to address them.
• Advance visibility into OIRT changes and initiatives that will affect the department.
• A clear path to raise ideas, escalate concerns, and receive substantive answers.
• The experience of OIRT as a solutions-oriented partner in achieving the department’s mission.

For the IT Team

• A structured understanding of each department’s priorities, challenges, and technology maturity.
• Earlier visibility into demand, enabling more effective planning and resource allocation.
• Fewer surprises for both OIRT and the FDU community it serves.
• A more informed basis for prioritizing projects and investments.
• A clearer demonstration of the role technology plays in advancing FDU’s goals.

For FDU

• Technology investments that better reflect the University’s actual needs and priorities.
• Increased transparency and confidence between OIRT and the departments it serves.
• A stronger foundation for strategic OIRT planning and governance.
• An OIRT organization recognized as a partner in advancing FDU’s academic and operational mission.

7. MEASURING SUCCESS

Critical Success Factors

BRMO succeeds when Practitioners engage consistently, business partners participate actively, and both sides experience the relationship as genuinely valuable. The most important early signal is whether business partners feel more informed and better served than before, and whether OIRT has clearer, more actionable insight into University needs. These results take time to develop. The first phase focuses on establishing cadence and building trust. Later phases are where strategic value becomes measurable and visible.

Key Metrics

• Business Partner Satisfaction Score: an annual survey measuring responsiveness, communication, and perceived value. Target: establish a baseline within three months and improve by 10 or more points by the end of Year 1.
• Engagement coverage: the percentage of assigned relationships with an active, documented meeting cadence. Target: 100 percent within six months.
• Demand visibility: the number of project ideas and technology needs surfaced through BRMO into OIRT planning. Establish a baseline within three months and track the trend.
• Open item resolution rate: the percentage of commitments made to business partners that are resolved or formally communicated on within 30 days.
• Escalation frequency: tracked as a health signal. Sustained high escalation volume suggests a relationship or process problem that needs attention.

Maturity Milestones

• 0 to 6 months: all relationships assigned, meeting cadences established, and an initial relationship health baseline captured.
• 6 to 12 months: first satisfaction survey completed, open item tracking in place, and an initial pipeline of University-sourced project ideas visible in OIRT planning.
• 12 to 24 months: BRMO is embedded in IT leadership routines, and business partners consistently report feeling informed, heard, and well served.
• 24 months and beyond: BRMO is recognized as a valued institutional function, and OIRT is consistently perceived as a strategic partner in advancing FDU’s mission.

8. GOVERNANCE AND ACCOUNTABILITY

Ownership

The BRMO function is owned by the CIO. Day-to-day operation is the responsibility of each BRMO Practitioner within assigned relationships. The CIO or a designated BRMO lead is responsible for maintaining the relationship assignment map, facilitating periodic Practitioner sync meetings, reviewing satisfaction data, and ensuring the framework is applied consistently across the OIRT team.

Charter Review Cycle

This charter will be reviewed annually. The CIO’s office will assess whether the framework is operating as intended, whether structural changes are needed, and whether metric targets should be adjusted. Business Partners will be invited to contribute to the review. Material changes to the charter require approval from the CIO and acknowledgment from IT leadership.

---

Welcome to our comprehensive guide on utilizing the FDU Jamf Connect for login and NETID credential synchronization on macOS. This article is tailored for the staff, faculty, and students at FDU, providing a detailed walkthrough of the Jamf Connect login interface.

The Jamf Connect login screen consists of three sections: The login fields, the function buttons, and language and Wi-Fi.

The login fields are used to enter the NetID and password while the login button initiates the login. The username can be entered in any form that is recognized by Okta.

• Shut down: Powers the machine off
• Restart: Reboot the machine
• Help: Opens a mini browser to the FDU IT site

• Language Selection: Changes language
• Wi-Fi: Allows selection of wireless network

1. Enter your “FDU NetID” and “Password” and click the “Login” button

• You will see the message “Creating your account on this Mac” while the account is being created on the Mac

• If you are using a non-standard account name that does not match your FDU NetID, you will be able to select this account at login and link it to your NetID

2. Locate the account and click “Connect” to link it to your NetID. If you do not wish to link the existing, account click “Create Account” to proceed with a new account

3. You will be prompted to enter the “existing password” for the local account. Click “Connect” to complete the link.

The Jamf Connect app is used to synchronize domain credentials with the local machine credentials.

1. Enter your “FDU NETID” and “Password” and click the “Sign In” button

2. If your NETID password is out-of-sync, you will be prompted to sync them by entering the Local Password you use to sign into the machine. Click “Sync” to sync the new NETID password

I. OBJECTIVE

Create a standard procedure by which Manager’s and their employee’s transfer University data during the period of time from when an employee makes their intention clear that they are separating from the University or the transfer of University data at the time of an employee’s involuntary separation from the University.

II. PRODUCURES

Voluntary Separation

It is the manager or direct supervisor’s responsibility to work with the separating employee to extract any data or files that reside locally on their computer that would be needed for business continuity. The supervisor should also ensure they understand what shared drives the separated employee used and have access to those drives if need be.

Using appropriate security precautions, the manager should meet several times with the separating employee to ensure all information is transferred over either email, a shared drive, One Drive or a thumb drive.

During the separation process, through the Employee Separation Checklist, the employee’s manager can select the ability to access the separating employee’s email for up to 30 days and/or forward emails addressed to the separated employee for up to 60 days.

Upon receiving the separation notice, Computing Services will validate through our Backup system that the separating employee’s complete laptop or desktop Image has been backed up.

Computing Services will manually trigger an additional backup within three days of separation.

Immediately upon the effective date of the separation, the separating employee’s manager is responsible for turning over the separating employees’ computer to Computing Services.

Computing Services will store the computer for 14 days as a precaution, and then wipe the data from that computer, reimage the computer, and shelf the computer for redistribution.

If it is discovered that information that resided on the separated employee’s computer was missed during the separation process and needs to be retrieved at a later point, the supervisor would need to contact the Vice President of Human Resources and request the specific data that would need to be recovered from our Backup system.

Involuntary Separation

Upon the dismissal of the individual, Human Resources, would immediately engage Computing Services as well as the direct supervisor to view and extract any data that might be needed by the department to ensure business continuity. This would take place as soon as possible from the date of dismissal.

If a legal hold is required, Computing Services and USAN would be notified and the existing processes of extracting and encrypting the hard drive as well as protecting all email correspondence would be executed. Computing Services would then remove the computer.

If a legal hold is not required, Computing Services will validate through our Backup system that the dismissed employee’s Image has been properly backed up and remove the computer.

Computing Services will store the computer for 14 days as a precaution, and then wipe the data from that computer, reimage the computer, and shelf the computer for redistribution.

If it is discovered that information that resided on the separated employee’s computer was missed during the separation process and needs to be retrieved at a later point, the supervisor would need to contact the Vice President of Human Resources and request the specific data that would need to be recovered from our Backup system.

III. IN CASE OF QUESTIONS

Questions regarding this procedure can be directed to the Vice President of Human Resources.

---

The FDU (Fairleigh Dickinson University) Self-Service Portal for Software is a a tool designed to enhance our community’s access to software and desktop related information. With the Self-Service Portal for Software, our Faculty and Staff can easily locate and install pre-loaded software onto FDU owned computers. Simply launch the portal and you will be presented with a variety of applications, each sanctioned and supplied by FDU. This portal will provide an easily searchable way to view all new applications made available to the user community, including Microsoft Teams, Cisco Jabber, the FDU VPN, and many more.

FDU Self Service Portal Icon

How to Use and Access the FDU Self Service Portal for Software

1. Locate the FDU Self-Service Portal for Software icon on the desktop and double-click it to launch the application or…
   1. Select the ‘Windows’ logo/start button on the bottom left of the desktop
   2. Type ‘FDU Self Service Portal for Software’ into the search bar
   3. Left click ‘FDU Self Service Portal for Software’ app to launch

2. To install a program, click on the name of the application, then click on the “Install” button to the right

3. A progress window will provide updates as the program is installed on your system. When complete, the Status column should indicate “Complete”

4. After the selected application finished downloading, it will automatically install and when completed, the status will show as “Completed”

1. Open the ‘Applications’ folder and locate and click the ‘FDU Self Service Portal’ icon or…

• Select the ‘Launchpad’ icon from the dock

Launchpad Icon

• Type ‘FDU Self Service Portal‘
• Click the ‘FDU Self Service Portal’ icon to launch

1. Find the ‘Self Service Portal’ app icon and tap to launch

FDU Self Service Portal App on iOS

2. Click ‘Install’ to install the requested item onto your device

Once the FDU Self-Service Portal application is open, you may then continue to select and install your desired software application. You may also access and use any self-service troubleshooting solutions that are available to you from within the FDU Self-Service Portal as well.

FDU’s Single Sign-On (SSO) experience has been improved and OKTA is the primary Single Sign-On provider. OKTA will replace our “Legacy” SSO login page for all applications over time.

OKTA SSO Login Page

New and existing FDU NetID users who are logging into OKTA for the first time will need to finish setting up their multifactor authentication with DUO.

1. Enter your FDU NetID and click “Next“

2. Enter your FDU NetID Password and click “Sign In”

3. For existing users with DUO configured please skip to step 4. For new users please click “Setup” then “Enroll” to continue the process

For instructions on setting up DUO for the first time, refer to our “Quick Start Guide“

4. If you are an existing DUO user, a prompt will be shown to redirect you to verification with Duo MFA. Click “Verify” to continue

5. Duo will automatically send a DUO Push to your registered device. Accept the DUO Push on your device to continue the authentication process

6. If don’t want to use DUO Push to authenticate, select “Other Options” and choose your preferred method from the list

---

Legacy SSO Login Page

1. Enter your FDU NetID and Password and click “Sign In“

2. Authenticate using DUO using any of the authentication options shown