uniWIKI - User contributions [en]

Information Systems:Zabbix NMS

2022-10-24T21:21:11Z

Anmolm:

==Overview==
Zabbix is an open source software package installed on a Linux operating system or used as a pre-built virtual machine appliance. The software's purpose is to monitor and display primarily SNMP statistics from network switches or any network attached hardware that speaks SNMP. At uniPHARM, we are using Zabbix to gain a lot of visibility on to what is happening on our network switch infrastructure. Zabbix can query each network port on each network switch and read all of the available statistics such as packets in/out or ping time or bandwidth usage and a hundred other metrics. Zabbix can display all those ports, functions and numbers as graphs so that humans can see if there is a bottleneck or some other problem. Zabbix does have some logic built in that makes choices on what it thinks is an existing problem. For example, if a port on switch has a large number of errors or a port's bandwidth is pegged at maximum or even if a port is unplugged, it will generate an alert on the Zabbix dashboard and wait for somebody to act on it. Unfortunately, Zabbix is not able to make configuration changes on the switches directly so keep in mind that Zabbix is a "network monitoring server" and not a "network management server".

* http://zabbix.unipharm.local/zabbix
* Username is admin
* Password is zabbix
* As of July 19 2019, AD logins are working but the above credentials are superior than an AD login. The Linux appliance username is "appliance".

The design of the Zabbix web interface does take a little getting used to. When not making any configuration changes to how Zabbix queries network attached hardware, stick to the "Monitoring" tab in the top left corner of the site. Within Monitoring you will be able to see one or more dashboards and a dedicated page for any listed Problems. You can also go to the Graphs tab and look and all the possible graphs by changing the group, host and graph drop down boxes. The Graphs tab is really the prime rib of the Zabbix application because the stat data can be presented in graphs that can go back as far as 2 years or 2 hours so trend lines can be visualsed easily.

The "Screens" tab is also extremely useful because it contains pre-built ... screens that show groups of graphs that are relevant together instead of individually. For example, one of the screens shows network traffic in/out plus errors on all of the wireless access points at uniPHARM. This shows which AP's have the most activity and shows what time of day that activity happens. The "Maps" tab shows a Visio style graphical layout of the network. Obviously its not as good as Visio but for an OSS web based mapper, its pretty good. Try and keep these diagrams current and up to date because they will be helpful should I.S. staff get hit by a bus at any time.

The object organization in Zabbix is also a little tricky to understand. There is a hierarchy which starts with "Host Groups" in the "Configuration" tab. A Host Group can contain one or more hosts plus one or more Templates. A template in Zabbix is ... a way of interpreting SNMP data. A template that correctly displays SNMP data from a Cisco switch is going to be different than a template that reads Juniper switch SNMP data. Luckily, most of the major hardware brands are included in Zabbix and there is also a bunch of generics that can also be used. Once you create a Host Group and assigned a Template you can create a Host. This is the part where Zabbix fails to be convenient. It's automatic network discovery function doesn't work and you have to manually create each network object. Yes, this is very time consuming and not convenient. In the Host creation step you can either use SNMP or the Zabbix agent to query stats. The agent is a small program that can be installed on a physical server or a VM but SNMP is best used for anything that's hardware. Zabbix will start to query the newly created host right away and depending on what it is and what template was applied, there may be many items, graphs, apps and triggers created that all work together to present as much information as possible.

Zabbix has been configured to send out email alerts when certain conditions are present. For example, if a switch or access point is not pingable, then Zabbix will create a problem ticket and send an email. The built in templates also allow much more fine grained alerts but I have tried to group things together logically. The alert configuration is in the Configuration/Actions tab. Here alerts can be turned off or on or edited. Its important to understand that if for example, a switch or server loses power and then comes back up, the problem ticket that Zabbix generates will be closed by the automated resolution ticket because the state of the hardware returned to baseline normal. If Zabbix is alerting on something that is a false positive like a wonky fan tachometer or a bad temperature sensor, then what needs to happen is the "Trigger Item" in the Host configuration needs to be disabled. That will mute an alert if it is included in an alert package.

As mentioned above, network discovery in Zabbix, at least for switches and printers doesn't work in an obvious way - it might but I couldn't figure it out. Discovery of the VMware infrastructure does indeed work and infact it works a little too well. The Host groups get a little untidy with how Zabbix displays virtual machines because it is showing by cluster and then by host so individual guests show up twice. Anywho, as of July 2019, the config of how Zabbix displays and tracks statistic info from the VMHosts and from the guests is correct. There are some yummy graphs in the Screens section and those screen should show anyone all the info they would ever need to see what's happening on the infrastructure.

==Configuration==
===Linux and Windows Agent===
The Zabbix agent can be installed on Linux servers for resource monitoring. Our 2 current Linux server VMs (owl and uwdoss) are Debian-based, and therefore the zabbix-agent package is available in the apt repository. Zabbix also offers an agent for Windows, which is downloadable from their site. It is installed and run as a Windows service.

The configuration file is located in the following directory:
* Linux: /etc/zabbix/zabbix_agentd.conf
* Windows: C:\Program Files\Zabbix Agent 2\zabbix_agent2.conf

This file must be edited after installation for the agent to be able to communicate with the server. Refer to one to see a typical config.

The Zabbix agent on the client (or even the one that runs on the server for self-monitoring) can do more than self-monitor its hardware resources (CPU, memory, storage etc.). For example, the agent can monitor MySQL. The Linux servers do run MySQL (MariaDB) and therefore have been additionally configured to report on the local MySQL instance to Zabbix. Read official documentation on how this and other Zabbix agent extensions can be configured.

==Additional Notes==
===Documentation to-do===
* Zabbix configuration - /etc/zabbix/, number of pollers, unreachable pollers, SNMP monitors
* Templates - shared templates from community, difference between Zabbix templates and vendor MIBs
* Triggers
* Graphs
* Screens
===Zabbix Upgrade - March 2021===
Zabbix was upgraded from 4.2 to 5.2 (the latest version). This was its first ever upgrade -[[User:Norwinu|norwizzle]]. Some notes from the upgrade:

* The docs provide a sufficient guide, although Linux experience is required since Zabbix is a Linux-based appliance.
* The underlying OS of our appliance is Ubuntu. There are other Zabbix flavors.
* Zabbix 5.2 required PHP 7.2. Ubuntu was at version 16.04, which was too old and therefore the repository did not have an upgrade to PHP 7.2 available.
* Ubuntu had to be upgraded from 16.04 to 18.04. A general Ubuntu upgrade guide was followed. Caution should always be taken when performing a major OS upgrade. On the other hand, Zabbix was not being used much by anyone, so YOLO.
* And then...Zabbix did not start upon the post-upgrade system restart. Turns out the upgrade overrwrote zabbix_server.conf (I was cavalier during the debconf/apt diff process) and the php conf in web/ and the DB password was now blank. The upgrade did ask for confirmation regarding this change, but looking at the diff, the removal of the DB password line seemed reasonable. It wasn't reasonable. A new password was set using <code>mysql -u root</code> then <code>SET PASSWORD 'zabbix'@'localhost' = '<hidden>'</code> etc. Zabbix booted after that.

==Original notes==
Darren originally wrote this page. Some stuff has since been addressed, so his comments - as well as old sections - will be moved here for reference.

* Updating Zabbix. I don't know how to do this, so either leave the Linux appliance as is, which is safe, or do some command line advanced magic to do in place upgrades of the Zabbix ... files. Oh and there is some sort of sharing page on the public Zabbix site where new or customized templates are available, that may be helpful in the future if we are using hardware that isn't included by default. A lot of hours were put into getting Zabbix usable, please take care of it, at the very least take a snapshot before doing anything crazy so that you can revert back.

===Things Still To Do===
* Zabbix does apparently speak WMI to Windows machines but I could not figure out how to do this because the documentation is not great. It would be useful for Zabbix to get WMI info.
* Better map icons. The default icons that are available in Zabbix are very limited and don't make creating maps as easy as it could. There is a way to import more icons/shapes but I wasn't able to get that far
* External monitoring - this one appears to be super complicated but there may be potential for Zabbix to replace the 24x7 Zoho service we use. Of course the downside of that is that because Zabbix is a VM it is internal and dependent on everything else working to be able to properly monitor external sites. The extended thought is that Zabbix as a "thing" won't be able to alert on anything if either the VM hangs or the host it is on hangs or is otherwise down itself. Funny how we didn't build in that redundancy to the VMware environment.

[[Category: Power, Alarms, and Monitoring]]

Information Systems:LAN infrastructure at uniPHARM

2022-10-22T01:57:17Z

Anmolm:

==Overview==
This is the main page for the LAN (wired network configuration) at uniPHARM.

==Switches==
This table outlines the physical network switches that make up the network.

{| class="wikitable sortable"
|-
! Hostname !! IP address || Switch model !! Location !! Username !! Password !! Notes
|-
| '''coresw''' || 172.30.16.4 || Cisco CBS350 || Server room || adminit || Newvisionit21! || '''Core switch.''' Stack of 3.
|-
| atpsw || 172.30.16.3 || 3Com 4200 || Server room || admin || visionit || Feeds data to POE injectors for Mirador temp. sensors '''(Retired)'''
|-
| accountingsw || 172.30.16.11 || Cisco SG350-28P || Accounting Wallmount Network Rack || adminit || NewVisionIT || POE, ~175W power budget
|-
| buyerswcisco || 172.30.16.18 || Cisco SG350-28P || Buying department closet || adminit || visionit|| -
|-
| itsw || 172.30.16.6 || 3Com 4200G || IT department ceiling tile. Yup. || admin || visionis || -
|-
| cagesw || 172.30.16.12 || 3Com 3870 || Computer lab || admin || visionit
|-
| dumpsw.unipharm.local || 172.30.16.7 || 3Com 4200G? || Electrical Room? || admin || visionds || -
|-
| pickingsw || 172.30.16.8 || 3Com 3870? || Rx picking zone network rack || admin || visionps || -
|-
| receivingswcisco || 172.30.16.17 || Cisco SG350-28P || DC Manager's Office || adminit || visionit || -
|-
| wallsw || 172.30.16.9 || 3Com 4200G? || Candy Mezzanine || admin || visionns || Functions merely to bridge the physical wiring between Receiving area and core network
|-
| jeremymsw || 172.30.16.16 || TP-Link SG105E || Jeremy's office || admin || visionit || Used for testing Yealink, web-managed smart switch
|-
| itlabswcisco || 172.30.16.19 || Cisco SG350-10MP || IT Lab/Cage || adminit || visionit ||
|}

* External link to backdoor access and hidden menus for the 3com 3870 switches http://etherhack.wikia.com/wiki/3Com_3870
* There is a spare, ready to use 3com 3870 24 port switch located at the very bottom of the networking rack in the server room. The switch has been reset to factory defaults and the username is admin and the password is blank. The switch is ready to be put into the core stack if needed.

==VLANs==
We started using VLANs in 2016, for the same reason why anyone would use VLANs - to manage/separate multiple networks using one physical switch infrastructure. The VLAN implementation being used is the standard 802.1q. The following table outlines the VLAN infrastructure.

