uniWIKI - User contributions [en]

Information Systems:Adobe Creative Cloud for Teams

2021-06-21T18:01:53Z

Aaront: /* Notes */

==Configuration==
uniPHARM has an Adobe Creative Cloud for Teams monthly subscription (4 users). The current usernames/passwords are:

{| class="wikitable sortable"
|-
! Username !! Password !! Activation 1 !! Activation 2 || Notes
|-
| adobecc@unipharm.com || !NewVisionIT2051 || - || - || Used for billing only
|-
| ccmediauser1@unipharm.com || NewVisionIT2051|| teresab1 || - || Adobe Creative Cloud License
|-
| ccmediauser2@unipharm.com || NewVisionIT2051|| donnak1|| - || Adobe Creative Cloud License
|-
| ccmediauser3@unipharm.com || NewVisionIT2051! || aaront || angelac1 || Adobe Acrobat Pro License only
|-
| ccmediauser4@unipharm.com || NewVisionIT2051 || || || No license.
|-
| ralphl@unipharm.com || same as windows login|| |||| Adobe Acrobat Pro License only
|-
| nancyn@unipharm.com || same as outlook login || |||| Adobe Acrobat Pro License only
|}

==Notes==
* During exchange deployment, ccmediauser* emails are now aliased to it@unipahrm.com
* June 2021, Adobe individual IDs created and assigned for Nancy and Ralph.
* 11:27, 25 May 2020 (PDT) Adobe Sign is an Acrobat module for e-signatures. Because Nancy and Ralph use this feature under ccmediauser4, this email address is now being forwarded to nancyn@unipharm.com. There are many alerts generated as part of the audit trail during the esignature document lifecycle.
* (Dec. 13, 2018) When signing in to the 3rd computer, Adobe CC now lets you sign another user out directly from said computer in order to free up a license/seat. It's a neat feature, and all but an official confirmation that
they understand people will use their licenses in revolving manner.
* On November 26, 2018 Darren created a new Adobe account because we changed from a monthly-credit-card-paying subscription to a yearly-purchase-order subscription. The new yearly purchase reduced the number of Creative Cloud licenses from 4 to 2 and added a quantity of 1 for Acrobat Pro.

[[Category: Desktop Software]]
[[Category: Adobe]]

Information Systems:Adobe Creative Cloud for Teams

2021-06-21T17:58:08Z

Aaront: /* Configuration */

==Configuration==
uniPHARM has an Adobe Creative Cloud for Teams monthly subscription (4 users). The current usernames/passwords are:

{| class="wikitable sortable"
|-
! Username !! Password !! Activation 1 !! Activation 2 || Notes
|-
| adobecc@unipharm.com || !NewVisionIT2051 || - || - || Used for billing only
|-
| ccmediauser1@unipharm.com || NewVisionIT2051|| teresab1 || - || Adobe Creative Cloud License
|-
| ccmediauser2@unipharm.com || NewVisionIT2051|| donnak1|| - || Adobe Creative Cloud License
|-
| ccmediauser3@unipharm.com || NewVisionIT2051! || aaront || angelac1 || Adobe Acrobat Pro License only
|-
| ccmediauser4@unipharm.com || NewVisionIT2051 || || || No license.
|-
| ralphl@unipharm.com || same as windows login|| |||| Adobe Acrobat Pro License only
|-
| nancyn@unipharm.com || same as outlook login || |||| Adobe Acrobat Pro License only
|}

==Notes==
* June 2021, Adobe individual IDs created and assigned for Nancy and Ralph.
* 11:27, 25 May 2020 (PDT) Adobe Sign is an Acrobat module for e-signatures. Because Nancy and Ralph use this feature under ccmediauser4, this email address is now being forwarded to nancyn@unipharm.com. There are many alerts generated as part of the audit trail during the esignature document lifecycle.
* (Dec. 13, 2018) When signing in to the 3rd computer, Adobe CC now lets you sign another user out directly from said computer in order to free up a license/seat. It's a neat feature, and all but an official confirmation that
they understand people will use their licenses in revolving manner.
* On November 26, 2018 Darren created a new Adobe account because we changed from a monthly-credit-card-paying subscription to a yearly-purchase-order subscription. The new yearly purchase reduced the number of Creative Cloud licenses from 4 to 2 and added a quantity of 1 for Acrobat Pro.

[[Category: Desktop Software]]
[[Category: Adobe]]

Information Systems:Adobe Creative Cloud for Teams

2021-06-21T17:51:45Z

Aaront: /* Notes */

==Configuration==
uniPHARM has an Adobe Creative Cloud for Teams monthly subscription (4 users). The current usernames/passwords are:

{| class="wikitable sortable"
|-
! Username !! Password !! Activation 1 !! Activation 2 || Notes
|-
| adobecc@unipharm.com || !NewVisionIT2051 || - || - || Used for billing only
|-
| ccmediauser1@unipharm.com || NewVisionIT2051|| teresab1 || - || Adobe Creative Cloud License
|-
| ccmediauser2@unipharm.com || NewVisionIT2051|| donnak1|| - || Adobe Creative Cloud License
|-
| ccmediauser3@unipharm.com || NewVisionIT2051! || aaront || angelac1 || Adobe Acrobat Pro License only
|-
| ccmediauser4@unipharm.com || NewVisionIT2051 || || || Adobe Acrobat Pro Licence only. Used for Adobe Sign.
|-
| ralphl@unipharm.com || same as windows login|| |||| Adobe Acrobat Pro License only
|-
| nancyn@unipharm.com || same as outlook login || |||| Adobe Acrobat Pro License only
|}

==Notes==
* June 2021, Adobe individual IDs created and assigned for Nancy and Ralph.
* 11:27, 25 May 2020 (PDT) Adobe Sign is an Acrobat module for e-signatures. Because Nancy and Ralph use this feature under ccmediauser4, this email address is now being forwarded to nancyn@unipharm.com. There are many alerts generated as part of the audit trail during the esignature document lifecycle.
* (Dec. 13, 2018) When signing in to the 3rd computer, Adobe CC now lets you sign another user out directly from said computer in order to free up a license/seat. It's a neat feature, and all but an official confirmation that
they understand people will use their licenses in revolving manner.
* On November 26, 2018 Darren created a new Adobe account because we changed from a monthly-credit-card-paying subscription to a yearly-purchase-order subscription. The new yearly purchase reduced the number of Creative Cloud licenses from 4 to 2 and added a quantity of 1 for Acrobat Pro.

[[Category: Desktop Software]]
[[Category: Adobe]]

Information Systems:Microsoft 365 Billing

2021-06-15T23:25:57Z

Aaront: Created page with "In order to add another mailbox or active user to our Microsoft 365, we need to purchase an additional license from the cdw site. csp.cdw.ca, each member of the IT staff has..."

In order to add another mailbox or active user to our Microsoft 365, we need to purchase an additional license from the cdw site.
csp.cdw.ca, each member of the IT staff has their own login and should be able to add or remove licenses from here. It should be noted that the vendor did say that reducing the number of licenses is more involved if we pay per year.

From there the licenses should become available in our M365admin center to be assigned.

Information Systems:Adobe Creative Cloud for Teams

2021-06-15T19:27:29Z

Aaront:

==Configuration==
uniPHARM has an Adobe Creative Cloud for Teams monthly subscription (4 users). The current usernames/passwords are:

{| class="wikitable sortable"
|-
! Username !! Password !! Activation 1 !! Activation 2 || Notes
|-
| adobecc@unipharm.com || !NewVisionIT2051 || - || - || Used for billing only
|-
| ccmediauser1@unipharm.com || NewVisionIT2051|| teresab1 || - || Adobe Creative Cloud License
|-
| ccmediauser2@unipharm.com || NewVisionIT2051|| donnak1|| - || Adobe Creative Cloud License
|-
| ccmediauser3@unipharm.com || NewVisionIT2051! || aaront || angelac1 || Adobe Acrobat Pro License only
|-
| ccmediauser4@unipharm.com || NewVisionIT2051 || || || Adobe Acrobat Pro Licence only. Used for Adobe Sign.
|-
| ralphl@unipharm.com || same as windows login|| |||| Adobe Acrobat Pro License only
|-
| nancyn@unipharm.com || same as outlook login || |||| Adobe Acrobat Pro License only
|}

==Notes==
* 11:27, 25 May 2020 (PDT) Adobe Sign is an Acrobat module for e-signatures. Because Nancy and Ralph use this feature under ccmediauser4, this email address is now being forwarded to nancyn@unipharm.com. There are many alerts generated as part of the audit trail during the esignature document lifecycle.
* (Dec. 13, 2018) When signing in to the 3rd computer, Adobe CC now lets you sign another user out directly from said computer in order to free up a license/seat. It's a neat feature, and all but an official confirmation that
they understand people will use their licenses in revolving manner.
* On November 26, 2018 Darren created a new Adobe account because we changed from a monthly-credit-card-paying subscription to a yearly-purchase-order subscription. The new yearly purchase reduced the number of Creative Cloud licenses from 4 to 2 and added a quantity of 1 for Acrobat Pro.

[[Category: Desktop Software]]
[[Category: Adobe]]

Information Systems:Staff Onboarding How-To

2021-06-15T16:52:14Z

Aaront: /* Extra things to check */

==Overview==
This page outlines the process for setting up a new Unipharm employee / staff member.

Main areas where user profiles have to be defined or linked to AD/green-screen profiles:
* Active Directory domain user
* IBM i user profile (green-screen/Mocha access)
* ASW profile for IBM i user
* UNITY user profile
* MS365 Mailbox
* Moodle user (linked to AD user)
* Unipharm wiki user (linked to AD user)
* WiNG wireless (staff WiFi)
* Kofax scanning profile, if applicable (linked to AD user)
* DocView permissions (IBM i user profile)
* Xerox scanning profile, if applicable

==Instructions==
* Create AD user, verify group membership if copying another user, or set manually.
* Use Navigator or green screen to create IBM i user profile. Also copy existing user for convenience.
* Go into UNITY (green-screen), System Administration -> OMM Menus -> Work with User Security (if prompted for password, just press Enter back out and wait for a few moments then go back in to find the person on the list).
* Position to or search for existing user to be used a template, use 8 beside the entry to copy user into a new UNITY user matching green-screen username.
* Configure MA (menu authority) for new user by entering MA beside their name. F10 to copy from existing user. Leave Menu name blank and just enter the source and target user profiles to copy all menu authorities.
* Configure FA (functional authority) using FA beside the name. To copy from existing user, type 'USR' in '''Type''', and the source user profile in '''Qualifier'''. Press Enter, and you should see a comparison of the source and target functional authorities. Use F19 (shift F7) to grant missing.
* Configure ASW user profile [[Information Systems: ASW User Security|using these instructions]]

==Extra things to check==
Depending on the role of the new employee, the following may also need to be checked and configured in advance:

* Mapped drives
* Permissions to send to Notes distribution lists
* SRFax
*Build RF, Build RET
*http://owl.unipharm.local/mediawiki/index.php/Information_Systems:Extension_User_Security
* If there is uncertainty on whether the account has what it needs ( specifically for RF admins, there is no harm in showing the profile to a supervisory to ensure the best experience for the new staff)
* [[Information Systems:ASW favorites (menu items)|ASW favorites (menu items)]]

[[Category: Staff On-boarding]]

Information Systems:Staff Onboarding How-To

2021-06-15T16:25:19Z

Aaront:

==Overview==
This page outlines the process for setting up a new Unipharm employee / staff member.

Main areas where user profiles have to be defined or linked to AD/green-screen profiles:
* Active Directory domain user
* IBM i user profile (green-screen/Mocha access)
* ASW profile for IBM i user
* UNITY user profile
* MS365 Mailbox
* Moodle user (linked to AD user)
* Unipharm wiki user (linked to AD user)
* WiNG wireless (staff WiFi)
* Kofax scanning profile, if applicable (linked to AD user)
* DocView permissions (IBM i user profile)
* Xerox scanning profile, if applicable

==Instructions==
* Create AD user, verify group membership if copying another user, or set manually.
* Use Navigator or green screen to create IBM i user profile. Also copy existing user for convenience.
* Go into UNITY (green-screen), System Administration -> OMM Menus -> Work with User Security (if prompted for password, just press Enter back out and wait for a few moments then go back in to find the person on the list).
* Position to or search for existing user to be used a template, use 8 beside the entry to copy user into a new UNITY user matching green-screen username.
* Configure MA (menu authority) for new user by entering MA beside their name. F10 to copy from existing user. Leave Menu name blank and just enter the source and target user profiles to copy all menu authorities.
* Configure FA (functional authority) using FA beside the name. To copy from existing user, type 'USR' in '''Type''', and the source user profile in '''Qualifier'''. Press Enter, and you should see a comparison of the source and target functional authorities. Use F19 (shift F7) to grant missing.
* Configure ASW user profile [[Information Systems: ASW User Security|using these instructions]]

==Extra things to check==
Depending on the role of the new employee, the following may also need to be checked and configured in advance:

* Mapped drives
* Permissions to send to Notes distribution lists
* SRFax
*Build RF, Build RET
*http://owl.unipharm.local/mediawiki/index.php/Information_Systems:Extension_User_Security
* [[Information Systems:ASW favorites (menu items)|ASW favorites (menu items)]]

[[Category: Staff On-boarding]]

Information Systems:Staff Onboarding How-To

2021-06-14T22:45:09Z

Aaront: /* Extra things to check */

==Overview==
This page outlines the process for setting up a new Unipharm employee / staff member.

Main areas where user profiles have to be defined or linked to AD/green-screen profiles:
* Active Directory domain user
* IBM i user profile (green-screen/Mocha access)
* ASW profile for IBM i user
* UNITY user profile
* MS365 Mailbox
* Moodle user (linked to AD user)
* Unipharm wiki user (linked to AD user)
* WiNG wireless (staff WiFi)
* Kofax scanning profile, if applicable (linked to AD user)
* DocView permissions (IBM i user profile)
* Xerox scanning profile, if applicable

==Instructions==
* Create AD user, verify group membership if copying another user, or set manually.
* Use Navigator or green screen to create IBM i user profile. Also copy existing user for convenience.
* Go into UNITY (green-screen), System Administration -> OMM Menus -> Work with User Security (if prompted for password, just press Enter).
* Position to or search for existing user to be used a template, use 8 beside the entry to copy user into a new UNITY user matching green-screen username.
* Configure MA (menu authority) for new user by entering MA beside their name. F10 to copy from existing user. Leave Menu name blank and just enter the source and target user profiles to copy all menu authorities.
* Configure FA (functional authority) using FA beside the name. To copy from existing user, type 'USR' in '''Type''', and the source user profile in '''Qualifier'''. Press Enter, and you should see a comparison of the source and target functional authorities. Use F19 (shift F7) to grant missing.
* Configure ASW user profile [[Information Systems: ASW User Security|using these instructions]]

==Extra things to check==
Depending on the role of the new employee, the following may also need to be checked and configured in advance:

* Mapped drives
* Permissions to send to Notes distribution lists
* SRFax
*Build RF, Build RET
*http://owl.unipharm.local/mediawiki/index.php/Information_Systems:Extension_User_Security
* [[Information Systems:ASW favorites (menu items)|ASW favorites (menu items)]]

[[Category: Staff On-boarding]]

Information Systems:VoIP Phone Configuration

2021-06-11T16:38:53Z

Aaront: /* 3CX Windows client */

==Overview==
This article discusses the user-facing side of the phone system including deskphones, cordless phones, and headsets.

==Administration==
===Initial Setup===
====Deskphone Setup (Yealink)====
* The first step when configuring a new phone desk phone is to unbox and label the phone to its extension.
* The second step is to determine what port it will be plugged into , meaning which port on which switch it plugs into.
* Tag The port switch port
* Plug the phone into the local port
* Log into 3cx
* Under the phones tab find the new phone by extension
* Hit assign extension
* Use Lan at the office
* Use Interface 192.168.44.2
* Log into the phone interface and set the phone with a static IP? (maybe)

====Cordless (DECT) Base and Phone Setup====
web link to general setup https://www.3cx.com/sip-phones/manually-provision-yealink-dect/

* unbox the base and handset
* plug the base into switch
* navigate to the 3cx management page
* under the advanced tab select FXS/DECT
* add the base using the mac address to the list of bases already present.
* use the interface 192.168.44.2
* copy the provisioning link provided here in the general tab
* define the extensions in the extensions tab
* navigate to the ip address of the wireless base
* navigate to settings and auto configuration , use the provisioning link copied before in the space for server URL
* confirm, auto provision now.
* to add a phone to a base, press and hold the wifi button on the base until the top light starts to flash, then on the handset select register and they will find each other.
*username is admin, and the password for the base is found on the FS/Dect page for the base.
*The handsets are managed by the base on the accounts page. In a case where you are just replacing a non functioning unit, use the settings( Register name/username/password) from the unit you are going to replace. Disable the account of the non functioning unit and enable the new handset on a new account.

====DECT Repeater Setup====
*Setting up a repeater requires a dect base, handset that is paired to that base and the repeater itself.
*from a paired handset navigate to settings and put it into repeater mode, choosing the type of repeater.
*the base will automatically reset when the paired handset is put into repeater mode, wait for the base to come online
*connect the repeater to power
*hold down the pairing button on the base until the phone light starts to flash
*press the pairing button on the repeater.
* the dect light should go from red to orange when it finds the base.

''There is one repeater in the recieving mezzannine, and one in large down''

====3CX Windows client====
The 3cx windows client is installed by the I.T staff, configuration requires the config file from the welcome email. Dragging and dropping is all that should be needed to configure the client.

The client is user profile based, meaning if another staff logs into their profile on a workstation that has the client configured on another profile it will not load their configuration.

====3CX App (iOS/Android)====

These apps are available to download from their respective stores. A QR code is sent to a user when their client is configured and they may use that to search the app and load their profile.

Once connected it is important to remind the user that it will use cellular data if wifi is not available.

===Firmware updates===
The Yealink deskphones and DECT bases require firmware updates. The firmware for the deskphones can and should only be updated through 3CX. This is because there is specific, 3CX-certified firmware which is different (and often lags behind) what Yealink generally releases. The firmware is auto-downloaded into the 3CX system as a part of its auto-updater. Once newer firmware is auto-downloaded into the repository, the system displays a warning for applicable phones that are now out of date. The firmware can be pushed from the 3CX console. This will reboot the phone and reset any user customizations that are not managed through 3CX. For example, the ringtone is manageable through 3CX, but the ''Display Clock'' within ''Screensaver'', is not.

==Supported deployment configurations==
This section discusses the different configurations that are in use currently. Originally there were only 2 standard configurations (office and warehouse employees), but the situation evolved rapidly due to COVID/WFH. In particular, the softphones, web client and mobile app have become part of standard usage, in some cases replacing the use of deskphones entirely e.g. Customer Service.

