New Core Migration: Financial Aid

Last night the IP range for Financial Aid was reconfigured to accommodate more workstations and printers in Kerr.

Cyder/IP change
Old ranges:
10.214.18.5 – 10.214.18.20 dynamic
10.214.18.21 – 10.214.18.84 static
New ranges:
10.214.18.5 – 10.214.18.55 dynamic
10.214.18.56 – 10.214.19.253 static
The result of this move was moving all hosts in bulk up into the new static range. Additionally, this new IP space will accommodate all workstations and printers in the CN_StudentAdmin security domain. This will become more relevant as we migrate these departments to the new core.

Printer change
Old IP printers were removed from workstations and replaced with new print queue printers.
Printer address: \\iscs-printq\KAd-108-Ricoh-MP-201
Printer IP: 10.214.18.90
Printer driver: PCL6 Universal v4.6
Security group: CN_Printers_KAd 108 Ricoh MP 201
ONID GPO: TSS – Printer Deployment – Financial Aid
TSS GPO: Printer Deployment – Financial Aid
Printer address: \\iscs-printq\KAd-220C-HP-LaserJet-4200TN
Printer IP: 10.214.18.87
Printer driver: HP Universal Printing PCL 6 (v6.0.0)
Security group: CN_Printers_KAd 220C HP LaserJet 4200TN
ONID GPO: TSS – Printer Deployment – Financial Aid
TSS GPO: Printer Deployment – Financial Aid
Printer address: \\iscs-printq\KAd-220C-Ricoh-MP-5002
Printer IP: 10.214.18.89
Printer driver: PCL6 Universal v4.6
Security group: CN_Printers_KAd 220C Ricoh MP 5002
ONID GPO: TSS – Printer Deployment – Financial Aid
TSS GPO: Printer Deployment – Financial Aid
Note: The GPOs only apply to the department’s users OU and domain users in the security group above.

Resolved Issues
IP printers were supposed to be removed automatically but weren’t on many systems. We resolved this manually given there weren’t many machines.
The reason for this is many printers were installed incorrectly with port names like 10.214.18.21_1. This likely occurred because an existing port wasn’t used when setting up printers. I’m looking into a way to accommodate for this.

Unresolved Issues
Just about every machine we logged into with our User+ account resulted in the error below. Most folks were running Office 2010 which could be related. I will submit a ticket for investigation.
IMG_3378