{| class="wikitable sortable"
|-
! VLAN ID !! Name !! L3 Network / IP Range !! Description !! Notes
|-
| '''1''' || Main LAN || 172.30.16.0/21 (172.30.16.1 - 172.30.23.255) || Default VLAN, untagged across the network for simplicity (so that every device doesn't have to be configured to talk this VLAN, or even be VLAN-aware at all). || Routed out Telus Fibre
|-
| '''2''' || Alt LAN (Staff/ guest BYOD, Shipping terminals) || 192.168.0.1/23 (192.168.0.1 - 192.168.1.254) || Colloquially known as the "Guest VLAN", but staff wifi devices are not technically guest devices. Currently, shipping computers are on this network, but they should be moved to VLAN 7 when it is created. || Routed out Shaw Business Internet
|-
| '''3''' || vMotion LAN || ?? || Small network to isolate vMotion traffic between the 3 virtual hosts. || -
|-
| '''4''' || Shaw WAN interfaces || Network of the Shaw static WAN IP (/32) || Network to isolate WAN traffic between Shaw modem and Sophos WAN interface from the rest of the network. Lots of ARP going on here! || -
|-
| '''5''' || Telus WAN interfaces || Network of our Telus WAN IPs (/27) || Network to isolate WAN traffic between Telus modem and Sophos WAN interface from the rest of the network. || -
|-
| '''6''' || VoIP LAN || 192.168.44.0/24 || Contains PBX and IP phones || Routed out Telus and Shaw (Sophos multipath)
|}

=Helpful Stuff=
The command to view what MAC address(s) is in use on a port for the Cisco SG350 switch is as follows. You will need to login to the switch via SSH in order to do this:
* show mac address-table interface gi1 (or ge1 sometimes too)
The port name is visible from the switches web interface and goes from gi1 to gi28 or ge1 to ge28. Then cross checking the MAC address in Spiceworks for example will allow you to see who is plugged into what port - however all the Cisco switches should already have human readable labels attached to all in-use ports as of July 2019.
[[Category: Networking]]

Information Systems:LAN infrastructure at uniPHARM

2022-10-20T22:15:20Z

Anmolm:

==Overview==
This is the main page for the LAN (wired network configuration) at uniPHARM.

==Switches==
This table outlines the physical network switches that make up the network.

{| class="wikitable sortable"
|-
! Hostname !! IP address || Switch model !! Location !! Username !! Password !! Notes
|-
| '''coresw''' || 172.30.16.4 || Cisco CBS350 || Server room || adminit || Newvisionit21! || '''Core switch.''' Stack of 3.
|-
| atpsw || 172.30.16.3 || 3Com 4200 || Server room || admin || visionit || Feeds data to POE injectors for Mirador temp. sensors '''(Retired)'''
|-
| accountingsw || 172.30.16.11 || Cisco SG350-28P || Accounting Wallmount Network Rack || adminit || visionit || POE, ~175W power budget
|-
| buyerswcisco || 172.30.16.18 || Cisco SG350-28P || Buying department closet || adminit || visionit|| -
|-
| itsw || 172.30.16.6 || 3Com 4200G || IT department ceiling tile. Yup. || admin || visionis || -
|-
| cagesw || 172.30.16.12 || 3Com 3870 || Computer lab || admin || visionit
|-
| dumpsw.unipharm.local || 172.30.16.7 || 3Com 4200G? || Electrical Room? || admin || visionds || -
|-
| pickingsw || 172.30.16.8 || 3Com 3870? || Rx picking zone network rack || admin || visionps || -
|-
| receivingswcisco || 172.30.16.17 || Cisco SG350-28P || DC Manager's Office || adminit || visionit || -
|-
| wallsw || 172.30.16.9 || 3Com 4200G? || Candy Mezzanine || admin || visionns || Functions merely to bridge the physical wiring between Receiving area and core network
|-
| jeremymsw || 172.30.16.16 || TP-Link SG105E || Jeremy's office || admin || visionit || Used for testing Yealink, web-managed smart switch
|-
| itlabswcisco || 172.30.16.19 || Cisco SG350-10MP || IT Lab/Cage || adminit || visionit ||
|}

* External link to backdoor access and hidden menus for the 3com 3870 switches http://etherhack.wikia.com/wiki/3Com_3870
* There is a spare, ready to use 3com 3870 24 port switch located at the very bottom of the networking rack in the server room. The switch has been reset to factory defaults and the username is admin and the password is blank. The switch is ready to be put into the core stack if needed.

==VLANs==
We started using VLANs in 2016, for the same reason why anyone would use VLANs - to manage/separate multiple networks using one physical switch infrastructure. The VLAN implementation being used is the standard 802.1q. The following table outlines the VLAN infrastructure.

{| class="wikitable sortable"
|-
! VLAN ID !! Name !! L3 Network / IP Range !! Description !! Notes
|-
| '''1''' || Main LAN || 172.30.16.0/21 (172.30.16.1 - 172.30.23.255) || Default VLAN, untagged across the network for simplicity (so that every device doesn't have to be configured to talk this VLAN, or even be VLAN-aware at all). || Routed out Telus Fibre
|-
| '''2''' || Alt LAN (Staff/ guest BYOD, Shipping terminals) || 192.168.0.1/23 (192.168.0.1 - 192.168.1.254) || Colloquially known as the "Guest VLAN", but staff wifi devices are not technically guest devices. Currently, shipping computers are on this network, but they should be moved to VLAN 7 when it is created. || Routed out Shaw Business Internet
|-
| '''3''' || vMotion LAN || ?? || Small network to isolate vMotion traffic between the 3 virtual hosts. || -
|-
| '''4''' || Shaw WAN interfaces || Network of the Shaw static WAN IP (/32) || Network to isolate WAN traffic between Shaw modem and Sophos WAN interface from the rest of the network. Lots of ARP going on here! || -
|-
| '''5''' || Telus WAN interfaces || Network of our Telus WAN IPs (/27) || Network to isolate WAN traffic between Telus modem and Sophos WAN interface from the rest of the network. || -
|-
| '''6''' || VoIP LAN || 192.168.44.0/24 || Contains PBX and IP phones || Routed out Telus and Shaw (Sophos multipath)
|}

=Helpful Stuff=
The command to view what MAC address(s) is in use on a port for the Cisco SG350 switch is as follows. You will need to login to the switch via SSH in order to do this:
* show mac address-table interface gi1 (or ge1 sometimes too)
The port name is visible from the switches web interface and goes from gi1 to gi28 or ge1 to ge28. Then cross checking the MAC address in Spiceworks for example will allow you to see who is plugged into what port - however all the Cisco switches should already have human readable labels attached to all in-use ports as of July 2019.
[[Category: Networking]]

Information Systems:LAN infrastructure at uniPHARM

2022-10-20T22:15:07Z

Anmolm:

==Overview==
This is the main page for the LAN (wired network configuration) at uniPHARM.

==Switches==
This table outlines the physical network switches that make up the network.

{| class="wikitable sortable"
|-
! Hostname !! IP address || Switch model !! Location !! Username !! Password !! Notes
|-
| '''coresw''' || 172.30.16.4 || Cisco CBS350 || Server room || adminit || Newvisionit21! || '''Core switch.''' Stack of 3.
|-
| atpsw || 172.30.16.3 || 3Com 4200 || Server room || admin || visionit || Feeds data to POE injectors for Mirador temp. sensors (Retired)
|-
| accountingsw || 172.30.16.11 || Cisco SG350-28P || Accounting Wallmount Network Rack || adminit || visionit || POE, ~175W power budget
|-
| buyerswcisco || 172.30.16.18 || Cisco SG350-28P || Buying department closet || adminit || visionit|| -
|-
| itsw || 172.30.16.6 || 3Com 4200G || IT department ceiling tile. Yup. || admin || visionis || -
|-
| cagesw || 172.30.16.12 || 3Com 3870 || Computer lab || admin || visionit
|-
| dumpsw.unipharm.local || 172.30.16.7 || 3Com 4200G? || Electrical Room? || admin || visionds || -
|-
| pickingsw || 172.30.16.8 || 3Com 3870? || Rx picking zone network rack || admin || visionps || -
|-
| receivingswcisco || 172.30.16.17 || Cisco SG350-28P || DC Manager's Office || adminit || visionit || -
|-
| wallsw || 172.30.16.9 || 3Com 4200G? || Candy Mezzanine || admin || visionns || Functions merely to bridge the physical wiring between Receiving area and core network
|-
| jeremymsw || 172.30.16.16 || TP-Link SG105E || Jeremy's office || admin || visionit || Used for testing Yealink, web-managed smart switch
|-
| itlabswcisco || 172.30.16.19 || Cisco SG350-10MP || IT Lab/Cage || adminit || visionit ||
|}

* External link to backdoor access and hidden menus for the 3com 3870 switches http://etherhack.wikia.com/wiki/3Com_3870
* There is a spare, ready to use 3com 3870 24 port switch located at the very bottom of the networking rack in the server room. The switch has been reset to factory defaults and the username is admin and the password is blank. The switch is ready to be put into the core stack if needed.

==VLANs==
We started using VLANs in 2016, for the same reason why anyone would use VLANs - to manage/separate multiple networks using one physical switch infrastructure. The VLAN implementation being used is the standard 802.1q. The following table outlines the VLAN infrastructure.

{| class="wikitable sortable"
|-
! VLAN ID !! Name !! L3 Network / IP Range !! Description !! Notes
|-
| '''1''' || Main LAN || 172.30.16.0/21 (172.30.16.1 - 172.30.23.255) || Default VLAN, untagged across the network for simplicity (so that every device doesn't have to be configured to talk this VLAN, or even be VLAN-aware at all). || Routed out Telus Fibre
|-
| '''2''' || Alt LAN (Staff/ guest BYOD, Shipping terminals) || 192.168.0.1/23 (192.168.0.1 - 192.168.1.254) || Colloquially known as the "Guest VLAN", but staff wifi devices are not technically guest devices. Currently, shipping computers are on this network, but they should be moved to VLAN 7 when it is created. || Routed out Shaw Business Internet
|-
| '''3''' || vMotion LAN || ?? || Small network to isolate vMotion traffic between the 3 virtual hosts. || -
|-
| '''4''' || Shaw WAN interfaces || Network of the Shaw static WAN IP (/32) || Network to isolate WAN traffic between Shaw modem and Sophos WAN interface from the rest of the network. Lots of ARP going on here! || -
|-
| '''5''' || Telus WAN interfaces || Network of our Telus WAN IPs (/27) || Network to isolate WAN traffic between Telus modem and Sophos WAN interface from the rest of the network. || -
|-
| '''6''' || VoIP LAN || 192.168.44.0/24 || Contains PBX and IP phones || Routed out Telus and Shaw (Sophos multipath)
|}

=Helpful Stuff=
The command to view what MAC address(s) is in use on a port for the Cisco SG350 switch is as follows. You will need to login to the switch via SSH in order to do this:
* show mac address-table interface gi1 (or ge1 sometimes too)
The port name is visible from the switches web interface and goes from gi1 to gi28 or ge1 to ge28. Then cross checking the MAC address in Spiceworks for example will allow you to see who is plugged into what port - however all the Cisco switches should already have human readable labels attached to all in-use ports as of July 2019.
[[Category: Networking]]

Information Systems:LAN infrastructure at uniPHARM

2022-10-20T22:12:35Z

Anmolm:

==Overview==
This is the main page for the LAN (wired network configuration) at uniPHARM.

==Switches==
This table outlines the physical network switches that make up the network.

{| class="wikitable sortable"
|-
! Hostname !! IP address || Switch model !! Location !! Username !! Password !! Notes
|-
| '''coresw''' || 172.30.16.2 || Cisco CBS350 || Server room || adminit || Newvisionit21! || '''Core switch.''' Stack of 3.
|-
| atpsw || 172.30.16.3 || 3Com 4200 || Server room || admin || visionit || Feeds data to POE injectors for Mirador temp. sensors (Retired)
|-
| accountingsw || 172.30.16.11 || Cisco SG350-28P || Accounting Wallmount Network Rack || adminit || visionit || POE, ~175W power budget
|-
| buyerswcisco || 172.30.16.18 || Cisco SG350-28P || Buying department closet || adminit || visionit|| -
|-
| itsw || 172.30.16.6 || 3Com 4200G || IT department ceiling tile. Yup. || admin || visionis || -
|-
| cagesw || 172.30.16.12 || 3Com 3870 || Computer lab || admin || visionit
|-
| dumpsw.unipharm.local || 172.30.16.7 || 3Com 4200G? || Electrical Room? || admin || visionds || -
|-
| pickingsw || 172.30.16.8 || 3Com 3870? || Rx picking zone network rack || admin || visionps || -
|-
| receivingswcisco || 172.30.16.17 || Cisco SG350-28P || DC Manager's Office || adminit || visionit || -
|-
| wallsw || 172.30.16.9 || 3Com 4200G? || Candy Mezzanine || admin || visionns || Functions merely to bridge the physical wiring between Receiving area and core network
|-
| jeremymsw || 172.30.16.16 || TP-Link SG105E || Jeremy's office || admin || visionit || Used for testing Yealink, web-managed smart switch
|-
| itlabswcisco || 172.30.16.19 || Cisco SG350-10MP || IT Lab/Cage || adminit || visionit ||
|}

* External link to backdoor access and hidden menus for the 3com 3870 switches http://etherhack.wikia.com/wiki/3Com_3870
* There is a spare, ready to use 3com 3870 24 port switch located at the very bottom of the networking rack in the server room. The switch has been reset to factory defaults and the username is admin and the password is blank. The switch is ready to be put into the core stack if needed.

==VLANs==
We started using VLANs in 2016, for the same reason why anyone would use VLANs - to manage/separate multiple networks using one physical switch infrastructure. The VLAN implementation being used is the standard 802.1q. The following table outlines the VLAN infrastructure.

{| class="wikitable sortable"
|-
! VLAN ID !! Name !! L3 Network / IP Range !! Description !! Notes
|-
| '''1''' || Main LAN || 172.30.16.0/21 (172.30.16.1 - 172.30.23.255) || Default VLAN, untagged across the network for simplicity (so that every device doesn't have to be configured to talk this VLAN, or even be VLAN-aware at all). || Routed out Telus Fibre
|-
| '''2''' || Alt LAN (Staff/ guest BYOD, Shipping terminals) || 192.168.0.1/23 (192.168.0.1 - 192.168.1.254) || Colloquially known as the "Guest VLAN", but staff wifi devices are not technically guest devices. Currently, shipping computers are on this network, but they should be moved to VLAN 7 when it is created. || Routed out Shaw Business Internet
|-
| '''3''' || vMotion LAN || ?? || Small network to isolate vMotion traffic between the 3 virtual hosts. || -
|-
| '''4''' || Shaw WAN interfaces || Network of the Shaw static WAN IP (/32) || Network to isolate WAN traffic between Shaw modem and Sophos WAN interface from the rest of the network. Lots of ARP going on here! || -
|-
| '''5''' || Telus WAN interfaces || Network of our Telus WAN IPs (/27) || Network to isolate WAN traffic between Telus modem and Sophos WAN interface from the rest of the network. || -
|-
| '''6''' || VoIP LAN || 192.168.44.0/24 || Contains PBX and IP phones || Routed out Telus and Shaw (Sophos multipath)
|}

=Helpful Stuff=
The command to view what MAC address(s) is in use on a port for the Cisco SG350 switch is as follows. You will need to login to the switch via SSH in order to do this:
* show mac address-table interface gi1 (or ge1 sometimes too)
The port name is visible from the switches web interface and goes from gi1 to gi28 or ge1 to ge28. Then cross checking the MAC address in Spiceworks for example will allow you to see who is plugged into what port - however all the Cisco switches should already have human readable labels attached to all in-use ports as of July 2019.
[[Category: Networking]]

Information Systems:LAN infrastructure at uniPHARM

2022-10-20T22:12:13Z

Anmolm:

==Overview==
This is the main page for the LAN (wired network configuration) at uniPHARM.

==Switches==
This table outlines the physical network switches that make up the network.

{| class="wikitable sortable"
|-
! Hostname !! IP address || Switch model !! Location !! Username !! Password !! Notes
|-
| '''coresw''' || 172.30.16.2 || Cisco CBS350 || Server room || adminit || Newvisionit21! || '''Core switch.''' Stack of 3.
|-
| atpsw || 172.30.16.3 || 3Com 4200 || Server room || admin || visionit || Feeds data to POE injectors for Mirador temp. sensors
|-
| accountingsw || 172.30.16.11 || Cisco SG350-28P || Accounting Wallmount Network Rack || adminit || visionit || POE, ~175W power budget
|-
| buyerswcisco || 172.30.16.18 || Cisco SG350-28P || Buying department closet || adminit || visionit|| -
|-
| itsw || 172.30.16.6 || 3Com 4200G || IT department ceiling tile. Yup. || admin || visionis || -
|-
| cagesw || 172.30.16.12 || 3Com 3870 || Computer lab || admin || visionit
|-
| dumpsw.unipharm.local || 172.30.16.7 || 3Com 4200G? || Electrical Room? || admin || visionds || -
|-
| pickingsw || 172.30.16.8 || 3Com 3870? || Rx picking zone network rack || admin || visionps || -
|-
| receivingswcisco || 172.30.16.17 || Cisco SG350-28P || DC Manager's Office || adminit || visionit || -
|-
| wallsw || 172.30.16.9 || 3Com 4200G? || Candy Mezzanine || admin || visionns || Functions merely to bridge the physical wiring between Receiving area and core network
|-
| jeremymsw || 172.30.16.16 || TP-Link SG105E || Jeremy's office || admin || visionit || Used for testing Yealink, web-managed smart switch
|-
| itlabswcisco || 172.30.16.19 || Cisco SG350-10MP || IT Lab/Cage || adminit || visionit ||
|}

* External link to backdoor access and hidden menus for the 3com 3870 switches http://etherhack.wikia.com/wiki/3Com_3870
* There is a spare, ready to use 3com 3870 24 port switch located at the very bottom of the networking rack in the server room. The switch has been reset to factory defaults and the username is admin and the password is blank. The switch is ready to be put into the core stack if needed.

==VLANs==
We started using VLANs in 2016, for the same reason why anyone would use VLANs - to manage/separate multiple networks using one physical switch infrastructure. The VLAN implementation being used is the standard 802.1q. The following table outlines the VLAN infrastructure.

{| class="wikitable sortable"
|-
! VLAN ID !! Name !! L3 Network / IP Range !! Description !! Notes
|-
| '''1''' || Main LAN || 172.30.16.0/21 (172.30.16.1 - 172.30.23.255) || Default VLAN, untagged across the network for simplicity (so that every device doesn't have to be configured to talk this VLAN, or even be VLAN-aware at all). || Routed out Telus Fibre
|-
| '''2''' || Alt LAN (Staff/ guest BYOD, Shipping terminals) || 192.168.0.1/23 (192.168.0.1 - 192.168.1.254) || Colloquially known as the "Guest VLAN", but staff wifi devices are not technically guest devices. Currently, shipping computers are on this network, but they should be moved to VLAN 7 when it is created. || Routed out Shaw Business Internet
|-
| '''3''' || vMotion LAN || ?? || Small network to isolate vMotion traffic between the 3 virtual hosts. || -
|-
| '''4''' || Shaw WAN interfaces || Network of the Shaw static WAN IP (/32) || Network to isolate WAN traffic between Shaw modem and Sophos WAN interface from the rest of the network. Lots of ARP going on here! || -
|-
| '''5''' || Telus WAN interfaces || Network of our Telus WAN IPs (/27) || Network to isolate WAN traffic between Telus modem and Sophos WAN interface from the rest of the network. || -
|-
| '''6''' || VoIP LAN || 192.168.44.0/24 || Contains PBX and IP phones || Routed out Telus and Shaw (Sophos multipath)
|}

=Helpful Stuff=
The command to view what MAC address(s) is in use on a port for the Cisco SG350 switch is as follows. You will need to login to the switch via SSH in order to do this:
* show mac address-table interface gi1 (or ge1 sometimes too)
The port name is visible from the switches web interface and goes from gi1 to gi28 or ge1 to ge28. Then cross checking the MAC address in Spiceworks for example will allow you to see who is plugged into what port - however all the Cisco switches should already have human readable labels attached to all in-use ports as of July 2019.
[[Category: Networking]]

Information Systems:LAN infrastructure at uniPHARM

2022-10-20T22:12:03Z

Anmolm:

==Overview==
This is the main page for the LAN (wired network configuration) at uniPHARM.

==Switches==
This table outlines the physical network switches that make up the network.

{| class="wikitable sortable"
|-
! Hostname !! IP address || Switch model !! Location !! Username !! Password !! Notes
|-
| '''coresw''' || 172.30.16.2 || Cisco CBS350 || Server room || adminit || Newvisionit21! || '''Core switch.''' Stack of 4.
|-
| atpsw || 172.30.16.3 || 3Com 4200 || Server room || admin || visionit || Feeds data to POE injectors for Mirador temp. sensors
|-
| accountingsw || 172.30.16.11 || Cisco SG350-28P || Accounting Wallmount Network Rack || adminit || visionit || POE, ~175W power budget
|-
| buyerswcisco || 172.30.16.18 || Cisco SG350-28P || Buying department closet || adminit || visionit|| -
|-
| itsw || 172.30.16.6 || 3Com 4200G || IT department ceiling tile. Yup. || admin || visionis || -
|-
| cagesw || 172.30.16.12 || 3Com 3870 || Computer lab || admin || visionit
|-
| dumpsw.unipharm.local || 172.30.16.7 || 3Com 4200G? || Electrical Room? || admin || visionds || -
|-
| pickingsw || 172.30.16.8 || 3Com 3870? || Rx picking zone network rack || admin || visionps || -
|-
| receivingswcisco || 172.30.16.17 || Cisco SG350-28P || DC Manager's Office || adminit || visionit || -
|-
| wallsw || 172.30.16.9 || 3Com 4200G? || Candy Mezzanine || admin || visionns || Functions merely to bridge the physical wiring between Receiving area and core network
|-
| jeremymsw || 172.30.16.16 || TP-Link SG105E || Jeremy's office || admin || visionit || Used for testing Yealink, web-managed smart switch
|-
| itlabswcisco || 172.30.16.19 || Cisco SG350-10MP || IT Lab/Cage || adminit || visionit ||
|}

* External link to backdoor access and hidden menus for the 3com 3870 switches http://etherhack.wikia.com/wiki/3Com_3870
* There is a spare, ready to use 3com 3870 24 port switch located at the very bottom of the networking rack in the server room. The switch has been reset to factory defaults and the username is admin and the password is blank. The switch is ready to be put into the core stack if needed.

==VLANs==
We started using VLANs in 2016, for the same reason why anyone would use VLANs - to manage/separate multiple networks using one physical switch infrastructure. The VLAN implementation being used is the standard 802.1q. The following table outlines the VLAN infrastructure.

{| class="wikitable sortable"
|-
! VLAN ID !! Name !! L3 Network / IP Range !! Description !! Notes
|-
| '''1''' || Main LAN || 172.30.16.0/21 (172.30.16.1 - 172.30.23.255) || Default VLAN, untagged across the network for simplicity (so that every device doesn't have to be configured to talk this VLAN, or even be VLAN-aware at all). || Routed out Telus Fibre
|-
| '''2''' || Alt LAN (Staff/ guest BYOD, Shipping terminals) || 192.168.0.1/23 (192.168.0.1 - 192.168.1.254) || Colloquially known as the "Guest VLAN", but staff wifi devices are not technically guest devices. Currently, shipping computers are on this network, but they should be moved to VLAN 7 when it is created. || Routed out Shaw Business Internet
|-
| '''3''' || vMotion LAN || ?? || Small network to isolate vMotion traffic between the 3 virtual hosts. || -
|-
| '''4''' || Shaw WAN interfaces || Network of the Shaw static WAN IP (/32) || Network to isolate WAN traffic between Shaw modem and Sophos WAN interface from the rest of the network. Lots of ARP going on here! || -
|-
| '''5''' || Telus WAN interfaces || Network of our Telus WAN IPs (/27) || Network to isolate WAN traffic between Telus modem and Sophos WAN interface from the rest of the network. || -
|-
| '''6''' || VoIP LAN || 192.168.44.0/24 || Contains PBX and IP phones || Routed out Telus and Shaw (Sophos multipath)
|}

=Helpful Stuff=
The command to view what MAC address(s) is in use on a port for the Cisco SG350 switch is as follows. You will need to login to the switch via SSH in order to do this:
* show mac address-table interface gi1 (or ge1 sometimes too)
The port name is visible from the switches web interface and goes from gi1 to gi28 or ge1 to ge28. Then cross checking the MAC address in Spiceworks for example will allow you to see who is plugged into what port - however all the Cisco switches should already have human readable labels attached to all in-use ports as of July 2019.
[[Category: Networking]]

Information Systems:LAN infrastructure at uniPHARM

2022-10-20T22:11:28Z

Anmolm:

==Overview==
This is the main page for the LAN (wired network configuration) at uniPHARM.

==Switches==
This table outlines the physical network switches that make up the network.

{| class="wikitable sortable"
|-
! Hostname !! IP address || Switch model !! Location !! Username !! Password !! Notes
|-
| '''coresw''' || 172.30.16.2 || Cisco CBS350 || Server room || admin || visionit || '''Core switch.''' Stack of 4.
|-
| atpsw || 172.30.16.3 || 3Com 4200 || Server room || admin || visionit || Feeds data to POE injectors for Mirador temp. sensors
|-
| accountingsw || 172.30.16.11 || Cisco SG350-28P || Accounting Wallmount Network Rack || adminit || visionit || POE, ~175W power budget
|-
| buyerswcisco || 172.30.16.18 || Cisco SG350-28P || Buying department closet || adminit || visionit|| -
|-
| itsw || 172.30.16.6 || 3Com 4200G || IT department ceiling tile. Yup. || admin || visionis || -
|-
| cagesw || 172.30.16.12 || 3Com 3870 || Computer lab || admin || visionit
|-
| dumpsw.unipharm.local || 172.30.16.7 || 3Com 4200G? || Electrical Room? || admin || visionds || -
|-
| pickingsw || 172.30.16.8 || 3Com 3870? || Rx picking zone network rack || admin || visionps || -
|-
| receivingswcisco || 172.30.16.17 || Cisco SG350-28P || DC Manager's Office || adminit || visionit || -
|-
| wallsw || 172.30.16.9 || 3Com 4200G? || Candy Mezzanine || admin || visionns || Functions merely to bridge the physical wiring between Receiving area and core network
|-
| jeremymsw || 172.30.16.16 || TP-Link SG105E || Jeremy's office || admin || visionit || Used for testing Yealink, web-managed smart switch
|-
| itlabswcisco || 172.30.16.19 || Cisco SG350-10MP || IT Lab/Cage || adminit || visionit ||
|}

* External link to backdoor access and hidden menus for the 3com 3870 switches http://etherhack.wikia.com/wiki/3Com_3870
* There is a spare, ready to use 3com 3870 24 port switch located at the very bottom of the networking rack in the server room. The switch has been reset to factory defaults and the username is admin and the password is blank. The switch is ready to be put into the core stack if needed.

==VLANs==
We started using VLANs in 2016, for the same reason why anyone would use VLANs - to manage/separate multiple networks using one physical switch infrastructure. The VLAN implementation being used is the standard 802.1q. The following table outlines the VLAN infrastructure.

{| class="wikitable sortable"
|-
! VLAN ID !! Name !! L3 Network / IP Range !! Description !! Notes
|-
| '''1''' || Main LAN || 172.30.16.0/21 (172.30.16.1 - 172.30.23.255) || Default VLAN, untagged across the network for simplicity (so that every device doesn't have to be configured to talk this VLAN, or even be VLAN-aware at all). || Routed out Telus Fibre
|-
| '''2''' || Alt LAN (Staff/ guest BYOD, Shipping terminals) || 192.168.0.1/23 (192.168.0.1 - 192.168.1.254) || Colloquially known as the "Guest VLAN", but staff wifi devices are not technically guest devices. Currently, shipping computers are on this network, but they should be moved to VLAN 7 when it is created. || Routed out Shaw Business Internet
|-
| '''3''' || vMotion LAN || ?? || Small network to isolate vMotion traffic between the 3 virtual hosts. || -
|-
| '''4''' || Shaw WAN interfaces || Network of the Shaw static WAN IP (/32) || Network to isolate WAN traffic between Shaw modem and Sophos WAN interface from the rest of the network. Lots of ARP going on here! || -
|-
| '''5''' || Telus WAN interfaces || Network of our Telus WAN IPs (/27) || Network to isolate WAN traffic between Telus modem and Sophos WAN interface from the rest of the network. || -
|-
| '''6''' || VoIP LAN || 192.168.44.0/24 || Contains PBX and IP phones || Routed out Telus and Shaw (Sophos multipath)
|}

=Helpful Stuff=
The command to view what MAC address(s) is in use on a port for the Cisco SG350 switch is as follows. You will need to login to the switch via SSH in order to do this:
* show mac address-table interface gi1 (or ge1 sometimes too)
The port name is visible from the switches web interface and goes from gi1 to gi28 or ge1 to ge28. Then cross checking the MAC address in Spiceworks for example will allow you to see who is plugged into what port - however all the Cisco switches should already have human readable labels attached to all in-use ports as of July 2019.
[[Category: Networking]]

Information Systems:LAN infrastructure at uniPHARM

2022-10-20T22:10:38Z

Anmolm:

==Overview==
This is the main page for the LAN (wired network configuration) at uniPHARM.

==Switches==
This table outlines the physical network switches that make up the network.

{| class="wikitable sortable"
|-
! Hostname !! IP address || Switch model !! Location !! Username !! Password !! Notes
|-
| '''coresw''' || 172.30.16.2 || 3Com 3870 || Server room || admin || visionit || '''Core switch.''' Stack of 4.
|-
| atpsw || 172.30.16.3 || 3Com 4200 || Server room || admin || visionit || Feeds data to POE injectors for Mirador temp. sensors
|-
| accountingsw || 172.30.16.11 || Cisco SG350-28P || Accounting Wallmount Network Rack || adminit || visionit || POE, ~175W power budget
|-
| buyerswcisco || 172.30.16.18 || Cisco SG350-28P || Buying department closet || adminit || visionit|| -
|-
| itsw || 172.30.16.6 || 3Com 4200G || IT department ceiling tile. Yup. || admin || visionis || -
|-
| cagesw || 172.30.16.12 || 3Com 3870 || Computer lab || admin || visionit
|-
| dumpsw.unipharm.local || 172.30.16.7 || 3Com 4200G? || Electrical Room? || admin || visionds || -
|-
| pickingsw || 172.30.16.8 || 3Com 3870? || Rx picking zone network rack || admin || visionps || -
|-
| receivingswcisco || 172.30.16.17 || Cisco SG350-28P || DC Manager's Office || adminit || visionit || -
|-
| wallsw || 172.30.16.9 || 3Com 4200G? || Candy Mezzanine || admin || visionns || Functions merely to bridge the physical wiring between Receiving area and core network
|-
| jeremymsw || 172.30.16.16 || TP-Link SG105E || Jeremy's office || admin || visionit || Used for testing Yealink, web-managed smart switch
|-
| itlabswcisco || 172.30.16.19 || Cisco SG350-10MP || IT Lab/Cage || adminit || visionit ||
|}

* External link to backdoor access and hidden menus for the 3com 3870 switches http://etherhack.wikia.com/wiki/3Com_3870
* There is a spare, ready to use 3com 3870 24 port switch located at the very bottom of the networking rack in the server room. The switch has been reset to factory defaults and the username is admin and the password is blank. The switch is ready to be put into the core stack if needed.

==VLANs==
We started using VLANs in 2016, for the same reason why anyone would use VLANs - to manage/separate multiple networks using one physical switch infrastructure. The VLAN implementation being used is the standard 802.1q. The following table outlines the VLAN infrastructure.

{| class="wikitable sortable"
|-
! VLAN ID !! Name !! L3 Network / IP Range !! Description !! Notes
|-
| '''1''' || Main LAN || 172.30.16.0/21 (172.30.16.1 - 172.30.23.255) || Default VLAN, untagged across the network for simplicity (so that every device doesn't have to be configured to talk this VLAN, or even be VLAN-aware at all). || Routed out Telus Fibre
|-
| '''2''' || Alt LAN (Staff/ guest BYOD, Shipping terminals) || 192.168.0.1/23 (192.168.0.1 - 192.168.1.254) || Colloquially known as the "Guest VLAN", but staff wifi devices are not technically guest devices. Currently, shipping computers are on this network, but they should be moved to VLAN 7 when it is created. || Routed out Shaw Business Internet
|-
| '''3''' || vMotion LAN || ?? || Small network to isolate vMotion traffic between the 3 virtual hosts. || -
|-
| '''4''' || Shaw WAN interfaces || Network of the Shaw static WAN IP (/32) || Network to isolate WAN traffic between Shaw modem and Sophos WAN interface from the rest of the network. Lots of ARP going on here! || -
|-
| '''5''' || Telus WAN interfaces || Network of our Telus WAN IPs (/27) || Network to isolate WAN traffic between Telus modem and Sophos WAN interface from the rest of the network. || -
|-
| '''6''' || VoIP LAN || 192.168.44.0/24 || Contains PBX and IP phones || Routed out Telus and Shaw (Sophos multipath)
|}

=Helpful Stuff=
The command to view what MAC address(s) is in use on a port for the Cisco SG350 switch is as follows. You will need to login to the switch via SSH in order to do this:
* show mac address-table interface gi1 (or ge1 sometimes too)
The port name is visible from the switches web interface and goes from gi1 to gi28 or ge1 to ge28. Then cross checking the MAC address in Spiceworks for example will allow you to see who is plugged into what port - however all the Cisco switches should already have human readable labels attached to all in-use ports as of July 2019.
[[Category: Networking]]

Information Systems:LAN infrastructure at uniPHARM

2022-10-20T22:10:21Z

Anmolm:

==Overview==
This is the main page for the LAN (wired network configuration) at uniPHARM.

==Switches==
This table outlines the physical network switches that make up the network.

{| class="wikitable sortable"
|-
! Hostname !! IP address || Switch model !! Location !! Username !! Password !! Notes
|-
| '''coresw''' || 172.30.16.2 || 3Com 3870 || Server room || admin || visionit || '''Core switch.''' Stack of 4.
|-
| atpsw || 172.30.16.3 || 3Com 4200 || Server room || admin || visionit || Feeds data to POE injectors for Mirador temp. sensors
|-
| accountingsw || 172.30.16.11 || Cisco SG350-28P || Accounting Wallmount Network Rack || adminit || visionit || POE, ~175W power budget
|-
| buyerswcisco || 172.30.16.18 || Cisco SG350-28P || Buying department closet || adminit || visionit|| -
|-
| itsw || 172.30.16.6 || 3Com 4200G || IT department ceiling tile. Yup. || admin || visionis || -
|-
| cagesw || 172.30.16.12 || 3Com 3870 || Computer lab || admin || visionit
|-
| dumpsw.unipharm.local || 172.30.16.7 || 3Com 4200G? || Electrical Room? || admin || visionds || -
|-
| pickingsw || 172.30.16.8 || 3Com 3870? || Rx picking zone network rack || admin || visionps || -
|-
| receivingswcisco || 172.30.16.17 || Cisco SG350-28P || DC Manager's Office || adminit || visionit || -
|-
| wallsw || 172.30.16.9 || 3Com 4200G? || Candy Mezzanine || admin || visionns || Functions merely to bridge the physical wiring between Receiving area and core network
|-
| jeremymsw || 172.30.16.16 || TP-Link SG105E || Jeremy's office || admin || visionit || Used for testing Yealink, web-managed smart switch
|-
| norwinusw || 172.30.16.15 || Netgear GS105PE || Norwin's office || - || visionit || Used to access multiple VLANs, network administration, and testing. This switch has PoE passthrough.
|-
| itlabswcisco || 172.30.16.19 || Cisco SG350-10MP || IT Lab/Cage || adminit || visionit ||
|}

* External link to backdoor access and hidden menus for the 3com 3870 switches http://etherhack.wikia.com/wiki/3Com_3870
* There is a spare, ready to use 3com 3870 24 port switch located at the very bottom of the networking rack in the server room. The switch has been reset to factory defaults and the username is admin and the password is blank. The switch is ready to be put into the core stack if needed.

==VLANs==
We started using VLANs in 2016, for the same reason why anyone would use VLANs - to manage/separate multiple networks using one physical switch infrastructure. The VLAN implementation being used is the standard 802.1q. The following table outlines the VLAN infrastructure.

{| class="wikitable sortable"
|-
! VLAN ID !! Name !! L3 Network / IP Range !! Description !! Notes
|-
| '''1''' || Main LAN || 172.30.16.0/21 (172.30.16.1 - 172.30.23.255) || Default VLAN, untagged across the network for simplicity (so that every device doesn't have to be configured to talk this VLAN, or even be VLAN-aware at all). || Routed out Telus Fibre
|-
| '''2''' || Alt LAN (Staff/ guest BYOD, Shipping terminals) || 192.168.0.1/23 (192.168.0.1 - 192.168.1.254) || Colloquially known as the "Guest VLAN", but staff wifi devices are not technically guest devices. Currently, shipping computers are on this network, but they should be moved to VLAN 7 when it is created. || Routed out Shaw Business Internet
|-
| '''3''' || vMotion LAN || ?? || Small network to isolate vMotion traffic between the 3 virtual hosts. || -
|-
| '''4''' || Shaw WAN interfaces || Network of the Shaw static WAN IP (/32) || Network to isolate WAN traffic between Shaw modem and Sophos WAN interface from the rest of the network. Lots of ARP going on here! || -
|-
| '''5''' || Telus WAN interfaces || Network of our Telus WAN IPs (/27) || Network to isolate WAN traffic between Telus modem and Sophos WAN interface from the rest of the network. || -
|-
| '''6''' || VoIP LAN || 192.168.44.0/24 || Contains PBX and IP phones || Routed out Telus and Shaw (Sophos multipath)
|}

=Helpful Stuff=
The command to view what MAC address(s) is in use on a port for the Cisco SG350 switch is as follows. You will need to login to the switch via SSH in order to do this:
* show mac address-table interface gi1 (or ge1 sometimes too)
The port name is visible from the switches web interface and goes from gi1 to gi28 or ge1 to ge28. Then cross checking the MAC address in Spiceworks for example will allow you to see who is plugged into what port - however all the Cisco switches should already have human readable labels attached to all in-use ports as of July 2019.
[[Category: Networking]]

Information Systems:Mirador Temperature Monitoring Server

2022-09-20T16:59:28Z

Anmolm:

DarrenF wrote this document on October 4 2012

This machine is the cold spare Mbox from ATP and it is supposed to powered off unless in use.

If the in-production Richmond or Calgary Mbox has a hard drive failure with loss of data
then what needs to happen is a restore from tape backup. First stop the Apache and
MySQL services on this machine. During the restore from tape only restore
the D: drive of the failed machine on to this machine. The only other folder that needs
to be restored from tape is C:\Program Files\Apache2\htdocs\plans
Then change the IP address of this machine to match the failed machine. Then reboot.

If the in-production Richmond or Calgary Mbox has a failure that does not affect it's
hard drive, then the following must be done. Stop the Apache and MySQL service on this machine.
Remove the undamaged hard drive from the failed Mbox. Plug it into any desktop as it
is a normal SATA hard drive. Copy the "data" folder from the D:
and paste it onto the D: of this machine replacing all existing files. Also copy and paste
the C:\Program Files\Apache2\htdocs\plans folder from the failed machine onto this one.
Change the IP address of this machine to match the failed Mbox and reboot.

The hard drive controller chip on the in-production Mboxes is the same as the chip on this
machine. It is theoretically possible to take the undamaged hard drive out of a failed
Mbox and plug it in to this machine. There are a couple of complications and this method
of rescure may not work.

The controller chip is the same but the motherboards are not identical.
The second SATA port on this machine has been disabled and cannot be turned on
A hard drive from an in-production Mbox may or may not have all the device drivers needed by this Mbox
The OEM license on the rescued hard drive does not allow transferrs to another computer
The OEM license may need to be reactived if moved from a failed Mbox to this machine

Other Important Information

* mirador.unipharm.local 172.30.18.36
* miradorcalgary.unipharm.local 172.30.18.39
* miradorspare.unipharm.local DHCP and then should be changed to one of the above IP's

Username Administrator
Password mbox

'''None of the 3 Mboxes are connected to Active Directory in any way'''

* Denise Delia is the technical contact at ATP and his phone number is 514-324-4720 ext 245
* His email address is d.delia@alternatives-tech.com

==ATP Access Points==

We have 3 ATP Access Points around the warehouse.

* 1 in Receiving
* 1 in Shipping
* 1 in returns

Mirador Temperature sensors need to connect with these APs to work.
=Some Things to note=
# The APs have a static IP address which is preconfigured by Cryopak.
# The APs are powered through POE straight from the core switch. Note: POE is supplied through POE injectors provided by Cryopak. These injectors are Low power POE (18V most probably) instead of the standard POE. So, please make sure to use those injectors, APs won't work with standard POE.
# The APs have an inbuilt battery which can last about 6 hrs or so. There is an indication on the APs screen to tell that.

[[Category: Servers - Hardware]]
[[Category: Power, Alarms, and Monitoring]]

Information Systems:Mirador Temperature Monitoring Server

2022-09-20T16:59:17Z

Anmolm:

DarrenF wrote this document on October 4 2012

This machine is the cold spare Mbox from ATP and it is supposed to powered off unless in use.

If the in-production Richmond or Calgary Mbox has a hard drive failure with loss of data
then what needs to happen is a restore from tape backup. First stop the Apache and
MySQL services on this machine. During the restore from tape only restore
the D: drive of the failed machine on to this machine. The only other folder that needs
to be restored from tape is C:\Program Files\Apache2\htdocs\plans
Then change the IP address of this machine to match the failed machine. Then reboot.

If the in-production Richmond or Calgary Mbox has a failure that does not affect it's
hard drive, then the following must be done. Stop the Apache and MySQL service on this machine.
Remove the undamaged hard drive from the failed Mbox. Plug it into any desktop as it
is a normal SATA hard drive. Copy the "data" folder from the D:
and paste it onto the D: of this machine replacing all existing files. Also copy and paste
the C:\Program Files\Apache2\htdocs\plans folder from the failed machine onto this one.
Change the IP address of this machine to match the failed Mbox and reboot.

The hard drive controller chip on the in-production Mboxes is the same as the chip on this
machine. It is theoretically possible to take the undamaged hard drive out of a failed
Mbox and plug it in to this machine. There are a couple of complications and this method
of rescure may not work.

The controller chip is the same but the motherboards are not identical.
The second SATA port on this machine has been disabled and cannot be turned on
A hard drive from an in-production Mbox may or may not have all the device drivers needed by this Mbox
The OEM license on the rescued hard drive does not allow transferrs to another computer
The OEM license may need to be reactived if moved from a failed Mbox to this machine

Other Important Information

* mirador.unipharm.local 172.30.18.36
* miradorcalgary.unipharm.local 172.30.18.39
* miradorspare.unipharm.local DHCP and then should be changed to one of the above IP's

Username Administrator
Password mbox

'''None of the 3 Mboxes are connected to Active Directory in any way'''

* Denise Delia is the technical contact at ATP and his phone number is 514-324-4720 ext 245
* His email address is d.delia@alternatives-tech.com

==ATP Access Points==

We have 3 ATP Access Points around the warehouse.

* 1 in Receiving
* 1 in Shipping
* 1 in returns

Mirador Temperature sensors need to connect with these APs to work.
=Some Things to note=
# The APs have a static IP address which is preconfigured by Cryopak.
# The APs are powered through POE straight from the core switch. Note: POE is supplied through POE injectors provided by Cryopak. These injectors are Low power POE (18V most probably) instead of the standard POE.So, please make sure to use those injectors, APs won't work with standard POE.
# The APs have an inbuilt battery which can last about 6 hrs or so. There is an indication on the APs screen to tell that.

[[Category: Servers - Hardware]]
[[Category: Power, Alarms, and Monitoring]]

Information Systems:Mirador Temperature Monitoring Server

2022-09-20T16:58:35Z

Anmolm:

DarrenF wrote this document on October 4 2012

This machine is the cold spare Mbox from ATP and it is supposed to powered off unless in use.

If the in-production Richmond or Calgary Mbox has a hard drive failure with loss of data
then what needs to happen is a restore from tape backup. First stop the Apache and
MySQL services on this machine. During the restore from tape only restore
the D: drive of the failed machine on to this machine. The only other folder that needs
to be restored from tape is C:\Program Files\Apache2\htdocs\plans
Then change the IP address of this machine to match the failed machine. Then reboot.

If the in-production Richmond or Calgary Mbox has a failure that does not affect it's
hard drive, then the following must be done. Stop the Apache and MySQL service on this machine.
Remove the undamaged hard drive from the failed Mbox. Plug it into any desktop as it
is a normal SATA hard drive. Copy the "data" folder from the D:
and paste it onto the D: of this machine replacing all existing files. Also copy and paste
the C:\Program Files\Apache2\htdocs\plans folder from the failed machine onto this one.
Change the IP address of this machine to match the failed Mbox and reboot.

The hard drive controller chip on the in-production Mboxes is the same as the chip on this
machine. It is theoretically possible to take the undamaged hard drive out of a failed
Mbox and plug it in to this machine. There are a couple of complications and this method
of rescure may not work.

The controller chip is the same but the motherboards are not identical.
The second SATA port on this machine has been disabled and cannot be turned on
A hard drive from an in-production Mbox may or may not have all the device drivers needed by this Mbox
The OEM license on the rescued hard drive does not allow transferrs to another computer
The OEM license may need to be reactived if moved from a failed Mbox to this machine

Other Important Information

* mirador.unipharm.local 172.30.18.36
* miradorcalgary.unipharm.local 172.30.18.39
* miradorspare.unipharm.local DHCP and then should be changed to one of the above IP's

Username Administrator
Password mbox

'''None of the 3 Mboxes are connected to Active Directory in any way'''

* Denise Delia is the technical contact at ATP and his phone number is 514-324-4720 ext 245
* His email address is d.delia@alternatives-tech.com

==ATP Access Points==

We have 3 ATP Access Points around the warehouse.

* 1 in Receiving
* 1 in Shipping
* 1 in returns

Mirador Temperature sensors need to connect with these APs to work.
=Some Things to note=
# The APs have a static IP address which is preconfigured by Cryopak.
# The APs are powered through POE straight from the core switch. Note: POE is supplied through POE injectors provided by Cryopak. These injectors are Low power POE (18W most probably) instead of the standard POE So please make sure to use those injectors, APs won't work with standard POE.
# The APs have an inbuilt battery which can last about 6 hrs or so. There is an indication on the APs screen to tell that.

[[Category: Servers - Hardware]]
[[Category: Power, Alarms, and Monitoring]]

Information Systems:Mirador Temperature Monitoring Server

2022-09-20T16:58:06Z

Anmolm:

DarrenF wrote this document on October 4 2012

This machine is the cold spare Mbox from ATP and it is supposed to powered off unless in use.

If the in-production Richmond or Calgary Mbox has a hard drive failure with loss of data
then what needs to happen is a restore from tape backup. First stop the Apache and
MySQL services on this machine. During the restore from tape only restore
the D: drive of the failed machine on to this machine. The only other folder that needs
to be restored from tape is C:\Program Files\Apache2\htdocs\plans
Then change the IP address of this machine to match the failed machine. Then reboot.

If the in-production Richmond or Calgary Mbox has a failure that does not affect it's
hard drive, then the following must be done. Stop the Apache and MySQL service on this machine.
Remove the undamaged hard drive from the failed Mbox. Plug it into any desktop as it
is a normal SATA hard drive. Copy the "data" folder from the D:
and paste it onto the D: of this machine replacing all existing files. Also copy and paste
the C:\Program Files\Apache2\htdocs\plans folder from the failed machine onto this one.
Change the IP address of this machine to match the failed Mbox and reboot.

The hard drive controller chip on the in-production Mboxes is the same as the chip on this
machine. It is theoretically possible to take the undamaged hard drive out of a failed
Mbox and plug it in to this machine. There are a couple of complications and this method
of rescure may not work.

The controller chip is the same but the motherboards are not identical.
The second SATA port on this machine has been disabled and cannot be turned on
A hard drive from an in-production Mbox may or may not have all the device drivers needed by this Mbox
The OEM license on the rescued hard drive does not allow transferrs to another computer
The OEM license may need to be reactived if moved from a failed Mbox to this machine

Other Important Information

* mirador.unipharm.local 172.30.18.36
* miradorcalgary.unipharm.local 172.30.18.39
* miradorspare.unipharm.local DHCP and then should be changed to one of the above IP's

Username Administrator
Password mbox

'''None of the 3 Mboxes are connected to Active Directory in any way'''

* Denise Delia is the technical contact at ATP and his phone number is 514-324-4720 ext 245
* His email address is d.delia@alternatives-tech.com

==ATP Access Points==

We have 3 ATP Access Points around the warehouse.

* 1 in Receiving
* 1 in Shipping
* 1 in returns

Mirador Temperature sensors need to connect with these APs to work.
=Some Things to note=
# The APs have a static IP address which is preconfigured by Cryopak.
# The APs are powered through POE. Note: POE is supplied through POE injectors provided by Cryopak. These injectors are Low power POE (18W most probably) instead of the standard POE So please make sure to use those injectors, APs won't work with standard POE.
# The APs have an inbuilt battery which can last about 6 hrs or so. There is an indication on the APs screen to tell that.

[[Category: Servers - Hardware]]
[[Category: Power, Alarms, and Monitoring]]

Information Systems:Mirador Temperature Monitoring Server

2022-09-20T16:39:33Z

Anmolm:

DarrenF wrote this document on October 4 2012

This machine is the cold spare Mbox from ATP and it is supposed to powered off unless in use.

If the in-production Richmond or Calgary Mbox has a hard drive failure with loss of data
then what needs to happen is a restore from tape backup. First stop the Apache and
MySQL services on this machine. During the restore from tape only restore
the D: drive of the failed machine on to this machine. The only other folder that needs
to be restored from tape is C:\Program Files\Apache2\htdocs\plans
Then change the IP address of this machine to match the failed machine. Then reboot.

If the in-production Richmond or Calgary Mbox has a failure that does not affect it's
hard drive, then the following must be done. Stop the Apache and MySQL service on this machine.
Remove the undamaged hard drive from the failed Mbox. Plug it into any desktop as it
is a normal SATA hard drive. Copy the "data" folder from the D:
and paste it onto the D: of this machine replacing all existing files. Also copy and paste
the C:\Program Files\Apache2\htdocs\plans folder from the failed machine onto this one.
Change the IP address of this machine to match the failed Mbox and reboot.

The hard drive controller chip on the in-production Mboxes is the same as the chip on this
machine. It is theoretically possible to take the undamaged hard drive out of a failed
Mbox and plug it in to this machine. There are a couple of complications and this method
of rescure may not work.

The controller chip is the same but the motherboards are not identical.
The second SATA port on this machine has been disabled and cannot be turned on
A hard drive from an in-production Mbox may or may not have all the device drivers needed by this Mbox
The OEM license on the rescued hard drive does not allow transferrs to another computer
The OEM license may need to be reactived if moved from a failed Mbox to this machine

Other Important Information

* mirador.unipharm.local 172.30.18.36
* miradorcalgary.unipharm.local 172.30.18.39
* miradorspare.unipharm.local DHCP and then should be changed to one of the above IP's

Username Administrator
Password mbox

'''None of the 3 Mboxes are connected to Active Directory in any way'''

* Denise Delia is the technical contact at ATP and his phone number is 514-324-4720 ext 245
* His email address is d.delia@alternatives-tech.com

==ATP Access Points==

We have 3 ATP Access Points around the warehouse.

* 1 in Receiving
* 1 in Shipping
* 1 in returns

Mirador Temperature sensors need to connect with these APs to work.
=Some Things to note=
# The APs have a static IP address which is preconfigured by Cryopak.
# The APs are powered through POE. Note: POE is supplied through POE injectors provided by Cryopak. These injectors are Low power POE (18W most probably) instead of the standard POE So please make sure to use those injectors, APs won't work with standard POE.
# The APs have an inbuilt battery which can last about 6 hrs or so. There is an indication on the APs screen to tell that.

[[Category: Servers - Hardware]]
[[Category: Power, Alarms, and Monitoring]]

Information Systems:Mirador Temperature Monitoring Server

2022-09-20T16:38:44Z

Anmolm:

DarrenF wrote this document on October 4 2012

This machine is the cold spare Mbox from ATP and it is supposed to powered off unless in use.

If the in-production Richmond or Calgary Mbox has a hard drive failure with loss of data
then what needs to happen is a restore from tape backup. First stop the Apache and
MySQL services on this machine. During the restore from tape only restore
the D: drive of the failed machine on to this machine. The only other folder that needs
to be restored from tape is C:\Program Files\Apache2\htdocs\plans
Then change the IP address of this machine to match the failed machine. Then reboot.

If the in-production Richmond or Calgary Mbox has a failure that does not affect it's
hard drive, then the following must be done. Stop the Apache and MySQL service on this machine.
Remove the undamaged hard drive from the failed Mbox. Plug it into any desktop as it
is a normal SATA hard drive. Copy the "data" folder from the D:
and paste it onto the D: of this machine replacing all existing files. Also copy and paste
the C:\Program Files\Apache2\htdocs\plans folder from the failed machine onto this one.
Change the IP address of this machine to match the failed Mbox and reboot.

The hard drive controller chip on the in-production Mboxes is the same as the chip on this
machine. It is theoretically possible to take the undamaged hard drive out of a failed
Mbox and plug it in to this machine. There are a couple of complications and this method
of rescure may not work.

The controller chip is the same but the motherboards are not identical.
The second SATA port on this machine has been disabled and cannot be turned on
A hard drive from an in-production Mbox may or may not have all the device drivers needed by this Mbox
The OEM license on the rescued hard drive does not allow transferrs to another computer
The OEM license may need to be reactived if moved from a failed Mbox to this machine

Other Important Information

* mirador.unipharm.local 172.30.18.36
* miradorcalgary.unipharm.local 172.30.18.39
* miradorspare.unipharm.local DHCP and then should be changed to one of the above IP's

Username Administrator
Password mbox

'''None of the 3 Mboxes are connected to Active Directory in any way'''

* Denise Delia is the technical contact at ATP and his phone number is 514-324-4720 ext 245
* His email address is d.delia@alternatives-tech.com

==ATP Access Points==

We have 3 ATP Access Points around the warehouse.

* 1 in Receiving
* 1 in Shipping
* 1 in returns

Mirador Temperature sensors need to connect with these APs to work.
=Some Things to note=
1. The APs have a static IP address which is preconfigured by Cryopak.
2. The APs are powered through POE. Note: POE is supplied through POE injectors provided by Cryopak. These injectors are Low power POE (18W most probably) instead of the standard POE So please make sure to use those injectors, APs won't work with standard POE.
3. The APs have an inbuilt battery which can last about 6 hrs or so. There is an indication on the APs screen to tell that.

[[Category: Servers - Hardware]]
[[Category: Power, Alarms, and Monitoring]]

Information Systems:Mirador Temperature Monitoring Server

2022-09-20T16:38:26Z

Anmolm:

DarrenF wrote this document on October 4 2012

This machine is the cold spare Mbox from ATP and it is supposed to powered off unless in use.

If the in-production Richmond or Calgary Mbox has a hard drive failure with loss of data
then what needs to happen is a restore from tape backup. First stop the Apache and
MySQL services on this machine. During the restore from tape only restore
the D: drive of the failed machine on to this machine. The only other folder that needs
to be restored from tape is C:\Program Files\Apache2\htdocs\plans
Then change the IP address of this machine to match the failed machine. Then reboot.

If the in-production Richmond or Calgary Mbox has a failure that does not affect it's
hard drive, then the following must be done. Stop the Apache and MySQL service on this machine.
Remove the undamaged hard drive from the failed Mbox. Plug it into any desktop as it
is a normal SATA hard drive. Copy the "data" folder from the D:
and paste it onto the D: of this machine replacing all existing files. Also copy and paste
the C:\Program Files\Apache2\htdocs\plans folder from the failed machine onto this one.
Change the IP address of this machine to match the failed Mbox and reboot.

The hard drive controller chip on the in-production Mboxes is the same as the chip on this
machine. It is theoretically possible to take the undamaged hard drive out of a failed
Mbox and plug it in to this machine. There are a couple of complications and this method
of rescure may not work.

The controller chip is the same but the motherboards are not identical.
The second SATA port on this machine has been disabled and cannot be turned on
A hard drive from an in-production Mbox may or may not have all the device drivers needed by this Mbox
The OEM license on the rescued hard drive does not allow transferrs to another computer
The OEM license may need to be reactived if moved from a failed Mbox to this machine

Other Important Information

* mirador.unipharm.local 172.30.18.36
* miradorcalgary.unipharm.local 172.30.18.39
* miradorspare.unipharm.local DHCP and then should be changed to one of the above IP's

Username Administrator
Password mbox

'''None of the 3 Mboxes are connected to Active Directory in any way'''

* Denise Delia is the technical contact at ATP and his phone number is 514-324-4720 ext 245
* His email address is d.delia@alternatives-tech.com

==ATP Access Points==

We have 3 ATP Access Points around the warehouse.

* 1 in Receiving
* 1 in Shipping
* 1 in returns

Mirador Temperature sensors need to connect with these APs to work.
=Some Things to note=
1. The APs have a static IP address which is preconfigured by Cryopak.
2. The APs are powered through POE. Note: POE is supplied through POE injectors provided by Cryopak. These injectors are Low power POE (18W most probably) instead of the standard POE So please make sure to use those injectors, APs won't work with standard POE. 
3. The APs have an inbuilt battery which can last about 6 hrs or so. There is an indication on the APs screen to tell that.

[[Category: Servers - Hardware]]
[[Category: Power, Alarms, and Monitoring]]

Information Systems:Mirador Temperature Monitoring Server

2022-09-20T16:38:15Z

Anmolm:

DarrenF wrote this document on October 4 2012

This machine is the cold spare Mbox from ATP and it is supposed to powered off unless in use.

If the in-production Richmond or Calgary Mbox has a hard drive failure with loss of data
then what needs to happen is a restore from tape backup. First stop the Apache and
MySQL services on this machine. During the restore from tape only restore
the D: drive of the failed machine on to this machine. The only other folder that needs
to be restored from tape is C:\Program Files\Apache2\htdocs\plans
Then change the IP address of this machine to match the failed machine. Then reboot.

If the in-production Richmond or Calgary Mbox has a failure that does not affect it's
hard drive, then the following must be done. Stop the Apache and MySQL service on this machine.
Remove the undamaged hard drive from the failed Mbox. Plug it into any desktop as it
is a normal SATA hard drive. Copy the "data" folder from the D:
and paste it onto the D: of this machine replacing all existing files. Also copy and paste
the C:\Program Files\Apache2\htdocs\plans folder from the failed machine onto this one.
Change the IP address of this machine to match the failed Mbox and reboot.

The hard drive controller chip on the in-production Mboxes is the same as the chip on this
machine. It is theoretically possible to take the undamaged hard drive out of a failed
Mbox and plug it in to this machine. There are a couple of complications and this method
of rescure may not work.

The controller chip is the same but the motherboards are not identical.
The second SATA port on this machine has been disabled and cannot be turned on
A hard drive from an in-production Mbox may or may not have all the device drivers needed by this Mbox
The OEM license on the rescued hard drive does not allow transferrs to another computer
The OEM license may need to be reactived if moved from a failed Mbox to this machine

Other Important Information

* mirador.unipharm.local 172.30.18.36
* miradorcalgary.unipharm.local 172.30.18.39
* miradorspare.unipharm.local DHCP and then should be changed to one of the above IP's

Username Administrator
Password mbox

'''None of the 3 Mboxes are connected to Active Directory in any way'''

* Denise Delia is the technical contact at ATP and his phone number is 514-324-4720 ext 245
* His email address is d.delia@alternatives-tech.com

==ATP Access Points==

We have 3 ATP Access Points around the warehouse.

* 1 in Receiving
* 1 in Shipping
* 1 in returns

Mirador Temperature sensors need to connect with these APs to work.
=Some Things to note=
1. The APs have a static IP address which is preconfigured by Cryopak.
2. The APs are powered through POE. Note: POE is supplied through POE injectors provided by Cryopak. These injectors are Low power POE (18W most probably) instead of the standard POE So please make sure to use those injectors, APs won't work with standard POE. 
3. The APs have an inbuilt battery which can last about 6 hrs or so. There is an indication on the APs screen to tell that.

[[Category: Servers - Hardware]]
[[Category: Power, Alarms, and Monitoring]]

Information Systems:Mirador Temperature Monitoring Server

2022-09-20T16:37:54Z

Anmolm:

DarrenF wrote this document on October 4 2012

This machine is the cold spare Mbox from ATP and it is supposed to powered off unless in use.

If the in-production Richmond or Calgary Mbox has a hard drive failure with loss of data
then what needs to happen is a restore from tape backup. First stop the Apache and
MySQL services on this machine. During the restore from tape only restore
the D: drive of the failed machine on to this machine. The only other folder that needs
to be restored from tape is C:\Program Files\Apache2\htdocs\plans
Then change the IP address of this machine to match the failed machine. Then reboot.

If the in-production Richmond or Calgary Mbox has a failure that does not affect it's
hard drive, then the following must be done. Stop the Apache and MySQL service on this machine.
Remove the undamaged hard drive from the failed Mbox. Plug it into any desktop as it
is a normal SATA hard drive. Copy the "data" folder from the D:
and paste it onto the D: of this machine replacing all existing files. Also copy and paste
the C:\Program Files\Apache2\htdocs\plans folder from the failed machine onto this one.
Change the IP address of this machine to match the failed Mbox and reboot.

The hard drive controller chip on the in-production Mboxes is the same as the chip on this
machine. It is theoretically possible to take the undamaged hard drive out of a failed
Mbox and plug it in to this machine. There are a couple of complications and this method
of rescure may not work.

The controller chip is the same but the motherboards are not identical.
The second SATA port on this machine has been disabled and cannot be turned on
A hard drive from an in-production Mbox may or may not have all the device drivers needed by this Mbox
The OEM license on the rescued hard drive does not allow transferrs to another computer
The OEM license may need to be reactived if moved from a failed Mbox to this machine

Other Important Information

* mirador.unipharm.local 172.30.18.36
* miradorcalgary.unipharm.local 172.30.18.39
* miradorspare.unipharm.local DHCP and then should be changed to one of the above IP's

Username Administrator
Password mbox

'''None of the 3 Mboxes are connected to Active Directory in any way'''

* Denise Delia is the technical contact at ATP and his phone number is 514-324-4720 ext 245
* His email address is d.delia@alternatives-tech.com

==ATP Access Points==

We have 3 ATP Access Points around the warehouse.

* 1 in Receiving
* 1 in Shipping
* 1 in returns

Mirador Temperature sensors need to connect with these APs to work.
=Some Things to note=
1. The APs have a static IP address which is preconfigured by Cryopak.
2. The APs are powered through POE. Note: POE is supplied through POE injectors provided by Cryopak. These injectors are Low power POE (18W most probably) instead of the standard POE So please make sure to use those injectors, APs won't work with standard POE.
3. The APs have an inbuilt battery which can last about 6 hrs or so. There is an indication on the APs screen to tell that.

[[Category: Servers - Hardware]]
[[Category: Power, Alarms, and Monitoring]]

Information Systems:Mirador Temperature Monitoring Server

2022-09-20T16:31:12Z

Anmolm:

DarrenF wrote this document on October 4 2012

This machine is the cold spare Mbox from ATP and it is supposed to powered off unless in use.

If the in-production Richmond or Calgary Mbox has a hard drive failure with loss of data
then what needs to happen is a restore from tape backup. First stop the Apache and
MySQL services on this machine. During the restore from tape only restore
the D: drive of the failed machine on to this machine. The only other folder that needs
to be restored from tape is C:\Program Files\Apache2\htdocs\plans
Then change the IP address of this machine to match the failed machine. Then reboot.

If the in-production Richmond or Calgary Mbox has a failure that does not affect it's
hard drive, then the following must be done. Stop the Apache and MySQL service on this machine.
Remove the undamaged hard drive from the failed Mbox. Plug it into any desktop as it
is a normal SATA hard drive. Copy the "data" folder from the D:
and paste it onto the D: of this machine replacing all existing files. Also copy and paste
the C:\Program Files\Apache2\htdocs\plans folder from the failed machine onto this one.
Change the IP address of this machine to match the failed Mbox and reboot.

The hard drive controller chip on the in-production Mboxes is the same as the chip on this
machine. It is theoretically possible to take the undamaged hard drive out of a failed
Mbox and plug it in to this machine. There are a couple of complications and this method
of rescure may not work.

The controller chip is the same but the motherboards are not identical.
The second SATA port on this machine has been disabled and cannot be turned on
A hard drive from an in-production Mbox may or may not have all the device drivers needed by this Mbox
The OEM license on the rescued hard drive does not allow transferrs to another computer
The OEM license may need to be reactived if moved from a failed Mbox to this machine

Other Important Information

* mirador.unipharm.local 172.30.18.36
* miradorcalgary.unipharm.local 172.30.18.39
* miradorspare.unipharm.local DHCP and then should be changed to one of the above IP's

Username Administrator
Password mbox

'''None of the 3 Mboxes are connected to Active Directory in any way'''

* Denise Delia is the technical contact at ATP and his phone number is 514-324-4720 ext 245
* His email address is d.delia@alternatives-tech.com

==ATP Access Points==

We have 3 ATP Access Points around the warehouse.

* 1 in Receiving
* 1 in Shipping
* 1 in returns

Mirador Temperature sensors need to connect with these APs to work.
=Some Things to note=
1.

[[Category: Servers - Hardware]]
[[Category: Power, Alarms, and Monitoring]]

Information Systems:Mirador Temperature Monitoring Server

2022-09-20T16:30:14Z

Anmolm:

DarrenF wrote this document on October 4 2012

This machine is the cold spare Mbox from ATP and it is supposed to powered off unless in use.

If the in-production Richmond or Calgary Mbox has a hard drive failure with loss of data
then what needs to happen is a restore from tape backup. First stop the Apache and
MySQL services on this machine. During the restore from tape only restore
the D: drive of the failed machine on to this machine. The only other folder that needs
to be restored from tape is C:\Program Files\Apache2\htdocs\plans
Then change the IP address of this machine to match the failed machine. Then reboot.

If the in-production Richmond or Calgary Mbox has a failure that does not affect it's
hard drive, then the following must be done. Stop the Apache and MySQL service on this machine.
Remove the undamaged hard drive from the failed Mbox. Plug it into any desktop as it
is a normal SATA hard drive. Copy the "data" folder from the D:
and paste it onto the D: of this machine replacing all existing files. Also copy and paste
the C:\Program Files\Apache2\htdocs\plans folder from the failed machine onto this one.
Change the IP address of this machine to match the failed Mbox and reboot.

The hard drive controller chip on the in-production Mboxes is the same as the chip on this
machine. It is theoretically possible to take the undamaged hard drive out of a failed
Mbox and plug it in to this machine. There are a couple of complications and this method
of rescure may not work.

The controller chip is the same but the motherboards are not identical.
The second SATA port on this machine has been disabled and cannot be turned on
A hard drive from an in-production Mbox may or may not have all the device drivers needed by this Mbox
The OEM license on the rescued hard drive does not allow transferrs to another computer
The OEM license may need to be reactived if moved from a failed Mbox to this machine

Other Important Information

* mirador.unipharm.local 172.30.18.36
* miradorcalgary.unipharm.local 172.30.18.39
* miradorspare.unipharm.local DHCP and then should be changed to one of the above IP's

Username Administrator
Password mbox

'''None of the 3 Mboxes are connected to Active Directory in any way'''

* Denise Delia is the technical contact at ATP and his phone number is 514-324-4720 ext 245
* His email address is d.delia@alternatives-tech.com

==ATP Access Points==

We have 3 ATP Access Points around the warehouse.
1 in Receiving
1 in Shipping
1 in returns

Mirador Temperature sensors need to connect with these APs to work.
=Some Things to note=
1.

[[Category: Servers - Hardware]]
[[Category: Power, Alarms, and Monitoring]]

Information Systems:Mirador Temperature Monitoring Server

2022-09-20T16:28:03Z

Anmolm:

DarrenF wrote this document on October 4 2012

This machine is the cold spare Mbox from ATP and it is supposed to powered off unless in use.

If the in-production Richmond or Calgary Mbox has a hard drive failure with loss of data
then what needs to happen is a restore from tape backup. First stop the Apache and
MySQL services on this machine. During the restore from tape only restore
the D: drive of the failed machine on to this machine. The only other folder that needs
to be restored from tape is C:\Program Files\Apache2\htdocs\plans
Then change the IP address of this machine to match the failed machine. Then reboot.

If the in-production Richmond or Calgary Mbox has a failure that does not affect it's
hard drive, then the following must be done. Stop the Apache and MySQL service on this machine.
Remove the undamaged hard drive from the failed Mbox. Plug it into any desktop as it
is a normal SATA hard drive. Copy the "data" folder from the D:
and paste it onto the D: of this machine replacing all existing files. Also copy and paste
the C:\Program Files\Apache2\htdocs\plans folder from the failed machine onto this one.
Change the IP address of this machine to match the failed Mbox and reboot.

The hard drive controller chip on the in-production Mboxes is the same as the chip on this
machine. It is theoretically possible to take the undamaged hard drive out of a failed
Mbox and plug it in to this machine. There are a couple of complications and this method
of rescure may not work.

The controller chip is the same but the motherboards are not identical.
The second SATA port on this machine has been disabled and cannot be turned on
A hard drive from an in-production Mbox may or may not have all the device drivers needed by this Mbox
The OEM license on the rescued hard drive does not allow transferrs to another computer
The OEM license may need to be reactived if moved from a failed Mbox to this machine

Other Important Information

* mirador.unipharm.local 172.30.18.36
* miradorcalgary.unipharm.local 172.30.18.39
* miradorspare.unipharm.local DHCP and then should be changed to one of the above IP's

Username Administrator
Password mbox

'''None of the 3 Mboxes are connected to Active Directory in any way'''

* Denise Delia is the technical contact at ATP and his phone number is 514-324-4720 ext 245
* His email address is d.delia@alternatives-tech.com

==ATP Access Points==

[[Category: Servers - Hardware]]
[[Category: Power, Alarms, and Monitoring]]

Information Systems:CheqMaster

2022-09-09T20:21:59Z

Anmolm:

=Overview=
Cheque Master a.k.a. Chequemaster is used to print cheques in A/P.

We do not print cheques on the i (i.e ASW); instead we use a PC package that prints as well as keeping a cheque register. The cheque is generated by ASW, but instead of printing, the spool file is sent to the IFS, where Cheque Master can read and process it. When completed, the file is moved to an archive folder.

==Technical Support==

Michael Guenzel (pronounced Gun zel, accent on second syllable)
VisionCraft
Suite 1600 Sun Life Plaza
144 - 4th Avenue SW
Calgary, Alberta, Canada T2P 3N4
Tel: (403) 232-6080 or (800) 265-6080
Fax: (403) 547-6213
mguenzel@visioncraft.com

==iSeries Setup==

Created an outq named CHEQUE in library QUSRSYS, which is not attached to a printer, but will be used to store the spool file until the cheques have printed.

Created a folder named ChqMaster in the IFS, that contains the VISION programs, cheque printing files, and an archive folder of completed cheque files.

Created a data file named APCHEQUE, that the spool files will be copied into.

Changed the RPGLE program FLR128 (Cheque printout - Blank stock) to put the cheque spool file into the outq CHEQUE, with a status of HOLD.

Changed the CLLE program FLC128 (Cheque printout – Blank stock) to copy the spool file to the file APCHEQUE, and then to ChqMaster in the IFS.

==Cheque Printer==
The cheque printer is an HP LaserJet printer capable of printing MICR font. It is served on the network by superserver as '''chqprt'''. This device name is important for the program to recognize it.

Cheqmaster is set to print to port LPT2 (via a setting in General Administration). Since this is a physical port, the CHEQUES2 bat file that is used to start Cheqmaster issues a <code>net use</code> command to specify/spoof the network printer chqprt as existing on port LPT2.

==Signatures==

The signature tool (signature.exe) is on tech/common/iSeries/Vision AP Cheques/signature. However, as it is a .net application, it will not currently run from a network drive, so it must be (temporarily) copied to a local drive.

The first step is to print the Signature Template (the form to be used to scan in signatures). Load the signature tool, and press the template button. Select the printer, press Print, then OK.

Have the signing officers sign this sheet. Note that in our test, the signature had to be approximately a quarter of an inch in from the side borders. Scan the sheet as TIF, black and white, at 300 dpi.

Go back into the signature tool. Press the Graphic File Select button, highlight the scanned file, and press Open. The template will appear in the box to the left. Click on the black square to the upper left to select a signature.

The selected signature will appear in the Signature box to the right. Use the scroll bars to center it between the lines.

Go to the Signature ID box and select either the Top or Bottom Signature. Press the Output File Select button. The selections will be automatically set for current directory, with the correct file name for the chosen signature ID, and the correct type. Press Save. Note, however, that this does NOT save the object; it just does the preparation. Press the Save button in the lower right corner to write the selected output file.

Repeat for both the top and bottom signature. When complete, copy visionB.bin and visionT.bin to the finance/vision folder on the iSeries.

It is possible to adjust the positions of the signatures and the micr line. Edit the text file MICR_ADJ.VCD to do this. The first pair of numbers is the X and Y co-ordinates of the micr line, the middle pair is the top signature, and the last pair is the bottom signature. ‘+’ means down or to the right. ‘-‘ is up or to the left. The unit of measure is 300th of an inch. Be very careful to make no other changes to this file.

==Print A/P Cheques==

Create A/P payment proposal, and do any maintenance necessary. When ready, do an option 8 – payment order. This will generate cheques, but will not print them. Instead the spool file will be copied to a shared folder, from where a PC cheque application will be able to print them.

Using explorer, double click on the drive mapped to finance/vision on BART. Key in your user ID and password to allow you to access the application and cheque printing files. This step only has to be done once a day.

Click on the A/P Cheque icon, and print cheques.

When the cheques have been successfully printed, go back to the iSeries. Confirm and update the A/P payment proposal.

Eventually, the outq and the APCHEQUES data file will have to be cleared.

==Potential Problems==

====Signatures====

If either the signatures or the micr line are not in the correct location, they can be moved. See the section on ‘Signatures’ for instructions on how to this.

====Load forms first====

Cheque forms must be loaded before printing starts. If the cheque printer does not have cheque forms loaded, nothing will print. When this happens, cheques must be voided and recreated.

====Error message when reading cheque file====

Message is “An unrecoverable error occurred during the preview scanning of the current file – call Vision Craft at 403-232-6000 for assistance”. Only the person that creates the cheque file in ASW can print it with ChqMaster. Whoever logged onto the computer (Windows logon) needs authority to the cheque files. Any IT person can go into iSeries Navigator and change the permissions on the cheque files.

====Disappearing data / signatures (really a printing issue)====

The transit # in the MICR line was changed in the test system to prepare for corporate clearing. Nancy turned off signatures, printed cheques from an old test file, and they looked fine. A few minutes later, when Mary printed production cheques, they came out blank, except for variable data -- no headings, no company name, no MICR line. We reset the printer, and Mary backed out of Chqmaster and went back in, but she still got an unusual message about signatures. We thought it was okay for her to proceed. Everything looked okay (including transit #), except the production cheques were missing signatures.

ANSWER: Mary got the message about the signatures because the file had already been printed. Chqmaster was flagging that a supervisor would need to be involved for signatures on the second run.

The reason the headings, company name, MICR line, etc. were dropped on Mary's first cheque run -- a coincidence of timing. Between Mary's pressing F1 and printing the cheques, Nancy logged out of Chqmaster. The act of logging out deleted all the data that Mary's F1 had set up. In short, the printer was made unready to receive Chqmaster data.

====User cannot print or connect to printer====
One of the steps in the CheqMaster routine is Initialize Printer, in which the program tries to connect to a printer on port LPT2. If this step doesn't work, the program was likely run via the executable, cheques.exe, rather than the batch file, which sets up the printer port first. Run CHEQUES2.bat instead.

==Edit MICR code using Chqmaster menu==

Log into Cheque Master. The program is cheques.exe, but the desktop icon is the easiest way to get in. Id and password are in CONFIGUR.VCD, which can be emailed to Michael Guenzel mguenzel@vision-craft.com in the event of a problem. First try restoring the contents of ChqMaster from the most recent backup.

From the Main Menu, F6 Administration

F3 Forms Maintenance: There will be 3 forms – CAD, USD, and Imp and three actions – add, change, delete.

F2 Change / Select form (CAD)

F8 Edit MICR line: overtype field to be changed (e.g., change branch transit number 00900 to 30120)

Press Enter

F9 repeatedly to get out

Print a test cheque

=Technical Notes=

* The cheque file is simply a text file with a .dat extension. It can be opened with Notepad to examine the cheque data for troubleshooting purposes. *DO NOT ALTER THE FILE UNDER ANY CIRCUMSTANCES.*
* The cheque file is placed on the IFS. Ensure that the user generating cheques has read/write privileges to the IFS share, otherwise the process will stop mid-way and no file will be available to print.

Tags: Cheque master, Chequemaster
[[Category: Software connected to IBM i]]

Information Systems:Generic user profiles for temporary warehouse employees

2022-07-14T19:15:40Z

Anmolm:

4 user profiles were created specifically for use by temporary warehouse employees during their "tryout" period. This is to prevent the rapid accumulation of stale profiles on the system. There are 2 users for each temp agency. Gerald will keep track of these assignments. A new profile can be created if/when a temp employee transitions into being a uniPHARM employee.

{| class="wikitable sortable"
|-
! User !! Password
|-
| ADECCO1 || Adecco2051
|-
| ADECCO2 || Adecco2052
|-
| ADECCO3 || Adecco2053
|-
| ADECCO4 || Adecco2054
|-
| RANDSTAD1 || Rand2051
|-
| RANDSTAD2 || Rand2052
|-
| RANDSTAD3 || Rand2053
|-
| RANDSTAD4 || Rand2054
|}

Information Systems:Generic user profiles for temporary warehouse employees

2022-07-14T19:15:18Z

Anmolm:

Information Systems:Adobe Creative Cloud for Teams

2022-07-13T18:55:56Z

Anmolm:

==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|| teresab || - || Adobe Creative Cloud License
|-
| ccmediauser2@unipharm.com || NewVisionIT2051|| donnak|| anmolm || Adobe Creative Cloud License
|-
| ccmediauser3@unipharm.com || NewVisionIT2051! || || angelac || 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:New Computer Setup

2022-07-07T21:31:26Z

Anmolm:

This Page will give you brief information about what to do to set up a new computer.

==Windows 10 Image==
Generally, Lenovo's laptop images are good so, there is no need to format and use a generic Windows 10 image.

==Setup Steps==
# Select '''Canada''' in region and click '''Yes'''.
# In keyboard layout select '''US'''.
# Skip the second keyboard option.
# Connect with the internet, you can connect with the ethernet cable or connect to a Wifi.
# Create a local user with '''username: adminit Password: visionit''' and click '''next'''.
# Select '''NO in location''' option and click '''Accept'''.
# Select '''NO in Find my Device''' user can't connect to their MS account due to Group Policy, So, the option is pointless.
# Select '''Send Required diagnostic data''' and select '''Accept'''.
# Select '''NO in Improve inking and typing''' option and click '''Accept'''.
# Select '''NO for tailored experiences with diagnostic data''' and click '''Accept'''. This will not reduce the number of ads, but this option will not send data to Microsoft.
# Select '''NO for advertising ID''' and click '''Accept'''.
# Use '''Not now for Cortana'''.
# Now Windows is set up. It will take some minutes to complete the setup process.

==Computer Name Notations==
After windows is setup up, We want to change the default computer name to a more appropriate name before we connect the computer to the Domain. The computer naming convention is as follow:
 ''Department'' '''''-''''' ''User's full Firstname and last name initial'' '''''-''''' ''number depending how many computer a user have'' For Example:'''''IT-JackM-01''''' OR '''''IT-JackM-02''''' OR '''''DC-Common-01''''' (Common Computers) If there are two people with same name, last name initials with help in identifying between them.

===Notations===

{| class="wikitable"
|-
! Department !! Notation
|-
| Finance|| FIN
|-
| warehouse || DC
|-
| Information Technology || IT
|-
| Purchasing || PUR
|-
| Buying || BUY
|-
| Customer Service || CS
|-
| Executives || EXC
|-
| Spare || SPARE
|-
| Others || UWD
|}

==Softwares to install==
This section will guide through different software required on a machine. Not all machines require all software so, be decide where the computer will be deployed and install accordingly.

{| class="wikitable"
|-
! No. !! Software !! Which Computer to Install !! Where to Find !! Notes
|-
| 1. || Mocha TN5250 || All Computers || Can be found on superserver (\\superserver\UWD Software\MochaSoft) (registration: UNIPHARM / 040965) || ERP System (Green Screen)
|-
| 2. || ASW || All Computers || Can be found on superserver (\\superserver\UWD Software\ASW\ASW GUI\Disk1) || GUI Version of Mocha TN5250
|-
| 3. || Chrome || All Computers || Can be found on superserver (\\superserver\UWD Software\Chrome) || Google Chrome
|-
| 4. || Adobe Acrobat Reader || All Computers || Download from web || Just the free version
|-
| 5. || Microsoft Office Home & Business 2019 || All Computers || Can be found on superserver (\\superserver\UWD Software\Microsoft Office), Keys Can be found at (\\superserver\Tech\common\Business Case Documents\2020\MS Office Upgrade & Email Migration (Complete)\Microsoft Office 2019 Licence Keys copy.xlsx) || Read More about MS Office
|-
| 6. || ACR Trend Reader || Warehouse || Can be foundon superserver (\\Superserver\UWD Software\ACR TrendReader) || Reads Thermostat Temp
|-
| 7. || 3CX Client || Customer Service || Can be found on superserver (\\Superserver\UWD Software\3cx) || To make/receive calls from computer
|-
| 8. || VIP Doc View || All Computers || Can be found on Superserver (\\Superserver\UWD Software\Gauss\VIP DocView) || Scanning Liberary
|-
| 9. || SRFax || All Computers || Can be Found on Superserver (\\Superserver\UWD Software\SRFax Printer Driver) || Driver to convert doc for fax
|-
| 10. || Fixme.it || All Computers || Can be found on Superserver (\\Superserver\UWD Software\Techinline Fix Me Unattended Client) || Unattented clients for remove service
|-
| 11. || ACS Analyser || Managers || Can be found on Superserver (\\Superserver\UWD Software\ASW Analyzer Newest Version) || Database software need configuration
|-
| 12. || iBMi Access || Selective Computers || Can be found on Superserver (\\Superserver\UWD Software\IBMiAccess_v1r1_WindowsAP_English) || Utility software for IBMi
|-
| 13. || Vantage || Laptops || Can be found in MS Store || For lenovo updates
|-
| 14. || SEP || All Computers || NA || NA
|}

Information Systems:New Computer Setup

2022-07-07T21:24:23Z

Anmolm:

Information Systems:New Computer Setup

2022-07-07T20:56:39Z

Anmolm:

This Page will give you brief information about what to do to set up a new computer.

==Windows 10 Image==
Generally, Lenovo's laptop images are good so, there is no need to format and use a generic Windows 10 image.

==Setup Steps==
# Select '''Canada''' in region and click '''Yes'''.
# In keyboard layout select '''US'''.
# Skip the second keyboard option.
# Connect with the internet, you can connect with the ethernet cable or connect to a Wifi.
# Create a local user with '''username: adminit Password: visionit''' and click '''next'''.
# Select '''NO in location''' option and click '''Accept'''.
# Select '''NO in Find my Device''' user can't connect to their MS account due to Group Policy, So, the option is pointless.
# Select '''Send Required diagnostic data''' and select '''Accept'''.
# Select '''NO in Improve inking and typing''' option and click '''Accept'''.
# Select '''NO for tailored experiences with diagnostic data''' and click '''Accept'''. This will not reduce the number of ads, but this option will not send data to Microsoft.
# Select '''NO for advertising ID''' and click '''Accept'''.
# Use '''Not now for Cortana'''.
# Now Windows is set up. It will take some minutes to complete the setup process.

==Computer Name Notations==
After windows is setup up, We want to change the default computer name to a more appropriate name before we connect the computer to the Domain. The computer naming convention is as follow:
 ''Department'' '''''-''''' ''User's full Firstname and last name initial'' '''''-''''' ''number depending how many computer a user have'' For Example:'''''IT-JackM-01''''' OR '''''IT-JackM-02''''' OR '''''DC-Common-01''''' (Common Computers) If there are two people with same name, last name initials with help in identifying between them.

===Notations===

{| class="wikitable"
|-
! Department !! Notation
|-
| Finance|| FIN
|-
| warehouse || DC
|-
| Information Technology || IT
|-
| Purchasing || PUR
|-
| Buying || BUY
|-
| Customer Service || CS
|-
| Executives || EXC
|-
| Spare || SPARE
|-
| Others || UWD
|}

==Softwares to install==
This section will guide through different software required on a machine. Not all machines require all software so, be decide where the computer will be deployed and install accordingly.

{| class="wikitable"
|-
! No. !! Software !! Which Computer to Install !! Where to Find !! Notes
|-
| 1. || Mocha TN5250 || All Computers || Can be found on superserver (\\superserver\UWD Software\MochaSoft) (registration: UNIPHARM / 040965) || ERP System (Green Screen)
|-
| 2. || ASW || All Computers || Can be found on superserver (\\superserver\UWD Software\ASW\ASW GUI\Disk1) || GUI Version of Mocha TN5250
|-
| 3. || Chrome || All Computers || Can be found on superserver (\\superserver\UWD Software\Chrome) || Google Chrome
|-
| 4. || Adobe Acrobat Reader || All Computers || Download from web || Just the free version
|-
| 5. || Microsoft Office Home & Business 2019 || All Computers || Can be found on superserver (\\superserver\UWD Software\Microsoft Office) || Read More about MS Office
|-
| 6. || ACR Trend Reader || Warehouse || Can be foundon superserver (\\Superserver\UWD Software\ACR TrendReader) || Reads Thermostat Temp
|-
| 7. || 3CX Client || Customer Service || Can be found on superserver (\\Superserver\UWD Software\3cx) || To make/receive calls from computer
|-
| 8. || VIP Doc View || All Computers || Can be found on Superserver (\\Superserver\UWD Software\Gauss\VIP DocView) || Scanning Liberary
|-
| 9. || SRFax || All Computers || Can be Found on Superserver (\\Superserver\UWD Software\SRFax Printer Driver) || Driver to convert doc for fax
|-
| 10. || Fixme.it || All Computers || Can be found on Superserver (\\Superserver\UWD Software\Techinline Fix Me Unattended Client) || Unattented clients for remove service
|-
| 11. || ACS Analyser || Managers || Can be found on Superserver (\\Superserver\UWD Software\ASW Analyzer Newest Version) || Database software need configuration
|-
| 12. || iBMi Access || Selective Computers || Can be found on Superserver (\\Superserver\UWD Software\IBMiAccess_v1r1_WindowsAP_English) || Utility software for IBMi
|-
| 13. || Vantage || Laptops || Can be found in MS Store || For lenovo updates
|}

Information Systems:New Computer Setup

2022-07-07T20:49:47Z

Anmolm:

This Page will give you brief information about what to do to set up a new computer.

==Windows 10 Image==
Generally, Lenovo's laptop images are good so, there is no need to format and use a generic Windows 10 image.

==Setup Steps==
# Select '''Canada''' in region and click '''Yes'''.
# In keyboard layout select '''US'''.
# Skip the second keyboard option.
# Connect with the internet, you can connect with the ethernet cable or connect to a Wifi.
# Create a local user with '''username: adminit Password: visionit''' and click '''next'''.
# Select '''NO in location''' option and click '''Accept'''.
# Select '''NO in Find my Device''' user can't connect to their MS account due to Group Policy, So, the option is pointless.
# Select '''Send Required diagnostic data''' and select '''Accept'''.
# Select '''NO in Improve inking and typing''' option and click '''Accept'''.
# Select '''NO for tailored experiences with diagnostic data''' and click '''Accept'''. This will not reduce the number of ads, but this option will not send data to Microsoft.
# Select '''NO for advertising ID''' and click '''Accept'''.
# Use '''Not now for Cortana'''.
# Now Windows is set up. It will take some minutes to complete the setup process.

==Computer Name Notations==
After windows is setup up, We want to change the default computer name to a more appropriate name before we connect the computer to the Domain. The computer naming convention is as follow:
 ''Department'' '''''-''''' ''User's full Firstname and last name initial'' '''''-''''' ''number depending how many computer a user have'' For Example:'''''IT-JackM-01''''' OR '''''IT-JackM-02''''' OR '''''DC-Common-01''''' (Common Computers) If there are two people with same name, last name initials with help in identifying between them.

===Notations===

{| class="wikitable"
|-
! Department !! Notation
|-
| Finance|| FIN
|-
| warehouse || DC
|-
| Information Technology || IT
|-
| Purchasing || PUR
|-
| Buying || BUY
|-
| Customer Service || CS
|-
| Executives || EXC
|-
| Spare || SPARE
|-
| Others || UWD
|}

==Softwares to install==
This section will guide through different software required on a machine. Not all machines require all software so, be decide where the computer will be deployed and install accordingly.

{| class="wikitable"
|-
! No. !! Software !! Which Computer to Install !! Where to Find !! Notes
|-
| 1. || Mocha TN5250 || All Computers || Can be found on superserver (\\superserver\UWD Software\MochaSoft) (registration: UNIPHARM / 040965) || ERP System (Green Screen)
|-
| 2. || ASW || All Computers || Can be found on superserver (\\superserver\UWD Software\ASW\ASW GUI\Disk1) || GUI Version of Mocha TN5250
|-
| 3. || Chrome || All Computers || Can be found on superserver (\\superserver\UWD Software\Chrome) || Google Chrome
|-
| 4. || Adobe Acrobat Reader || All Computers || Download from web || Just the free version
|-
| 5. || Microsoft Office Home & Business 2019 || All Computers || Can be found on superserver (\\superserver\UWD Software\Microsoft Office) || Read More about MS Office
|-
| 6. || ACR Trend Reader || Warehouse || Can be foundon superserver (\\Superserver\UWD Software\ACR TrendReader) || Reads Thermostat Temp
|-
| 7. || 3CX Client || Customer Service || Can be found on superserver (\\Superserver\UWD Software\3cx) || To make/receive calls from computer
|-
| 8. || VIP Doc View || All Computers || Can be found on Superserver (\\Superserver\UWD Software\Gauss\VIP DocView) || Pulls scanned docs from AS400
|-
| 9. || SRFax || All Computers || Can be Found on Superserver (\\Superserver\UWD Software\SRFax Printer Driver) || Driver to convert doc for fax
|-
| 10. || Fixme.it || All Computers || Can be found on Superserver (\\Superserver\UWD Software\Techinline Fix Me Unattended Client) || Unattented clients for remove service
|-
| 11. || ACS Analyser || Managers || Can be found on Superserver (\\Superserver\UWD Software\ASW Analyzer Newest Version) || Database software need configuration
|-
| 12. || iBMi Access || Selective Computers || Can be found on Superserver (\\Superserver\UWD Software\IBMiAccess_v1r1_WindowsAP_English) || Utility software for IBMi
|-
| 13. || Vantage || Laptops || Can be found in MS Store || For lenovo updates
|}

Information Systems:UWDDC4 Domain Controller

2022-07-04T21:31:17Z

Anmolm:

=Outdated=
This Active Directory domain controller holds none of the FSMO roles for the unipharm.local domain.

This server has an OS of Windows Server 2012R2 and the only server role that is installed is to be a domain controller. No other applications or services are installed and no other programs or services SHOULD be installed on a domain controller. The AD setup is generic as in there is only 1 forest with 1 domain and no sub domains. There is only 1 site configured so replication only occurs with the other DC, which is UWDDC1.

Due to the OS being Server 2012R2, all of the GPO templates for Windows7 clients and Server 2008R2 clients were included. DarrenF installed the Windows10 GPO templates in early 2016 for testing purposes. When Windows10 clients are deployed, the GPO templates will be applicable.

The OU's in the unipharm.local are organized by department with a couple of exceptions. Buyers have different GPO's assigned to them so buyer's assistants have their own OU and their own GPO's. The GPO's assigned to JohnT and JeremyM are in the Business Intelligence OU because they wanted the same GPO settings. To be more logical, JohnT would be in the Managers OU and Jeremy should be in the IT OU. The design of the OU structure is fine for uniPHARM but might not scale up if the number of staff doubles or triples and there are many more departments doing very different work.

The list of GPO files in AD are properly labeled for what they do. A GPO marked as for printers only handles printers, a GPO for mapped drives only handles mapped drives. There are GPO files with many many settings and they are marked logically so that it is obvious. The GPO files that contain lots of settings are assigned to most of the departmental OU's.

As of 2018, the IT department is not using GPO's to deploy software, only for Windows configuration, printers, mapped drives and URL favourites.

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

Information Systems:UWDDC3 Domain Controller

2022-07-04T21:30:55Z

Anmolm:

=Outdated=
This Active Directory domain controller holds all the FSMO roles for the unipharm.local domain.

This server has an OS of Windows Server 2012R2 and the only server role that is installed is to be a domain controller. No other applications or services are installed and no other programs or services SHOULD be installed on a domain controller. The AD setup is generic as in there is only 1 forest with 1 domain and no sub domains. There is only 1 site configured so replication only occurs with the other DC, which is UWDDC2.

Due to the OS being Server 2012R2, all of the GPO templates for Windows7 clients and Server 2008R2 clients were included. DarrenF installed the Windows10 GPO templates in early 2016 for testing purposes. When Windows 10 clients are deployed, the GPO templates will be applicable.

The OU's in the unipharm.local are organized by department with a couple of exceptions. Buyers have different GPO's assigned to them so buyer's assistants have their own OU and their own GPO's. The GPO's assigned to JohnT and JeremyM are in the Business Intelligence OU because they wanted the same GPO settings. To be more logical, JohnT would be in the Managers OU and Jeremy should be in the IT OU. The design of the OU structure is fine for uniPHARM but might not scale up if the number of staff doubles or triples and there are many more departments doing very different work.

The list of GPO files in AD are properly labeled for what they do. A GPO marked as for printers only handles printers, a GPO for mapped drives only handles mapped drives. There are GPO files with many many settings and they are marked logically so that it is obvious. The GPO files that contain lots of settings are assigned to most of the departmental OU's.

As of 2018, the IT department is not using GPO's to deploy software, only for Windows configuration, printers, mapped drives and URL favourites.

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

Special:Badtitle/NS102:Page/Accounting Finance:CIBC-Entering eDEPOSITS

2022-06-21T16:36:26Z

Anmolm:

{{#access: assigned to = Group/Finance Group | actions = edit, read}}
{{#manage rights: assigned to = User:Nancyn}}

Special:Badtitle/NS102:Page/Accounting Finance:CIBC-Entering eDEPOSITS

2022-06-21T16:36:10Z

Anmolm:

{{#access: assigned to = Group:Group/Finance Group | actions = edit, read}}
{{#manage rights: assigned to = User:Nancyn}}

Special:Badtitle/NS102:Page/Accounting Finance:CIBC-Entering eDEPOSITS

2022-06-21T16:35:01Z

Anmolm:

{{#access: assigned to = Group: Group/Finance Group | actions = edit, read}}
{{#manage rights: assigned to = User:Nancyn}}

Special:Badtitle/NS102:Page/Accounting Finance:CIBC-Entering eDEPOSITS

2022-06-21T16:32:36Z

Anmolm:

{{#access: assigned to = Group:Finance Group | actions = edit, read}}
{{#manage rights: assigned to = User:Nancyn}}

Special:Badtitle/NS102:Group/Finance Group

2022-06-21T16:30:03Z

Anmolm:

{{#member: members = User:Nancyn, User:Christinet, User:Donnak, User:Angelac, User:Ralphl, User:Sionya, User:Williamw, User:Gurmeetm}}
{{#manage group: assigned to = User:Nancyn}}

Special:Badtitle/NS102:Group/Finance Group

2022-06-21T16:27:43Z

Anmolm:

{{#member: members = User:Nancyn, User:Harmanr, User:Christinet, User:Donnak, User:Angelac, User:Ralphl, User:Sionya, User:Williamw, User:Gurmeetm}}
{{#manage group: assigned to = User:Nancyn}}

File:image.png

2022-05-15T23:42:09Z

Anmolm: File uploaded with MsUpload

File uploaded with MsUpload

Information Systems:How to Get Phone's Mac Address?

2022-05-15T23:36:27Z

Anmolm: Reverted edits by Anmolm (talk) to last revision by Jeremym

=Overview=

To provide a better user experience for staff when accessing the staff wifi from their personal mobile devices IT needs to save the MAC address of their device inside the Staff Wi-Fi admin page. If staff purchase a new phone or new staff come on board, the MAC address of your mobile device will not be known. The purpose of this article is to provide some useful steps staff can follow to help them find the MAC address of their mobile device so they can provide it to the IT dept for it to be added to the saved device list in the Staff Wi-Fi.

=Phones Type=

==iPhones==
1. Unlock your phone and locate the settings and open it.
[[File:iPhone Step1.jpg|frameless|left]] 

2. Click on the Wi-Fi option.
[[File:iPhone Step2.jpg|frameless|left]] 

3. Locate uwd_staff and click on the Blue “i” icon.
[[File:iPhone Step3.jpg|frameless|left]] 

4. Turn off the Private Address and the Wi-Fi Address below will change. All we need is that Wi-Fi Address to add your device to our system.
[[File:IPhone Step4.jpg|frameless|left]] 

 Note: For this particular WIFI (SSID) Private mac address needs to be turned off otherwise it won't connect.

==Android/SamSung==
1. Unlock your phone and locate the settings and open it.
[[File:samsung step1.jpg|frameless|left]] 

2. Go all the way down and click on About Phone .
[[File:samsung step2.jpg|frameless|left]] 

3. Click on Status information .
[[File:samsung step3.1.jpg|frameless|left]] 

4. Send IT dept the full Phone Wi-Fi MAC address so, they can put you into the system.
[[File:samsung step4.jpg|frameless|left]] 

5. Now, to connect with the Wi-Fi, Go to the main menu and from there choose Connections .
[[File:samsung step5.jpg|frameless|left]] 

6. Select Wi-Fi .
[[File:samsung step6.jpg|frameless|left]] 

7. Select uwd_staff .
[[File:samsung step7.jpg|frameless|left]] 

8. Click of gear icon as shown.
[[File:samsung step8.jpg|frameless|left]] 

9. Click View more .
[[File:samsung step9.jpg|frameless|left]] 

10. Click on MAC address type .
[[File:samsung step10.jpg|frameless|left]] 

11. Select Phone MAC from the menu.
[[File:samsung step11.jpg|frameless|left]] 

12. Turn on/off the wifi and connect to uwd_staff and you should be connected.
[[File:samsung step12.jpg|frameless|left]] 

 

 If you are stuck and any point please let IT dept know and we will be more than happy to help. 

[[Category: Miscellaneous I.T.]]

Information Systems:How to Get Phone's Mac Address?

2022-05-15T23:36:16Z

Anmolm:

=Overview=

To provide a better user experience for staff when accessing the staff wifi from their personal mobile devices IT needs to save the MAC address of their device inside the Staff Wi-Fi admin page. If staff purchase a new phone or new staff come on board, the MAC address of your mobile device will not be known. The purpose of this article is to provide some useful steps staff can follow to help them find the MAC address of their mobile device so they can provide it to the IT dept for it to be added to the saved device list in the Staff Wi-Fi.

=Phones Type=

==iPhones==
# Unlock your phone and locate the settings and open it.
:[[File:iPhone Step1.jpg]]
# Click on the Wi-Fi option.
[[File:iPhone Step2.jpg|frameless|left]] 

# Locate uwd_staff and click on the Blue “i” icon.
[[File:iPhone Step3.jpg|frameless|left]] 

4. Turn off the Private Address and the Wi-Fi Address below will change. All we need is that Wi-Fi Address to add your device to our system.
[[File:IPhone Step4.jpg|frameless|left]] 

 Note: For this particular WIFI (SSID) Private mac address needs to be turned off otherwise it won't connect.

==Android/SamSung==
1. Unlock your phone and locate the settings and open it.
[[File:samsung step1.jpg|frameless|left]] 

2. Go all the way down and click on About Phone .
[[File:samsung step2.jpg|frameless|left]] 

3. Click on Status information .
[[File:samsung step3.1.jpg|frameless|left]] 

4. Send IT dept the full Phone Wi-Fi MAC address so, they can put you into the system.
[[File:samsung step4.jpg|frameless|left]] 

5. Now, to connect with the Wi-Fi, Go to the main menu and from there choose Connections .
[[File:samsung step5.jpg|frameless|left]] 

6. Select Wi-Fi .
[[File:samsung step6.jpg|frameless|left]] 

7. Select uwd_staff .
[[File:samsung step7.jpg|frameless|left]] 

8. Click of gear icon as shown.
[[File:samsung step8.jpg|frameless|left]] 

9. Click View more .
[[File:samsung step9.jpg|frameless|left]] 

10. Click on MAC address type .
[[File:samsung step10.jpg|frameless|left]] 

11. Select Phone MAC from the menu.
[[File:samsung step11.jpg|frameless|left]] 

12. Turn on/off the wifi and connect to uwd_staff and you should be connected.
[[File:samsung step12.jpg|frameless|left]] 

 

 If you are stuck and any point please let IT dept know and we will be more than happy to help. 

[[Category: Miscellaneous I.T.]]

Information Systems:How to Get Phone's Mac Address?

2022-05-15T23:35:41Z

Anmolm:

=Overview=

To provide a better user experience for staff when accessing the staff wifi from their personal mobile devices IT needs to save the MAC address of their device inside the Staff Wi-Fi admin page. If staff purchase a new phone or new staff come on board, the MAC address of your mobile device will not be known. The purpose of this article is to provide some useful steps staff can follow to help them find the MAC address of their mobile device so they can provide it to the IT dept for it to be added to the saved device list in the Staff Wi-Fi.

=Phones Type=

==iPhones==
# Unlock your phone and locate the settings and open it.
:[[File:iPhone Step1.jpg|frameless|left]]
# Click on the Wi-Fi option.
[[File:iPhone Step2.jpg|frameless|left]] 

# Locate uwd_staff and click on the Blue “i” icon.
[[File:iPhone Step3.jpg|frameless|left]] 

4. Turn off the Private Address and the Wi-Fi Address below will change. All we need is that Wi-Fi Address to add your device to our system.
[[File:IPhone Step4.jpg|frameless|left]] 

 Note: For this particular WIFI (SSID) Private mac address needs to be turned off otherwise it won't connect.

==Android/SamSung==
1. Unlock your phone and locate the settings and open it.
[[File:samsung step1.jpg|frameless|left]] 

2. Go all the way down and click on About Phone .
[[File:samsung step2.jpg|frameless|left]] 

3. Click on Status information .
[[File:samsung step3.1.jpg|frameless|left]] 

4. Send IT dept the full Phone Wi-Fi MAC address so, they can put you into the system.
[[File:samsung step4.jpg|frameless|left]] 

5. Now, to connect with the Wi-Fi, Go to the main menu and from there choose Connections .
[[File:samsung step5.jpg|frameless|left]] 

6. Select Wi-Fi .
[[File:samsung step6.jpg|frameless|left]] 

7. Select uwd_staff .
[[File:samsung step7.jpg|frameless|left]] 

8. Click of gear icon as shown.
[[File:samsung step8.jpg|frameless|left]] 

9. Click View more .
[[File:samsung step9.jpg|frameless|left]] 

10. Click on MAC address type .
[[File:samsung step10.jpg|frameless|left]] 

11. Select Phone MAC from the menu.
[[File:samsung step11.jpg|frameless|left]] 

12. Turn on/off the wifi and connect to uwd_staff and you should be connected.
[[File:samsung step12.jpg|frameless|left]] 

 

 If you are stuck and any point please let IT dept know and we will be more than happy to help. 

[[Category: Miscellaneous I.T.]]

Information Systems:How to Get Phone's Mac Address?

2022-05-15T23:34:54Z

Anmolm:

=Overview=

To provide a better user experience for staff when accessing the staff wifi from their personal mobile devices IT needs to save the MAC address of their device inside the Staff Wi-Fi admin page. If staff purchase a new phone or new staff come on board, the MAC address of your mobile device will not be known. The purpose of this article is to provide some useful steps staff can follow to help them find the MAC address of their mobile device so they can provide it to the IT dept for it to be added to the saved device list in the Staff Wi-Fi.

=Phones Type=

==iPhones==
# Unlock your phone and locate the settings and open it.
:[[File:iPhone Step1.jpg|frameless|left]] 

# Click on the Wi-Fi option.
[[File:iPhone Step2.jpg|frameless|left]] 

# Locate uwd_staff and click on the Blue “i” icon.
[[File:iPhone Step3.jpg|frameless|left]] 

4. Turn off the Private Address and the Wi-Fi Address below will change. All we need is that Wi-Fi Address to add your device to our system.
[[File:IPhone Step4.jpg|frameless|left]] 

 Note: For this particular WIFI (SSID) Private mac address needs to be turned off otherwise it won't connect.

==Android/SamSung==
1. Unlock your phone and locate the settings and open it.
[[File:samsung step1.jpg|frameless|left]] 

2. Go all the way down and click on About Phone .
[[File:samsung step2.jpg|frameless|left]] 

3. Click on Status information .
[[File:samsung step3.1.jpg|frameless|left]] 

4. Send IT dept the full Phone Wi-Fi MAC address so, they can put you into the system.
[[File:samsung step4.jpg|frameless|left]] 

5. Now, to connect with the Wi-Fi, Go to the main menu and from there choose Connections .
[[File:samsung step5.jpg|frameless|left]] 

6. Select Wi-Fi .
[[File:samsung step6.jpg|frameless|left]] 

7. Select uwd_staff .
[[File:samsung step7.jpg|frameless|left]] 

8. Click of gear icon as shown.
[[File:samsung step8.jpg|frameless|left]] 

9. Click View more .
[[File:samsung step9.jpg|frameless|left]] 

10. Click on MAC address type .
[[File:samsung step10.jpg|frameless|left]] 

11. Select Phone MAC from the menu.
[[File:samsung step11.jpg|frameless|left]] 

12. Turn on/off the wifi and connect to uwd_staff and you should be connected.
[[File:samsung step12.jpg|frameless|left]] 

 

 If you are stuck and any point please let IT dept know and we will be more than happy to help. 

[[Category: Miscellaneous I.T.]]

Information Systems:How to Get Phone's Mac Address?

2022-05-15T23:33:37Z

Anmolm:

=Overview=

To provide a better user experience for staff when accessing the staff wifi from their personal mobile devices IT needs to save the MAC address of their device inside the Staff Wi-Fi admin page. If staff purchase a new phone or new staff come on board, the MAC address of your mobile device will not be known. The purpose of this article is to provide some useful steps staff can follow to help them find the MAC address of their mobile device so they can provide it to the IT dept for it to be added to the saved device list in the Staff Wi-Fi.

=Phones Type=

==iPhones==
1. Unlock your phone and locate the settings and open it.
:[[File:iPhone Step1.jpg|frameless|left]] 

2. Click on the Wi-Fi option.
[[File:iPhone Step2.jpg|frameless|left]] 

3. Locate uwd_staff and click on the Blue “i” icon.
[[File:iPhone Step3.jpg|frameless|left]] 

4. Turn off the Private Address and the Wi-Fi Address below will change. All we need is that Wi-Fi Address to add your device to our system.
[[File:IPhone Step4.jpg|frameless|left]] 

 Note: For this particular WIFI (SSID) Private mac address needs to be turned off otherwise it won't connect.

==Android/SamSung==
1. Unlock your phone and locate the settings and open it.
[[File:samsung step1.jpg|frameless|left]] 

2. Go all the way down and click on About Phone .
[[File:samsung step2.jpg|frameless|left]] 

3. Click on Status information .
[[File:samsung step3.1.jpg|frameless|left]] 

4. Send IT dept the full Phone Wi-Fi MAC address so, they can put you into the system.
[[File:samsung step4.jpg|frameless|left]] 

5. Now, to connect with the Wi-Fi, Go to the main menu and from there choose Connections .
[[File:samsung step5.jpg|frameless|left]] 

6. Select Wi-Fi .
[[File:samsung step6.jpg|frameless|left]] 

7. Select uwd_staff .
[[File:samsung step7.jpg|frameless|left]] 

8. Click of gear icon as shown.
[[File:samsung step8.jpg|frameless|left]] 

9. Click View more .
[[File:samsung step9.jpg|frameless|left]] 

10. Click on MAC address type .
[[File:samsung step10.jpg|frameless|left]] 

11. Select Phone MAC from the menu.
[[File:samsung step11.jpg|frameless|left]] 

12. Turn on/off the wifi and connect to uwd_staff and you should be connected.
[[File:samsung step12.jpg|frameless|left]] 

 

 If you are stuck and any point please let IT dept know and we will be more than happy to help. 

[[Category: Miscellaneous I.T.]]

Information Systems:How to Get Phone's Mac Address?

2022-05-15T23:33:17Z

Anmolm:

=Overview=

To provide a better user experience for staff when accessing the staff wifi from their personal mobile devices IT needs to save the MAC address of their device inside the Staff Wi-Fi admin page. If staff purchase a new phone or new staff come on board, the MAC address of your mobile device will not be known. The purpose of this article is to provide some useful steps staff can follow to help them find the MAC address of their mobile device so they can provide it to the IT dept for it to be added to the saved device list in the Staff Wi-Fi.

=Phones Type=

==iPhones==
1. Unlock your phone and locate the settings and open it.
:[[File:iPhone Step1.jpg|frameless|left]] 

2. Click on the Wi-Fi option.
[[File:iPhone Step2.jpg|frameless|left]] 

3. Locate uwd_staff and click on the Blue “i” icon.
[[File:iPhone Step3.jpg|frameless|left]] 

4. Turn off the Private Address and the Wi-Fi Address below will change. All we need is that Wi-Fi Address to add your device to our system.
[[File:IPhone Step4.jpg|frameless|left]] 

 Note: For this particular WIFI (SSID) Private mac address needs to be turned off otherwise it won't connect.

==Android/SamSung==
1. Unlock your phone and locate the settings and open it.
[[File:samsung step1.jpg|frameless|left]] 

2. Go all the way down and click on About Phone .
[[File:samsung step2.jpg|frameless|left]] 

3. Click on Status information .
[[File:samsung step3.1.jpg|frameless|left]] 

4. Send IT dept the full Phone Wi-Fi MAC address so, they can put you into the system.
[[File:samsung step4.jpg|frameless|left]] 

5. Now, to connect with the Wi-Fi, Go to the main menu and from there choose Connections .
[[File:samsung step5.jpg|frameless|left]] 

6. Select Wi-Fi .
[[File:samsung step6.jpg|frameless|left]] 

7. Select uwd_staff .
[[File:samsung step7.jpg|frameless|left]] 

8. Click of gear icon as shown.
[[File:samsung step8.jpg|frameless|left]] 

9. Click View more .
[[File:samsung step9.jpg|frameless|left]] 

10. Click on MAC address type .
[[File:samsung step10.jpg|frameless|left]] 

11. Select Phone MAC from the menu.
[[File:samsung step11.jpg|frameless|left]] 

12. Turn on/off the wifi and connect to uwd_staff and you should be connected.
[[File:samsung step12.jpg|frameless|left]] 

 

 If you are stuck and any point please let IT dept know and we will be more than happy to help. 

[[Category: Miscellaneous I.T.]]

Information Systems:How to Get Phone's Mac Address?

2022-05-15T23:32:20Z

Anmolm: Reverted edits by Anmolm (talk) to last revision by Jeremym

Information Systems:How to Get Phone's Mac Address?

2022-05-15T23:32:08Z

Anmolm:

=Overview=

To provide a better user experience for staff when accessing the staff wifi from their personal mobile devices IT needs to save the MAC address of their device inside the Staff Wi-Fi admin page. If staff purchase a new phone or new staff come on board, the MAC address of your mobile device will not be known. The purpose of this article is to provide some useful steps staff can follow to help them find the MAC address of their mobile device so they can provide it to the IT dept for it to be added to the saved device list in the Staff Wi-Fi. 
 Note: Images in the article are just for reference, what you see can be different than the images, please follow the instructions to be accurate. 
=Phones Type=

==iPhones==
1. Unlock your phone and locate the settings and open it.
[[File:iPhone Step1.jpg|frameless|left]] 

2. Click on the Wi-Fi option.
[[File:iPhone Step2.jpg|frameless|left]] 

3. Locate uwd_staff and click on the Blue “i” icon.
[[File:iPhone Step3.jpg|frameless|left]] 

4. Turn off the Private Address and the Wi-Fi Address below will change. All we need is that Wi-Fi Address to add your device to our system.
[[File:iphone Step4.1.png|frameless|left]] 

 Note: For this particular WIFI (SSID) Private mac address needs to be turned off otherwise it won't connect.

==Android/SamSung==
1. Unlock your phone and locate the settings and open it.
[[File:samsung step1.jpg|frameless|left]] 

2. Go all the way down and click on About Phone .
[[File:samsung step2.jpg|frameless|left]] 

3. Click on Status information .
[[File:samsung step3.1.jpg|frameless|left]] 

4. Send IT dept the full Phone Wi-Fi MAC address so, they can put you into the system.
[[File:samsung step4.jpg|frameless|left]] 

5. Now, to connect with the Wi-Fi, Go to the main menu and from there choose Connections .
[[File:samsung step5.jpg|frameless|left]] 

6. Select Wi-Fi .
[[File:samsung step6.jpg|frameless|left]] 

7. Select uwd_staff .
[[File:samsung step7.jpg|frameless|left]] 

8. Click of gear icon as shown.
[[File:samsung step8.jpg|frameless|left]] 

9. Click View more .
[[File:samsung step9.jpg|frameless|left]] 

10. Click on MAC address type .
[[File:samsung step10.jpg|frameless|left]] 

11. Select Phone MAC from the menu.
[[File:samsung step11.jpg|frameless|left]] 

12. Turn on/off the wifi and connect to uwd_staff and you should be connected.
[[File:samsung step12.jpg|frameless|left]] 

 

 If you are stuck and any point please let IT dept know and we will be more than happy to help. 

[[Category: Miscellaneous I.T.]]

Information Systems:Managing staff and guest devices on the wireless network

2022-05-10T16:52:27Z

Anmolm:

===Overview===
'''uwd_staff''' and '''uwd_guest''' are the wireless networks for staff and guest use, respectively. This article will discuss the management of devices connected to these networks.

A few configuration notes to provide context:

* Both networks use captive portal authentication. There is a separate captive portal instance for each network, but both use the same backend (RADIUS) to authenticate.
* uwd_guest uses captive portal only.
* uwd_staff has MAC authentication ''and'' captive portal authentication. MAC authentication takes precedence. Captive portal is used as a fallback.
* Both networks are on VLAN 2. DHCP is currently provided by the Telus-provisioned, Actiontec router in the Narc cage.
* Both are unencrypted (e.g. they do not use WPA/WPA2).

Despite MAC authentication being the primary authentication method for uwd_staff, the premise is that when a staff member joins a new device to the network, the MAC address will not yet exist in the database and thus authentication will 'fall back' to captive portal. For more information on the authentication scheme used in these networks, read [[Information_Systems:Advanced_wireless_administration_(WLAN)#Guest_and_staff_wireless_authentication|'''here''']].

===Procedure for adding a staff device===
The RADIUS user pool '''Staff_LocalAuth''' already contains credentials (matching their Windows credentials) for all staff, as of December 2017. These instructions are specifically for adding a MAC address to bypass captive portal authentication for a staff member. However, instructions for adding a new staff member (username/password) can be extrapolated here.

* You will receive an email - similar to the one below - when a staff member successfully authenticates a device using captive portal.
Date :2017-11-01 14:00:43
Device :ap-controller-office-2nd-floor
Description :Captive-portal authentication success for client 40-D3-AE-45-2E-04(192.168.1.106) user 'Darrenf'
* [https://172.30.18.80 Log in to WiNG] {{ userpass }}.
* Under the '''Configuration''' tab, navigate to '''RADIUS''' -> '''User Pools'''. Double-click the Staff_LocalAuth user pool to enter it.
* As is shown, both the MAC addresses used for MAC authentication and username/passwords used for CP authentication are defined here.
* Click 'Add'.
* Using the email, set MAC address as the username and password. '''''Important: Use lowercase and hyphens.'''''
* Add the MAC address and username to the table below. This, along with the email, are currently the only ways we can keep track of user-device relationships. It is unfortunate that a field doesn't exist in the WiNG implementation of RADIUS that we could use to specify this user-device relationship. Maybe in the future.
* For Group List, check uniPHARM_Staff. (There isn't much to groups right now.)
* Save the addition, and perform a '''Commit and Save'''. At this point, the changes are live.
* At this point, the staff member should no longer see the captive portal when connecting to the network.

===Procedure for connecting to the guest network===
There is nothing that needs to be done for a guest to be able to connect to uwd_guest, other than perhaps providing the staff member hosting the guest with the username/password. In due time, this will become common knowledge anyway. Currently, it is 'unipharm/guest'. All guests connect to the network under the same user.

===Caveats, issues, and other notes===
* Guest network consists of a single user (although I guess we could always define more, but they'll still be generic).
* Currently users in the staff user pool can log in to uwd_guest, despite being in a group that technically forbids this.
* Self-registration using OTPs (one-time passwords) to be explored in the future. Requires at least a VX controller.

===List of registered staff devices===
Company policy equates a successful login to an acceptance of the Terms of Conditions, as specified on the login page. Devices listed here should not prompt re-authentication via captive portal e.g. association to uwd_staff is via MAC authentication.
A list of Registered Staff Devices can be found here.[file:\\superserver\tech\common\Staff_Wifi\Staff_MAC_Addresses.xlsx]

[[Category: Wireless (WLAN)]]

Information Systems:Managing staff and guest devices on the wireless network

2022-05-10T16:52:16Z

Anmolm:

Information Systems:Managing staff and guest devices on the wireless network

2022-05-10T16:51:28Z

Anmolm:

===Overview===
'''uwd_staff''' and '''uwd_guest''' are the wireless networks for staff and guest use, respectively. This article will discuss the management of devices connected to these networks.

A few configuration notes to provide context:

* Both networks use captive portal authentication. There is a separate captive portal instance for each network, but both use the same backend (RADIUS) to authenticate.
* uwd_guest uses captive portal only.
* uwd_staff has MAC authentication ''and'' captive portal authentication. MAC authentication takes precedence. Captive portal is used as a fallback.
* Both networks are on VLAN 2. DHCP is currently provided by the Telus-provisioned, Actiontec router in the Narc cage.
* Both are unencrypted (e.g. they do not use WPA/WPA2).

Despite MAC authentication being the primary authentication method for uwd_staff, the premise is that when a staff member joins a new device to the network, the MAC address will not yet exist in the database and thus authentication will 'fall back' to captive portal. For more information on the authentication scheme used in these networks, read [[Information_Systems:Advanced_wireless_administration_(WLAN)#Guest_and_staff_wireless_authentication|'''here''']].

===Procedure for adding a staff device===
The RADIUS user pool '''Staff_LocalAuth''' already contains credentials (matching their Windows credentials) for all staff, as of December 2017. These instructions are specifically for adding a MAC address to bypass captive portal authentication for a staff member. However, instructions for adding a new staff member (username/password) can be extrapolated here.

* You will receive an email - similar to the one below - when a staff member successfully authenticates a device using captive portal.
Date :2017-11-01 14:00:43
Device :ap-controller-office-2nd-floor
Description :Captive-portal authentication success for client 40-D3-AE-45-2E-04(192.168.1.106) user 'Darrenf'
* [https://172.30.18.80 Log in to WiNG] {{ userpass }}.
* Under the '''Configuration''' tab, navigate to '''RADIUS''' -> '''User Pools'''. Double-click the Staff_LocalAuth user pool to enter it.
* As is shown, both the MAC addresses used for MAC authentication and username/passwords used for CP authentication are defined here.
* Click 'Add'.
* Using the email, set MAC address as the username and password. '''''Important: Use lowercase and hyphens.'''''
* Add the MAC address and username to the table below. This, along with the email, are currently the only ways we can keep track of user-device relationships. It is unfortunate that a field doesn't exist in the WiNG implementation of RADIUS that we could use to specify this user-device relationship. Maybe in the future.
* For Group List, check uniPHARM_Staff. (There isn't much to groups right now.)
* Save the addition, and perform a '''Commit and Save'''. At this point, the changes are live.
* At this point, the staff member should no longer see the captive portal when connecting to the network.

===Procedure for connecting to the guest network===
There is nothing that needs to be done for a guest to be able to connect to uwd_guest, other than perhaps providing the staff member hosting the guest with the username/password. In due time, this will become common knowledge anyway. Currently, it is 'unipharm/guest'. All guests connect to the network under the same user.

===Caveats, issues, and other notes===
* Guest network consists of a single user (although I guess we could always define more, but they'll still be generic).
* Currently users in the staff user pool can log in to uwd_guest, despite being in a group that technically forbids this.
* Self-registration using OTPs (one-time passwords) to be explored in the future. Requires at least a VX controller.

===List of registered staff devices===
Company policy equates a successful login to an acceptance of the Terms of Conditions, as specified on the login page. Devices listed here should not prompt re-authentication via captive portal e.g. association to uwd_staff is via MAC authentication.
A list of Registered Staff Devices can be found here.[file:///superserver/tech/common/Staff_Wifi/Staff_MAC_Addresses.xlsx Here]

[[Category: Wireless (WLAN)]]