====General (in-office)====
:'''''Setup 1 (office):''''' Yealink deskphone, EPOS wireless headset via USB (connected to deskphone)
:'''''Setup 2 (warehouse):''''' Yealink cordless DECT phone
:'''''Setup 3 (certain staff):''''' 3CX Web Client, EPOS wireless headset via USB (connected to computer)
:'''''Optional components:''''' 3CX Web Client, 3CX App (mobile)

Setup 1 was the original setup for all office users, and involves a Yealink deskphone (T54W) and, for staff using a headset, an EPOS SD-Pro Or D10 DECT headset connected to the phone via USB.

Some staff who have been exposed to either the web client or mobile app (due to WFH or other means) continue to use these in-office for the additional features. For example, some warehouse supervisors use the mobile app instead of the cordless phone.

====WFH (except Customer Service)====
:'''''Setup:''''' 3CX Web Client and 3CX App (mobile)
:'''''Additional components: ''''' 3CX Browser Extension for Chrome or Edge (Chromium-based)

When working from home, the web client is the recommended deployment for office staff that are not in Customer Service. Theoretically, the web client is more performant through the WAN compared to the softphone as it uses WebRTC rather than SIP/RTP (I think...). Being browser-accessible, the web client is also simpler to deploy and maintain than the Windows client.

====Customer Service====
:'''''Setup 1: ''''' 3CX for Windows softphone, EPOS Connect, 3CX Plugin for EPOS
:'''''Setup 2 (WFH): ''''' 3CX for Windows softphone (through RDP), Poly/Plantronics C3220 USB headset (USB pass-through), Plantronics Hub Software (supports 3CX integration)
:'''''Additional components: ''''' Kuando BusyLight

The '''3CX for Windows''' softphone (a.k.a. desktop client) has become the preferred deployment for Customer Service agents, along with the headset connected directly to the computer. This is true whether in-office or WFH. Call control and other features are enabled through the EPOS Connect softaware and the 3CX Plugin for EPOS. While the headset could theoretically work in plug-and-play mode, both of these need to be installed for a smooth experience.

This software communicates to the server via the main LAN, which is different from the deskphones that [[Information_Systems:VoIP_LAN_configuration |communicate on the VoIP VLAN]].

For historical reference, the original deployment for CS agents involved a deskphone (including a sidecar attachment for the receptionist), and a wireless headset connected to the deskphone via USB. The deskphone introduced another vendor into the equation - Yealink, which in turn presented limitations due to only a subset of features on the deskphone being interoperable with 3CX. For example, the deskphone neither displays call queue information nor Away status for other users.

TBC -[[User:Norwinu|norwizzle]] ([[User talk:Norwinu|talk]])

[[Category: Phone System]]

Information Systems:VoIP Phone Configuration

2021-06-11T16:35:04Z

Aaront: /* 3CX App (iOS/Android) */

==Overview==
This article discusses the user-facing side of the phone system including deskphones, cordless phones, and headsets.

==Administration==
===Initial Setup===
====Deskphone Setup (Yealink)====
* The first step when configuring a new phone desk phone is to unbox and label the phone to its extension.
* The second step is to determine what port it will be plugged into , meaning which port on which switch it plugs into.
* Tag The port switch port
* Plug the phone into the local port
* Log into 3cx
* Under the phones tab find the new phone by extension
* Hit assign extension
* Use Lan at the office
* Use Interface 192.168.44.2
* Log into the phone interface and set the phone with a static IP? (maybe)

====Cordless (DECT) Base and Phone Setup====
web link to general setup https://www.3cx.com/sip-phones/manually-provision-yealink-dect/

* unbox the base and handset
* plug the base into switch
* navigate to the 3cx management page
* under the advanced tab select FXS/DECT
* add the base using the mac address to the list of bases already present.
* use the interface 192.168.44.2
* copy the provisioning link provided here in the general tab
* define the extensions in the extensions tab
* navigate to the ip address of the wireless base
* navigate to settings and auto configuration , use the provisioning link copied before in the space for server URL
* confirm, auto provision now.
* to add a phone to a base, press and hold the wifi button on the base until the top light starts to flash, then on the handset select register and they will find each other.
*username is admin, and the password for the base is found on the FS/Dect page for the base.
*The handsets are managed by the base on the accounts page. In a case where you are just replacing a non functioning unit, use the settings( Register name/username/password) from the unit you are going to replace. Disable the account of the non functioning unit and enable the new handset on a new account.

====DECT Repeater Setup====
*Setting up a repeater requires a dect base, handset that is paired to that base and the repeater itself.
*from a paired handset navigate to settings and put it into repeater mode, choosing the type of repeater.
*the base will automatically reset when the paired handset is put into repeater mode, wait for the base to come online
*connect the repeater to power
*hold down the pairing button on the base until the phone light starts to flash
*press the pairing button on the repeater.
* the dect light should go from red to orange when it finds the base.

''There is one repeater in the recieving mezzannine, and one in large down''

====3CX Windows client====
====3CX App (iOS/Android)====

These apps are available to download from their respective stores. A QR code is sent to a user when their client is configured and they may use that to search the app and load their profile.

Once connected it is important to remind the user that it will use cellular data if wifi is not available.

===Firmware updates===
The Yealink deskphones and DECT bases require firmware updates. The firmware for the deskphones can and should only be updated through 3CX. This is because there is specific, 3CX-certified firmware which is different (and often lags behind) what Yealink generally releases. The firmware is auto-downloaded into the 3CX system as a part of its auto-updater. Once newer firmware is auto-downloaded into the repository, the system displays a warning for applicable phones that are now out of date. The firmware can be pushed from the 3CX console. This will reboot the phone and reset any user customizations that are not managed through 3CX. For example, the ringtone is manageable through 3CX, but the ''Display Clock'' within ''Screensaver'', is not.

==Supported deployment configurations==
This section discusses the different configurations that are in use currently. Originally there were only 2 standard configurations (office and warehouse employees), but the situation evolved rapidly due to COVID/WFH. In particular, the softphones, web client and mobile app have become part of standard usage, in some cases replacing the use of deskphones entirely e.g. Customer Service.

====General (in-office)====
:'''''Setup 1 (office):''''' Yealink deskphone, EPOS wireless headset via USB (connected to deskphone)
:'''''Setup 2 (warehouse):''''' Yealink cordless DECT phone
:'''''Setup 3 (certain staff):''''' 3CX Web Client, EPOS wireless headset via USB (connected to computer)
:'''''Optional components:''''' 3CX Web Client, 3CX App (mobile)

Setup 1 was the original setup for all office users, and involves a Yealink deskphone (T54W) and, for staff using a headset, an EPOS SD-Pro Or D10 DECT headset connected to the phone via USB.

Some staff who have been exposed to either the web client or mobile app (due to WFH or other means) continue to use these in-office for the additional features. For example, some warehouse supervisors use the mobile app instead of the cordless phone.

====WFH (except Customer Service)====
:'''''Setup:''''' 3CX Web Client and 3CX App (mobile)
:'''''Additional components: ''''' 3CX Browser Extension for Chrome or Edge (Chromium-based)

When working from home, the web client is the recommended deployment for office staff that are not in Customer Service. Theoretically, the web client is more performant through the WAN compared to the softphone as it uses WebRTC rather than SIP/RTP (I think...). Being browser-accessible, the web client is also simpler to deploy and maintain than the Windows client.

====Customer Service====
:'''''Setup 1: ''''' 3CX for Windows softphone, EPOS Connect, 3CX Plugin for EPOS
:'''''Setup 2 (WFH): ''''' 3CX for Windows softphone (through RDP), Poly/Plantronics C3220 USB headset (USB pass-through), Plantronics Hub Software (supports 3CX integration)
:'''''Additional components: ''''' Kuando BusyLight

The '''3CX for Windows''' softphone (a.k.a. desktop client) has become the preferred deployment for Customer Service agents, along with the headset connected directly to the computer. This is true whether in-office or WFH. Call control and other features are enabled through the EPOS Connect softaware and the 3CX Plugin for EPOS. While the headset could theoretically work in plug-and-play mode, both of these need to be installed for a smooth experience.

This software communicates to the server via the main LAN, which is different from the deskphones that [[Information_Systems:VoIP_LAN_configuration |communicate on the VoIP VLAN]].

For historical reference, the original deployment for CS agents involved a deskphone (including a sidecar attachment for the receptionist), and a wireless headset connected to the deskphone via USB. The deskphone introduced another vendor into the equation - Yealink, which in turn presented limitations due to only a subset of features on the deskphone being interoperable with 3CX. For example, the deskphone neither displays call queue information nor Away status for other users.

TBC -[[User:Norwinu|norwizzle]] ([[User talk:Norwinu|talk]])

[[Category: Phone System]]

Information Systems:Symantec Endpoint Protection

2021-06-10T21:35:32Z

Aaront:

SEPM – Symantec Endpoint Protection Manager

Symantec Endpoint Protection is the anti-virus and anti-malware application that is used at UWD. SEP provides a barrier for malware on all desktops, laptops and Windows based servers. The application needs to have its license renewed every February and the cost of the license is determined by the number of seats needed. As of November of 2013, the number of seats needed is 70. The actual number of used seats is about 65 but there needs to be some extra for spare or temporary computers.
The client application is controlled by SEP Manager which is installed on the Smithers server. SEPM is responsible for controlling the configuration, maintenance and deployment of the SEP clients. SEPM also is responsible for downloading the anti-virus and anti-malware definitions and then distributing them to the SEP clients.

The specific configuration of SEP is extremely important and absolutely critical to the software working correctly. The default factory configuration of the SEP client is too restrictive and will prevent UWD staff from being productive. The SEP client consists of modules that have different functions. The only modules that are needed by UWD are the anti-virus and anti-malware modules. Other modules such as the Symantec firewall are not needed because they conflict with the built in firewall that is included in Windows.
The configuration of the SEP clients is also not change-able by restricted Windows users. The settings for turning off and on the SEP client and how it behaves is locked out to the SEPM program only. The reason for this is to prevent a virus from having the ability to disable the SEP client.

The SEP clients are configured to query SEPM for new definitions once per hour each day. If new definitions are available they are distributed from SEPM which downloads them directly from Symantec. Having only SEPM query Symantec for definitions saves on network bandwidth.

The SEP clients are configured to do a complete anti-virus scan of all files on the local hard drive each day at 5AM. It is set to occur at that time because the scan is processor intensive and would be disruptive to users if it was set to run during the work day. In the case of laptops that are usually not powered on at 5AM, the scan occurs when the machine is on and at idle and the scan runs at a low intensity for a longer period.

When a virus or malware touches the local file system or the memory of desktop/laptop/server, the SEP client will try to halt that process and present a pop up window to the user telling them to stop what they are doing and contact the IT department. The SEP client is configured to first try to delete the virus but if it can’t do that, it will try to quarantine it. If possible the SEP client will communicate to SEPM about the infection. SEPM will then notify IT by email that an infection occurred and on what machine.
It is up to the IT administrator to determine if the infection is first real or a false positive, and then how to properly clean out the virus if SEP hasn’t already done it. The only way to be 100% positive that a virus is gone is to re-image the computer. This erases the entire hard drive and restores the user profile from the Superserver. Re-imaging is not always convenient but for some cases it is the quickest method to restore from a real virus infection. The safety of the corporate network is paramount and sometimes it is just the best method to wipe the machine and restore the OS image.

SEPM is capable of producing some useful reports on which computers have the latest definitions and the rates and types of infections. SEPM is also the recommended starting point to deploy the SEP client to desktops/laptops/servers. The configuration settings in SEPM are integrated into a client package and then sent over the network to install remotely on the computer. SEPM then instructs the client to reboot if needed. Doing deployments in this method makes sure that the client gets the right settings and the latest definitions in one step. Upgraded versions of the SEP client can also be deployed this way and do not require IT staff to walk around to each work station.

SEPM can be access from the Smithers desktop directly or from the web administration page at
https://smithers.unipharm.local:8443/console/apps/sepm

Technical support is part of the license with first level being off shore based and second level located in Oregon. The phone number for technical support is 1-800-721-3934 and is available 24/7. The support technician will need a license number and that can be found on the license certificate document that is emailed to IT when the license is renewed each year.

==CHANGELOG==
*As of Feb-05-2020 mysymentec is the way to reach out to them , https://support.symantec.com/us/en.html is the url and the username password have been added to the password list.
*As of march-01-20 Broadcom has taken ownership of support , the above link and credentials have been migrated tot he broadcom site by aaront
*AS OF MAY2021
*SYMANTEC ENDPOINT MANAGER VERSION IS 14
*CLIENT VERSIONS FOR WORKSTATIONS IS 14
*CLIENT VERSIONS FOR SERVERS IS 12
*Client packages located on SUPERSERVER|UWDSOFTWARE|SYMANTEC
*SYMANTEC DIAGNOSTIC TOOL located on SUPERSERVER|UWDSOFTWARE|SYMANTEC

[[Category: Servers - Software]]

Information Systems:Windows Admin Centre WAC

2021-06-10T18:33:56Z

Aaront:

WAC is a free program that helps centrally manage windows devices, it is very useful in our non enterprise environment.

How it is deployed and configured will be added here, in its current state it is able to connect to the windows workstations that have the GPO to enable the WS-Management service running called enable WinRM.

It is not yet configured to administer the servers but should be done.

Information Systems:Windows Admin Centre WAC

2021-06-10T18:33:08Z

Aaront: Created page with "WAC is a free program that helps centrally manage windows devices, it is very useful in our non enterprise environment. How it is deployed and configured will be added here,..."

WAC is a free program that helps centrally manage windows devices, it is very useful in our non enterprise environment.

How it is deployed and configured will be added here, in its current state it is able to connect to the windows workstations that have the GPO to enable the WS-Management service running on the destination, WinRM.

It is not yet configured to administer the servers but should be done.

Information Systems:WSUS

2021-05-31T21:37:37Z

Aaront:

WSUS – Windows Software Update Service

The WSUS application is provided to IT administrators for free from Microsoft. The application is installed on the Smithers server, on top of its Windows Server 2012R2 operating system. The purpose of the WSUS application is to provide a managed local version of the Windows Updates website that consumers use to get patches from Microsoft. WSUS presents all of the patches that have been created by Microsoft for all of its products going back at least 14 years. Since it is not practical to download everything for all products, WSUS allows an IT administrator to choose not only which products get patches, but also which patches get applied to client machines.
The client machines ( in the context of WSUS )include all desktops and laptops plus all the Windows based servers. The client machines are configured to query the WSUS application based on settings applied from GPO objects in Active Directory. Machines not connected to AD don’t use WSUS.

The GPO settings instruct the client machines to query the WSUS application every 4 hours for any new patches. If there are patches, then they are downloaded right away and set to install at midnight of whichever day the patches were given authorization to install. The one exception to that is for the Windows servers. They download the patches when they are detected and then install on Saturday at midnight. In most cases one or more patches will require a reboot and that happens automatically after the last patch is installed for the server or the desktops/laptops. If the laptop, for example, is powered off, the patches get installed the next day when it is turned on.
Microsoft publishes patches and updates on the first Tuesday of every month. The number of patches and updates do vary but sometimes there are many and it may be advisable and wise to delay the installation of them for a week or two, to allow Microsoft to fix any defects in the published patches. Critical security patches that fix vulnerabilities by “unauthenticated remote attackers” should be installed as soon as possible.

It is important to review the patches and updates that are published by Microsoft each month. Even though WSUS is currently configured to only present patches for products we use, there are instances where a particular version of a product or an architecture of a product does not apply. When that happens, that patch or update can be declined from the WSUS GUI. Patches that don’t apply to any of our machines should not be downloaded to the WSUS database because they only take up valuable hard drive space. An example of this is when an update to Internet Explorer is published for the Itanium architecture. Since we have no servers with Itanium processors, that patch should be declined and not downloaded.

Other Important Information

* Dictionary updates for Microsoft Office should be declined because they take up very large amounts of hard drive space ( on Smithers ) which is disproportional to their usefulness
* Once per year, the superseded updates need to be removed from the WSUS database. The command for this is inside the settings GUI
* It is important to remove old decommissioned computers from the WSUS GUI as well as place newly installed computers into the correct WSUS group
* It is very rare that new Microsoft products are installed at UWD, but when they are, the corresponding product needs to be added into WSUS, otherwise it will not be recognized as needing updates. Same goes for when old Microsoft products are removed – they need to be removed from WSUS to save on disk space.
* There is no technical support from Microsoft for WSUS as it is a free product. There are many public websites that contain useful tips and those are the only available option for sorting out technical problems. That being said, WSUS is highly reliable and is the industry standard for enterprise grade patching of Microsoft software. If an IT administrator is not using WSUS, then they are doing it wrong.
* Microsoft has changed functionality in WSUS installed on Server 2012R2 for Windows10 clients. Make sure that if we deploy Windows10 clients they are getting the right patches in the correct manner from the WSUS server
* Feature updates have a .esd file extension, and therefore for IIS to pass it along, .esd needs to be added to the MIME file types on the WSUS server.

[[Category: Desktops/Company Workstations]]
[[Category: System Administration]]

Information Systems:Cannot Close Inbound Shipment-Purchase Order Locked by Another User

2021-05-27T22:00:31Z

Aaront:

When a user opens a PO in 'Work with Purchase Orders', the PO header records in file SROORPHE is flagged, so that no other process will attempt to update it until the first user is finished. If 'Work with Purchase Orders' does not complete properly, that flag is left on, so that the record remains locked. (Note - a software lock; not a system lock.)

Use [[Information Systems:DFU]] on file SRBPOH in library UP1480BFVA to clear the field 'WSID'.

When I position to the file, then put 18 in front of it, it takes me to a page that asks for the production order and the order number. Order number is what the user will give you and production number needs to be figured out.

[[Category: Receiving Problems (I.T.)]]

Information Systems:VoIP Phone Configuration

2021-05-27T17:51:03Z

Aaront: /* Cordless (DECT) Base and Phone Setup */

==Overview==
This article discusses the user-facing side of the phone system including deskphones, cordless phones, and headsets.

==Administration==
===Initial Setup===
====Deskphone Setup (Yealink)====
* The first step when configuring a new phone desk phone is to unbox and label the phone to its extension.
* The second step is to determine what port it will be plugged into , meaning which port on which switch it plugs into.
* Tag The port switch port
* Plug the phone into the local port
* Log into 3cx
* Under the phones tab find the new phone by extension
* Hit assign extension
* Use Lan at the office
* Use Interface 192.168.44.2
* Log into the phone interface and set the phone with a static IP? (maybe)

====Cordless (DECT) Base and Phone Setup====
web link to general setup https://www.3cx.com/sip-phones/manually-provision-yealink-dect/

* unbox the base and handset
* plug the base into switch
* navigate to the 3cx management page
* under the advanced tab select FXS/DECT
* add the base using the mac address to the list of bases already present.
* use the interface 192.168.44.2
* copy the provisioning link provided here in the general tab
* define the extensions in the extensions tab
* navigate to the ip address of the wireless base
* navigate to settings and auto configuration , use the provisioning link copied before in the space for server URL
* confirm, auto provision now.
* to add a phone to a base, press and hold the wifi button on the base until the top light starts to flash, then on the handset select register and they will find each other.
*username is admin, and the password for the base is found on the FS/Dect page for the base.
*The handsets are managed by the base on the accounts page. In a case where you are just replacing a non functioning unit, use the settings( Register name/username/password) from the unit you are going to replace. Disable the account of the non functioning unit and enable the new handset on a new account.

====DECT Repeater Setup====
*Setting up a repeater requires a dect base, handset that is paired to that base and the repeater itself.
*from a paired handset navigate to settings and put it into repeater mode, choosing the type of repeater.
*the base will automatically reset when the paired handset is put into repeater mode, wait for the base to come online
*connect the repeater to power
*hold down the pairing button on the base until the phone light starts to flash
*press the pairing button on the repeater.
* the dect light should go from red to orange when it finds the base.

''There is one repeater in the recieving mezzannine, and one in large down''

====3CX Windows client====
====3CX App (iOS/Android)====

===Firmware updates===
The Yealink deskphones and DECT bases require firmware updates. The firmware for the deskphones can and should only be updated through 3CX. This is because there is specific, 3CX-certified firmware which is different (and often lags behind) what Yealink generally releases. The firmware is auto-downloaded into the 3CX system as a part of its auto-updater. Once newer firmware is auto-downloaded into the repository, the system displays a warning for applicable phones that are now out of date. The firmware can be pushed from the 3CX console. This will reboot the phone and reset any user customizations that are not managed through 3CX. For example, the ringtone is manageable through 3CX, but the ''Display Clock'' within ''Screensaver'', is not.

==Supported deployment configurations==
This section discusses the different configurations that are in use currently. Originally there were only 2 standard configurations (office and warehouse employees), but the situation evolved rapidly due to COVID/WFH. In particular, the softphones, web client and mobile app have become part of standard usage, in some cases replacing the use of deskphones entirely e.g. Customer Service.

====General (in-office)====
:'''''Setup 1 (office):''''' Yealink deskphone, EPOS wireless headset via USB (connected to deskphone)
:'''''Setup 2 (warehouse):''''' Yealink cordless DECT phone
:'''''Setup 3 (certain staff):''''' 3CX Web Client, EPOS wireless headset via USB (connected to computer)
:'''''Optional components:''''' 3CX Web Client, 3CX App (mobile)

Setup 1 was the original setup for all office users, and involves a Yealink deskphone (T54W) and, for staff using a headset, an EPOS SD-Pro Or D10 DECT headset connected to the phone via USB.

Some staff who have been exposed to either the web client or mobile app (due to WFH or other means) continue to use these in-office for the additional features. For example, some warehouse supervisors use the mobile app instead of the cordless phone.

====WFH (except Customer Service)====
:'''''Setup:''''' 3CX Web Client and 3CX App (mobile)
:'''''Additional components: ''''' 3CX Browser Extension for Chrome or Edge (Chromium-based)

When working from home, the web client is the recommended deployment for office staff that are not in Customer Service. Theoretically, the web client is more performant through the WAN compared to the softphone as it uses WebRTC rather than SIP/RTP (I think...). Being browser-accessible, the web client is also simpler to deploy and maintain than the Windows client.

====Customer Service====
:'''''Setup 1: ''''' 3CX for Windows softphone, EPOS Connect, 3CX Plugin for EPOS
:'''''Setup 2 (WFH): ''''' 3CX for Windows softphone (through RDP), Poly/Plantronics C3220 USB headset (USB pass-through), Plantronics Hub Software (supports 3CX integration)
:'''''Additional components: ''''' Kuando BusyLight

The '''3CX for Windows''' softphone (a.k.a. desktop client) has become the preferred deployment for Customer Service agents, along with the headset connected directly to the computer. This is true whether in-office or WFH. Call control and other features are enabled through the EPOS Connect softaware and the 3CX Plugin for EPOS. While the headset could theoretically work in plug-and-play mode, both of these need to be installed for a smooth experience.

This software communicates to the server via the main LAN, which is different from the deskphones that [[Information_Systems:VoIP_LAN_configuration |communicate on the VoIP VLAN]].

For historical reference, the original deployment for CS agents involved a deskphone (including a sidecar attachment for the receptionist), and a wireless headset connected to the deskphone via USB. The deskphone introduced another vendor into the equation - Yealink, which in turn presented limitations due to only a subset of features on the deskphone being interoperable with 3CX. For example, the deskphone neither displays call queue information nor Away status for other users.

TBC -[[User:Norwinu|norwizzle]] ([[User talk:Norwinu|talk]])

[[Category: Phone System]]

Information Systems:VoIP Phone Configuration

2021-05-27T17:21:13Z

Aaront: /* Cordless (DECT) Base and Phone Setup */

==Overview==
This article discusses the user-facing side of the phone system including deskphones, cordless phones, and headsets.

==Administration==
===Initial Setup===
====Deskphone Setup (Yealink)====
* The first step when configuring a new phone desk phone is to unbox and label the phone to its extension.
* The second step is to determine what port it will be plugged into , meaning which port on which switch it plugs into.
* Tag The port switch port
* Plug the phone into the local port
* Log into 3cx
* Under the phones tab find the new phone by extension
* Hit assign extension
* Use Lan at the office
* Use Interface 192.168.44.2
* Log into the phone interface and set the phone with a static IP? (maybe)

====Cordless (DECT) Base and Phone Setup====
web link to general setup https://www.3cx.com/sip-phones/manually-provision-yealink-dect/

* unbox the base and handset
* plug the base into switch
* navigate to the 3cx management page
* under the advanced tab select FXS/DECT
* add the base using the mac address to the list of bases already present.
* use the interface 192.168.44.2
* copy the provisioning link provided here in the general tab
* define the extensions in the extensions tab
* navigate to the ip address of the wireless base
* navigate to settings and auto configuration , use the provisioning link copied before in the space for server URL
* confirm, auto provision now.
* to add a phone to a base, press and hold the wifi button on the base until the top light starts to flash, then on the handset select register and they will find each other.
*username is admin, and the password for the base is found on the FS/Dect page for the base.

====DECT Repeater Setup====
*Setting up a repeater requires a dect base, handset that is paired to that base and the repeater itself.
*from a paired handset navigate to settings and put it into repeater mode, choosing the type of repeater.
*the base will automatically reset when the paired handset is put into repeater mode, wait for the base to come online
*connect the repeater to power
*hold down the pairing button on the base until the phone light starts to flash
*press the pairing button on the repeater.
* the dect light should go from red to orange when it finds the base.

''There is one repeater in the recieving mezzannine, and one in large down''

====3CX Windows client====
====3CX App (iOS/Android)====

===Firmware updates===
The Yealink deskphones and DECT bases require firmware updates. The firmware for the deskphones can and should only be updated through 3CX. This is because there is specific, 3CX-certified firmware which is different (and often lags behind) what Yealink generally releases. The firmware is auto-downloaded into the 3CX system as a part of its auto-updater. Once newer firmware is auto-downloaded into the repository, the system displays a warning for applicable phones that are now out of date. The firmware can be pushed from the 3CX console. This will reboot the phone and reset any user customizations that are not managed through 3CX. For example, the ringtone is manageable through 3CX, but the ''Display Clock'' within ''Screensaver'', is not.

==Supported deployment configurations==
This section discusses the different configurations that are in use currently. Originally there were only 2 standard configurations (office and warehouse employees), but the situation evolved rapidly due to COVID/WFH. In particular, the softphones, web client and mobile app have become part of standard usage, in some cases replacing the use of deskphones entirely e.g. Customer Service.

====General (in-office)====
:'''''Setup 1 (office):''''' Yealink deskphone, EPOS wireless headset via USB (connected to deskphone)
:'''''Setup 2 (warehouse):''''' Yealink cordless DECT phone
:'''''Setup 3 (certain staff):''''' 3CX Web Client, EPOS wireless headset via USB (connected to computer)
:'''''Optional components:''''' 3CX Web Client, 3CX App (mobile)

Setup 1 was the original setup for all office users, and involves a Yealink deskphone (T54W) and, for staff using a headset, an EPOS SD-Pro Or D10 DECT headset connected to the phone via USB.

Some staff who have been exposed to either the web client or mobile app (due to WFH or other means) continue to use these in-office for the additional features. For example, some warehouse supervisors use the mobile app instead of the cordless phone.

====WFH (except Customer Service)====
:'''''Setup:''''' 3CX Web Client and 3CX App (mobile)
:'''''Additional components: ''''' 3CX Browser Extension for Chrome or Edge (Chromium-based)

When working from home, the web client is the recommended deployment for office staff that are not in Customer Service. Theoretically, the web client is more performant through the WAN compared to the softphone as it uses WebRTC rather than SIP/RTP (I think...). Being browser-accessible, the web client is also simpler to deploy and maintain than the Windows client.

====Customer Service====
:'''''Setup 1: ''''' 3CX for Windows softphone, EPOS Connect, 3CX Plugin for EPOS
:'''''Setup 2 (WFH): ''''' 3CX for Windows softphone (through RDP), Poly/Plantronics C3220 USB headset (USB pass-through), Plantronics Hub Software (supports 3CX integration)
:'''''Additional components: ''''' Kuando BusyLight

The '''3CX for Windows''' softphone (a.k.a. desktop client) has become the preferred deployment for Customer Service agents, along with the headset connected directly to the computer. This is true whether in-office or WFH. Call control and other features are enabled through the EPOS Connect softaware and the 3CX Plugin for EPOS. While the headset could theoretically work in plug-and-play mode, both of these need to be installed for a smooth experience.

This software communicates to the server via the main LAN, which is different from the deskphones that [[Information_Systems:VoIP_LAN_configuration |communicate on the VoIP VLAN]].

For historical reference, the original deployment for CS agents involved a deskphone (including a sidecar attachment for the receptionist), and a wireless headset connected to the deskphone via USB. The deskphone introduced another vendor into the equation - Yealink, which in turn presented limitations due to only a subset of features on the deskphone being interoperable with 3CX. For example, the deskphone neither displays call queue information nor Away status for other users.

TBC -[[User:Norwinu|norwizzle]] ([[User talk:Norwinu|talk]])

[[Category: Phone System]]

Information Systems:Barcodes for LTO5/6 Tapes

2021-05-25T20:09:52Z

Aaront: Created page with "The Barcodes for LTO5/6 tapes are being created using the brother P-touch editor on the Lab PC or can have it installed on a laptop and communicate with either the Qnl7xx whic..."

The Barcodes for LTO5/6 tapes are being created using the brother P-touch editor on the Lab PC or can have it installed on a laptop and communicate with either the Qnl7xx which is wireless on the network, or the Qnl5xx which is USB attached.

Barcode size needs to be exact and testing the label using an RF scanner should be done before sticking it to a tape.

Information Systems:Microsoft Office 2019 Training

2021-05-20T23:28:01Z

Aaront: /* Oulook how-to, FAQ */

=Microsoft Office 2019 Training=

The following link is provided as a free resource that provides comprehensive training on a variety of topics from basic to more advanced topics for Word 2019, Excel 2019, Powerpoint 2019 and Access 2019. Feel free to go through this training material on your own if you feel you need a refresher or would like to better familiarize yourself with the new look and features of Office 2019.

https://edu.gcfglobal.org/en/topics/office/

Additional training as needed will be added to this page.

=Outlook 2019 Training=

The following link is provided by Microsoft as a free resource that provides an excellent overview of Microsoft Outlook functionality for all platforms. For most staff Windows and iOS & Android training would be the training courses to focus on as we mainly use Outlook on our work provided Windows computers or as an app on your personal Apple or Android mobile device.

https://support.microsoft.com/en-us/office/outlook-training-8a5b816d-9052-4190-a5eb-494512343cca

=Oulook how-to, FAQ=
'''Outbox'''-This is holding area for emails that are not yet sent. The outbox is in alphabetical order in the folder tree by default, it may be dragged to any position needed.( this is true for all folders!)

'''Outbox''' is a folder that holds your emails before sending either by user choice or because you are offline. By default our outlook clients are set to not delay sending emails so this folder will be empty for most. If there is a need to delay the sending of an email, outbox should be configured to meet that requirement. In outlook options under advanced uncheck send immediately if connected, if you would like all emails to wait in the outbox before sending.

'''Junk Mail'''- If you are in your inbox or any folder that receives email, and there is mail there that you would like to block right click on the email and then hit junk, then hit block the sender, from now on that senders emails will go to your junk folder.
Junk Folder

This is a folder that has emails that have been flagged as junk. It may be in alphabetical order in the list of folders and can be dragged into whatever position is best.
This folder should be checked regularly when there is missing email, similar to barracuda. If an email is expected and it isn’t in your inbox, check the junk folder then reach out to Information Services.

What to do if….
*an email is in your junk folder and it shouldn’t you may right click on it and can choose to mark it as not junk.
*an email is in your inbox and you always want email from this sender to be junk, hit block sender.
*an email should never be blocked from a domain ,a mailing list, or a group we can choose to never block the sender preventing the mail from being marked as junk.

If you select junk mail options you will get choices to change the behaviour of automatic filtering, by default this is off.
There is a tab that has all the safe senders, recipients and blocked senders, you may unblock someone from here, if accidentally blocked.

*If you are selecting many emails at once you may use the home tab and section that is called delete to find the junk icon with all the same options but can be more easily applied to multiple emails at once.

'''Out of Office''' There is an out of office setting it is found by pressing file, then Automatic Replies ( out of office), from here you must choose to enable it for internal and external users and set the day and times for it to start and stop. There is also a rules function similar to mail rules that allows specific out of office messages conditions.

Additional training as needed will be added to this page.

[[Category: Training]]

Information Systems:SRFax (desktop faxing) Administration

2021-05-20T21:41:05Z

Aaront: /* Valid Fax Numbers For Outside Sources Like Pharmacies And Vendors When THEY Need To Send TO uniPHARM */

This is a technical guide. For user guides (e.g. how to send faxes), consult the [[:Category: Fax|'''Fax category''']].
==Overview==
uniPHARM uses a hosted fax service, SRFax, to send and receive fax documents such as recall notices to and from our business partners. This replaced Xerox/device-based faxing.

===How it works===
Users fax PDFs (or other supported documents) from the desktop as they would print something. A fax printer driver (downloadable from SRFax) is (or should be) installed on each computer, and printing from Windows applications should summon a pop-up where you configure cover pages, enter destination numbers etc., and finally, send the fax.

==Configuration==
===Account Details===
{| class="wikitable"
| Website (administration/user portal) || https://www.srfax.com
|-
| Login credentials || admin@unipharm.com / NewVisionIT2051
|-
| Subscription Details ||
:* $16.95 per month Health Care Plan
:* 800 pages included
:* $0.03/page overage
:* 6 additional inbound/outbound numbers at $4.95/month each
|-
| Company Info || Located in Sydney, BC
|-
|}

===SRFax Accounts===
If you really want a full understanding of the SRFax setup, make the effort to understand this section. Otherwise, skip it and wing it. The way the accounts are setup is a little complicated but was determined to achieve the best outcome (with regards to user ease-of-use and convenience of administration).

{| class="wikitable"
|-
! style="width: 15%"|Account Name !! style="width: 5%"|Account type (Main/Sub) !! style="width: 9%"|Billing account type (Inbound/Outbound) !! Purpose !! style="width: 7%"|Fax number !! Username/login !! Mapped aliases !! Account number !! Notes
|-
| Administration Account || '''Main''' || Inbound/Outbound || Primarily for admin purposes, also the ultimate ''route'' through which outbound faxes travel. || 604-276-8478 || admin@unipharm.com || norwinu, darrenf, jeremym, nancyn || 92531 || nancyn and jeremym aliased to this account for address book management and billing administration, respectively.
|-
| Outbound Fax - Company Main || Sub || Outbound only || Used to group users (majority of staff members) for outbound faxing || 604-276-8478 (routes through Main account) || fax@unipharm.com, or aliased users || Most staff members, with their usernames in AD format (e.g. norwinu; '''Exceptions''': tomc, timm1) || 99797 ||
|-
| Outbound Fax - Purchasing Dept. || Sub || Outbound only || Used to group Purchasing Dept. users for outbound faxing || 604-276-8478 (routes through Main account) || purchasing@unipharm.com, or aliased users || elizag, johnt, judyt, rubys, shannonm, simonl, monicat || 99783 || Separated out so department can keep their own address books, local to the group.
|-
| Inbound Fax - Receiving || Sub || Inbound/Outbound2 || Placeholder for inbound route only; for receiving faxes destined for Receiving department copier (reccopier) || 604-276-5250 || faxreceiving@unipharm.com || None || 99645 ||
|-
| Inbound Fax - Returns || Sub || Inbound/Outbound2 || Placeholder for inbound route only; for receiving faxes destined for Returns department copier (rtncopier) || 604-276-5283 || faxreturns@unipharm.com || None || 99643 ||
|-
| Inbound Fax - Elaho || Sub || Inbound/Outbound2 || Placeholder for inbound route only; for receiving faxes destined for 2nd-floor copier (elaho) || 604-270-9728 || faxelaho@unipharm.com || None || 99639 ||
|-
| Inbound Fax - Stein || Sub || Inbound/Outbound2 || Placeholder for inbound route only; for receiving faxes destined for 1st-floor copier (stein) || 604-270-8537 || faxstein@unipharm.com || None || 99647 ||
|-
| Angela Chan || Sub || Inbound/Outbound || Inbound and outbound; dedicated for use by Angela only || 604-270-2884 || angelac@unipharm.com || None || 99571 || Inbound faxes will print to ''angelacprinter''
|-
| Ralph Lai || Sub || Inbound/Outbound || Inbound and outbound; dedicated for use by Ralph only || 604-276-5255 || ralphl@unipharm.com || None || 99579 || Inbound faxes will print to ''rongprinter''
|-
|colspan="9"| 1 SRFax requires aliases to have a username > 4 characters, yet the email address cannot be used (reserved for user accounts). So the user names for tomc and timm are 'Tom Chotwanwirach' and 'Tim Matiachuk' respectively. Will they notice? Lol c'mon now, it's fax.
2 Note that while these accounts are of the Inbound/Outbound type (billing-wise), the point is that they are being used for inbound purposes only.
|}

The primary justification for the level of complexity in the way the users were set up came from the desire to keep the inbound fax "experience" the same as when uniPHARM used traditional Xerox/device-based faxing. Each Xerox had a phone number and thus represented a distinct inbound route. Each Xerox was also a distinct outbound route, yet this was not as important (i.e. origin of the fax was not important; the cover page always indicated the return fax number). Yet another factor was that that faxing is an infrequently used (and outdated) means of communication, so it was not ideal to set users up as full-featured sub-accounts, as that would've incurred unnecessary administrative burden. Lastly, it was sensible to have groups like Purchasing to have group-local address books. Thus to translate all these requirements to hosted/internet faxing, users were set up as shown above.

Key points:

* There are 2 concepts of "users" - '''user accounts''' and '''aliases'''. User accounts are those listed in the table above and, in our design, are mostly symbolic/representational, with the exception of Ron and Angela's (these are true user sub-accounts in the conventional sense). The rest of the staff members are not user accounts, but are aliases, aliased to one of the two symbolic "Outbound" users listed above. I.T. staff are aliased to the admin account.

* Regarding user accounts, there is one main account, to which all sub-accounts fall under. This is for administration purposes. User accounts can also be inbound/outbound and outbound-only. Inbound/outbound accounts have a dedicated fax number, while outbound-only accounts use the main account's fax number. '''''If I haven't lost you by now, congratulations. I am truly impressed. Not that this stuff is hard, but rather because of the [https://en.wikipedia.org/wiki/Rube_Goldberg_machine Rube Goldberg-ness] of the entire setup (a fax setup, no less). -[[User:Norwinu|norwizzle]] ([[User talk:Norwinu|talk]])'''''

* Any time a fax is sent, it is done through a specific user account. Aliased users therefore send as the user they are aliased to. When aliased users log in, they are all logging into the same account (which for most staff members, is '''Outbound Fax - Company Main''').

* Any time a fax is sent, it also must go out a certain fax number. For inbound/outbound user accounts, its own fax number is used. For outbound-only users, the main account's fax number is used.

* The concept of users only really comes into play during administration. That is, if you follow the table above, you will notice that all staff members (with the exception of Ron and Angela) ultimately send faxes through one number.

* All inbound faxing occurs through pre-defined routes, with phone numbers mapped to email addresses, which in turn are mapped to printers.

* Logging into the admin/main account lets you see everything across the sub-accounts, but some settings may require you to "admin-log-in" to the sub-account (similar to Barracuda administration, where you can enter into each user's account from the admin account).

===Address book===
The main account has the master address books, which all sub-accounts and their aliases can read, but not edit. The main account and its aliases, however, can edit these address books.

Each sub-account can have their local address books as well. This is primarily why some of them were created (e.g. '''Outbound Fax - Purchasing Dept.)

===Delivery notifications===
Because of the way users are set up, setting up delivery notifications (success/failure fax confirmations) to notify the original sender was a somewhat tricky matter. SRFax has been pre-configured to do the following:

* When faxing through the print driver, delivery notifications will be sent to the Email field in the Account Details tab (success or fail). This is a suitable workaround for the fact that aliased users all send faxes under the same account. Note that the user account's email address will also receive a copy. For example, if alias ''rubys'' sends a fax, it will send to ''rubys@unipharm.com'', as the fax driver is configured with this email. A delivery notification will also be sent to purchasing@unipharm.com (and since this email doesn't exist, we can expect this pathway to just be a blackhole).

* When faxing through the web portal, there is no Email field to specify. Thus, delivery confirmations will not be specific to the user, but

* The relevant settings can be found under '''Settings''' -> '''Sending Faxes'''. These settings are specific to each user account.

===Automatic Email Manager===
Automatic Email Manager is a piece of software installed inside the SuperServer virtual machine, that checks emails and auto-processes (prints or files) any contained attachments. It is an important part of the fax workflow as it prints inbound fax documents automatically to their designated printers (determined by destination email address, which in turn, [[#SRFax Accounts|is mapped to a specific inbound phone number]]).

[[Information Systems: Automatic Email Manager|Read more about Automatic Email Manager here]]

==Basic administration==
===Editing the master address books===
# Log in to SRFax as any of admin@unipharm.com, 92531, or the aliased users for this account.
# Navigate to '''Faxes''' -> '''Edit Address Book'''.
# Edit contact(s). A group may have to be selected first.
# This address book and its contacts are special in that they are visible to all users when sending a fax, but will not show up in the 'Edit Address Book' area of their accounts.

===Adding/removing a staff member (alias)===
Also for changing permissions for aliased users.
# Log in to SRFax as admin.
# Navigate to '''My Account''' -> '''User Administration'''.
# Most staff members will be aliased to '''Outbound Fax - Company Main'''. Click the Edit button for that account to log into it as admin.
# Navigate to '''My Account''' -> Account Access to see the aliases for this account.
# Add or remove users as needed. Edit permissions as needed.
# Click 'Exit' at the top left to return back to the admin account.

===Configuring the print driver===
Prior to doing this, make sure you have the account number of the user being set up. To retrieve this, log in as admin and navigate to '''My Account''' -> '''User Administration''', or consult the table above.
# Acquire and install the print driver from SRFax ('''Support''' -> '''SRFax Printer Driver''') if it is not already installed.
# Bring up the configuration/fax wizard by attempting to print something using the fax driver (the printer is named just SRFax).
# In the '''Account Details''' tab, click Change.
# Fill in the proper account number. ''For the majority of situations, it should be the account number of one of the Outbound accounts''.
# Enter the corresponding password. {{userpass}}
# '''Important: ''' If this computer is used primarily by one user, enter their email address in the Email field. This is where [[#Delivery notifications|delivery notifications]] are sent.
# Review the settings under the other tabs, change if necessary.
# Cancel out of the wizard.

===Inspecting fax traffic===
# Log in to SRFax as admin.
# Under '''Faxes''', navigate to any of '''Faxes Received''', '''Faxes Sent''', or '''Faxes Queued''' to analyze corresponding traffic. Use '''Call Log Reports''' to generate a report.
# Recall that since this the admin account, you can inspect/analyze usage/traffic of the sub-accounts.

===Billing tasks===
* Invoices are emailed to accountspayable@unipharm.com and jeremym@unipharm.com.
* The admin account can access and generate invoices in the web portal. There are also functions to display charges summarized by user in '''My Account''' -> '''Past Invoices'''.

===Valid Fax Numbers For Outside Sources Like Pharmacies And Vendors When THEY Need To Send TO uniPHARM===
* Main 604-270-8537
* Buying 604-270-9728
* Receiving 604-276-5250
* Returns 604-276-5283
* RalphL 604-276-5255
* AngelaC 604-270-2884

[[Category: Fax]]

Information Systems:Renewing the Web Orders SSL Certificate

2021-05-19T16:01:25Z

Aaront:

Instructions On How To Renew An SSL Certificate For Web order Or InfoNet
These instructions were written by DarrenF on January 11 2016 and describe what needs to be done when the SSL certificate on a website hosted on the Power8 needs to be renewed. Hopefully this all happens before the current expiry date.
# Go to https://bart.unipharm.local:2005/ibm/console - No as of 2019 use Web Navigator instead
# Ignore unsupported browser message
# Login with credentials – probably all object auth or qsec
# On left side IBM I Management panel, at the bottom, click on “Internet Configurations”
# Then click on “Digital Certificate Manager” in the main tab
# Log in again with same credentials
# On the left side, click on “Select A Certificate Store”
# Choose *SYSTEM and click continue
# Enter in the password which is visionit and click continue
# Click the triangle twisty next to “Manage Certificates” and then click “View Certificate”
# Write down the friendly name of the certificate that needs to be renewed because there may be duplicates from past years – make sure that you renew the correct certificate by checking the expiry date!
# Click “Renew Certificate” in the “Manage Certificate” menu
# Select the correct certificate that needs to be renewed and click the Renew button
# The next screen should only have 1 option as an Internet Certificate Authority, click continue
# Choose “Yes – Create a new key pair” and click continue
# The “New Certificate Label” is the friendly name for this renewal – try and make the label descriptive and unique
# Key size must be 2048
# Fill out the rest of the fields underneath Certificate Information and take a screenshot of that screen
# Country code is CA and then click continue
# Copy the certificate request into Notepad and save the file – be sure to copy from the first dash line to the end of the last dash line
# Click OK
# Take the saved block of text and provide that to the CA reseller when purchasing the renewed certificate
# Try and buy a renewed certificate for the longest period of time possible unless the website or server doing the hosting is going to be decommissioned
# If using Network Solutions they will do an email and phone validation on the SSL renewal to make sure that the certificate is going to the correct company
# When the CA has issued the renewed certificate, download it
# On the Digital Certificate Manager website, on the left side click “Import Certificate” from the “Manage Certificates” menu
# Choose “Server or client” and click continue
# The renewed certificate file from the CA needs to be copied to the IFS, /temp works well
# Type the file path into the import screen and click continue
# Assign the NEW certificate to the correct application which should be either Web Orders or InfoNet at the bottom of the list
# Specify the same friendly label as you chose in step 16 and click continue
# If you get an error that validation of the certificate failed then the CA’s root certificates also need to be imported in the correct order so that the renewed certificate can be validated all the way up the chain by going back to step 26 and choosing CA instead of server ( if unsure of this process call it in as doing it wrong can break the key and requires a repurchase of the key)
# Click on “Assign Certificate” from the “Manage Certificates” menu
# Choose the newly renewed certificate you just imported and click “Assign to Application”
# Either InfoNet or Web Orders should be at the bottom of the list, put a check mark in the right application and click REPLACE
# Delete the files that were put on the IFS as they are not needed anymore
# Log out of the Digital Certificate Manager page and the web Navigator site
# At this point you could stop the IBM HTTP( using IBMI navigator|File Systems|IBM Web Administration for i|Manage|Http Server|Websmart) server and then restart it to see the renewed certificate immediately – otherwise you will have to wait for the EOD to automatically bounce the web server instances
# Check in a web browser that the new certificate with the correct expiry dates is actually being used
# Profit

[[Category: WebSmart]]
[[Category: How-to pages]]
[[Category: I.T. Periodic Tasks]]
[[Category: SSL Certificates]]

Information Systems:Retro PC VM- windows 7 pro

2021-05-17T23:28:12Z

Aaront:

For RF administration this VM was created.
In order to get the VM to see the usb device, right click on the device in the vm pane. Then hover over removable devices, all usb devices will be listed, go ahead and connect to the usb device you want to connect to which will disconnect the device from the host and pass through to the VM.

Information Systems:Retro PC VM- windows 7 pro

2021-05-17T22:09:22Z

Aaront: Created page with "For Rf administration this VM was created. in order to get the vm to see the usb device, right click on the device in the vm pane. Then hover over removable devices, all usb..."

For Rf administration this VM was created.
in order to get the vm to see the usb device, right click on the device in the vm pane. Then hover over removable devices, all usb devices will be listed, go ahead and connect to the usb device you want to connect to which will disconnect the device from the host and pass through to the VM.

Information Systems:RF configuration / Standard deployment package

2021-05-17T21:16:41Z

Aaront: /* Files */

=Changes=

A single executable contains all the files necessary to install the MobiControl agent and Windows CE settings for deployment of an RF gun into production use. The following summarizes every single change that the MobiControl agent exacts on the device from its default configuration.

==Registry settings==
===DHCP===
DHCP is enabled
===Power===
* Display timeout:
* Backlight settings:
* Sleep timeout:

===Wireless (Summit Client Utility)===
The WAP G2 uses a wireless adapter by Summit Wireless. The utility (Start --> Programs --> Summit) has its own registry settings and defines settings associated with roaming, transmit power etc. The roaming settings are particularly important.

More info: http://www.summitdata.com/Documents/Glossary/knowledge_center_r.html#standard_roaming

==Files==
All the files needed to work with an RF gun are located in superserver\tech\RFguns
This includes the windows CE OS files
MCagent
ActiveSync Installer for windows 7

===Wallpaper===
Logo-v2.bmp is used as the device wallpaper.

===Config Change: Full ASCII mode for sign-on ID badges (Distribution Centre)===

May 29, 2015 - User accounts will have case-sensitive passwords on the new Power8, effective June 13, 2015. Distribution Centre staff scan ID badges to sign on to RF terminals, so new badges need to be generated. The Code 39 barcode format of these ID badges use special characters to specify lowercase. Thus, a change needs to be pushed out to all the RF terminals to set the Full ASCII mode in the terminal's Scanner Settings to on (it is off by default).

[[Category:RF Guns]]
[[Category:MobiControl]]

Information Systems:RF configuration / Standard deployment package

2021-05-17T21:16:13Z

Aaront: /* Files */

=Changes=

A single executable contains all the files necessary to install the MobiControl agent and Windows CE settings for deployment of an RF gun into production use. The following summarizes every single change that the MobiControl agent exacts on the device from its default configuration.

==Registry settings==
===DHCP===
DHCP is enabled
===Power===
* Display timeout:
* Backlight settings:
* Sleep timeout:

===Wireless (Summit Client Utility)===
The WAP G2 uses a wireless adapter by Summit Wireless. The utility (Start --> Programs --> Summit) has its own registry settings and defines settings associated with roaming, transmit power etc. The roaming settings are particularly important.

More info: http://www.summitdata.com/Documents/Glossary/knowledge_center_r.html#standard_roaming

==Files==
All the files needed to work with an RF gun are located in superserver\tech\RFguns
This includes the windows CE OS files
MCagent
ActiveSync Installer for windows

===Wallpaper===
Logo-v2.bmp is used as the device wallpaper.

===Config Change: Full ASCII mode for sign-on ID badges (Distribution Centre)===

May 29, 2015 - User accounts will have case-sensitive passwords on the new Power8, effective June 13, 2015. Distribution Centre staff scan ID badges to sign on to RF terminals, so new badges need to be generated. The Code 39 barcode format of these ID badges use special characters to specify lowercase. Thus, a change needs to be pushed out to all the RF terminals to set the Full ASCII mode in the terminal's Scanner Settings to on (it is off by default).

[[Category:RF Guns]]
[[Category:MobiControl]]

Information Systems:Laser Printers

2021-05-15T02:37:58Z

Aaront:

This article is to keep track of the laser printers used in the distribution centre and office.

{| class="wikitable"
|-
! Hostname !! Location !! Model !! Notes
|-
| gm-printer || GM's office || Brother MFC-L3770CDW || -
|-
| Example || Example || Example || -
|-
| Example || Example || Example || -
|-
| Example || Example || Example || -
|-
| it-lab-printer || IT Lab/Cage || Lexmark MS415DN || -
|-
| buying-dept-printer || Buying Department || Lexmark MS415DN || -
|-
| accounting-dept-printer || Accounting Department || Lexmark MS415DN || -
|-
| dc-office-printer || DC Office || Lexmark MS415DN || -
|-
| dc-large-down-invoice-printer || DC Large Down || Lexmark MS521DN || -
|-
| dc-fridge-invoice-printer || DC Fridge || Lexmark MS521DN || -
|-
| dc-narc-invoice-printer || DC Narc Cage || Lexmark MS521DN || -
|}

===Old===

uniPHARM uses Lexmark laser printers for printing invoices at each picking station in the distribution centre. The most common model is the T650/T652. In the past we also used the T640 and T630 which have all been phased out. Lexmark colour laser and black only laser printers are present in the office areas. While there is no restriction on the use of other brands of laser printers (HP for example) it is a best practice to keep the number of brands as close to 1 as possible so that users don't have to adjust to 10 different print drivers. The T650 lasers at each of the picking stations is connected to the HP print server box with a parallel cable. When purchasing replacement invoice printers, the parallel port must also be purchased as new black only laser printers don't come with a built in port. This of course wouldn't be a problem if we could just network attach all the picking station printers. Also keep in mind that the T650s that print invoices at the picking stations are all using their factory defaults because they are not network attached. All they need is to be plugged into the HP print server box with a parallel cable and powered on. If the Lexmark still does not print an invoice then power cycle the HP print server box at the picking station. If that still doesn't work then check the network cable. If the green lights on the HP print server box are not blinking rapidly then there is no valid network connection.

The Lexmark printers at the picking stations are not setup as shared network printers from a Windows print server. The HP boxes are configured as TCPIP printers on the Lucy Jetforms server, but they are not shared so that users can print to them. The 2 Lexmarks in the office area are setup as shared network printers from SuperServer and are used by staff for general office printing.

BONUS MAGIC SAUCE TIP
If you need to install a new fuser into the LP05 printer in accounting (C748 model) and the printer refuses to see a brand new fuser as a brand new fuser, reboot the printer while holding down the 2 and the 6 buttons on the front panel. The printer will boot into a special configuration menu where you have to reset the page counter on the new fuser. I suppose you could do this same trick when that printer prompts for a new fuser because that printer eats consumables like the fat Austrian kid on the Simpsons eats chocolate.

To reset the T650/52 d/dn maintenance counter turn the power off, hold the check mark and the right arrow while turning on and wait for the 128mb to flash then wait for the config menu.Reset the maintenance clock from there.

Replacing the consumables should be evidence based, the print quality or page count should be used to determine if the consumable actually needs to be changed. Resetting the maintenance counter is sometimes preferred as the consumable being low may be inaccurate.

[[Category:Printing]]

Information Systems:Xerox printers

2021-05-12T17:30:57Z

Aaront:

uniPHARM uses Xerox printers for office printing (as opposed to Lexmark printers used in the warehouse). These printers are under either lease or managed print service agreements:

{| class="wikitable sortable"
|-
! Printer hostname !! Model !! Location / purpose !! Contract type
|-
| reccopier || Xerox VersaLink B405DN || Receiving area office || Managed Print Services
|-
| rtncopier || Xerox VersaLink B405DN || Returns department || Managed Print Services
|-
| elaho || Xerox Versa C60 || 2nd-floor printing alcove || Lease
|-
| stein || Xerox AltaLink B8055 || 1st-floor [[:Category:uniPHARM Dictionary|dumps area]] || Lease
|}

==Support info==

* Contact number for leased printers (Xerox One Number): 1-800-275-9376
* Contact number for printers under Managed Print Services: 1-866-487-4239
* Contract end date: December 2023 (?)

==Old printers==
This section is for reference purposes. These printers are no longer being used.

There are 4 different Xerox copier models in use as of 2016. The Colour C60 is located in the printing alcove on the second floor. The colour touch screen is used to setup copy, scan and fax options. The has 2 fax lines connected so that it can fax inbound and outbound at the same time. The C60 is leased and Xerox provides consumable toner and other supplies as part of the lease cost. Xerox also provides technical support and repairs as part of the lease. When requesting supplies, repairs or support you must provide the serial number which can be found on the copiers admin page.

:[http://elaho.unipharm.local/ Elaho Administration Web GUI]

*admin
*1111
*at this time you must use edge/explorer for web administration.
Supplies Phone Number 1-800-275-9376
Support Phone Number 1-800-275-9376

The WorkCentre 5855 is located next the Supervisors Office in the shipping area of the DC. It has no colour capability but it does have the ability to fax inbound/outbound. The supplies the 5855 uses are different from the 7775 and there is a much smaller and less complicated touch screen. The 5855 is also on the same lease program as the 7775.

:[http://stein.unipharm.local/ Stein Administration Web GUI]

*admin
*1111

The WorkCentre 4265 copiers are located in the Receiving Office and the Returns Areas in the DC. They are smaller copiers with fewer paper trays. They both do have a single fax phone line attached and have very similar software capabilities compared to the 5855 and are on the same lease program as the 5855 and 7775.

:[http://reccopier.unipharm.local/ Reccopier Administration Web GUI]
:[http://rtncopier.unipharm.local/ Rtncopier Administration Web GUI]

*admin
*1111

The WorkCentre 6605 copiers are slightly smaller than the 4265s but otherwise perform and behave in the same way. The 6605s were free from Xerox and are NOT on the lease program and toner and supplies DO need to be purchased for the 2 that are used by the payroll administrator and general manager. Both of the 6605s are network and fax attached.

==Xerox Fleet Management==
This is a useful portal site that Xerox provides for leased or managed printers
* https://office.services.xerox.com/FMP/LoginPage.aspx
* Username is darrenf@unipharm.com
* Password is NewVisionIT2051@!

==Xerox Device Agent Software===
There is an application from Xerox called the Xerox Device Agent, installed on the WDS virtual machine. This program sends the page meter reads for the copiers in Returns and Receiving to WestX for billing purposes. This application consumes a lot of CPU time. DarrenF tried for 4 months to get Xerox and its developers to figure out why a crappy little program uses so much CPU 24/7. Xerox wasn't willing to acknowledge a problem or allow a conversation to happen with their in-house developers - so the support ticket was closed as unresolved. The Xerox Device Agent software needs to continue to run and report billing data to WestX so if the CPU usage becomes a problem, try to get a new version of the app or open a new ticket with Xerox and prepare for pain.

This was resolved, it was due to not having the newest version of the app provided by west X , running smooth now.

==Xerox NeckBeard Support==
On June 13th, 2019, a Xerox technician was called onsite to fix the C60 that was not copying paper in the top feeder or from the glass. He determined that the OS was corrupt and did a factory reset of the machine which wiped out all of its configuration settings. He failed to notify anyone that he was doing a factory reset and he failed to create a backup clone file of the configuration to restore. This caused a great deal of inconvenience and extra work that was not necessary if a clone file was available. If this dumbfuckery ever happens again, there are saved clone files on the SuperServer in the following location : \\superserver.unipharm.local\Tech\Logs And Backups\Xerox Copier Clone Files\. In that folder are clone files for all the leased and MPS copiers as of June 2019. The 2 Xerox MFDs that are used by RonG and AngelaC cannot produce clone files. In case you haven't caught on, a clone file is a file that contains all the settings that are configured on a printer, with the purpose of "cloning" itself onto another printer of the same model or the exact same one after some asshat decides to do something idiotic.

Xerox support is very helpful, when called they respond within a day. They are willing to teach and leave extra supplies in case of emergent need. Recently the C60 needed to have maintenance, remember that the bottom drawer has a security screw, if need be to release the drawer and unjam the document, replace pick rollers.

The Altalink , also under the service has temporary files that need to be cleared out regularly, this can be scheduled, and takes 20-60 minutes based on what you are clearing.
Software update performed may 12 2021, with support, to resolve network card restart issue.

[[Category: Printing]]
[[Category: Pages with Contact Information]]

Information Systems:Microsoft Office 2019 Training

2021-05-11T19:49:36Z

Aaront: /* Oulook how-to, FAQ */

=Microsoft Office 2019 Training=

The following link is provided as a free resource that provides comprehensive training on a variety of topics from basic to more advanced topics for Word 2019, Excel 2019, Powerpoint 2019 and Access 2019. Feel free to go through this training material on your own if you feel you need a refresher or would like to better familiarize yourself with the new look and features of Office 2019.

https://edu.gcfglobal.org/en/topics/office/

Additional training as needed will be added to this page.

=Outlook 2019 Training=

The following link is provided by Microsoft as a free resource that provides an excellent overview of Microsoft Outlook functionality for all platforms. For most staff Windows and iOS & Android training would be the training courses to focus on as we mainly use Outlook on our work provided Windows computers or as an app on your personal Apple or Android mobile device.

https://support.microsoft.com/en-us/office/outlook-training-8a5b816d-9052-4190-a5eb-494512343cca

=Oulook how-to, FAQ=
'''Outbox'''-This is holding area for emails that are not yet sent. The outbox is in alphabetical order in the folder tree by default, it may be dragged to any position needed.( this is true for all folders!)

'''Outbox''' is a folder that holds your emails before sending either by user choice or because you are offline. By default our outlook clients are set to not delay sending emails so this folder will be empty for most. If there is a need to delay the sending of an email, outbox should be configured to meet that requirement. In outlook options under advanced uncheck send immediately if connected, if you would like all emails to wait in the outbox before sending.

'''Junk Mail'''- If you are in your inbox or any folder that receives email, and there is mail there that you would like to block right click on the email and then hit junk, then hit block the sender, from now on that senders emails will go to your junk folder.
Junk Folder

This is a folder that has emails that have been flagged as junk. It may be in alphabetical order in the list of folders and can be dragged into whatever position is best.
This folder should be checked regularly when there is missing email, similar to barracuda. If an email is expected and it isn’t in your inbox, check the junk folder then reach out to Information Services.

What to do if….
*an email is in your junk folder and it shouldn’t you may right click on it and can choose to mark it as not junk.
*an email is in your inbox and you always want email from this sender to be junk, hit block sender.
*an email should never be blocked from a domain ,a mailing list, or a group we can choose to never block the sender preventing the mail from being marked as junk.

If you select junk mail options you will get choices to change the behaviour of automatic filtering, by default this is off.
There is a tab that has all the safe senders, recipients and blocked senders, you may unblock someone from here, if accidentally blocked.

*If you are selecting many emails at once you may use the home tab and section that is called delete to find the junk icon with all the same options but can be more easily applied to multiple emails at once.

Additional training as needed will be added to this page.

[[Category: Training]]

Information Systems:Microsoft Office 2019 Training

2021-05-11T19:49:15Z

Aaront:

=Microsoft Office 2019 Training=

The following link is provided as a free resource that provides comprehensive training on a variety of topics from basic to more advanced topics for Word 2019, Excel 2019, Powerpoint 2019 and Access 2019. Feel free to go through this training material on your own if you feel you need a refresher or would like to better familiarize yourself with the new look and features of Office 2019.

https://edu.gcfglobal.org/en/topics/office/

Additional training as needed will be added to this page.

=Outlook 2019 Training=

The following link is provided by Microsoft as a free resource that provides an excellent overview of Microsoft Outlook functionality for all platforms. For most staff Windows and iOS & Android training would be the training courses to focus on as we mainly use Outlook on our work provided Windows computers or as an app on your personal Apple or Android mobile device.

https://support.microsoft.com/en-us/office/outlook-training-8a5b816d-9052-4190-a5eb-494512343cca

=Oulook how-to, FAQ=
Outbox-This is holding area for emails that are not yet sent. The outbox is in alphabetical order in the folder tree by default, it may be dragged to any position needed.( this is true for all folders!)

'''Outbox''' is a folder that holds your emails before sending either by user choice or because you are offline. By default our outlook clients are set to not delay sending emails so this folder will be empty for most. If there is a need to delay the sending of an email, outbox should be configured to meet that requirement. In outlook options under advanced uncheck send immediately if connected, if you would like all emails to wait in the outbox before sending.

'''Junk Mail'''- If you are in your inbox or any folder that receives email, and there is mail there that you would like to block right click on the email and then hit junk, then hit block the sender, from now on that senders emails will go to your junk folder.
Junk Folder

This is a folder that has emails that have been flagged as junk. It may be in alphabetical order in the list of folders and can be dragged into whatever position is best.
This folder should be checked regularly when there is missing email, similar to barracuda. If an email is expected and it isn’t in your inbox, check the junk folder then reach out to Information Services.

What to do if….
*an email is in your junk folder and it shouldn’t you may right click on it and can choose to mark it as not junk.
*an email is in your inbox and you always want email from this sender to be junk, hit block sender.
*an email should never be blocked from a domain ,a mailing list, or a group we can choose to never block the sender preventing the mail from being marked as junk.

If you select junk mail options you will get choices to change the behaviour of automatic filtering, by default this is off.
There is a tab that has all the safe senders, recipients and blocked senders, you may unblock someone from here, if accidentally blocked.

*If you are selecting many emails at once you may use the home tab and section that is called delete to find the junk icon with all the same options but can be more easily applied to multiple emails at once.

Additional training as needed will be added to this page.

[[Category: Training]]

Information Systems:Exchange and Outlook Administration

2021-05-10T22:26:19Z

Aaront: /* How-tos */

==How-tos==
===Fix default mail app glitch===
On a computer where the HCL Notes installation preceded the Outlook installation, some applications may continue to invoke Notes when using the "Send via email" function. This occurs even after all the file types, protocols, and default application have been changed in Windows -> Default Programs. 2 examples that can be used to test for or reproduce the problem are Microsoft Excel (File -> Share -> Email) and the old Snipping Tool (right-click on screenshot, then "Send To").

The fix is to delete the '''HCL Notes''' key (and all its subkeys) in <code>HKEY_LOCAL_MACHINE\SOFTWARE\Clients\Mail</code>.

this is a link to the outlook troubleshooting page.
https://docs.microsoft.com/en-us/outlook/troubleshoot/outlook-client-welcome

[[Category: Email]]

Information Systems:Website SSL Certificates

2021-05-07T15:47:11Z

Aaront: /* Certificate Details */

==Background==
uniPHARM hosts several websites using HTTPS and therefore maintains SSL/TLS certificates.

==Certificate Details==
{| class="wikitable"
|-
! Website/Service !! Provider !! Managed By !! Notes
|-
| unipharm.com || Sectigo || Network Solutions || Exware hosts the site, therefore they provide the CSR, which uniPHARM submits to NS. Cert is provided back to Exware.
|-
| medicinecentre.com || LetsEncrypt || Exware || Managed by Exware. This is a LetsEncrypt cert that has 90-day validity. Exware automates the renewals.
|-
| secure.medicinecentre.com || Sectigo || Network Solutions || Used for the [https://secure.medicinecentre.com/ website Rx refill form]
|-
| orders.unipharm.com (Web Orders) || Sectigo || Network Solutions || Web Orders
|-
| infonet.unipharm.com || Sectigo || Network Solutions || Infonet
|-
| nts.unipharm.com || Sectigo || Network Solutions || IBM iNotes webmail access, I think Traveler/Verse app too, to some degree
|-
| mail.unipharm.com || Sectigo || Network Solutions || Used for secure mail protocols, webmail client portal
|-
| infonext.unipharm.com || LetsEncrypt || uniPHARM IT || [[Information_Systems:UWDOSS_-_Open_Source_Development_Server#Renew_SSL_certificate|Must be auto-renewed]].
|-
| unipharm.3cx.ca || LetsEncrypt || 3CX || Auto-managed by the 3CX software (likely certbot).
|-
| rmtgw.unipharm.com || Sectigo || Network Solutions || Developed and maintained for WFH during COVID-19
|}

Network Solutions certificates must be renewed on a yearly basis.

==Notes==
* The Network Solutions certificates are signed by the AddTrust/USERTrust root CA. These CAs are owned by COMODO/Sectigo.
* Previously, 2+ year certs were allowed. There was a change in industry that now prevents this to something like 390 days (13 months). Any 2-year options e.g. from Network Solutions is likely now just for accounting/payment convenience i.e. a new cert will still need to be generated ever year.

[[Category: SSL Certificates]]

Information Systems:Electronic Ordering

2021-05-06T17:07:04Z

Aaront: /* Setup for email-based order systems */

==Background==
Electronic ordering is colloquially known as POS ordering. POS systems will be used to refer to software at the store that is used to submit electronic orders to uniPHARM.
There are two primary ways of ordering from uniPHARM: [[:Category:Web Orders | Web Orders]], and electronic ordering. This section discusses the latter. POS systems are proprietary software (with complementing hardware, in some cases) that communicate with uniPHARM to place orders and, in some cases, retrieve invoices. Most POS systems communicate via FTP, while some send orders via email. For the store, a POS system is a way to do inventory management, as quantities can be managed for each product and thus automated ordering can be set up based on levels of stock. While Web Orders allows for convenient on-demand ordering, POS systems are becoming more and more popular for stores that want better control, automated ordering, and insight into their inventory.

==Setup for email-based order systems==
As of 2018, uniPHARM is trying to discourage email ordering. POS systems that send orders via email are still supported, but new setups are almost always FTP-based. WinRx is the exception.
As of the fall of 2020 and spring of 2021 WinRx has an FTP option, however they are slow to roll it out to stores as "not all the stores can handle the change"- ARI.

Email ordering is straightforward and is usually carried out by the software provider.

==Setup for FTP-based order systems==

Upon acquiring a POS/PMS system, either the POS vendor (most cases) or the store will request for credentials to be able to connect their software to our system. Most of the configuration is related to FTP connectivity, as email connectivity (where applicable) is pre-configured.

===Create folders on the Mail server===
Using remote desktop or Windows Explorer, navigate to the C:\FTPOrders folder on Mail. Create a folder for the store using their account number as the folder name. If one already exists, this indicates that this is the store's 2nd POS system. Append a suffix to the folder. This folder will be the user's home directory.

Within this folder, create '''invoices''', '''orders''' and '''orders\z-archive''' i.e.:

: C:\FTPOrders\12345\invoices
: C:\FTPOrders\12345\orders
: C:\FTPOrders\12345\orders\z-archive

Important: The folder name "z-archive" is because the RPG program that reads the folder reads everything alphabetically. Since an "archive" folder comes alphabetically before the filenames of the order files e.g. "order-102323.pos", the program skips this folder without error.

===Generate Serv-U account===
Make an FTP account for the store in Serv-U, matching the username with the home directory (folder) you created in the previous step i.e. '12345K' for C:\FTPOrders\12345K. It is important that the username matches the foldername, as the directory permissions and virtual paths that will be pre-configured are based on this. Generate this password. Specify these additional settings:

* Home directory should be set to the folder '''''that contains''''' the '''invoices''' and '''orders''' subfolders i.e. C:\FTPOrders\12345\ranger
* Ensure ''Lock home user in directory'' is checked.

Finally, under the Groups tab, add the user to either the POS-Shareholders or POS-Customers groups. '''This step is very important''', as directory permissions and virtual paths are specified accordingly.

'''Note: The process of adding POS FTP users has been simplified through the use of the New User template and groups. For details on these pre-configured settings, check out [[Information Systems:Serv-U FTP Server|this page]].'''

===Create AIP records===

FTP configuration on the i involves two files - one to retrieve order files from our FTP server (mail), and one to write invoices to the same server. A record will need to be added to both files for each store setup:

# In Extensions, use menu option 22 - Work with UWD IT Tools and 30 - FTP connections
# Add the records below by using menu options 4 and 5. F10 within DFU adds a new record

====4-Order FTP Configuration====

Name: Cust12345
Description: Northview Pharmacy
FTP Server: ftp.unipharm.com
FTP User ID: ftporders <-- The i uses the same account for all stores to access their folders on the FTP server
FTP Password: visionit525
FTP Directory: 12345/ranger/orders <-- Double-check this folder to make sure it's the same as the one you created on the FTP server
FTP Archive Directory: z-archive
M=Move D=Delete N=None: M <-- Use D to just delete files instead of archiving if M doesn't work.
Transmission Source: FTP
Customer # Type: UWD
Ext 1: X12 <-- Use KRO for Kroll, DAT for AssystPOS/AssystRx, X12 for DCS/Ranger , ARI/applied robotics
Ext 2:
Ext 3:

====5-Invoice FTP Configuration====

Partner: 12345
Order Source: <-- Leave blank to set as the catch-all i.e. all other invoices sent to this POS
Description: Northview Pharmacy - Default
FTP Server: ftp.unipharm.com
FTP User ID: ftporders
FTP Password: visionit525
FTP Directory: 12345/ranger/invoices <-- Double-check this folder to make sure it is the same as the one you created on the FTP server.

===Creating a second account for a second POS system (if necessary)===

Should a store request setup for a second POS/PMS system, follow the steps above with these additional changes:

# Make their second Serv-U account unique by appending a letter to the end of their username e.g. '''12345K''', for a Kroll installation.
# Append the same letter when creating new records in the Order ,however create the same customer number . FTP configuration on the i e.g. 12345K and Cust12345K
# Create the necessary folders, see instructions in section [[#Create folders on the Mail server | Create folders on the Mail server]]

==POS Systems used by uniPHARM customers==
This section details previous experiences and general notes about the various POS and PMS systems that interact with uniPHARM. With the exception of WinRx, on-site I.T. staff have no access to the software, so the following information is the result of over-the-phone troubleshooting experience and dealing with the technical support departments of these companies.
===Telus AssystRx/AssystPOS===
Also known as Assyst Rx-A
====Contact information====
* Company name: Telus Health
* Phone: 1-888-561-6555
====Notes/Issues====
* There are stretches of time where some stores place orders that never reach our system. They may or may not get an order confirmation (most of the time they do not), but there is also no seeming error on their end, leading to the frustrating experience of not receiving an expected delivery the next day. To date, the exact cause of this is unknown, but it is suspected that the Pharmanet connection is the culprit. See [[Pharmanet]] for explanation

* The following an email from Don Yakubowski at Telus Assyst Health that sheds some light on how the mailer works in AssystPOS/AssystRx for sending orders to uniPHARM.

Ok a few things to clarify here..
* The Assyst app relies on the routing as defined on their Unix server..site does not run Assyst Rx-A or POS on a Windows server. Yes..they have windows wkstns, and they are using some
Windows based mail application to receive their email replies..the confirmation emails...but the orders outbound to Unipharm originate from the Unix server.
* The routing the email order will take follows whatever is defined on Unix server and in this case, since the Pharmanet path is the server's Default gateway with no other
Static routing defined....ALL traffic from the Unix server is presently going out the Pnet path. This is NOT something defined within the Assyst application per se...but is at the Unix level.
* To alter the path when a customer is using both Assyst RX-A and POS...and therefore needs to send claims to Pnet from the same Unix server, it is common to leave the Pnet path as
The default, and if other destinations should have or must have a non-Pnet path such as their alternative HS router, then we would ADD static routes to the Unix server redirecting that traffic
Via the alternate gateway. IN this example, if we wish to keep the Unix server sending Pnet /RX related traffic out Pnet path, and only intervene to have Unipharm destined order emails
Go out thru hsrouter, we would add a route on Unix server like: /etc/route add mail.unipharm.com 192.168.0.2 ( where 0.1 is the def GW Pnet path, and 0.2 is the hsrouter path ).
* This routing is not application or protocol specific...it would send anything destined to mail.unipharm.com out this hsrouter path after such a setting got applied.
This would also remain in place thru any Unix server reboot as it gets added into server startup scripts that execute every time server is rebooted.
* As Norwin pointed out, such routing decisions could not be applied by the Dlink 1024 switch as it is not a Layer 3 ( routing capable ) switch, so the only places to
Apply and control routing here are directly on the Unix server itself, or depending on what the actual "router" units are that are installed in this network, on the routers themselves.
Some routers can support having "static"routes added into them, others can not.
-Don

===RangerPOS===
====Contact info====
* Company name: DCS Tech

===CashRx===
* Company name: CashRx
* Website: http://www.cashrx.ca/

===KrollRx===
* Company name: Kroll Systems

===ARI WinRx===
====Contact info====
Company name: Applied Robotics Inc.

--[[User:Norwinu|norwinu]] ([[User talk:Norwinu|talk]]) 10:17, 13 July 2015 (PDT) To my limited understanding, a PMS has the functionality of a POS, in that it is able to place orders from uniPHARM, but it also manages the dispensing and inventory of pharmaceuticals.

==Troubleshooting==
===IOP reporting duplicate POs===
If IOP reports duplicate POs, delete the files manually on the FTP server. They will likely still be sitting there. Then, set the Orders configuration file to D for delete, or, if it's M, make sure the files are being moved to the archive folder (which might mean renaming the folder).

The AIP programs (RPG) responsible for fetching the order files from ServU via FTP do not read the directory listings elegantly. For example, if there is a folder called archive, and the order files are of the Telus Assyst format e.g. order-1023.pos, then AIP will pick up and process the order, but fail to move the file into the archive folder (for reasons unknown, because the program silently fails). If the folder is re-named z-archive, the M works, but then AIP will log errors every 3 minutes because it's not hardcoded to recognize "z-archive" (although this is an acceptable outcome).

[[Category: Ordering]]
[[Category: FTP]]

Information Systems:Staff Onboarding How-To

2021-05-05T22:19:51Z

Aaront: /* Extra things to check */

==Overview==
This page outlines the process for setting up a new Unipharm employee / staff member.

Main areas where user profiles have to be defined or linked to AD/green-screen profiles:
* Active Directory domain user
* IBM i user profile (green-screen/Mocha access)
* ASW profile for IBM i user
* UNITY user profile
* MS365 Mailbox
* Moodle user (linked to AD user)
* Unipharm wiki user (linked to AD user)
* WiNG wireless (staff WiFi)
* Kofax scanning profile, if applicable (linked to AD user)
* DocView permissions (IBM i user profile)
* Xerox scanning profile, if applicable

==Instructions==
* Create AD user, verify group membership if copying another user, or set manually.
* Use Navigator or green screen to create IBM i user profile. Also copy existing user for convenience.
* Go into UNITY (green-screen), System Administration -> OMM Menus -> Work with User Security (if prompted for password, just press Enter).
* Position to or search for existing user to be used a template, use 8 beside the entry to copy user into a new UNITY user matching green-screen username.
* Configure MA (menu authority) for new user by entering MA beside their name. F10 to copy from existing user. Leave Menu name blank and just enter the source and target user profiles to copy all menu authorities.
* Configure FA (functional authority) using FA beside the name. To copy from existing user, type 'USR' in '''Type''', and the source user profile in '''Qualifier'''. Press Enter, and you should see a comparison of the source and target functional authorities. Use F19 (shift F7) to grant missing.
* Configure ASW user profile [[Information Systems: ASW User Security|using these instructions]]

==Extra things to check==
Depending on the role of the new employee, the following may also need to be checked and configured in advance:

* Mapped drives
* Permissions to send to Notes distribution lists
* SRFax
*http://owl.unipharm.local/mediawiki/index.php/Information_Systems:Extension_User_Security
* [[Information Systems:ASW favorites (menu items)|ASW favorites (menu items)]]

[[Category: Staff On-boarding]]

Information Systems:Staff Onboarding How-To

2021-05-05T20:47:28Z

Aaront: /* Overview */

==Overview==
This page outlines the process for setting up a new Unipharm employee / staff member.

Main areas where user profiles have to be defined or linked to AD/green-screen profiles:
* Active Directory domain user
* IBM i user profile (green-screen/Mocha access)
* ASW profile for IBM i user
* UNITY user profile
* MS365 Mailbox
* Moodle user (linked to AD user)
* Unipharm wiki user (linked to AD user)
* WiNG wireless (staff WiFi)
* Kofax scanning profile, if applicable (linked to AD user)
* DocView permissions (IBM i user profile)
* Xerox scanning profile, if applicable

==Instructions==
* Create AD user, verify group membership if copying another user, or set manually.
* Use Navigator or green screen to create IBM i user profile. Also copy existing user for convenience.
* Go into UNITY (green-screen), System Administration -> OMM Menus -> Work with User Security (if prompted for password, just press Enter).
* Position to or search for existing user to be used a template, use 8 beside the entry to copy user into a new UNITY user matching green-screen username.
* Configure MA (menu authority) for new user by entering MA beside their name. F10 to copy from existing user. Leave Menu name blank and just enter the source and target user profiles to copy all menu authorities.
* Configure FA (functional authority) using FA beside the name. To copy from existing user, type 'USR' in '''Type''', and the source user profile in '''Qualifier'''. Press Enter, and you should see a comparison of the source and target functional authorities. Use F19 (shift F7) to grant missing.
* Configure ASW user profile [[Information Systems: ASW User Security|using these instructions]]

==Extra things to check==
Depending on the role of the new employee, the following may also need to be checked and configured in advance:

* Mapped drives
* Permissions to send to Notes distribution lists
* SRFax
* [[Information Systems:ASW favorites (menu items)|ASW favorites (menu items)]]

[[Category: Staff On-boarding]]

Information Systems:SuperServer

2021-05-04T20:26:47Z

Aaront:

SuperServer is the file and print server used by all staff. All user created files such as Word or Excel files need to be saved on the SuperServer. All of the office area laser printers and copiers are shared from SuperServer.

The OS on this machine is Windows Server 2008R2. The file and print server role is the only role that is installed on SuperServer. The C: drive on the SuperServer only contains the OS and small applications for monitoring and controlling the RAID hardware and emailing of faxes. The D: and E: drives are used for file storage. Both the D: and E: have Shadow Copies turned on with a 100GB limit and the Shadow Copy service is on a schedule running every 2 hours from 7AM to 6PM daily. The Shadow Copy service is set to take a snapshot every 2 hours starting at 7AM and stop at 5PM. Please note that most if not all Cryptolocker malware is able to delete Shadow Copy snapshots.

The structure of the shared folders is either by department or by general function. Permissions are applied through Active Directory groups with either read or modify permissions. The "messiness" of the shared folders is mostly under control but there is room for improvement. There are very large numbers of files that are not used or opened but need to be retained. Be very careful if files dated as being old are deleted.

Most ( but not all ) users in Active Directory are roaming users which means their user profile on their workstation actually resides as a copy on the D:\Profiles share on the SuperServer. When a user logs off from their workstation, any file updates get copied to the SuperServer. Staff using laptops are not roaming users.

Office printers are shared from the SuperServer using a DNS hostname instead of an IP address. DONT use an IP address to share a printer. Both 32bit and 64bit drivers are installed for each shared printer. Try not to use generic universal print drivers, especially for copiers. Print driver isolation should also be turned on for all print drivers to protect the print spooler from crashing on badly coded print drivers.

All files on all volumes are backed up to tape Monday to Friday nights starting at midnight. Monthly backups also contain all files and those tapes are not recycled.

==Changes==
* On 04-05-21 AaronT replaced the file permissions on the folder , DC supervisors book. Inherited permissions were all removed and the folder was given allow permissions to the security group DC Supervisors, and Deny to the group non supervisors, Full Control to Management and Domain Admins.

[[Category: Servers - Hardware]]
[[Category: IBM System x Servers]]

Information Systems:SuperServer

2021-05-04T20:26:08Z

Aaront:

SuperServer is the file and print server used by all staff. All user created files such as Word or Excel files need to be saved on the SuperServer. All of the office area laser printers and copiers are shared from SuperServer.

The OS on this machine is Windows Server 2008R2. The file and print server role is the only role that is installed on SuperServer. The C: drive on the SuperServer only contains the OS and small applications for monitoring and controlling the RAID hardware and emailing of faxes. The D: and E: drives are used for file storage. Both the D: and E: have Shadow Copies turned on with a 100GB limit and the Shadow Copy service is on a schedule running every 2 hours from 7AM to 6PM daily. The Shadow Copy service is set to take a snapshot every 2 hours starting at 7AM and stop at 5PM. Please note that most if not all Cryptolocker malware is able to delete Shadow Copy snapshots.

The structure of the shared folders is either by department or by general function. Permissions are applied through Active Directory groups with either read or modify permissions. The "messiness" of the shared folders is mostly under control but there is room for improvement. There are very large numbers of files that are not used or opened but need to be retained. Be very careful if files dated as being old are deleted.

Most ( but not all ) users in Active Directory are roaming users which means their user profile on their workstation actually resides as a copy on the D:\Profiles share on the SuperServer. When a user logs off from their workstation, any file updates get copied to the SuperServer. Staff using laptops are not roaming users.

Office printers are shared from the SuperServer using a DNS hostname instead of an IP address. DONT use an IP address to share a printer. Both 32bit and 64bit drivers are installed for each shared printer. Try not to use generic universal print drivers, especially for copiers. Print driver isolation should also be turned on for all print drivers to protect the print spooler from crashing on badly coded print drivers.

All files on all volumes are backed up to tape Monday to Friday nights starting at midnight. Monthly backups also contain all files and those tapes are not recycled.

* On 04-05-21 AaronT replaced the file permissions on the folder , DC supervisors book. Inherited permissions were all removed and the folder was given allow permissions to the security group DC Supervisors, and Deny to the group non supervisors, Full Control to Management and Domain Admins. *

[[Category: Servers - Hardware]]
[[Category: IBM System x Servers]]

Information Systems:Remote Desktop Gateway

2021-04-28T23:23:13Z

Aaront:

Remote Desktop Gateway

Developed Spring 2020 due to COVID WFH

lives on DC1

rmtgw.unipharm.com

UNIPHARM\username

password

Information Systems:Remote Desktop Gateway

2021-04-28T23:23:00Z

Aaront:

Remote Desktop Gateway

Developed Spring 2020 due to COVID WFH

lives on DC1

rmtgw.unipharm.com

UNIPHARM\username
password

Information Systems:Remote Desktop Gateway

2021-04-28T20:34:14Z

Aaront:

Remote Desktop Gateway

Developed Spring 2020 due to COVID WFH

lives on DC1

rmtgw.unipharm.com

Information Systems:Setting up an IBM i printer

2021-04-26T22:35:25Z

Aaront: /* Set device up in JetForm */

==Steps==
===Configure basic printer settings===
* Unbox, power on, and network the device.
* Access the web GUI, fill out device information (name, location, SNMP).
* Set static IP and other network settings (DNS, gateway etc.). Use an IP within the range for printers (check DNS server or do a network scan). Use Colosoft to scan the network for acceptable IP range. Confirm selection of IP address with nslookup. Leave Netmask and gateway unchanged.
* Give the device a hostname, using the convention (check DNS server for current printer names).
* Register the hostname in DNS (domain controllers, or MMC).

===Set device up as a printer on Lucy===
* Printers that will be used primarily for IBM i printing (i.e. invoice printers) need to be defined on lucy.unipharm.local, as that is where JetForm is installed). Define a printer share here. Follow the naming convention for the device/printer/share name because IBM i has a 10-character limit.

===Set device up as an IBM i network printer===
* Follow IBM i instructions for setting up a printer as a '''device description''' (of type 3812). This should be done using the CRTDEVD command. Important parameters to note are the manufacturer type/model, the host name, and device description type etc. [https://www.ibm.com/support/pages/information-printers-lexmark This page] will indicate which printer protocol to use, most likely IPP or SNMP (this page is for Lexmark but there are similar pages for other printer manufacturers).
* Remember to vary on the device and start the printer writer (STRPRTWTR ''printer name'').
* Test print from IBM i using WRKSPLF and changing the printer on a 1-pager. You may receive a QSYSOPR message such as this when trying to print, in which case you can reply with 'I' to ignore.
Load form type '*STD' device L90INV22A writer L90INV22A.

===Set device up as an ASW printer===
* Log in to ASW.
* Go to System Management -> System setup -> Printer control tasks -> Work with Jetform printers.
* F6 to add, enter the device name as configured everywhere else (the 10-character-limit name).

===Set device up in JetForm===
remote into lucy1
open jetforms under file|management|add a printer
add the printer.

===Add printer in RF print control table===
unity|start unipharm extensions|VA company|50 warehouse menu|80 IT MENU | 50 update printer control

[[Category: IBM i]]
[[Category: Printing]]

Information Systems:Setting up an IBM i printer

2021-04-26T22:33:28Z

Aaront: /* Add printer in RF print control table */

==Steps==
===Configure basic printer settings===
* Unbox, power on, and network the device.
* Access the web GUI, fill out device information (name, location, SNMP).
* Set static IP and other network settings (DNS, gateway etc.). Use an IP within the range for printers (check DNS server or do a network scan). Use Colosoft to scan the network for acceptable IP range. Confirm selection of IP address with nslookup. Leave Netmask and gateway unchanged.
* Give the device a hostname, using the convention (check DNS server for current printer names).
* Register the hostname in DNS (domain controllers, or MMC).

===Set device up as a printer on Lucy===
* Printers that will be used primarily for IBM i printing (i.e. invoice printers) need to be defined on lucy.unipharm.local, as that is where JetForm is installed). Define a printer share here. Follow the naming convention for the device/printer/share name because IBM i has a 10-character limit.

===Set device up as an IBM i network printer===
* Follow IBM i instructions for setting up a printer as a '''device description''' (of type 3812). This should be done using the CRTDEVD command. Important parameters to note are the manufacturer type/model, the host name, and device description type etc. [https://www.ibm.com/support/pages/information-printers-lexmark This page] will indicate which printer protocol to use, most likely IPP or SNMP (this page is for Lexmark but there are similar pages for other printer manufacturers).
* Remember to vary on the device and start the printer writer (STRPRTWTR ''printer name'').
* Test print from IBM i using WRKSPLF and changing the printer on a 1-pager. You may receive a QSYSOPR message such as this when trying to print, in which case you can reply with 'I' to ignore.
Load form type '*STD' device L90INV22A writer L90INV22A.

===Set device up as an ASW printer===
* Log in to ASW.
* Go to System Management -> System setup -> Printer control tasks -> Work with Jetform printers.
* F6 to add, enter the device name as configured everywhere else (the 10-character-limit name).

===Set device up in JetForm===

===Add printer in RF print control table===
unity|start unipharm extensions|VA company|50 warehouse menu|80 IT MENU | 50 update printer control

[[Category: IBM i]]
[[Category: Printing]]

Information Systems:Printers And Picking Stations In The DC

2021-04-26T21:45:54Z

Aaront: /* Recommendations For Future Improvement */

Information about printers should be moved to these two articles:
[[Information Systems:Zebra Thermal printers |Zebra Thermal Printers]]
[[Information Systems:Workgroup Laser Printers |Workgroup Laser Printers]]

Info about picking stations can remain in this article.
==Production Printer Fleet Totals==
For an updated list, please refer to [[Information_Systems:Workgroup_Laser_Printers |this article]]
* Lexmark MS415 invoice printer - 1
* Lexmark T650 invoice printers - 8
* Lexmark T640 invoice printers - 2
* Lexmark T630 invoice printers - 1
* Zebra S4M direct thermal label printers - 20
* Zebra 2746e label printers - 4 plus 1 using a ribbon for a total of 5
* Zebra small label printers - 1(GX420t) 1(LP2242) 1(TLP2742) 1(TLP2844) in Returns and Receiving

==Ready Spares Printer Fleet Totals==
* Lexmark MS521 ready for deployment- need RF control testing :1
* Lexmark MS521 windows print ready:1
* Lexmark T650 spare invoice printers - 1
* Lexmark T640 spare invoice printers - 1
* Lexmark T630 spare invoice printers - 0
* Zebra S4M ready spare - 4

==Production Picking Stations==
* OTC picking station has 1 Lexmark T650 and 2 Zebra S4M all connected via parallel cable to an HP print box
* HABA picking stations has 1 Lexmark T650 and 2 Zebra S4M all connected via parallel cable to an HP print box
* LargeDown picking station has 1 Lexmark T650 and 2 Zebra S4M all connected via parallel cable to an HP print box
* Lower90s picking station has 1 Lexmark T650 and 2 Zebra S4M all connected via parallel cable to an HP print box
* Pharmies picking station has 1 Lexmark T650 and 2 Zebra S4M all connected via parallel cable to an HP print box
* HomeHealthCare picking station has 1 Lexmark T650 and 2 Zebra S4M all connected via parallel cable to an HP print box
* FridgeArea picking station has 1 Lexmark T640 and 2 Zebra S4M all connected via parallel cable to an HP print box
* NarcCage picking station has 1 Lexmark MS415 and 2 Zebra S4M all connected via parallel cable to an HP print box (Lexmark MS410 also network attached)
* Candy picking station has 1 Lexmark T640 and 2 Zebra S4M all connected via parallel cable to an HP print box
* SalesArea picking station has 1 Lexmark T650 and 2 Zebra 2746e all connected via parallel cable to an HP print box
* TobaccoArea picking station has 1 Lexmark T630 and 2 Zebra 2746e all connected via parallel cable to an HP print box (yes they still pick here)

==Other Laser Printer Or Label Printers In The DC==
* Mail slots desk in shipping has a Zebra S4M connected to an HP print box
* DC Supervisors office has a Zebra 2746e connected to a Lexmark print box under the desk using a ribbon to print shelf labels
* The cold chain receiving workstation in Receiving has a Zebra TLP 2844 connected via parallel cable to print item labels
* The desktop that JeffP uses has a parallel cable attached Zebra LP2242 used to print item labels
* The desktop that DexterG uses has a parallel cable attached Zebra TLP2742 used to print item labels
* There is a network attached Zebra GX420t label printer that BarryF uses for item labels
* Under the mezzanine in Receiving there is a Zebra S4M attached to an HP print box that is used to print license plates

==Recommendations For Future Improvement==
* According to Gerald if the Buyers moved items out of the "Tobacco Area" into some other spot in the warehouse then we could take the printers from that picking station and make them spares- this was done
* License plate label printer in Receiving may not need to be there because any S4M can print license plates
* The high traffic picking stations have network cabling that can be used to network attach printers without the use of a HP print box, but tracing and terminating those network cables doesn't happen instantaneously.
* Something think about is that Zebra has industrial spec label printers similar to the S4M that can connect via wifi which would greatly simplify the cabling mess in the DC
* If we are to use the Lexmark MS521 printers then we have to have the corresponding cable termination supplies and tools
* Pictures (some blurry) of all the printers mentioned on this page are available on the SuperServer in Tech\Common

==Links To Other Printer Wiki Pages==
* Mobile_belt_printers[[http://elearning.unipharm.local:8080/mediawiki/index.php/Information_Systems:Mobile_belt_printers]]
* Lexmark_printers[[http://elearning.unipharm.local:8080/mediawiki/index.php/Information_Systems:Lexmark_printers]]
* Xerox_printers[[http://elearning.unipharm.local:8080/mediawiki/index.php/Information_Systems:Xerox_printers]]
* Zebra_Thermal_printers[[http://elearning.unipharm.local:8080/mediawiki/index.php/Information_Systems:Zebra_Thermal_printers]]

==Changelog==
* This page is current as of July 2, 2019
* If an invoice printer fails to print , check lucy1 and the print manager for the spooler ,services to make sure they are running.
[[Category:Printing]]

Information Systems:Printers And Picking Stations In The DC

2021-04-26T21:44:51Z

Aaront: /* Ready Spares Printer Fleet Totals */

Information about printers should be moved to these two articles:
[[Information Systems:Zebra Thermal printers |Zebra Thermal Printers]]
[[Information Systems:Workgroup Laser Printers |Workgroup Laser Printers]]

Info about picking stations can remain in this article.
==Production Printer Fleet Totals==
For an updated list, please refer to [[Information_Systems:Workgroup_Laser_Printers |this article]]
* Lexmark MS415 invoice printer - 1
* Lexmark T650 invoice printers - 8
* Lexmark T640 invoice printers - 2
* Lexmark T630 invoice printers - 1
* Zebra S4M direct thermal label printers - 20
* Zebra 2746e label printers - 4 plus 1 using a ribbon for a total of 5
* Zebra small label printers - 1(GX420t) 1(LP2242) 1(TLP2742) 1(TLP2844) in Returns and Receiving

==Ready Spares Printer Fleet Totals==
* Lexmark MS521 ready for deployment- need RF control testing :1
* Lexmark MS521 windows print ready:1
* Lexmark T650 spare invoice printers - 1
* Lexmark T640 spare invoice printers - 1
* Lexmark T630 spare invoice printers - 0
* Zebra S4M ready spare - 4

==Production Picking Stations==
* OTC picking station has 1 Lexmark T650 and 2 Zebra S4M all connected via parallel cable to an HP print box
* HABA picking stations has 1 Lexmark T650 and 2 Zebra S4M all connected via parallel cable to an HP print box
* LargeDown picking station has 1 Lexmark T650 and 2 Zebra S4M all connected via parallel cable to an HP print box
* Lower90s picking station has 1 Lexmark T650 and 2 Zebra S4M all connected via parallel cable to an HP print box
* Pharmies picking station has 1 Lexmark T650 and 2 Zebra S4M all connected via parallel cable to an HP print box
* HomeHealthCare picking station has 1 Lexmark T650 and 2 Zebra S4M all connected via parallel cable to an HP print box
* FridgeArea picking station has 1 Lexmark T640 and 2 Zebra S4M all connected via parallel cable to an HP print box
* NarcCage picking station has 1 Lexmark MS415 and 2 Zebra S4M all connected via parallel cable to an HP print box (Lexmark MS410 also network attached)
* Candy picking station has 1 Lexmark T640 and 2 Zebra S4M all connected via parallel cable to an HP print box
* SalesArea picking station has 1 Lexmark T650 and 2 Zebra 2746e all connected via parallel cable to an HP print box
* TobaccoArea picking station has 1 Lexmark T630 and 2 Zebra 2746e all connected via parallel cable to an HP print box (yes they still pick here)

==Other Laser Printer Or Label Printers In The DC==
* Mail slots desk in shipping has a Zebra S4M connected to an HP print box
* DC Supervisors office has a Zebra 2746e connected to a Lexmark print box under the desk using a ribbon to print shelf labels
* The cold chain receiving workstation in Receiving has a Zebra TLP 2844 connected via parallel cable to print item labels
* The desktop that JeffP uses has a parallel cable attached Zebra LP2242 used to print item labels
* The desktop that DexterG uses has a parallel cable attached Zebra TLP2742 used to print item labels
* There is a network attached Zebra GX420t label printer that BarryF uses for item labels
* Under the mezzanine in Receiving there is a Zebra S4M attached to an HP print box that is used to print license plates

==Recommendations For Future Improvement==
* According to Gerald if the Buyers moved items out of the "Tobacco Area" into some other spot in the warehouse then we could take the printers from that picking station and make them spares
* License plate label printer in Receiving may not need to be there because any S4M can print license plates
* The high traffic picking stations have network cabling that can be used to network attach printers without the use of a HP print box, but tracing and terminating those network cables doesn't happen instantaneously.
* Something think about is that Zebra has industrial spec label printers similar to the S4M that can connect via wifi which would greatly simplify the cabling mess in the DC
* If we are to use the Lexmark MS521 printers then we have to have the corresponding cable termination supplies and tools
* Pictures (some blurry) of all the printers mentioned on this page are available on the SuperServer in Tech\Common

==Links To Other Printer Wiki Pages==
* Mobile_belt_printers[[http://elearning.unipharm.local:8080/mediawiki/index.php/Information_Systems:Mobile_belt_printers]]
* Lexmark_printers[[http://elearning.unipharm.local:8080/mediawiki/index.php/Information_Systems:Lexmark_printers]]
* Xerox_printers[[http://elearning.unipharm.local:8080/mediawiki/index.php/Information_Systems:Xerox_printers]]
* Zebra_Thermal_printers[[http://elearning.unipharm.local:8080/mediawiki/index.php/Information_Systems:Zebra_Thermal_printers]]

==Changelog==
* This page is current as of July 2, 2019
* If an invoice printer fails to print , check lucy1 and the print manager for the spooler ,services to make sure they are running.
[[Category:Printing]]

Information Systems:Microsoft 365 Exchange Online - Setup and Configuration

2021-04-26T18:14:18Z

Aaront: /* SPF */

==Overview==
This wiki page attempts to document and discuss major topics of Exchange setup and configuration. This will be a mix of design/strategy talk and some how-tos for technical administration. Ultimately, another page should be made to adapt the information discussed here into more concise technical instructions for specific administration tasks.

==Mailboxes==
Users are essentially mailboxes in Exchange i.e. there is no Users section. In Exchange Online, a mailbox shows up when a user is created in 365 Admin Center.

===Shared Mailboxes===
Like groups/lists, shared mailboxes are communal to a group of users. But unlike groups/lists, they are actual mailboxes that accumulate mail. The company requires a few of these:
* Accounts Payable: accountspayable@unipharm.com
* Accounts Receivable: accountsreceivable@unipharm.com
* EDI Support: edisupport@unipharm.com
* Customer Service Voicemail: csvm@unipharm.com

====Adding a shared mailbox====
Given the limited number of shared mailboxes, and the company's particular use of them as mailbox "identities" rather than a communal email "sink", it has been decided to add shared mailboxes as separate accounts as opposed to opening them as additional mailboxes.

To add a shared mailbox:
* Remove any shared mailboxes previously opened as additional mailboxes (and not added as accounts).
* Perform the steps to add another email account (Office 365).
* Enter in the shared mailbox email.
* Instead of entering a password, click ''Sign in as another account''.
* Enter in the user's credentials. This will only work if the user has Full Access permissions to the shared mailbox (do this in EAC).

====Other methods====
The other ways of adding shared mailboxes are discussed here just for reference:

'''''Manually opening a shared mailbox'''''
:* In Outlook 2019, File -> Account Settings -> double-click account -> More Settings -> Advanced
:* In the Mailboxes section -> Add -> Enter exact Display Name of shared mailbox
:* Save/Apply

'''''Automapping'''''
:'''Note: Automapping has been disabled for all shared mailboxes.'''

:* Automapping is a feature that makes the shared mailboxes which a user has access to automatically visible in Outlook i.e. the shared mailboxes are automatically mapped to the user. This is enabled by default. There are implications:
::* Automapping lumps the data of shared mailboxes in the same OST file as the user's own mailbox. This is one of the reasons there is official documentation on how to disable automapping and [https://docs.microsoft.com/en-us/outlook/troubleshoot/profiles-and-accounts/remove-automapping-for-shared-mailbox how to reset an automapped Outlook configuration]. Considering the company's user base and computer/desktop assignments, this isn't expected to be a problem. But it's something to keep aware of. Imagine a case of 3 users that access 2 shared mailboxes ecah including their own, all logging in to the same computer with a 120GB SSD, with Outlook set to sync all mail. It is feasible for this to grow massively.
::* Automapping appears to be very finicky when mailbox delegation (permissions) are set to security groups instead of users. Discussion on the internet refers to having to reset permissions.

==Contacts and Groups==
===Contacts===
Contacts are non-Exchange users i.e. either external to the organization e.g. a shareholder store. For now, the primary use of contacts is the distribution lists. Unlike in the previous Lotus Notes system where these contacts were merely email addresses e.g. "strings", contacts in Exchange are "objects" and therefore have attributes like Company, First Name, Phone Number etc. This makes it feasible to have a directory of external contacts instead of just internal users.
====Shareholder email addresses====
Note: It is not yet a company policy to maintain an address book of individual shareholder emails in Exchange/Outlook. These contacts are maintained for the sake of the mailing lists.
In an attempt to maintain clean and consistent entries, several conventions have already been put into play, best depicted in the following example entry for the personal email associated with Marks Marine Pharmacy (the one that would go in the private/sensitive list). The Classic Exchange admin center is shown as it exposes more fields:
::[[File:2021-03-06 22_15_29-Edit Mail Contact.png|400px|border]]

Recommendations when creating new entries:
* If this contact/email will be used in private/confidential list only, prefix the Display Name with [Private]. Also, check the 'Hide contacts from the address list'. You may need to do this in Classic EAC.
* If this contact will be a member of both private and general/publicly-visible distribution lists, do not prefix the name.

===Groups===
{{quote|03/31/2021 - Take these docs with a grain of salt, there's a lot of changes right now}}
The term groups in Exchange is encompassing of distribution lists and security groups (permissions). There are 4 types of Exchange groups. The two used primarily are ''Distribution list'' groups and ''Mail security'' groups. The former is equivalent to the idea of a conventional mailing list, wherein an email sent to the group address is distributed to its members. The latter is used for assigning permissions.
====Distribution Lists====
* The email address convention for department-based groups (and most other groups) is ''department''group@unipharm.com
* The following is an example of a configured group. The manager has been specified as a group owner in addition to IT to enable self-management.
::[[File:2021-03-06 14_41_32-Exchange admin center.png|300px|border]]
* Some groups are meant to be internal (e.g IT group), while others are meant to also be addressable by users outside the organization (e.g. Returns). Check related permissions and set up aliases accordingly. For example, Returns group follows the convention returnsgroup@unpharm.com, but it is logical to have '''returns@unipharm.com''' as an alias, as this is a more common format for a public-facing contact email address (same as customerservice@unipharm.com).
::[[File:2021-03-06 14_58_33-Exchange admin center.png|200px|border]]

====Shareholder mailing lists====
There exist several mailing lists for correspondence with shareholders and associate members. Refer to the Contacts section above for how shareholder email addresses are maintained.

====Sensitive mailing lists====
A few of the distribution lists are for sending confidential information to shareholders and associate members, and therefore have the 'Specified senders' permissons set. The option to prevent these lists and their constituent contacts from being displayed in the global address book should also be checked. The ability to hide contacts from address lists appears to currently be available only in the Classic admin center:
::[[File:2021-03-06 16_53_57-Edit Mail Contact.png|400px|border]]
====Other group types====
* '''Microsoft 365 groups''' have additional functionality to enable better collaboration for the group's members. The company currently does not collaborate in such a fashion for these to be useful (e.g. no Sharepoint, no Teams, no shared folders on cloud storage).
* '''Dynamic distribution list''' is a good concept on paper as it allows distribution lists to be "self-adjusting" based on attributes e.g. a Customer Service list could be set up to include any users with the Department attribute set to Customer Service. However, it was tested to have one major showstopping limitation - the dynamic nature of the list (recipients determined at the time of send) means it is not possible to view members of that list (neither in Outlook when trying to send to the list, or in the admin console). Not being able to see the recipients severely limits its usefulness, and therefore, setting up dynamic lists was forgone as an endeavor to potentially ease contact group administration.
====Nested groups====
'''A word of caution regarding nested groups.'''

Nesting groups within other groups generally makes sense when it comes to permissions. This is especially true with Microsoft AD, where object hierarchy and the concept of RBAC are predominant (a user can be assigned one or more roles, which grants them the specific set of permissions associated with those roles). However, issues have been encountered with group nesting during setup, primarily related to "trying to get too fancy". The ultimate goal was to have permissions and group membership dynamically assigned based on attribute e.g. the user's department. This was found to not even be remotely achievable in Exchange. These general rules of thumb have been surmised from experimentation with group nesting:

* Nesting like group types appears to work. Distribution lists groups are ok to nest within other distribution list groups. The same goes for mail security groups.
* Nesting security groups can lead to some quirks, but is still recommended. For example, nested security groups seems to break shared mailbox automapping and ownership.
* Distribution list groups should not be nested within security groups (see point #1).

TL;DR - exercise caution when using group nesting, and assign permissions to users as a fallback (troubleshoot later).

==Address Book==
With Exchange address books, there exists two types of implementations: out-of-the-box or address book policies. This fork on the road comes early; either accept the out of the box functionality and do nothing else, or enter the world of address book policy routing and accept the more complex management. This of course depends on the needs of the company, and we needed and decided on the latter. This path also requires PowerShell (no options or visibility exists in EAC, besides the ability to assign an existing policy (created with PowerShell) to a user).

===Address book policies===
An address book policy allows you to customize what a user sees, from the sublists, to the contacts viewable in those sublists. For example, the default address book policy has the following address lists: All Groups, All Users, All Distribution Lists etc. It is both unintuitive if you are not fully invested in the Microsoft way. For example, we don't use Microsoft groups, so All Groups is empty, and what we know as groups are actually, Distribution Lists. All Users, on the other hand, contains staff, but also shared mailboxes and resources (Projector, iPad), but not rooms. To make even one customization to all of this, ABPs are needed.

* ABP routing is an Exchange flag that has been enabled for our domain.
* An address book policy specifies the following:
: * 1 x '''Global Address List (GAL)''' - contains all objects (mailboxes, contacts, rooms etc.) that a user is able to "see". An ABP is linked to 1 GAL and therefore a user can only see 1 GAL.
: * 1 x '''Offline Address Book (OAB)''' - specifies one or more address lists to download/cache. To make it more confusing, the Offline Address Book behaves more like an address list.
: * 1 x '''Room Address List'''
: * 1 or more custom (or built-in) '''Address Lists''' - Address Lists are groupings that are subsetted from the GAL. For example, the built-in All Rooms address list filters for GAL objects where the ObjectType is RoomMailbox (not quite, but something to that effect).

Again, all these are created/set in PowerShell.

====Current address book policies====
There are two ABPs (default still exists but is not meant to be used).

{| class="wikitable"
|-
! Address Book Policy !! Global Address List !! Offline Address Book -> Offline Address List !! Room List !! Address Lists !! Notes
|-
| Staff Address Book Policy || Staff Global Address List || Staff Offline Address Book -> Offline Address List (Staff) || Rooms and Resources || Company Contacts, Distribution Lists, Staff, Public Folders || Should be the default assigned to staff members.
|-
| Executive Address Book Policy || Executive Global Address List || Executive Offline Address Book -> Offline Address List (Executive) || Rooms and Resources || Company Contacts, Company Contacts (Executive), Distribution Lists, Distribution Lists (Executive), Staff, Public Folders || Can see what staff see, and the private lists/contacts.
|}

''Congrats if you're still following at this point.''

====Address Lists and Filtering====
The usefuleness of address book policies lies in filtering (inclusion filtering), which is used to produce address lists. This is a big topic and is mostly PowerShell talk. Therefore, this is left for official technical docs, but provided are two examples to try and explain the concept:
* The address list '''Distribution Lists (Executive)''' specifies a filter that translates to:
:Include only objects where:
::* ObjectClass equals 'group'
::* DisplayName is like '*(Private)'
* The address list '''Staff''' specifies a filter that translates to:
::Include only objects where:
::* ObjectCategory equals 'person' AND 'user'
::* RecipientType does not equal 'RoomMailbox'
::* RecipientType does not equal 'EquipmentMailbox'

''These are not the exact filters used, they're meant to explain the concept only.''

====Relationship between contact management and ABPs====
It should be noted that contacts, groups, and group membership are not affected by address book policies. ABPs only affect what a user sees in the address book. A not-good analogy: you can take out pages of a phone directory and group them differently or put stickers over some entries so they're not visible (ABPs), but you don't change what's printed in the directory (that's contact management).

==Mail flow and mail rules==
===Connectors===
Because mail hosting for unipharm.com is spread over 2 servers, configuring Exchange "connectors" is necessary to properly route mail to and from MDaemon (the on-prem mail server). This is a complex topic and should be described on another page.

==Email security==
Email security is handled by Exchange Online Protection, a feature that comes with all Exchange Online / 365 accounts. It "sits" before the mail routing/delivery process - for both inbound and outbound mail flows - and checks messages for threats and spam. The policies determine what gets detected as spam/threats and the outcome of those messages. Depending on if the new or classic admin portal is being used, there are various areas to configure or tweak these policies:
:* In Classic Admin Center, these policies are found in the '''protection''' section.
:* In New Admin Center, these policies are found in a separate '''Security and Compliance''' Admin Center altogether, under '''Threat management'''.

===Malware policies===
* Email servers do a fairly good job detecting and blocking viruses in emails, silently. As an organization, we also don't deal with attachment types (.exe, audio/video containers etc.) that are normally flagged as viruses. Therefore, these policies have not been changed from the defaults.

===Spam policies===
* Unlike spam-handling pre-Exchange that involved a user quarantine, the current spam policy is set to direct spam to a user's junk folder.
:[[File:2021-03-30 15_50_03-edit spam filter policy.png|400px]]

====Spam scoring====
There are two scores related to spam-handling: SCL (Spam Confidence Level), and BCL (Bulk Complaint Level). The Bulk Complaint Level threshold can be set, but the SCL appears to be set (at least for Exchange Online). These values are 5 (spam) and 9 (high-confidence spam), according to [https://docs.microsoft.com/en-us/microsoft-365/security/office-365-security/spam-confidence-levels?view=o365-worldwide the docs]

Note: These scores are present in the message headers, and have been validated to make it all the way to MDaemon (in messages destined for non-Exchange mailboxes). Therefore, we could potentially capitalize on the spam and bulk scoring done by EOP by having MDaemon recognize and act on these headers.

===Phishing===
Phishing remains the greatest threat when it comes to email security. Without Advanced Threat Prection (additional cost on top of EOP), we rely on reputation-based and heuristic-based detection mechanisms of the email security service (EOP) to flag emails that contain phishing content. Barracuda did a fantastic job (very low penetration from empirical evidence). It remains to be seen how EOP handles these types of "attacks" (they come in waves).

==Security/AAA==
===Custom Admin Roles===
Exchange allows for the creation of custom admin roles that have a specific combination of permissions. For example, the Company Directory Management role was created to allow users to manage the address book:
::[[File:2021-03-23 11_58_18-Exchange admin center.png|400px]]

===Password policies===
* Password expiry has been disabled in 365 from the 90-day default:
::[[File:2021-03-23 12_14_04-Microsoft 365 admin center.png|border|400px]]
* Self-service password resets have been enabled in Azure AD. Users will be notified when they reset their passwords:
::[[File:2021-03-23 12_21_01-Password reset - Azure Active Directory admin center.png|400px|border]][[File:2021-03-23 12_23_00-Password reset - Azure Active Directory admin center.png|400px|border]]
* (Update this section with info on password management strategy when it gets discussed)

==Other Notes==
* Microsoft is currently transitioning from what they're now terming Classic Exchange admin center to the New Exchange admin center. Some options remain editable only in the old portal.

==SPF==
SPF has been enabled, https://docs.microsoft.com/en-us/microsoft-365/security/office-365-security/set-up-spf-in-office-365-to-help-prevent-spoofing?view=o365-worldwide,
Using a company like mxtoolbox, we can put in the email that we want to check the SPF record for and see how it is set.
::[[File:mtoolboxupipharmspf.png]]

Information Systems:Microsoft 365 Exchange Online - Setup and Configuration

2021-04-26T18:10:03Z

Aaront: /* SPF */

File:mtoolboxupipharmspf.png

2021-04-26T18:02:15Z

Aaront:

Information Systems:Microsoft 365 Exchange Online - Setup and Configuration

2021-04-26T17:56:59Z

Aaront: /* Other Notes */

Information Systems:Microsoft 365 Exchange Online - Setup and Configuration

2021-04-26T17:56:11Z

Aaront: /* Other Notes */

==Overview==
This wiki page attempts to document and discuss major topics of Exchange setup and configuration. This will be a mix of design/strategy talk and some how-tos for technical administration. Ultimately, another page should be made to adapt the information discussed here into more concise technical instructions for specific administration tasks.

==Mailboxes==
Users are essentially mailboxes in Exchange i.e. there is no Users section. In Exchange Online, a mailbox shows up when a user is created in 365 Admin Center.

===Shared Mailboxes===
Like groups/lists, shared mailboxes are communal to a group of users. But unlike groups/lists, they are actual mailboxes that accumulate mail. The company requires a few of these:
* Accounts Payable: accountspayable@unipharm.com
* Accounts Receivable: accountsreceivable@unipharm.com
* EDI Support: edisupport@unipharm.com
* Customer Service Voicemail: csvm@unipharm.com

====Adding a shared mailbox====
Given the limited number of shared mailboxes, and the company's particular use of them as mailbox "identities" rather than a communal email "sink", it has been decided to add shared mailboxes as separate accounts as opposed to opening them as additional mailboxes.

To add a shared mailbox:
* Remove any shared mailboxes previously opened as additional mailboxes (and not added as accounts).
* Perform the steps to add another email account (Office 365).
* Enter in the shared mailbox email.
* Instead of entering a password, click ''Sign in as another account''.
* Enter in the user's credentials. This will only work if the user has Full Access permissions to the shared mailbox (do this in EAC).

====Other methods====
The other ways of adding shared mailboxes are discussed here just for reference:

'''''Manually opening a shared mailbox'''''
:* In Outlook 2019, File -> Account Settings -> double-click account -> More Settings -> Advanced
:* In the Mailboxes section -> Add -> Enter exact Display Name of shared mailbox
:* Save/Apply

'''''Automapping'''''
:'''Note: Automapping has been disabled for all shared mailboxes.'''

:* Automapping is a feature that makes the shared mailboxes which a user has access to automatically visible in Outlook i.e. the shared mailboxes are automatically mapped to the user. This is enabled by default. There are implications:
::* Automapping lumps the data of shared mailboxes in the same OST file as the user's own mailbox. This is one of the reasons there is official documentation on how to disable automapping and [https://docs.microsoft.com/en-us/outlook/troubleshoot/profiles-and-accounts/remove-automapping-for-shared-mailbox how to reset an automapped Outlook configuration]. Considering the company's user base and computer/desktop assignments, this isn't expected to be a problem. But it's something to keep aware of. Imagine a case of 3 users that access 2 shared mailboxes ecah including their own, all logging in to the same computer with a 120GB SSD, with Outlook set to sync all mail. It is feasible for this to grow massively.
::* Automapping appears to be very finicky when mailbox delegation (permissions) are set to security groups instead of users. Discussion on the internet refers to having to reset permissions.

==Contacts and Groups==
===Contacts===
Contacts are non-Exchange users i.e. either external to the organization e.g. a shareholder store. For now, the primary use of contacts is the distribution lists. Unlike in the previous Lotus Notes system where these contacts were merely email addresses e.g. "strings", contacts in Exchange are "objects" and therefore have attributes like Company, First Name, Phone Number etc. This makes it feasible to have a directory of external contacts instead of just internal users.
====Shareholder email addresses====
Note: It is not yet a company policy to maintain an address book of individual shareholder emails in Exchange/Outlook. These contacts are maintained for the sake of the mailing lists.
In an attempt to maintain clean and consistent entries, several conventions have already been put into play, best depicted in the following example entry for the personal email associated with Marks Marine Pharmacy (the one that would go in the private/sensitive list). The Classic Exchange admin center is shown as it exposes more fields:
::[[File:2021-03-06 22_15_29-Edit Mail Contact.png|400px|border]]

Recommendations when creating new entries:
* If this contact/email will be used in private/confidential list only, prefix the Display Name with [Private]. Also, check the 'Hide contacts from the address list'. You may need to do this in Classic EAC.
* If this contact will be a member of both private and general/publicly-visible distribution lists, do not prefix the name.

===Groups===
{{quote|03/31/2021 - Take these docs with a grain of salt, there's a lot of changes right now}}
The term groups in Exchange is encompassing of distribution lists and security groups (permissions). There are 4 types of Exchange groups. The two used primarily are ''Distribution list'' groups and ''Mail security'' groups. The former is equivalent to the idea of a conventional mailing list, wherein an email sent to the group address is distributed to its members. The latter is used for assigning permissions.
====Distribution Lists====
* The email address convention for department-based groups (and most other groups) is ''department''group@unipharm.com
* The following is an example of a configured group. The manager has been specified as a group owner in addition to IT to enable self-management.
::[[File:2021-03-06 14_41_32-Exchange admin center.png|300px|border]]
* Some groups are meant to be internal (e.g IT group), while others are meant to also be addressable by users outside the organization (e.g. Returns). Check related permissions and set up aliases accordingly. For example, Returns group follows the convention returnsgroup@unpharm.com, but it is logical to have '''returns@unipharm.com''' as an alias, as this is a more common format for a public-facing contact email address (same as customerservice@unipharm.com).
::[[File:2021-03-06 14_58_33-Exchange admin center.png|200px|border]]

====Shareholder mailing lists====
There exist several mailing lists for correspondence with shareholders and associate members. Refer to the Contacts section above for how shareholder email addresses are maintained.

====Sensitive mailing lists====
A few of the distribution lists are for sending confidential information to shareholders and associate members, and therefore have the 'Specified senders' permissons set. The option to prevent these lists and their constituent contacts from being displayed in the global address book should also be checked. The ability to hide contacts from address lists appears to currently be available only in the Classic admin center:
::[[File:2021-03-06 16_53_57-Edit Mail Contact.png|400px|border]]
====Other group types====
* '''Microsoft 365 groups''' have additional functionality to enable better collaboration for the group's members. The company currently does not collaborate in such a fashion for these to be useful (e.g. no Sharepoint, no Teams, no shared folders on cloud storage).
* '''Dynamic distribution list''' is a good concept on paper as it allows distribution lists to be "self-adjusting" based on attributes e.g. a Customer Service list could be set up to include any users with the Department attribute set to Customer Service. However, it was tested to have one major showstopping limitation - the dynamic nature of the list (recipients determined at the time of send) means it is not possible to view members of that list (neither in Outlook when trying to send to the list, or in the admin console). Not being able to see the recipients severely limits its usefulness, and therefore, setting up dynamic lists was forgone as an endeavor to potentially ease contact group administration.
====Nested groups====
'''A word of caution regarding nested groups.'''

Nesting groups within other groups generally makes sense when it comes to permissions. This is especially true with Microsoft AD, where object hierarchy and the concept of RBAC are predominant (a user can be assigned one or more roles, which grants them the specific set of permissions associated with those roles). However, issues have been encountered with group nesting during setup, primarily related to "trying to get too fancy". The ultimate goal was to have permissions and group membership dynamically assigned based on attribute e.g. the user's department. This was found to not even be remotely achievable in Exchange. These general rules of thumb have been surmised from experimentation with group nesting:

* Nesting like group types appears to work. Distribution lists groups are ok to nest within other distribution list groups. The same goes for mail security groups.
* Nesting security groups can lead to some quirks, but is still recommended. For example, nested security groups seems to break shared mailbox automapping and ownership.
* Distribution list groups should not be nested within security groups (see point #1).

TL;DR - exercise caution when using group nesting, and assign permissions to users as a fallback (troubleshoot later).

==Address Book==
With Exchange address books, there exists two types of implementations: out-of-the-box or address book policies. This fork on the road comes early; either accept the out of the box functionality and do nothing else, or enter the world of address book policy routing and accept the more complex management. This of course depends on the needs of the company, and we needed and decided on the latter. This path also requires PowerShell (no options or visibility exists in EAC, besides the ability to assign an existing policy (created with PowerShell) to a user).

===Address book policies===
An address book policy allows you to customize what a user sees, from the sublists, to the contacts viewable in those sublists. For example, the default address book policy has the following address lists: All Groups, All Users, All Distribution Lists etc. It is both unintuitive if you are not fully invested in the Microsoft way. For example, we don't use Microsoft groups, so All Groups is empty, and what we know as groups are actually, Distribution Lists. All Users, on the other hand, contains staff, but also shared mailboxes and resources (Projector, iPad), but not rooms. To make even one customization to all of this, ABPs are needed.

* ABP routing is an Exchange flag that has been enabled for our domain.
* An address book policy specifies the following:
: * 1 x '''Global Address List (GAL)''' - contains all objects (mailboxes, contacts, rooms etc.) that a user is able to "see". An ABP is linked to 1 GAL and therefore a user can only see 1 GAL.
: * 1 x '''Offline Address Book (OAB)''' - specifies one or more address lists to download/cache. To make it more confusing, the Offline Address Book behaves more like an address list.
: * 1 x '''Room Address List'''
: * 1 or more custom (or built-in) '''Address Lists''' - Address Lists are groupings that are subsetted from the GAL. For example, the built-in All Rooms address list filters for GAL objects where the ObjectType is RoomMailbox (not quite, but something to that effect).

Again, all these are created/set in PowerShell.

====Current address book policies====
There are two ABPs (default still exists but is not meant to be used).

{| class="wikitable"
|-
! Address Book Policy !! Global Address List !! Offline Address Book -> Offline Address List !! Room List !! Address Lists !! Notes
|-
| Staff Address Book Policy || Staff Global Address List || Staff Offline Address Book -> Offline Address List (Staff) || Rooms and Resources || Company Contacts, Distribution Lists, Staff, Public Folders || Should be the default assigned to staff members.
|-
| Executive Address Book Policy || Executive Global Address List || Executive Offline Address Book -> Offline Address List (Executive) || Rooms and Resources || Company Contacts, Company Contacts (Executive), Distribution Lists, Distribution Lists (Executive), Staff, Public Folders || Can see what staff see, and the private lists/contacts.
|}

''Congrats if you're still following at this point.''

====Address Lists and Filtering====
The usefuleness of address book policies lies in filtering (inclusion filtering), which is used to produce address lists. This is a big topic and is mostly PowerShell talk. Therefore, this is left for official technical docs, but provided are two examples to try and explain the concept:
* The address list '''Distribution Lists (Executive)''' specifies a filter that translates to:
:Include only objects where:
::* ObjectClass equals 'group'
::* DisplayName is like '*(Private)'
* The address list '''Staff''' specifies a filter that translates to:
::Include only objects where:
::* ObjectCategory equals 'person' AND 'user'
::* RecipientType does not equal 'RoomMailbox'
::* RecipientType does not equal 'EquipmentMailbox'

''These are not the exact filters used, they're meant to explain the concept only.''

====Relationship between contact management and ABPs====
It should be noted that contacts, groups, and group membership are not affected by address book policies. ABPs only affect what a user sees in the address book. A not-good analogy: you can take out pages of a phone directory and group them differently or put stickers over some entries so they're not visible (ABPs), but you don't change what's printed in the directory (that's contact management).

==Mail flow and mail rules==
===Connectors===
Because mail hosting for unipharm.com is spread over 2 servers, configuring Exchange "connectors" is necessary to properly route mail to and from MDaemon (the on-prem mail server). This is a complex topic and should be described on another page.

==Email security==
Email security is handled by Exchange Online Protection, a feature that comes with all Exchange Online / 365 accounts. It "sits" before the mail routing/delivery process - for both inbound and outbound mail flows - and checks messages for threats and spam. The policies determine what gets detected as spam/threats and the outcome of those messages. Depending on if the new or classic admin portal is being used, there are various areas to configure or tweak these policies:
:* In Classic Admin Center, these policies are found in the '''protection''' section.
:* In New Admin Center, these policies are found in a separate '''Security and Compliance''' Admin Center altogether, under '''Threat management'''.

===Malware policies===
* Email servers do a fairly good job detecting and blocking viruses in emails, silently. As an organization, we also don't deal with attachment types (.exe, audio/video containers etc.) that are normally flagged as viruses. Therefore, these policies have not been changed from the defaults.

===Spam policies===
* Unlike spam-handling pre-Exchange that involved a user quarantine, the current spam policy is set to direct spam to a user's junk folder.
:[[File:2021-03-30 15_50_03-edit spam filter policy.png|400px]]

====Spam scoring====
There are two scores related to spam-handling: SCL (Spam Confidence Level), and BCL (Bulk Complaint Level). The Bulk Complaint Level threshold can be set, but the SCL appears to be set (at least for Exchange Online). These values are 5 (spam) and 9 (high-confidence spam), according to [https://docs.microsoft.com/en-us/microsoft-365/security/office-365-security/spam-confidence-levels?view=o365-worldwide the docs]

Note: These scores are present in the message headers, and have been validated to make it all the way to MDaemon (in messages destined for non-Exchange mailboxes). Therefore, we could potentially capitalize on the spam and bulk scoring done by EOP by having MDaemon recognize and act on these headers.

===Phishing===
Phishing remains the greatest threat when it comes to email security. Without Advanced Threat Prection (additional cost on top of EOP), we rely on reputation-based and heuristic-based detection mechanisms of the email security service (EOP) to flag emails that contain phishing content. Barracuda did a fantastic job (very low penetration from empirical evidence). It remains to be seen how EOP handles these types of "attacks" (they come in waves).

==Security/AAA==
===Custom Admin Roles===
Exchange allows for the creation of custom admin roles that have a specific combination of permissions. For example, the Company Directory Management role was created to allow users to manage the address book:
::[[File:2021-03-23 11_58_18-Exchange admin center.png|400px]]

===Password policies===
* Password expiry has been disabled in 365 from the 90-day default:
::[[File:2021-03-23 12_14_04-Microsoft 365 admin center.png|border|400px]]
* Self-service password resets have been enabled in Azure AD. Users will be notified when they reset their passwords:
::[[File:2021-03-23 12_21_01-Password reset - Azure Active Directory admin center.png|400px|border]][[File:2021-03-23 12_23_00-Password reset - Azure Active Directory admin center.png|400px|border]]
* (Update this section with info on password management strategy when it gets discussed)

==Other Notes==
* Microsoft is currently transitioning from what they're now terming Classic Exchange admin center to the New Exchange admin center. Some options remain editable only in the old portal.

==SPF has been enabled, https://docs.microsoft.com/en-us/microsoft-365/security/office-365-security/set-up-spf-in-office-365-to-help-prevent-spoofing?view=o365-worldwide,
Using a company like mxtoolbox, we can put in the email that we want to check the SPF record for and see how it is set.

Information Systems:Outlook and Exchange - Tips for Staff

2021-04-26T16:27:09Z

Aaront:

=Tips=
==Enable From: and BCC: fields==
* Create new email
* Go to Options tab
* Select From and BCC. These settings are enabled permanently thereafter.
:[[File:2021-03-30 22_32_27-Untitled - Message (HTML).png|300px|thumb| Only BCC is shown here, but you will likely have the From option as well.]]

==Alternate navigation pane==
The navigation pane to toggle between Mail, Calendar, Contacts has icons by default. Change these to words:
* Click ellipses (3 dots, as shown below) in the navigation screen (bottom left of the screen):
:[[File:2021-03-30 22_38_48-Inbox - norwinu@unipharm.com - Outlook.png|300px|thumb]]
* Select ''Navigation Options''.
* Un-check Compact Navigation. Save.
:[[File:2021-03-30 22_40_28-Inbox - norwinu@unipharm.com - Outlook.png|300px|thumb]]

==The elusive List view in Calendar==
Unlike in Notes, viewing the calendar as a list of events is not amongst the other quick toggles e.g. Day/Week/Month. However, it can be found in Change View:

==Scheduled Delivery==
Finished an email but don't want to send it just yet, but also don't want to forget? Use the '''Delay Delivery''' feature, in the Options tab when creating an email
:[[File:2021-03-30 22_57_33-Untitled - Message (HTML).png|300px|thumb]]
Use this to schedule Away notices to staff, or scheduling an email at the start of the next business day so it doesn't get lost in the backlog ;)

:[[File:2021-03-30 22_47_47-uniPHARM IS Operations Calendar - Internet Calendars - Outlook.png|300px]]

==Recover deleted items from the server==
If you deleted a message and then emptied your Trash (''Deleted Items'' in Outlook) folder, there is a last resort / bailout. Navigate to the Deleted Items folder, and the ''Recover Deleted Items from Server'' option should appear at the top:
:[[File:2021-03-30 22_57_33-Untitled - Message (HTML).png|300px|thumb]]

==Archive rather than delete==
Deleting emails should be done by choice, not to keep within quota. While a limit does still exist (50GB), this is on average 10-100x more than your previous mail quota.

==Email signatures do not take up==

==Templates or Saved Drafts==
In lotus notes folks used a lot of templates or pre made emails containing specific information that is used over and over. In order to do this in outlook, one way is to create a new email with all the required information and saving the email to the desktop.

Another way is to create a template email and create a shortcut to the template on the desktop or somewhere the user is familiar with.

Information Systems:Workstation UPS

2021-04-24T18:25:40Z

Aaront: /* Notes */

Many staff have a small UPS for their workstation. The models vary, and some serve multiple computers. Most are non-smart devices with no network presence.

==Inventory==
{| class="wikitable sortable"
|-
! User !! Location !! Model !! Date of last battery replacement !! Notes
|-
| Scanning PC 2 || Receiving Office || APC Back-UPS 1500 RS || 2020-05 || -
|-
| Customer Service || RavinderA desk || APC Smart 750 XL || 2020-05 || -
|-
|AaronT Workstation || - || Example || N/A || -
|-
|Returns-PC-1 || - || || ||-
|-
|Returns-PC-2 || - || || || -
|-
|Promo-PC2 || - || || || -

|}

==Notes==
* Free management software should be installed on each workstation with a UPS (and connected via USB). To date, this has never been done.

There is software configured on the customer service UPS and is a great example of how to setup the rest.
[[Category: Power, Alarms, and Monitoring]]